Department of Defence. Spatial Data Management Plan. DRMS Document Id: Version: Defence Support and Reform Group R

Transcription

1 Department of Defence Defence Support and Reform Group Spatial Data Management Plan DRMS Document Id: R Version: Status: Draft Dated: 01 March 2015 Produced for: Director SIM

2 EXECUTIVE SUMMARY The Defence Support and Reform Group (DSRG) Spatial Data Management Plan (SDMP) has been developed to provide standards and specifications for spatial data management. The standards and specifications within the SDMP will improve data consistency and availability of information, and facilitate spatial information dissemination and sharing within DSRG. With its use, DSRG will achieve a standardised approach to spatial data management that will realise many benefits to both the organisation and its staff including: Consistent and more reliable data that will lead to more informed decision making; Closer integration with other DSRG information systems and Defence spatial data users Portability of staff skills; and Greater interoperability with organisations outside of Defence. The SDMP shall be used by spatial data users both within Defence and Defence Contractors, and data managers within DSRG. It is the responsibility of data users to implement the SDMP Specifications and produce data in accordance with the specifications. Data Users shall implement all requirements defined in Section 2, and the specific data requirements in Sections 3 onwards as determined by the type of data to be created or updated. The SDMP is made up of three main Sections: Section 1 provides an introduction to the SDMP, the scope of implementation and other background information to the document. Section 2 contains the General Data Specification that describes data formats, file naming conventions, metadata requirements, the approved datum and coordinate systems, measurement units, accuracy and other DSRG data standards. Sections 3 onwards contain a set of specific data type specifications that shall be implemented by all spatial data users. The data specifications cover the key DSRG data types, the Master Site Plan and the Spaces (Floor) Plans, in addition to specifications for engineering detail survey, aerial photography, master planning, environmental data and other data types. Appendices support the SDMP, providing detail of the DSRG Spatial Data Management Specification, the full Metadata Specification and additional appendices to support the core data specification and data type specifications. Table E-1 summarises the information held within each Section and Appendix. Version ii 01 March 2015

3 Table E-1 SDMP Sections and Appendices SDMP Section Section 1 Section 2 Section 3 Section 4 Section 5 Section 6 Section 7 Section 8 Section 9 Section 10 Section 11 Section 12 Section 13 Section 14 Appendix A Appendix B Appendix C Appendix D Appendix E Appendix F Appendix G Appendix H Appendix I Appendix J Appendix K Appendix L Appendix M Description of Contents Introduction Data Specification Master Site Plan Datasets Spaces Plan Datasets Reference Data Engineering Detail Survey for Infrastructure and Assets Garrison Support Services Data Communications Data Aerial Photography Satellite Imagery Master Planning Datasets Contaminated Sites Data Environmental Data Hazards Data Glossary References Contaminated Sites Data Standards Metadata Specification Directory Structure Scale and Accuracy Master Site Plan AutoCAD Standards Space Plan Standards Garrison Support Services AutoCAD Standards Master Planning CAD Standards Environmental Data Model Space Plan Labelling Standards Hazards Spatial Data Standards A set of template datasets are provided as part of the SDMP to assist in the implementation of the SDMP specification. The templates are available on the Defence Estate Quality Management System and include example data that has been collected in accordance with the SDMP specifications. Version iii 01 March 2015

4 TABLE OF CONTENTS Executive Summary Table of Contents Version History ii iv x 1 Introduction Purpose of SDMP Spatial Data Definitions Intended Audience Structure of SDMP Application of the SDMP SDMP Point of Contact Linkages with NSIMS DSRG Spatial Data Policy Future Changes to Spatial Data Management General Data Specification Introduction Data Format File Names Directory Structures Metadata Datums Coordinate Systems Units of Measurement Spatial Accuracy Spatial Scale Data Capture Data Viewing Version iv 01 March 2015

5 2.13 Spatial Integrity of Features - Topology Spatial Integrity of Features Topology in a CAD Environment Data Attributes Imagery Management Image Tiling Hardcopy Archival Vectorisation of Information Master Site Plan Datasets Scope of Specification Deliverables Deliverable Templates Data Deliverable Specification Specific Data Requirements Topology Specifications For Information Only Topology Guidelines Spaces Plans Scope of Specification Deliverables Deliverable Templates Required Inputs Data Deliverable Specification Specific Data Requirements Reference Data Scope of Specification Deliverables Deliverable Specification General Reference Documentation Deliverable Specification Design Drawings Version v 01 March 2015

6 6 Engineering Detail Survey for Infrastructure and Assets Scope of Specification Deliverables Data Inputs Deliverable Specification Specific Data Requirements Garrison Support Services Data Scope of Specification Status of Specification Deliverables Deliverable Templates Specific Data Requirements Communications Data Scope of Specification Deliverables Deliverable Templates Required Inputs Specific Data Requirements Field Capture Data Capture Aerial Photography Scope of Specification Deliverables Acquisition Requirements Orthophoto Specifications Orthophoto Deliverables Deliverable Specification Version vi 01 March 2015

7 9.7 Quality Assurance Documentation Specific Metadata Requirements Satellite Imagery Scope of Specification Background Information Deliverables Deliverable Specification Specific Data Requirements Master Planning Datasets Scope of Specification Deliverables Deliverable Templates Deliverable Specification Contaminated Sites Data Scope of Specification Deliverables Data Deliverable Templates Required Inputs Data Deliverable Specification Environmental Data Scope of Specification Background Information Data Deliverables Data Deliverable Templates Data Deliverable Specification Specific Data Requirements Hazards Data 95 Version vii 01 March 2015

8 14.1 Scope of Specification Schedule 11 Hazardous Chemicals Data and Maps (HAZCHEM) Hazardous Areas Data Unexploded Ordnance (UXO) Data Tables Table 1-1 SDMP User Groups...3 Table 1-2 SDMP Sections and Appendices...4 Table 1-3 Spatial Data Technical Authority...7 Table 1-4 Principles of the DSRG Spatial Data Policy...8 Table 2-1 List of Table 2-2 DSRG Spatial Data Formats Table 2-3 Recommended Tile Sizes Table 3-1 Scope of Master Site Plan Data Table 4-1 DEMS Structure Level Codes Table 4-2 Office Space Area Calculations Table 4-3 Spaces Plan Title Block Table 4-4 Spaces Plan - Optional Attributes Table 4-5 Spaces Plan - Defence Attributes Table 4-6 Spaces Floor Plan XData for Window Attributes Table 4-7 Spaces Floor Plan XData for Wall Attributes Table 5-1 Design and As-Constructed Title Block Requirements Table 5-2 Design and As-Constructed Title Block Optional Information Table 6-1 Scope of Data Collected using Engineering Detail Survey Table 7-1 Garrison Support Service Activities Table 7-2 Garrison Support Grounds Maintenance Grass Cuts Table 8-1 Communication Pit Data Table 8-2 Communications Conduit Data Table 8-3 Communication Cable Data Table 8-4 Communications Conduit Cable Link Data Table 9-1 Orthophoto Options for Resolution and Accuracy Table 9-2 Orthophoto Technical Specifications Table 9-3 Orthophoto Quality Assurance Plan Table 9-4 Aerial Photography Specific Metadata Requirements Table 10-1 Satellite Imagery Specific Metadata Requirements Table 14-1: Schedule 11 Hazardous Chemicals Workplace Site Map Presentation Guidelines Version viii 01 March 2015

9 Figures Figure 1-1 Master Site Plan Dataset - example data...2 Figure 1-2 Spaces Plan Dataset - example data...2 Figure 1-3 Specification Process Flow Diagram...6 Figure 2-1 Examples of Correct Topological Representation Figure 2-2 Examples of Correct Topological Representation Figure 2-3 Incorrect Topology - Unconnected line and point features Figure 2-4 Correct Topology - Connected line and point features Figure 3-1 Master Site Plan Dataset - example data Figure 4-1 Spaces Plan Dataset - example data Figure 8-1 Communication Pit Labels Figure 8-2 Communication Conduit Labels Figure 8-3 Communication Cable Labels Figure 14-1: Example Workplace Site Map Appendices Appendix A Glossary A-1 Appendix B References B-1 Appendix C Contaminated Sites Data Standards C-1 Appendix D Metadata Specification D-1 Appendix E Directory Structure E-1 Appendix F Scale and Accuracy F-1 Appendix G Master Site Plan AutoCAD Standards G-1 Appendix H Space Plan Data Standards H-1 Appendix I Garrison Support Services AutoCAD Standards I-1 Appendix J Master Planning CAD Standards J-1 Appendix K Environmental Data Model K-1 Appendix L Space Plan Labelling Standards L-1 Appendix M Hazards Spatial Data Standards M-1 Version ix 01 March 2015

10 VERSION HISTORY Version Number Date Amendment Comment Released By 1.0 Feb 06 Draft Oct 06 Published May 07 Draft Feb 08 Published Aug 08 Published Dec 11 Draft Mar 15 Draft Baseline version for release Includes name change from CSIG to DSG Updated SDMP Section 5 Spatial Metadata Specifications v4.4 of 8 May 07. Updated Section 1 Guiding Principles to numbered paragraphs and added a Table of Contents for the each SDMP section. The Section 1 version number acts as the overall version number for the entire SDMP. If any section is updated, Section 1 should also be updated. Updated SDMP Section 5 Spatial Metadata Specs v4.5, Section 6 Baseline Spatial Data Specifications v3.1 and Section 7 Spatial Data Specifications v3.1. Includes name change from DSG to DS. General restructure and revision of SDMP to improve currency, ease-ofuse and reduce ambiguity. Update of Section 12 and Appendix C. Addition of section 14 and appendix M for inclusion of Hazards Data John Ramsay DIIE John Ramsay DIIE John Ramsay DIIE Berceuse Bindle DIIE Berceuse Bindle DIIE Berceuse Bindle DSIM Rod Armstrong Version x 01 March 2015

11 Section 1 Introduction 1 INTRODUCTION 1.1 Purpose of SDMP The Defence Support and Reform Group (DSRG) Spatial Data Management Plan (SDMP) has been developed to provide standards and specifications for spatial data management and has been developed with reference to spatial standards both within Defence and the spatial industry The standards and specifications within the SDMP will improve data consistency and availability of information, and facilitate spatial information dissemination and sharing within DSRG. With its use, DSRG will achieve a standardised approach to spatial data management that will realise many benefits to both the organisation and its staff including: Consistent and more reliable data that will lead to more informed decision making; Closer integration with other DSRG information systems and Defence spatial data users; Portability of staff skills; and Greater interoperability with organisations outside of Defence The SDMP has been developed as an initiative of the Directorate of Strategic Information Management (at that time known as the Infrastructure Information Environment - IIE) and forms a component of the Strategic Information Management Directorate (SIM) architecture. The SDMP provides the Data Specification for all data stored and managed within the DSRG National Spatial Information Management System (NSIMS). All spatial data shall meet the SDMP Specification to allow data to be accessed within NSIMS and DSRG Enterprise Level Spatial Systems. Section 1 - Introduction 1.2 Spatial Data Definitions Spatial data is information that defines the geographic location and spatial dimension of natural or constructed features on Earth. Spatial data stores geographic locations as a series of points, lines, and polygons using coordinate systems and topology to record and inform the location of information. Spatial data can be mapped using Computer Aided Design (CAD) or Geographic Information Systems (GIS) software. Defence Support (DSRG) conducts business with the assistance of spatial data in many forms and for many different purposes DSRG relies on two Key or Foundation Spatial Datasets upon which other spatial data is developed and referenced. These Key Spatial Datasets types are - Master Site Plan Dataset Spaces Plan Dataset A Master Site Plan Dataset exists for all key Defence Properties and contains the locations of natural and man-made features such as buildings, road, runways, and services. This dataset is used to plan and design new infrastructure on properties, Version March 2015

12 Section 1 Introduction and is used as a basis for the capture of garrison support services data. A sample of data from a Master Site Plan Dataset is shown in Figure 1-1. Section 1 - Introduction Figure 1-1 Master Site Plan Dataset - example data A Spaces Plan Dataset or Floor Plan is created for all key Defence Buildings and is distinct from an architectural floor plan in that it only shows the size, shape layout and identification number of spaces and rooms within Defence Buildings, door openings, staircases and fittings. The data captured is used to assist in building management through the allotment of rooms, cleaning services, management of information technology assets and changes to buildings. A sample of data from a Spaces Plan Dataset is shown in Figure 1-2. Figure 1-2 Spaces Plan Dataset - example data Version March 2015

13 Section 1 Introduction Other common spatial data used by DSRG includes: Aerial photography and satellite imagery; Reference documentation including design and as-constructed plans of DSRG structures, assets and infrastructure, and associated reports; and Environmental data and information overlays including environmental monitoring, heritage, contaminated sites data, weed and fire mapping. 1.3 Intended Audience The SDMP is intended for use by those creating, using and managing spatial data within, and on behalf of, the Defence Support and Reform Group (DSRG) There are two key SDMP User Groups that are referred to within the SDMP, these are listed in Table 1-1. Section 1 - Introduction Table 1-1 SDMP User Groups SDMP User Group Data Users Data Managers Description of Group DSRG Project Officers, Directorate of Operations and Training Area Management personnel and Defence Contractors (Estate Maintenance and Operations Services (EMOS) and National Program Services (NPS) and National Project Delivery (NPD) contractors) that create, use and analyse spatial data. DSRG staff with a responsibility to manage spatial data to facilitate use of spatial data within their region or nationally. These include: Regional Information Officers (RIO); Regional Environmental Officers (REO); staff within the Directorate of Strategic Information Management (DSIM) and staff from the Estate Planning Branch, External Land Planning Directorate. 1.4 Structure of SDMP The SDMP contains two types of Standards: The General Data Specification (Section 2). (Section 3 onwards). The General Data Specification (Section 2) contains the Data Specification that applies to all spatial data. The General Specification prescribes the data formats, file naming conventions, metadata requirements, the approved datum and coordinate systems, measurement units, accuracy and other DSRG data standards. (Sections 3 onwards) contain a set of specifications for specific types of spatial datasets. The specifications for the two Version March 2015

14 Section 1 Introduction DSRG Key Spatial Datasets are detailed, and specifications for other types of Spatial Data. Appendices provide additional support to the SDMP. The appendices include the Spatial Data Management Specification, the full Metadata Specification and additional appendices to support the general data specification and specialised data specifications. Table 1-2 summarises the information held within each Section and Appendix. Table 1-2 SDMP Sections and Appendices SDMP Section Description of Contents Implementation Responsibility Section 1 - Introduction Section 1 Introduction: All Users Introduction to the SDMP, the scope of implementation and background information Section 2 General Data Specification All Users Applicable to all spatial data Specifications for specific types of spatial datasets Section 3 Master Site Plan Datasets All users working Section 4 Spaces Plan Datasets with data that falls Section 5 Reference Data within the scope of the Specification Section 6 Engineering Detail Survey for Infrastructure and Assets Section 7 Garrison Support Services Data Section 8 Communications Data Section 9 Aerial Photography Section 10 Satellite Imagery Section 11 Master Planning Datasets Section 12 Contaminated Sites Data Section 13 Environmental Data Section 14 Hazards Data Appendices Additional supporting information Appendix A Glossary For Information Purposes Only Appendix B References For Information Purposes Only Appendix C Contaminated Sites Data Standards All users working with data that falls within the scope of the Specification Appendix D Metadata Specification SDMP Technical Authority Appendix E Directory Structure All users Version March 2015

15 Section 1 Introduction Appendix F Scale and Accuracy For Information Purposes Only Appendix G Master Site Plan AutoCAD Standards All users working Appendix H Space Plan Standards with data that falls Appendix I Garrison Support Services AutoCAD Standards within the scope of the Specification Appendix J Master Planning CAD Standards Appendix K Environmental Data Model Appendix L Space Plan Labelling Standards Appendix M Hazards Spatial Data Standards Associated Documents A set of template datasets are provided as part of the SDMP to assist in the implementation of the SDMP specification. The templates are available on the Defence Estate Quality Management System (DEQMS) site and include example data that has been collected in accordance with the SDMP specifications. Section 1 - Introduction 1.5 Application of the SDMP The SDMP shall be applied by DSRG technical and business owners, spatial data managers and their representatives. This includes the Estate Planning Branch, External Land Planning Directorate and Defence Support Operations (DSO) services providers, Estate Maintenance and Operations Services (EMOS) and National Program Services (NPS) and National Project Delivery (NPD) contractors. All are responsible for the appropriate application of standards and the implementation of the SDMP requirement accordingly The SDMP specification process flow shall be applied as described below in Figure 1-3. Version March 2015

