The key objective of A-SPEC is to create a Community of Sharing. Learning form each of our experiences will
- enrich the experience and
- provide a foundation for contribution
'As Constructed' data has been acknowledged as one of the foundation building blocks for a DIGITAL BUILT ENVIRONMENT to enable SMART CITIES.
A-SPEC is a suite of data specifications supporting the delivery of machine readable data relating to infrastructure assets - A Digital Twin.
A-SPEC provides certainty that the correct data is captured in the correct format - streamlining processes related to the capture, validation and usage of infrastructure information.
A-SPEC delivers benefits to all participants involved in the commissioning, designing, building and maintaining of infrastructure assets through providing the basis for a consistent and efficient approach to the supply of digital 'As-Constructed' data.
Download the following brochures for more information about A-SPEC:
The A-SPEC suite of specifications have been created in close consultation with A-SPEC Community members and directly addresses the needs of the Community to develop inventories and future programs.
The A-SPEC Knowledge Sharing Community comprises a growing consortium of 60+ Local Authorities across Australia using the A-SPEC standard specifications. This includes 17 of 31 Growth Area Councils in Australia who have identified A-SPEC as the preferred method of engagement with industry.
Any modification or enhancement to any of the A-SPEC specifications is controlled by clear governance arrangements and change management protocols that includes consultation with the A-SPEC Community. This collective approach to the specifications ensures all Community Members' interests are taken into account in the specification evolution process. Enhancements are driven by the user Community for the user Community.
Keeping in mind that all changes to the specifications are subject to approval by the A-SPEC Community, a proposed Roadmap outlining the ongoing development of A-SPEC is here.
A-SPEC FOR CAPTURING NEW ASSETS
Current A-SPEC Versions valid from 31 May 2019
CAPTURING HISTORICAL DATA
Capturing historical data either from backlog or retrospective field capture has been challenging. What is to be captured? What can be seen? How much detail do I take from existing drawings?
A-SPEC FOR CAPTURING EXISTING ASSETS
The following table outlines versions of the specifications that have been tailored to accommodate this requirement. Each of these documents was created in parallel and in harmony with the full versions used for the capture of newly created assets.
Each attribute has been explored and categorised as to its practicality of capture. The table below describe the requirement for the capture of each attribute.
|C||Core requirement – data is to be collected in the field to populate the attribute|
A required attribute and may need more research possibly through sourcing existing plans in the office or other field testing.
It is to be noted that further investigation may not be warranted and therefore this field may not have a value entered into it.
|O||Optional field - use as appropriate.|
Previous A-SPEC Versions valid until 31 May 2019
Addendum List (As of 4/03/2019) INCORPORATED INTO CURRENT VERSIONS PUBLISHED 31 MAY 2019
|Release Date||Addendum Name||Relevant Spec/s||Content of Addendum|
|10 December 2018||ADDENDUM No 1 - R-Spec 20181210||R||Attribute name changes in Asset Class Traffic Management Points.|
|25 February 2019||ADDENDUM No 2 - R-Spec 20190225||R||Attribute name changes in Asset Class Pathway Centreline.|
|4 March 2019||ADDENDUM No 3 - R-Spec 20190304||R||An example included in the Description column does not align with the published CODE LIST CODE value in the ITS (Lines) & ITS (Point) Asset Classes|
|25 February 2019||ADDENDUM No 1 - D-Spec 20190225||D||Attribute default value changes in Asset Class OSDS-Linear|
|4 March 2019||ADDENDUM No 2 - D-Spec 20190304||D||An example included in the Description column in the Water Harvesting Device Asset Class was changed to align with the new value in the Position CODE LIST CODE.|
|13 March 2019||ADDENDUM No 3 - D-Spec 20190313||D||Attribute to be added to asset Pits in the spreadsheet (exists in document)|
|25 February 2019||ADDENDUM No 1 - O-Spec 20190225||O||
Attribute data type and length changes in Asset Classes Landscaping and Jetties, Piers, and Marinas.
|4 March 2019||ADDENDUM No 2 - O-Spec 20190304||O||An example included in the Description column does not align with the Position CODE LIST CODE value.|
|25 February 2019||CODE LIST Addendum No 1 20190225||D, O|| Additional CODES missing from published versions added in Bank Foundation Material,
Geofabric/Transition Material, Valve Control Type, Valve Power Type CODE LISTS.
|4 March 2019||CODE LIST Addendum No 2 - 20190304||D, O||CODE modified from published version in Position CODE LIST.|
|6 March 2019||CODE LIST Addendum No 3 - 20190306||S, W||CODES added and modified from published version in Pipe Installation Method CODE LIST.|
Below is a link to our CODE LISTS for all A-SPEC Specifications for newly created assets.
Please note some codes that appear in the versions for the Existing Assets may not appear in this table. This will be addressed from Vesrion 1.0.6
Care is to be taken in the use of this list.
If you wish to help us expand or modify our list, contact us with recommended Codes and Descriptions for specific CODE LISTS or NEW CODE LISTS.
Addendum List (As of 4/03/2019) INCORPORATED INTO CURRENT VERSIONS PUBLISHED 6 JUNE 2019
If you have any questions relating to A-SPEC, please contact us.