Skip to content
  1. Services
  2. Digital Content
  3. Digital Assets Service

Digital Assets Service

Marafei creates or adapts visual and 3D assets for an agreed experience, interface or display. Digital asset production can cover models, textures and scene elements, with the scope, delivery formats and acceptance checks defined around the application that will receive them.

Build a new asset or adapt an existing file?

You may need a product model for a web viewer, a component for a training application or an object for a museum display. Start with what the user needs to see or do, then specify the files your team needs to operate and update it.

Review what you already have. An approved design file may provide a starting point for modelling or conversion, but test a sample before committing a batch. If the task needs only one fixed view, a photograph or illustration may be sufficient.

Starting material Review before pricing What a sample should establish
Photographs and visual references Available angles, dimensions and approved materials Expected shape and gaps in the references
CAD or an existing model File version, permissions, units and sensitive geometry What can be converted, simplified or rebuilt
A physical object or architectural feature Access, capture permission and documentation limits Suitable capture method and detail to preserve
Artwork or a 2D element Resolution, dimensions and display position Legibility at its intended viewing size

Include physical capture in the scope if the project needs it. Choose a sample that represents the difficult work, such as a reflective finish or a part with a controlled dimension, before approving the remaining assets.

Assets for products, training and visitor experiences

Product models and finish options

A commission can specify a product model with approved materials and finish variants. The product team reviews its appearance; the application team checks the export in the intended viewer. Agree the reference lighting and comparison method so that reviewers can interpret differences in appearance.

Components for training

A training application may need a part that users can rotate, separate or identify by label. Specify the dimensions that matter, the information a subject expert must approve and any required motion. Instructional procedures and assessment logic belong in the scope of the complete training experience.

Objects for museum interpretation

An asset can give visitors a view of a feature that is difficult to inspect on the displayed object. Use an authorised reference and an approved description. Review object identity, significant details and labels, and provide another way to access the information for visitors who cannot use the interactive view.

Scene elements for VR and AR

Prepare scene objects against the receiving application's requirements. For a virtual world or metaverse environment, name the platform, version and constraints. A finished VR or AR experience, an audience-facing video and a physical 3D print require their respective production scopes. An asset handover should identify the reusable files it supplies.

Specify delivery for each destination

glTF supports transmission and loading of 3D models and scenes; GLB can package the data in a binary file. Check that the receiving viewer supports the features used by the asset. Khronos glTF reference

OpenUSD supports asset interchange and composition of scenes from multiple elements. Consider it where the production tools support the workflow and its referenced components. Introduction to OpenUSD

Destination Specify before production Sample check
Web viewer Viewer version, browser, device, export and permitted extensions Model opening, textures and loading time
VR or AR application Engine version, device, units, axes and pivot Placement, movement, appearance and performance
Scene production tools Applications, versions, formats and referenced files Resolve dependencies and assemble the scene
Display installation Playback tool, viewing distance and required resolution Read important details and labels from the audience position

Set file size, geometry and texture budgets after testing the intended view and device. Preserve the features needed for the task; internal geometry may be unnecessary if it will never be shown. Inspect the asset in the actual destination. Check which properties survive import; the format name cannot settle that question.

An approved master and reusable variants

Give the master a clear name and revision, and record which exports derive from it. Test whether one version works across the requested destinations before commissioning separate variants.

A product model might need a lighter web export and more detailed textures for a close view. Identify the dimensions, silhouette, finish and visible details that must survive simplification. Record each version's file size and loading result on the agreed device. Reuse in another channel also depends on its rights and may need additional preparation.

References, localization and permissions

Provide approved images or design files, dimensions where needed, and material or brand references. Assign responsibility for appearance and technical accuracy. A marketing reviewer may approve the finish while an engineer checks a controlled dimension or sensitive component.

Approve Arabic and English terminology, units and labels. Decide whether labels are part of the asset or an editable layer in the interface, then check them at the intended viewing size. Identify information that must be omitted from shared exports.

Request a rights record for models, textures, fonts and other supplied elements. The agreement should identify permitted use, adaptation, redistribution and source delivery, including components that need a separate licence. Permission to share a reference with a production team does not automatically establish permission to publish it.

External example: documentation assets used in a visitor app

Scottish Ten and Climate Change Explorer

Historic Environment Scotland describes reusing models created for Scottish Ten in Climate Change Explorer, an app presenting climate impacts at five Edinburgh landmarks. This documents a public interpretation use for recorded assets; it does not provide a measured improvement in visitor understanding. The institution's app description

A Saudi visitor centre could pilot one approved architectural feature, retaining a reference model for specialists and preparing a lighter display version with approved Arabic annotations. A specialist would compare a selected detail across both versions, while the operator checks loading on the intended display. These are proposed local acceptance checks; the external project belongs to the named institution.

Digital asset production cost and comparable quotes

Marafei prices the work to the agreed project scope. Give suppliers the same asset list, delivery versions, rights requirements and acceptance tests. Request a sample price and a separate estimate for the remaining batch.

Quote item Clarify what is included
References or capture Available inputs and additional documentation needed
Modelling and materials Asset count, complexity and required detail
Optional animation Clips, behaviour and model preparation
Platform variants Exports, conversion and tests for each destination
Rights and editable source Licences, source files and dependencies
Review and handover Revision rounds, acceptance roles and support scope

Compare the deliverables before comparing totals. A runtime export has a different handover scope from an editable source with export instructions. Missing references and delayed approvals affect the work plan; agree a delivery date after reviewing these inputs.

Discuss your digital asset production project with Marafei using an initial asset list, target applications and approved reference material.

