17Documentation#

17.1ITS program#

The Contractor's ITS program shall include:

1. a)detailed design drawings, design calculations, manufacturers specifications and schematic layout of components for review by the Administrator
2. b)applications for electricity supply
3. c)applications for telecommunications services
4. d)updates to operations manuals
5. e)updates to equipment or System descriptions
6. f)updates to maintenance and repair manuals
7. g)updates to program schedule
8. h)quality plans
9. i)testing and commissioning plans
10. j)FAT, IAT, CT, CAT and where applicable, SAT activities, and
11. k)equipment delivery.

The Contractor shall provide to the Administrator updates to the ITS program of Works on a fortnightly basis.

17.2Calculations and design data#

The Contract shall include in the final design documentation copies of all calculations, Safety Requirements Specifications as described in Clause 8.5, assumptions and design data relating to equipment provided in accordance with this Technical Specification.

All such information shall be certified by a RPEQ as meeting the requirements of the Contract.

The RPEQ shall only certify documents within their registered field of practice.

The Contract shall include in the final design documentation copies of documentation detailing the assessment and resulting design impacts of all devices and/or systems in accordance with AS 61508.0.

17.3Design and manufacturing certifications#

The Contractor shall include in the final design documentation (and include in the operations manuals) copies of relevant compliance certificates for equipment and materials, including:

1. a)radio frequency interference
2. b)electromagnetic compatibility
3. c)retro-reflectivity
4. d)paint thickness
5. e)Austel approvals, and
6. f)other relevant certifications.

The Contractor shall include in the final design documentation the following documents where relevant:

1. a)fabrication and assembly drawings, detailing all the components to be installed
2. b)manufacturer's specifications of the enclosure / cabinets and of all major components, detailing ratings and performance characteristics
3. c)a schematic layout of components, building details and interconnection diagrams
4. d)recommendations for routine maintenance tasks, and
5. e)recommendations on spare parts.

Prior to Practical Completion all documentation shall be updated to reflect any variations from the certified final design documentation. All updated manufacturer equipment manuals, maintenance manuals, procedures, design documentation, engineering drawings and system specific software and hardware configurations shall be supplied to the Administrator.

All engineering design drawings shall be certified by a RPEQ. The RPEQ shall only certify documents within their registered field of practice. Design drawings shall be arranged and presented to clearly allow such certification(s).

17.4Operations manuals#

Prior to Practical Completion, the Contractor shall provide the Administrator with copies of a comprehensive operations manual in electronic format. The manual shall be delivered on External Removable Storage Device (ERSD) devices or similar approved electronic media.

The electronic files must be organised in a clear and logical directory structure. To ensure compatibility and accessibility, file directory paths, including file names, must not exceed 255 characters in total length. The Contractor shall ensure that directory and file names are concise, descriptive, and free from unnecessary depth or complexity.

The ERSD shall be securely stored in appropriately labelled A4-sized storage pockets and included within the operations manual package. The Contractor must confirm with the Administrator that the format and structure of the electronic manual meet all specified requirements prior to submission.

17.4.1Manual contents#

The manuals shall consist of a dedicated section to cover each separate ITS application or equipment. Each physical volume of the manual shall be provided with a high-level Table of Contents that contains a comprehensive list of the ITS applications / equipment provided. The table of contents in each volume shall highlight the installation Sites for the ITS applications / equipment it contains. Each installation Site shall be further sub-divided with the following headings as appropriate:

1. 1.Operating Procedures
2. 2.Maintenance, Diagnostics and Troubleshooting
3. 3.Repair Manuals for components or individual ITS Equipment, including circuit descriptions, Functional Block diagrams; Complete circuit diagrams to component level
4. 4.Maintenance Manuals as detailed in Clause 19
5. 5.Compliance Certificates
6. 6.Recommended Spares
7. 7.Calculations and Design Data
8. 8.Test, Configuration and Commissioning Records
9. 9.Drawings and System Schematics (including Functional System Block Diagrams)
10. 10.Wiring and Termination Diagrams
11. 11.Mains Power Details
12. 12.Telecommunications Details
13. 13.Training notes and Training presentations.

17.4.2Electronic copies of manual#

Unless otherwise specified, electronic copies of the following documentation shall also be provided in addition to Clause 17.4.1.

1. 1.The Index and contents of the (ERSD) shall match that of the paper copy.
2. 2.The electronic contents will be duplicated in 2 different copy formats.
3. 3.The Narrative text of both versions shall be in a left justified size 12 (or larger) serif type font, similar to Times New Roman.

The first copy shall be a PDF copy of the folder's Paper contents including separate PDF copies of the standalone Graphics (Drawings).

The Second copy shall be a duplicate of the first, but the file formats must remain in their original source formats such as file1.docx, file2.xlsx, file3.dwg including any associated original graphics files.

PDF files must be provided as native PDF, exported directly from the source software and not scanned images.

Information that specifically identifies each item, such as a serial number, firmware revision number or the like shall also be included in the manuals.

An example of the Table of Contents is included in Appendix A of this Technical Specification.

Where generic documents (such as the user manual for a specific ITS device) are relevant to more than one Site installation, only one copy need be provided in each copy of the operations manuals. Cross-reference(s) to the Site installation section in the operations manuals that contains the relevant documentation shall be provided in the other Site installation sections.

The Contractor shall update the Operator's Manual throughout the Contract as necessary to retain the manual's currency and accuracy.

17.5Test, configuration and commissioning results#

Copies of all test, configuration and commissioning results shall be provided in the respective section of the operations manuals.

Where results are hand written, the original copy shall be provided. Results recorded by hand shall be in blue ink.

17.6Principal's maintenance manual#

The Contractor shall update the Maintenance Manual throughout the Contract to retain the manual's currency and accuracy. Prior to final handover, the maintenance manual shall be provided to the Administrator.

This maintenance manual shall include content which is no lesser than that included in the maintenance manual implemented by the Contractor during the defects liability and/or maintenance phase(s) of the Contract.

17.7Asset data#

The Contractor shall provide asset data for all equipment installed as part of the Project. Such data must be structured and submitted in strict compliance with the asset data capture schema as prescribed by the Principal.

The Contractor is required to liaise with the Principal to obtain the necessary forms, templates, and associated guidelines. All fields within the forms must be completed accurately and in accordance with the instructions and specifications provided by the Principal.

Where the Contractor is required to utilise Building Information Modelling (BIM) for Intelligent Transport Systems (ITS), these shall be in accordance with the standards and guidelines provided by the Principal. In addition, the ITS asset model, which forms the basis of the asset data, must be structured and submitted in strict compliance with the asset data capture schema as prescribed by the Principal, to enable the Principal to manage the asset efficiently and effectively post-delivery.