Solutions · Studios, Media and Catalog Itemion

Control Project Assets from Department Intake to Set Issue, Wrap and Long-Term Reuse

Connect costumes, props, set assets, furniture, kits, accessories, documents and specialist inventory to projects, departments, scenes, characters, locations, issue records, returns, wrap reconciliation and approved archive or reuse.

The solution can support storage-only archives, active production operations, multi-unit shoots, department-controlled access and post-project commercial or institutional reuse.

Projects and departments
Issue, return and continuity
Wrap, archive and reuse
From project setup to accountable archive and reuse
Configure + issue + reconcile + preserve
01
Configure Project Control
Create project, unit, department, role, access, title-alias and confidentiality structures.
02
Receive and Catalogue Assets
Record custody, project context, kits, sets, components, images, condition and locations.
03
Issue, Move and Return
Control department pulls, set issues, vehicles, temporary sites, returns and discrepancies.
04
Wrap, Archive and Reuse
Reconcile the project, restore inventory, preserve history and release approved assets to future use.
Every project asset should remain connected to ownership, department, location, issue and final disposition.
Project truth + custody truth
Choose the studio-asset operating model

Use Archive Storage, Managed Project Operations or Connected Reuse

The operating depth can vary by project, department, asset group or lifecycle stage. A closed archive, active shoot and reusable prop library do not need identical controls.

Swipe through the studio-asset models
01

Archive and Storage

Preserve closed-project assets with approved visibility, access, custody and long-term location control.

  • Dedicated or shared archive space
  • Project and department grouping
  • Restricted or named-user access
  • No compulsory commercial release
03

Connected Archive and Reuse

Prepare approved assets for future projects, controlled rentals, institutional access, sale or recycling.

  • Rights and release approval
  • Cross-project search and reuse
  • Rental or sales eligibility
  • Disposition and recycling history
Four connected studio-solution components

Control Projects, Asset Context, Movement and Final Disposition

Each component remains connected so a costume, prop, set piece or equipment kit can move through active use and long-term archive without losing custody or project history.

Swipe through the studio-solution components
01

Project, Department and Custody

Configure projects, units, departments, access and the authoritative identity of every controlled asset.

ProjectDepartmentCustodyAccess

View project and custody controls

02

Catalogue, Kits and Continuity

Connect categories, images, dimensions, scene context, characters, kits, sets and components.

CatalogueKitsScenesContinuity

View catalogue and continuity

03

Issue, Movement and Access

Reserve, issue, transfer and return assets across warehouses, stages, sets, sites and vehicles.

IssueSetTransitReturn

View issue and movement

04

Wrap, Archive and Reuse

Reconcile project assets, restore condition, assign archive status and control future use or disposition.

WrapReconcileArchiveReuse

View wrap and archive

See studio and project asset control in action

Follow an Asset from Project Setup to Set Issue, Wrap and Reuse

Start with the complete studio-asset architecture, then move through project configuration, receiving, custody, catalogue, kits, continuity, restricted storage, department pulls, issue-to-set movement, return, wrap, archive and approved reuse.

Slide 1 of 10

Complete studios, media and production architecture

02
Project, department and access configuration The screen configures project, aliases, units, departments, approved users, image visibility, embargo and operating ownership.
Step 1 · Configure project control

Create the Structure Used by the Active Project

The solution begins with units, departments, roles, confidentiality and ownership decisions.

  • Project, season, campaign or alias
  • Units and departments
  • Roles and access permissions
  • Embargo and restricted visibility
What this screen demonstrates Confidentiality controls protect the project without hiding operational responsibility.
03
Project asset intake and custody The screen records packages, assets, kits, sets, components, source, department, quantity, condition, custody QR and route.
Step 2 · Receive and identify

Preserve Package, Asset, Kit and Component Relationships

Every controlled asset receives the appropriate project and custody context.

  • Packages, assets and quantities
  • Kits, sets and components
  • Source, owner and department
  • Condition, identity and route
What this screen demonstrates Grouped kits can remain operationally connected while components retain individual control.
04
Asset catalogue, kits and continuity The screen loads category fields and links assets to kits, characters, scenes, episodes, continuity versions, images and documents.
Step 3 · Build the project catalogue

Describe the Asset in Physical and Creative Context

Category-driven data combines custody facts with the context needed by production teams.

  • Category-specific attributes
  • Kit and component relationships
  • Character, scene and episode
  • Continuity, images and documents
