Attch_5_RP_Linear_Segmentation_Guidance.pdf

Linear Infrastructure Playbook Consolidated PDF

Date of Playbook Consolidation: 20 October 2014

Note: Please check the Playbook on the CE Portal for the most updated version. Updates are communicated through the “Playbook Updates” list on the right hand side of each Playbook.

FA4610-18-T-0012

Attachment 5 Linear Segmentation Guide

Linear Infrastructure – Overview

Introduction

The Linear Infrastructure Playbook describes the standardized business processes, roles, and responsibilities involved in implementing linear segmentation of real property (RP) assets on Air Force (AF) installations, focusing on pavements and water / underground utilities. Linear segmentation achieves more accurate RP data to support increased asset visibility, more auditable RP records, investment planning for operations and preventive maintenance efforts, and an understanding of the impacts on related facility systems in the environment. The contents of this Playbook capture key rules for segmenting assets, as well as best practices for implementing segmentation on an AF installation.

This Playbook will help implement Department of Defense (DoD) and AF policy to institute the linear segmentation approach for asset management, where each asset is divided into standardized nodes and segments. The concept of linear segmentation dates back to 2005 with the implementation of the Real Property Inventory Requirements (RPIR) initiative. Linear segmentation was established as a policy directive by the Office of the Secretary of Defense (OSD) in 2008. This directive refers to the RPIR initiative and requires the DoD Components to identify linear structures (e.g., pavement, railroads, and distribution lines) into trackable and measurable modules in the appropriate RP asset management system. This Playbook also serves as the Standard Operating Procedure (SOP) for the 2012 OSD directive to segment linear assets.

Figure 1: Definition of Linear Structure

Squadron Linear Segmentation Phasing

The implementation of the linear segmentation policy is four-phased. This Playbook supports the first phase, in which the installation employs a standardized approach in identifying linear segments and ensures the RP records are updated to reflect the inventory at the segmented level. This phase achieves compliance with the OSD requirement, updates records to reflect the most current state of pavement and utility systems, and validates the RP record. This phase is expected to start immediately and be completed over the next few years.

Figure 2: Squadron Linear Segmentation Phasing

Implementation of linear segmentation across AF assets will be an on-going effort for years to come. Once our systems are segmented in the first Asset Accountability phase, there will be a routine maintenance aspect required as linear systems are added, demolished, or modified. Eventually, linear segmentation will serve to enable more informed risk analysis, portfolio management, and investment planning decisions.

NexGen IT Applicability

As AF Civil Engineer (CE) migrates to NexGen IT, some data elements will integrate with NexGen IT, while some data elements may remain separately managed. Data elements to be migrated are to be determined.

For more information, refer to the following links:

Playbook Webinar

Webinar Recording Webinar Deck Webinar Speaker Notes

Operations Program Group Page Asset Accountability & Optimization (AAO) Program Group Page

Table of Contents

Playbook Overview Process Narratives o Linear Infrastructure – High Level o 5.0 Perform Pavements Facility Mapping o 6.0 Implement Pavements Segmentation Rules o 9.0 Perform Utilities Facility Mapping o 10.0 Implement Utilities Segmentation Rules o 11.0 Generate Supporting Documentation and Update Real Property Records o 12.0 Perform Continuous Updates

Reference Narratives o Acronyms

FA4610-18-T-0012

o Comprehensive References o Definitions o Linear Segmentation Rules for Pavements o Linear Segmentation Rules for Utilities o Strategic Goals

Playbook Roles

Please note that process narratives that do not explicitly involve a specific role may still pertain to that role in an integral way. Some roles are teams that consist of individual roles; please refer to the corresponding narratives to understand the specific roles involved. The process narratives are intended to be used together to provide a comprehensive view of the Playbook topic.

ROLE PROCESS

Linear Segmentation

Team Linear Infrastructure High Level

Facility Map Development Team

5.0 Perform Pavements Facility Mapping

9.0 Perform Utilities Facility Mapping

Real Property Office

(RPO)

6.0 Implement Pavements Segmentation Rules

10.0 Implement Utilities Segmentation Rules

11.0 Generate Supporting Documentation and Update Real Property Records

12.0 Perform Continuous Updates

GeoBase Office 6.0 Implement Pavements Segmentation Rules

10.0 Implement Utilities Segmentation Rules

12.0 Perform Continuous Updates

Pavement Engineer 6.0 Implement Pavements Segmentation Rules Airfield Manager 6.0 Implement Pavements Segmentation Rules

Airfield Pavement Evaluation (APE) Team /

Pavement Condition Index (PCI) Survey

Consultant

6.0 Implement Pavements Segmentation Rules

CE Operations 10.0 Implement Utilities Segmentation Rules

12.0 Perform Continuous Updates

Evaluation Team 10.0 Implement Utilities Segmentation Rules Base Civil Engineer

(BCE)

11.0 Generate Supporting Documentation and Update Real Property Records

Operations Flight Chief 11.0 Generate Supporting Documentation and Update Real Property Records

Sub-AMP Manager 11.0 Generate Supporting Documentation and Update Real Property Records

Other 12.0 Perform Continuous Updates

Linear Infrastructure Playbook Scope

Limitations. This Playbook does not replace, supersede, or circumvent existing DoD or AF policy.

