JO_6000_53E_RMMC_April 2022 (003).pdf

U.S. DEPARTMENT OF TRANSPORTATION

FEDERAL AVIATION ADMINISTRATION

Air Traffic Organization Policy

Effective Date:

04/15/2022

SUBJ: Remote Maintenance Monitoring and Control Interface Development and Implementation

1. Purpose of This Order. This order defines the requirements for providing Remote Maintenance Monitoring and Control (RMMC) capabilities as well as the roles and responsibilities for developing, implementing and integrating the RMMC interfaces for National Airspace System (NAS) systems and services. Refer to Appendix A, Administrative Information, for additional information (i.e., definitions, acronyms and related publications).

2. Audience. This order applies to any Federal Aviation Administration (FAA) office that procures, installs, implements, and/or supports systems and/or services for the

NAS.

3. Where Can I Find This Order. You can find an electronic copy of this order on the Directives Management System (DMS) website: https://employees.faa.gov/tools resources/orders notices/. Or, go to the MyFAA Employee website, select ‘Tools and Resources’, then select ‘Orders and Notices’. You may also find this order on the Technical Operations (Tech Ops) Directives Information System (DIS) website at http://dis.faa.gov/.

4. What This Order Cancels. This order cancels and replaces Order JO 6000.53D, Remote Maintenance Monitoring Interface Development and Implementation, dated June 30, 2016.

5. Explanation of Policy Changes. The purpose of this revision is to emphasize the necessity of RMMC requirements for all NAS systems and services and significantly reduce instances where RMMC is waivered. These changes include:

a. Updated requirements for implementing RMMC capabilities for all NAS systems and services,

b. Updated roles and responsibilities, and

c. Revised appendices, added appendix C, which provides context for this RMMC order’s monitoring needs and requirements, and articulates the actions Operations Support is taking to further the Tech Ops Strategic Plan – Recharting the Future with regard to current and future Tech Ops monitoring.

Distribution: Electronic Initiated By: AJW-131

ORDER

JO 6000.53E

https://emplovees.faa.gov/tools http://dis.faa.gov/

JO 6000.53E 04/15/2022

6. RMMC. The evolution of Next Generation (NextGen) in the NAS has precipitated the expansion of Tech Ops monitoring requirements beyond its individual system RMMC capabilities. RMMC now provides the ability to remotely monitor and control (M&C) independent NAS systems and services. RMMC has expanded this capability to include enterprise service monitoring across multiple NAS systems and services.

RMMC has expanded its capabilities into the following three categories:

a. Independent system monitoring and control capabilities

b. Enterprise system monitoring and control capabilities

c. Enterprise service monitoring and control capabilities

Note: The term ‘control’ (as determined by RMMC), is defined as: A system’s/services’s ability to ingest, and process a ‘command request’. At a minimum, control capabilities consist of the issuance of a ‘command request’ to obtain the current state (status) of a system/service. The scope of a ‘command request’ ranges from requesting the current status of a system/service to controlling parameters, or resetting a system/service.

RMMC provides Tech Ops the capability to perform one or more of the following monitor and/or control functions from a remote location.

a. Monitor system status and alarms

b. Manage and control system configuration

c. Perform fault detection, isolation and restoration

d. Conduct trend analysis of system performance (including predictive maintenance and RCM)

e. Perform corrective and periodic maintenance

f. Perform certification

7. Candidates for RMMC Capabilities.

a. All new FAA-owned NAS systems or services, referred to by Facility Service and Equipment Profile (FSEP), that the FAA must monitor, provide maintenance oversight, or certify due to contractual or operational requirements must implement RMMC interfaces approved by the Maintenance Automation Team (MAT) AJW-131.

b. All new contractor provided NAS systems, services, referred to by FSEP, or provisional services that the FAA must monitor, provide maintenance oversight, or certify due to contractual or operational requirements must implement MAT approved RMMC interfaces.

c. Existing NAS systems and services that implement a Service Life Extension

Program (SLEP) or technical refresh effort must ensure the inclusion of RMMC functionality. NAS systems and services that currently have an RMMC waiver will be re-evaluated during SLEP or technical refresh.

d. Existing NAS systems and services that have implemented RMMC capabilities at limited fielded locations must coordinate with the MAT on completing the implementation of RMMC. The exception to this would be those NAS systems and services that currently have an RMMC waiver for limited RMMC implementation.

e. If existing NAS systems or services currently retain an RMMC waiver, and

Technical Operations determines such systems or services are required for enterprise monitoring purposes, then those systems or services must coordinate with the MAT on implementing RMMC functionality.

8. Roles and Responsibilities.

a. The MAT is the Air Traffic Organization Office of Primary Responsibility for providing oversight and ensuring RMMC is implemented on both legacy and new systems and services. The MAT shall collaborate with the NAS Integration and Support Group (NISG) In Service Managers (ISMs), NAS Security and Operations (NASEO), second level engineering organizations(s) or system owner(s), and individual Program Offices (PO) on RMMC requirements. The MAT will ensure there is conformance to RMMC Policies and provide oversight/guidance on common solutions that benefit the overall remote monitoring infrastructure. The MAT may establish and keep a record of Program Level Agreements with appropriate PO or system owner to ensure adequate funding is available for:

(1) Installing, connecting, conducting end-to-end testing, and implementing RMMC at the system/service location(s) and within the current FAA Tech Ops-operated M&C platform,

(2) Developing and sustaining the RMMC interface, including implementation and travel,

(3) Installing the RMMC communications circuits per FAA Order 1830.10, Managing New Telecommunications Requirements, and documentation (e.g., Maintenance technical documentation, MHBK, TI, etc.).

b. The NISG ISM serves as the primary Tech Ops lead for identifying, developing, delivering, and verifying Tech Ops RMMC requirements as systems and/or services are integrated into the NAS. The ISM coordinates between the appropriate PO or system owner and the MAT to ensure RMMC requirements, including Predictive Maintenance (pDM), are identifiedand satisfied. The NISG ISM shall ensure all aspects of the ‘NISG Acquisition Management System (AMS) Life Cycle Management, Standard Operating Procedures’ document are applied to RMMC implementation.

c. The implementing acquisition PO or system owner shall coordinate with the MAT and the appropriate NISG ISM to determine RMMC requirements for all legacy systems/services (undergoing upgrades/replacement of exiting installed equipment), and newly deployed (i.e., new investments) systems/services. This coordination must occur prior to developing the initial requirements and specifications for systems/services described above. For NAS systems and services that require RMMC, the PO or system owner must fund this effort to include but not limited to:

(1) Installing, connecting, conducting end-to-end testing, and implementing RMMC at the system/service location(s) and within the current FAA Tech Ops-operated M&C platform,

(2) Developing and sustaining the RMMC interface, including implementation and travel,

(3) Developing and presenting RMMC interface training as defined by the Tech Ops Training and Development Group,

(4) Installing the RMMC communications circuits per FAA Order 180.10 and documentation (e.g., Maintenance technical documentation, MHBK, TI, etc.)

If a NAS system/service requires RMMC capability, the PO or system owner must enter into a formal agreement with the MAT to detail the process for developing the RMMC interface and the roles and responsibilities of all parties involved. Appendix B outlines the process for developing a formal agreement for the RMMC interface. The PO or system owner coordinates with the ISM to ensure all Tech Ops RMMC requirements are satisfied.

9. Evaluation Criteria of RMMC Control Capabilities (all systems are required to have monitoring). The definition of control capabilities (as determined by RMMC) is found in Section 6 of this order. The stakeholders identified in appendix B will use the evaluation criteria shown below as a guideline to determine, initially, if RMMC control capabilities are required. This criterion will be applied as it pertains to individual system/service, as well as site-specific and enterprise monitoring.

a. System/service ability to accept and process control commands – Determine if this capability is native to the system/service, or complexity of implementing this capability.

b. Impact of implementing control commands – Evaluate any impacts (e.g., safety, security) or concerns of implementing this capability, as well as alternative means of obtaining status information (e.g., frequent updates from system/service).

c. Cost vs. benefit of implementing control commands – Evaluate the cost associated with implementing control capabilities, and the benefits obtained.

10. Waivers. Programs that anticipate failure to fulfill the RMMC requirement must request a waiver. Approvals for the requested waivers must be granted from the following prior to being presented to the Vice President of Technical Operations for signature.

a. MAT manager

b. NISG manager

c. Director of Operations Support

The NISG is required to keep the original documents on file. The MAT will post copies of the approved waivers on Knowledge Services Network.

A waiver granted under a previous investment no longer applies.

Prior waivers granted by the Director of Technical Operations may be evaluated as necessary to ensure compliance with this policy.

11. Exceptions. In some instances, a site identified as receiving equipment with RMMC capability may not provide the same operational benefit as another location. For these sites, the Tech Ops service area must submit a request for an exception to the MAT manager and/or NASEO for consideration. Requests for exceptions must explain the lack of RMMC benefit for that site and the plans to relocate the RMMC assets to a location where an increased operational benefit would be achieved. All requests for exceptions will be evaluated to determine both the cost and operational benefits of implementing RMMC at an individual location. The evaluation team consists of the following representatives with the responsibility for the facility(s) of interest:

a. Tech Ops service area

b. NASEO Control Centers

c. Service Operation Center

d. MAT

e. ISM

The MAT will review exceptions as necessary to ensure compliance with this policy.

Jeffrey S. Planty Vice President, Technical Operations Services

A-1

Appendix A

Appendix A. Administrative Information

1. Distribution. This order will be distributed electronically.

2. Definitions.

a. Enterprise. NAS and non-NAS related equipment and systems that are interconnected to provide a service.

b. Enterprise Service. Capabilities provided to the NAS by one or more enterprise systems.

c. Enterprise Service Monitoring. Monitoring data flow across interconnected NAS systems over FAA networks

d. Enterprise System. Any system that provides services to the NAS using geographically diverse, interdependent components connected by FAA networks.

