ID07180034_Supporting_Documents_Part_8.pdf

United States Air Force

Environmental GIS Program

Data Layer Specifications for:

Wildlife Management Area

March 01, 2018

Data Layer Specification – Wildlife Management Area

2 | P a g e

Revision History Date: Version: Description of Revision:

12/12/2016 WildlifeManagement Area_20161212

Removed “the vertical datum shall be Mean Sea Level (MSL_Height),” from the Coordinate System section.

6/23/2016 WildlifeManagement Area_20160623

Added WildlifeMgtArea_P representation under “Data Layer Details” section.

Added WildlifeMgtArea_P topology under “Geometry/ Topology” section.

Updated “Positional Accuracy” section.

3/9/2017 WildlifeManagement Area_20170310

Updated all Air Force Standard attribute fields to match August 6, 2015 GeoBase Data Dictionary.

Updated “Positional Accuracy” section.

Updated “For Empty Text Values” subsection.

Updated the “Representation” subsection of the “Data Layer Details” section.

Updated the “Point Features” subsection of the “Geometry/Topology” section.

6/8/2017 WildlifeManagement Area_201700608

Updated the data layer update frequency in the “Sources and Source Selection” section.

Updated “Data Steward POC”

3/1/2018 WildlifeManagement Area_20180301

Updated Data Layer Details, Geometry/Topology, Positional Accuracy, Attributes, and Business Tables sections.

Updated domain table in Appendix 1.

3 | P a g e

This Data Layer Specification (DLS) defines geospatial data specifications for the WildlifeMgtArea_A and WildlifeMgtArea_P data layers implemented under the United States Air Force Civil Engineer

Center (AFCEC) Environmental GIS Program.

Definition Areas where specific actions have been taken to manage wildlife populations such as, but not limited to: food plots, salt licks, guzzlers, government wildlife management areas (if applicable), etc.

Data Layer Details

SDSFIE 3.1.1 AF AFCEC/CZ

Adaptation Feature Class Name:

WildlifeMgtArea_A WildlifeMgtArea_P

SDSFIE 3.1.1 AF AFCEC/CZ

Adaptation Feature Dataset:

environmentalNaturalResources

Previous Layer Names:

gov_wildlife_management_area LandManagementZone

Geometry Type: Polygon, Point

Data Steward Organization (Program Area):

Program Area: Natural Resources

Data Steward POC: AFCEC/CZTQ Air Force Natural Resources Program SME

Representation:

Wildlife management areas are represented as closed polygons depicting the outermost extent of the area.

Each individual wildlife management area is represented by a single area feature.

All points developed from areas shall represent the centroid of wildlife management areas.

Implementing Authorities and Regulations

Implementing Program(s):

Driver(s):

HQ AF/A7CAN

AFI32-10112, Installation Geospatial Information and Services (IGI&S), 19 October 2007

AFI32-7062, Comprehensive Planning, 27 June 2013

AFI32-7064, Integrated Natural Resources Management, 18 November 2014

AFI32-7065, Cultural Resources Management Program, 19 November

AFH32-9007, Managing Air Force Real Property, 1 May 1999

AFI32-1084, Facility Requirements; Chapter 11-16, 1 September 1996

4 | P a g e

Implementing Program(s):

Driver(s):

Garrison Mapping Concept of Operations (CONOPS) Version 2.0, 12 June 2003

USAF Installation Geospatial Information and Services (IGI&S) Data Model, 15 December 2009

Real Property Inventory Management (RPIM), v2.0

RPIM 3.0, extracted 4/2009

10 USC 2671

PL 86 - 337 ( Hunting, Fishing, and Trapping)

Geometry/Topology

Polygon Features:

Polygons must not overlap.

Polygons must be single part features.

Polygons must be larger than cluster tolerance (.001 meter).

Point Features:

If a point represents a polygon feature, then the point must fall properly inside of the coinciding polygon.

Sources and Source Selection Information for this geospatial data layer must be obtained and/or validated at the installation level. The Data Steward will have overall responsibility for completing and updating the spatial, attribute and metadata features of this geospatial data layer in accordance with this DLS. The data layer will be updated on an annual (yearly) basis at a minimum. More frequent updates may be performed if new data has been developed prior to the annual update. Additionally a bi-annual

(every 6 months) Quality Control (QC) check will be performed on all data housed in GeoBase.

Updates and QC will be performed on any new data prior to uploading it to GeoBase.

Possible sources for the data layer are: planimetric data extracted from stereo or ortho-imagery, differential GPS survey, conventional surveys using a survey grade GPS, computer aided design

(CAD), imagery, hardcopy documents, attribute or tabular data.

Positional Accuracy Horizontal Accuracy: Data developed within this layer should be within 12 meters of the actual location at the 95% confidence level. Accuracy reported at the 95% confidence level means that

95% of the positions in the dataset would have an error with respect to true ground position that is equal to or smaller than the stated accuracy threshold value.

Vertical Accuracy: Not Applicable.

5 | P a g e

Note: Horizontal accuracy should be recorded within the “Quality” element of the metadata. Where positional accuracy cannot be determined, this section should be populated with “Not Recorded” and a brief statement explaining why it cannot be determined should be provided.

Coordinate System The bounding coordinates to capture the north, south, east, and west most spatial extents of the

WildlifeMgtArea_A and WildlifeMgtArea_P layers will be based on the Universal Transverse

Mercator (UTM) Zone, meters. Datasets within the database should have a spatial reference with a precision of 1000. The horizontal datum to be utilized for all data is World Geodetic System 1984

(WGS84), and the projection is the Universal Transverse Mercator (UTM) zone for the installation.

Attributes The following table lists the attributes for the WildlifeMgtArea_A and WildlifeMgtArea_P data layers.

