Governing a CAD environment: an owner, a standards register, shared libraries and coordinated upgrades

A machine design business with twenty engineers notices problems that seem unrelated. The same M8 bolt appears in bills of materials under three part numbers. Assemblies opened on one workstation report missing components that appear fine on another. A customer’s drawings arrive with a title block nobody recognises. Last month, one engineer installed the new CAD release early, saved files into the shared project folder, and nobody else could open them. The person who set the system up left last year, and nobody is quite sure where the current templates live.

None of these problems came from a single bad decision. A computer-aided design (CAD) environment usually decays through accumulation: a setting changed for one project and never reverted, a library copied locally to meet a deadline, an exception that became permanent, an upgrade done by whoever got to it first, and knowledge held by one person who has since moved on. Each change is small. Together they produce inconsistent data, wasted time, bill of materials errors that reach purchasing and production, and occasionally lost work.

Governance turns a set of good decisions about the CAD environment into a system that stays maintained. It needs three things: a named owner with defined authority, a written record of what has been decided, and a process for changing it deliberately. This article explains how to set up the administrator role, keep a standards register, control shared libraries, manage settings and deployment, run upgrades as coordinated events and review the environment periodically. It is general information applicable to most 3D CAD and product data management systems; specific settings and procedures depend on the software and release in use.

Name an owner

CAD administration sits between engineering and IT, and often belongs to neither. IT controls servers, networks, security, backups and operating system updates. Engineering understands drawing standards, revision control, what the data mean and what an approval represents. Neither can run the environment alone.

The single most effective step is to name a CAD administrator, even if the role is only part of someone’s job. Write down:

• Who holds the role and what proportion of their time it takes.
• What they decide: templates, libraries, locked settings, property schemas, workflows and upgrade timing.
• How they work with IT: who manages servers, backups, licence services, network shares and security updates, and how changes are coordinated.
• Who deputises when they are away.

Unnamed responsibilities are the ones that slip: the restore test that is never run, the permissions review that never happens, the library that is never cleaned up.

Keep a standards register

A standards register is a single document recording every controlled decision about the CAD environment. It takes perhaps a day to establish and answers questions that would otherwise depend on someone’s memory. Typical sections:

The register is not compliance theatre. It lets a new administrator, an auditor or an engineer find out what is standard and why, without archaeology.

Control shared libraries

Standard part libraries, especially libraries that generate fasteners and other hardware on demand, are among the highest-risk shared resources. When each workstation generates its own copies, the same nominal component ends up represented differently across the business. The problems surface late, in bills of materials and purchasing: three line items for one bolt, three part numbers sent to a supplier, assemblies that cannot find components on another machine.

Good practice:

• Use one shared location for each library, addressed identically from every workstation. Where a network share is used, refer to it by its full network path rather than a mapped drive letter, because drive letters differ between machines. Where a data management system holds the library, check that every user’s local view is set up the same way.
• Configure before production use. Decide which standards are enabled, how components are numbered and described, how sizes and variants are named, which properties they carry and which sizes are permitted. Agree numbering and descriptions with purchasing and production, because they drive the bill of materials and the business system.
• Treat naming conventions for variants as effectively permanent. Assemblies record the names of the variants they use; changing the convention later breaks references across historical designs.
• Restrict the range to sizes and grades the business actually buys and stocks.
• Give the library an owner, and control additions through the administrator.

The same principles apply to design libraries of standard features, purchased components and company standard parts. The building reusable CAD blocks that stay consistent article covers consistency of reusable content in two-dimensional drafting.

Control templates and properties

Templates, title blocks and property definitions determine what every new part, assembly and drawing contains. Keep one authoritative set in a controlled location, with a single person responsible for changes. Define the property schema, the names, meanings and permitted values of properties such as part number, description, material, finish, revision and approval, so that title blocks and bills of materials populate consistently. Use controlled lists for properties such as material and finish, rather than free text. The creating CAD templates for consistent drawing starts article covers template content in more detail.

Manage settings and deployment

Many CAD systems allow an administrator to prepare an installation image that defines which products are installed, where files live and which settings are applied, and to lock settings so users cannot change them. Use this to make every workstation consistent, particularly for file locations, templates, library paths, units and drafting standards.

Lock what genuinely must be consistent, and leave personal preferences, such as interface layout, free. Publish the locking policy with the reasons for each locked setting; people accept controls they understand far more readily than ones that seem arbitrary.

Roll out changes in stages rather than to every workstation at once:

1. Test add-ins, macros and integrations against the new configuration on a non-production machine.
2. Install on the administrator’s own machine first.
3. Run a pilot with three to five engineers covering the range of work, for at least a working week on real projects.
4. Fix problems in the image, not on individual machines, so the fix reaches everyone.
5. Release to the rest team by team.
6. Verify that versions and settings are consistent, then retire the old image.

During the pilot, check that templates and library components come from the shared locations, that drawings and bills of materials generate correctly on real assemblies, that add-ins and macros work and that printing and exports to customer and supplier formats behave as expected.