Applicability. This Playbook is written for the primary audience consisting of installation subject matter experts (SMEs) for pavements and utilities, as well as installation RPOs and Geographic Information System (GIS) technicians. The secondary audience includes Major Command (MAJCOM) and Field Operating Agency (FOA) SMEs.

Linear Infrastructure – High Level

Roles and Responsibilities Narrative References and Resources Advice and Tips

This narrative describes the high level process for implementing linear segmentation, gathering supporting documentation, and performing database updates for pavement and utility (water, electric) assets. The roles and responsibilities defined here represent overall descriptions that apply to the remainder of the playbook.

Estimated completion times for processes and steps are provided where possible.

Roles and Responsibilities

ROLES RESPONSIBILITIES

Linear

Segmentation Team

The Linear Segmentation Team represents all organizations that collaborate to execute the processes in this playbook and is responsible to the Base Civil Engineer (BCE). This effort is led by the Real Property Office (RPO) and closely supported by the GeoBase Office and Civil Engineer (CE) Operations. CE Operations includes Operations Engineering, the Shop, Activity Management Planning (AMP) Managers, and their respective engineers. This team identifies the need to create or update a facility map, designates the appropriate personnel to participate, and implements given rules and policy in segmenting linear assets. For pavements assets, this team should include the Pavement Engineer, the Airfield and Transportation Networks (A&TN) AMP Manager, sub-AMP Managers, and the Airfield Manager as necessary. For utilities assets, this team should include the Utilities AMP Manager and appropriate sub-AMP Managers.

Narrative

Step 1.0 – RPO calls for facility map development meeting Role: Linear Segmentation Team Estimated Completion Time: N/A

When a need to develop or update a facility map is identified, the RPO initiates the high level process by calling for a facility map development meeting. The RPO has primary responsibility for this effort to ensure compliance with Real Property (RP) guidance but requires the support of the other organizations to ensure all assets are mapped correctly.

Proceed to Decision 2.0.

Decision 2.0 – Asset type?

Depending on which asset type is being evaluated, pavements or utilities, the process continues to asset-specific processes involving relevant roles.

If ‘Pavements’, proceed to Step 3.0.

If ‘Utilities’, proceed to Step 7.0.

Step 3.0 – Establish Facility Map Development Team for pavements

Estimated Completion Time: RPO – 0.25-0.5 hours, GeoBase Office – 0.25-0.5 hours, Pavement Engineer – 2 hours

The RPO, GeoBase Office, CE Operations, and A&TN AMP Manager (as needed) designate representatives to serve on the Facility Map Development Team. These representatives gather relevant pavement management documents to support the facility mapping effort.

Proceed to Step 4.0.

Step 4.0 – Prepare for pavements facility map development meeting

Estimated Completion Time: RPO – 2-16 hours, GeoBase Office – 8-24 hours, Pavement Engineer – 2-8 hours, Airfield Manager – 2-8 hours

For pavements, the representatives identified in the previous step compile the necessary information to assign the pavement facility numbers at the facility map development meeting. For pavements assets, one meeting should be conducted for the airfield, and one meeting should be conducted for the roads and parking.

RPO: Runs a report for all relevant facilities in Automated Civil Engineer System – Real Property (ACES-RP) using specified category codes (CATCODEs) and researches the facility numbers using historical data, such as RP cards. During this step, the RPO also reviews the category codes associated with existing facilities and brings this information to the Facility Map Development Team meeting

GeoBase Office: Determines if the facility map currently exists. If the map does not exist, the GeoBase Office creates an initial map depicting the geospatial extents of each facility based on existing Geographic Information System (GIS) data using the Air Force (AF) Adaptation 3.0 Initial migration of Pavement Branch (includes all pavements migrated from Spatial Data Standards for Facilities, Infrastructure, and Environment [SDSFIE] 2.6 or earlier) that includes any data from old master plan tabs, the current pavement condition index (PCI) survey map, construction history from last PCI report, and the last structural pavement evaluation

Pavement Engineer: Gathers current pavement reports and sends electronic copies of the pavement mapping and construction history to the other team members. The Pavement Engineer also compiles copies of past pavement evaluations to provide historical data if required. If the base does not have these reports, they can be downloaded at the Pavement Evaluation Report site

Airfield Manager: In the case of airfield pavements assets, compiles information on the current airfield pavement designation map identifying the names and use of each apron, taxiway, runway, or other facilities (e.g., helipad, hot cargo pad, warm-up pad, power check pad, overrun, shoulders)

Proceed to Process 5.0 Perform Pavements Facility Mapping.

Process 5.0 – Perform Pavements Facility Mapping

Estimated Completion Time: 1 year

Once the RPO, GeoBase Office, Pavement Engineer, and Airfield Manager have accumulated relevant data from their respective informational sources, the representatives from these offices meet to form the Facility Map Development Team. The Facility Map Development Team conducts a facility-by-facility review of the pavements facility map created by the GeoBase Office. The team updates the map as required to ensure 100% of the pavements assets in the RP database are accounted for. When the team encounters unassigned assets or must make changes to the pavement facilities documented in the Real Property record, they will follow the recommended standards outlined in this playbook. Separate pavement facility maps should be created for the airfield network and the roads and parking network. Linear assets are assigned according to usage, or CATCODE (refer to the Air Force Category Codes document for a complete listing); the Real Property Unique Identifier (RPUID) serves as the linkage between RP and GeoBase records, as opposed to facility identification (FACID).