What this screen demonstrates The same record supports warehouse control and project-specific search.
05
Storage and restricted access The screen assigns project assets to racks, rails, cages, rooms and restricted zones with department and user permissions.
Step 4 · Store and protect

Connect Physical Location with Project Access Rules

The storage map can distinguish open, department-controlled, confidential and high-security areas.

  • Warehouse, room, cage, rack and rail
  • Project and department allocation
  • Restricted access and approvals
  • Current location and movement history
What this screen demonstrates Users see only the locations and assets permitted by their role.
06
Search, kit builder and project pull The screen filters by project, department, category, scene, character, continuity, availability and location and builds a pull.
Step 5 · Find and reserve assets

Build Department Pulls around the Schedule and Creative Brief

The project team can create kits, alternatives, holds and reservations with explicit context.

  • Project and department filters
  • Scene, character and continuity filters
  • Kit, shortlist and alternatives
  • Hold, reserve and approval
What this screen demonstrates Selections remain connected to the project schedule and responsible department.
07
Issue-to-set and transit The screen records assets, kits, responsible person, destination, vehicle, issue condition, expected return, scan and signature.
Step 6 · Transfer temporary custody

Know Who Has the Asset and Where It Is Being Used

Issue-to-set creates an accountable temporary location and responsible owner.

  • Responsible person or department
  • Set, stage, site, unit or vehicle
  • Issue date and expected return
  • Scan, signature and condition proof
What this screen demonstrates Assets remain visible while outside the primary warehouse.
08
Project return and discrepancy The screen compares expected and returned assets, kit components and condition and records missing, wrong or damaged items.
Step 7 · Return and inspect

Verify Assets, Kits and Components after Use

Partial returns and discrepancies remain open until the approved resolution is complete.

  • Expected, returned and outstanding
  • Kit and component completeness
  • Before-and-after condition
  • Hold, reviewer and next action
What this screen demonstrates The department and project context remains visible during discrepancy review.
09
Production wrap reconciliation The screen compares project totals across departments, vendors, units and temporary locations and captures sign-off and open issues.
Step 8 · Reconcile the project

Close Asset Responsibility across Every Department and Location

Wrap converts many operating records into one project-wide reconciliation result.

  • Expected versus returned totals
  • Departments, vendors and locations
  • Missing and unresolved assets
  • Department and manager sign-off
What this screen demonstrates A wrapped project can still contain open exceptions that remain visible and owned.
10
Archive, reuse and disposition The screen sets archive collection, rights, confidentiality, future project availability, rental, sale, donation, recycling or disposal.
Step 9 · Preserve or release

Turn Wrapped Inventory into an Accountable Archive or Reuse Pool

Final disposition remains controlled by ownership, rights, condition and approval.

  • Archive collection and location
  • Rights and confidentiality state
  • Future project or commercial availability
  • Value and disposition history
What this screen demonstrates Catalogue visibility does not override ownership or release restrictions.
Swipe through the Studios, Media and Production walkthrough
01
Build project control before assets begin moving

Project, Unit, Department, Access and Custody Control

Assets should be connected to the correct studio, project, season, unit, department and responsible team while retaining their permanent custody identity.

Confidential projects can use title aliases, restricted images, embargo dates and role-based visibility without breaking operational traceability.

Project and department structure
Restricted access
Permanent custody history
Swipe through project and custody controls

Project and Unit Structure

Create the operating context required by films, series, campaigns and multi-unit shoots.

  • Studio, project, season or campaign
  • Main, second or specialist unit
  • Episode, schedule or phase
  • Active, wrapped and archived states

Departments and Responsible Teams

Assign assets and workflows to the teams that own or operate them.

  • Costume, art, props and set decoration
  • Furniture, action, makeup or specialist teams
  • Department head and approved users
  • Shared and cross-department assets

Confidentiality and Access

Restrict sensitive project information while preserving operational accountability.

  • Project alias and restricted title
  • Role and department permissions
  • Image and metadata visibility
  • Embargo and release date

Permanent Custody Record

Connect the physical asset to ownership, project context, location and activity history.

  • Custody QR and readable identity
  • Owner, source and acquisition context
  • Current department and location
  • Issue, return and exception history
02
Describe assets in the language of the project

Asset Catalogue, Kits, Sets, Scenes and Continuity Context

The category should load the relevant attributes for costumes, props, furniture, set pieces, documents, equipment and specialist assets.

Project context can include character, scene, episode, location, continuity state, department kit and component relationships.

Category-driven attributes
Kit and set relationships
Scene and continuity context
Swipe through catalogue, kit and continuity controls