16 Section 1 Introduction Garrison Support Services Data Section 7 Communications Data Section 8 Aerial Photography Section 9 Satellite Imagery Section 10 Master Planning Datasets Section 11 Contaminated Sites Data Section 12 Environmental Data Section 13 Hazards Data Section 14 Section 1 - Introduction Figure 1-3 Specification Process Flow Diagram Version March 2015

17 Section 1 Introduction 1.6 SDMP Point of Contact General Note About Data: The DSRG spatial capability is currently going through a process of transition from file-based data formats to specifications for geodatabases. Through this transition the DSRG Spatial Data Technical Authority will act as the point of contact for questions relating to the SDMP, the data specifications within the SDMP and DSRG Spatial Data. Contact details for the DSRG Spatial Data Technical Authority are provided in Table 1-3. Table 1-3 Spatial Data Technical Authority Position Section: DSRG Spatial Data Technical Authority Manager Spatial Systems Department of Defence Defence Support Chief Operating Officer Division Strategic Planning and Performance Management Branch Directorate of Strategic Information Management Section 1 - Introduction Address: F3-GF-063, Fairbairn Park Offices, Fairbairn, ACT Telephone: Facsimile: Spatial Information Systems group mailbox [email protected] 1.7 Linkages with NSIMS The National Spatial Information Management System (NSIMS) is currently the DSRG repository for all DSRG Spatial Information and is supported by the SDMP. NSIMS is located within the Defence Restricted Network (DRN) and is access managed NSIMS includes the following components: A spatial dataset metadata catalogue for searching and locating spatial and aspatial data; A gazetteer for defining and performing searches on geographic extents of a named feature; A viewing tool that allows spatial datasets to be displayed; and A tool to allow datasets to be uploaded to, and downloaded from, the system All DSRG spatial data can be stored within NSIMS if the data meets the specifications of the SDMP. Version March 2015

18 Section 1 Introduction 1.8 DSRG Spatial Data Policy The principles of the DSRG Spatial Data Policy are described in and shall be adhered to by all DSRG spatial data users. Table 1-4 Principles of the DSRG Spatial Data Policy Principle Description User Responsibility Data Standards apply to all DSRG Spatial Data Information is a Defence Asset Security Adherence to Standards Interoperability Access Data from its Point of Truth The Standards and Specifications within the SDMP apply to DSRG Spatial Data. Specific standards apply to specific spatial datasets including the DSRG Key Spatial Datasets and other spatial data. Spatial Information shall be valued and protected as a key Defence asset. Management of spatial data shall include arrangements to preserve confidentiality, privacy, security and intellectual property rights which will protect the rights of data owners and appropriate sectors of the Defence stakeholder community. Data shall be collected, stored and disseminated according to Defence Standards and specifications. Data shall be gathered in a manner that is independent of specific vendor applications and readily integrated with other systems that adhere to this principle. Data shall be acquired from a point as close to its (the data s) source as possible. When considering the relevance and application of the SDMP specification, spatial data providers and managers should consider which section of the SDMP specification shall be applied to spatial datasets. Arrangements shall be in place to protect DSRG s information assets in the event of its complete or partial loss, or destruction. The provision of Defence information is permitted on a Needs to Know basis. Defence data shall not be provided to a third-party without direct approval and the implementation of a Data License. Data shall be managed in such a way that security is maintained at all times. The SDMP identifies the applicability and scope of minimum spatial data standards and shall be applied for DSRG Spatial Data. DSRG Contract Documents may identify additional specific requirements that shall be applied. To the extent practicable, all spatial data that is provided in reports, and designed and produced for Defence shall have the widest benefit to the broader DSRG business, and to existing data and information systems. All finalised spatial data should be stored within NSIMS to allow DSRG to access a single data source and minimise the requirement to obtain multiple versions of data from external sources. Section 1 - Introduction Version March 2015

19 Section 1 Introduction Principle Description User Responsibility Documented Data shall be Shared Data shall be Collected with Assured Integrity Authoritative Errors and Omissions Metadata documentation shall be collected and maintained. Proper documentation of spatial data will ensure data is stored and can be retrieved logically and appropriately in support of DSRG operations and decision making. Spatial information shall be made accessible and leveraged across the Defence Restricted Network (DRN) to enable improved decision making and minimise costs to Defence e.g. due to duplication. Data shall be openly available to all DRN users through the use of NSIMS to maximise the benefit of the data to the organisation as a whole. Data shall be entered only once into Defence systems. There shall be a single authoritative source for each data element. DRN users shall have access to valid, reliable, complete data they can use with confidence to support improved decision making. Errors or omissions found in any dataset shall be rectified prior to final delivery or reported as soon as practical to the DSRG business owner or NSIMS Custodian. The DSRG Metadata Entry Tool (MET) shall be used to create and edit metadata to provide documentation of spatial datasets. The MET can be downloaded from: gement/default.asp NSIMS shall be used to store and access spatial data to ensure that data is shared between DRN users. Data gathering initiatives shall avoid unnecessary duplication of effort, and the consequent risks of unnecessary expenditure and inconsistent data. NSIMS custodian and user roles shall be used to manage spatial data integrity within NSIMS. NSIMS shall be used to store and access spatial data to ensure that the most current and complete spatial data is available to DRN users. NSIMS validates spatial dataset against SDMP requirements prior to upload in NSIMS. DRN users should report errors, omissions and improvement actions via the NSIMS issue feedback link. Section 1 - Introduction 1.9 Future Changes to Spatial Data Management The SDMP is currently going through a process of staged revision with the implementation of the National Spatial Information Management System (NSIMS), the Garrison and Estate Management System (GEMS) Data Model and the transition from file-based data formats to specifications for Geodatabases. As part of this revision some of the SDMP data specifications will be revised to meet the requirements of the new systems and data formats. Contact the DSRG Spatial Data Version March 2015

20 Section 1 Introduction Technical Authority for further information regarding the revision schedule and implications for data capture projects Currently a Geodatabase Model is being designed for the Master Site Plan Dataset. It is anticipated that this will be implemented later in A Geodatabase Model for other DSRG Data will be implemented over time. Section 1 - Introduction Version March 2015

21 Section 2 General Data Specification Section 2 General Data Specification Section 2 General Data Specification Version March 2015

22 Section 2 General Data Specification 2 GENERAL DATA SPECIFICATION 2.1 Introduction This section defines the General Data Specification and standards for spatial data. Specific or additional requirements are provided within the Specialised Data Specifications in Sections 3 onwards. The Specialised Data Specification for the type of data being created or updated must be read in conjunction with the General Data Specification. See Table 2-1 for a list of the. Table 2-1 List of Section 3 Section 4 Section 5 Section 6 Section 7 Section 8 Section 9 Section 10 Section 11 Section 12 Section 13 Section 14 Master Site Plan Datasets Spaces Plan Datasets Reference Data Engineering Detail Survey for Infrastructure and Assets Garrison Support Services Data Communications Data Aerial Photography Satellite Imagery Master Planning Datasets Contaminated Sites Data Environmental Data Hazards Data Section 2 General Data Specification The SDMP shall be applied by DSRG technical and business owners, spatial data managers and their representatives. This includes Infrastructure Division (ID) and Defence Support Operations (DSO) services providers, Estate Maintenance and Operations Services (EMOS) and National Program Services (NPS) and National Project Delivery (NPD) contractors. All are responsible for the appropriate application of standards and the implementation of the SDMP requirement accordingly. 2.2 Data Format All DSRG spatial data shall meet the format requirements defined in Table 2-2. Version March 2015

23 Section 2 General Data Specification Table 2-2 DSRG Spatial Data Formats Information Type Preferred Format Extension Comments CAD (Computer Aided Design) Data AutoCAD Drawing file* DWG* Shall be compatible with AutoCAD Release 2007 GIS Data ESRI Shapefile SHP, SHX and DBF Digital Elevation Models Satellite Imagery /Scans Aerial Photography Georeferenced Images Geodatabase Band Interleaved by Line Band Sequential TIFF and GeoTIFF ArcGIS GRID ERDAS IMAGINE Comma separated value Encapsulated Compressed Wavelet TIFF and GeoTIFF JPEG* Band Interleaved by Line Band Sequential ERDAS IMAGINE oracle spatial SQL server SAP ESRI personal geodatabase BIL BSQ TIFF & TIF Standard contents of ArcGIS GRID directory IMG CSV or TXT ECW TIFF & TIF JPG* BIL BSQ IMG Shapefiles shall be supplied with the three basic file extensions as a minimum and content must comply with relevant SDMP specification requirements It is anticipated that database extracts would be provided by DSRG for amendment. JPG and TIF images shall be supplied with an associated world file containing image header information (.JFW or.tfw file) ECWs shall be supplied with an associated ERS file containing the image header information. JPG and TIF images shall be supplied with an associated world file containing image header information (.JFW or.tfw file) Satellite Imagery should preferably be in 16-bit (raw) or 8-bit (pan-sharpened) JPEG2000 is a valid format Section 2 General Data Specification Version March 2015

24 Section 2 General Data Specification Information Type Preferred Format Extension Comments Data Attribute Tables Packaged reference information documents Dbase IV Comma separated value MS Excel 97 (*.xls) Portable Document Format AutoCAD Design Web Format DBF CSV or TXT XLS PDF DWF These data formats shall only be provided in addition to other data deliverables (in formats listed above) * Data format endorsed by the Approved Technology Standards List (ATSL) as a Defence Standard. Section 2 General Data Specification Version March 2015

25 Section 2 General Data Specification 2.3 File Names File names shall succinctly summarise the data to allow users to quickly understand the content of the data. The file name should include the subject of the data and the data locality Spaces shall not be used in file names, underscores shall be used to separate text File naming conventions specific to particular types of data are covered with the Specialised Data Specification sections of the SDMP Specific file naming requirements for ESRI GIS Elevation Model Grid file format: the ESRI Grid file format stores data within a set of directories that can be easily confused with standard directory folders in Windows Explorer. Each ESRI Grid file shall be clearly named to identify the file as a Grid format, and shall provide a description of the file contents within the filename limit of 13 characters. The following filename format shall be adhered to: Format: [Short description of file contents]_grd Example: MBTAelev_grd (elevation grid for Mount Bundy Training Area) Section 2 General Data Specification 2.4 Directory Structures Directory structures used for spatial data deliverables shall be intuitive to users A recommended directory structure is defined within Appendix E and is available for download as a ready-defined structure from the following page on the DSRG Defence Estate Quality Management System (DEQMS) website Metadata Metadata is structured documentation that describes spatial data. Information stored within metadata includes the data currency, accuracy, method of capture, data author, and data quality Metadata allows data users to make an informed decision on the suitability of data for a given purpose, to understand how the data was captured and the currency of the data All DSRG data shall have a metadata record that accompanies the dataset. A valid metadata record is required to allow data to be loaded into the DSRG National Spatial Information Management System (NSIMS) Metadata shall be created and edited using the DSRG Metadata Entry Tool (MET). The MET allows users to create, view and edit metadata records within the defined metadata structure. Instructions on installation and use are provided on the DSRG Defence Estate Quality Management System website: Version March 2015

26 Section 2 General Data Specification The MET is a simple tool designed for non-specialist users to create metadata that meets the DSRG Metadata Specification. The tool provides an interface that leads a user through dialog steps and options to create a metadata record. Users do not need to be familiar with the full DSRG Metadata Specification (Appendix D) to create metadata that meets this specification The MET creates a metadata file with the same filename as the data but with an.xml file extension. This metadata file should remain in the same directory location as the dataset and shall always have the same filename as the data Keywords are used to improve efficiency in locating relevant information. A set of keywords has been developed to align to DSRG s business structure. Multiple sets of keywords can be assigned to a dataset to assist users in locating a dataset in the future Specific Metadata Requirements The following metadata requirements shall be stored in metadata records: Data capture methodology shall be specified in enough detail for the data capture to be repeated or for the methodology to be reviewed. Horizontal and vertical accuracy of captured data shall be recorded. Section 2 General Data Specification The full DSRG Metadata Specification is provided within Appendix D. The Metadata Specification is written for reference by the SDMP Technical Authority and Contractors designing Directorate of Strategic Information Management (DSIM) architectures. It is not expected that DSRG Data Users or DSRG Data Managers shall be familiar with the contents of the Metadata Specification. 2.6 Datums A datum is the reference point against which spatial position measurements are taken. Detailed information on datums can be found on the following website: Horizontal Datum A Horizontal datum is used to describe the position of a point on the Earth s surface in association with a Coordinate System Defence has adopted the World Geodetic System 1984 (WGS84) as the standard for all spatially referenced data created for DSRG Although WGS84 has been adopted across Defence to support Defence operations, DSRG recognises that industry partners who Version March 2015

27 Section 2 General Data Specification 2.7 Coordinate Systems support the Defence Estate only have access to GDA and as a consequence will accept the use of GDA94 for spatial data used to support the Defence Estate as specified in the Spatial Data Management Vertical Datum A Vertical datum is used to describe a position vertically as the elevation or depth of a point DSRG has adopted Australian Height Datum (AHD) as the standard vertical datum A coordinate system divides the Earth s surface using a set of coordinates to identify the position of a point DSRG has adopted the Geographic Coordinate System and the Map Grid of Australia (MGA) as the standard coordinate systems. MGA requires the use of the GDA94 datum. Section 2 General Data Specification DSRG will accept data in the MGA coordinate system where data is provided in a format that does not support the use of Geographic Coordinates. The metadata accompanying these data must clearly state the datum and coordinate system used Geographic Coordinate System The Geographic Coordinate System defines the locations of points on the surface of the Earth using Latitude and Longitude Latitude and longitude coordinates shall be recorded in the format Decimal Degrees and shall be recorded to a minimum of 5 decimal places (approximate equal to a precision of 1 m). Example: Lines of latitude are measured as an angle from the equator (0 ) to either Pole, 90 South and 90 North Lines of longitude intersect both the North and South poles. They are numbered using degrees beginning at the Royal Greenwich Observatory in England, which is designated as 0, and continue both East and West until they meet at Map Grid of Australia Map Grid of Australia is a projected coordinate system that defines the locations of points on the surface of the Earth by the measurement of metres from a point of origin. Version March 2015

28 Section 2 General Data Specification 2.8 Units of Measurement Units of measurement shall be recorded using metric standard scientific (SI) units. The units of measure shall be defined within the dataset attributes or metadata The unit of length measurement shall be metres unless specified within the Data Type Specifications in Sections 3 onwards In ongoing projects, the unit of measurement within the dataset attributes shall be kept consistent. 2.9 Spatial Accuracy Spatial accuracy measures how closely a position in a dataset is located to its true position on the Earth s surface Spatial data shall be captured at an accuracy that is appropriate for the data use. For example, Master Site Plans and Spaces Plans require a high spatial accuracy for use in asset and infrastructure management that is specified within the Data Type Specifications in Sections 3 onwards Where a spatial accuracy is not specified within the SDMP the DSRG Project Officer shall provide guidance on an appropriate level of accuracy. Section 2 General Data Specification Spatial accuracy shall be recorded in metadata records for all data capture and derived data products Global Positioning Systems (GPS) are used by DSRG in a variety of business purposes. The right type of GPS must be used to obtain data of a suitable accuracy for the business purpose for which it is being collected. Hand-held GPS cannot collect data at the accuracy required for the Master Site Plan Dataset. An Engineering Detail Survey using Survey Control Stations must be used for Master Site Plan Data collection. Differential GPS can be used for applications that require higher accuracy than a hand-held GPS, but don t require the accuracy of an Engineering Detail Survey Global Positioning System (GPS) receivers record accuracy (or precision) of the GPS reading as a Dilution of Precision (DOP) or Estimated Precision Error (EPE). These values can vary dependent on the satellite position and signal quality. Where an accuracy of <30m is required, these readings should be recorded with the attributes of the GPS positional data and stored against each record or in the metadata record Spatial Scale Scale is the ratio of the distance on a hardcopy map or electronic data viewer to the true distance on the ground (eg. 1:50,000). Data or maps with smaller scales (1:250,000) are less accurate and show less detail compared to data or maps at larger scales (1:25,000). Version March 2015