The goal to complete this process for all bases is September 2013.

This process has been further defined in a separate narrative document. For additional information, please refer to the supporting narrative for Process 5.0 Perform Pavements Facility Mapping.

Proceed to Process 6.0 Implement Pavements Segmentation Rules.

Process 6.0 – Implement Pavements Segmentation Rules

This process describes the method of assigning segments to a facility number on the GeoBase map and in the pavement management system. In order to ensure the entire pavement inventory is mapped consistently and accurately, pavement evaluation teams and contractors use this process when conducting a structural pavement evaluation or PCI survey.

This process has been further defined in a separate narrative document. For additional information, please refer to the supporting narrative for Process 6.0 Implement Pavements Segmentation Rules.

Proceed to Process 11.0 Generate Supporting Documentation and Update Real Property Records.

Step 7.0 – Establish Facility Map Development Team for utilities

The RPO, GeoBase Office, Operations Engineering, the Shop, and the Utilities AMP Manager (as needed) designate representatives to serve on the Facility Map Development Team for utilities. These representatives gather relevant utilities management documents to support the facility mapping effort.

Proceed to Step 8.0.

Step 8.0 – Prepare for utilities facility map development meeting

Estimated Completion Time: RPO – 2-16 hours, GeoBase Office – 8-24 hours, Operations Engineering – 2-8 hours

The following roles compile the necessary information to assign the utilities facility numbers at the facility map development meeting.

RPO: Runs a report for all relevant facilities in ACES-RP using specified CATCODEs and researches the facility numbers using historical data, such as RP cards. During this step, the RPO also reviews the CATCODEs associated with existing facilities and brings this information to the Facility Map Development Team meeting

GeoBase Office: Determines if the facility map currently exists. If the map does not exist, the GeoBase Office creates an initial map depicting the geospatial extents of each facility based on existing GIS data and current utility information and/or Utilities Tab maps

CE Operations: Reviews data on utility assets and bring this information to the meeting. This includes Operations Engineering, the Shop, and the Utilities AMP Manager

Proceed to Process 9.0 Perform Utilities Facility Mapping.

Process 9.0 – Perform Utilities Facility Mapping

Once the RPO, GeoBase Office, and CE Operations have accumulated relevant data from their respective informational sources, the representatives from these offices meet to form the Facility Map Development Team. The Facility Map Development Team conducts a facility-by-facility review of the utilities facility map created by the GeoBase Office. The team updates the map as required to ensure 100% of the linear utilities assets in the real property database are accounted for. Any unassigned linear assets will be assigned to either a new or existing facility.

Linear assets are assigned according to usage, or CATCODE (refer to the Air Force Category Codes document for a complete listing); the RPUID serves as the linkage between RP and GeoBase records, as opposed to FACID.

This process has been further defined in a separate narrative document. For additional information, please refer to the supporting narrative for Process 9.0 Perform Utilities Facility Mapping.

Proceed to Process 10.0 Implement Utilities Segmentation Rules.

Process 10.0 – Implement Utilities Segmentation Rules

Once utility facilities have been identified and mapped, the Linear Segmentation Team assigns segments to utility assets on the GeoBase map. The Linear Segmentation Team, including the RPO, the GeoBase Office, and CE Operations, performs the activities outlined in this process.

This process has been further defined in a separate narrative document. For additional information, please refer to the supporting narrative for Process 10.0 Implement Utilities Segmentation Rules.

Process 11.0 – Generate Supporting Documentation and Update Real Property Records

Once all facilities have been mapped and segmented, the team gathers the required supporting documentation to justify updates to real property records as necessary. To modify records in all instances of linear segmentation, the Department of Defense (DD) Form 1354, Transfer and Acceptance of DoD Real Property is completed in accordance with the Unified Facilities Criteria (UFC) 1-300-08, the Criteria for Transfer and Acceptance of DoD Real Property.

This process has been further defined in a separate narrative document. For additional information, please refer to the supporting narrative for Process 11.0 Generate Supporting Documentation and Update Real Property Records.

Proceed to Process 12.0 Perform Continuous Updates.

Process 12.0 – Perform Continuous Updates

Identifying the need to update RP records for enhanced accuracy is an ongoing process. Multiple actors can identify the need at any time. Once the need is validated by RPO the process of facility mapping and segmentation begins again at Step 1.0.

This process has been further defined in a separate narrative document. For additional information, please refer to the supporting narrative for Process 12.0 Perform Continuous Updates.

Proceed to Linear Infrastructure High Level.

Templates o N/A

Policies and Regulations o UFC 1-300-08, Criteria for Transfer and Acceptance of DoD Real Property

Forms o DD Form 1354, Transfer and Acceptance of DoD Real Property

Documents o Air Force Category Codes

File Directories / Systems o ACES-RP o AF Adaptation 3.0 Initial Migration of Pavement Branch o SDSFIE 3.0

Websites o Air Force e-Publishing o Pavement Evaluation Reports

Related Playbooks o Military Construction (MILCON) Playbook o Planning Requirements for Environmental Impact Analysis Process (PREIAP) Playbook o Preventive Maintenance Playbook o Project Management Playbook