Upgrade together, on a published date

In many CAD systems, file formats move in one direction: a file saved in a newer major release cannot be opened in an older one. One engineer upgrading early and saving into shared data can make that data unusable for everyone else, irreversibly without restoring from backup. That single fact turns upgrades into coordinated team events.

Plan each upgrade with:

• A compatibility check: the versions of the licence service, data management server and client, add-ins, operating systems and databases that the new release requires, and the order in which they must move. Data management systems often require client and server versions to match, so the client change may need to happen for everyone on the same day.
• A decision on timing. Many organisations wait for an early service pack before adopting a new release. That is a sensible default, not a rule. Reasons to move earlier include a fix or capability with real value, or a customer who has already moved; reasons to wait include uncertified add-ins or a critical project phase; reasons to move regardless include operating system or database end of support.
• A published date, held firmly. An office that upgrades late but together is better off than one that upgrades early and unevenly.
• Rollback positions: what can be undone at each step, and the point after which rollback is no longer possible.
• Library planning: if a mixed-version period is unavoidable, separate library locations per major version, decided before the upgrade.

Backups, restores and continuity

CAD and product data are among a design business’s most valuable assets. Confirm with IT how the data are backed up, including the data management database and file store together, and test a restore periodically, recording the result in the register. A backup that has never been restored is an assumption. Document how licences are served and what happens if the licence server fails.

Review annually

Once a year, the administrator reviews the environment against the register: settings that have drifted, locations that have multiplied, exceptions that have outlived their reason, libraries with duplicate or unused content, permissions that no longer match roles and supporting software approaching end of support. The review catches the slow accumulation that daily work never notices.

A worked example

This is an illustrative example. A 25-person machine design and build business uses 3D CAD with a data management system. Its problems are those described in the opening: duplicate fasteners in bills of materials, missing references between workstations, an uncoordinated upgrade and no clear owner since the previous administrator left.

Owner. The engineering manager names a senior designer as CAD administrator for about one day a week, with a written agreement with the IT provider covering servers, backups, licence service and network shares.

Register. In two days, the administrator builds a standards register: the release in use, controlled locations, locked settings with reasons, the property schema, workflow states and a change log. Three undocumented exceptions are found; two are removed and one is formalised with an expiry date.

Library. The hardware library is moved to a single location in the data management system. With purchasing, the administrator sets numbering and descriptions to match the business system, restricts sizes to stocked ranges and fixes variant naming. A clean-up replaces duplicate fasteners in active designs.

Settings. An installation image with locked file locations, templates, library paths and drafting standard is piloted with four engineers for a week, corrected and rolled out team by team.

Upgrade. An upgrade policy is published: the office moves together, after an early service pack, on a date announced a month ahead, with add-ins tested in advance. The next upgrade happens over a weekend, with the data management client switched for everyone on the same day.

Result. Within three months, duplicate fasteners disappear from new bills of materials and purchasing reports fewer part number queries. Missing reference complaints stop. A restore test, the first in years, succeeds and is recorded. When the administrator takes leave, the deputy can answer questions from the register.

Applying this in an Australian design office

• Name a CAD administrator, with defined time, authority and an agreement with IT.
• Keep a standards register covering versions, locations, settings, exceptions and changes.
• Use one shared location per library, addressed identically everywhere.
• Configure libraries before use, with purchasing and production.
• Control templates and property schemas.
• Lock essential settings through deployment, and explain why.
• Pilot changes and roll out in stages.
• Upgrade together on a published date, after checking compatibility.
• Test restores and review the environment annually.

Where CAD environments go wrong

• Nobody owns the environment.
• Libraries installed locally on every workstation.
• Mapped drive letters for shared content.
• Settings changed per project and never reverted.
• Engineers upgrading individually.
• Changes rolled out to everyone at once.
• Backups never restored.

Questions to ask about your CAD environment

• Who owns our CAD environment, and how much time do they have?
• Where are our templates, libraries and standards, and could a new starter find them?
• Do our bills of materials show the same component under different numbers?
• Which settings are locked, and do engineers know why?
• What is our policy for upgrades, and when is the next one?
• When did we last restore our design data from backup?

Bringing it together

A CAD environment rarely fails in one event; it decays through small, unrecorded changes. Governance stops the decay with three things: a named owner with authority and a clear interface with IT, a standards register recording what has been decided and why, and a deliberate process for change. Control shared libraries and templates centrally, configure them before use and agree numbering with purchasing. Lock the settings that must be consistent, pilot and stage every rollout, and upgrade as one team on a published date. Test restores and review the environment each year. The result is design data that stay consistent, bills of materials that purchasing can trust and an environment that survives staff changes.

---

Source: KEVOS editorial notes, drawing on earlier KEVOS CAD administration handbooks on governance and standards registers, standard library governance, deployment and settings governance, and upgrade planning and version compatibility. The guidance is written to apply to 3D CAD and data management systems generally. The worked example is illustrative. This article is general information.