Industry News
ADAC Version 6: A Technical Overview for Industry and Councils
A practical overview of the structural and workflow considerations introduced with ADAC Version 6 for asset owners, councils, utilities and delivery teams.
ADAC Version 6 continues the move towards more consistent, structured digital asset information. For councils, utilities, designers and contractors, the important change is not simply a new XML version: it is the need to keep project data, geometry, asset attributes and receiver requirements aligned throughout delivery.
What changes in practice
Version 6 projects should be prepared against the schema and receiver profile nominated for the job. Teams need to confirm required asset classes, attribute rules, coordinate reference information and supporting document expectations before final export. A file that is valid against a base schema may still require receiver specific information.
A stronger validation workflow
A dependable workflow separates three checks:
- Schema structure: the XML follows the selected ADAC schema.
- Project and asset content: required values, identifiers and geometry are present and internally consistent.
- Receiver profile requirements: council or utility rules are applied for the intended destination.
infrADAC supports these checks inside the design environment and through browser review. Findings identify work that needs attention, but they do not replace the receiving authority's own assessment.
Planning a transition
Organisations moving to Version 6 should review templates, profile files, drawing standards, export procedures and quality assurance checklists together. Pilot projects are useful for confirming how existing source data maps to the new delivery requirements before a wider rollout.
Where to find current requirements
The infrADAC Wiki maintains the current ADAC XML reference material, product manuals and council or utility directory. Always confirm the nominated schema and receiver profile for the specific project before delivery.