From representative sample to production batch

  1. Approve the asset specification: purpose, reference, scale, appearance and destination.
  2. Select a representative difficult item and produce the sample needed to test the requirements.
  3. Import it into the buyer's application and record findings and acceptance limits.
  4. Agree the revised specification before producing the batch.
  5. Review exceptions. A different asset type or an upstream reference change may require another sample.

Agree which properties are checked on every asset and which can be reviewed by sampling the batch. Record the approver and accepted deviations against the revision so the team can identify the current file.

Accept the asset in the receiving application

Open the package in a test project separate from the artist's working files. Check the inventory, then compare scale, orientation, pivot, materials and required animation with the approved reference. Place or rotate the asset as the application will use it.

Khronos provides a validator for glTF and GLB files. Treat format validation and the application's visual and performance checks as separate acceptance steps. glTF Validator

If editable source is included, change an agreed property, such as a product material, and re-export the asset. Open the result and record the tool version, device, settings and outcome. Review an alternative means of communicating the information for users who cannot rotate the model or read its labels.

Handover and future changes

Request a manifest covering exports, textures, dependencies, previews and any agreed editable sources. Import notes should identify the software versions and explain how to reproduce the export. Include the rights record and approved revision.

Assign responsibility for storing the master and updating derivatives when the product or material changes. Retest the affected destinations before replacing files in use. Review rounds, support and change requests should be defined in the proposal for the agreed files and applications.

Prepare your asset specification with Marafei

Send an approved example and an initial list. For each asset or similar group, identify:

  • Its purpose and what the user needs to see or do.
  • Approved references, dimensions, materials and labels.
  • Receiving application, version, device and required format if known.
  • Animation, variants and editable-source requirements.
  • Usage rights and limits on sharing references or files.
  • Intended use date and the people who approve appearance, technical accuracy and delivery.

Use the specification to agree what will be produced, delivered and tested. Agree the sample and its acceptance criteria within scope before approving the batch.

Frequently asked questions

Introductory answers that help define the scope before discovery.

What does digital asset production include?

It can include creating or adapting visual and 3D assets for an agreed use. Specify assets, variants, deliverable formats, tests and rights in the proposal.

What should I include in a digital asset production brief?

List the asset, purpose, references and rights, target application and version, date and editable-source needs. Name the person who accepts the result.

Can a CAD model become a digital asset for web or immersive display?

Review the controlled revision and sensitive detail, then test a sample. Agree what can be simplified and which dimensions must remain faithful.

When should we consider 3D capture for a digital asset?

Consider capture when an approved physical object or site is the reference. Check access, rights and the details to preserve, then compare capture with modelling from references.

How do an asset’s editable source and runtime export differ?

The source supports agreed edits in the authoring workflow. A runtime export is prepared for a target application. List each required file and its supported software version.

When is GLB suitable for delivering a digital asset?

Use it when the receiving app supports the required glTF features. Test import, textures, material appearance, movement and file size on the agreed setup. glTF [1]

When should we request USD for digital asset delivery?

Consider it for a compatible scene composition or interchange workflow. Test the layers, references and target tools on a representative sample. OpenUSD [2]

Does format validation prove a digital asset is ready to use?

Validation checks conformance. Open the asset in the receiving application to check appearance, scale, animation and performance. glTF Validator [3]

Can we share one asset across web, AR and VR?

Start with a controlled master. Test each destination and define channel variants only where its performance, features or layout need them.

How should we choose a digital asset’s level of detail?

Agree viewing distance, device, important features and a performance target. Test a sample and simplify details that do not serve the task.

Does a digital asset include animation?

Specify it in scope if needed. Agree motions, clip names, duration and looping, then check them in the destination application.

How are Arabic and English labels handled in digital assets?

Approve the terminology and units, then decide whether text is part of the asset or an editable interface layer. Review legibility in the target application.

Who can edit, publish or reuse a delivered asset?

Ask for a rights record covering the master, export and third-party elements. Confirm who can adapt, share or publish each asset under the agreement.

How can I verify that an asset is editable?

Open the named source in the agreed tool version, modify an approved property, re-export and check the result in the receiving application.

How do we estimate digital asset production costs?

Itemise reference preparation, complexity, materials, optional motion, variants, review rounds, rights and testing. Ask for a pilot and a separate batch estimate.

How do we approve a digital asset sample before a batch?

Choose a representative difficult item and test it against the asset specification. Record acceptable deviations and get approval before scaling.

What belongs in a digital asset handover manifest?

List the master or source where scoped, each export, textures, dependencies, file versions, permissions and import notes. Record tested destinations.

Who manages digital asset updates after handover?

Name the owner of the master and the person who approves derivatives. Agree which destinations are retested after a change and how releases are tracked.

How do I choose between an asset service and a content service?

Commission an asset when the deliverable is a reusable file for an existing project or platform. Scope finished audience-facing material separately.

How do we compare digital asset production suppliers?

Give each supplier the same asset list, target platforms, rights and tests. Compare the sample, included source files, review rounds and update terms.

Sources and references

  1. Khronos Group: glTF

    Khronos Group

    Accessed:

  2. OpenUSD: Introduction to USD

    OpenUSD

    Accessed:

  3. Khronos Group: glTF Validator

    Khronos Group

    Accessed:

  4. Historic Environment Scotland: Climate Change Explorer

    Historic Environment Scotland

    Accessed:

Publisher

Marafei

Publisher: Marafei

This service content was prepared, written and reviewed by Marafei’s team of specialists, consultants and technical engineers.

Marafei team

Don’t hesitate to
contact us.

You can book a demo with us by filling out this information, and we will get in touch with you as soon as possible

Business Hours

Sunday–Thursday
8:00 AM–6:00 PM