SDSFIE 3.1.1 Air Force AFCEC/CZ Adaptation Attributes

Domain (D)

Attribute Name Definition Allowed Values Data Type

(Length) Advocate wildlifeMgtAreaIDPK

The unique identifier for each feature in the feature class. The value should be calculated as follows:

INST_SITE0001000000

1, where INST is the 4 character installation ID, SITE0001 is the 4 character 4 digit site ID, followed by a 7 digit unique number starting with 0000001.

String (20)

AF

sdsID A unique identifier for all features and objects in the SDSFIE.

GUID SDSFIE

sdsFeatureName The common name of the feature.

Any common name used to describe the

Wildlife Management Area.

String (80)

SDSFIE

6 | P a g e

Domain (D)

Attribute Name Definition Allowed Values Data Type

(Length) Advocate sdsFeatureDescription A narrative describing the feature.

Any descriptive information about the Wildlife Management

Area that is not already included in the attribute table.

String (255)

SDSFIE

sdsMetadataID The foreign key to a metadata record.

SDSFIE

areaSize

(Polygon geometry) The value of the measured area.

Recorded to the 1/1000 of an acre.

Double AF

D areaSizeUOM

(Polygon geometry)

The unit of measure for the area of the calculated area.

acre

String

AF

perimeterSize

The value of the measured perimeter.

Recorded to the 1/1000 of a foot

Double AF

D perimeterSizeUOM (Polygon geometry)

The perimeter unit of measure.

foot String (25) latitude

The latitude coordinate of the "centroid" of the polygon in decimal degrees.

decimal degrees Double AF longitude

The longitude coordinate of the "centroid" of the polygon in decimal degrees.

MGRScentroid

Military Grid Reference System for the centerpoint of the

(area) critical infrastructure. MGRS is calculated from the

Latitude and Longitude values.

latitude

(Point geometry)

The latitude coordinate in decimal degrees to sub foot precision.

longitude

The longitude coordinate in decimal degrees to sub foot precision.

7 | P a g e

Attribute Name Definition Allowed Values Data Type

(Length) Advocate

MGRS

Military Grid Reference System for the coordinate point.

MGRS is calculated from the Latitude and

Longitude values.

elevation

The elevation of the subject item in relation to a datum.

Double AF

D elevationUOM

(Point geometry)

The unit of measure for elevation dimension.

foot String (25)

AF

dateDesig

Date the area was designated. Format for date is YYYYMMDD (i.e., September 15, 1994 = 19940915).

Integer (Long)

AF

D mgtLevel

Discriminator. The governmental level of management for the area.

For a list of domain values, see GovMgt in

Appendix 1.

String (10)

AF

restriction

Any restrictions associated with the management area, including special rules or notes.

(240)

AF

restrictPeriod Range of dates or description of restriction period.

(30)

AF

D installationID

Installation identifier assigned to the

Installation by real property.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String (16)

AF

D installationName

The actual name of the installation that is associated with the installation ID defined by real property.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String (100)

8 | P a g e

Attribute Name Definition Allowed Values Data Type

(Length) Advocate

D siteID Installation identifier assigned to the Site by real property.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String (36)

AF

D majorCommand Service Major

Command of the installation.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String (10)

AF

D realPropertySiteUniqu eID

The unique identifier (UID) used to permanently identify a Site. This UID will be a

Real Property Site Unique Identifier (RPSUID). Source:

RPIM, v3.0, extracted 4/2009.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String (20)

AF

wacInnrCode The NGA World

Airfield Identifier.

The NGA World Airfield Identifier

Code: List of codes can be accessed at the following site:

https://www.extranet.

nga.mil/

String (10)

AF

dataSteward

The data steward is the entity that oversees the data content, context, and associated business rules of the feature class.

AF

D country

The country code is an abbreviation for the country that owns the specific feature class.

For the list of domain values see ISO ALPHA-

2 Code / FIPS 10-4 standard.

String (5)

AF

https://www.extranet.nga.mil/ https://www.extranet.nga.mil/ http://www.nationsonline.org/oneworld/country_code_list.htm http://www.nationsonline.org/oneworld/country_code_list.htm

9 | P a g e

Attribute Name Definition Allowed Values Data Type

(Length) Advocate

D owner

The military service, country, government that owns that specific feature.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String (10)

AF

createDate

Date the feature was originally acquired, created or generated.

If the day is unknown, default to the first day of the month. If only the year is known, default to the first day of the year.

Date AF creator

Person who created the feature. Last name of the person and first initial. Example: Jane

Smith would be attributed as "SmithJ."

AF

D dataCollection

Coded domain value which identifies the collection methodology used to calculate, create or record the feature.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String (20)

AF

dataSource

Identifies the installation office, government agency, contractor or vendor that acquired, created or generated the feature.

AF

editor

Contractor or person that edited the feature attribution or geometry from its original or previous value. Last Name of the person and first initial. For example, Jane Smith would be attributed as SmithJ.

10 | P a g e

Attribute Name Definition Allowed Values Data Type

(Length) Advocate dateEdited

Date that the feature was edited from its original or previous value.

Date AF metaNotes

Describes other details about what was created or edited and why.

(255)

AF

mediaLink

Used to link the record to associated multimedia records that reference data such as imagery, video, audio, scanned documents, drawings, and other digital media.

AF

narrative Any additional comments or notes.

AF

GEOLOC

JOPES geolocator code.

(4)

SHAPE_Length

ESRI-generated field. ESRI

SHAPE_Area

ESRI-generated field. ESRI

Business Tables The business table will contain information that goes beyond the attribute table information, which will be related to the data layer using a Feature Key or other Identifier found in both the attribute table and business table. Additional attributes to be determined by the Program Area Manager. The business tables for WildlifeMgtArea_A and WildlifeMgtArea_P are:

