L-1_size-scope-complexity-summary_Amend-1_2016-09-09.pdf

TFM-2 SIR DTFAWA-16-R-00010 Amendment 1 Section L, Attachment L.1

Part III Section L-1:

TFM-2 Size, Scope and Complexity SummarySupplemental

The purpose of this document is to provide a summary additional information onof the size, scope and complexity of the work under this contract. Section C of the SIR comprises the full scope of work.

The Traffic Flow Management System (TFMS) supports the Federal Aviation Administration (FAA) Traffic Management personnel in providing efficiency-critical National Airspace System (NAS) services. Throughout each day, Traffic Managers use the TFMS to maintain near real-time situational awareness and predict areas which may experience congestion due to volume or capacity reductions or unusual demand increase. The TFMS is used to facilitate planning telecons every two hours to proactively plan impact mitigation strategies between the Air Traffic Control System Command Center (ATCSCC), Traffic Management Units (TMU) at all major Air Traffic Control (ATC) facilities (810 sites), and flight operators. TFMS remote sites are also located at other FAA and Govt. offices (39).

The TFMS supports strategic and tactical Traffic Flow Management (TFM) 24/7/365. It does this under all conditions, but becomes especially important when external factors such as adverse weather reduces NAS capacity and require proactive planning, coordination and adjustments to mitigate impacts, e.g., missed connections, canceled flights, increased fuel consumption, etc. The ATCSCC uses the TFMS to model and implement NAS-wide Traffic Management Initiatives (TMI) to make the most efficient use of available capacity to avoid gridlock and minimize delays. When delays are necessary, TFMS assigns departure times equitably and gives flight operators flexibility though submission of trajectory options and departure slot substitutions.

If core TFMS services were lost, the immediate impact would be greatly reduced national situational awareness, forcing TFM personnel to revert to contingency procedures limited to local situational awareness and ad hoc coordination across the NAS with reduced system efficiency, less flight operator flexibility, and increased probability of gridlock at major airports across the country.

Some TFMS products are also used by other FAA offices, Government agencies and flight operators who participate in Collaborative Decision Making (CDM), see http://cdm.fly.faa.gov.

The TFMS is also the FAA’s primary provider of flight information to the public, see http://www.fly.faa.gov. TFMS has 30 different applications users may interact with. Please refer to the J-3 Attachment, TFMS Functional Description, for more summary information on the TFMS products, tools, services and users.

The TFMS receives data on planned and active flights from various sources, forecasts demand for monitored NAS elements, and provides information and alerts to FAA users and other NAS stakeholders. Information on flights within the continental United States and inbound/outbound international flights is processed by the TFMS. Many industry vendors subscribe to non-sensitive TFMS data feeds. The TFMS has data interfaces with more than 30 FAA systems and external entities. Please refer to the J-2 Attachment, TFMS Interface Requirements Specification (IRS), for more information on TFMS external interfaces.

http://cdm.fly.faa.gov/ http://www.fly.faa.gov/

The TFMS is based on a multi-tiered, centralized Service Oriented Architecture (SOA) running custom application software (see tTable L-1-1 below) on commercial hardware and software infrastructure components, e.g., Java Enterprise Edition platform. Please refer to the J-3 Attachment, TFMS System/Subsystem Specification Document (SSDD), for more information.

The TFM Production Center (TPC), at the William J. Hughes Technical Center (WJHTC) in New Jersey, performs the core data processing and distribution of flight data functions. There is also a backup Disaster Recovery Center (DRC) in northern Virginia. Wide Area Network (WAN) services are provided via the FAA Telecommunications Infrastructure (FTI).

Key performance requirements include:

• The overall service Operational Availability must be at least 99.9% (including planned maintenance downtime).

• The system must process a minimum of 10,000 active flights concurrently.

• The system must support a minimum of 1,100 concurrent users with no degradation of performance.

The TFMS Service Desk operates 24/7/365 to monitor and control system components and help TFMS users with problems. This support is currently provided primarily by contract personnel onsite at the TPC known as System Management Console Operators (SMCO). The ATCSCC also has onsite contract technical support daily, Operational Support Specialists (OSS), from 0700 to 2300 Eastern Time. An average of 167 new service desk tickets were opened per month in calendar year 2015. An average of 34 per month were escalated to Second Level Engineering (SLE). See Tables L-1-2, L-1-3 and L-1-4 for a summary of required recurring system checks and actions performed by these operators/specialists.

The following provides additional information on system performance and support workload:

• Help desk contacts (calls, email, or other) average 250 per month.

• Tickets written average 105 per month with an average of 10 escalated to Second Level Engineering (SLE) support.

• TFMS outages average 6 per month (degradations not classified as outages are part of the incident ticket average).

• Database anomalies experienced average 10 per month.

• New thin client user/customer/clients average 20 per month.

• Current thin-client user accounts total 2,265.

• Security incidents average 5 per month.

• Work requests approved by the government (configuration changes, software/hardware modifications, adaptations, patches/releases, baseline changes) – configuration setting changes average 25 per month and patches average 4 per year.

• PTRs implemented for 2016 – 181.

• Engineering Changes implemented – average 2 per year.

• User/customer/client requests (other than PTRs and ECs) – average 25 per month.

• SLE tickets opened by in AIMS – average 30 per month.

• Tickets escalated from first to second level – average 10 per month.

• Ad-hoc problems resolved – average 40 per year.

• Change Requests opened/closed – 5 year average for open CRs is 830 and for closed CRs is 670.

• Software releases and patches – average 4 per year.

• Visits to TFMS sites – average 8 sites per year (excluding the ATCSCC, DRC &

FAAHQ).

• RCAs performed – average 6 per year.

Since there is no defined end state for TFMS, the FAA plans to continue incrementally adding functionality to TFMS in accordance with investment decisions. Two major TFMS releases are nominally planned for each calendar year with deployment in the spring and fall to avoid severe weather season and holiday moratoriums. Each release nominally requires several months of system engineering to develop updates to system-level requirements and design materials. The detailed design, development, integration test and deployment cycle is typically 18 24 months.

Concurrent work on some phase of four to five major releases is common.

Table L-1-1, TFMS Custom Application Code Summary

Note: DSI stands for Delivered Source Instruction – doesn’t include support and test tools. See Attachment J-1 for more abbreviations.

Application Total DSI Technology

DB-FSA 33,050 SQL

DB-IRIS 1,985 SQL

DB-NTML 134,206 SQL

DB-NTML Data Warehouse 71, 157 SQL DB-OpsNet 99,422 SQL DB-Playbook 36,943 SQL DB-TFMS Core 99,821 SQL

DSP 270,860 C/C++

FSA 38,527 Java FSM 145,759 Java NTML 239,617 Java Remote Site, misc. – Includes: autosend, email, prefset manager, nas.server, ftm, list server, rrsvr, rtr, watchdog, hadds_api

204,233 C/C++

Remote Site - Diverted Flight List 8,880 Java Remote Site - NAS Monitor 22,352 Java Remote Site RDPS 8,768 Java Remote Site - RJAM 86,063 Java Remote Site - DACS 8,259 C/C++ Remote Site - TSD 301,640 C/C++

RRIA 693,353 C/C++

Scripts 53,424 e.g., unix scripting, python, etc.

TFMS Core 804,379 Java TFMS Core Toplink Coded 155,846 Mix of Toplink mappings / SQL TFMS Core XML 59,407 XSD / XSLT TSS - Advisory 10,502 Java / Web Technologies TSS - ATCSCC Logs 15,507 Java / Scripts TSS - Common Web Infrastructure / JSPs 3,236 Java / Web Technologies TSS - Connection Pool Servlet 356 Java / Web Technologies TSS - Current Reroutes 5,195 Java / Web Technologies TSS - Current Restrictions 1,731 Java / Web Technologies TSS - CVRS 7,914 Java / Web Technologies TSS - DCR 1,337 Java / Web Technologies TSS - DTO Recap 412 Java / Web Technologies TSS - FlyFAA 25,002 Java / Web Technologies

Application Total DSI Technology TSS - GAAP 2,374 Java / Web Technologies TSS - GDP Coversheets 40,534 Java / Web Technologies TSS - NTML Integration 1,433 Java / Scripts TSS - OIS 23,592 Java / Web Technologies TSS - OPSNet 40,875 Java / Web Technologies TSS - Playbook 5,555 Java / Web Technologies TSS - QA Shift Survey 3,133 Java / Web Technologies TSS - RAT 2,338 Java / Web Technologies TSS - Request Tools 2.0 3,352 Java / Web Technologies TSS - RMGR 15,010 C / Visual Basic TSS - RMT 3,082 Java / Web Technologies TSS - RVSM 6,536 Java / Web Technologies TSS - SIR 1,973 Java / Web Technologies TSS - STMP 17,293 Java / Web Technologies TSS - Support Tools 16,080 Java / Visual Basic / VB Voice TSS - TCA 4,937 Java / Web Technologies TSS - Telcon 4,228 Java / Web Technologies