N/A

Version: 04/12/2013

Linear Infrastructure Comprehensive References

The following is a comprehensive list of references used within the Linear Infrastructure Playbook.

Strategic Goals

Linear Infrastructure Strategic Goals

Definitions and Acronyms

Linear Infrastructure Acronyms Linear Infrastructure Definitions

DD Form 1354 Inventory Adjustment Memorandum – Aerial Photo Interpretation DD Form 1354 Inventory Adjustment Memorandum – Physical Survey DD Form 1354 Template for Linear Segmentation

AFI 32-1041 Airfield Pavement Evaluation Program AFI 32-9005, Real Property Accountability and Reporting Air Force Linear Segmentation Guidance Memorandum (1 April 2013) AFMAN 32-1084, Facility Requirements DoD for Segmenting Types of Linear Structures DoDI 4165.14, Real Property Inventory and Forecasting OSD Real Property Information Model Version 5.0 Real Property Inventory Requirements UFC 1-300-08, Criteria for Transfer and Acceptance of DoD Real Property UFC 3-250-01FA, Pavement Design for Roads, Streets, Walks, and Open Storage Areas UFC 3-250-18FA, General Provisions and Geometric Design for Roads, Streets, Walks, and Open Storage Areas UFC 3-260-01, Airfield and Heliport Planning and Design UFC 3-260-03, Airfield Pavement Evaluation UFC 3-270-06, Paver Asphalt Surfaced Airfields Pavement Condition Index (PCI) UFC 3-701-01, DoD Facilities Pricing Guide

AF Form 332, Base Civil Engineer Work Request (No Link) DD Form 1354, Transfer and Acceptance of DoD Real Property

Air Force Category Codes American Society for Testing and Materials (ASTM) E1557-09 Standard Classification for Building Elements and

Related Sitework Implementing GeoBase at United States Air Combat Command MicroPAVER Version 6.0 User’s Manual

Air Force Adaptation 3.0 Initial Migration of Pavement Branch

ACES-PM

ACES-RP

PAVER Pavement Management Software Spatial Data Standards for Facilities, Infrastructure and Environment (SDSFIE) 3.0

Pavement Evaluation Website Air Force e-Publishing Whole Building Design Guide

Military Construction (MILCON) Playbook Planning Requirements for Environmental Impact Analysis Process (PREIAP) Playbook Preventive Maintenance Playbook Project Management Playbook

Version: 04/23/2013

Linear Infrastructure Acronyms

A

A&TN Airfield and Transportation Network ACES Automated Civil Engineer System ACES-PM Automated Civil Engineer System – Project Management ACES-RP Automated Civil Engineer System – Real Property AF Air Force AFCESA Air Force Civil Engineer Support Agency AFH Air Force Handbook AFI Air Force Instruction AFMAN Air Force Manual AMP Activity Management Plan / Planning AP Apron APE Airfield Pavement Evaluation ASTM American Society for Testing and Materials

B

BCE Base Civil Engineer

C

CAD Computer Automated Drawing CATCODE Category Code CE Civil Engineer CIP Common Installation Procedure

D

DD Department of Defense DoD Department of Defense DoDI Department of Defense Instruction DR Driveway

E

ECT Energy Commissioning Team EMCS Energy Management Control System

F

FAC Facility Analysis Category

FACID Facility Identification FOA Field Operating Agency

G

GIS Geographic Information System

H

HDPE High-Density Polyethylene

I

J

K

KVA Kilovolt Ampere

L

LF Linear Feet

M

MAJCOM Major Command MILCON Military Construction

N

O

OA Other Apron

P

PA Parking Area PCC Portland Cement Concrete PCI Pavement Condition Index PL Parking Lot POC Point of Contact PREIAP Planning Requirements for Environmental Impact Analysis Process PVC Polyvinyl Chloride

Q

R

R Runway RD Road RP Real Property RPI Real Property Inventory RPIM Real Property Information Model RPIR Real Property Inventory Requirements RPO Real Property Office RPSUID Real Property Site Unique Identifier RPUID Real Property Unique Identifier

S

SDSFIE Spatial Data Standards for Facilities, Infrastructure, and Environment SOW Statement of Work SY Square Yards

T

T Taxiway

U

UFC Unified Facilities Criteria

V

W

X

Y

Z

Version: 09/14/2012

Linear Infrastructure Definitions

Asset Type The most encompassing level of segmentation. This may also be referred to as

“linear structure type.” (Source: DoD Guide for Segmenting Types of Linear Structures)

Branch For pavements, a logical subset of a network confined to a single pavement use for airfields, road name for roads, and facility supported or use for parking areas. (Source: Linear Segmentation Rules for Pavements)

For utilities, see Grouping

Category Code

(CATCODE)

The most detailed classification of real property (RP) that describes a specific RP type and function, which, in the Department of the Air Force (AF), is represented by a numerical code of six digits. Military Department categories are established by the Military Departments. (Source: DoD Guide for Segmenting Types of Linear Structures)

Facility In the RP context, a building, structure, or linear structure out to an imaginary line surrounding a facility at a distance of five feet from the foundation that, barring specific direction to the contrary such as a utility privatization agreement, denotes what is included in the basic record for the facility (e.g., landscaping, sidewalks, utility connections). This imaginary line is what is commonly referred to as the “five-foot line.” (Source: AFI 32-9005, Real Property Accountability and Reporting)