Table Name Identifier Source nr_WildlifeMgtArea_A wildlifeMgtAreaIDFK Program Area Manager nr_WildlifeMgtArea_P wildlifeMgtAreaIDFK Program Area Manager

“No Data” Value in Attributes Directions for populating required attributes for which no data/information is available. Use the appropriate values below:

11 | P a g e

For Empty Text Values

TBD (To Be Determined) – A value is required but the value has yet to be determined.

unknown The value cannot be reasonably determined.

NA (Not Applicable) No value exists.

For Empty Integer Values

99999 (To Be Determined) – A value is required but the value has yet to be determined.

88888 The value cannot be reasonably determined.

77777 (Not Applicable) No value exists.

For Empty Date Values 9/9/9999 (To Be Determined) – A value is required but the value has yet to be determined.

8/8/8888 The value cannot be reasonably determined.

7/7/7777 (Not Applicable) No value exists.

Extent The data layer’s extent will be to the installation boundary, unless otherwise noted by the program area manager.

Metadata Complete Federal Geographic Data Committee (FGDC) compliant metadata for the data layer using the Procedures for Creating Metadata document. Update the metadata Lineage section as edits are made or as necessary.

Theme Keywords: Natural Resources, Wildlife Management Area

12 | P a g e

Appendix 1: SDSFIE 3.1.1 AF AFCEC/CZ Adaptation

Attribute Domain Tables DOMAIN TABLE NAME: GovMgt

ATTRIBUTE NAME: mgtLevel

CODED DOMAIN DEFINITION

city City Government county County Government federal Federal Government local Local

NA Not Applicable: No value exists.

other Other. Must be described in the sdsFeatureDescription attribute.

state State Government

TBD To Be Determined: A value is required but the value has yet to be determined.

United States Air Force

Environmental GIS Program

Data Layer Specifications for:

Wildland Urban Interface

March 01, 2018

Data Layer Specification – Wildland Urban Interface

2 | P a g e

Revision History Date: Version: Description of Revision:

12/12/2016 WildlandUrbanInterface Area_20161212

Removed “the vertical datum shall be Mean Sea Level (MSL_Height),” from the Coordinate System section.

6/23/2016 WildlandUrbanInterface Area_20160623

Updated “Positional Accuracy” section.

3/9/2017 WildlandUrbanInterface Area_20170310

Updated all Air Force Standard attribute fields to match August 6, 2015 GeoBase Data Dictionary.

Updated “Positional Accuracy” section.

Updated “For Empty Text Values” subsection.

6/8/2017 WildlandUrbanInterface Area_20170608

Updated the data layer update frequency in the “Sources and Source Selection” section.

Updated “Data Steward POC”

3/1/2018 WildlandUrbanInterface _20180301

Updated Definition, Data Layer Details, Geometry/Topology, Sources and Source Selection, Positional Accuracy, Attributes, and Business Tables sections.

Added Appendix 1 for domain table.

3 | P a g e

This Data Layer Specification (DLS) defines geospatial data specifications for the

WildlandUrbanInterface_A data layer implemented under the United States Air Force Civil Engineer

Center (AFCEC) Environmental GIS Program.

Definition The area or zone where structures and other human development meet or intermix with undeveloped wildland or vegetative fuels. There are two main categories of communities that meet this description: Interface and Intermix Community.

Data Layer Details

SDSFIE 3.1.1 AF AFCEC/CZ

Adaptation Feature Class Name:

WildlandUrbanInterface_A

SDSFIE 3.1.1 AF AFCEC/CZ

Adaptation Feature Dataset:

environmentalNaturalResources

Previous Layer Names: None

Geometry Type: Polygon

Data Steward Organization (Program Area):

Program Area: Natural Resources

Data Steward POC: AFCEC/CZTQ Air Force Natural Resources Program SME

Representation:

Wildland urban interface areas are represented as closed polygons depicting the outermost extent of the area.

Each individual wildland urban interface area is represented by a single area feature.

Implementing Authorities and Regulations Implementing Program(s):

Driver(s):

HQ AF/A7CAN

AFI32-10112, Installation Geospatial Information and Services (IGI&S), 19 October 2007

AFI32-7062, Comprehensive Planning, 27 June 2013

AFI32-7064, Integrated Natural Resources Management, 18 November

AFI32-7065, Cultural Resources Management Program, 19 November

AFH32-9007, Managing Air Force Real Property, 1 May 1999

AFI32-1084, Facility Requirements; Chapter 11-16, 1 September 1996

Garrison Mapping Concept of Operations (CONOPS) Version 2.0, 12 June 2003

4 | P a g e

Implementing Program(s):

Driver(s):

USAF Installation Geospatial Information and Services (IGI&S) Data Model, 15 December 2009

Real Property Inventory Management (RPIM), v2.0

RPIM 3.0, extracted 4/2009

Geometry/Topology Polygon Features:

Polygons must not overlap.

Polygons must be single part features.

Polygons must be larger than cluster tolerance (.001 meter).

Sources and Source Selection Information for this geospatial data layer must be obtained and/or validated at the installation level. The Data Steward will have overall responsibility for completing and updating the spatial, attribute and metadata features of this geospatial data layer in accordance with this DLS. The data layer will be updated on an annual (yearly) basis at a minimum. More frequent updates may be performed if new data has been developed prior to the annual update. Additionally a bi-annual

(every 6 months) Quality Control (QC) check will be performed on all data housed in GeoBase.

Updates and QC will be performed on any new data prior to uploading it to GeoBase.

Possible sources for the data layer are: data available from the Texas A&M Forest Service Wildfire

Risk Assessment Portal or the Southern Group of State Foresters Wildfire Risk Assessment Portal, planimetric data extracted from stereo or ortho-imagery, differential GPS survey, conventional surveys using a survey grade GPS, computer aided design (CAD), imagery, hardcopy documents, attribute or tabular data.

