Below is the uncorrected machine-read text of this chapter, intended to provide our own search engines and external engines with highly rich, chapter-representative searchable text of each book. Because it is UNCORRECTED material, please consider the following text as a useful but insufficient proxy for the authoritative book pages.
132 A P P E N D I X B CONOPS Template CONCEPT OF OPERATIONS FOR AIRPORT NAME ________________________________________ Airport Director Date: ________________________________________ Project Manager Date: ________________________________________ ACC Manager Date:
CONOPS Template 133 Record of Reviews and Changes Change ID Date Reviewed Date Approved Comment Signature
134 Guidance for Planning, Design, and Operations of Airport Communications Centers Concept of Operations TABLE OF CONTENTS Executive Summary 1. Mission Description 2. ACC Operational Context and Architecture 3. Organizational System Drivers and Constraints 4. Center Functions 5. Operational Scenarios 6. Implementation Concepts and Rationale 7. ACC Operational Architecture 8. Organizational and Business Impact 9. Risks and Technology Readiness Assessment 10. Notes 11. Appendices
CONOPS Template 135 Executive Summary 1. Mission Description 1.1 Mission Statement A succinct one- to two-paragraph statement which embodies the purpose and function of the ACC. It will be used continually when adding new functionality to the center. 1.2 ACC Goals and Objectives 1.3 ACC System Architecture This section describes the current systems operating in the ACC and includes the following: ⢠The operational environment and its characteristics ⢠Major system components and the interconnections among these components, operational nodes, activities performed at each node, and connectivity and information ï¬ow between nodes ⢠Interfaces to external systems or procedures ⢠⢠Capabilities or functions of current systems, including activities and relationships among activities, inputs and outputs, constraints, and mechanisms that perform those activities. Charts and accompanying descriptions depicting inputs, outputs, data ï¬ow, and manual and automated processes suï¬cient to understand the current system or situation from the userâs point of view ⢠(Optional) Performance characteristics (e.g., speed, throughput, volume, and frequency of individual systems ) ⢠(Optional) Quality attributes (e.g., reliability, maintainability, availability, ï¬exibility, portability, usability, and eï¬ciency ) ⢠(Optional) Provisions for safety, security, privacy, and continuity of operations in emergencies 2. ACC Operational Context and Architecture The Executive Summary, usually around two pages long, should summarize the purpose of the document, including any guidance which is meaningful to the preparation and approval process of the CONOPS. The Executive Summary focuses the stakeholderâs attention on the most important aspects of the CONOPS document and provides suï¬cient information for the executive decisionmaker to understand the purpose and contents of this conceptual document. The ACC operational context clariï¬es the boundaries of the center as it is being conceived. This section describes the placement of the ACC within the airport organizational structure, types of users or personnel contained within the ACC, training and skill required, responsibilities, activities, and interactions with one another. This section also includes a Command Relationship Chart detailing the command, control, and coordination of all organizational components in the ACC. The Mission Description is an overview of the ACCâs goals and objectives, underlying mission and business rationale, the current (As Is) Architecture, a list of key stakeholders and expectations, and the current gaps in capabilities that require resolution. It also looks at the future of the ACC and begins to lay the framework for potential expansion of the ACC as the mission evolves. Enter Airport Managementâs Goals for the ACC. These are broad-ranging statements which describe the ultimate achievements that management is seeking with the ACC. For each goal, enter the concrete objective(s) to be attained within the overall goal statement.
136 Guidance for Planning, Design, and Operations of Airport Communications Centers In this section, the following six components should be addressed: ⢠Current functional components of the ACC ⢠Current organizations, roles, and responsibilities ⢠Current policies, including regulations, procedures, and standards of all entities which may govern activities in the ACC, including the airport, the FAA, and NIMS ⢠Projected ACC performance drivers ⢠Existing communication protocols and standards and intended modiï¬cations ⢠Current and projected personnel numbers, skills, and competencies 3. Organizational System Drivers and Constraints 3.1 Outline the Airport Operational Approach Identify the airportâs approach to operational management, situational awareness, and other functions being operated from the ACC. 3.2 Legal Requirements Speciï¬cally Related to the ACC List all legal requirements that apply to the ACC. 3.3 Identify External Airport Organizations That Support the ACC and Describe Their Roles List all entities external to the airport that may have a role in working with the ACC, including IROP and emergencies 3.4 Identify Any Organizational Constraints that Impact the Entire ACC 4. Center Functions 4.1 Individual Center Functions This section will include an entry for each of the functions (see Appendix C) contained within the ACC and the following sections will be repeated for every function: ⢠Function Title ⢠Detailed description of the function. This paragraph provides a detailed description of the function and should include, as applicable: A description of the function The functionâs operational environment and its characteristics Operational Scenarios, including the situational awareness template, where applicable. Include one or more operational scenarios that describe the role of the function and its interaction within the airportâs internal and external stakeholders. The scenarios should include events, actions, stimuli, information, interactions, and so forth, as applicable. ⢠Related CONOPS Functions. List any other function managed in the ACC that has a tangential relationship to the function. ⢠Related Airport Functions. List any other function managed elsewhere in the airport that has a tangential relationship to the function. ⢠Information Foundation. Include all of the following: â â â â Inputs to the function from systems, reports, regularly scheduled meetings, including interfaces to external systems or procedures â All outputs from the function
CONOPS Template 137 5. Operational Scenarios 6. Implementation Concepts and Rationale Describe how the ACC was developed and the rationale used to justify its development. 7. ACC Operational Architecture 8. Organizational and Business Impact 9. Risks and Technology Readiness Assessment Include either the initial risk assessment developed for the ACC or the most current risk assessment. 10. Notes This section may contain any general information that aids in understanding the CONOPS for the ACC. 11. Appendices Appendices may be used to provide additional information related to the ACC. â Constraints or obstacles that aï¬ect the function - This paragraph describes any operational policies and constraints that apply to the function â The primary manager of the function and their reporting structure â The roles and responsibilities of all airport staï¬ responsible for the proper execution of the function â The intended outcome of the function â describe the airportâs intended successful objective in performing this function, including goal and related objectives â Performance metrics which measure a successful outcome for the function â list performance indicators which identify a success level for the function List any major scenarios that aï¬ect the ACC in its entirety. For example, list all situations which the airport considers as a âmajor event.â Describe the ACC in a graphical representation, depicting all of the information ï¬ows, systems, and inputs and outputs. Include the interface to non-ACC systems where relevant. Describe airport managementâs view on the eï¬ect that it expects the ACC to have on the business of the airport organization and its stakeholders (e.g., community, airlines, and concessionaires).