In the linear segmentation context, an asset with a specific single function that can only have one Facility Analysis Category (FAC) and one CATCODE.

(Source: Linear Segmentation Rules for Pavements)

Facility Analysis Category (FAC)

A classification of RP types within a “Basic Category,” represented by a four-digit code. DoD FACs aggregate Military Department categories into common associations based upon commonality of function, unit of measure, and unit costs. (Source: DoD Guide for Segmenting Types of Linear Structures)

GeoBase Office Delivers a comprehensive, integrated capability for the AF to attain, maintain, and sustain one geospatial information infrastructure supporting U.S. AF basing requirements. GeoBase is not a single application, but rather a concept of integrated operations. Successful GeoBase deployment involves strategic planning, data capture, data modeling, technology deployment, and training for mission sustainment. (Source: Implementing GeoBase at United States Air Force Air Combat Command)

Geographical / Functional Area

Regarding utilities, geographical / functional areas are defined by the base and can be different from base to base. Common naming of areas on base are flight line, cantonment or housing. The base can have other naming systems to aid its management of the systems such as north-side, south-side, campus, etc.

(Source: Linear Segmentation Rules for Utilities)

Grouping Regarding utilities, consists of interconnected individual segments (linear and non-linear), which would isolate utility service with the minimum by valves, switches or other mechanism needed. (Source: Linear Segmentation Rules for Utilities)

Installation A base, camp, post, station, yard, center, or other activity, including leased facilities, under the jurisdiction, custody, or control of the Secretary of Defense or the Secretary of a Military Department, or in the case of an activity in a foreign country, under the operational control of the Secretary of Defense or the Secretary of a Military Department, without regard to the duration of operational control. An installation may include one or more sites. (Source: DoD Guide for Segmenting Types of Linear Structures)

FA4610-18-T-0012

Linear Structure A facility whose function requires that it traverse land such as a road, rail line, pipeline, fence, or pavement. Includes distribution systems that provide a common service or commodity to more than one building or structure. Linear structures are constructed across the earth – above, on, and below the surface of the ground or water – with one physical dimension (usually length) significantly greater than the other dimensions. A linear structure generally provides the transport mechanism that enables the flow of a service or commodity from its source to its intended destination. (Source: DoD Guide for Segmenting Types of Linear Structures)

Military Department Category

See Category Code (CATCODE).

Network A collection of assets based on a common service, function, or commodity provided identified by a Real Property Site Unique Identifier (RPSUID). (Source:

Linear Segmentation Rules for Pavements)

Non-Linear Segment Regarding utilities, a segment, such as a valve or transformer, not measured by linear footage but by some other unit of measure (e.g., kilovolt-ampere).

(Source: Linear Segmentation Rules for Utilities)

Pavement Condition Index (PCI)

The PCI results from a condition survey and is a numerical rating of the pavement condition that ranges from 0 to 100, with 0 being the worst possible condition and 100 being the best possible condition. (Source: UFC 3-270-06, Paver Asphalt Surfaced Airfields Pavement Condition Index)

Real Property (RP) Land and improvements to land (i.e., facilities), including equipment affixed and built into the facility as an integral part of the facility (such as heating systems), but not movable equipment (e.g., plant equipment, industrial equipment, buoys).

In many instances this term is synonymous with real estate. (Source: DoD Guide for Segmenting Types of Linear Structures)

Real Property Asset An individual facility or land parcel. (Source: DoD Guide for Segmenting Types of Linear Structures)

Real Property Officer

(RPO)

An individual who works in the Real Property Office (RPO) and, based on his or her training, knowledge, and experience in RP management, accountability, and control procedures, is appointed by proper authority, and shall:

Establish and maintain an organization’s formal property records, systems, and financial records, in connection with government RP, irrespective of whether the property is in the individual’s possession

Ensure that all transactions can be audited in their entirety Implement and adhere to associated internal controls

(Source: DoD Guide for Segmenting Types of Linear Structures) Real Property Unique Identifier (RPUID)

A non-intelligent code used to permanently and uniquely identify a DoD RP asset. RPUIDs can be non-linear facilities (vertical construction) or linear structures (water distribution lines, wastewater collection, electrical distribution lines, etc). For linear structures, one RPUID is assigned to one completely connected system. It is important to note that for linear assets that there can be multiple RPUIDs for each CATCODE. (Source: DoD Guide for Segmenting Types of Linear Structures)

Real Property Site Unique Identifier

(RPSUID)

A non-intelligent code used to permanently and uniquely identify a DoD RP site.

(Source: DoD Guide for Segmenting Types of Linear Structures)

Section A subset of a branch that is assigned based on specific physical or usage characteristics. (Source: Linear Segmentation Rules for Pavements)

Segment Subdivisions of facilities with consistent physical and usage characteristics (e.g., branch, section). (Source: UFC 3-260-03, Airfield Pavement Evaluation)

FA4610-18-T-0012

Site Physical (geographic) location that is or was owned by, leased to, or otherwise possessed by a DoD component. Each site is assigned to a single installation.

A site may exist in one of three forms:

Land only, where there are no facilities present and where the land consists of either a single land parcel or two or more contiguous land parcels