e. Enterprise System Monitoring. Monitoring a single enterprise system.

f. Reliability Centered Maintenance (RCM). An analytical process used to develop efficient maintenance strategies to avoid or reduce the adverse consequences of failure on operational performance. The RCM ensures that an asset is performing within its acceptable parameters. The RCM effort reviews current maintenance activities and determines improvements in maintenance practices to help prevent failure or reduce the impact of failure in the NAS.

Appendix A 04/15/2022

A-2

Appendix A. Acronym List

DIS Directives Information System FAA Federal Aviation Administration FSEP Facility, Service & Equipment Profile ISM In-Service Manager JAI Joint Acceptance Inspection M&C Monitor and Control MAT Maintenance Automation Team NAS National Airspace System NASEO NAS Security and Enterprise Operations NextGen Next Generation NISG NAS Integration and Support Group NOTAM Notice to Airman OPR Office of Primary Responsibility PO Program Office RCM Reliability Centered Maintenance RMM Remote Maintenance Monitoring RMMC Remote Maintenance Monitoring and Control Tech Ops Technical Operations

Appendix A 04/15/2022

A-3

Appendix A. Related Publications

• FAA Order 1370.114, Implementation of Federal Aviation Administration (FAA) Telecommunications Infrastructure (FTI) Services and Information Security Requirements in the National Airspace System (NAS)

• FAA Order 1830.10, Managing New Telecommunications Requirements

• FAA Order 3900.57, Environmental and Occupational Safety and Health (EOSH)

• FAA Order 6000.5, Facility, Service, and Equipment Profile (FSEP), identifies the FSEP entry requirements.

• FAA Order 6000.15, General Maintenance Handbook for National Airspace (NAS) Facilities, identifies policy and procedures for using RMM for maintaining NAS facilities.

• FAA Order 6050.19G, Radio Spectrum Planning

• FAA Order 6000.30, National Airspace System (NAS) Maintenance Policy, identifies the RMM requirements for Technical Operations Services.

• FAA Order 1375.8, Guidance for Implementing Standardized Maintenance and Monitoring Data Exchanges

• FAA Order 6050.32, Spectrum Management Regulations and Procedures

• FAA Order 6000.56 (Draft), Oversight and Management of Leased and Provisioned Services

• Technical Operations Strategic Plan, Recharting the Course (2021)

Appendix B 04/15/2022

B-1

Appendix B. Developing a Formal Agreement for the RMMC Interface

As stated within this order, a Tech Ops representative from the MAT will enter into a formal agreement with the PO. At a minimum, the information below must be included in the formal agreement.

g. A stakeholders group, led by the MAT, will oversee and approve the development of the

RMMC interface. The MAT will ensure that the stakeholders (listed below) are involved in developing the RMMC interface.

(1) MAT (AJW-131)

(2) NASEO (AJW-B)

(3) Bargaining Unit Representative(s)

(4) Operations Support Team (AJW-141)

(5) NAS system program office

(6) Appropriate ISM

(7) Remote Maintenance Systems Engineering Team (AJW-175)

(8) Other Second Level support organizations or system owners as required

(9) Predictive Maintenance Lead (AJW-123)

(10) User community representatives, and

(11) Other stakeholders as required

h. To facilitate the effective development of the RMMC interface, the MAT will ensure that:

(1) The NAS Security and Cyber-Security teams review and approve this interface,

(2) The PO or system owner has satisfied the requirements to interface with the NESG (if applicable),

(3) The interface is developed per current Interface Requirements Documents

3.1 The interface utilizes the current data standard as identified in Order 1375.8, Guidance for Implementing Standardized Maintenance and Monitoring Data Exchanges

(4) The PO or system owner provides the necessary documentation (i.e., interface control documents) to develop the RMMC interface,

(5) The PO or system owner provides the necessary funding to develop and test the RMMC interface,

(6) The appropriate stakeholders or vendor(s) are tasked to build the interface,

(7) The appropriate interface is identified, Appendix B 04/15/2022

B-2

(8) The appropriate interface infrastructure, including cost, is identified,

(9) The appropriate monitoring data points are identified,

(10) FSEP, Maintenance Handbook, and other relevant changes are identified for implementation through the Program Office Integrated Logistics Management Team (inclusive of NISG ISM), and

(11) Schedules for the interface development and testing are established.

Appendix C

C-1

Appendix C. Technical Operations Monitoring Our Future 2022

TECHNICAL OPERATIONS

Monitoring our Future 2022

Appendix C 04/15/2022

C-2

Table of Contents

Executive Summary ................................................................................................................... C-3

Introduction ………………….…………………………….....….……………….……….......C-5

Simplified National Air Space 2018…………………….………………………….……..…..C-6

Current State of Monitoring……………………………………………….…………….….....C-7

STDDS & ASSC service flow from NAS Technical Reference Site….……….….......C-7

Future Monitoring, Risk Management, more Effective Decisions…………………….….......C-8