Category-Specific Asset Data

Capture the fields relevant to the physical and creative asset.

  • Type, material, dimensions and weight
  • Colour, finish, construction and condition
  • Brand, maker, era or provenance
  • Handling, care and safety restrictions

Kits, Sets and Components

Keep grouped assets operationally connected without losing individual custody.

  • Department kit or scene package
  • Hero, duplicate and backup units
  • Parent, child and component relationships
  • Complete, partial and missing states

Scene, Character and Continuity

Connect assets to the creative context required for controlled reuse during the project.

  • Character, talent or role
  • Scene, episode and schedule
  • Continuity look or version
  • Script, reference and approval notes

Images, Documents and Evidence

Retain the visual and documentary material required for custody and project use.

  • Front, back, detail and condition images
  • Purchase, rental or source documents
  • Continuity and set-reference images
  • Versions, reviewers and approvals
03
Control temporary custody outside the storage location

Department Pulls, Issue-to-Set, Site Movement and Return

Project teams need search, shortlist, reservation and issue workflows that reflect departments, scenes, schedules, units and temporary locations.

Every issue should identify the responsible person, destination, expected return, vehicle or handover and the assets or kits that moved.

Project search and pulls
Issue-to-set custody
Multi-location return control
Swipe through issue, movement and access controls

Project Search and Department Pulls

Find approved inventory using project, creative and operational context.

  • Project, department and category filters
  • Character, scene, episode and continuity
  • Location, availability and condition
  • Shortlist, kit and alternative selection

Issue and Handover

Transfer temporary responsibility to the approved person or team.

  • Responsible crew member or department
  • Set, stage, site or vehicle destination
  • Issue date and expected return
  • Scan, signature and condition proof

Temporary Locations and Transit

Keep assets visible while they move beyond the primary warehouse.

  • Stage, set, outdoor site or client location
  • Transit vehicle and movement state
  • Cross-unit or cross-department transfer
  • Restricted or high-security movement

Return and Discrepancy

Compare expected and returned assets, kits, components and condition.

  • Partial and complete return
  • Missing, wrong or damaged asset
  • Kit and component completeness
  • Hold, reviewer and next action
04
Close the project without losing future value

Catalog Itemion Wrap, Reconciliation, Archive and Approved Reuse

Wrap should reconcile expected assets, department holdings, temporary sites, vendors, returns, missing components, condition and final ownership decisions.

After reconciliation, assets can move to archive, future-project availability, controlled rental, sale, donation, recycling, disposal or another approved disposition.

Project wrap reconciliation
Archive and preservation
Rights-controlled reuse
Swipe through wrap, archive and reuse controls

Wrap Reconciliation

Compare project records with assets physically returned from every department and location.

  • Expected versus returned totals
  • Open issues and outstanding locations
  • Missing components and vendor assets
  • Department and manager sign-off

Condition, Care and Restoration

Prepare retained assets for long-term storage or future approved use.

  • Condition comparison and evidence
  • Cleaning, repair or specialist work
  • Packaging and archival preparation
  • Final condition and reviewer

Archive and Rights Control

Preserve assets with the access, project and ownership restrictions that continue after wrap.

  • Archive collection and location
  • Confidentiality and image restrictions
  • Ownership, rights and release state
  • Retention and review dates

Reuse, Release and Disposition

Make future use accountable and subject to owner approval.

  • Future project reuse
  • Controlled rental or sales route
  • Donation, recycling or disposal
  • Approval, value and disposition history
Studio, media and production workflow

Configure, Receive, Catalogue, Issue, Reconcile and Preserve

The sequence connects project control, physical custody, creative context, temporary movement and final disposition.

Swipe through the studio-asset workflow
01

Configure the Project

Create units, departments, access, confidentiality and operating ownership.

02

Receive and Identify

Record assets, kits, sets, components, condition, source and custody identity.

03

Catalogue and Store

Capture project context, images, continuity, documents and controlled location.

04

Search, Reserve and Issue

Create department pulls and transfer custody to sets, sites, units and vehicles.

05

Return and Reconcile

Verify assets and kits, record condition, discrepancies and outstanding returns.

06

Wrap, Archive and Reuse

Restore, preserve and release assets only through approved rights and disposition rules.

Confidentiality does not remove operational accountability

Aliases, restricted images and role-based access can protect the project while custody and movement remain traceable.

Wrap is not merely a bulk return

It requires project-wide reconciliation, department sign-off, condition decisions and final ownership or reuse instructions.

Studio-asset responsibility