Positional Accuracy Horizontal Accuracy: Data developed within this layer should be within 12 meters of the actual location at the 95% confidence level. Accuracy reported at the 95% confidence level means that

95% of the positions in the dataset would have an error with respect to true ground position that is equal to or smaller than the stated accuracy threshold value.

Vertical Accuracy: Not applicable.

Note: Horizontal accuracy should be recorded within the “Quality” element of the metadata. Where positional accuracy cannot be determined, this section should be populated with “Not Recorded” and a brief statement explaining why it cannot be determined should be provided.

5 | P a g e

Coordinate System The bounding coordinates to capture the north, south, east, and west most spatial extents of the

WildlandUrbanInterface_A layer will be based on the Universal Transverse Mercator (UTM) Zone, meters. Datasets within the database should have a spatial reference with a precision of 1000. The horizontal datum to be utilized for all data is World Geodetic System 1984 (WGS84), and the projection is the Universal Transverse Mercator (UTM) zone for the installation.

Attributes The following table lists the attributes for the WildlandUrbanInterface_A data layer.

SDSFIE 3.1.1 Air Force AFCEC/CZ Adaptation Attributes

Domain (D)

Attribute Name Definition Allowed Values Data Type

(Length) Advocate wildlandUrbanInterIDP

K

The unique identifier for each feature in the feature class. The value should be calculated as follows:

INST_SITE0001000000

1, where INST is the 4 character installation ID, SITE0001 is the 4 character 4 digit site ID, followed by a 7 digit unique number starting with 0000001.

AF

sdsID A unique identifier for all features and objects in the SDSFIE.

GUID SDSFIE

sdsFeatureName The common name of the feature.

Any common name used to describe the

Wildland Urban Interface area.

String (80)

SDSFIE

sdsFeatureDescription A narrative describing the feature.

Any descriptive information about the

Wildland Urban Interface area that is not already included in attribute table.

String (255)

SDSFIE

sdsMetadataID The foreign key to a metadata record.

SDSFIE

areaSize The value of the measured area.

Recorded to the 1/1000 of an acre.

Double AF

6 | P a g e

Attribute Name Definition Allowed Values Data Type

(Length) Advocate areaSizeUOM The unit of measure for the area of the calculated area.

acre

String (20)

AF

perimeterSize The value of the measured perimeter.

Recorded to the 1/1000 of a foot.

Double AF perimeterSizeUOM The perimeter unit of measure.

foot

String (25)

AF

latitude

The latitude coordinate of the "centroid" of the polygon in decimal degrees.

decimal degrees Double AF longitude

The longitude coordinate of the "centroid" of the polygon in decimal degrees.

decimal degrees Double AF

MGRScentroid

Military Grid Reference System for the centerpoint of the

(area) critical infrastructure. MGRS is calculated from the

Latitude and Longitude values.

AF

D wuiCategory The type of WUI category the feature represents.

For a list of domain values, see

WUIcategory in Appendix 1.

String (10)

AF

D installationID

Installation identifier assigned to the

Installation by real property.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String (16)

AF

D installationName

The actual name of the installation that is associated with the installation ID defined by real property.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String

7 | P a g e

Attribute Name Definition Allowed Values Data Type

(Length) Advocate

D siteID Installation identifier assigned to the Site by real property.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String (36)

AF

D majorCommand Service Major

Command of the installation.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String (10)

AF

D realPropertySiteUniqu eID

The unique identifier (UID) used to permanently identify a Site. This UID will be a

Real Property Site Unique Identifier (RPSUID). Source:

RPIM, v3.0, extracted 4/2009.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String (20)

AF

wacInnrCode The NGA World

Airfield Identifier.

The NGA World Airfield Identifier

Code: List of codes can be accessed at the following site:

https://www.extranet.

nga.mil/

String (10)

AF

dataSteward

The data steward is the entity that oversees the data content, context, and associated business rules of the feature class.

AF

D country

The country code is an abbreviation for the country that owns the specific feature class.

For the list of domain values see ISO ALPHA-

2 Code / FIPS 10-4 standard.

String (5)

AF

https://www.extranet.nga.mil/ https://www.extranet.nga.mil/ http://www.nationsonline.org/oneworld/country_code_list.htm

8 | P a g e

Attribute Name Definition Allowed Values Data Type

(Length) Advocate

D owner

The military service, country, government that owns that specific feature.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String (10)

AF

createDate

Date the feature was originally acquired, created or generated.

If the day is unknown, default to the first day of the month. If only the year is known, default to the first day of the year.

Date AF creator

Person who created the feature. Last name of the person and first initial. Example: Jane

Smith would be attributed as "SmithJ."

AF

D dataCollection

Coded domain value which identifies the collection methodology used to calculate, create or record the feature.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String (20)

AF

dataSource

Identifies the installation office, government agency, contractor or vendor that acquired, created or generated the feature.

AF

editor

Contractor or person that edited the feature attribution or geometry from its original or previous value. Last Name of the person and first initial. For example, Jane Smith would be attributed as SmithJ.

9 | P a g e

Attribute Name Definition Allowed Values Data Type

(Length) Advocate dateEdited

Date that the feature was edited from its original or previous value.

Date AF metaNotes

Describes other details about what was created or edited and why.

AF

mediaLink

Used to link the record to associated multimedia records that reference data such as imagery, video, audio, scanned documents, drawings, and other digital media.

AF

narrative Any additional comments or notes.

AF

GEOLOC

JOPES geolocator code.

(4)

AF

SHAPE_Length ESRI-generated field. ESRI

SHAPE_Area ESRI-generated field. ESRI

Business Tables The business table will contain information that goes beyond the attribute table information, which will be related to the data layer using a Feature Key or other Identifier found in both the attribute table and business table. Additional attributes to be determined by the Program Area Manager. The business table for WildlandUrbanInterface_A is:

Table Name Identifier Source nr_WildlandUrbanInterface wildlandUrbanInterIDFK Program Area Manager

“No Data” Value in Attributes Directions for populating required attributes for which no data/information is available. Use the appropriate values below:

For Empty Text Values

TBD (To Be Determined) – A value is required but the value has yet to be determined.

unknown The value cannot be reasonably determined.

NA (Not Applicable) No value exists.

10 | P a g e

For Empty Integer Values

99999 (To Be Determined) – A value is required but the value has yet to be determined.

88888 The value cannot be reasonably determined.

77777 (Not Applicable) No value exists.

For Empty Date Values 9/9/9999 (To Be Determined) – A value is required but the value has yet to be determined.

8/8/8888 The value cannot be reasonably determined.

7/7/7777 (Not Applicable) No value exists.

Extent The data layer’s extent will be to the installation boundary, unless otherwise noted by the program area manager.

Metadata Complete Federal Geographic Data Committee (FGDC) compliant metadata for the data layer using the Procedures for Creating Metadata document. Update the metadata Lineage section as edits are made or as necessary.

Theme Keywords: Natural Resources, Wildland Urban Interface

11 | P a g e

Appendix 1: SDSFIE 3.1.1 AF AFCEC/CZ Adaptation

Attribute Domain Tables DOMAIN TABLE NAME: WUIcategory

ATTRIBUTE NAME: wuiCategory

CODED DOMAIN DEFINITION

interface

The Interface Community exists where structures directly abut wildland fuels. There is a clear line of demarcation between residential, business, and public structures and wildland fuels. The development density for an interface community is usually 3 or more structures per acre, with shared municipal services.

intermix

The Intermix Community exists where structures are scattered throughout a wildland area. There is no clear line of demarcation; wildland fuels are continuous outside of and within the developed area. The development density in the intermix ranges from structures very close together to one structure per 40 acres.

NA Not Applicable: No value exists.

TBD To Be Determined: A value is required but the value has yet to be determined.

CONTRACTOR PROFILE WORKSHEET

SECTION 1. Contract Information

3. Contract Type: 4. Contract Office

[ ] Construction - MILCON [ ] Base Contracting [ ] Construction - SABER [ ] AFCEE

[ ] Services [ ] COE

[ ] CLS [ ] ROICC

[ ] BOS [ ] Red Horse [ ] Other, explain [ ] Other, explain

Name Orgn/Office Email Phone

10. Contracting Officer

11. QAE

12. COTR

13. Other

14. Other

15. Will hazardous materials be used in the performance of this contract? [ ] Yes [ ] No

16. Will hazardous waste potentially be generated during the performance of the contract? [ ] Yes [ ] No

17. Who is responsible for hazwaste disposal?

18. Remarks:

SECTION II. FOR IHMP USE

19. Tracking requirement: [ ] Yes [ ] No 20. Shop Code: 21. Servicing Hazmart:

22. Reporting Frequency: [ ] weekly [ ] bi-weekly [ ] monthly [ ] quarterly [ ] end of contract

23. Provide Reports to:

24. Additional Reporting Instructions

25. Date of closeout report: 26. Closeout Inspection [ ] Yes [ ] No

9. Contractor Name and full Address:

1. Type of Contract: [ ] Transient [ ] Embedded 2. Contract No.

5. Contract Award Date:

6. Contract End Date:

7. Will GPC be used? [ ] Yes [ ] No

8. Project Description:

Contractor Profile Worksheet #1

TRANSIENT CONTRACTOR ABBREVIATED AUTHORIZATION WORKSHEET

2a

2b

2c

II. Process Information

8a

8b

8c

9a

9b

10a

10b

10c

III. Submitter Information

Complete one form per material, attach MSDS and return to contracting officer when complete.

1. Contractor Name:

Container Unit/Size/Pkg (e.g. 55 GL DR, 1 LB CN):

Other (explain):

10. Will this material generate a waste stream (excess, empty containers, etc)? [ ] Yes [ ] No

If yes, location where waste will be collected:

If yes, describe the expected waste:

Is the container a pressurized aerosol can? [ ] Yes [ ] No

6. Process Description (How will the material be used? Continue on back if needed):

I. Material Information

2. Material Stock Number (MSN, if known):

Part Number/Trade Name:

Manufacturer Name:

City & State:

Type of Container (e.g. metal drum, plastic jar, paper bag, etc.):

If attaching an MSDS, skip to Container Unit/Size/Pkg below

7. Application method (brushed, sprayed, poured, squeezed, etc):

If yes, method of disposal:

11. Name:

13. Title:

12. Date:

14. Phone:

Return this completed worksheet and attached MSDSs to the contracting officer

9. Will material be stored overnight on base? [ ] Yes [ ] No

If yes, maximum amount (number of containers) stored:

If yes, location:

8. Location where work will be accomplished (answer one):

Building Number:

New Construction:

Transient Contractor Abbreviated Authorization Worksheet #2

TRANSIENT CONTRACTOR ABBREVIATED AUTHORIZATION WORKSHEET

IV. IHMP INSTRUCTIONS

17. Local Process Name

18. Process Name 18. Process Type

V. ENVIRONMENTAL REVIEW

19. Environmental Comments

19b. Date

VI. BIOENVIRONMENTAL REVIEW

20. Bioenvironmental Comments

20b. Date

VII. SAFETY REVIEW

21. Safety Comments

21b. Date

16. Rationale if no requirement:

[ ] No hazardous materials [ ] Exempt on Base [ ] Consumer Commodity per 29CFR 1910.1200

Other (explain):

15. Tracking requirement: [ ] Yes [ ] No

19a. Name

20a. Name

