MicroStation Telecom Drafting on DGN: Seed Files, Levels, Cells, and Interchange

The first MicroStation file we refuse is usually a seed, not a sheet. Someone copied last year's workset. The master units still read as international feet while the survey arrived in US survey feet. Every cell placed after that inherits a scale lie that only shows up when the DWG lands on a receiver using a different unit from the seed.

This guide is about the DGN object model that has to survive that handoff. Seed files, level libraries, cells and nested references come before sheet cosmetics. Working units and the geographic coordinate system sit in that same contract. OpenComms Designer and OpenUtilities Designer sit around the model as product context, not as a partnership claim. The test is whether a receiver can attach the same seed and round-trip 2 known control points without borrowing the author's configuration.

Seed the DGN before a cell is placed

MicroStation telecom drafting is DGN production of OSP geometry under a locked seed, with named levels, cells, live references, working units and a geographic coordinate system the receiver can prove. Bentley's MicroStation 2026 release announcement names build 26.00.00.178 of 20 March 2026. The owner's seed still controls the package.

Name MicroStation telecom drafting from the seed

A copied workset is not a standard. Bentley's MicroStation 2026 product page, in the section What is new in MicroStation 2026, describes the Configurations Wizard as a guided interface for configurations, workspaces and worksets. That is the one place this guide treats those three layers as a set, because the product itself names them that way. We still start production from the owner's delivered seed, not from whatever last opened on the drafter's machine.

The seed report is the first acceptance artifact. It names master units, sub-units, the GCS and the seed file identity the receiver will stamp. If that report disagrees with the owner's published dgnlib, production does not start. A later plot cannot repair a wrong unit. Our GIS mapping services treat that seed lock as part of the mapping workstream, not as a CAD preference the drafter gets to choose.

I would rather fail a handoff on the seed report than explain a tenth-of-a-foot shift after staking crews have already occupied the corridor and set hubs. The US survey foot and the international foot differ by 2 parts per million. On a 50,000-foot corridor that is 0.1 foot. The plot will not show it. The two control points will.

The CAD/GIS documentation standards guide treats CRS discipline as a deliverable. On a DGN that discipline lives in the Geographic Coordinate System dialog, not in a DWG viewport. Software capability does not choose the owner's system. The seed does.

Release authority is split on purpose. The CAD lead corrects seed metadata. In-house engineering resolves whether the GCS matches the survey basis. When those two answers disagree, we issue a new seed rather than relabeling the old one. The buyer names the system it will stamp on that new seed. A DGN cannot move from exhibit to construction merely because the linework did not change.

Record working units before anyone places a cell

Working units are not a display setting. They are the numeric contract of every coordinate stored in the file, and a later display change does not rewrite what was already stored under that unit. We write master units and sub-units on the seed report, then lock them in the workspace so a later user cannot switch feet to meters inside a live design file. A cell placed under the wrong unit is not a cell we can scale back to truth. It is geometry we replace.

Sheet indexing is a later concern. It does not forgive a seed whose units were wrong when the first cell was placed. We do not open the sheet index until the seed report is accepted.

Put meaning in levels and cells

A cell named SPLICE_EXIST can still carry the proposed line style from a V8i library. The plot looks finished. The native object is a lie. We encode status through the level library and the cell library together, then keep item types on the cell so a grayscale plot and a native interrogation tell the same story. Color is not the contract.

Interrogate the cell, not the legend

Telecom meaning on a DGN is tested by selecting 8 representative cells: proposed, existing, removed and record, plus one each of aerial, underground, splice and cabinet. A reviewer reads level, cell name, item type and annotation. If any of those four disagree, the library is wrong. We stop production on that library rather than annotating around it.

The fiber design software comparison already places MicroStation as the utility DGN path. This guide is the native contract behind that path. AutoCAD layers do not map onto MicroStation levels one for one. A DWG layer named FIBER-AERIAL-PROPOSED may land on a DGN level whose by-level style still says existing. The cell library has to carry the status the level cannot.

One limitation I still catch in our own libraries: V8i cell names that only the original author can decode. Familiarity is not control. We map or retire those names against the owner's receiving standard before production expands. A cell that requires tribal knowledge fails the 8-element test even when every drafter on this floor can recite it.

Quantity extraction follows native cells. A schedule that counts a cell the legend marks existing is an object-standard error, not a sheet error. We repair the cell and republish. Hand-editing the displayed schedule leaves the next issue to reproduce the same lie.

GIS can store the same splice. It does not issue the DGN cell. We keep facility identity in the cell library so a weak DGN cannot be excused by a good geodatabase sitting somewhere else. The GIS mapping outsourcing guide is the other half of that boundary: the geodatabase owns the asset record when the owner needs that function, and the DGN owns the sheet.

Attach references a receiver can detach

A nested DWG that resolved on the author's search path is not a delivered reference. It is a local accident. We attach survey files and GIS extracts as live references. They stay detachable through review. We package only the attachments the receiver's environment can find. Copying nested content into the master makes a tidy archive by erasing the boundary reviewers still need.

Nested is not copied

Bentley's MicroStation product page, under Interoperability, states that a DWG can be brought into a DGN project as a reference. That is the intended path. Flattening the DWG into the master to make the file simpler for the next drafter is how a later survey update has nowhere left to land. We keep the reference live until the issue that depends on it is accepted, then we package the attachment method in the seed report.