Keep Rights, Physical Operations and Department Use Explicit

The operating model should show who owns the assets and project decisions, who performs custody work and who may select, issue, use and return inventory.

Responsibility
Studio or Project Owner
Vault Operations
Department or Catalog Itemion Team
Provide project, ownership, rights and confidentiality rules
Responsible
Configure and apply
Follow approved access
Receive, identify, catalogue and store assets
Provide source and creative context
Responsible where scoped
Review department context
Create pulls, approve issue and control temporary use
Approve restricted or exceptional use
Verify and hand over where scoped
Select, receive and return
Record condition, missing assets and discrepancies
Review commercial or rights effect
Inspect and record
Clarify use and return context
Wrap reconciliation and archive decision
Approve final project decisions
Reconcile and report
Complete department sign-off
Future reuse, rental, sale or disposition
Control rights and release
Provide operational readiness
Request approved future use
Swipe through the studio-asset responsibility views
01

Studio or Project Owner

  • Ownership and rights Define
  • Confidentiality Approve
  • Wrap decisions Approve
  • Future release Control
02

Vault Operations

  • Receive and identify Responsible where scoped
  • Catalogue and store Responsible where scoped
  • Issue and return Verify and record
  • Wrap and archive Reconcile and maintain
03

Department or Catalog Itemion Team

  • Creative context Provide
  • Selection and use Responsible
  • Return and discrepancy Clarify
  • Department sign-off Complete
Different studio and project requirements

Configure the Solution Around the Format, Department and Lifecycle

The right controls depend on project duration, confidentiality, department structure, asset type, location count and post-project value.

Swipe through the studio and media use cases
Film and OTT ProjectsUse project, unit, department, character, scene, set, issue, return and wrap controls.
Television and SeriesUse season, episode, continuity, recurring sets, repeated issue and long-running archive structures.
Advertising and Branded ContentUse short schedules, client approvals, campaign kits, rapid movement and final disposition.
Costume and Wardrobe DepartmentsUse characters, looks, duplicates, accessories, fittings, returns and garment care.
Art, Props and Set DecorationUse kits, components, dimensions, scene context, vehicles, installation and condition control.
Multi-Unit and Multi-Site ShootsUse unit permissions, temporary locations, transit, cross-unit transfers and reconciliation.
Closed Project ArchivesUse restricted access, retention rules, rights, provenance and preservation requirements.
Reusable Studio LibrariesUse cross-project search, availability, rental, sales, donation, recycling and reuse reporting.
Studios, Media and Catalog Itemion FAQs

Common Questions before Project Assets Are Onboarded

The final scope depends on project type, departments, confidentiality, asset volume, active locations, issue frequency, wrap requirements and reuse rights.

Request a Studio Asset Assessment

Can a studio use storage without managed project operations?

Yes. Archive and storage models can be used without compulsory catalogue, issue, marketplace or fulfilment services.

Can confidential projects use aliases and restricted images?

Yes. Project aliases, role-based access, restricted metadata, limited images and embargo dates can be configured while preserving custody history.

Can assets be linked to departments, characters, scenes and episodes?

Yes. Project context can include units, departments, characters, scenes, episodes, continuity versions, schedules and locations.

Can kits and sets contain individually controlled assets?

Yes. Kits and sets can remain grouped while their components retain individual identities, conditions and movement records where required.

Can inventory be issued to stages, sets, outdoor sites and vehicles?

Yes. Temporary operational locations can include stages, sets, client sites, outdoor locations, transit vehicles and department-controlled areas.

Who is responsible for an issued asset?

The issue record identifies the approved person or department, destination, date, expected return, condition and handover evidence.

How are missing or damaged assets handled?

Missing, wrong, damaged or incomplete assets move to discrepancy and hold with evidence, an assigned reviewer and a recorded resolution.

What happens during production wrap?

Wrap reconciles expected and returned assets across departments, sites and vendors, records outstanding issues, confirms condition and captures final ownership or archive decisions.

Can archived assets be reused, rented or sold?

Potentially. The studio or rights owner controls whether an asset can be reused internally, rented, sold, donated, recycled or otherwise released.

Does catalogue completion make an asset available outside the project?

No. Cross-project or commercial release requires the applicable ownership, rights, confidentiality, condition and availability approvals.

Begin with the project structure, departments and asset lifecycle

Tell Us How Assets Must Be Received, Issued, Reconciled and Preserved

We will map projects, units, departments, confidentiality, categories, kits, continuity, locations, issue workflows, wrap reconciliation, archive and approved reuse.