29 Section 2 General Data Specification The accuracy of a dataset or map is equal to ± ½ mm (0.0005m) at map scale. A scale accuracy table is provided in Appendix F. Example: 2.11 Data Capture ± m at 1:50,000 = ± 25m ± m at 1:10,000 = ± 5m Data products derived from other data sources shall be captured at a scale appropriate for the data use and where possible defined in Australian industry standards Data created from multiple data sources takes on the smallest dataset scale. For example if data is combined from 1:250,000 vegetation mapping and 1:100,000 vegetation mapping the resulting dataset will have a scale of 1:250, Data Viewing Software functionality enables users to zoom into a dataset and use or print information at very large scales. Caution shall be taken when using data beyond the scale at which it was collected as the accuracy of the data remains the same (see accuracies defined in Appendix F). Section 2 General Data Specification 2.13 Spatial Integrity of Features - Topology All data captured or provided for DSRG shall be topologically clean and free of errors. Data shall be corrected for overshoots and undershoots, polygons shall be closed, and slivers removed. Figure 2-1 and Figure 2-2 provide examples on how correct topology shall be applied Topologically clean data allows users to link attributes to features more accurately and to undertake various types of spatial analysis within a Geographical Information System. For example, analysis can be undertaken to calculate the area or parameter of a feature automatically, analyse proximity of features to other features, and automatically quantify change over time. Version March 2015

30 Section 2 General Data Specification Undershoot in feature Correct Representation Incorrect Representation Overshoot in feature Correct Representation Incorrect Representation Section 2 General Data Specification Pseudo-node in contiguous features Pseudo node Same feature with identical attribute values. Broken line in feature Correct Representation Incorrect Representation Figure 2-1 Examples of Correct Topological Representation Version March 2015

31 Section 2 General Data Specification Artefacts Correct Intersection Incorrect Intersection Incorrect Intersection Linear Feature Spike in Linear Feature Open Polygon Section 2 General Data Specification Slivers Incorrect Representation Correct Representation Figure 2-2 Examples of Correct Topological Representation 2.14 Spatial Integrity of Features Topology in a CAD Environment The following information will assist in maintaining topologically clean data in a CAD environment. Poly-lines (polygons) close their start and end points are the same; Line features join or snap together they share endpoints; Line feature vertices can also join with point features they share nodes; Point features provide the vertices for the connecting linework; and Text is associated with the appropriate polygon, line or point feature. The capturing/editing of the CAD line work will include: Snapping of line/poly-line nodes to appropriate point features; Version March 2015

32 Section 2 General Data Specification Breaking utility line work at appropriate point features, e.g. where a pipe/cable connects to above ground features; Not Breaking utility line work where it does not intersect, e.g. where pipes/cables are at different height levels; and Point/Symbol features are represented as a block. The following examples provide an overview of the requirements for producing topologically correct Master Site Plan data within a CAD environment. Section 2 General Data Specification Figure 2-3 Incorrect Topology - Unconnected line and point features Figure 2-3 shows CAD line features that intersect a point (symbol) feature but the line features do not meet at the node within the point feature. Figure 2-4 Correct Topology - Connected line and point features Version March 2015

33 Section 2 General Data Specification The correct topology (Figure 2-4) represents the line features intersecting a point feature by inserting a new vertex to the line and snapping it to the insertion point of the point feature. It is assumed that the line feature should be split at the point feature and that the relevant end points of the lines should be at the point feature Data Attributes Data attributes store descriptive information about particular spatial features within a dataset. Data attributes can include descriptions, dates of capture or update, area, position coordinates, the value of a measurement taken at the location, or a classification or category Data attributes are described within the SDMP Detailed Data Specifications within Section 3 onwards for specific types of data Where no Specification exists for a data type or where additional attributes are required, the additional attributes shall be reviewed to confirm that there is a clear business requirement. Attributes shall be intuitive to users and shall be allocated intuitive attribute names. Attributes codes and classifications shall follow established industry standards where possible. A description of the business requirements for the information, the attributes and attribute classifications shall be provided within the associated metadata record for the data. If data attributes are provided in an attribute table that is separate to the spatial data then a Unique Identifier shall be included in both the spatial data and the attribute table to enable the spatial features and attributes to be linked. Section 2 General Data Specification 2.16 Imagery Management Image Tiling Digital ortho imagery and LiDAR data are generally tiled (divided into smaller images) to manage file size It is recommended that the tiling process is undertaken by the data provider. It is also recommended that the data is delivered in both an uncompressed and compressed format The recommended tile size to the pixel resolution or Ground Sample Distance (GSD) is detailed in Table 2-3, in all cases the uncompressed file size should be under 300Mb. Table 2-3 Recommended Tile Sizes Pixel resolution (GSD) (m) Tile size (km) x x x x A tile layout dataset or diagram shall be supplied. It is recommended that a layout is provided in GIS format to allow it to be overlaid with the tiled images. Version March 2015

34 Section 2 General Data Specification It is recommended that for most users images are used in compressed formats. Imagery files in excess of 300mb on standard PCs will result in slow display rates. There are numerous proprietary software programs available that can be used to tile or compress data. These include ERDAS Imagine and ERmapper Digital imagery file size can be reduced by applying a compression algorithm. The compression ratio can be varied, however the greater the compression the more the quality of the image will be degraded. There are lossless image compressions algorithms available, but the amount of compression is limited. In most cases it is recommended that files are compressed to no more than a 10:1 ratio Tile File Names The naming convention for tiles cut from a large data is generally based on the co-ordinates values of the lower left corner of the tile. This can be amended, as required, for smaller tiles. EXAMPLE: Lower left corner: E N Tile Name: If appropriate additional information can be added to the tile name e.g. M where: Section 2 General Data Specification M=MGA 6=Zone =Easting 6230=Northing 1=0.1m resolution 01=January 10= Tile metadata should record the following information in addition to DSRG Standard Metadata requirements: Release version; Area of tile; Date flown; Camera/sensor type; Photo scale; Image Resolution; and Digital Elevation Model (DEM) details (if relevant). Version March 2015

35 Section 2 General Data Specification 2.17 Hardcopy Archival Where electronic documents do not exist and hardcopy files are to be scanned for archival, the following requirements shall apply unless otherwise specified in the Statement of Work: The plans shall be scanned at a minimum of 200dpi; Raster images shall be saved as compressed tiff images (LZW compression); Any colour plans shall be scanned as 24 bit jpeg images; Images shall be cropped to minimum plan extents; Images shall be rotated where necessary; Skewed images shall be de-skewed (original dyelines may not be straight); and Poor quality originals shall be enhanced (de-speckled and/or sharpened) Vectorisation of Information Vectorisation of hardcopy information and/or electronic images has been undertaken by Defence in the past to capture vector features relating to Defence Properties. Vectorisation of information is not recommended due to the low return on the financial investment and should only be undertaken for a specific business purpose where the financial value of undertaking the work is greater than the cost of vectorisation. Section 2 General Data Specification Version March 2015

36 Section 3 Master Site Plan Dataset Section 3 Master Site Plan Dataset Version March 2015

37 Section 3 Master Site Plan Dataset SPECIALISED DATA SPECIFICATION have been created to document standards for specific types of spatial data that have requirements that may differ from, or be additional, to the General Data Specification in Section 2. The provide more detailed information relating to the requirements for specific types of data and how the specification should be implemented. The contained within the SDMP are listed below: 3 Master Site Plan Datasets 29 4 Spaces Plans 34 5 Reference Data 47 6 Engineering Detail Survey for Infrastructure and Assets 51 7 Garrison Support Services Data 56 8 Communications Data 61 9 Aerial Photography 69 Section 3 Master Site Plan Dataset 10 Satellite Imagery Master Planning Datasets Contaminated Sites Data Environmental Data Harzards Data 94 Version March 2015

38 Section 3 Master Site Plan Dataset Section 3 Master Site Plan Dataset Section 3 Master Site Plan Dataset Version March 2015

39 Section 3 Master Site Plan Dataset 3 MASTER SITE PLAN DATASETS 3.1 Scope of Specification The specification covers the capture and update of the Master Site Plan Dataset that DSRG collects for Defence Properties. The Master Site Plan Dataset stores the position of infrastructure and asset features as listed in Table 3-1 and is a DSRG Key (or Foundation) Spatial Dataset upon which other spatial data is developed and referenced. This specification will be used when a Major or Minor Work or Activity Request has been issued to update a Master Site Plan Dataset. Table 3-1 Scope of Master Site Plan Data Feature Descriptions Air Conditioning Services Airport Infrastructure Compressed Air Services Communications Networks Stormwater Drainage Electricity Services Fire Services Fuel Services Gas Services Oxygen Services Property Features Road Features Security Services Sewerage Services Steam Services Structures Survey Features Topographic Features Traffic Features Vegetation Water Features Water Reticulation Section 3 Master Site Plan Dataset This dataset is used to manage and maintain existing infrastructure, to plan and design new infrastructure on properties, and as a basis for the capture of garrison support services data. A sample of data from a Master Site Plan Dataset is shown in Figure 3-1. Figure 3-1 Master Site Plan Dataset - example data Version March 2015

40 Section 3 Master Site Plan Dataset The Master Site Plan data is collated from as-constructed design drawings or through Engineering Detail Survey and is accurate to ±0.05 m. A high level of accuracy is required for this data to be used as a base for the design of new infrastructure or services on Defence Properties. To maintain the integrity of the data source the Master Site Plan Dataset must be updated to remain current and must be collected to the nominated accuracy. 3.2 Deliverables The following deliverables shall be provided: A dataset containing Master Site Plan data for all features that have been created or updated. A separate dataset shall be created for each Defence Property. Metadata record for each Master Site Plan Dataset. 3.3 Deliverable Templates A dataset template in AutoCAD and an AutoCAD file containing sample data is available on the Defence Estate Quality Management Systemat the following location: Section 3 Master Site Plan Dataset 3.4 Data Deliverable Specification Data Format Data shall be delivered in either: Data Accuracy AutoCAD Drawing format. A detailed data specification is documented in Appendix G respectively. It is recommended that the deliverable templates are used as the basis of creating Master Site Plan Data. An alternate GIS data format is currently being developed. Users wishing to utilise this data format should contact the DSRG Spatial Data Technical Authority The Master Site Plan Dataset shall have a horizontal and vertical accuracy of ±0.05 m Engineering Detail Survey Data Capture Requirements Detail survey shall include all significant infrastructure and asset features from the building line out Structures and buildings capture shall include the external walls of the building, the roofline and the height of the roofline shall be captured. Version March 2015

41 Section 3 Master Site Plan Dataset Kerbs capture shall include the kerb profile, top and lip levels at tangent points, changes of direction and grade, and changes in kerb type shall be captured. Maximum 25 m intervals on straights and large radius bends, and at nominal 5 m intervals on small radius bends Storm water and sewerage capture shall include manhole surface shape, perimeter levels and invert levels, and the size and direction of pipes shall be captured. Any change in direction of the pipes shall be recorded Underground Cables / Conduits capture shall include a single polyline which shall be used to delineate the location of the cables and shall include any change in direction Concrete lined drains and other surface drainage structures e.g. drop structures capture shall include detail survey at 25 m intervals for long runs Road furniture and line-marking capture shall include edge lines to define existing carriageway widths. Section 3 Master Site Plan Dataset Trees with a trunk diameter greater than 0.2 m shall be located and the type, trunk diameter and the spread defined. The diameter of the trunk shall be measured 1 m above natural surface level. Trees shall be represented to scale, with spot heights, diameter, species and height to be shown as text in the drawing Readily observed information regarding features and services shall be noted such as the size/diameter of culverts and lines between power poles. 3.5 Specific Data Requirements 3.6 Topology Specifications For Information Only Data must be captured so that it can be used within a GIS topological model of points, lines, and polygons that can then be linked to a database The SDMP specifications were initially designed to meet CAD software requirements where the data and information is designed to provide a detailed drawing providing a good picture (rendering) of the data. Although the data and information in a CAD file consist of symbols, points, lines, and poly-lines these elements are referred to as simple features and do not have any topology or link to a database A topologically structured GIS supports feature (object) relationships which enables the GIS to perform advanced analysis of the data such as determining the best route from point A to point B as is commonly performed by in-car navigation systems. Capturing data using the topology specifications will support the ability to Version March 2015

42 Section 3 Master Site Plan Dataset perform spatial analysis (network analysis) on connecting or adjacent features such as points, lines and polygons. 3.7 Topology Guidelines The following features shall be collected in accordance with the topology requirements defined within Section 2 of this document. Polygons: Buildings Linework: Storm Water/Drainage Sewage pipelines Water Supply pipelines Communication cables Electricity cables Gas pipeline Fuel pipelines Fire water pipelines Points related to: Storm Water/Drainage Sewage Water Supply Communications Electricity Gas Fuel Fire water infrastructure Text related to: Storm Water/Drainage Sewage Water Supply Communications Electricity Gas Fuel Fire water infrastructure Section 3 Master Site Plan Dataset Version March 2015

43 Section 4 Spaces Plan Dataset Section 4 Spaces Plan Dataset Section 4 Spaces Plan Dataset Version March 2015

44 Section 4 Spaces Plan Dataset 4 SPACES PLANS 4.1 Scope of Specification The specification outlines the convention DSRG has adopted for the capture of data for the Spaces Plan Dataset. The Spaces Plan Dataset, or Floor Plan Dataset, is created for all key Defence Buildings and is distinct from an architectural floor plan in that it only shows the size, shape layout and identification number of spaces and rooms within Defence Buildings, door openings, staircases and fittings. The Spaces Plan Dataset is a DSRG Key or Foundation Dataset upon which other DSRG data is based. This specification will be used when a Major or Minor Work or Activity Request has been issued to update a Spaces Plan Dataset Where an existing building has a numbering schema in place, that numbering should be adopted The data captured is used to assist building management through the allotment of rooms, management of information technology assets, cleaning services, and changes to buildings. A sample of data from a Spaces Plan Dataset is shown in Figure 4-1. Section 4 Spaces Plan Dataset Figure 4-1 Spaces Plan Dataset - example data The Spaces Plan Dataset is collated from as-constructed design drawings, or through measurement survey, and is accurate to ±0.05 m. This accuracy is required for this data to be used as a base for the design of new infrastructure or services on Defence Properties, and to provide data for future calculation to evaluate net return on assets. To maintain the integrity of the data source the Spaces Plan Dataset must be updated to remain current and must be collected to the nominated accuracy The Spaces Plan Dataset shall be updated, if any space or space number is changed, within 60 days of the change occurring Information stored within each Spaces Floor Plan Dataset includes fixed or static elements such as external and internal wall outlines, doorways, voids, core areas, wet areas, corridors, foyers, open spaces and undercrofts. The plans include columns, glazing and other openings (as a line or outline). A list of elements that Version March 2015

45 Section 4 Spaces Plan Dataset shall be included within the Spaces Floor Plan Datasets are detailed in Appendix H In most cases, spaces are areas within a Defence Structure that has a DEMS structure category of Building. Spaces data shall be collected for DEMS Building structure categories with a status that is not Disposed, Demolished, Mothballed or Under Construction A space is, in most cases, an enclosed physical area either internal or external to a building External spaces include external stairs, ramps directly attached to the building areas, and areas containing air conditioning equipment adjacent to a building. Verandas and areas with a roof are also included within the specification, but patios without a roof are not considered spaces in this context. 4.2 Deliverables A Spaces Plan shall be produced, and be distinct from architectural floor plans, for each building level. There shall be one floor plan per level. Section 4 Spaces Plan Dataset A metadata record for each data file Updates to space IDs or space types shall be recorded in relevant DEMS Remote Data Module (RDM) datasets Transmittal documentation containing the following information: Sender s details; Date of transmittal; Media type; and List of files including the filename and a summary of changes made to the file. 4.3 Deliverable Templates A file template containing all file settings and layer structures, and a file containing sample data is available on the Defence Estate Quality Management Systemat the following location: Version March 2015