The open test is simple. Take the archive to a machine that has never seen the project. Detach each reference. Reattach it from the delivered folder. If a nested DWG asks for a font or a path that exists only on the author's drive, the package is incomplete. We correct the recipe. We do not write a workstation instruction and call that delivery.

Source authority stays on the reference, not on the master. A GIS extract used for context does not become construction position merely because it is visible. A field-verified survey used for staking does not become a planning exhibit merely because someone turned the level off. The reference list names each file, its date and the use it is allowed to support. Promotion into design geometry is a separate, recorded step.

When a survey shifts, we reload the reference and recheck only the sheets that depend on it. Unrelated drafting does not inherit a project-wide hold. The CAD coordinator may approve packaging. The source owner still answers a disputed coordinate. Draftech calculates the drawing impact before the buyer chooses recollection or a local hold.

Hold units through the interchange recipe

Two control points decide whether interchange worked. Not the plot. Not the file extension. We pick points the owner already knows. We export the DGN through RealDWG and measure those same points on the DWG. Then we export the same geometry to the GIS format the owner named and measure them again. If either hop moves, the recipe is wrong.

Test MicroStation telecom drafting through interchange

Bentley's New and Changed in MicroStation 2025 documentation, in the RealDWG 2026 Support section, states that MicroStation 2025 was updated to support RealDWG 2026, including custom objects and object enablers. MicroStation 2026 continues that DWG path. Fidelity of the engine is not fidelity of the unit. A successful export log cannot replace the 2-point measurement.

The product page also lists direct integration with Esri ArcGIS REST services and export of CAD data into an Esri file geodatabase. That is a capability. It is not an acceptance test. We still record the transformation, the GCS and the intended use before anyone treats the GIS file as the design. The fiber as-built GIS documentation standards apply once field changes are accepted. They do not rescue a DGN whose control points already drifted on the way out.

Multi-annotation scale in MicroStation 2026 is a read-only display of AutoCAD annotation that carries more than one scale. Useful when a received DWG is the source. It is not a reason to skip the DGN-side annotation standard. We still write DGN text and dimensions to the owner's annotation scale. Borrowed DWG annotation stays tagged as borrowed.

A clean-environment failure here is often a contract failure. The PDF may be correct while the delivered DGN loses a nested survey or a custom line style that only the original workstation can still resolve. If the agreement requires editable native files, that missing dependency blocks delivery even though no line moved. If the contract requires only an issued PDF, the same local dependency still threatens the next revision. The seed report tells the checker which consequence applies.

Choose MicroStation, OpenComms or OpenUtilities

A work-order GIS and a drawing package are different products that happen to share a CAD engine. Core MicroStation is the drawing engine. OpenComms Designer is the communications work-order suite. OpenUtilities Designer is the utility-network suite for electric, gas, water and wastewater. Picking the wrong one produces a file that plots and still cannot post a work order.

Bentley OpenComms Designer 2023 Help, topic OpenComms Using the DGN Persistence Mode, posted 3 September 2024, states that DGN persistence saves graphical features in DGN files and stores feature properties as XML fragments. A database record is stored for each feature too. That is the mode to keep when the owner already runs OpenComms for fiber or coax. Flattening those features into a dumb DGN to make a prettier sheet is how the next work order loses the feature the sheet still shows.

OpenUtilities Designer, on Bentley's product page, is built on the MicroStation CAD engine for electric, gas, water and wastewater networks. Telecom work-order logic does not belong there. A cooperative that already uses OpenUtilities for distribution can still receive a core MicroStation DGN for the fiber attachment package. The two files share an engine. They do not share a data model.

Draftech completes this drafting in-house. We are not a Bentley partner and we do not sell a certification. We produce the DGN the owner's seed requires, and we test the interchange recipe the owner named before the first production cell is placed in that seed. If full turnkey construction is in scope, Draftech-managed subcontract crews return redlines and field evidence under QA/QC and safety controls. Those observations become design only after the in-house team issues a revision.

For a cooperative that issues DGN: lock the seed and the level library to the owner's dgnlib before production. Reject a copied workset even when last year's cells look familiar. The seed report is the first page of the submittal.

For an overbuilder whose pole owner wants DWG: require the 2-point round-trip on RealDWG 2026 output before acceptance. A DGN that only plots is not the product the pole owner can revise.

For an operator already on OpenComms: keep DGN persistence. Do not flatten work-order features into a drawing-only DGN so a reviewer can ignore the database. The sheet is a view of the feature, not a replacement for it.

For a buyer who only needs plotted PDFs: still name the seed and the GCS, because the next revision will need them. Paying for a PDF today without a receivable DGN is how the second issue costs more than the first.

The acceptance demonstration uses 2 sheets with different references. The receiver opens each native file and reattaches the delivered references from the packaged folder. Then they measure the same 2 control points after a DWG export. Failure shows which package recipe is incomplete. That evidence is more useful than another production screenshot, because it tests whether the owner can revise the work after the original workstation is gone.

The demonstration can run on a real sheet set. Our free design offer for the first 20,000 linear feet of a route delivers native construction drawings and permit drawings through agency approval, and the receiver can open those DGN files in a clean environment before any production contract exists.