NAS Infrastructure Services (NIS) monitoring tool CPDLC services…………...…....C-9

Service Management…………………………………………………………………….…...C-10

Impact and Operational Risk Analysis…………………………………………………...…..C-10

Operational Risk Management for Technical Operations Core Principles……….......C-11

Improved Situational Awareness…………………………………………………………......C-12

NIS monitoring tool screenshots…………………………………………………......C-12

Maint Optimization, Predictive Maint, Enhanced Reliability Centered Maint……................C-12

Control……………………………………………………………………………………........C-14

Correlation to Air Traffic Operations…………………………………………………….......C-14

Technical Operations Monitoring Workforce……………………………………..................C-14

Data Analytics, Data Collection, Management and Ownership…………………...................C-15

Monitoring our Future 2022 – Advancing the Plan………………………………..................C-15

Table A: Monitoring Matrix………………………………………………………..…….......C-19

Table B: Tech Ops Pre-Acquisition and Monitoring Requirements Mapping……………….C-22

C-3

Executive Summary

Technical Operations has been tasked by the Administrator of the FAA with the mission of ensuring the NAS operates at the required level of service to ensure safe and efficient movement of aircraft. We perform this mission through modernization, integration, management, operation, and maintenance of air navigation services and infrastructure.

While the FAA has made tremendous progress in modernizing the NAS, Technical Operations strives to bring our vision of being the leader in management of air navigation services and infrastructure to everything we do. In turn, Technical Operations provides a gateway to new technologies bringing this vision into focus. This document begins defining the steps Technical Operations must take to achieve the FAA's and Technical Operations' strategic plans. It is intended to advance and support the key initiatives set forth in those plans.

The future of the NAS is service oriented. That is, NAS service oriented. Technical Operations can no longer be hardware or system centric. The implementation of service oriented architecture, cloud computing, and constantly changing needs of our stakeholders to be agile and flexible, requires that we arrive at this service centered approach sooner rather than later. The demand for our services and the ever-expanding complexity of the NAS requires that we accept and accommodate technological advancements quickly and with minimal negative impacts to the current users of the operational NAS. The FAA and Technical Operations must integrate new services with existing services while modernizing our infrastructure. Somewhat like trying to change a tire on a car while it's still moving, deployment must maintain the highest degree of safety and security possible. Our ability to monitor all of these services and every segment within each service must include enhancements that improve overall situational awareness, decision making capabilities, and the productivity of our workforce.

The Office of Inspector General Audit Report titled, FAA Oversight is Key for Contractor- Owned Air Traffic Control Systems that are not Certified, AV-2011-149, dated August 4, 2011, stated the FAA is solely responsible for maintaining the safety and integrity of the NAS.

Technical Operations is responsible for oversight of operational service contracts. This translates to: Technical Operations must be able to monitor, identify, and manage any service within the operational NAS that is negatively impacting the performance of any service segment within the NAS. This encompasses both FAA-owned and managed services, as well as non-Fed services, and those services owned or leased by contractors and/or vendors. This requires standardized and integrated monitoring capabilities that include FAA-owned and managed data which provides the end-to-end NAS performance and situational awareness needed to make real-time operational decisions that protect and safeguard all operational services within the NAS. This end-to-end NAS service monitoring capability must also include the ability to determine operational impacts of one service on another, as well as the impacts on the NAS as a whole. Technical Operations’

C-4 monitoring capabilities will continue to need and indeed, must, include equipment and system-level performance status while adding service and situational awareness and impact status of all NAS operations. The FAA and Technical Operations must not solely rely on the reports or the status provided by vendors, contractors, or non-Fed entities. Our monitoring capabilities must include the ability for Technical Operations to independently monitor and confirm the health and performance status of all NAS services, as well as any service that has the potential to impact the

NAS.

The purpose of this document is to articulate and set into motion, actions being taken by Technical Operations to move forward the strategies and visions described in Charting the FAA's Future Fiscal Year (FY) 22-26 and the Technical Operations Strategic Plan 2021 – Recharting the Course. Our ability to monitor the health and performance of all operational NAS services and any other services that have the potential to impact or alter the performance of the operational NAS is paramount. We cannot fulfill our organizational mission without the ability to see every segment end-to-end of all services within the NAS.

The Administrator established Four Pillars, or goals to guide the FAA over the next several years:

1.Safety, 2. People, 3. Global Leadership, and 4. Operational Excellence.

Those Pillars then drove the creation of the Technical Operations Strategic Plan 2021 – Recharting the Course. Technical Operations Strategic Plan 2021 has five strategic focus areas:

1. Organizational Transformation, 2. Stakeholder Engagement, 3. Innovative Solutions, 4. Future Workplace, and 5. Workforce Investment.

This document describes the current and future Technical Operations monitoring environments. It explains the monitoring functions and capabilities that are required to fulfill

Charting the FAA's Future FY 22-26

Technical Operations Strategic Plan 2021 – Recharting the Course

Technical Operations – Monitoring the Future 2022