46 Section 4 Spaces Plan Dataset 4.4 Required Inputs A Remote Data Module (RDM) is a database containing a subset of the data held in the DSRG DEMS relational database. The RDM contains the relevant space and level data for each building and shall be supplied by the DSRG Regional Information Officer. In the future this information may be stored within a different database and be updated using a different process The Space Plan Dataset for new buildings will be created using the template that can be downloaded from the Defence Estate Quality Management System Changes to existing buildings must be updated into the existing Space Plan Dataset for that building. The existing dataset is stored within NSIMS and shall be supplied by the DSRG Project Manager. 4.5 Data Deliverable Specification Data Format Spaces floor plans shall be delivered in AutoCAD Release 2006 format. Section 4 Spaces Plan Dataset File Names The following filename format shall be adhered to: Units of Measurement Spatial Accuracy Format: [DEMS Property Code]-[DEMS Site Code]-[DEMS Structure Code]-[DEMS Level Code].dwg Example: 0253-A dwg Data shall be captured in millimetres Data shall be produced to a horizontal accuracy of ±0.05 m. Version March 2015

47 Section 4 Spaces Plan Dataset 4.6 Specific Data Requirements Space Identification Wet areas and ablutions shall be considered one space unless a door creates a separate space Stairs and stairwells shall be considered a separate space except where they are part of a corridor or a low landing Where an area comprises workstations or work areas divided by removable or half height partitions there are two approaches that shall be specified within the Statement of Works and confirmed by the DSRG Regional Information Officer. The area shall be deemed as a single space (default option). Each workstation or work area will be deemed a space Fire Hose reels shall be considered an individual space when contained within an alcove or cupboard. Section 4 Spaces Plan Dataset Space Numbering Electrical switch/substation and communications areas shall be captured Existing space numbering conventions within a DSRG Region shall be adhered to unless otherwise directed by the DSRG Regional Information Officer The consistency of Space numbering is relied upon by many discrete business areas in Defence including: building maintenance; voice and IT services; and asset management. The space numbering standards must be implemented within projects Spaces within a building will be identified using the following format Format: [Building Number]-[Level ID]-[Space ID] Example: The Level ID shall be consistent with those used in DEMS as displayed in Table 4-1. Where level codes have been previously entered into DEMS in a non-standard format, (ie GND instead of GF), the local Regional Information Officer should be notified and discussions held to determine the most appropriate format for the collection of the spaces data. If a non-standard format is adopted, Version March 2015

48 Section 4 Spaces Plan Dataset the reasons why non-standard formats were adopted should be described in the metadata file. Table 4-1 DEMS Structure Level Codes Level Code S01 Sub Level 1 S02 Sub Level 2 BM GF Basement Level Ground Floor Description M00 Mezzanine Level 0 01 Level 1 M01 Mezzanine Level 1 02 Level 2 M02 Mezzanine Level 2 03 Level 3 RF Roof Section 4 Spaces Plan Dataset The Space ID shall comprise three numerical characters (e.g. 009). External spaces will be preceded with an X. For example, X001 denotes external space No Space numbering shall commence from the first space encountered from the main entry point of the building and continue in a clockwise and inward direction. This convention shall apply to all levels of multi-level buildings with numbering restarting from 001 on subsequent floors It is important to recognise the impact of space numbering during the design process, the application of space identification, and the number for door and window schedules. For example, where the Defence property, site or building codes are not yet available a substitute constant can be used to prefix the numbered spaces. Once as-constructed documentation is completed the Spaces Plan Dataset can more easily be generated with actual Defence codes without renumbering the spaces. In this way maintenance reference in building manuals can be easily interpreted against design documentation, as constructed and final spaces plans. EXAMPLE: Substitute building code AB is used. Space Ids become AB , AB , AB At handover the actual building code is assigned (088) and all Space Ids are amended to substitute AB to 088. Version March 2015

49 Section 4 Spaces Plan Dataset Renumbering Spaces Associated With New Works Space Labelling Where an existing space is split into 2 spaces, those new spaces should be renamed using the existing space number plus consecutive letters of the alphabet. EXAMPLE: Space 50 becomes spaces 50a and 50b Space labelling shall be undertaken for all office accommodation. All other spaces shall be labelled unless directed otherwise by the DSRG Project Manager The requirements for space labelling are detailed within Appendix L Spaces Floor Plan Data Capture Section 4 Spaces Plan Dataset Spaces floor plans are to be expressed as simple, to-scale, diagrams with detail kept to a minimum Drawing elements shall include external and internal wall outlines, doorways, voids, core areas (including lifts and stairways), wet areas (simplistically identified), corridors, foyers, open spaces and undercroft areas. The floor plans shall include columns, glazing and other openings (as a line or outline) Higher detailed fittings such as workstations, toilets, urinals, basins, sinks, showers and baths may be requested within the Statement of Works for illustrative purposes but shall be provided as an Xreference to the Space Plan on an appropriate layer, using a set of standardised blocks All floor plans must form closed polygons Floor outlines shall be coincident between levels The floor plan shall record the level ID and the Space ID Space Floor Plan Datasets for new buildings shall be compiled from as-constructed architectural design plans Spaces floor plan data for existing buildings may be obtained from the following sources: Field Capture Field measurement using appropriate electronic measuring equipment and an audit of each Space. Field capture shall include the following requirements: Version March 2015

50 Section 4 Spaces Plan Dataset Measurement of external/internal wall thickness, offset external wall, change layer to internal wall; Measurement of the hallway, main rooms, then all rooms off the hallways and main rooms; Doors shall be measured from the door jam and the correct opening direction shown. The hook point of the door shall be the corner of the wall (not the centre of the wall); Only features that are permanently part of the building shall be collected. No furniture such as tables, workstations or bookshelves shall be captured unless specified within the Statement of Works. Electronic CAD files - Existing CAD files may be available from various sources. These could consist of various forms, quality, structure and versions. Hardcopy or Scanned Raster Images If no other information is available hardcopy information can be used as a basis to assist in drafting plans that meet the Data Specification. These shall be used with caution as they may not be to scale Where existing spaces floor plan information exists, data verification shall be undertaken using a Field Audit. The Field Audit shall confirm that the information is correct, to scale, and that attribute information including space IDs and areas are correct. Where the existing spaces floor plan differs greatly from the supplied plan, the existing drawing shall be discarded and a new drawing prepared from new measurements. Minor incorrect measurements that fall within the required accuracy are acceptable for existing data. Section 4 Spaces Plan Dataset Area Calculations As Defence has not adopted an agreed method of measurement (such as BOMA) thus the following broad methods are outlined for their purpose It is preferred that gross external area, actual area and available area shall be calculated. (Calculation of office space nominal area is optional and if required shall be specified in the Statement of Work). Please refer to Table 4-2 for further information. Gross External Area Required for estate value and management calculations. The gross external area is the total external area of the structure. It is the footprint of the structure and the maximum area covered by the floor spaces. Actual Area Required for management and maintenance for office accommodation that is not open plan. The actual area is the area of all spaces from the outline formed from the inside of each wall and not including the wall thickness. Version March 2015

51 Section 4 Spaces Plan Dataset Available Area Required for office space management. The available area is the total available office accommodation area available for workspace accommodation. It is calculated for the whole level or floor (rather than for individual spaces), from the outline formed from the inside of external walls and around areas not-available for workspace, it does not include the wall thickness. The available area ignores partitions that are temporary in nature but takes into account structural, permanent features. Areas that are not available for workspace areas include halls, stairs, lifts, toilets, communication rooms, kitchens, porches, balconies and some store rooms. Nominal Area of office space (Optional) Required for bulk office space planning and management (office accommodation buildings only). Nominal area is area designated for office accommodation types (e.g. EL2 Office, Resource Room, standard workspace etc.), it describes the area of individual workpoints within a space. Nominal areas are recorded as the presence of each type of workpoint within the Spaces Plan Dataset. Defence has a defined nominal area for each type of workpoint category (Defence Accommodation Guidelines). Section 4 Spaces Plan Dataset Table 4-2 Office Space Area Calculations Structure Type Gross External Area Actual Area Available Area Nominal Area General structures Office Accommodation Static spaces with Office Accommodation Yes Yes Yes Yes Available area summarised for each floor Yes Yes Location of each workpoint added to Spaces Plan. Nominal area summarised for each floor A Statement of Work may require the documentation of existing or planned office accommodation usage. Within office accommodation Nominal areas will apply to available office accommodation areas and Actual area will apply for all other static spaces. Area tallies will summarise Nominal and Actual separately. Version March 2015

52 Section 4 Spaces Plan Dataset Floor Plan Presentation Floor Plans shall be drawn at 1:1 scale with coordinate 0,0 at the bottom left of the drawing Data shall be drawn square to the AutoCAD World UCS and displayed at Drawing Extents All floor plans for an individual structure shall be vertically registered to allow floor plans to be overlain with each other if required All floor plan data shall be assigned to the correct layer structure listed in Appendix H. No other information shall be included in the floor plan Drawing borders shall be placed in Paperspace and on Layer DRGSHT. Section 4 Spaces Plan Dataset A simple scale bar shall be placed with its left hand end at coordinate 0,0 in Model Space The drawing title shall be placed within an AutoCAD Block at the bottom left hand corner of the drawing centred above the scale bar. The drawing block attributes are listed in Table 4-3. The only visible attribute shall be the floor name. Table 4-3 Spaces Plan Title Block Attribute Example Comments FLOOR_NAME 0429/A026-GF The drawing title shall reflect the file name of the drawing. This shall be the only visible attribute. AREA_AVAILABLE Annotation text style shall be Arial font and shall be a legible size when floor plans are printed at A3. All text shall be stored within the AR_TEXT Layer Space IDs shall be displayed on the plan as text centred on the Space, and shall be stored in the appropriate layer. The actual area shall be shown if requested within the Statement of Works Fire Hose reels shall be labelled with the text FH in the AR_TEXT layer. Version March 2015

53 Section 4 Spaces Plan Dataset Descriptions of miscellaneous features including counters or display cabinets shall be placed in the AR_TEXT layer Remote Data Module (RDM) Update A Remote Data Module (RDM) is a database containing a subset of the data held in the DSRG DEMS relational database. The RDM contains the relevant space and level data for each building and shall be supplied by the DSRG Regional Information Officer. In the future this information may be stored within a different database and be updated using a different process The following information shall be assigned to each space in the RDM: Actual Area or Nominal Area (for workstations) Space Room Standard Floor Finish (where required by Statement of Works) Section 4 Spaces Plan Dataset The Space Room Standard and Floor Finish shall be selected from a drop down list within the RDM. The full list of options is provided within Appendix H Optional Data Capture Additional Space Attributes If specified in the Statement of Work, the attributes in Table 4-4 shall be populated within the SP_ATTRIBUTE layer for each Space and shall be defined in an AutoCAD block Visibility of attributes on drawings should be discussed with the DSRG Project Manager prior to commencement. Table 4-4 Spaces Plan - Optional Attributes Attribute Example Comments DEMS 0249/A026-GF-01 The full DEMS Space code SPACE 001 Always visible TYPE Store Refer to full list in Appendix H AREA ACTUAL 10.6 AREA NOMINAL 6.0 FLOOR FINISH Carpet Refer to full list in Appendix H The attributes in Table 4-5 shall to be populated as directed by Defence Project Manager. Version March 2015

54 Section 4 Spaces Plan Dataset Table 4-5 Spaces Plan - Defence Attributes DIVISION BRANCH GROUP UNIT/SECTION VACANT/OCCUPIED SPARE Optional Data Capture - Garrison Support Services If required, the capture of specific information for Garrison Support purposes shall be specifically included in the Statement of Work. This information shall not be collected unless specifically requested. Section 4 Spaces Plan Dataset Floor Finishes Windows A floor finish which describes the type of floor covering shall be assigned to each space. A list of floor finishes is provided within Appendix H Within the Remote Data Module (RDM) floor finishes shall be assigned to the space data Within the Spaces Floor Plan floor finishes shall be identified on a per floor/or per space basis (as applicable) and shall be represented in such a way that area measurements may be readily determined/ extracted such as a closed polyline or polygon Within the Spaces Floor Plan a window shall be represented as a polyline of the correct window width. Window height attributes: the height of the window; and the height of the base of the window above floor level, shall be assigned to the polyline Window attribute data shall be stored using AutoCAD Extended entity data (XData) defined in Table 4-6. Version March 2015

55 Section 4 Spaces Plan Dataset Table 4-6 Spaces Floor Plan XData for Window Attributes Registered Application Name Code 1040 Code Wall Heights WINDOW_XDATA Real Number, eg 1470, being the height of the window top in millimetres above its sill. Real Number eg 1470, being the height of the window still in millimetres above floor level Within the Spaces Floor Plan wall height shall be assigned to the polyline representing the wall. Section 4 Spaces Plan Dataset Wall attribute data shall be stored using AutoCAD Extended entity data (XData) defined in Table 4-7. Table 4-7 Spaces Floor Plan XData for Wall Attributes Registered Application Name Code 1040 WALL_XDATA Real Number, eg 2440, being the height of the wall in millimetres above floor level Version March 2015

56 Section 5 Reference Data Section 5 Reference Data Section 5 Reference Data Version March 2015

57 Section 5 Reference Data 5 REFERENCE DATA 5.1 Scope of Specification This specification will be used when a Major or Minor Work or Activity Request has been issued to design new infrastructure or make changes to existing infrastructure The specification covers all reports, building operational manuals, as-constructed documents, defect liability, equipment manuals, and design manuals. This specification also covers as-constructed Computer Aided Design (CAD) data relating to Defence Properties including the following: Architectural plans (Design, etc.); Engineering plans (Structural, Civil, Communications, Electrical, Hydraulic, Mechanical etc.); Landscaping; and Demolition plans These documents are required for reference purposes and it is not expected that all Section 2 General Specification requirements will be applied to the data. Please refer to the following specification for details of which standards do apply. Section 5 Reference Data 5.2 Deliverables The design and as-constructed documentation Reports, building operational manuals, as-constructed documentation, defect liability, and equipment manuals Metadata record for each data file. 5.3 Deliverable Specification General Reference Documentation The specification details requirements in addition to those detailed in the Section 2 Data Specification File Names Directory Structure Metadata Accepted industry standards shall be applied Accepted industry standards shall be applied A metadata record is required for each document. Version March 2015

58 Section 5 Reference Data 5.4 Deliverable Specification Design Drawings The specification details requirements in addition to those detailed in the Section 2 Data Specification Data Format File Names Directory Structure Accepted industry standards shall be applied to as-constructed documentation of data Accepted industry standards shall be applied Unless otherwise specified in the Statement of Work, drawings are to be provided within the following Directory Structure: Section 5 Reference Data Format: [PropertyName]\[ProjectName]\[Discipline]\ PropertyName is the name of the relevant property as per the DEMS Property Code. ProjectName is the Project Title, Facility Name, Asset Name or Building Use. Discipline is the drawing type. (Architectural, Civil, Electrical, Mechanical etc). Example: Datums, Coordinate Systems, Spatial Accuracy and Integrity of Features Drawing Details Design drawings are not required to meet the standards defined in Section 2 relating to datums, coordinate systems, accuracy and integrity of features The information in Table 5-1 is to be provided in the drawing title block. The information in Table 5-2 is optional. Version March 2015

59 Section 5 Reference Data TITLE Any information not shown on the title block may be supplied as a list or spreadsheet with the transmittal documentation. Table 5-1 Design and As-Constructed Title Block Requirements Element BASE NO PROJECT DISCIPLINE SCALE DATE Description Drawing title eg Detail and Level, Site Plan etc. Do not include the Project title, facility name, or the following punctuation symbols: semi-colons, colons, forward or backslash, fullstops. DEMS Property Code number for the Property/Site. Project Title, Facility Name, Asset Name or Building Use Architectural, Structural, Survey, Mechanical, Hydraulics, Electrical, As-constructed, Environmental etc. Plan scale (Plotted scale of plan) Date of plan Section 5 Reference Data Table 5-2 Design and As-Constructed Title Block Optional Information Element Description CONTRACTOR The Principal Contractor PLAN NO SIZE XREFs Defence Plan No or Contractors Plan No. Plan size (A0, B1 etc.) A list of attached plans All x-referenced drawings shall be bound to the parent file and the individual references shall be deleted All drawings are to be cleaned up (purged and audited) for archive purposes All referenced images are to be supplied with the drawing. Image references are to be relative (not full path) Where multiple drawings/sheets are stored in a single AutoCAD window, each separate drawing shall be saved in either.dwf or.pdf format, and supplied in addition to the original AutoCAD drawing. Version March 2015