Facility or facilities only, where the underlying land is neither owned nor controlled by the government. A stand-alone facility can be a site. If a facility is not a stand-alone facility, it must be assigned to a site

Land and all the facilities thereon, where the land consists of either a single land parcel or two or more contiguous land parcels

(Source: DoD Guide for Segmenting Types of Linear Structures) Structure A facility, other than a building or linear structure, which is constructed on or in the land. (Source: DoD Guide for Segmenting Types of Linear Structures) Sustainment The maintenance and repair activities necessary to keep a typical inventory of facilities in good working order over their expected service life. It includes regularly scheduled adjustments and inspections, preventive maintenance tasks, and emergency response and service calls for minor repairs. It also includes major repairs or replacement of facility components (usually accomplished by contract) that are expected to occur periodically throughout the facility service life. This includes regular roof replacement, refinishing wall surfaces, repairing and replacing electrical, heating, and cooling systems, replacing tile and carpeting, and similar types of work. (Source: DoD Guide for Segmenting Types of Linear Structures)

Source: AFI 32-9005, Real Property Accounting and Reporting; DoD Guide for Segmenting Types of Linear Structures;

Implementing GeoBase at United States Air Combat Command; Linear Segmentation Rules for Pavements; Linear Segmentation Rules for Utilities; UFC 3-260-03, Airfield Pavement Evaluation; UFC 3-270-06, Paver Asphalt Surfaced Airfields Pavement Condition Index

Linear Infrastructure Strategic Goals

The Linear Infrastructure Playbook supports Civil Engineering Goal 3 and Objectives 3.1 and 3.2.

CE Goal 3: Develop sustainable installations by implementing asset management principles for built and natural resources

Implementing asset management as the foundation of Civil Engineering operations and integrating energy, energy security, and environmental considerations in all aspects of business will enable the Civil Engineering enterprise to “Build Sustainable Installations”. Air Force Civil Engineers must ensure they are efficiently and effectively planning, acquiring, sustaining, operating and managing the built and natural infrastructure on Air Force installations.

In managing Air Force installations, the focus will be on the infrastructure needed to execute the mission, diverting resources away from excess, obsolete and underutilized facilities. Civil Engineers will actively pursue the objective to offset the reduction in funds available for installation support activities by improving efficiencies and management of the Air Force physical plant.

Objective 3.1: Establish enterprise-wide total CE asset (built, natural, and human) visibility to enable asset accountability and support lifecycle-based program management

Asset management enables Civil Engineers to determine what they have, both in terms of real property inventory and asset performance. Total asset visibility is an accurate, complete, transparent, enterprise-wide inventory of built (e.g., facility, furnishing, infrastructure, pavements, interior space, etc.), natural (e.g., air quality, land, water, etc.) and human assets.

Civil Engineers will improve their understanding of asset performance through maintenance history, energy use, condition, age, space utilization rates and implementation of standardized facility and infrastructure condition assessments. While engineers currently have interim tools that provide limited visibility at the base and MAJCOM level, the long term NexGen IT solution will enable the enterprise wide view of this data.

Civil Engineers must standardize both the data collected and the data storage systems, in order to roll up that data and provide integrated decision quality information from which investment decisions can be made across the Air Force. Asset visibility and performance data will allow Civil Engineers to leverage strategic sourcing for requirements needed across our portfolio (e.g. the annual chiller requirements we need across the Air Force can be strategically purchased, leveraging size for reduced costs and delivery on demand). Total asset visibility will be implemented across all functional areas to account for every piece of the Air Force Civil Engineering enterprise.

Objective 3.2: Manage the CE Portfolio with targeted, informed and predictive decision quality data to ensure the optimal application of resources and investments

The asset management process also gives Civil Engineers the ability to determine what will be needed in the future. Comparing those needs with what is currently available (i.e. total asset visibility) drives investment planning to eliminate the gaps between the two. Leveraging lifecycle analysis and centralized portfolio management enables senior Air Force leaders to make enterprise-wide predictive decisions that best support the mission.

Source: 2011 USAF CE Strategic Plan

Linear Infrastructure – 5.0 Perform Pavements Facility Mapping

Roles and Responsibilities Narrative

Pavement Facility Designation Process and Standards

Once the Real Property Office (RPO), GeoBase Office, Pavement Engineer, and Airfield Manager have accumulated relevant data from their respective informational sources, the representatives from these offices meet to form the Facility Map Development Team. The Facility Map Development Team conducts a facility-by-facility review of the pavements facility map created by the GeoBase Office. The team updates the map as required to ensure 100% of the pavements assets in the real property (RP) database are accounted for. When the team encounters unassigned assets or must make changes to the pavement facilities documented in the Real Property record, they will follow the recommended standards outlined in this playbook. Separate pavement facility maps should be created for the airfield network and the roads and parking network Linear assets are assigned according to usage, or category code (CATCODE). For a complete listing of CATCODES, refer to the Air Force Category Codes document. The Real Property Unique Identifier (RPUID) serves as the linkage between RP and Geographic Information System (GIS) records, as opposed to facility identification (FACID).

