FAQs
Before You Continue
Please note: A-SPEC specifications and reference materials are confidential and only available once a Confidential Disclosure Deed is signed with GISSA International. This FAQ page is publicly available, but access to the specifications themselves is subject to those terms.
Got a question about A-SPEC? You're probably not the first — here are answers to some of the most common questions from the A-SPEC Community.
With a growing list of questions, the quickest way to find yours is to search the page (Ctrl+F on Windows, Cmd+F on Mac) for a keyword — like "cost," "accreditation," or "existing assets" — or browse by specification, as some questions are grouped under A-SPEC, B-Spec, D-Spec, O-Spec, R-Spec, S-Spec, W-Spec and X-Spec.
Can't find what you're after? Send us a message via our Contact page — feel free to attach files or photos if that helps explain what you need.
1. About A-SPEC
| Question | Answer |
|---|---|
| Who is GISSA and what is their role in A-SPEC? | GISSA is a vendor-independent information management consultancy established in 1990. GISSA is the originator and manager of A-SPEC, the Australian asset specification standard. We work with A-SPEC users to understand context and requirements, onboard the specification, train employees and consultants, harmonise data across systems and add features and classifications over time |
| What is A-SPEC? | A-SPEC is a common data specification that ensures 'As Constructed' infrastructure data is captured consistently and correctly, first time. It covers a range of asset types — including buildings, drainage, open space, and roads — through a suite of individual specifications developed with the A-SPEC Community. |
| How does A-SPEC inform a Digital Twin environment? | A Digital Twin is only as reliable as the data behind it. A-SPEC ensures that 'As Constructed' infrastructure data — from surveyors, contractors, and consultants — is captured in a consistent, machine-readable format from the outset. That consistency means the data can be reliably fed into and maintained within a Digital Twin, rather than requiring costly rework or reconciliation between different data sources and formats. |
| What's the difference between A-SPEC and D-Spec or the other specs? | Think of A-SPEC as the overarching framework, and D-Spec as one specific application of it — for stormwater drainage infrastructure. If you're supplying or receiving digital data about drainage assets like pipes, pits, or WSUD elements, you'll be working with D-Spec, but always alongside the A-SPEC Introduction & Overview document, which sets out the rules common to every specification in the suite (B-Spec, D-Spec, O-Spec, and so on). |
| What are the specifications under the A-SPEC framework? |
|
| What kind of data does A-SPEC cover? | A-SPEC data typically addresses the location of an asset and its specific characteristics, to establish your asset inventory or register. |
| Why does asset data quality matter so much for infrastructure decisions? | Poor data quality directly undermines the ability to make sound investment decisions — without reliable information on an asset's condition, risk, and performance, organisations end up "sweating assets" past their useful life or making poorly targeted renewal decisions. This has been identified as a leading cause of inefficient infrastructure spending in government reviews internationally. |
| How does A-SPEC help with benchmarking and comparing performance across organisations? | When every organisation captures and describes asset data differently, comparing performance — even within the same sector — becomes meaningless. A-SPEC's standardised terminology and structure means data captured by one council or authority is directly comparable to another's, enabling genuine benchmarking and shared learning across the A-SPEC Community. |
| What is Digital Engineering, and how does it relate to A-SPEC? | Digital Engineering (DE) is a broad discipline covering the use of digital tools and processes across the full lifecycle of a built asset — design, construction, BIM models, digital twins, and project delivery workflows. A-SPEC sits within this wider landscape but has a narrower, specific focus: defining what GIS-based asset data must be captured and delivered so that councils and utilities can manage their assets once they're built. DE is about how things get designed and built digitally; A-SPEC is about what spatial asset information gets handed over at the end. |
| Is A-SPEC the same as Digital Engineering? | No - A-SPEC is a specification for GIS-based asset data deliverables — it defines what spatial data is required, in what format, and to what standard. Digital Engineering is the broader set of digital design, modelling, and delivery practices that may produce that data in the first place. A project can follow strong DE practices and still fail to deliver A-SPEC-compliant data if the final GIS handover isn't structured and machine-readable. |
2. Getting Started
| Question | Answer |
|---|---|
| How do I get access to the specifications? |
The process is the same whether you're a prospective subscriber, an asset owner, or a service provider — start by completing the Contact form to submit your enquiry. Turnaround on our end is fast — we endeavour to finalise standard enquiries within the day we receive your signed NDA. If there are queries about the terms, this may take a little longer. See below for what's involved at each step. |
| What information will GISSA ask for when I request access? |
To tailor the right support for you, GISSA will confirm:
|
| What happens once I've provided that information? |
The standard process is:
For service providers, we have created the following guide to assist you: A-SPEC Quick Start Guide for Consultants Final 20260218. |
| What if I'm supplying data to an organisation that isn't an A-SPEC member? | Let GISSA know — a separate conversation is needed to discuss your intentions and how access would be provided in that case. |
| What can I do once I have access? |
A few things worth knowing:
|
| What is the Asset Deliverables Checklist, and when do I complete it? | It confirms, in advance, exactly which asset data will be delivered at Practical Completion — completed with the asset owner during project planning, not at submission. Available on the Resources page (login required). |
| I'm not a GIS person, so what can I do? | The starting point for determining how you will create the data may be your surveyor, as many surveyors have specific capability to deliver A-SPEC data — typically because their surveying software vendor provides an A-SPEC output solution. If you are unsure, please contact GISSA. |
| Do I need to be a licensed or certified surveyor to do the field capture? | This is driven by the jurisdiction you are working in. Please confirm with your association or relevant government agency. |
| How do I find out the detail I need to know for my project? | Three steps: (1) confirm which specification(s) apply to your project's asset types, (2) check the Downloads page for the current, required version of each, and (3) confirm your client's specific requirements, since these can vary by project even within the same specification. If anything's unclear, contact GISSA for guidance. |
3. Cost & Accreditation
| Question | Answer |
|---|---|
| How much does A-SPEC cost? | Cost to customers (e.g. councils, utilities, and asset owners) is in the form of an annual subscription. Contact GISSA for pricing specific to your organisation.
There is no cost to service providers (surveyors, engineers, building contractors, landscape architects, etc.). In both situations, your organisation will be requested to sign a Non-Disclosure Agreement to protect the intellectual property you will be exposed to. |
| Is A-SPEC transferable to other countries or jurisdictions? | Yes — contact GISSA to discuss the process. |
| Can I get accredited to deliver A-SPEC data, and what is the cost? | Yes, individuals can become accredited. This includes your capability to deliver against the specification's requirements, and how you communicate with the A-SPEC member to resolve any issues raised. Please contact GISSA for a quote — there is a set structure of an initial cost followed by an annual cost to maintain accreditation, though the amount will vary depending on what's required. |
4. Specifications & Data Requirements
| Question | Answer |
|---|---|
| Why does A-SPEC separate "as-constructed" data from ongoing asset management data? | As-constructed data is captured once, at the point an asset is built — and it's extremely costly, sometimes practically impossible, to collect retrospectively if missed. A-SPEC's DDS versions ensure this critical data is captured correctly the first time, forming the foundation that ongoing asset management (condition monitoring, risk assessment, renewal planning) relies on for the rest of the asset's life. |
| Is there a full list of which asset types belong to which specification? | Yes — the Asset Deliverables Checklist maps every asset type to its relevant specification, and is used during project planning to confirm what's required at Practical Completion. Available on the Resources page (login required). |
| Where do I find the correct EPSG code for my project? | Common EPSG codes for Australia are listed in the relevant consultant guide (Sub Appendix 1) and also referenced in each specification. Confirm the correct code with your asset owner before submission. |
| Is there a glossary of A-SPEC terms? | Pending |
| What if I have asset types that aren't included in the A-SPEC suite? | A-SPEC is designed for expansion to accommodate new and emerging infrastructure. X-Spec, for example, was introduced specifically to cover supplementary asset classes that don't naturally fit within the existing specifications. |
| What's the difference between the DDS version and the Existing Assets version of a specification? | A-SPEC covers both new and existing assets — you're not limited to newly constructed infrastructure. The DDS version applies to newly constructed assets — for example, from subdivision developments or capital works. The Existing Assets version is used when assets are already built or installed and the capture is retrospective, such as confirming an existing inventory, hydraulic modelling, or flood plain mapping. |
| How do I capture historical or existing asset data? |
Start by accessin the specifications that have the term existing in their document name. For example "B-Spec - Existing - Version 1.0.6 FINAL 20230904-V5.pdf" Each attribute in the Existing Assets versions is categorised by how critical it is to capture:
|
| What is the Harmonised Codelist, and how do I use it? | The Harmonised Codelist provides the standard codes used across all A-SPEC specifications for newly created assets. Some codes used in Existing Assets versions may not yet appear in this list. |
| What if the feature I have does not exist as a Code? | GISSA has developed a tool called the Code Dashboard that will enable you to create a new code and, at the same time, communicate this to GISSA. This can be accessed on the Resources page. |
| Is there a glossary of A-SPEC terms? | Yes — the A-SPEC Glossary of Terms and Definitions lists common terms and their alternative names (used across different jurisdictions), so everyone can synthesise to the same A-SPEC terminology. See the Glossary page for the full list. |
| Is there a full list of which asset types belong to which specification? | Yes — the Asset Types table lists every asset type against its relevant specification (B-Spec, D-Spec, O-Spec, R-Spec, S-Spec, W-Spec, and X-Spec), so you can quickly confirm which spec covers what you're planning to work with. See the A-SPEC Full Asset Listing for the full list. |
| Are there worked examples of how A-SPEC has been applied to specific situations? | Yes — GISSA has begun developing a set of worked examples based on real questions from the A-SPEC Community. See the Practice Notes: Real Questions from the A-SPEC Community page for the current list — it's a growing resource, with new examples added as they arise. |
| What does "digital data" mean in the A-SPEC context? | In A-SPEC, digital data specifically means GIS layers — spatial data representing assets as points, lines, or polygons, each carrying attributes (like material, install date, or condition) tied to a location on a map. This is different from a generic "digital" file like a PDF report or a Word document. A-SPEC's focus on GIS layers is what allows asset information to be mapped, queried, and integrated directly into a council or utility's spatial asset management systems. |
| What does "machine-readable" mean in relation to GIS layers, and why does it matter? | A machine-readable GIS layer is one that GIS software can open, interpret, and use automatically — with correctly structured geometry (points, lines, polygons) and attribute fields that are clearly named and populated with usable values, not a scanned image or a static picture of a map. A shapefile or geodatabase feature class with proper attribute fields is machine-readable; a PDF map or a screenshot of a GIS layer is not, even though both might be called "digital." A-SPEC requires machine-readable GIS layers specifically, because that's what allows the data to load directly into a council or utility's GIS and asset management systems without manual rework. |
| Does digital data have to be machine-readable to meet A-SPEC requirements? | Yes. A-SPEC's deliverable requirements are built around machine-readable GIS formats specifically, because the goal is for councils and utilities to load asset data directly into their corporate information systems of GIS and Asset Managment — not manually redraw or re-digitise it from PDFs or static maps. |
| What's an example of digital data that isn't machine-readable in the A-SPEC context? | A PDF map showing asset locations, a scanned as-built drawing, or a screenshot of a GIS layer exported as an image. All of these are technically "digital," but none of them can be automatically loaded into a GIS or asset management system as usable spatial data — the geometry and attributes would need to be manually redrawn and re-entered, which is exactly the gap A-SPEC is designed to close. |
| Can a project be "digitally advanced" and still fail A-SPEC requirements? | Yes, and this is a common gap. A project can use sophisticated 3D modelling and BIM tools throughout design and construction, and still hand over asset locations at Practical Completion as a PDF site plan or an image rather than a proper GIS layer. Strong Digital Engineering practice during delivery doesn't automatically produce a machine-readable GIS layer at handover — that has to be planned for specifically. |
5. Integration & Compatibility
| Question | Answer |
|---|---|
| Can A-SPEC data be integrated with other systems, such as financials? | Yes. Members use A-SPEC data to drive things like BIM, maintenance forecasting, cost forecasting, and asset performance monitoring. |
| Does A-SPEC compete with my existing asset management software? | A-SPEC is not an asset management package, and doesn't compete with your existing systems. It complements them by providing data in a standard format, and doesn't dictate the data models your systems use. |
| Does A-SPEC align with recognised industry standards? | Yes — A-SPEC currently aligns with standards such as AS 5488-2022, ISO 55000. |
| How does A-SPEC support compliance with Victoria's Asset Management Accountability Framework (AMAF)? |
AMAF is the Victorian Government's mandatory asset management policy framework, aligned to ISO 55000. For Victorian agencies, A-SPEC supports AMAF compliance directly at the acquisition stage — providing standardised, correctly captured as-constructed data at the point of construction, which is the foundation for the condition monitoring, performance tracking, and maturity self-assessment AMAF requires further downstream. Since A-SPEC also aligns with ISO 55000, adopting A-SPEC supports the same underlying standard your AMAF compliance is measured against. If your jurisdiction has its own asset management accountability framework, the same principle applies: A-SPEC's standardised, ISO 55000-aligned approach to as-constructed data provides a strong foundation for meeting similar requirements, wherever you're based. |
| What's the relevant WSAA standard for water and wastewater data? | A-SPEC aligns with A Water Industry Guide for the Management of Asset Data using Uniclass, developed jointly by WSAA (Water Services Association of Australia) and BIM4Water. |
| Should I include A-SPEC requirements in my Project management Framework? | Yes - this will provide guidance to your project managment and project delivery teams as to the requirements based on your organisations "gated" approach. For example when to determine requirements, or how to communicate the requirements and tie them into the deliverables. |
| Is A-SPEC a Common Data Environment (CDE)? | Not quite — A-SPEC is a data specification, defining what asset data should contain and how it should be structured. A CDE (as defined by ISO 19650) is a platform or repository where data is stored, versioned, and managed through a workflow. A-SPEC provides the data standard that a CDE relies on to be genuinely useful, rather than being a CDE itself. |
6. Governance & Changes
| Question | Answer |
|---|---|
| How are changes to the specifications proposed and approved? | Once proposed, GISSA undertakes a consultation process with the A-SPEC Community. Enhancements are driven by the user Community, for the user Community. |
| Who can propose a change to A-SPEC? | Changes are initiated by suggestions from the A-SPEC Community and through research undertaken by GISSA. If you'd like to propose a change, contact GISSA — proposed changes currently under consideration can be viewed on the Proposed Changes for Feedback page. |
| What is the future for A-SPEC and GISSA? |
Every year we hold forums and member/user/network consultations to understand needs and requirements, and update A-SPEC and support services. With strong governance and a capable service team, A-SPEC is designed and supported for consistency, continuity, and sustainability. |
7. Submission & Compliance
| Question | Answer |
|---|---|
| What is the purpose of the Certification Form and the Quality Report? | Each submission must include a Certification Form and a Quality Report, as they provide specific details about the project. For convenience, these are combined into a single template, available for download on the relevant specification's reference page via your login. |
| Why is it important to integrate A-SPEC requirements into a project management framework's gated approach? | Most capital works projects follow a project management framework with a gated approach — defined checkpoints between phases, typically from concept, through design and construction, to practical completion and handover. Integrating A-SPEC requirements into these gates, rather than treating data delivery as a final step, ensures that asset data expectations are confirmed early and checked at each stage, rather than being left as an afterthought at handover. This reduces the risk of data gaps, rework, or non-compliant submissions being discovered only at Practical Completion — when it's often too late or too costly to correct them. |
| What validation systems does A-SPEC support? | This depends on your asset owner — common options include the GDV Hub, ACDC, or a proprietary system. Confirm with your asset owner early in project planning. |
| What file formats are accepted for A-SPEC data submission? | Accepted formats vary by validation system, but commonly include Esri Shapefiles, MIF/MID, and GeoPackage. Check with your asset owner to confirm what's supported. |
| What happens if my data fails validation? | Validation is iterative, and it's common not to pass on the first attempt. If it keeps failing, contact your asset owner's GIS/Asset Management team or GISSA for support. See the Quick Start Guide for common causes of validation failure. |
| What are common causes of validation failure? | Common causes include missing or incomplete attributes, incorrect or null values, geometry errors (wrong type, inaccurate positioning, or topology issues like gaps and overlaps), and coordinate system errors such as an incorrect EPSG code. |
| What is a QA/Tolerance report, and why does A-SPEC request one with each data submission? | A QA/Tolerance report records any changes that occur in the field during construction, so they can be checked against the data actually submitted. A-SPEC requests one with every data submission to confirm that what's been delivered accurately reflects what was built — not just what was originally designed — and to support the internal QA processes organisations already have in place for verifying asset handover. |
| Why is this considered a gap in current asset handover processes? | Many current processes don't capture a clear record of how as-constructed data was verified against real-world conditions on site — data is often submitted without confirmation that field changes during construction were properly reflected. A-SPEC's processes are designed specifically to close that gap, supporting organisations' own internal QA and verification processes rather than replacing them, and giving councils and utilities confidence that submitted data is accurate, not just design intent carried through unchanged. |