60 Section 6 Engineering Detail Survey for Infrastructure Assets Section 6 Engineering Detail Survey for Infrastructure Assets Section 6 - Engineering Detail Survey for Infrastructure Assets Version March 2015

61 Section 6 Engineering Detail Survey for Infrastructure Assets 6 ENGINEERING DETAIL SURVEY FOR INFRASTRUCTURE AND ASSETS 6.1 Scope of Specification The specification covers the capture of infrastructure, asset and topographical features on Defence Properties using surveying techniques. Engineering detail survey is predominantly undertaken by DSRG to collect data of high spatial accuracy (±0.05 m) to create or update DSRG Master Site Plan dataset and in some cases condition appraisal information This specification will be used when a Major or Minor Work or Activity Request has been issued to undertake an engineering detail survey on a Defence Property Features captured using engineering detail survey are listed in Table 6-1. Table 6-1 Scope of Data Collected using Engineering Detail Survey Feature Descriptions Air Conditioning Services Airport Infrastructure Compressed Air Services Communications Networks Stormwater Drainage Electricity Services Fire Services Fuel Services Gas Services Oxygen Services Property Features 6.2 Deliverables Road Features Security Services Sewerage Services Steam Services Structures Survey Features Topographic Features Traffic Features Vegetation Water Features Water Reticulation Section 6 - Engineering Detail Survey for Infrastructure Assets The deliverables shall be defined in the specific survey brief. The following deliverables are likely to be included: A dataset containing collected features. This dataset shall meet the Specification for Master Site Plan Datasets (Section 3). A digital triangulated terrain model. A survey report stating methods applied, accuracy achieved, discrepancies and including Survey Control diagrams. A Metadata record for each data file. Hard copy survey plan(s) at a scale of 1:500 (as required). Version March 2015

62 Section 6 Engineering Detail Survey for Infrastructure Assets 6.3 Data Inputs The existing Master Site Plan Dataset shall be used as the basis to conduct and update surveys. The existing Master Site Plan Dataset shall be obtained from the relevant DSRG Regional Information Officer. 6.4 Deliverable Specification Data Format Accuracy Quality Assurance Digital data can be collected in either GIS or AutoCAD format compatible with the Section 2 Data Specification. AutoCAD files shall be both provided in both 2D and 3D All surveys shall have a horizontal and vertical accuracy of ±0.05 m The initial set up position for the As-Constructed survey shall be established using a minimum of 3 control points All As-Constructed detail data shall be reviewed by a senior surveyor. The surveyor shall certify completeness, and that accuracy standards detailed in these specifications are achieved The certification shall include a signed hardcopy plan of the As- Constructed data and a report detailing the Project number, methodology, discrepancies and new control marks. 6.5 Specific Data Requirements Survey Control Stations Section 6 - Engineering Detail Survey for Infrastructure Assets Survey Control Stations are physical marks in the ground which are used by surveyors as a reference location. A Survey Control Station has horizontal co-ordinates and a vertical height recorded against it Survey Control Stations, or Defence Facilities Reference Points (DFRP), stored with WGS-84 and or GDA94 compliant coordinates are available at most Defence Properties and shall be used as the co-ordinate origin for all survey work undertaken for and on behalf of DSRG. The location of DFRPs are available in a Survey Control Listing from the DSRG Regional Information Officer. Version March 2015

63 Section 6 Engineering Detail Survey for Infrastructure Assets Where suitable Survey Control Stations are not available in the area to be surveyed, or there is a possibility that an existing Survey Control Station may be disturbed/destroyed due to construction, a Survey Control Station shall be established by the surveyor to the following ICSM Standards Horizontal Control shall be established to Class B, equivalent to Order 2; and Vertical Control shall be established to Class LC, equivalent to Order L3 for differential levelling and Class C, equivalent to Order 3 for GPS heighting Survey Control Stations shall not be located on sandstone walls, tree trunks or other sensitive areas. Any paint used shall be a removable water based type. With placement of new Survey Control Station, the surveyor shall take into account the possibility of disturbance by mowers or other vehicular traffic New Survey Control Stations shall be listed on a Survey Control diagram that includes a locality sketch, the type of stabilisation, coordinates of the control and the Reduced Level (RL). The diagram shall be attached to the Survey Report. The existing Survey Control Listing held by the Regional Information Office shall be updated New Survey Control Stations shall be included in an update to the Master Site Plan Dataset Continuously Operating Reference Station (CORS) Networks A CORS is a network of global navigation satellite reference stations that will provide code range and carrier phase data to users. CORS are managed across Australian States and Territories by state government and private organisations. Section 6 - Engineering Detail Survey for Infrastructure Assets A CORS network within the vicinity of the Defence Property can be used to collect engineering detail survey Topographical Information Ground survey of the natural surface shall be undertaken to a vertical accuracy of ±0.05 m over the entire site The grid spacing shall be approximately 25 m. This spacing can be increased by the surveyor if warranted by the terrain, providing the accuracy limits are maintained and the changes of grade are surveyed. Version March 2015

64 Section 6 Engineering Detail Survey for Infrastructure Assets All topographical features shall be correctly strung to ensure accurate modelling. Section 6 - Engineering Detail Survey for Infrastructure Assets Version March 2015

65 Section 7 Garrison Support Services Data Section 7 Garrison Support Services Data Section 7 Garrison Support Services Data Version March 2015

66 Section 7 Garrison Support Services Data 7 GARRISON SUPPORT SERVICES DATA 7.1 Scope of Specification The specification covers the requirements for data depicting the physical location of Service Activities in the Garrison Support Services Contract The purpose of this specification is to standardise the collection of Garrison Support Service information and create a national standard for presentation of mapping in relation to Garrison Support Service contracts This specification will be used when a Major or Minor Work, or Activity Request, has been issued to undertake the creation or update of Garrison Support Services Data Garrison Support Service data is collected in the Service Activity categories described in Table 7-1. Table 7-1 Garrison Support Service Activities Service Category Hospitality & Catering Accommodation Management Access Control Laundry & dry Cleaning Services Cleaning Waste Management Grounds Maintenance Pest & Vermin Control Sport & Recreation Management Stores Management POL Services Transport Services Fire Fighting & Rescue Services Range & Training area Management Sub-Category Classified Commercial & Domestic Industrial, Hazardous & Clinical Organic Recyclables Sanitary Interceptor Pits Gardens & Grass Water Trees & Shrubs Other Section 7 Garrison Support Services Data 7.2 Status of Specification GENERAL NOTE: The Garrison Support Services Data Specification is scheduled for review. Please contact the DSRG Spatial Data Technical Authority to discuss the review schedule and the implications on Garrison Support Services data Version March 2015

67 Section 7 Garrison Support Services Data capture. The revision of the Garrison Support Services Data Specification will affect the data format and the presentation of data. 7.3 Deliverables The following deliverables shall be provided: A dataset containing Garrison Support Services data for all features that have been created or updated. A separate dataset shall be created for each Defence Property. Metadata record for each Garrison Support Services Dataset The data format should be chosen such that it is suitable for inclusion with tender documents, which means that the data must be readable with commonly available, de-facto standard, viewers on CD-ROM or DVD-ROM (care should be taken to ensure that these are readable by the Defence desktop PC Standard Operating Environment (SOE)). The data will include: A site map showing the location of each facility; Individual maps of each service activity for each facility; A browser type interface allowing simple navigation to the sites and access to these maps; and The maps must be able to be printed from the CD/DVD and interactively viewed If the data is delivered in AutoCAD format then it shall adhere to the standards provided in Appendix I of this specification. Section 7 Garrison Support Services Data Hardcopy For each facility, individual maps are to be produced for each Service Activity. Each map will have a legend for that service and show the Facility Name and Function, Property code, Scale & Date of production Maps may be produced of whole Properties or parts thereof depending on the extent of the Service and clarity of information; (ie Ranges/Training Areas may have individual maps for each facility or sites may be mapped for large Barracks), however a map showing the whole property is to be produced. Version March 2015

68 Section 7 Garrison Support Services Data 7.4 Deliverable Templates A set of template datasets are provided as part of the SDMP to assist in the implementation of the SDMP specification. The template for the existing Garrison Support Services Data Specification is available on the Defence Estate Quality Management System (DEQMS) site and includes example data that has been collected in accordance with the SDMP specifications Specific Data Requirements Grounds Maintenance Grassed areas to be shown by cut type. Table 7-2 Garrison Support Grounds Maintenance Grass Cuts Cut Type Manicure Cut Domestic Cut Rough Cut Slash Cut Brush Cutting Airfield Cut Grass Length Grass length shall not exceed 40mm and shall not be shorter than 20mm. Grass clippings removed. Grass length shall not exceed 70mm and shall not be shorter than 30mm Grass clippings removed. Grass length shall not exceed 150mm and shall not be shorter than 60mm. Grass clippings may be left scattered, not to be left in windrows, on the cut area but must be removed from any adjacent paved areas immediately upon completion of mowing Grass length shall not exceed 300mm and shall not be shorter than 150mm. Grass clippings may be left scattered, not to be left in windrows, on the cut area but must be removed from any adjacent paved areas immediately upon completion of mowing. Brush cutting is conducted to a standard similar to the designated cut for the adjacent area, in areas which are inaccessible to standard mowing equipment. As per CASA standard. Section 7 Garrison Support Services Data Separate total areas for each cut type are to be calculated and shown either on the face of the map for small sites or included in the legend for larger sites Explosives areas / Fuel Farms and Revetments are shown in addition to the Grass cut type Parade Grounds & Recreation areas are to be shown by surface type (Bitumen/Grass etc). Version March 2015

69 Section 7 Garrison Support Services Data Waste Management Services Cleaning Services Location of Bins is indicative and shows the scope of the service, not necessarily the exact location Where there are multiple bins at one location a single symbol with text showing the number may be used. Eg: Garbage Bins are to show the capacity in m Pathology waste shows the frequency of collection Weekly or Monthly The Service Cleaning is intended to show Buildings that require cleaning, however if the office area of a store or warehouse is the only part cleaned, the mapping should be indicative of the part to be cleaned. x6 Section 7 Garrison Support Services Data Version March 2015

70 Section 8 Communications Data Section 8 Communications Data Section 8 Communications Data Version March 2015

71 Section 8 Communications Data 8 COMMUNICATIONS DATA 8.1 Scope of Specification The specification encompasses all communications networks on Defence Properties outside the line of the building, excluding networks within buildings. The specification includes data relating to telephone, data, fire control and security networks This specification will be used when a Major or Minor Work or Activity Request has been issued to undertake the creation or update of communications data The communication data is used to amend and update existing spatial and textual databases, assist in maintenance and planning, and provide a permanent record of development Currently communication network data is stored in two formats. Over time these formats will change through the implementation of geodatabase data formats to store this information. Section 8 Communications Data A Communications Asset Database known as the Integrated Cable Management System (ICAMS) stores attributes relating to pits, cables and conduits. Data attributes relating to communication assets are collected through field work or from As-Constructed drawings and entered into the database. The DSRG Master Site Plan Dataset for each Property stores the location of Pits, Cables and Conduits. Communication features are captured through Field Survey techniques defined in Section 7 of the SDMP or from As-Constructed drawings. The features as added to the Master Site Plan Dataset for the Property as per the specifications provided in Section 3 of the SDMP. 8.2 Deliverables Updated Communications Database Updated Master Site Plan Dataset Photographs of pits Metadata record for each data file. 8.3 Deliverable Templates A file template containing all file settings and layer structures, and a file containing sample data is available on the Defence Estate Quality Management System (DEQMS) at the following location: Version March 2015

72 Section 8 Communications Data 8.4 Required Inputs DSRG Region Communications Database DSRG Master Site Plan Dataset 8.5 Specific Data Requirements Extended Entity Data (XData) The Integrated Cable Management System (ICAMS) is linked to Communications Conduits and Pits stored in the Master Site Plan Dataset using AutoCAD Extended Entity Data (XData). This is required to allow spatial query functions and thematic mapping of communications cable networks to be carried out. Extended Entity Data (XData) Specification for Communication Pits The XData shall be added to the Pit feature and the corresponding Pit Number text in the Master Site Plan. Section 8 Communications Data Registered Application Name: GFIScomms Code 1000, ASCII string: Compit Code 1000, ASCII string: [Pit No] (e.g. P0673) Extended Entity Data (XData) Specification for Conduits The XData shall be added to the Conduit feature in the Master Site Plan. 8.6 Field Capture Registered Application Name: GFIScomms Code 1000, ASCII string: Conduit Code 1000, ASCII string: [AutoCAD Entity Handle of Polyline] (e.g. 2B970) Location of the communications network (pits and conduits) shall be captured from either As-Constructed drawings or through using Field Survey techniques that comply with the current Survey Specification for Facility Detail. 8.7 Data Capture Communications Pits All communications pits shall be numbered and clearly labelled. The pit numbers shall be allocated by the appropriate Information and Communications Technology Liaison Officer or DSRG Regional Information Manager. Version March 2015

73 Section 8 Communications Data The labels shall be made of aluminium and engraved with the appropriate pit number using standard 5mm high number stamps. Pit labels shall display, as a minimum, the pit number, and where appropriate the from pit and the to pit (Figure 8-1). In the case where the conduit/cables are from or to multiple pits, the conduits within the pit will be labelled with from Pit and to Pit information (Figure 8-2) Pit labels shall be attached to the collars of pits with Ramset concrete nails. FROM PIT DATA/TELECOMMUNICATIONS CABLE ROUTE /PIT MARKER TO PIT Section 8 Communications Data PIT NUMBER Table 8-1 Communication Pit Data Figure 8-1 Communication Pit Labels Each pit number shall be prefixed by the letter P and sufficient characters allocated to allow all pit numbers to be the same length (e.g. P0001, P1000) Each pit shall be photographed and the image provided.tiff or.jpg format. The photographs shall be named with the pit number (e.g. Photograph of pit 1000 should be named 1000.jpg) A template shall be displayed within each photograph clearly showing the base number, date and pit number A complete condition appraisal shall be carried out and the communications pit information entered into the Communications Asset Database Compit Table (Table 8-1). Communications Asset Database Table Name: Compit Field Name Type Size Description PITID Long Integer Auto Number PIT_NO Text 255 Unique pit number Version March 2015

74 Section 8 Communications Data Communications Asset Database Table Name: Compit Field Name Type Size Description BaseNo Double Defence Property Code (from DEMS) PROJECT Text 50 Project name/number TYPE Text 100 Material type (conc, plastic) LID_MATERIAL Text 50 Lid Material (PVC, Metal, Concrete) SIZE Text 50 Size of pit LOCATION Text 100 Nearest building number or zone NO_LIDS Integer Number of lids PADLOCKS Integer Number of Padlocks KEY_NUMBER Text 50 Key number SECURITY Text 100 Security status (locked or unlocked) CONDITION Text 100 Condition of pit ACTION Text 255 Remedial action if any required COMMENTS Text 255 Comment CONDUITS Integer Number of conduits entering pit CABLES_info Text 50 Details of Number & Type of cables in pit DEPTH Double Depth of pit GFISx Double X co-ordinate of pit GFISy Double Y co-ordinate of pit GFISzoom Double GFIS zoom (default is 30) Last_Inspection Date/Time Date of inspection Acadent Text 50 AutoCAD entity handle of block in dwg file Section 8 Communications Data Conduits All conduits shall be clearly labelled. The conduit numbers shall be allocated by the DSRG Regional Information Manager Labels shall be made of Traffolyte (or another DSRG approved non-deteriorating material) displaying, as a minimum, the conduit number in black letters on a light (white or yellow) background (Figure 8-2). Figure 8-2 Communication Conduit Labels Version March 2015