21a. Name

Transient Contractor Abbreviated Authorization Worksheet #2

TRANSIENT CONTRACTOR HAZMAT USAGE WORKSHEET

2. Contractor Name: 3. Page of

5. Reporting End Date:

8. Part Number/Trade Name

11. Amt

Used

Enter the total amount of containers used (round up for partials) used during this reporting period

1. Shop Code:

4. Reporting Start Date:

HAZMAT USAGE INFORMATION

Continue on another sheet if required.

6. MSN 7. Container Size 9. Manufacturer 10. Local Process Name

Transient Contractor Hazmat Usage Worksheet #3

Profile Worksheet Instructions

Block No Block Description Action Required

1 Type of Contract

Check type of Contract. Transient Contractors are typically short‐term contractors to include construction. This form is intended for Transient

Contractors, however, there may be a circumstance where it would be applicable to an embedded contractor

2 Contract No Enter Contract Number

3 Contract Type Check the type of Contract. If Other , explain.

4 Contract Office Check the contracting office managing the contract. If Other, explain.

5 Contract Award Date Enter the contract award date

6 Contract End Date Enter the contract end date

7 Will GPC be used Check whether a Government Purchase Card will be used

8 Project Description Describe the general scope of the project

9 Contractor Name and Full Address Enter the Primary Contractor Company name and full address

10, 11, 12 POC Information

Enter name, organization/office symbols, email and phone for the Contracting

Officer (CO), Quality Assurance Evaluator (QAE), and Contract Officer Technical

Respresentative (COTR).

13, 14 POC Information Enter information for other contact personnel

Will Hazardous materials be used in the performance of this contract?

Check yes or no. Hazardous materials are any materials with an Material Safety

Data Sheet (MSDS) or Safety Data Sheet (as applicable)

Will hazardous waste potentially be generated during the performance of the contract? Check yes or no.

17 Who is responsible for hazwaste disposal?

Indicate the organization/company responsible for removing any hazardous waste generated as a result of the contract performance, for example, Company or Installation Hazwaste Office. Note: Hazwaste disposal responsibilities should be stipulated in the contract.

18 Remarks

Remarks concerning hazardous material use or environmental impacts related to the contract performance

19 Tracking Requirement

Check No if the contractor has indicated there are no hazardous materials used in the contract performance.

Check Yes if after review of the contractor MSDSs and Authorization submittals it is determined there is a tracking requirement in EESOH‐MIS

20 Shop Code

Enter the EESOH‐MIS Shop Code that will be used to track the contractor hazmat use

21 Servicing Hazmart Enter the EESOH‐MIS Hazmart that will track the contractor hazmat use

22 Reporting Frequency

After review of the contractor MSDS and Authorization submittals, determine the

Usage reporting frequency

23 Provide Reports to Indicate to whom the contractor will directly provide the usage reports

24 Additional Reporting Instructions Indicate any additional reporting instructions

25 Date of Closeout Report Enter the date of the contractor final hazmat usage report.

26 Closeout Inspection

Enter No, if no closeout inspection is required

Enter Yes if a closeout inspection is required and any other information such as date attended and inspection results.

Purpose: This worksheet will allow the IHMP to annotate basic contractor information and will serve as a record that contractors were assessed for reporting requirements. This Profile sheet will serve as a "Cover Sheet" to the contractor provided authorizations and tracking worksheets.

Section II. IHMP USE

Authorization Worksheet Instructions

1 Contractor Name Enter the Primary Contractor Company Name

2 Material Stock Number

If known, enter Material Stock Number, otherwise leave blank. The IHMP will provide this number if this material requires reporting.

2a Part Number/Trade Name

Skip to block 5 if attaching an MSDS, otherwise be as accurate as possible entering part number and trade name

2b Manufacturer Enter the manufacturer company name as stated on the MSDS

2c City & State Enter the manufacturer company city and state location as stated on the MSDS

3 Container Unit/Size/Pkg

Enter the Container unit quantity, unit descriptor, and type of package for the material, e.g. 55 GL DR, 1 LB CN

4 Type of Container

Enter the kind of container the material comes in, such as metal drum, plastic jar, paper bag, etc.

Is the container a pressurized aerosol can?

If the container is a consumer type aerosol can and the contents are pressurized and dispensed through a valve, answer yes. Otherwise answer No.

6 Process Description

A brief but detailed description of how the material will be used. This will typically require at a minimum what you are doing with the material, what you are doing it to (end item), and how you are doing it. Other information such as location or frequency may be included. For example, painting exterior lights with a brush, or lubing lawn mowers with grease gun quarterly. Use as much space as needed to accurately convey the process, and continue on an extra sheet if required.

7 Application Method

Short description of how the material will be applied (should match what was included in block 8, Process Description. Examples include, brush, roller, HVLP gun, rag, hand, power washer, etc.)

Location where work will be acomplished Answer one of the following blocks (10a ‐ 10c)

8a Building Number

If the work will be accomplished in a specific building on base, enter a building number. If the work will be done in close proximity to a building (but not on or in it), use the building number as a reference and attach a site drawing of the location.

8b New Construction

Describe where the new construction will happen, and attach a site drawing of the location.

8c Other

If the location does not fall in the first two categories above, such as base‐wide, resurfacing first street, environmental remediation of base areas, etc, describe area and attach a site drawing of the location if applicable.

9 While material be stored overnight?

If contractors bring their material each day and is not stored on base, this would be no‐‐skip to block 12. If the contractor has a storage area on base to keep material stock available, this would be yes.

9a If Yes, Location

Provide the location (building number or other site description) where the material will be stored.

9b

If Yes, Maximum Amount (number of containers) Stored

Provide the highest number of containers that is expected to be stored at any one time at this location.

Will this material generate a waste stream (excess, empty containers, etc)?

