Why DUC Exists

Engineering projects do not move from design to delivery in a single pass.

Drawings and models are developed, reviewed, changed, and reviewed again. Each cycle creates new information around the design: references, annotations, external files, revisions, relationships, and application state.

The main design files usually survive. The structure connecting everything around them often does not.

The recurring engineering cycle

Different tools may be used at each stage.

A CAD or BIM application may create the design. Another application may prepare the review. Feedback may arrive through annotations, documents, or imported files. The next revision may then return to the original authoring tool.

Without a shared document model, the technical workspace has to be reconstructed at every transition.

Where DUC fits

DUC provides a persistent document layer beneath this cycle.

Applications can read from and write to the same structured document as the project moves through development, review, change, and delivery.

A .duc document can preserve the wider workspace around the design, including:

• Native drawing entities;
• External models, documents, and media;
• Revisions of external files;
• Annotations and metadata;
• Relationships between elements;
• Views and document organization;
• Extensible application state.

This information becomes part of the document instead of remaining trapped inside one application or scattered across unrelated files.

More than a folder of files

A folder can contain every asset used by a project without representing how those assets relate to each other.

It does not inherently describe which revision is being used, which annotation belongs to which element, how objects are arranged, or which views are meaningful.

DUC makes this structure explicit.

The document represents not only the assets, but also the technical workspace built around them.

A foundation, not a replacement

DUC does not replace specialized formats such as STEP, IFC, DXF, PDF, or other engineering file types.

It also does not replace the tools used to create, review, or deliver technical work.

Those assets and tools continue to serve their existing purposes. DUC provides the document structure that allows them to participate in the same workspace.

The applications may change throughout the project. The underlying technical context does not need to be discarded and rebuilt each time.

The underlying idea

Engineering work is more than its final drawing or model.

The references, external assets, relationships, revisions, and document state surrounding that design are also part of the technical artifact.

DUC exists to give that wider technical workspace a structured and portable form.