75 Section 8 Communications Data The label shall be fixed to the communication pit wall in a secure manner (screws or liquid nails) in the vicinity of the conduit opening and positioned in such a manner that there is no ambiguity of conduit numbering The conduit number shall be a four-digit integer that contains preceding 0s (eg. 0001, 0010), where required the label will include the previous pit or next pit information (Figure 8-2) The conduit information shall be entered into the Communications Asset Database Conduit Table (Table 8-2) Adjacent conduits that run between pits or buildings shall be represented by a single polyline within the Master Site Plan. The AutoCAD entity handle for the polyline shall be added in the Conduit table fk_acadent field (see Table 8-2) for all the conduits represented by the polyline. The AutoCAD entity handle shall be attached to the polyline within the Master Site Plan using AutoCAD s Extended Entity Data in for format provided in Section Section 8 Communications Data Table 8-2 Communications Conduit Data Communications Asset Database Table Name: Conduit Name Type Size Description CONDUITID Long Integer Auto number CONDUIT Text 50 Unique conduit identifier BASENO Long Integer Defence Property Code (from DEMS) PROJECT Text 50 Project name/number TYPE Text 100 Material type SIZE Double Diameter of conduit FROM Text 50 Start Pit or building number TO Text 50 End Pit or building number CONDITION Text 100 Condition COMMENT Text 255 Comment OPENING Text 50 Type of opening (Bell mouth, cut-off) % FULL CAPACITY Double Estimate of % full SHIELD WIRE Text 3 Yes or No EARTH STAKE Text 3 Yes or No PULL ROPE Text 3 Yes or No DEPTH Double Depth in metres LENGTH Double Length in metres fk_acadent Text 50 AutoCAD entity handle of conduit in dwg file Version March 2015

76 Section 8 Communications Data Cables All cables shall be clearly labelled. The cable numbers shall be allocated by the DSRG Regional Information Manager The label shall be fixed to the cable in a secure manner, near the top of the pit if possible and positioned in such a manner that it is clearly visible when the pit is opened The method of labelling shall be permanent, durable and easy to identify. Labels should be made of Traffolyte (or another DSRG approved non-deteriorating material), with black letters on a white background fixed by cable ties at either end The cable number, from creation and to termination must be clearly printed on the label. Labels shall be placed on cables at start and end, and at every communications pit in between (Error! Reference source not found.). Section 8 Communications Data Figure 8-3 Communication Cable Labels The cable numbers shall be a three-digit integer containing proceeding 0s (eg. 001, 010) Where a cable splits a hierarchal numbering system shall be adopted. This will enable all cables to be traced from the origin to the termination point. The hierarchal numbering system shall follow the following convention: where cable 001 splits into two or more cables the new branches should be numbered , etc: where cable splits the new branches should be numbered , etc The cable information shall be entered into the Communications Asset Database Cable Table (Table 8-3). Table 8-3 Communication Cable Data Communications Asset Database Table Name: Cable Field Name Type Size Description CableID Long Integer Auto number Version March 2015

77 Section 8 Communications Data Communications Asset Database Table Name: Cable Field Name Type Size Description CABLE_NO Text 50 Unique cable identifier BASENO Long Integer Defence Property Code (from DEMS) PROJECT Text 50 Project name/number TYPE Text 50 Cable type (optic fibre/copper) SIZE Double Size (mm) or capacity (pairs/cores) COLOUR Text 50 Cable colour JOINT LOCATION Text 150 Location of joint (Pit No eg P1004) JOIN TYPE Text 100 Type of joint CREATED Text 100 Origin of cable (eg Bldg 1001) TERMINATES Text 100 Termination point (eg Bldg 1002) COMMENTS Text 255 Comments SECOND JOIN Text 100 Location of second joint (Pit No eg P1004) LENGTH Double Length of cable OWNER Text 50 Owner of cable (Defence, Telstra) CONDITION Text 50 Condition SECURE Yes/No Security status (secure network)( Yes, No) FROM CABINET Text 50 Cabinet No from (if applicable) TO CABINET Text 50 Cabinet No to from (if applicable) Section 8 Communications Data Conduit/Cable Linking Every conduit that a cable runs through shall be recorded within the Communications Asset Database. One entry shall be made for each conduit/cable combination The conduit cable link information shall be entered into the Communications Asset Database CondCableLink Table (Table 8-4). Table 8-4 Communications Conduit Cable Link Data Communications Asset Database Table Name: CondCableLink Name Type Description BaseNo Long Integer Defence Site Code (from DEMS) Conduit Long Integer Conduit number (ConduitID from Conduit table) Cable Long Integer Cable number (Cable ID from Cable table) Order Integer Sequence of conduit/cable section (optional) Version March 2015

78 Section 9 Aerial Photography Section 9 Aerial Photography Section 9 Aerial Photography Version March 2015

79 Section 9 Aerial Photography 9 AERIAL PHOTOGRAPHY 9.1 Scope of Specification This specification applies to the capture and post processing of aerial imagery over Defence Properties by DSRG Contractors using cameras and digital sensors mounted on aircraft The focus of these specifications is on the delivery of final products that meet DSRG s requirement for current and future use in the most cost effective manner. Within the foreseeable future, Aerial Photography Acquisition Programs are likely to involve one of a finite number of digital camera/sensor technologies. For this reason the imagery acquisition hardware/software technologies are not specified here. Instead, it is the responsibility of the contractor to meet the Deliverable Specifications using the most appropriate technology. 9.2 Deliverables The primary deliverable from aerial photography is digital imagery which should be supplied in TIFF and compressed ECW format. In the case of vertical photography the imagery must be ortho-rectified and other secondary deliverables may also be required (see Section 3.3). Section 9 Aerial Photography 9.3 Acquisition Requirements Platform Flight Planning Aircraft will be required to operate at altitudes from 1,200 feet to 25,000 feet above ground level and have a suitable altitude range for the project. In exceptional circumstances it may be required to fly at higher altitudes The Contractor will only deploy aircraft that are maintained in accordance with manufacturer s and statutory requirements and have current airworthiness certification. DSRG will also require written acknowledgement from the Contractor that all aircraft operations and clearances will be the responsibility of the Contractor and that they will be undertaken in accordance with Australian Air Safety Regulations It will be the responsibility of the Contractor to plan the photographic sortie to meet the requirements of the project and the specifications outlined in this document. This includes managing situations such as obtaining permission to enter property to survey ground control points, or to place a GPS ground station Approval to acquire imagery over Defence installations (especially Airfields) shall be gained prior to any imagery being flown. The Version March 2015

80 Section 9 Aerial Photography contact details for the respective approval authorities shall be provided to the contractor The contractor shall build a suitable lead time into the flying program to allow for the approvals Special Acquisition Requirements Camera When the photography is required for oblique or pictorial purposes only, optimum image quality will be sought. When the photography is required for ortho-rectification the imagery should be sourced using a calibrated metric camera/sensor system Vertical photography will be exposed using a large format metric camera or sensor. Details of any proposed metric camera to be used for the project must be submitted to DSRG for approval. For vertical photography the Contractor will provide a current calibration certificate from the manufacturer or an approved standardising laboratory for any sensor lens that will be used. Section 9 Aerial Photography Image Resolution Stereo Imagery Oblique photography may be exposed with smaller format, side mounted cameras where appropriate and acceptable to DSRG. Specific specifications for this type of camera may be contained in the project brief and are not contained in this document For vertical photography the image resolution (ground sample distance or GSD) and the area to be covered will be defined in the project brief. The Contractor will be required to demonstrate that the defined resolution is achievable All vertical aerial photography will be acquired as overlapping (stereo) frames or swaths For perspective centre cameras the required forward overlap between consecutive photographs in each flight strip will be 60% unless otherwise specified. The deviation range in forward overlap will not exceed +/- 5% The minimum lateral overlap shall be 25% unless otherwise specified. The deviation range in lateral overlap will not exceed +/- 5%. Version March 2015

81 Section 9 Aerial Photography Camera Attitude For push broom sensors the forward, nadir and back view angles will be required. The minimum lateral overlap shall be 30% unless otherwise specified Photography will not be undertaken when atmospheric conditions are likely to produce excessive tilts in the aerial photographs or deviation from flight paths Compensation is to be made for crabbing and drift by rotating the camera about the vertical axis such that the lateral edges of each frame are parallel to and not displaced laterally from the intended flight path by more than 5% of the specified side overlap Atmospheric Conditions No cloud or cloud shadow should obscure detail on any area being photographed. However, if the Contractor considers that conditions on the day of the flight will not improve once on site, contact will be made with DSRG to decide whether the photography is to be flown. Section 9 Aerial Photography Solar Altitude The photography will not be attempted when smoke, haze or any other conditions would impair the quality of the photographic image. However, if the Contractor believes conditions will not improve once on site it is critical that contact must be made with DSRG to decide the future of the project. Failure to consult with DSRG before proceeding with the photography under marginal conditions could lead to rejection of the materials captured Photography over open terrain with low relief will not be attempted when the solar altitude is less than 25 degrees, or less than 35 degrees over steep or timbered country Where water surfaces are extensive over the area being photographed, the solar altitude will be such that the sun s reflection does not appear in the photographs If a project cannot be completed in one sortie or on the same day every effort must be made to complete the outstanding runs at the first weather window of opportunity. If photography is being undertaken to complete a project or to re-fly rejected frames taken some days, (or weeks) earlier, careful consideration must be given to the time of day the adjacent runs were captured. The next additional new run or re-fly must be undertaken as close to the same time of day as possible. Version March 2015

82 Section 9 Aerial Photography Tidal Conditions Coverage Airborne DGPS Data For projects that include the capture of aerial photography over large coastal water bodies every effort must be made to complete the intertidal zone in one sortie. If it cannot be completed in one sortie then any appending runs must be flown at a similar tide height and sun angle if logistically possible. If only one parameter is possible the similar tide height is most critical Each run will extend outside the specified area by at least one stereoscopic pair, ie two principal points will fall outside of the specified area at the beginning and end of each run The first and last runs will have at least 15% of each photograph extending laterally outside of the boundaries of the specified area. Section 9 Aerial Photography The recording of airborne Differential Global Positioning System (DGPS) data for photo centres and photo metadata is part of the aerial photography acquisition requirements. The contractor is responsible for ensuring that this data is recorded for all vertical aerial photography The contractor is required to supply the photo metadata to DSRG within 7 days of the acquisition of the photography Image Quality and Colour Balance The contractor will be responsible for the supply of raw metric digital imagery to the same quality of Colour Balance and Consistency as the Benchmark imagery samples (where supplied by DSRG). DSRG understands that due to various climatic and seasonal conditions there will be some variations to the Benchmark Colour imagery. In this case sample images from the new photography, representative of the area, should be supplied to DSRG for acceptance DSRG may undertake random checks of the digital imagery supplied for colour balance and extraneous materials appearing on the scans plus other image degradation (such as steps or banding of scan lines). Results of this assessment will be made known to the contractor and if considered excessive remedial action by the contractor will be required. 9.4 Orthophoto Specifications Version March 2015

83 Section 9 Aerial Photography The focus of these orthophoto specifications is to ensure the final deliverables meet DSRG s requirements for current and future use in the most cost effective manner. For this reason the actual imagery acquisition hardware/software technologies and production methodology to be used are deliberately not specified. In the case of ortho-rectified imagery DSRG will determine the image resolution required for their project requirements. It will be the responsibility of the contractor to ensure that the specifications applicable to the specified resolution are met. 9.5 Orthophoto Deliverables Deliverables will often be limited to the supply of orthophoto (ortho-rectified image) tiles (ie the primary deliverable). In some cases DSRG may also require the supply of secondary deliverables. This is particularly the case when the raw stereo imagery and associated data sets are required for photogrammetric mapping Primary Deliverables The primary deliverables are 3 band (RGB) orthophoto tiles. In some instances there may be a requirement for 4 band (RGB & NIR) imagery. A metadata record for each data file Secondary Deliverables Section 9 Aerial Photography Raw (un-rectified) imagery as frames or swathes Ground control identification sketches and their surveyed coordinates (in terms of MGA/AHD) Aero-triangulation report/s Image support files (interior and exterior orientation data for each frame or image swathe) Digital elevation model (DEM) Key diagram in ESRI shapefile format DGPS camera centre air station coordinates (in term of MGA/AHD) Version March 2015

84 Section 9 Aerial Photography 9.6 Deliverable Specification Table 9-1 sets out the typical uses for orthophotos at various resolutions and lists their associated accuracy and tiling requirements. DSRG brief will indicate the appropriate resolution for each defined area. Table 9-2 defines the orthophoto technical specifications. Table 9-1 Orthophoto Options for Resolution and Accuracy Description/Use Very low level photography / Very detailed engineering and infrastructure design. Standard resolution for built environment / Facilities management Standard resolution for built environment / Facilities management Standard resolution for rural environment / Range management Standard resolution for rural environment / Range management Standard resolution for rural environment / Large range management Very high level photography / Regional area coverage Very high level photography / Regional area coverage Orthophoto Resolution (GSD) Table 9-2 Orthophoto Technical Specifications Spatial Accuracy (RMSE) Orthophoto tile size 5cm 15cm 500m x 500m 10cm 30cm 1km x 1km 15cm 45cm 1km x 1km 20cm 60cm 2km x 2km 25cm 75cm 2km x 2km 30cm 90cm 2km x 2km 40cm 120cm 5km x 5km 50cm 150cm 5km x 5km Section 9 Aerial Photography General Coverage Horizontal Datum Vertical Datum Map Projection Data Tiling Special Considerations Digital Elevation Model File Format Description DSRG will provide a full description to define the extent of the each area All survey values/airborne DGPS data will be supplied in terms of GDA94 and be directly tied in to the local published survey control network. All elevation data must be supplied as heights above/below Australian Height Datum (AHD) and be directly tied in to the local published survey control network. Ellipsoid heights must be reduced to AHD heights using AUSGeoid09 model. All ortho-rectified imagery must be supplied in terms of the Map Grid of Australia (MGA) coordinate system. All Primary data sets should be supplied in predefined tiles specified in Table 9-1 (tile layout to be based on the MGA coordinate system). DSRG will provide details of any special considerations applicable to the project. For example: All coastal data should be acquired at low tide (+/-2hrs) on any day. The digital elevation data used in the ortho-rectification process should be of sufficient accuracy to enable to the resulting orthophoto to meet the accuracy specifications detailed in Section bit GeoTIFF and compressed ECW Version March 2015

85 Section 9 Aerial Photography 9.7 Quality Assurance Documentation Prior to commencement of the aerial photography capture, a quality assurance plan shall be submitted to DSRG It is expected that the documentation will provide detailed information on systems to be used in the survey, operational information to be captured during the survey (eg. mission date, time, flight altitude, forward and side overlap), maps of survey coverage and boundary overlaps, flight plans and any other pertinent survey information. Table 9-3 Orthophoto Quality Assurance Plan QA Deliverables Quality Assurance Plan Pre-Survey Quality Assurance Deliverables Description The Contractor shall prepare and submit a Quality Assurance Plan. The plan must address the organisation and management of the project, work procedures, environmental considerations, safety and risk control and test procedures. The Quality Assurance Plan must detail the procedures to be used to verify that the deliverables meet the required specification. Approval to commence the aerial survey is contingent on DSRG s acceptance of the Quality Assurance Plan. Proposed aerial photography flight plan Section 9 Aerial Photography Version March 2015

86 Section 9 Aerial Photography 9.8 Specific Metadata Requirements A number of additional metadata requirements shall be recorded for all aerial photography. These requirements are listed in Table 9-4 with the name of the metadata element in which the information shall be recorded. These elements should be recorded in the metadata Lineage element. Table 9-4 Aerial Photography Specific Metadata Requirements Metadata Element Acquisition Start Date Acquisition End Date Sensor type Focal Length Flying Height (AGL) INS/IMU Used Number of Runs Number of Frames/Swathes Output Pixel Size Description of Aerotriangulation Process Used and Residual Results Description of Ortho-rectification Process Used Spatial Accuracy Horizontal Spatial Accuracy Vertical Limitations of the Data Section 9 Aerial Photography Version March 2015

87 Section 10 Satellite Imagery Section 10 Satellite Imagery Section 10 Satellite Imagery Version March 2015