C-5 the tasks and responsibilities of Technical Operations. It informs all Technical operations' employees, partners, and stakeholders of our future direction, and outlines in general terms, the activities required to move from where we are now to where we need to be to achieve our monitoring vision of: "Monitoring systems will be used to provide real-time and predictive homogeneous information needed to accomplish system and equipment maintenance, troubleshoot service threads, and ensure service is available when needed." The focus areas required to positively impact our ability to achieve this vision are:

1. Provide real-time and predictive homogeneous information shared by monitoring systems; 2.

Accomplish service, system, and equipment maintenance via a service monitoring system; 3.

Troubleshoot service threads to determine and isolate the service anomaly; 4. Correlate NAS service status, to include NAS infrastructure status, Air Traffic operations status, and other impacting factors to determine impact to the operational NAS; and 5. Update policy and metrics to reflect service availability and the current state of the operational NAS when needed.

Introduction

The NAS of the future is expected to be service centric. Data generated by NAS will no longer be provided only to the local air traffic control facility. It will be collected, packaged, and provided to multiple users both within and outside the FAA. NAS services are being deployed as non-governmental sources, driving the need for enhanced oversight. The screenshot of the "Simplified National Airspace System 2018" on the next page, readily shows the complexity of the NAS network. It also provides an idea of the challenges our monitoring workforce has with regard to monitoring the health and performance status of the NAS network. It is our responsibility to provide the workforce with the monitoring tools they need to do the tasks assigned to them. Our workforce must be able to monitor, troubleshoot and isolate any segment within the NAS that is not performing as expected. And, if necessary, shut down that segment to ensure no negative impacts are propagated by it to any other services within the NAS.

Integrated NAS-wide monitoring capabilities require standardization to improve the data access needed for enhanced decision-making and oversight. Monitoring systems continue to include equipment maintenance while adding service status and situational awareness of NAS operations.

It includes monitoring oversight systems used to provide awareness of leased equipment and services, as well as any non-fed equipment determined to require RMMC capabilities. This integrated monitoring capability will also include an operational impact function which will be used to implement the "service when needed" philosophy.

The tables in this document are provided to highlight organizational monitoring uses, responsibilities, and notional requirements. In the future, separate, more detailed documents may be needed. At that time, the tables may no longer be needed in this document and this document can be updated to reflect those changes.

C-6

This document describes high-level Technical Operations monitoring needs and activities. As programs mature within the AMS process, it is expected that companion documents will be created that define more detailed, program specific Technical Operations monitoring requirements.

AJW-1’s ISMs will be actively involved, in partnership and working collaboratively with Program Management Office (PMO) staff in developing these requirements. Examples of this might be detailed monitoring needs and requirements associated with RMMC, RCM, Remote Maintenance Logging System (RMLS) and program interfaces to RMLS, data analytics, data harvesting, data sharing, etc.

C-7

Current State of Monitoring

Below are screenshots taken from the NAS Technical Reference Site. These are just two of tens of thousands of NAS services Technical Operations are responsible for monitoring. These screenshots highlight the multitude of potential services and users that could be impacted by a poor performing segment within the end-to-end NAS service.

Today's monitoring systems act independently since they were developed to monitor performance of a specific system. They include data points needed to determine the status of equipment to the Lowest Replacement Unit level. They also provide control of the system for resets, reconfiguration, adjustments, and software loads. Some current monitoring systems provide oversight of vendor provided services.

Much of the remote maintenance monitoring (RMM) that is needed has not yet been implemented.

Due to this incomplete implementation, we have missing data and are left unable to monitor many segments within the end-to-end NAS service. A wide variance in approaches to collecting the needed RMM data must be considered and implemented to ensure all needed data and data points are available.

These systems lack a common language and protocol. In order to determine the cause of a NAS service interruption, protocol analyzes information from several of these monitoring systems.

The RMLS provides a common user interface to systems that are connected and used for remote monitoring and maintenance.

These monitoring systems are used by Technical Operations Control Center (TOCC) specialists and others. They use the monitoring systems to provide continuous monitoring of NAS services.

The TOCC includes:

• Service Operations Centers

• Operations Control Centers

• Enterprise Control Centers

• Operations Enterprise Control

C-8

• Network Enterprise Management Center

• NAS Cyber Operations

• Wide Area Augmentation System Operations, and

• Enterprise Data Services System Support Center (SSC).

SSC specialists use these monitoring systems to provide 1st-level maintenance of NAS systems and equipment, including but not limited to; corrective maintenance, preventative maintenance, certification, and system operator functions.

SSCs, districts, and TOCCs need to be able to reassign maintenance responsibilities to personnel at various geographic locations or control centers. Technical Operations monitoring capabilities must support the ability for this Technical Operations need to be fulfilled.

Technical Services and 2nd-Level Engineering also use monitoring systems to assist in troubleshooting and restoration of systems.

Future Monitoring, Risk Management, more Effective Decisions

Each newly deployed system integrated into a monitor of monitors (overall NAS status type monitor) will implement the monitoring capability that provides end-to-end service monitoring.