Physically identifying the geometric extent of each facility in a facility map is the first, and arguably the most critical, step in integrating pavement management and pavement RP data. In many cases, bases do not have a pavement facility map for either airfields or roads and parking. Instead, bases may only have the tabular data in Air Force Civil Engineer System – Real Property (ACES-RP) and / or RP record cards. In these cases, there is no way to clearly identify the geometric extent of each pavement facility. The only way to resolve this issue is for the base RPO to work with the GeoBase Office, Pavement Engineer, and Airfield Manager to develop a pavement facility map. This process may take anywhere from a day to a week depending on the size of the base and the number of unknown facilities.

The best approach for this update is for the base to conduct two separate meetings to review the facility map – one meeting to review the airfields and one meeting to review roads and parking areas. Each team member will provide supporting information to aid the team in making decisions based on the preparatory material compiled in Linear Infrastructure High Level, Step 4.0. There is a great deal of variability in the way bases have implemented rules for assigning pavement facility numbers in the past. The intent of this effort is to map the existing pavement facilities documented in the Real Property record to the maximum extent possible and to implement standards for designating pavement facilities when making updates or changes to the pavement facility map and Real Property records. The facility map should clearly show the geospatial extents of each pavement facility listed in the RP record. It will include all paved and unpaved surfaces that are used as (have CATCODEs for) airfields, roads, driveways, and parking areas. Separate pavement facility maps will be created for the airfield network and the roads and parking network.

Note: This Process serves as the Standard Operating Procedure (SOP) for Task 1: Complete Pavement Facility Maps, in the memorandum, “Air Force Linear Segmentation Implementation Guidance,” dated 1 April 2013.

Facility Map Development

Team

The Facility Map Development Team consists of the RPO, GeoBase Office, Pavement Engineer/Sub-Activity Management Planning (AMP) Manager, and Airfield Manager. In most cases, the Pavement Engineer and Sub-AMP Manager are the same person; if they are not, the base will decide which person will participate in this process, based on which person has the most knowledge of all base pavements. As Civil Engineer (CE) Transformation continues, the role of the AMP Manager and Sub-AMP Manager will increasingly focus on total system operations and accountability and will therefore become a more substantial role in this process. The Airfield Manager participates on an as-needed basis, specifically when airfield assets are involved.

The RPO has primary responsibility for this effort to ensure compliance with RP guidance but needs the support of this team to assign pavement assets to a facility according to Air Force (AF) guidance. The RPO’s interest in this process also pertains to the need to report the total number of square yards (SY) for each facility, as opposed to needing to know precisely where the facilities are located. However, the team cannot provide the correct area unless it can delineate the facility on a map. To accomplish this, the team needs an understanding of the RP and facility use guidance to ensure compliance. Additionally, the team will need engineering and historical information. It takes a total team effort with the active participation and cooperation of all to accomplish this task.

Entry from Linear Infrastructure High Level, Step 4.0.

Step 5.1 – Review facility assignments Role: Facility Map Development Team Estimated Completion Time: 2-4 hours

The team may opt to go through this process by either going down the tabular list of pavement facilities sequentially and identifying the geospatial extents of each on the map or, using the map as the guide, going from top to bottom, left to right, and checking off each facility on the tabular list as they are identified on the map. The first approach is suggested in most cases.

Each member of the Facility Map Development Team contributes to facility assignment recommendations based on the information at hand. While going through this process, the team should look at the area of each facility on the list.

This entails looking at the description of the facility and determining the geospatial extents of the facility on the map.

For instance, if the description of the facility describes a transient apron, the team will mark the current area of the transient apron on the map. The team may discover a discrepancy between the area described in the RP record and the area identified on the map. In these cases, the team will look at the old RP record cards, past pavement evaluation reports, previous imagery, or any other sources available to verify the geospatial extents shown on the map are correct. When determining the authoritative source of information, explicit descriptions in the RP record, as-built drawings, or documented surveys will take precedence. If these are not available, past pavement evaluations or old master plan tabs (E7) are the next best source of information. In other words, use the most authoritative, time-relevant document available. There may be cases where the team does not have enough information to clearly define where a facility is located on the map. In these cases, the team will follow the standards outlined in this playbook for designating pavement facilities and use its best judgment to determine the geospatial extents of the facilities on the map. The team makes recommendations, but the RPO, as the process owner, makes the final decision in the event of competing recommendations.

Below are the specific tasks by role to be completed during the review of facility assignments:

RPO: Recommends facility assignments based on a complete list of pavement facility numbers and descriptions generated by ACES-RP, historical RP cards, and any other relevant records

GeoBase Office: Provides a draft pavement facility map, imagery (if the pavement facility map does not already have imagery in the background), and old master plan tabs (especially E7 Tab for airfields)

Pavement Engineer: Provides branch and section maps, as well as construction history from current pavement evaluation reports and old reports that may help provide historical context for the team’s decisions on the geospatial extents of each facility

Airfield Manager: Provides recommendations to the team regarding geospatial extents of each airfield pavement facility and information on current use of airfield facilities

Proceed to Step 5.2.

Step 5.2 – Apply pavement facility numbers to map

Estimated Completion Time: 2-4 hours

The GeoBase Office representative labels the areas on the map with the correct pavement facility numbers according to the Facility Map Development Team’s decision in the preceding step. An example of a pavement facility map is provided in the Advice and Tips section of this narrative.

Proceed to Step 5.3.

Step 5.3 – Identify unassigned pavements