88 Section 10 Satellite Imagery 10 SATELLITE IMAGERY 10.1 Scope of Specification Satellite imagery is collected from sensors mounted on orbiting satellites. The data collected by the satellites is transmitted to ground stations for processing. Satellite images often visually resemble an aerial photograph, but the image stores the amount of electro-magnetic radiation reflected and/or emitted by the Earth's surface. This information is used to perform data analysis DSRG uses satellite imagery in a wide range of analysis including: mapping and monitoring vegetation; estate planning; erosion or disturbance mapping; and change detection This specification provides guidance to DSRG staff on the acquisition of satellite imagery This specification will be used when a Major or Minor Work or Activity Request has been issued to undertake the acquisition of satellite imagery. Section 10 Satellite Imagery 10.2 Background Information The most commonly used commercially available satellite imagery for land management and monitoring are: ALOS Aster Digital Globe Earth Resource Observation Satellites (EROS) EO-1 GeoEye IKONOS Landsat TM and MSS (pre 1990) MODIS NOAA Rapid Eye RESOURCESAT-1 (IRS-P6) SPOT The selection of an imagery product is dependent on the requirements of the Statement of Work (SOW). A variety of these products are used within DSRG Spectral Resolution Spectral resolution relates to the number and width of spectral wavelength bands collected by satellite sensors. Different bands are useful for distinguishing different land cover types. Spectral Version March 2015

89 Section 10 Satellite Imagery Spatial Resolution resolution requirements shall be carefully considered when designing a satellite image analysis / remote sensing project The following satellite imagery is available: Multispectral Images are suitable for image analysis and remote sensing data analysis. Multispectral imagery can include data bands in the visible, near infrared and thermal infrared ranges with the pixel values representing a reflectance measure within each wavelength band of the sensor. Three Band or RGB Images are enhanced satellite images that have been contrast stretched, colour balanced and/or mosaiced so that they are suitable for use as a background image in CAD or GIS software. This data is suitable for image feature classification to extract extents of the manmade features such as buildings, roads, dams or even general extent of vegetation cover (although it is not recommended for land cover/land use classifications). This type of imagery is not recommended for remote sensing image analysis as the pixel values are modified and do not represent reflectance measures. Single Band Images (Panchromatic) These images often have high spatial resolution and can be used for image feature extraction. These images have limited applications on their own for remote sensing spectral analysis and should not be used for such purposes. Pan-Sharpened Images a merged product derived from both panchromatic and multispectral imagery, often from the same sensor. This produces high resolution colour (natural and/or false colour) images similar to the above and can be used for image feature extraction. These data should not be used as the basis of image analysis processing as the pixel values are modified and do not represent reflectance measures. Section 10 Satellite Imagery Spatial resolution is the area on the Earth s surface that is represented by an imagery pixel, spatial resolution affects the scale of mapping that can be obtained from imagery. Satellite imagery is available in a range of spatial resolutions, from 0.6m panchromatic imagery from Digital Globe to 30m multispectral imagery from Landsat TM. Example: Satellite imagery with a resolution of 25m is suitable for mapping at 1:50,000 or smaller. Version March 2015

90 Section 10 Satellite Imagery 10.3 Deliverables The digital imagery shall be delivered as specified in the Scope of Works A metadata record shall be produced for each data file Deliverable Specification The specification details any additional requirements in addition to those detailed in the Section 2 Data Specification Data Format File Names Data shall be provided in Encapsulated Compressed Wavelet (.ecw) format with an associated header file (.ers), OR in georeferenced tiff format with associated world file To provide consistency and facilitate data discovery the following filename format shall be adhered to: Section 10 Satellite Imagery Specific Metadata Requirements Format: [Short Property Name]_[Other relevant information]_[satellite Imagery Sensor]_[Data of Capture in YYYYMMDD format] Example: GardenIsland_NorthernSection_LandsatTM_ CultanaTA_DigitalGlobe_ A number of additional metadata requirements shall be recorded for all satellite imagery. These requirements are listed in Table 10-1 with the name of the metadata element in which the information shall be recorded. Table 10-1 Satellite Imagery Specific Metadata Requirements Requirements Number of rows in imagery Number of columns in imagery DSRG Metadata Element Data Quality Information > Lineage Data Quality Information > Lineage Cell (pixel) size: these must be square Resource Identification > Resolution > Sample Distance Sensor- platform, including version number (eg. SPOT5, LANDSAT TM7) Date of capture Data Quality Information > Lineage Extent Information > Temporal Extent Version March 2015

91 Section 10 Satellite Imagery Time of capture NADIR angle: angle of sensor Sun angle: sun angle at time of image capture Spectral bands: number and wavelengths Sensor resolution: may differ from image cell size due to resampling Image processing: detailed description of image processing undertaken including details on georeferencing, orthorectification (RMS errors, source data); resampling methods Extent Information > Temporal Extent Data Quality Information > Lineage Data Quality Information > Lineage Data Quality Information > Lineage Data Quality Information > Lineage Data Quality Information > Lineage Section 10 Satellite Imagery 10.5 Specific Data Requirements NADIR Angle NADIR angles shall be minimised and should be between 0 and 15 degrees. The NADIR angle is the pointing angle of the sensor at the time of capture relative to the area of land being sensed. A number of the satellites are programmable and can scan the earth at varying angles to increase the frequency of image capture. However, this can result in high NADIR angles and significant skewing of the imagery which can be detrimental to the product quality when mapping land cover Cloud Cloud cover shall be minimised and where possible products with 0%-10% cloud cover should be obtained. Satellite imagery is affected by cloud, haze and smoke (the exception being radar imagery) as well as the shadows produced, therefore minimising cloud present in the imagery is important. Cloudy or hazy conditions can affect the diffuse light penetration and reflectance (and hence the overall image quality) even if cloud or shadow is not present within the specific area of interest Sensor and Pre-Supply Processing Artefacts Banding, and line or pixel drop outs relating to a mal-functioning sensor and / or satellite communication can affect usability of imagery. Images with artefacts shall be rejected and must be resupplied with the capture of new or replacement imagery. Version March 2015

92 Section 10 Satellite Imagery Georeferencing Satellite imagery shall be orthorectified, particularly in areas of high relief. This shall be undertaken using the best available Digital Terrain Model (DTM) and ground control data. If this is not being undertaken by the satellite image provider then an ortho-ready product type, or unprocessed imagery should be specified. Satellite image providers pre-process imagery using standard models however, the accuracies of these models and the nature of the terrain in the area of interest should be considered before selecting this option. Where orthorectification is specified a Route Mean Square (RMS) error of less than one pixel is required Georeferencing using ground control coordinate locations is an alternative to orthorectification. Georeferencing in this manner shall only be undertaken following consultation with the commissioning DSRG Project Manager and after an acceptable accuracy is agreed. A Route Mean Square (RMS) error of less than one pixel is preferred. Section 10 Satellite Imagery Image Compression For change detection, all images shall be co-registered to within one pixel Owing to the large size of image files (including aerial photography), image compression is very useful for usability within CAD and GIS systems. Compressed imagery shall not be used for image analysis and shall not be used as an input to such processes. Where compressed imagery is requested or supplied, imagery should also be supplied in an uncompressed lossless format. Version March 2015

93 Section 11 Master Planning Datasets Section 11 Master Planning Datasets Section 11 Master Planning Datasets Version March 2015

94 Section 11 Master Planning Datasets 11 MASTER PLANNING DATASETS 11.1 Scope of Specification The specification covers the requirements for the production of Master Planning datasets and mapping outputs. Defence Master Planning is the process by which real estate is reserved to allow for the optimal long term siting of activities on an establishment. Master Planning outputs are also used in planning for engineering infrastructure systems to support existing and emerging Defence capabilities within regional and environmental constraints. Master planning is a significant element of Defence capability and estate management A master plan is based on a year time horizon and permits development of an establishment to effectively achieve its functional role as identified by Government policy, Defence capability requirements, and force disposition decisions. Appropriate areas of serviced land are provided to manage the strategic development of competing land uses, and thus to ensure ADF capabilities are sustained in a secure operational environment. Master plans for significant bases are commissioned by the Estate Planning Branch, External Land Planning Directorate with plans for other bases being commissioned by regional offices Estate Planning Branch, External Land Planning Directorate use the data to plan an estate including new buildings, facilities, capabilities and property disposal. Section 11 Master Planning Datasets This specification will be used when a project is initiated by Estate Planning Branch, External Land Planning Directorate to support the planning cycle on a particular Defence property The Master Planning Datasets store the position of Master Planning Boundaries and is used as part of the Master Planning process. Master Planning requires three types of Datasets, these are: Zone Plans These plans define the spatial reservation of land for prescribed groups of compatible uses and activities. Compilation of Zone Plans can encompass Existing and Proposed Zones Defence has derived a standard set of zones for use in all future Zone Plans: Operational Zone Operational Support Zone Base Support Zone Domestic Zone Open Space Zone Future Development Zone Open Training Zone Version March 2015

95 Section 11 Master Planning Datasets Precinct Plans Additional zones shall not be added, unless specified by the Estate Planning Branch, External Land Planning Directorate Precincts are derived from issues analysis. Examples of precincts which may be shown are: Constraints Mapping Security Levels (High / Medium / Low) Heritage Safety Constrained (Arc/Buffer, etc.) Environmental Conservation, Offset Non-Defence Use Unit or Regimental Special Projects Constraint maps convey the spatial extent of the following constraints: Section 11 Master Planning Datasets D(AC)R Defence (Areas Control) Regulations The regulations are concerned with providing height restrictions on man-made structures and vegetation around military airfields. ANEF The Australian Noise Exposure Forecast (ANEF) system ANEF is a scientifically-based computational procedure for determining aircraft noise exposure levels around airfields. The ANEF maps display the aerodrome and the surrounding localities, and the noise exposure contours of ANEF, (the higher the ANEF value, the greater the noise exposure). Explosive Ordnance Safety Templates The criteria defining distances from explosive ordnance and storage facilities, which controls land uses that may not be desirable or compatible with the storage of explosive materials. Extraneous Lighting (DOD) and (CASA) regulations The criteria defining distances from runways, where the amount of upward light emitted in specific areas needs to be controlled. Bird Strikes The criteria regulating distances away from airfields within which developments attracting wildlife (birds and bats) need to be controlled. Version March 2015

96 Section 11 Master Planning Datasets 11.2 Deliverables A Dataset shall be produced for each plan type A Metadata record shall be produced for each Dataset Deliverable Templates A file template containing the data model, and a file containing sample data is available on the Defence Estate Quality Management System (DEQMS) at the following location: 11.4 Deliverable Specification The specification details any additional requirements in addition to those detailed in the Section 2 Data Specification Data Format Digital data can be collected in either GIS or AutoCAD format compatible with the Section 2 Data Specification. (NOTE GIS is preferred) Section 11 Master Planning Datasets File Names Directory Structure Appendix J contains detailed specifications for the provision of AutoCAD data The following filename format shall be adhered to: Format: [DEMS Property Name]_[Mapping Type]_[Year]_[DEMS Property Code]_[Existing or Proposed] Where: Mapping Type: Zone / Precinct / DACR / ANEF Year: Year of map production Existing of Proposed: Whether the plan is existing (E) or proposed (P) Example: Amberley_RAAF_Base_Zone_2008_0861_E The main plan dataset shall be in a parent directory with referenced files in the same directory or at a lower level. Version March 2015

97 Section 12 Contaminated Sites Data Section 12 Contaminated Sites Data Section 12 Contaminated Sites Data Version March 2015

98 Section 12 Contaminated Sites Data 12 CONTAMINATED SITES DATA 12.1 Scope of Specification The specification defines the capture of data relating to known or potential contaminated sites on Defence properties. The purpose of this data is to inform Defence employees and contractors of contamination issues that may impact base planning and infrastructure development at the site Contaminated Sites data assists the National Contamination Remediation Program (NCRP) in the strategic management and tracking of known or potential contamination issues. This is part of a program of identification, assessment and management of contaminated sites across the Defence estate Contaminated Sites Data shall be collected according to this specification to allow consistency in management and reporting The National Contamination Remediation Program (NCRP) undertakes contamination investigations, remediation, monitoring and management projects and programs. Spatial data is collected as part of this work to visually illustrate the outcomes of the project and assist in the improved management of the contaminated sites. Datasets of contamination have been collated to produce a single point of reference for interrogation of information to identify whether contamination investigation, remediation and/or management activity will impact on planning, development, delivery or evaluation of a DSRG activity. The data is a valuable management tool for program planning in the National Contamination Remediation Program and decontamination provisions liability assessment. Section 12 Contaminated Sites Data This specification covers the capture and update of Defence Contaminated Site data that is collected by NCRP over Defence Properties. The Contamination datasets outline the spatial extent of the contamination; stores attribute information defining the Contamination Risk, and provides a link to the Property Contamination Profile (PCP) which is held in the Defence corporate records management system (known as Objective ). All data in the Contamination datasets is derived from the PCP information The Contaminated Sites Datasets that are included within this specification are as follows: Defence Property Boundaries Contaminated: This dataset provides summary contamination information for each Defence Property including the CHAT Risk Ranking, the stage and status of contamination investigation, and general background. Contaminated Sites: This dataset provides detailed information on areas of known and potential contamination within Defence properties. The dataset includes the contaminants of concern, receptors and contamination source. Contaminated Sites Sampling Locations: This dataset details the location of soil sampling sites, groundwater sampling sites and sediment sampling sites. Version March 2015

99 Section 12 Contaminated Sites Data 12.2 Deliverables The deliverables required for a given scope of work will be defined by the work scope. These will be one or more of the following: Defence Property Boundaries Contaminated Contaminated Sites Contaminated Sites Sampling Locations All datasets created or updated in association with these specific datasets shall form part of the project deliverables. Datasets may include groundwater mapping or contours, soil salinity or associated outputs An A3 PDF plot of the Contaminated Sites Register (CSR) shall be provided using the following colours to highlight CSR risk. The plan shall show the whole property, with inserts to show the CSR if required, each CSR shall be labelled with the CSR number. The Master Site Plan Dataset and aerial photographs should be used to help define the position of the CSR. Very High; Red High; Purple Medium; Green Low; Dark Blue A metadata record shall be produced for each dataset. Section 12 Contaminated Sites Data 12.3 Data Deliverable Templates A file template containing all file settings, features, symbology, attributes and layer structures, is available on the Defence Estate Quality Management System (DEQMS) at the following location. A file containing sample data is also available Required Inputs Existing contaminated sites datasets relating to the Defence property Data Deliverable Specification The specification details any additional requirements in addition to those detailed in the Section 2 General Data Specification Data Format File Names Data shall be provided in an ESRI Shapefile. Version March 2015

100 Section 12 Contaminated Sites Data The contaminated sites datasets shall be named as follows: Spatial Accuracy Defence Property Boundaries Contaminated Dataset Filename; Example: Contaminated Sites Dataset Filename; Example: Sampling Locations Dataset Filename; Code> Example: Defence_PCP_<State> Defence_PCP_NSW.shp Defence_CSR_<Property Asset Code> Defence_CSR_1302.shp Defence_CSRsampling_<Property Asset Defence_CSRsampling_ Approximate boundaries will be collected for Areas of Concern and Contaminated Sites Sampling locations shall be captured using a hand-held GPS to an accuracy of ±10m. Section 12 Contaminated Sites Data Data Attributes Data attribute shall be collected for each area of Contamination. Attribute requirements are detailed within Appendix C. Version March 2015

101 Section 12 Contaminated Sites Data Section 13 Environmental Data Section 12 Contaminated Sites Data Version March 2015

102 Section 12 Contaminated Sites Data 13 ENVIRONMENTAL DATA 13.1 Scope of Specification The specification covers data collected for environmental management purposes. The specification provides guidance on the minimum data requirements for Environmental Data Background Information Environmental data shall be collected in formats suitable for use with a Geographical Information System (GIS) to allow Data Users to collect data attributes against spatial features and to undertake spatial analysis on the data The Data Model is located within Appendix K. The Environmental Data Model is divided into the following sections: Base Data; Environment; Environmental Management; Military; and Topography The data model details a General Context to each dataset and the following information: Section 12 Contaminated Sites Data File names; Dataset description; Data custodian (The Defence Data Manager staff position that manages a specified dataset for Defence); Data owner (The Directorate within Defence that creates a dataset); Feature types; Update frequency; and Specific data collection or attribute requirements The Data Model provides an Attribute Table detailing minimum data collection specifications for core environmental datasets. Additional attributes shall be captured as required. The data model details the following attribute information: Field names; Description of the field; Field data types; Field size; Units; and Values or example values. Version March 2015