The capability will provide several levels of NAS situational awareness including lower-level (system) status information into higher-level service status indications. In addition to the maintenance functions provided today, monitoring systems in the future will include service and situational awareness, control functions including service, system, and equipment regardless of whether they are FAA owned and managed or vendor leased or owned. Control functions will be evaluated and implemented on an individual equipment, system and service basis. All service, system, and equipment status will provide information to be ingested by the Technical Operations operational NAS service monitoring tool(s).

Current RMLS monitoring is focused on equipment using the Maintenance Automation System Software (MASS) application and the NAS Infrastructure Services (NIS) monitoring tool. The Automated Maintenance Management System is introducing new tools expected to replace MASS. Current monitoring tools will likely change names and/or be replaced or upgraded.

Throughout this document MASS and NIS will refer to the current applications and tools, as well as the future applications and tools or suite of applications that may enhance or replace any current monitoring functionality, regardless of what they are called in the future.

NextGen and other new services are much more complex with different components of the end-to-end service being maintained and managed by different entities and systems. This complexity is what drives the need for end-to-end service centric monitoring. The equipment and system status information is still vitally important, but they are only pieces of the NAS puzzle. Future monitoring capabilities require the ability to see the entire NAS. NIS allows logical service flows to be built to define the status of a service and its components.

C-9

The services can then be displayed in whatever manner meets the needs of the user. The screenshot below is taken from the NIS monitoring tool and shows a Controller Pilot Data Link Communications (CPDLC) service – note the multiple NAS systems and data segments required to display the complete end-to-end CPDLC service.

To facilitate the building of logical data flows, a common data exchange model must be used. A host of diverse systems within the NAS make an abundance of data elements available for consumers within the realm of Operations and Maintenance (O&M). Applying these various data elements into an accepted exchange model establishes data element names, definitions and formatting rules, thereby allowing the efficient sharing of data with NIS and other monitoring tools and applications. With proper data elements identified and trusted, data can be searched and displayed dynamically. The FAA established Order 1375.8, Guidance for Implementing Standardized Maintenance and Monitoring Data Exchanges, to provide the format and standard for the exchange of O&M data.

Future monitoring solutions will require sustainable common solutions. The data content and format will be as directed by the current monitoring requirements of Technical Operations, the National Monitoring Team, the Maintenance Automation Team (MAT, AJW-131) and the NAS Security Enterprise Operations directorate (AJW-B).

C-10

Order 6000.15, General Maintenance Handbook, along with its appendixes, Order JO 6000.53, Remote Maintenance Monitoring and Control Interface Development, and others are guiding documents for Technical Operations maintenance and monitoring capability requirements.

Technical Operations directorates, in particular, the Technical Operations ISMs within AJW-13, in partnership and collaboration with NextGen (ANG) and PMO groups and teams, work together to ensure program requirements fulfill the needs this document describes. Meeting the needs outlined is very important in ensuring successful program implementation and deployment. Systems and services deployed and operating within the operational NAS using these monitoring capabilities, effective NAS management, service monitoring, maintenance optimization, predictive maintenance, situational awareness, and risk management will allow for more effective decisions when determining risk to the operational performance of all NAS services. This monitoring status provides invaluable information to the ISMs and the larger Technical Operations community when mitigating risks, whether the risk is due to preventive and corrective maintenance or program implementation and deployment activities.

The NIS monitoring tool will be able to provide data to other monitoring tools and/or have the functionality itself to provide service status views for situational awareness, for correlation of NAS infrastructure anomalies, Air Traffic operations and other potential impacting factors thereby providing complete service performance and health status, as well as operational impacts to the NAS. This information can then be used to make more informed risk-based decisions regarding thestate of the NAS.

Service Management

Individual service monitors provide a service view of systems and equipment that make up an end-to-end service. Some examples of that are DataComm and System Wide Information Management. Technical Operations may also embed the maintenance function into the service monitor. The system will provide high-level end-to-end service status to the NIS monitoring tool.

The NIS monitoring tool displays each NAS service status using data points such as system alarms, telecommunication status messages, service status, and NAS maintenance logs. The system will report service status as full service, reduced service, loss of service, or unmonitored and can share the status with other situational awareness and impact generator applications.

Impact and Operational Risk Management Analysis

All maintenance activities that could impact equipment, systems, and/or services will be coordinated through operations using a dynamic and predictive NAS impact generator and operational risk model to evaluate each maintenance request. The impact and operational risk analysis generator will interface with operational NAS systems and aeronautical information systems to predict impacts to NAS operations. Generator outputs will identify anomalies and service interruptions for geographical areas, routes, and procedures that are affected and available from anywhere there is connectivity.

C-11

Output can vary depending on the user's role and will be customizable to the user's needs. The output will describe impacts as service interruptions or degradations, rather than equipment or system specific. In addition, capability to run scenarios for predictive impacts will be provided.

