What is the current KDOT workspace published in KART?

Any project with a NTP after Oct. 1, 2021, should be using a KDOT CONNECT Workspace in conjunction with a KDOT approved Bentley CONNECT edition platform application. Please review the information regarding our supported software resources on our public web page: KDOT CADD Support Design Software (ksdot.org).  

Will this require a full workspace switch on current projects, or just a configuration file switch? If it is to be required for all current and future projects, a full workspace update would be a large change.

The intent is all workspaces being used on active projects will remain essentially as they are. We will need to publish minimal updates to those workspaces, as necessary, that would allow newer products to run on the older workspace resources, but aside from those small adjustments, the existing project workspaces will remain the same. Once our completely reworked Sunflower workspace is released, it will only apply to any new projects that are started after its release. There is no expectation for project workspace migration as there are significant changes at a fundamental level between the two workspaces that would prevent any easy migration of project data. It is not our intent to have an adverse impact on the schedule or budget of existing projects, but rather to enable the use of newer enhancements and increased stability, while minimizing security / compatibility concerns that stem from the use of older software versions.

Once a project has started, can the consultant continue upgrading the version of the civil design software? For example, if a project begins using the KDOT CONNECT 10.10 workspace, can the design team switch to newer OpenX versions mid-project? Additionally, when the December 10th policy implementation date arrives, do active projects need to migrate to a newer workspace or recreate their ProjectWise environment in order to comply with the required OpenX 2023 product version?

Under the KDOT CADD Software Use Policy 2025, all active KDOT projects using any CONNECT Edition workspace must use one single KDOT-approved OpenX product version, regardless of the workspace assigned to the project. At the initial policy rollout, this version is OpenX 2023. This requirement applies even if the project originally began using OpenX 10.10 products.

The policy does not require consultants to upgrade or migrate an existing project’s workspace. Projects must remain locked to the workspace version assigned in their project’s software environment unless designated by KDOT. Instead, only the application version used on the workspace (OpenX 2023, and later KDOT-approved versions) changes.

Because newer OpenX products are designed to operate on older OpenX schema workspaces, upgrading the application version is allowed and expected, and no workspace uplift or data migration is required. On December 10th, consultants and KDOT staff will begin opening existing project files using OpenX 2023, which will uplift files automatically as they are opened—consistent with Bentley’s recommended best-practice. Each uplift creates a .bak backup file, allowing rollback if needed.

For projects currently using the KDOT CONNECT 10.10.02 workspace, compliance simply requires updating to 10.10.03 once it is implemented in the consultant’s environment. This minor update includes mostly the specific updates necessary for OpenX 2023 software use (e.g., Civil Labeler DGNLIB, OpenBridge 2023 resources). The overall workspace structure remains unchanged, and no new ProjectWise workspace needs to be created.

Some consultants have had file corruption issues when upgrading to newer versions - it happens to only some of the files but is still concerning when applied to an entire project.

We’ve had conversations with Bentley at length regarding best-practice with uplifts, and they have stated on multiple occasions that project datasets do not need to be explicitly uplifted via Civil File Manager. They went so far as to say (despite my conflicting recollection) that Civil File Manager only existed to facilitate v8i to CONNECT file conversions, and that modern CONNECT Edition products should never need to explicitly use it to uplift files. As you open files they should be uplifted as they are opened with the new version for the first time. We also have regular interaction with peer DOT’s via IHEEP that have had similar ad-hoc uplift policies for quite some time now that have not experienced notable issues. Not to say that there won’t be any issues, but we can say that this updated Design Software Use policy is in-line with what Bentley is putting forward as their best practice from a civil file management perspective, and that we’re not the first DOT to walk that path. It’s also worth noting that any uplift of a file will produce a backup of the file with a .bak extension. These may end up in user’s local ProjectWise cache directory, but if issues are encountered then this does provide a path for consultants to roll the version of the file back and mitigate any data loss while the issue is investigated.

How often will versions be analyzed for approval? For example, how soon would consultants be expecting the OpenX2024 versions to be KDOT approved? Could the initial approved version be 2024?

As stated above, our intent is to stay within the last two major yearly versions published by Bentley (e.g. 2023, 2024). If we’re not on the current yearly release (e.g. 2024) then we should be on the prior yearly release (e.g. 2023). I didn’t want to prevent our ability to be flexible in our adoption of updated releases moving forward so didn’t state specific requirements in the policy but generally speaking we will be targeting adoption of the first update to the initial major yearly version release (e.g. 2023.1, 2024.1). Typically, this first update release resolves most of the issues introduced in the initial major yearly version release. The hope is that if we are not supporting an ever-growing number of product and workspace versions that it will allow us to be more responsive on new version adoption. Uncoupling the workspace updates from the approval of new OpenX product versions should also help us stay true to this goal.

