MicroStation FAQs
Below is a list of popular questions and a short answer.
For more information please contact ECS on 1300 762 614
Short answer: Buy through a local Bentley Channel Partner such as Engineering Cad Solutions
for perpetual options or directly on the Bentley eStore using the following link -
MicroStation 12-month subscription.
Why it matters: Procurement routes determine support, pricing and entitlement management.
Next step: Contact an authorised channel partner to request a quote and licensing options.
eStore Ordering Process video.
Short answer: 12-month Subscription named-user licensing ( Aust $3,967 ) and once off perpetual licenses ( Aust $13,660 ) managed via Bentley accounts.
Why it matters: Licensing type affects cost predictability, concurrent use, and cloud entitlements.
Next step: Map your concurrent user needs and ask for a named-user vs perpetual cost comparison.
Talk to an expert.
Short answer: Subscription gives access to latest releases and named licensing; perpetual grants a legacy ownership model with optional maintenance (termed SELECT).
Why it matters: Long-term ROI, upgrade cadence and licensing differ between models.
Next step: Calculate total cost of ownership over 3-5 years for both options.
Short answer: Contractors typically use named-user subscriptions.
Why it matters: Misaligned licensing can block collaboration during delivery.
Next step: Standardise access via subscriptions.
Short answer: Bentley offers support tiers and online videos; resellers add bespoke training and onboarding packages.
Why it matters: Proper onboarding reduces delivery risk and accelerates standards adoption.
Next step: Bundle pragmatic training (workspaces, CADconform, publishing to iModel) into the purchase.
Talk to an expert.
Short answer: Key productivity tools are AccuDraw, AccuSnap, Key-in commands, and custom toolboxes/workspaces.
Why it matters: Using these tools consistently reduces drafting time and error rates.
Next step: Create standard toolboxes and short macros for recurring drafting tasks.
Short answer: Use DGNLib, Workspaces, CADconform feature tables and seed files to enforce levels, symbology and annotation scales.
Why it matters: Standards enforcement ensures compliance and reduces rework at handover.
Next step: Build a DGNLib with templates and validate deliverables using CADconform checks.
Request a Demo
Short answer: Use annotation scales, named views, title block templates and automated sheet production scripts for consistency.
Why it matters: Consistent annotation avoids downstream misinterpretation and accelerates approvals.
Next step: Standardise title blocks and author a sheet production script for plan/profile outputs.
Request a Demo
Short answer: Use the native DWG import with mapping tables, purge and clean-up scripts, and verify units/georeference after import.
Why it matters: Clean migration preserves geometry, layers and attribute data critical for digital twins.
Next step: Run test imports, build mapping tables, and document the conversion process.
Short answer: Seed models, level templates, chained elements and DGN referencing (DgnAttach) reduces rework by standardising repeated geometry.
Why it matters: Linear projects benefit from repeatable library elements and reference-driven updates.
Next step: Build corridor seed files and reference libraries for common corridor elements.
Short answer: 3D AccuDraw, Item Types (metadata), Solids modeling, and the OpenRoads/OpenBuildings toolsets accelerate precise 3D work.
Why it matters: Efficient 3D tools reduce modeling time and improve digital twin fidelity.
Next step: Enable and configure OpenRoads/OpenBuildings modules for corridor and building modeling.
Short answer: Use Item Types, properties, and attribute mapping to attach lifecycle metadata to elements.
Why it matters: Metadata is the bridge between design geometry and operational asset registers.
Next step: Define a minimal item type schema aligned to ISO 19650 (international standard for BIM) and your asset register fields.
Request a demo.
Short answer: Use iTwin Capture or native point cloud tools, create lightweight references and register point cloud subsets to reduce model bloating.
Why it matters: Reality capture improves accuracy but can overwhelm file size and performance if unmanaged.
Next step: Adopt clipping, tiling and level of detail (LOD) rules for point cloud consumption.
Talk to an expert.
Short answer: Use spatial query tools, model comparison, and federate models to iModel for cross-discipline clash analysis.
Why it matters: Early clash detection prevents costly site changes and supports handover readiness.
Next step: Set up rule-based checks and schedule periodic federation for integrated clash runs.
Short answer: Publish federated iModels with embedded metadata, create asset schedules and deliver indexed, searchable models.
Why it matters: Handover-ready models minimise data transformations and speed operational use.
Next step: Define handover templates and export processes to produce iModels and IFC with required metadata.
Short answer: MicroStation publishes iModels and natively connects to ProjectWise for version control and collaborative editing.
Why it matters: Integration enables federated models, change tracking and secure collaboration across stakeholders.
Next step: Setup model publishing to iTwin and configure ProjectWise access controls.
Short answer: Use references (DgnAttach), standard seed files, shared DGNLibs and a central ProjectWise repository with named worksets.
Why it matters: Structured collaboration reduces clashes and ensures everyone works to the same standards.
Next step: Establish a collaboration charter, naming conventions and reference management rules.
Request a demo.
Short answer: Export to iModel, PDF plan sets, IFC or publish 3D web views using iTwin for accessible stakeholder review.
Why it matters: Non-CAD stakeholders need usable views to support approvals, procurement and community engagement.
Next step: Create a publishing checklist that includes format, metadata, and viewer permissions.
Short answer: Define data standards, item types, quality assurance (QA) gates, naming conventions and a publication schedule governed by a BIM or data steward.
Why it matters: Governance preserves model integrity and ensures lifecycle usability.
Next step: Appoint a data steward and doccument the governance process in a short handbook.
Read the Article.
Short answer: Track metrics such as time to handover, number of rework issues, metadata completeness, and stakeholder satisfaction.
Why it matters: Quantitative KPIs prove ROI and highlight where to improve workflows.
Next step: Define baseline metrics and set quarterly targets for improvement.