The Technical Operations workforce will prioritize restorations based on safety and service impacts and may allow delayed restoration based on an operational risk model. An operational risk management tool will be developed and will be utilized, taking into account, safety, security redundant services, passenger impact, and NAS system efficiency.

The Technical Operations Operational Risk Management (ORM) core principles can be found at this link: ORM Core Principles and Considerations (faa.gov). Additional ORM information can be found on the ORM website at Operational Risk Management (faa.gov).

https://my.faa.gov/content/dam/myfaa/org/linebusiness/ato/operations/technical_operations/media/ORM/ORM_Core_Principles_and_Considerations.pdf https://my.faa.gov/org/linebusiness/ato/operations/Operational_Risk_Management.html

C-12

Improved Situational Awareness

A feature of the NIS monitoring tool includes improved situational awareness capability. The design will enable diverse teams composed of representatives from various Air Traffic Management organizations to collaborate on topics critical to effective and efficient air traffic service delivery. Our collaborative partnerships and real-time situational awareness are cornerstones to NAS operations and maintenance planning. Accurate and timely NAS situational awareness will reduce the impact of service anomalies on NAS operations.

It is important to note that all program implementation and/or deployment activities in the field require compliance with all Technical Operations ORM processes and principles. The link to those principles are shown on page C-11 of this document.

Maintenance Optimization, Predictive Maintenance, and Enhanced ReliabilityCentered Maintenance Individual systems, along with equipment and service monitoring tools provide NAS equipment, system, and service status. They assist in better decision making when scheduling and/or performing local and remote activities such as preventative and corrective maintenance, resets, reboots, etc. Other individual monitors provide status for oversight of leased services such as the Surveillance Broadcast System and FTI. Some systems provide status data to an optimized remote maintenance monitoring system.

These monitors provide high-level equipment and system status for the NIS monitoring tool consumption. Technical Operations monitoring tools must support the FAA's and

C-13

Technical Operations strategic plans. Some key activities from the Technical Operations StrategicPlan 2021 – Recharting the course, related to monitoring are:

• Expand the service management model, remote monitoring and maintenance strategies to all NAS systems,

• Continue the realignment of the monitoring of all NAS services and equipment within each Enroute airspace area within each Technical Operations District and standardize the operating procedures for control centers,

• Develop RMMC requirements for the retrieval and delivery of machine data directly from NAS systems for use in predictive maintenance,

• Implement standard maintenance applications for the management and monitoring of NAS service to improve event coordination.

What is predictive maintenance (PdM)? Predictive maintenance is work that is scheduled in the future based on analysis of sensor measurement and formulas. PdM predicts into the future when you will need to service your equipment. It is intended to be proactive rather than reactive. It eliminates the need and optimizes maintenance activities.

Currently, the RCM program addresses the consequences and cause of failures. Technical Operations uses it as a root cause analysis tool to determine the effectiveness and validity of scheduled preventative maintenance tasks. In the future, enhanced RCM is expected to automate the current process, expand the condition monitoring equipment to capture real time trending of in-service machine health (requires RMMC integration) and will use PdM to move from scheduled maintenance processes to a culture where artificial intelligence algorithms predict future failures which dictate optimized maintenance activities. A visual representation of where we are and where we are going might look like the following:

C-14

Control

This document describes and creates the core building blocks for Technical Operations to move to a more proliferated control posture. A control strategy is being pursued and is expected to be published in the future. In the meantime, current control capabilities are fully functional at this time to the extent allowable by the systems, equipment, and orders in place. While the implementation of control capability is not uniform across the NAS, it is expected that control functions will be proliferated among more and more services and systems in the future. In order to maintain a safe and secure operational NAS, it is imperative that Technical Operations have the ability to not only isolate a performance problem within the NAS but also manage it, if it has the potential to negatively impact other NAS services and/or the operational NAS itself. Control commands are evaluated and vetted per the RMMC Interface Development and Implementation Order JO 6000.53. The RMMC order language has evolved to require "Updated requirements for implementing RMMC capabilities for all NAS systems and services." This replaces the previous approach which stated, "All new systems and/or services must be evaluated for RMMC requirements per the evaluation criteria stated in this order."

Correlation to Air Traffic Operations

Air Traffic System Operations initiates Traffic Management Initiatives (TMI) based on factors impacting the flow of aircraft across the NAS. These factors include changes in weather conditions, NAS service status, and Air Traffic Control (ATC) facility status. The ground delay program uses TMI to issue miles in trails, ground stops, etc. NAS operational service status includes availability of surveillance from enroute and terminal radar facilities as well as Automatic Dependent Surveillance Broadcast. Navigation, another NAS operational service, includes approaches, fixes, and air routes. Both ground-based NAS infrastructure systems and satellite systems provide these operational services. FAA protocol reports ATC facility status as normal, limited, alert, and zero. ATC facilities change their status based on the same impacting factors as above plus local concerns such as staffing. The Traffic Flow Management System provides ATC facilities' arrival and departure rates and peak traffic periods. Other impacting factors on AT operations are current and forecast weather conditions, fires and other disasters. All of these factors and more are used to determine the operational status of the NAS.