What version of MicroStation Connect is KDOT currently using?

The list of our supported software versions can be found on our external website (KDOT CADD Support Design Software (ksdot.org)

Does/will KDOT provide a ZIP with the Workspace files to KART alongside the Installer?

In the currently published installer, there is an option "Configure for Custom Extraction" for those familiar with configuring workspaces and just want to access the files to update a custom configuration.

Why is the Workspace zip file empty after unzipping?

We've heard some organizations have security policy on their deployed ZIP solutions that may prevent the ZIP contents from displaying. if you right-click on the ZIP file and open with Windows Explorer you shouldn't have any issues accessing underlying content. Additionally, some organizations have also run into issues running the executable. If this is the case, we recommend right-clicking on the installation and selecting Properties. At the bottom of the General tab, you should see a Security section that normally isn't there. Selecting Unblock should allow the installer to run. 

We would like to implement the KDOT Workspace on our internal ProjectWise hosted by Bentley. Do you provide any guidance?

Typically, we are limited on the amount of support we are able to provide to consultants converting our delivered local workspace installation into server / ProjectWise implementations. if you are running into specific issues, please reach out to kdot.cadd.support@ks.gov and we will assist as best we can.

What is the current KDOT workspace published in KART?

Any project with a NTP after Oct. 1, 2021 should be using the KDOT CONNECT 10.10 Workspace in conjunction with a KDOT approved CONNECT Edition Bentley platform application. Please review the most recent Design Software Use Policy linked on KDOT CADD Support Design Software (ksdot.org)

What version of Bentley Design software is KDOT currently using?

The list of our supported software versions can be found on our website (KDOT CADD Support Design Software (ksdot.org)

Will KDOT revise any documents to account for the change from v8i to CONNECT and possible new methods for using it?

We've shifted a lot toward videos to cut down on documentation overhead. Currently, the KDOT Graphic Standards Manual will have update memos to supplement the guidance. A full rewrite is planned as a larger effort moving forward. KDOT workspace resources in conjunction with CADconform serves as digital Graphics Standards.

Are additional Text favorites being developed?

Text favorites to support the annotation groups, etc. are being developed and refined. If there are more direct text favorite needs tied to manual labeling, etc. please reach out to kdot.cadd.support@ks.gov and let us know and we will add them as needs are identified (and relayed to us). 

Is OpenBridge Modeler a requirement for Bridge Design/Replacement projects?

As noted in the initial Design Software Use Policy guidance, bridges are not required to be 3D modeled in OpenBridge Modeler; however, the latest KDOT approved OpenX version of the software must be used on all projects effective with the updated Design Software Use Policy. 3D Modeling resources continue to be updated to support 3D modeling workflows using OpenBridge.

Does the KDOT workspace come with a default layout for creating a title sheet for a project?

The most common layout used for projects is KDOT Title w Seal and can be found in the workspace folder:  \KDOT_XX.XX\Standards\dgn

I cannot find some of the items previously included in the workspace like the Docs and ControlCAD. Were they removed?

These items are located in this relative location: C:\ProgramData\KDOT CONNECT Workspace 10.10\Docs"

I have noticed a discrepancy between the Templates provided and the Standard Drawings. Which is correct?

Any discrepancies should be resolved. In the event of a found discrepancy , the KDOT Standard Drawing should be used.  Please reach out to kdot.cadd.support@ks.gov with any discrepancies you find.

This project is in PowerGEOPAK using the NS Workspace but the Standard Drawing shows Connect Edition.

Regardless of the project’s designation as a V8i or CONNECT Edition project, Bentley’s CONNECT Edition software and KDOT’s CONNECT Edition workspace should be used to CADconform these converted standards if modifications are necessary. Submittals to KDOT which include files authored in more than workspace should be compiled into a submittal for each. This means that projects with v8i and CONNECT would have a minimum of two submittals.

Should we start the project in OpenRoads Designer CONNECT Edition?

Yes. Any projects with NTP date after 10-01-2021 should be completed in the latest KDOT approved CONNECT Edition software version. The Design Software Use Policy and other workspace information can be found on our public website here: KDOT CADD Support Home (ksdot.org)

Where are KDOT Standard Drawings hosted for download?

http://kart.ksdot.gov

My project has an NTP prior to Oct, 1st, 2021 so it is being done in PowerGEOPAK with the NS Workspace; not OpenRoads Designer (ORD).  Do you have procedures to utilize these revised standards in the NS Workspace without voiding the CADconform certification?

Regardless of the project’s designation as a v8i or CONNECT Edition project, KDOT-approved Bentley’s CONNECT Edition software version and KDOT’s CONNECT Edition workspace must be used to conform the standards that require modification. Therefore, we are delivering all CONNECT Edition standard drawings in a pre-certified state, so that if no modifications are necessary, the standards should not need to be re-conformed, as typical sheet titleblock information (e.g. project number, year, sheet numbers) can be added via the tag sets in the file without causing invalidation of the CADconform certification. NOTE: Project Submittals which have both v8i and CONNECT content should be delivered in two submittals (one for v8i and one for CONNECT).

We are having issues getting downloaded standards in the correct font. Is this an issue your group has heard of before or can provide support for?

The published PDF’s of the standard drawings should always render/display the fonts correctly in modern PDF viewers; however, working with the DGN files in a CAD environment will require our KDOT font resources to be loaded in order to display and produce PDF’s properly. If the consultant is pulling the standard drawing DGN files directly into MicroStation or AutoCAD. It would be necessary for them to either include the KDOT TrueType Font in their workspace configuration or simply install the font locally to the machine in order for it to render properly. These font resources are delivered in the current release of our downloadable KDOT Workspace installer, which will install the KDOT TrueType fonts locally on the machine in addition to supporting extraction of the workspace resources without the need to have a product installed.

RCB Requests- Will these be ready to consume in ORD?

On 08/29/25, a new web-based RCB Request App became available and is available via https://kart.ksdot.gov/ for submitting and managing reinforced concrete box (RCB) and rigid frame box (RFB) structure requests. The new system streamlines workflows with automated CAD detail generation, approval routing, improved cost estimation, and support for legacy .rce file import.

Is KDOT going to use SUDA for drainage calculations? (Using 3D areas and structures)?

SUDA resources are available for 85% of commonly used items. The calcs won't be able to be done in SUDA due to the drainage manual reliance on custom formulas but prototypes can be updated with properly calculated values. NOTE: We are actively working with Bentley to see if these can be used in the software.

Regarding the process of how geology will be implemented into the model and cross sections. Will KDOT be providing us a surface of the geology that we will implement into the model and cross sections? If not, how will this work?

Geology workflow is a work-in progress. A 3D geology workflow developed for v8i products has been updated for CONNECT Edition products. The upcoming KDOT 10.10.03 version of the workspace will include resources for a 3D Geology Annotation Corridor along with workflow guidance for Geology and Road Design which can be found on our website KDOT CADD Support Home (ksdot.org) under the Workspace Documentation section.

What is the current standard for Survey Code?

Connect Edition will use the Alpha Code Sheet, V8i will still use the Numeric Code sheet. Both are available in KART

Things are displaying differently in the CONNECT workspace than they did in the Legacy v8i workspace (Plan/Profile/Cross Section Annotations), is this the new preference?

This is not a new preference. With each workspace release, KDOT is updating these out-of-the-box settings to align with KDOT standards. Project Managers are aware that some things may not appear as they did previously.  Project Managers and Consultants should reach out to kdot.cadd.support@ks.gov if needed to address concerns.

Are 4-Sided Callout Notes being used now? 

Yes. There is not a memo about this yet, however, the Bureau of Road design sent an email stating "4-sided is the way we want to go and our intentions."

Named Boundary: Will there be a Drawing Seed for the Plan Sheet with General Notes developed?

A new Standard Drawing (RD040) General Note Sheet has been developed. This new drawing contains a repository of general notes off to the side for your reference. Add items from the list to the sheet as appropriate for your project.

If we chose to migrate an existing project to the OpenX software, does KDOT expect the appearance of the already developed plan sheets to migrate 100% to the KDOT Connect workspace or will there be a grace period where the appearance can be a mix of the old/new standards?

The expectation is everything produced by a consultant to be to CONNECT edition standards. Any sheets produced off of the actual design should be redone anyway by virtue of the design method and subsequent dynamic sheeting workflow changing completely. Any non-delivered consultant-produced static sheets being brought forward are fairly easy to update via refmerge into a CONNECT Edition workspace seed and CADconformed to the new standard. We’ve been through this process internally and while the amount of effort can vary according to the sheet content and technician’s skill level, it does go fairly quickly. I would not consider this an undue burden to a conversion process.

With OpenRoads Designer, what is the workflow for creating these cross-section extension sheets and getting them to line up with the main sheets?

Our testing seems to indicate that it’s likely just the difference in height between the mainline named boundaries and the extension named boundaries due to less height difference in the intersecting corridor geometry. The named boundaries can be manually extended in height to match the adjacent named boundaries using basic MicroStation element manipulation tools so that the extension sheets will line up.

Profile Sheet Grid is only plotting what matches the Named Boundary. Should this be full sheet like old?

No, however, in OpenX 2023, Bentley added a new option "Full Last Boundary" to Create Named Boundaries that mandates the placement of a full profile boundary for the last sheet.

Are there any KDOT resources for Interplot Organizer, so we may set it up and use it as KDOT intends it to be used?

Yes, we deliver all of the necessary Iplot resources in both our legacy V8i NS workspace and CONNECT Edition workspace installers. Our KDOT Graphics Standards Manual provides guidance in the appendix (Section 8.4) detailing the installation, configuration and use of ProjectWise InterPlot Organizer in conjunction with the KDOT workspace.

NOTE: Bentley will be discontinuing support for ProjectWise InterPlot products July 31, 2026, except for ProjectWise InterPlot Organizer, which will be discontinued on December 31, 2028. KDOT will be working to develop another solution prior to deprecation.

Upon adding the standard drawing to the Print Organizer, and printing PDFs, there are underlines showing up in the titleblock text. How can I resolve this?

What you’re seeing in the PDF prints are the underscores of the Enter Datafield Regions in the standard sheet border cell. Check the Display attributes and make sure Data fields are disabled. If this doesn't resolve the issue it may be our delivered design script (KDOT.pen) is not loading correctly in your workspace configuration. We don’t provide much in the way of Print Organizer support since we’re heavily invested in Interplot Organizer (Iplot) and deliver all of the necessary plotting resources in both our legacy V8i NS workspace and CONNECT Edition workspace installers. Print Organizer does honor IPLOT Design Scripts for the most part, so you’ll want to reach out to your IT/CAD support contact(s) to ensure that the KDOT.pen is loading correctly in your KDOT workspace configuration.

Why are the results different when plotting from two different machines?

Check Projectwise Interplot Configure and make sure the Engine is set for the program you are using to plot (IE OpenRoads, PowerGEOPAK)

Is there a video or process explained for plotting in Open Road Designer using the Plot Set Organizer?

We don’t provide much in the way of Print Organizer support since we’re heavily invested in InterPlot Organizer (Iplot) and deliver all the necessary plotting resources in both our legacy V8i NS workspace and CONNECT Edition workspace installers.

This is directly related to how we have historically used it to create, modify, and save plot sets and how we are currently using Iplot to drive our renditioning process.

Print Organizer does honor IPLOT Design Scripts for the most part, so MicroStation print should be able to read iplot design scripts.

Please reach out to your IT/CAD support contact(s) to ensure that the KDOT.pen is loading correctly in your KDOT workspace configuration.

Is KDOT developing new labeling tools or cells for CADconform? Using CADconform with CONNECT?

CADconform will be used in CONNECT and features have been updated to support annotative workflows and resources in the CONNECT Edition workspace. Any calls to D&C Manager now automatically call the feature definition and civil geometry tools.

Can you provide guidance on File DSN error and/or Disciple not available errors in CADconform?

We have noticed some issues internally after removing the redundant “KDOT” from the CADconform Discipline name. These seemed to resolve themselves when using the latest version of CADconform, combined with a removal of the CADconform cache directory (%appdata%\Altiva Software), and following the CADconform branding guidance provided in the workspace Docs folder (CADconform Update Guidance for CONNECT Workspace.pdf). With a default local install of the latest CADconform, and our workspace locally installed, it seems to find the discipline without issue.

We know the users are locked to the new Discipline name, so if you haven’t updated your cadconform.pwl then you will need to do that. You may also need to remove the old discipline folder from your CADconform directory. Folders in that location show up as disciplines in CADconform dynamically strictly by their presence.

I have downloaded the current workspace from KART and am getting multiple CADconform errors. 

Check to make sure you have the current version of CADconform from Altivasoft.com. Delete the CADconform cache (%appdata% in File explorer and delete the Altiva Software Folder).

How does CADconform work with side-by-side installations? Can V8i & Connect use the same version of CADconform?

Published KDOT workspaces include a few PDF’s that may be helpful. Both can be accessed prior to the installation of the new workspace as they are bundled with the install in the downloaded .zip file.

Specifically, steps 10 and 11 in the updated Deployment Guide, and the supplemental PDF document “Using CADconform v8.1+ with KDOT_NS_Workspace”. You can download the latest KDOT workspace from KART.

I continue to get a CADconform flag stating the cell differs from the library definition. How do I resolve this?

A removal of the CADconform cache directory (%appdata%\Altiva Software) will typically resolve this issue. If the cell has data fields that are editable, be sure that you are utilizing Fill-In Data Region tool instead of double clicking to fill out enter data regions.

We can get CADconform to work in the local workspace but cannot get it to work inside ProjectWise.

Our typical delivered setup relies on your CADconform application to be loaded by other configuration – either your company or the cadconform.cfg in the appl directory on a local install. We only redirect the resources to the workspace location. You may have to modify KDOT CADconform64.cfg to support an external CADconform resource location if your workspace is in ProjectWise. Please reach out to kdot.cadd.support@ks.gov if you need further assistance.

We have been accepted for a KDOT job recently, and within the RFP under project management section, it states "Provide electronic plan files compliant with KDOT Graphic Standards Manual, including CAD conformance checks and ControlCAD indexed DGN files with ProjectWise attributes". Is ControlCAD just like our CADconform or is this something separate that we need to obtain?

ControlCAD is a suite of products (including CADconform), and the two products you may not be familiar with are Indexer and Submittal. Indexer and Submittal can be generally found in the local workspace (varies depending on the product installed) here: C:\ProgramData\KDOT Workspace XX.XX\ControlCAD

Indexer is used to gather the relevant metadata on each file to populate our ProjectWise attributes after we upload the submitted files into our ProjectWise system. It’s a cascading series of dialogs to populate all the attribute information we require. This information is stored in XML files with the same name as the file they were indexed from.

Submittal is a file submittal software. It is able to check for things like valid CADconform certification markers in the files, and accompanying Indexer XML files, among other things. It is this [filename].submittal that you will turn in to KDOT to satisfy the source file delivery requirements of your project.

There’s a mildly dated video on our YouTube channel that is still relevant and should be helpful.

Creating a Submittal Archive with ControlCAD - YouTube

NOTE: Submittals with both v8i and CONNECT content should be separated into two submittals (One for v8i content and one for CONNECT content).

How do I access and sign into CADconform in Connect Edition?

KDOT doesn’t deliver CADconform with the workspace, you will have to independently download, install, and license their latest version from https://altivasoft.com/downloads/CADconform/.

KDOT’s workspace will redirect the resources (Standard, Discipline, User) to our workspace, but relies on CADconform being loaded independently. In CONNECT Edition products, CADconform can be accessed as a workflow in the top-left of the application.

The marker that places with the toolbox is just the KDOT_Compliant certification marker, when I insert the cell Survey_Compliant, it doesn’t update when I run the certify, however, the KDOT_Compliant certification marker does.

The marker and certification cells used depend on the user that you are logged in as. The Survey_Compliant cell certification is tied to the Surveys login in CADconform.

Is the creation of a ControlCAD Indexer .xml file for each DGN file still required, and if so, is there any guidance you can provide to expedite this process?

While the information in the Graphic Standards Manual is admittedly grossly out of date related to CONNECT Edition resources and processes, the section regarding the submittal of files remains largely relevant. We are still requiring the use of CADconform for CAD standards conformance / certification, Indexer for the collection of electronic file metadata, and Submittal for the bundling and delivery of the project submittal.

Internally we are still directing our users to produce one sheet per DGN in order to leverage ProjectWise Titleblock Integration for the sheet numbers until Bentley can support the federation of information between ProjectWise environment attributes and the Sheet Index. While it would be preferable for importing the files into ProjectWise as attributed documents per sheet, we will not reject a submittal if there are multiple sheet models per DGN at this time. If you opt to keep multiple sheet models in one file they should still be logically divided into separate sheet files by sheet type and not lumped in with the source corridor file for the sake of properly indexing the data. Please index the sheet container DGN with the first sheet number of the series, and be sure to note the page ranges that will be missing in the submittal as that is one of our QA/QC processes for evaluation of the submittal.

One XML file per file submitted is still required.  One thing that may help is the Retain Settings checkbox. This will allow you to retain all information from one file to the next and only update the attributes that have changed. Each time you press the Save button it will advance to the next file, bringing all the attribution from the last file. Only the last few categories will likely need altered from one file to the next. KDOT has also included resources such as updated titleblock cells which work in conjunction with Sheet Index.

We are having issues with the drawing certification cell coming in much larger than the border, no matter the scale settings. Is this a known issue with a known solution?

We have included guidance in the workspace download. The relative location of the guidance can be found here: "C:\ProgramData\KDOT CONNECT Workspace XX.XX\Docs\Certification Marker Cell Scaling Issue Work Around.pdf"

The issue is resolved in CADconform V8.1.48 and newer.