103 Section 12 Contaminated Sites Data 13.3 Data Deliverables A data file shall be produced for each deliverable Metadata record for each data file Data Deliverable Templates A set of file templates containing the data model requirements are available on the Defence Estate Quality Management System (DEQMS) at the following location Data Deliverable Specification The specification details any additional requirements in addition to those detailed in the Section 2 General Data Specification Data Format File Names Data shall be provided in a GIS data format File names shall be as specified in Appendix K or as detailed in the Section 2 General Data Specifications. Section 12 Contaminated Sites Data Data Attributes Data attributes shall be as specified in Appendix K or as detailed in the Section 2 General Data Specifications Specific Data Requirements Specific data requirements shall be as specified in Appendix K. Version March 2015

104 Section 14 Hazards Data Section 14 Hazards Data Section 14 Hazards Data Version March 2015

105 Section 14 Hazards Data 14 HAZARDS DATA 14.1 Scope of Specification The specification defines the capture and presentation of data relating to known or potential Hazards on Defence properties. The purpose of this data is to inform Defence employees and contractors of hazards that may impact safe operation of the site, base planning and infrastructure development at the site Schedule 11 Hazardous Chemicals Data and Maps (HAZCHEM) Background Work Health and Safety Regulations (Cth) 2011 (WHS Regs), Regulation (Reg) 347 requires a person conducting a business or undertaking (PCBU) at a workplace must, if the quantity of a Schedule 11 hazardous chemical or group of Schedule 11 hazardous chemicals used, handled or stored at the workplace exceeds the manifest quantity for the Schedule 11 hazardous chemical or group of Schedule 11 hazardous chemicals to: Section 14 Hazards Data Map Requirements a. prepare a manifest of Schedule 11 hazardous chemicals, including site plans (maps) prepared in accordance with Schedule 12 of the WHS Regs; and b. ensure that the Regulator (Comcare) is given written notice where manifest quantities are used, handled or stored, at a workplace in accordance with Reg In accordance with point (a) above this specification outlines the requirements for spatial data representing areas within workplaces on the Defence Estate where Schedule 11 hazardous chemicals are used, handled or stored. The specification also outlines the requirements for the required site maps showing these same areas in hard or soft copy form The audience for these maps includes Emergency Services, Comcare and all Defence (including contractors) site personnel WHS Regulations, Schedule 12, Clause 7 and Defence WHS Manual, Vol 3, Part 3A, Chapter 1, Procedure HC:03-15 Notification of Hazardous Chemicals Manifest Quantities, Pipelines and Abandoned Tanks specifies the minimum detail which must be shown on workplace site plans (maps): 1. Show the location of containers and other storage of hazardous chemicals in bulk and provide their identification details (e.g. DGT 3); Version March 2015

106 Section 14 Hazards Data 2. Show the location of storage areas for packaged hazardous chemicals and IBCs and provide their identification details (e.g. PS3); 3. Show the location where hazardous chemicals are manufactured or generated and provide their identification details (e.g MA 2); 4. Show on the map areas which have been designated for chemicals that are in transit (e.g ITA 1); 5. A legend describing what the map symbols represent; 6. Show the location of the main entrance (gate) to the Property (and other points of entry) and clearly show the access route to the workplace from the main entrance of the property; 7. Show on the map entry and exit points to/from the workplace; 8. Show on the site map any essential site services, including fire services and isolation points for fuel and power; Section 14 Hazards Data 9. Show on the site map all drainage systems; 10. Show on the site map where the manifest is located; 11. Show and provide a description of adjoining workplaces, occupancies or sites (e.g. car repair shop and furniture factory); 12. Show on the site map the location of all other buildings, amenities, fences, car parks and storage areas; 13. Include a north point symbol indicating the direction of true north; 14. Ensure the site name and address details are recorded on the site map along with the date it was prepared / revised; and 15. Include a description of the activities carried out in adjoining sites or premises. Note: The completed workplace map (plan) must match the information in HCM002 Notification Form and Manifest document Refer to Appendix M for the symbology requirements to be used for all Defence Schedule 11 Hazardous Chemical site maps The Comcare approved map template must be used for all Defence workplace site maps as shown in Figure 14-1: Example Workplace Site Map. Refer for available pre-prepared template. Version March 2015

107 Section 14 Hazards Data Section 14 Hazards Data Spatial Data Management Plan Figure 14-1: Example Workplace Site Map Version March 2015

108 Section 14 Hazards Data Workplace site maps will use the current Master Site Plans (Section 3) and or current imagery as their base map. Layers selected from Master Site Plans should be selected so as to show the general above ground configuration of the site and any below ground infrastructure into which escaped material may drain. Refer to Appendix M for the recommended list of Master Site Plan layers to be used in Workplace site maps Table 14-1 provides map presentation guidelines that must be adhered to. Table 14-1: Schedule 11 Hazardous Chemicals Workplace Site Map Presentation Guidelines Title Map Element Guideline The map title shall include the Defence property number, property name, State/Territory and the name of the workplace as per the Defence Notification. Section 14 Hazards Data Locality map Legend Scale The locality map extent must be such that the Property entrance and workplace are included. The map legend shall show symbols as per Appendix M and will include only these features included in the map. 1. Map scale will be such that the map is readable. The preferred scale range is 1:500 1: Where a single notification includes widely separated sites that would lead to map features being unreadable, multiple map sheets should be used. North point Regional reference Where ever possible the map must be oriented so that north is up the page. The reference number that identifies the workplace documented by the Manifest. The reference number conforms to the following schema: PPPP-AAAA Where PPPP is the DEMS_ID of the property. AAAA is the DEMS Asset number of the tank, container, storage area or compound that is used to store, handle or generate the hazardous chemicals. Where no such feature is present or there are multiple tanks, containers etc. the DEMS asset number of a building or structure in close proximity may be used, if it is shown on the map, as the Regional reference. Version March 2015

109 Section 14 Hazards Data Comcare reference Workplace address Tanks Abandoned tanks The workplace number assigned by Comcare must be shown in the legend panel (if known) The legend panel shall include the address of the workplace, as per the Defence Notification. Tanks will be labelled with a DGT number, and detail sourced from the Defence Notification including: 1. Volume (maximum capacity in Litres/Kilograms); 2. Contents (with the appropriate GHS or ADG code and description) 3. Any local identification number or code; 4. The tanks Defence Asset number (DEMS); 5. Where individual labelling of tanks is impractical tanks may be labelled with the DGT number and cross referenced to a table listing the above details, e.g. DGT 001. Any tank that has not been formerly de-commissioned, whether in use or not, must be shown. Those that are not in use may be shown as Abandoned. Section 14 Hazards Data Below manifest quantities Site access Manifest Assembly Area Base map labelling Where a workplace contains other quantities of Hazardous Chemicals that are below manifest thresholds, which may be relevant in the event of an incident, their presence may be noted and labelled. A line or lines showing the access route from the Properties main gate to the workplace exit and entry points may be substituted for a written description of the access route. The location of the Manifest must be shown in the body of the map. A note must also be shown below the locality map describing the location(s) of the Manifest. Where it is not practical to hold the manifest at the workplace (i.e. with the manifest quantity) the location where the Manifest is held must be shown in the locality map and described in the note below the locality map (e.g. Bulk LPG Bullet). The assembly area(s) for the site must be shown. If inclusion within the map would impact readability (reduction of the scale) then a symbol(s) may be placed at the map margin with an arrow pointing in the direction of the actual location with the name of that location and the distance in metres. The base map must include, where relevant: 1. Road names: 2. Building/Structure asset codes (DEMS) 3. Building/Structure names 4. Names/Descriptions of yards, compounds etc. that may be relevant; Version March 2015

110 Section 14 Hazards Data Hydrants, extinguishers, First Aid, Spill Kits, Eye Wash, Emergency Showers. Creation and Revision dates Softcopy map delivery Review Procedure 1. These features must be shown in the immediate vicinity of the workplace where outside buildings or structures. 2. These features may be shown when inside buildings only when they would be accessible and relevant in the event of an incident. 1. The date of the maps creation must be shown. 2. The date of the map revision must be shown. Where maps are delivered in softcopy form (adobe PDF format) care must be taken to ensure all fonts are embedded to ensure maps render accurately on end users computers Prior to finalisation workplace site maps must be provided to the relevant contacts at the property for review and confirmation purposes. A checklist is provided at Appendix M to guide and support this process. Section 14 Hazards Data Dependences Workplace site maps are supporting documentation for Notifications made by Defence to the Commonwealth WHS Regulator, Comcare. As such, the details shown on workplace site maps must be sourced from and match the details in the Notification and Manifest documents Spatial Data Requirements Areas representing the locations where Schedule 11 Hazardous Chemicals are stored, handled, manufactured and or generated will be captured as polygons. The representation may be: 1. A polygon representing the individual container/tank the material is held within; or 2. A polygon that represents an area (eg yard, compound etc) where materials are held; or 3. A polygon that represents the extent of containers/tanks/yards/compounds etc. when no base data representing these individually is available The location of infrastructure and equipment used to respond to incidents related to the subject Schedule 11 Hazardous Chemicals will be represented as point features. Version March 2015

111 Section 14 Hazards Data Deliverables 1. Only infrastructure and equipment that is not within the scope of Master Site Plans (Section 3) are to be included in this dataset. Appendix M provides a list of features that may be included in this dataset Spatial data will be captured in Shapefile format in accordance with the requirements of Section 2 General Data Specification, except where specified otherwise in this section Attribute information to be captured and stored with Polygon and Point features is described at Appendix M The following are the minimum expected deliverables where a workplace site map is updated or a new one is created: 1. Workplace Site map(s), conforming to in PDF format; Section 14 Hazards Data Deliverable Templates 2. New and or updated HAZCHEM spatial data conforming to in shapefile format. 3. There shall be one polygon and one point HAZCHEM spatial dataset for each Property; 4. New and or updated metadata record for each HAZCHEM spatial data set; and 5. New and or updated map documents where ESRI ArcGIS is used to prepare workplace site map(s). Refer A file template containing the data model, and a file containing sample HAZCHEM data is available on the Defence Estate Quality management System (DEQMS) at the following location: Deliverable Specification This sub-section details any additional requirements in addition to those detailed in Section 2 Data Specification Data Format Workplace site maps can be prepared in any application supporting data formats compatible with Version March 2015

112 Section 14 Hazards Data File Names the Section 2 Data Specification. (NOTE ESRI ArcGIS.mxd map documents are preferred) Appendix M contains detailed specifications for the provision of workplace site maps and HAZCHEM spatial data The following filename schema for workplace site maps shall be adhered to: [DEMS Property Number]-HAZCHEM Map-[Regional reference] Refer Table 14-1 for definition of the Regional reference. Example: 0089-HAZCHEM Map-B0116.pdf The following filename schema for workplace HAZCHEM spatial data shall be adhered to: Section 14 Hazards Data Defence_HAZCHEM_[DEMS Property Number] Example: Defence_HAZCHEM_0089.shp The following filename schema for infrastructure and equipment used to respond to incidents shall be adhered to: Defence_HAZCHEM_PT_[DEMS Property Number] Example: Defence_HAZCHEM_PT_0089.shp The following filename schema for workplace HAZCHEM map documents prepared using ESRI ArcGIS shall be adhered to: Workplace_[DEMS Asset Number] The DEMS asset number will aligned with that chosen for the workplace site maps, refer Example: Workplace_B0116.mxd Where a HAZCHEM map document (e.g..mxd files) reference other data, the map document and referenced data may be packaged into compressed data archive (.zip). Version March 2015

113 Section 14 Hazards Data Specific Metadata Requirements References Workplace HAZCHEM spatial data are to be documented as GIS Data-Vector Workplace HAZCHEM map documents (e.g.mxd files) or compressed data archive shall be included within the scope of the HAZCHEM spatial data metadata The requirements for these data and maps are informed by the following: Defence WHS Manual, Vol 3, Part 3A, Chapter 1, Procedure HC:03-15 Notification of Hazardous Chemicals Manifest Quantities, Pipelines and Abandoned Tanks Work Health and Safety Regulations (Cth) 2011 (WHS Regs), Regulation (Reg) 347 and schedule 12, Clause 7. Section 14 Hazards Data 14.3 Hazardous Areas Data Background In order to properly discharge the applicable safety duties under the WHS Act, Defence needs to identify the safety hazards and risks arising from its operations. Accordingly, it is required to identify all hazardous areas on the Defence Estate Hazardous areas are areas where a flammable atmosphere may be expected to be present owing to the presence of flammable gases, vapours, liquids, or combustible dusts, fibres or flyings may occur in dangerous quantities and where explosives materials/substances are exposed to the atmosphere For further information on identification of hazardous areas refer also to the WHS Code of Practice - Managing Risks of Hazardous Chemicals in the Workplace - July Appendix I - Fire and Explosion Risks Spatial Data Requirements Areas delineating the location and extent of hazardous areas will be represented as polygons. Each polygon will represent the individual structure/room/cabinet/yard/etc each hazardous area is contained within. That is there must be one polygon for each hazardous area. Version March 2015

114 Section 14 Hazards Data Deliverables Spatial data will be captured in Shapefile format in accordance with the requirements of Section 2 General Data Specification, except where specified otherwise in this section Attribute information to be captured and stored with each polygon is described at Appendix M The following are the minimum expected deliverables: 1. New and or updated Hazardous Areas spatial data 2. There shall be one Hazardous Areas spatial dataset for each Property; and 3. New and or updated metadata record for each Hazardous Areas spatial data set; Section 14 Hazards Data Deliverable Templates A file template containing the data model, and a file containing sample Hazardous Areas spatial data is available on the Defence Estate Quality management System (DEQMS) at the following location: Deliverable Specification This sub-section details any additional requirements in addition to those detailed in Section 2 Data Specification File Names The following filename schema for Workplace Hazardous Areas spatial data shall be adhered to: Defence_Hazardous_Areas_[DEMS Property Number] Example: Defence_Hazardous_Areas_0089.shp Specific Metadata Requirements References Hazardous Areas spatial data are to be documented as GIS Data- Vector. Version March 2015

115 Section 14 Hazards Data The requirements for these data are informed by the following: 14.4 Unexploded Ordnance (UXO) Data Background WHS Code of Practice - Managing Risks of Hazardous Chemicals in the Workplace - July Appendix I - Fire and Explosion Risks Work Health and Safety Regulations (Cth) 2011 (WHS Regs), Regulation (Reg) The Department of Defence is required to maintain a comprehensive record of sites confirmed as, or suspected of being contaminated by unexploded ordnance (UXO). Section 14 Hazards Data A primary purpose of these records is for protection of members of the public from the hazards associated with UXO, and to increase public awareness of these hazards The records are made available to the general public, planning authorities, utility companies, and industry in order to influence local land use planning and development activities Defences owns and maintains spatial data delineating areas that have potential for the presence of UXO in order to support the above requirements The spatial data covers land: 1. Occupied by the Commonwealth; 2. Divested by the Commonwealth of a legal interest in the land; and 3. Land the Commonwealth has never had a legal interest in Spatial Data Requirements Areas delineating the location and extent of areas that have potential for the presence of UXO will be represented as polygons. Each polygon will encompass a region determined to have an equal level of UXO potential. There must be one polygon for each UXO area Spatial data will be captured in Shapefile format in accordance with the requirements of Section 2 General Data Specification, except where specified otherwise in this section. Version March 2015

116 Section 14 Hazards Data Deliverables Attribute information to be captured and stored with each polygon is described at Appendix M The following are the minimum expected deliverables: Deliverable Templates 1. New and or updated UXO spatial data 2. There shall be one UXO spatial dataset for the entire geographic scope of services; and 3. New and or updated metadata record for new or updated UXO spatial data set; A file template containing the data model, and a file containing sample UXO spatial data is available on the Defence Estate Quality Management System (DEQMS) at the following location: Section 14 Hazards Data Deliverable Specification This sub-section details any requirements in addition to those detailed in Section 2 Data Specification File Names Where a project is contributing new UXO spatial data the following filename schema shall be adhered to: UXO_[Project Number] Example: UXO_SN0089.shp Where a project is updating existing UXO spatial data the existing filename will be preserved Specific Metadata Requirements UXO spatial data are to be documented as GIS Data-Vector References The requirements for these data are informed by the following: Version March 2015

117 Section 14 Hazards Data Commonwealth Policy on the Management of Land Affected by Unexploded Ordnance, Section 14 Hazards Data Version March 2015