TSS - WDG SVR 11,274 C/C++

Grand Total 3,781,585

Table L-1-2 TPC SMCO Recurring System Checks and Actions

Task Due System Check 7am Daily OVO Check 8am Every 4 hours CTOP Report Generated/Sent Daily - After DSR-I System Check 9am Daily System Check 11am Daily OPSNET Reports 11:30am Weekdays OVO Check 12pm Every 4 hours System Check 1pm Daily System Check 3pm Daily OVO Check 4pm Every 4 hours System Check 5pm Daily Nightly Activity Email Daily WSI Satellite Check Daily 9-ACT-ASDI Check Multiple Daily Stat ZNY alerts Daily

Chiller checks Daily GTP (Day) Wednesdays SDB (Thur) Thursday am OAG (Thurs) [DRC (Friday)] Thursday am Monthly OPSNET Report 16th of Month System/Chiller 7pm Daily 7:15 Planning Telcon Daily OVO Check 8pm Every 4 hours System/Chiller 9pm Daily 9:15 Planning Telcon Daily System/Chiller 11pm Daily Run ./clean_ophran_rvrII.sh on sv10 Daily Run ./delete_reroute_history.sh Daily OVO Check Midnight Every 4 hours System/Chiller 1am Daily System/Chiller 3am Daily OVO Check 4am Daily System/Chiller 5am Daily OPSNET Daily AKAMAI Twice per Shift Hardware Checks Daily WSI Satellite Check Daily Service Desk Backups Daily Aocasvr400 Check Daily ASDI/OPSNET Mail Check Every 4 hours Reboot DCC Operational Workstations Daily/Monthly Backup bocbsv50 Daily Restart Public Webservers Daily Database Data Purge Check Daily Run Close-wait diagnostic script Monday Adaptation Removal Monday Restart FAA & EXT Oracle Containers Monday DRC Adaptation Removal Tuesday Restart DRC Containers Tuesday GTP (Night) Wednesday OAG FPSD (Thurs) Thursday DRC Adaptation Thursday

Restart Oracle Containers Thursday Check archiving (dctaux760) Friday 0500z (1AM) Restart TAP 1 & 2 Containers and JAPIs Friday Restart TAP 3 & 4 Containers and JAPIs Saturday Restart TAP 5 & 6 Containers and JAPIs Sunday OID Sync from OPS to DRC Sunday Run portRVR-TFMDI.sh after OID Sync Sunday ERAM testing w/Hadds issues When Tested Oracle Discover Restarts Monthly (End of Month) SD Server Reboot (tpcsvr551) Monthly (End of Month)

Table L-1-3 TPC SMCO Additional Recurring System Checks and Actions Performed at Night

Monday TFMS Adaptation Removal (STF, AOCA, BOCB) FAA & Ext Portal Subsystem Container Restarts BIRT (Tomcat) Server Restarts Advisory Threading Webservers Restarts Tuesday DRC Container Restarts TFMS DRC Adaptation Removal BIRT (Tomcat) Server Restarts Advisory Threading Webservers Restarts Wednesday TFMS Weekly Site Configuration Update BIRT (Tomcat) Server Restarts Advisory Threading Webservers Restarts Thursday TFMS Core Container Restarts TFMS DRC Weekly Site Configuration Update BIRT (Tomcat) Server Restarts Advisory Threading Webservers Restarts Friday BIRT (Tomcat) Server Restarts Advisory Threading Webservers Restarts

Saturday BIRT (Tomcat) Server Restarts Advisory Threading Webservers Restarts Sunday OID Synchronization from OPS to DRC TAPS Container and Japi Restarts (TAPS 5 & 6) BIRT (Tomcat) Server Restarts Advisory Threading Webservers Restarts Monthly (End of Month) Oracle Discoverer Restart (dcted8608) SD Server Reboot (tpcsvr551) On second of the month, send rria_metrics.csv from /tmp on tpcsv50 $dccops/$dccops2/$EOF file server switch and reboot Oracle Core Database Restarts (1st Friday) Oracle TSS Database Restarts (2nd Friday)

Table L-1-4 ATCSCC OSS Recurring System Checks and Actions

Daily Shift Start Checks (6am) Daily System Check 10am Daily System Check 2pm Daily System Check 6pm Daily Clear Email Notify Window (all nodes) Daily Daily Automation Issues email sent (Close of shift) Daily