The Facility Map Development Team identifies any pavements that do not have an assigned facility number. The team will follow the standards outlined in this playbook for designating pavement facilities and use its best judgment to determine the geospatial extents of the facilities on the map. The GeoBase Office representative tracks any changes and updates the GeoBase pavement facility layer.

The GeoBase Office tracks any changes by adjusting the pavement facility layer. The team will draft a mapping in various formats and post to a central repository.

Proceed to Step 5.4.

Step 5.4 – Verify current use and CATCODE

The team verifies the CATCODEs for each pavement facility are accurate based on current use. The team should refer to AFMAN 32-1084, Facility Requirements for CATCODE guidance. RPO guidance is to use the closest six-digit CATCODE available.

Once the CATCODEs are verified and the team has no more changes to the pavements facility map, the final map will be posted to the GeoBase system of record. During pavement evaluations, the facility map will also be provided to the Airfield Pavement Evaluation (APE) Team and/or one of their consultants for them to assign the segments to the facilities. Note that substantiating documentation for any facility changes will not be completed until after segments are assigned to the facilities and the map is validated with a pavement condition survey as outlined in Process 6.0.

Once Process 6.0 is completed, supporting documentation is generated and the RP records are updated in Process 11.0.

Below are the specific tasks by role to be completed during the verification of current use and CATCODE assignment:

RPO: Verifies that the CATCODEs are correct according to the RP records and designated current use GeoBase Office: Ensures that the mapping complies with Spatial Data Standards for Facilities, Infrastructure, and Environment (SDSFIE) 3.0 Pavement Engineer: Identifies any conflicts between the Pavement Condition Index (PCI) survey / pavement evaluation records and the pavement facility map. Additionally, the Pavement Engineer provides information on current designation/use of airfield pavements

Airfield Manager: Provides information on current designation/use of airfield pavements

Proceed to Process 6.0 Implement Pavements Segmentation Rules.

o AFI 32-1041, Airfield Pavement Evaluation Program o AFI 32-9005, Real Property Accounting and Reporting o Air Force Linear Segmentation Guidance Memorandum (1 April 2013) o AFMAN 32-1084, Facility Requirements

FA4610-18-T-0012

o UFC 01-300-08, Criteria for Transfer and Acceptance of DoD Real Property o UFC 03-250-01FA, Pavement Design for Roads, Streets, Walks, and Open Storage Areas o UFC 03-250-18FA, General Provisions and Geometric Design for Roads, Streets, Walks, and Open

Storage Areas o UFC 03-260-03, Airfield Pavement Evaluation

Pavement Facility Designation Process and Standards

The Facility Map Development Team should start with the common installation picture for the airfield. The team should show all load bearing pavement, as well as shoulders and any roads or parking areas. While roads and parking areas are not included in the airfield network, they serve as good reference points. The team should label any known pavement facility numbers, as well as any information such as apron, taxiway, and runway names.

Including buildings with building numbers can be beneficial as RP record cards often reference the building with which a specific pavement is associated. If possible, this map should be created such that the vector data is overlaid on the imagery for the base. If this is not possible, the team should at least have a hard copy of the most current imagery or the ability to project the image on a screen in the room in which it will be working

Other essential information includes a RP report listing all of the pavement facilities sorted by facility number with the CATCODE, category name, area, and any descriptions or notes that may be included in the RP database.

The team should include a complete list of pavement CATCODEs with the definition for each category

In addition, maps from the last PCI survey, as well as the construction history from the last PCI report and the last structural pavement evaluation are needed. Note that it may be beneficial to include the branch and section information from the last PCI on the map described above. This will aid in determining where natural breaks are for any unknown facilities

Once all relevant information is accumulated, the process is straightforward. The team should go down the list of pavement facility numbers identifying the extent of each facility on the map and labeling it with the facility number.

It is best if the person updating the GIS map marks up the hard copy and makes notes. When complete, the team updates the GeoBase Pavement Facility Map with the pavement facility numbers o Currently the primary constraint for creating a linear facility is that the user cannot mix CATCODEs.

For example, overruns (CATCODE 111115) cannot be combined in a facility with the main load bearing surface of the runway (CATCODE 111111). The facility is not only tied to the CATCODE but also to other things as outlined in AFI 32-9005, such as when it was originally constructed and construction type. With that said, over time, rules for determining pavement facilities have been applied differently at any given base, so there is a lot of variation from location to location o Runways and Overruns: Runway pavements are typically well-defined and should not pose any significant issues. Typically each runway at a base has its own facility number and the overruns for the runway have a separate facility number. Simply outline or highlight the areas and label them with the correct facility number. Runway shoulders should be identified and labeled as well. The runway shoulders should be a separate facility as well. But, many bases may have all shoulders for runways, aprons, and taxiways included in one facility. If the team developing the pavement facility plan needs to make changes to runway facility numbers, the best solution is to have a facility number for the load bearing surface of each runway. The two overruns for each runway will have one facility number, and the shoulders for all runways will have a facility number. Ensure that each facility has the correct CATCODE assigned in the RP record o Runway and Overrun Standard: If the team developing the pavement facility plan makes updates or changes to runway facility designations, they will create a facility number for the load bearing surface

FA4610-18-T-0012

of each runway. The two overruns for each runway will have one facility number, and as a minimum the shoulders for all runways will have…