Enter yes or no if this material is expected to generate a waste. Wastes include empty, partially filled or leftover full containers, spills, cleanup rags, used applicators, etc. If no, skip to block 13.

10a If Yes, Describe the Expected Waste

Provide a short description of the expected or typical waste generated by this material in the process described in block 8.

Purpose: This worksheet should be completed by the contractor for each hazardous material they will be using on the installation

Authorization Worksheet Instructions

10b

If Yes, Location Where Waste Will Be

Collected

Provide the location where the waste will be accumulated pending proper disposal. Attach a site drawing if applicable.

10c If Yes, Method of Disposal

Provide expected method of disposal, such as manifest to an approved hazardous waste treatment, storage and disposal facility.

11 Name Enter the submitter's name.

12 Date Date of submission.

13 Title Submitter's Job Title

14 Phone Submitter's Phone

Section IV. IHMP Instructions

15 Tracking requirement Enter Yes, if the IHMP determines there is a tracking requirement in EESOH‐MIS

16 Rationale if no requirement

Enter the rationale for excluding a submitted material from tracking. Either select the appropriate check box or write the rationale.

17 Local Process Name If tracking is required, enter the Local Process Name for EESOH‐MIS data entry

18 Process Name If tracking is required, enter the Process Name for EESOH‐MIS data entry

19 Process Type If tracking is required, write the Process Type for EESOH‐MIS data entry

20 Environmental Review

Enter any comments and conditions of use. Note: if the material will have restrictive conditions of use or requires disapproval, this must first be coordinated with the Contracting Officer.

20a Name Name of reviewer

20b Date Date of review

21 Bioenvironmental Review

Enter any comments and conditions of use. Note: if the material will have restrictive conditions of use or requires disapproval, this must first be coordinated with the Contracting Officer.

21a Name Name of reviewer

21b Date Date of review

22 Safety Review

Enter any comments and conditions of use. Note: if the material will have restrictive conditions of use or requires disapproval, this must first be coordinated with the Contracting Officer.

22a Name Name of reviewer

22b Date Date of review

Usage Worksheet Instructions

1 Shop Code

Enter the EESOH‐MIS Shop Code that will be used to track the contractor hazmat use

2 Contractor Name Enter the Contractor Name

3 Reporting Start Date Enter the Reporting Start Date

4 Reporting End Date Enter the Reporting End Date

5 MSN

Enter the Material Stock Number (MSN) provided on the Authorization

Form for the material used during the reporting period

6 Container Size

Enter the Container unit quantity, unit descriptor, and type of package for the material, e.g. 55 GL DR, 1 LB CN

7 Part Number/Tradename Enter the part number and/or tradename of the material used.

8 Manufacture Enter the manufacturer name of the material

9 Local Process Name We haven't given this to them

10 Amount used Enter the number of containers used in the reporting period

Promptly return to the Contracting Officer on the reporting end date or at the conclusion of the contract period, whichever comes first

HAZMAT USAGE INFORMATION

For Sections 5 through 10 enter the total amount of containers used during the reporting period (round up for partials). An entry is required for each item that required tracking used during the reporting period. No entry is necessary if the material was not used. Attach

MSDSs for any changes in material used.

Hazardous Materials Management Process (HMMP) – “Plan Phase” – Overview

Introduction to the HMMP Playbook

HMMP Playbook Purpose, Goals and Scope

In accordance with AFI 32-7001 Environmental Management and PAD 12-03 Implementation of Enterprise-Wide Civil Engineer Transformation, the HMMP program must meet EMS requirements and follow the Plan, Do, Check, Act (PDCA) framework in accordance with ISO14001 International Standard for Environmental Management Systems – Requirements with guidance for use. In lieu of a federal requirement or an AFI driver for a HMMP management plan, the HMMP Playbook serves as the HMMP management plan.

In accordance with the EMS (Plan, Do, Check, Act / PDCA) framework, the HMMP Playbook is organized in the following manner:

I. Plan

HMMP Overview

II. Do

Element I - Ongoing Functions

Element II - Process maps and narratives

III. Check

Monitoring and Measurement

IV. Act

Corrective Actions and Continual Improvement

Limitation: This playbook does not replace, supersede, or circumvent existing DoD or Air Force policy.

Federal, state, local or OCONUS regulations and permit conditions take precedence over the guidance in this playbook. This playbook references the Enterprise Environmental, Safety, and Occupational Health Management Information System (EESOH-MIS).

Playbook Roles

The major roles involved in the HMMP program are AFCEC, CE HM Manager (also known as the Installation Hazmat Manager “IHMM”, or HMMP Team Lead), HMMP Team, Shop, Hazmart, and Data Steward. Detailed information about their responsibilities can be found in the Element I Ongoing Functions narratives.

Organization of the HMMP Playbook

The organization of HMMP Playbook follows the EMS PDCA cycle, with particular emphasis on the Do (Implementation and Operation) segment of PDCA.

The DO section of the HMMP Playbook is divided into two Elements. Element I documents all ongoing functions and responsibilities within the HMMP Program in textual narrative form. Element II documents the HMMP lifecycle and operational processes through process maps and accompanying textual narratives.

I. Plan

Overview

II. Do (Implementation and Operation)

Element I: HMMP Ongoing Functions o Establishing and Maintaining HMMP Team o AFCEC Functions o CE HM Manager (HMMP Team Lead) Functions o Shop Functions o Hazmart Functions o Data Steward Functions o Reporting (Regulatory and Process Improvement) o Training

Element II: HMMP Lifecycle Process o 1.0 Establish HMMP Shop and Hazmart

1.1 Establish Hazmat Tracking

1.2 Create Shop/Hazmart Profile

1.3 Obtain Tracking System Access

1.4 Train Users on HMMP

o 2.0 Perform Process Authorization