Technical Operations Monitoring Workforce

The Technical Operations monitoring workforce includes, but is not limited to, the TOCC specialists, the SSC specialists, the Technical Services staff and engineers. This Technical Operations workforce may use more than one monitoring function based on the needs of their assigned task and responsibilities. Table A shows the relationship between these assigned tasks and responsibilities, current and planned applications, and the Technical Operations monitoring workforce.

C-15

Data Analytics, Data Collection, Management and Ownership

Accurate NAS status requires strict configuration management of the data used to define relationships between equipment, systems, and services. Order 1800.66, Configuration Management Policy includes well-defined requirements for all data elements. In order to ensure a safe and secure operational NAS, and manage the services operating in the NAS, the FAA and Technical Operations must own and collect the service data from all services, systems, and equipment. All systems and services, including vendor provided services, producing NAS information and data, must provide system and service status to be ingested into the NIS monitoring tool. The ISMs, while working with ANG and PMO, will address all new systems and services added to the NAS, for Technical Operations monitoring tool data collection needs and requirements. All new systems and services added to the NAS must use an information exchange model for O & M data. Order 1375.8 has been selected and is currently in use by the NIS monitoring tool.

Monitoring our Future 2022 –Advancing the Plan

This document supports and advances the strategic plans and visions laid out in the FAA's Charting the Future FY22-26 and Technical Operations Strategic Plan 2021 – Recharting the Course by implementing the following initiatives:

1. Provide real time and predictive homogeneous information shared by monitoring systems.

Continuous end-to-end monitoring of the NAS with the focus being on the NAS service will be one of the key factors in providing safe and secure NAS services when needed and will provide the timely and accurate situational awareness required to make informed risk- based decisions.

An integrated maintenance automation system along with the NIS monitoring tool will improve standardization and data access needed for more effective decision making and support our oversight responsibilities.

Current, accurate, and standardized data from all NAS services and systems is absolutely essential to informed decision making. Individual maintenance monitoring systems and services send status information to the NIS monitor. The NIS monitor provides a holistic view of the end-to-end NAS service status and is used to determine and isolate the segment of the service and the maintenance organization responsible for correcting the anomaly causing the degradation or interruption of the service. The data collected and displayed in the NIS monitor can then be used for predictive analysis when planning for maintenance or other types of work planned for the operational NAS network, such as software and hardware upgrades, just to name one example.

C-16

Predictive Maintenance will require an additional level of data to be collected from NAS field assets. In order to build robust predictive models, traditional RMMC capabilities will need to be updated where feasible in two main ways. First, connected assets will communicate real-time data at high-frequency (every second or minute instead of daily or on-demand). Second, data points will be recorded at the sensor level, sending unmodified system health data such as temperature, voltage, dampness, etc. Both of these updates will require sufficient technological capability both at the edge and in data storage to support the increased bandwidth long-term. AJW-123 has begun scoping this in increased infrastructure and working to outline the requirements.

2. Accomplish system and equipment maintenance via a monitoring system.

Currently, much of our monitoring is done via individual system maintenance monitor control systems within the local environment. Technical Operations is evolving and will continue to evolve from a culture of maintenance and troubleshooting performed primarily on-site and locally, to optimized maintenance, monitor and control capabilities. The NIS monitoring tool will be a key tool in this evolution. In addition, maintenance handbooks, technical instruction books as well as maintenance orders and policies will be updated and modified to support optimized maintenance, auto-logging, operational risk management, and risk-based decision making initiatives.

3. Troubleshoot service threads to determine system or segment responsible for aservice anomaly.

The maintenance automation system via the NIS tool provides NAS service level monitoring across geographic boundaries and systems, and includes services with multiple vendors, cloud services, networks, satellite, and cyber and physical security. The compilation of the local system and subsystem service and equipment health and performance statuses provides the state of the end-to-end service. The NIS tool is used to monitor and troubleshoot all service anomalies and will report these service statuses as full service, reduced service, loss of service, or unmonitored.

A drill down feature is available and can provide information on the specific alarm or log that generated the change in service status.

4. Correlate NAS infrastructure status, Air Traffic operation's status, and otherimpacting factors to determine operational impact.

The data collected from each of the NAS systems and services, including those that are leased, owned, and vendor-provided, will interface with operational NAS systems and aeronautical information systems and be used to predict impacts to NAS operations should any NAS service be reported as degraded or lost entirely. The impact generator outputs will identify anomalies and service interruptions for geographical areas, routes, and procedures affected by negative health and

C-17 performance issues. It can be used not only to show the current impacts but also in a predictive manner to achieve better planning and activity scheduling with less operational impacts to Technical Operations, Air Traffic, and other users of NAS data. The situational awareness monitor will provide real-time, accurate NAS operational status, filtering capability based on users roles, and can include:

• Core 30 airports

• ARTCC boundaries

• NOCC tracked events

• NAS services and/or major systems

A record and playback composite function is included with the NIS monitor which can be used to review actual cause and effect of any operational disruptions.