CAD Guardian Civil, infrastructure, MicroStation, and DGN package owners
CAD Guardian logo

Public runnable evaluation kit

MicroStation DGN Workflow Quick-Start Kit

Name seed files, levels, cells, references, and export risk before DGN conversion or automation spreads across infrastructure workflows.

Runs public DGN fixture checks, writes a JSON report, and frames the MicroStation SDK, Python, seed, level, cell, reference, and export handoff.

Download ZIP Open GitHub Repo Consulting Page
git clone https://github.com/tsmithcode/cadguardian-microstation-dgn-workflows-proof.git && cd cadguardian-microstation-dgn-workflows-proof
First paid sliceSeed, level, reference, and export readiness
Risk removedLate DGN review failure after conversion or package automation
Best buyerCivil CAD lead managing DGN standards and deliverables

Procurement Fit

CAD Guardian LLC · NAICS 541512 · SIC 7373

Entity

CAD Guardian LLC, Delaware LLC, operates this public evaluation kit and the matching MicroStation consulting path.

Offer fit

Drawing/Document Automation Slice, Quote Automation Prototype, and Implementation Build Slice.

Boundary

Public runnable proof kit available; private customer artifacts, DGN files, credentials, and estimate notes are not exposed.

Direct-Answer Proof

Best for, proof, send-list, next action

Best for

Civil, infrastructure, plant, and facilities CAD teams evaluating DGN seed files, levels, cells, references, and export risk.

Decision this proves

Whether one DGN package class is clear enough for MicroStation-native automation, or should stay in package-readiness checks first.

Proof to review

Public DGN fixture receipts, seed/reference/export checks, native adapter boundaries, and reports/quickstart-report.json.

What to send

The generated report, DGN package class, seed/level/cell/reference/export assumptions, and desired next runtime boundary.

Next action

Run the kit and use the consulting page when the DGN package boundary is ready for private MicroStation review.

Start With the Download

One ZIP, one report, one decision path
  1. 01Download the ZIP or clone the repo from GitHub.
  2. 02Run npm run doctor, npm run verify, then npm run demo.
  3. 03Open reports/quickstart-report.json and compare it with the included docs.
  4. 04Use the native handoff examples only after the package boundary is clear.
npm run doctor && npm run verify && npm run demo

Why Download This Kit

Highest-return use cases first

Download signal

You need a DGN package conversation grounded in seed, level, reference, and export facts.

Download signal

You want to show what can be safely checked outside MicroStation and what must stay native.

Download signal

You need a reviewer-safe proof before any conversion workflow becomes policy.

Best First Funded Slice

Small enough to trust, useful enough to buy

Seed and level audit

Protect the standards users expect before conversion or automation spreads.

Reference and cell boundary

Surface the objects that usually break late in infrastructure review.

Export readiness decision

Make PDF, DWG, and DGN export assumptions explicit before a lead trusts the workflow.

STAR Story

Interview-ready and buyer-safe

Situation: A civil or infrastructure CAD team needs DGN help, but seed files, levels, cells, references, and exports are not clearly governed.

Task: Name package readiness before conversion or automation spreads across DGN workflows.

Action: Bundle public DGN fixtures, validate seed/reference expectations, and show MicroStation DGN vocabulary through Python and .NET-style adapter examples.

Result: A reviewer can run the package check, inspect export risk, and discuss the MicroStation runtime boundary with concrete terms.

Workflow

From request to accepted output
  1. 01DGN package request
  2. 02Seed fixture inventory
  3. 03Level and cell check
  4. 04Reference policy check
  5. 05Export risk check
  6. 06MicroStation runtime boundary
  7. 07Reviewer signoff
  8. 08Next readiness decision

Pareto Checks

The few checks that change the decision

Seed file inventory

Prevents conversion or automation from drifting away from the seed file users expect.

Level, cell, and reference boundary

Names the objects that usually make DGN work fail late in review.

Export package risk

Makes PDF/DWG/DGN export assumptions explicit before a civil CAD lead trusts automation.

Native Signals

Vocabulary for the licensed runtime
  • DgnFile
  • DgnModel
  • ModelRef
  • Element
  • Level
  • Cell
  • Reference attachment
  • Seed file
  • Export package
  • MicroStation Python

Public Fixtures

Reusable, public-safe evidence

Acceptance Standard

What the downloader should be able to prove

Run confidence: The scripts complete on public fixtures and produce an inspectable report.

Business confidence: The first automation slice is narrow, named, and tied to a repeated human review cost.

Runtime confidence: Native CAD work starts only where the proof names a real licensed-runtime boundary.

Safety Boundary

Public repo hygiene

This repo uses approved public fixtures only. It does not include client drawings, private opportunity notes, credentials, tokens, proprietary files, or license-uncertain assets.

The native examples are handoff scaffolds for the licensed CAD environment, not a claim that every runtime behavior can be validated outside the product.