2.3 Generate Authorization Request or Request Exemption

2.5 Conduct Environmental Approval

2.5.12 Consider Product Substitutions

o 3.0 Track Hazmat

3.4 Process Request and Receive Hazmat

3.4.20 Decant Inventory

3.5 Manage Inventory

3.5.4 Manage Inventory Transaction

3.5.5 Initiate Periodic Audits

3.5.6 Perform Inventory Analysis Shelf Life

3.6 Use Hazmat

3.12 Determine Whether to Reuse/Redistribute or Dispose of Hazmat o 4.0 Manage Deployments III. Check

Monitoring and Measurement

IV. Act

Corrective Actions and Continual Improvement

Introduction the HMMP Program

About the HMMP Program

Hazardous materials (hazmat) are used in every facet of the Air Force mission and pose risks to the health and safety of personnel, surrounding communities, and the broader environment. In 1997, with the first publication of AFI 32-7086, Hazardous Materials Management, the AF created the Hazardous Material Management Process (HMMP) to meet changing regulatory reporting requirements while more effectively reduce the risks and costs associated with the use of hazmat. These evolving environment, safety, and occupational health (ESOH) regulatory requirements for civil engineering (CE), bioenvironmental engineering (BE), and safety (SE) were becoming increasingly complex, and the Air Force could not adequately protect the mission and warfighter from non-compliance without taking greater responsibility for hazmat management.

The development of the HMMP was in many ways a forerunner of today’s AFSO21 process improvement efforts. With AF Civil Engineers and AF Maintenance as champions, HQ USAF assembled a cross-functional integrated product team composed of subject matter experts from weapon system maintenance, supply, acquisition, contracting, CE, BE, and safety to breakdown functional stovepipes and re-engineer AF hazmat management.

Purpose of the HMMP Program

Using the Environmental Management System (EMS) framework and Plan Do Check Act (PDCA) cycle, the purpose of the HMMP Program is to: (1) support Air Force missions; (2) evaluate and mitigate risk to the environment and protect the safety and health of personnel on Air Force installations and surrounding communities; (3) minimize Air Force use of hazmat consistent with mission requirements; (4) and maintain Air Force compliance with environmental reporting requirements related to hazmat usage.

HMMP Program Specific Mission and Goals

Mission Statement: The HMMP supports accomplishment of the AF mission by minimizing and effectively managing dependence on hazmat within acceptable levels of mission and ESOH risk. The HMMP is an asset management approach that allows the AF to systematically manage hazmat and optimize the associated performance, risk and expenditures over the lifecycle.

Goal #1: Establish and sustain an effective installation HMMP Team o Communications and training

Communication Plan

Training Plan o Protect the safety and health of personnel on Air Force installations and communities surrounding Air Force installations from Air Force misuse of hazmat.

o Consistent and active participation of team members.

KPI: Ensure that the HMMP Team has been formally chartered and established under the installation ESOH Council.

KPI: HMMP Team meetings will occur as specified in the approved HMMP Team charter.

o Comply with applicable hazardous material management laws, and regulations

KPI: Ensure data is available to support timely reporting (EPCRA, etc.)

o Executive Order(EOs), especially 13423, Strengthening Federal Environmental, Energy, and Transportation Management, requires Federal Agencies to develop and implement hazardous chemical reduction goals

Develop specific reduction goals on targeted chemicals

Identify those NSNs with multiple vendors that have products with wide variances in chemical ingredients to create separate NSNs

Goal #2: Establish and sustain effective Hazardous Material Tracking Activities (HTA) to manage all hazmat entering an installation o Organizations procuring hazmat must participate in a structure to manage and track all hazmat.

KPI: Periodic surveillance of Shops/Supply Activities starting with self audits to ensure that all hazmat entering the installation is captured within a Hazmart. Additionally, review GPC purchases to ensure tracking of local purchases.

o The HTA enables the efficient procurement and inventory of hazardous materials

Minimize number of stock numbers/products used for hazmat procurement

Identify most sensible source of supply/procurement methods for hazmat, e.g. Blanket

Purchase Agreements, Just-in-Time contracts, Government Purchase Cards (GPC), DLA E-Mall, GSA Advantage, etc.

Manage hazmat with shelf life to avoid disposal

Minimize quantities of hazmat procured by shops

Goal #3: Proactively identify ESOH risk reduction opportunities through cross functional process authorization o Identify, evaluate, minimize, mitigate, and authorize those processes that use a hazardous material to reduce ESOH risk and maximize NI capacity.

Effectively manage dependence on hazmat

Number of negative incidents (spills, NOVs) related to hazmat use

Number of self-audit findings related to hazmat use

Minimize ESOH risks and compliance burden

Number of compliance reports supported by regulators

Number of compliance findings supported by self-audits

Evaluate Process Authorization requests

Percent/Number of process authorization materials changes to reduce

ESOH constraints, based on the corresponding EESOH-MIS values

Number of authorizations per base

Percent shops with authorizations o Provide work area supervisors with information necessary to comply with applicable hazardous material ESOH requirements.

Authorizations will document conditions of use as applicable

Make available Hazard Communication information to the shop supervisor through the tracking system, e.g. physical hazards, inventory reports

Provide ability to document/log hazmat usage to meet permit requirements, e.g. air emission tracking

Allow shops to maintain and report on hazmat inventory o Protect the safety and health of personnel on Air Force installations and communities surrounding Air Force installations from Air Force misuse of hazmat.

Goal #4: Optimize environmental management and reporting by fielding a standard enterprise hazmat tracking system o Collect, track and maintain data related to the receipt, issue, storage, use and disposal of hazardous materials to meet environmental reporting obligations and other ESOH requirements

Implement EESOH-MIS (hazmat Tracking System)

KPI: Percentage of base EESOH-MIS deployment to…