Attachment 1 - IDSR Section C (SOW) Market Survey.pdf

IDSR/NIDs Second Level Engineering and Software Maintenance

PART I - SECTION C

Statement of Work

IDSR/NIDS Second Level Engineering Software Maintenance

C-i

TABLE OF CONTENTS

C.1.1 Introduction

C.1.1.1 Background

C.1.1.2 Purpose

C.1.1.3 Scope

C.2.1 Applicable Documents

C.2.1.1 FAA Documents

C.3.1 Federal Standards

C.3.1.1 Obtaining Copies of Documents

C.3.2 Definitions

C.3.3 Required Tasks

C.3.3.1 General

C.3.3.2 Detailed Task Requirements C.3.3.2.1 Software Second Level Engineering Support C.3.3.2.2 TASK 1 – IDSR/ NIDS Maintenance Support C.3.3.2.3 TASK 2 – IDSR/NIDS Software Maintenance Support C.3.3.2.4 Software Configuration Management/Quality Assurance C.3.3.2.5 TASK 3 - Software Testing C.3.3.2.6 Test and Evaluation Support C.3.3.2.7 Test Conduct C.3.3.2.8 Test Tools C.3.3.2.9 Government Tests

C.3.4 TASK 4 - Other Engineering Support

C.3.5 Project Management

C.3.6 Discrepancy Reporting System

C.3.7 List of Deliverables

Acronyms

C-1

C.1.1 Introduction

C.1.1.1 Background

The Federal Aviation Administration Air Traffic Systems - En Route Operational Systems (AJM-25), have a requirement to provide second level engineering support to the Integrated Display System Replacement (IDSR), also referred to as National Airspace System Information Display Systems (NIDS).

C.1.1.2 Purpose

This Statement of Work (SOW) delineates the Contractor's work tasks required for software engineering services to support the IDSR NIDS software.

C.1.1.3 Scope

This SOW describes the requirements for the services to be provided under this contract for Second Level Engineering Support.

C.2.1 Applicable Documents

The following specifications, standards, instructions, orders, guidelines, and handbooks form a part of this SOW. The National Airspace System (NAS) is updated periodically, and, unless otherwise specified, the document to be used must be that listed in the latest issue of the FAA Index of Specifications or applicable System Support Directive (SSD) at the time of this solicitation. Unless separately cited in their own right, specification, standards, handbooks, and other documents referenced within cited documents are not considered as applicable documents for this SOW and must not be considered binding in any way in performance of the SOW.

In the event of a conflict between this SOW and a referenced document, the SOW must take precedence.

C.2.1.1 FAA Documents

Document Title

FAA Order 1600.54 FAA Automated Information Systems Security Handbook

FAA Order 6000.30 Policy for Maintenance of the NAS

ATS TEGS Air Traffic Services Test and Evaluation Gold Standard

FAA Order 1370.82 Information Systems Security Program

FAA 1600.1 Rev F Personnel Security Program

FAA Order 1600.75

Protecting Sensitive Unclassified Information (SUI)

FAA Order 1600.78 Personal Identity Verification (PIV) Card and Other Identification Cards.

FAA-D-2494 Rev. B Technical Instruction Book Manuscript: Electronic, Electrical, and Mechanical Equipment, Requirements for Preparation of Manuscript and Production of Books, Appendix I

C-2

NAS-IR-3113118 Interface Requirements Document (IRD) ASOS Controller Equipment Information Display System (ACE-IDS) To NAS Information Display System (NIDS)

NAS-IR-31133118 Interface Requirements Document Automated Field Observation System (AFOS)/ Advanced Weather Interactive Processing System (AWIPS) To NAS Information Display System (NIDS)

NAS-IR-31063118 Interface Requirements Document Automated Surface Observing System (ASOS) to NAS Information Display System (NIDS)

NAS-IR-82153118 Interface Requirements Document Digital Altimeter Setting Indicator (DASI) to NAS Information Display System (NIDS)

NAS-IR-82013118 Interface Requirements Document Flight Data Input/Output (FDIO) System to NAS Information Display System (NIDS)

NAS-IR-92063118 Interface Requirements Document Voice Recorder Systems that use Global Positioning System (GPS) Time Source (GTS) To NAS Information Display System (NIDS)

NAS-IR-31180001 Interface Requirements Document External Systems that use a Ribbon Display Terminal To NAS Information Display System (NIDS)

NAS-IR-33113118

Interface Requirements Document Runway Visual Range System To NAS Information Display System (NIDS)

NAS-IR-31203118 Interface Requirements Document Stand Alone Weather Sensors (SAWS) Via Control Display Unit (CDU) To NAS Information Display System

(NIDS)

NAS-IR-31143118 Interface Requirements Document Wind Measuring Equipment (WME) Climatronics & Loral To NAS Information Display System (NIDS)

NIDS-IR-00000001 Interface Requirements Document NAS Information Display System (NIDS) Virtual Operator Interface Device (VOID) To NAS Information Display System ASOS Interface Application

NAS-IR-31233118 Interface Requirements Document Surface Weather System (SWS) to NAS Information Display System (NIDS)

NAS-IR-31243118 Interface Requirements Document Automated Weather Observing System Model-C (AWOS-C) to NAS Information Display System (NIDS)

IDSR-12-03 MSR

Revision 3

Minimum System Requirements Integrated Display System Replacement (IDSR) Revision 3

FAA Order JO 6160.14 NAS Information Display System (NIDS) Maintenance Technical Handbook (MTHB)

FAA TI 6160.71 NAS Information Display System (NIDS) Hardware Maintenance Technical Instruction Book

C-3

NAS-IC-31083118 Interface Control Document (ICD) NAS Information Display System (NIDS) ASOS Controller Equipment Information Display System (ACE-

IDS)

NAS-IC-31133118 Interface Control Document NAS Information Display System (NIDS) Automated Field Observation System (AFOS)/ Advanced Weather Interactive Processing System (AWIPS)

NAS-IC-31063118 Interface Control Document NAS Information Display System (NIDS) Automated Surface Observing System (ASOS)

NAS-IC-82153118 Interface Control Document NAS Information Display System (NIDS) Digital Altimeter Setting Indicator (DASI)

NAS-IC-82013118 Interface Control Document NAS Information Display System (NIDS) Flight Data Input/Output (FDIO) System

NAS-IC-92063118 Interface Control Document NAS Information Display System (NIDS) Voice Recorder Systems that use Global Positioning System (GPS) Time Source (GTS)

NAS-IC-25233118 Interface Control Document NAS Information Display System (NIDS) External Systems that use a Ribbon Display Terminal

NAS-IC-33113118 Interface Control Document NAS Information Display System (NIDS) Runway Visual Range System

NAS-IC-31203118 Interface Control Document NAS Information Display System (NIDS) Stand Alone Weather Sensors (SAWS) Via Control Display Unit (CDU)

NAS-IC-31143118 Interface Control Document NAS Information Display System (NIDS)Wind Measuring Equipment (WME) Climatronics & Loral

NAS-IC-31233118 Interface Control Document Surface Weather System (SWS) / NAS Information Display System (NIDS)

NIDS-IC-00000001 Interface Control Document NAS Information Display System (NIDS) Virtual Operator Interface Device (VOID) / NAS Information Display System ASOS Interface Application

NAS-IC-31010001-01 Interface Control Document (ICD) Automated Weather Observing System Model-C (AWOS-C) to NAS Display Subsystems

C.3.1 Federal Standards

DOD-STD-1686 Electrostatic Discharge Control Program for Protection of Electrical and Electronic Parts, Assemblies and Equipment

C-4

C.3.1.1 Obtaining Copies of Documents

Copies of FAA specifications and interface documents may be obtained from the Federal Aviation Administration, Headquarters Public Inquiry Center APA-230, 800 Independence Avenue SW, Washington, DC 20591, 202-267-3484. Requests should fully identify material desired and cite the solicitation or contract number.

Requests for copies of documents not covered in the preceding paragraph should be addressed to the Contracting Officer. Requests should fully identify material desired and cite the solicitation or contract number.

C.3.2 Definitions

The term source code used throughout this document includes all software developed, Non- Developmental Items (NDI), firmware, microcode, source code files, and other source logic files for all processors, controllers, Field Programmable Gate Arrays (FPGAs), and other logic devices comprising the specified system.

The term Adaptation Data used throughout this document includes all system adaptation files.

The term Configuration Data used throughout this document includes all application, operating system, and other configuration data required by the system target processors.

All references to the "Government" or “FAA” in this SOW must mean by authority of the Contracting Officer or designee.

C.3.3 Required Tasks

C.3.3.1 General

The Contractor must provide Second Level Engineering Support services on a Time and Material (T&M) basis for all IDSR systems in accordance with FAA Second Level Engineering (FAA-SLE) processes and FAA-SLE developed schedules. FAA-SLE is responsible for determining schedules, build content, and approval of software designs and code reviews.

The Contractor must provide Second Level Engineering support to include, but not limited to the following:

Collaboration with FAA-SLE with all aspects of IDSR FAA-SLE will determine schedules and build content of each IDSR release with contractor input and support.

Provide support to all milestones within the FAA IDSR Schedule which identifies and tracks all

IDSR milestones.

Conduct engineering analysis associated with maintenance issues and security vulnerabilities;

identified against the system design and baselines. Assess and identify recommended changes to the baselines, the system architecture, and design/interface documentation to address the maintenance issues.

Support software development activities to ensure correct understanding of system requirements and system design during system maintenance.

Support requirements analysis for new functionality. The Contractor must support Government meetings to discuss and review the requirements analysis results. After the requirements analysis effort is completed and reviewed by the Government, the Government will determine if the new functionality will be packaged in a software release for implementation. If the functionality is

C-5 selected for implementation, the Government will identify the requested software release for packaging.

Resolve complex IDSR hardware and software problems; including PTR resolution, security vulnerabilities and development of new software functionality and releases.

Design, integrate and test upgrades to the IDSR developed software and CAS, firmware, microcode, and other logic for operational improvements using an open, standards-based system design;

Support integration and test activities including assessment of test success criteria, test procedures, and test results.

Test new IDSR system baselines prior to deployment including test procedure development/modification, and test/demonstration execution support;

Provide instructions to aid in distributing new releases of IDSR software, hardware, firmware, microcode, other logic, configuration data, and adaptation data.

Configuration management of IDSR hardware, software, firmware, microcode, other logic, and documentation.

Provide input to IDSR System Support Directives (SSD), technical instruction (TI) manuals, system specifications, system interface requirement documents (IRD), and interface control documents (ICD), and maintenance handbooks when warranted by technical changes.

Provide on-site support activities as required.

Provide technical support, on an as needed basis, to all FAA/SLE IDSR Functional Teams.

Conduct End-Of-Life (EOL) analysis of IDSR Hardware and Software, to include reporting the results of such analysis to the Government and providing recommendations for replacement items.

Other technical activities deemed necessary in support of IDSR/NIDS.

C.3.3.2 Detailed Task Requirements

The following subsections provide a description of the Task requirements to be included under this SOW.

C.3.3.2.1 Software Second Level Engineering Support

The objective of the system software support function is to provide comprehensive life cycle software support to the IDSR systems as directed. This must include but not be limited to the activities outlined below.

C.3.3.2.2 TASK 1 – IDSR/ NIDS Maintenance Support

The contractor must perform, as directed, maintenance activities to support the IDSR system. This must include, but not limited to the following activities:

Provide support for problem determination and software diagnostics including the analysis of system recorded data and error logs.

Support the troubleshooting, classification, and resolution of program trouble reports (PTR’s).

Support for corrective and enhancement maintenance releases and security vulnerabilities.

The Contractor must develop code modifications, in accordance with C.3.3.2.3, in order to provide functional enhancements and fixes. All changes must be submitted to and approved by the FAA Contracting Officer. The Contractor must review and comment on code modifications

C-6 developed by the FAA. The FAA must have final approval over implementation of all software modifications.

All Operating System and COTS application changes must require Government approval.

CDRL E012 Technical Report-Study/Services

CDRL E011 Version Description Document (VDD)

C.3.3.2.3 TASK 2 – IDSR/NIDS Software Maintenance Support

The contractor must perform, as directed, software maintenance activities to support the IDSR. This must include, but not be limited to the following activities:

FAA-SLE involvement in software and engineering design inspections o Contractor will provide FAA-SLE the ability to review, comment, attend, and make recommendations to the inspection packages

FAA-SLE has rights to modify code in parallel with the contractor

Contractor will provide FAA-SLE the software baseline prior to the completion of the contractor regression testing.

Contractor will wait for final decision from FAA-SLE to release the software baseline to

FAA-SLE

FAA-SLE will make final decision to deploy software baseline operationally.

Perform software requirements verification, code, unit test, integrate, test, and deliver updates for the system software.

Perform software design reviews in the context of how to implement the software modifications and/or system level requirements.

Contractor will review any of the FAA’s design or code packages, as requested

Support for the creation and modification of system Adaptation and Configuration Data.

Support for the creation of system build and distribution media.

Support communication with the user community during requirement and system analysis, prototyping, and fielding of system software.

Provide software support for troubleshooting software.

Provide support for software quality assurance (QA) issues and strategies.

CDRL M002 Meeting Conference Minutes

CDRL M023 Conference Agenda

CDRL E011 Version Description Document (VDD)

CDRL E014 Software Requirements Specification (SRS)

CDRL E016 Software Build Procedures

CDRL E017 Build Letter

CDRL E018 Software Design Review Packages

C-7

CDRL E019 Software Code Review Package

CDRL E020 Software Release Packages/Binaries

C.3.3.2.3.1 Software Configuration Management/Quality Assurance

The contractor must support and monitor, as directed, software Configuration Management (CM) and QA activities to support the IDSR. This must include but not be limited to the following:

Support all software tools necessary to automatically generate a list of files for inclusion in a Software Version Description Document for all releases

Support QA tools to verify software build integrity, process control and quality, changed module trace to authorizing change instrument, software measurement and metrics collection, and enforcement of user permissions for access to make software changes.

The Contractor must implement formal configuration control beginning with the establishment of the existing IDSR approved baseline.

CDRL E011 Version Description Document (VDD)

CDRL E015 Software Repository Documentation

C.3.3.2.5 TASK 3 - Software Testing

The purpose of the Software Testing function is to conduct and support testing to ensure system requirements are satisfied and the release changes have no caused the system to regress in an unacceptable manor. This includes functional, performance and other requirements. This must include but not be limited to the activities outlined below

Provide support to ensure that the FAA has the appropriate test tools necessary to support testing.

This includes using and/or modifying existing test tools, as necessary.

Provide support for test demonstration or test documentation, such as test procedures, including preparation, maintenance and coordination of changes.

Provide support for functional, integration and regression test of software enhancements.

Conduct required data reduction and analysis to identify validate and verify any discrepancies and identify/recommend actions in response to test outcomes.

Support test meetings, report findings, address action items, and propose recommendations.

Provide the government with written reports detailing discrepancies, observations, reviews, conclusions and recommendations with regard to the specific tests involved.

CDRL T005 Software Test Procedures (Description (Scenarios/Scripts)) (STD) CDRL T008 Software Test Report (STR)

C.3.3.2.5.1 Test and Evaluation Support

The contractor must plan, conduct and document an integrated Test and Evaluation (T&E) strategy, in accordance with this SOW. The contractor must perform, as directed, test and evaluation activities to support the IDSR Program. This must include, but not be limited to the following:

C-8

Conduct verification testing for functional enhancements, security changes and fixes with

FAA Test Management approved procedures. This testing may be performed at the WJHTC or completed remotely by the vendor but must be witnessed by the FAA.

Conduct System Level Regression Testing on IDSR SW releases prior to delivery to the FAA Test team with FAA Test Management approved procedures.

Conduct Simulated Interface Regression Testing on IDSR SW releases prior to delivery to the FAA Test team with FAA Test Management approved procedures.

The contractor must conduct tests, collect and analyze data, and perform the required data reduction to verify the requirements and associated specifications. The Government reserves the right to review, comment on and approve all test procedures, reports and schedules, and to witness contractor testing during any test phase. The contractor must support regular status and Test Working Group meetings, as required by the Government. The contractor must provide a detailed Test and Evaluation Exit briefing including all defects, features, etc. tested along with any issues found to the Government prior to the deployment of the IDSR System Release.

CDRL T005 Software Test Procedures (Scenarios/Scripts) (STD) CDRL T008 Software Test Report (STR)

C.3.3.2.5.2 Test Conduct

The Contractor must allow the Government representatives to monitor the test executions. The Government will be notified in advance of the schedules for testing, this includes verification testing, System Regression testing and Interface Regression Testing. The Contractor must execute all steps in the test procedures and document anomalies and deviations preventing the execution of specific steps. As-run test procedures must be available for review and copy upon Government request. The Contractor must use the En Route and Oceanic Second Level Engineering Automated Issue Management System (AIMS) for submitting, tracking and reporting issues found during testing.

C.3.3.2.5.3 Test Tools

The Contractor must provide the Government with new or modified COTS, test tools/simulators and necessary test software along with support documentation.

C.3.3.2.5.4 Government Tests

The Contractor must provide support to the Government test activities executed at the WJHTC. This includes phone support for issues, triage of AIMS issues documented during Government testing and on-site support, as requested by the Government.

C-9

C.3.4 TASK 4 - Other Engineering Support

The Contractor must provide other engineering support to accomplish the purposes of this SOW, including, but not limited to the following activities:

• Support to the FAA in the preparation and/or review of FAA technical documentation related to the specified system. The Contractor must review and provide written comments on the technical accuracy and completeness of each document. The FAA must have final approval over all changes to system-specific documentation.

• Develop changes to system-specific technical documentation for all Contractor-developed functional enhancements.

• Support to the FAA in the familiarization of the IDSR software maintenance activities, troubleshooting and fault isolation.

• Support Technical Interchange Meetings (TIMs) as requested by the FAA.

• Maintain an IDSR system for testing and troubleshooting the IDSR hardware and software.

• Provide updates to the IDSR/NIDS technical manuals as required by introduction of functional enhancements: For example, the NIDS Instruction Book: Maintenance and Installation and the NIDS Technical Instruction Book: Database Administration, and the Maintenance Handbook.

C.3.4.1 SIB/TRIAGE SUPPORT

The Contractor must support the En Route and Oceanic Second Level Engineering Automated Issue Management System (AIMS) resolution system by participating in SIB/Triage teleconferences held bi-weekly each for one hour. Support must include the subtasks in Section C.3.3.2.2. With the Contractor’s input, each AIMS ticket will be reviewed for the severity level and if the issue is a defect or a new feature for the system. If it is a defect, the Contractor must correct the defect under the contract’s existing warranty clause. If it is a new feature, the FAA will draft new requirements and provide them to the Contractor for cost and schedule estimates.

CDRL E012 Technical Report-Study/Services

CDRL E001 Interface Control Document (ICD)

CDRL E014 Software Requirements Specification (SRS)

C.3.4.2 24 Hour On-Call Support

The FAA maintains a 24-hour help desk. In the event additional support is needed, the Contractor must provide a point of contact and telephone number to respond to FAA requests for site outages and restoration issues and other site support.

C-10

C.3.5 Project Management

The Contractor must assign a point of contact (POC) that must be the single focal point within the Contractor’s activity for all project tasks. The POC must be prepared at all times to present and discuss, with the Contracting Officer (CO) and/or the Contracting Officer Representative (COR) the current status pertaining to the total contract.

The Contractor must continuously monitor the technical performance of this contract, and of all subcontracts, to provide the Government with a timely assessment of program progress or problems, and to control the contract activities as well as subcontractor and vendor activities.

The Contractor must provide input to the FAA system schedule for each system. The schedule will be maintained by the government or other support contractors in the form of an integrated program schedule, and will include both planned dates and actual completion dates.

The Contractor must provide updated status monthly, for the activities and milestones indicated.

The Contractor must prepare and submit Status Reports on a monthly basis.

CDRL M003 Program Management Status Reports

C.3.6 Discrepancy Reporting System

The Contractor must use the FAA’s discrepancy reporting system as part of the Contractor’s CM program. The Contractor must document all system level discrepancies identified during development or testing and must submit corrective action plans.

C.3.7 List of Deliverables

All data items identified in this SOW must be delivered to the Government in digital media compatible with the Microsoft Office suite of products, (unless otherwise specified).

The Government may at its discretion choose to use a suitable format proposed by the Contractor for any of the deliverables indicated in lieu of Government format.

The following deliverables must be provided. All references to days are in calendar days.

Contract Deliverable Requirements Lists (CDRL)

DUE DATE

Data Rights

CDRL M002 Meeting Minutes C.3.3.2.3, C.3.3.2.5, C.3.3.2.6, C.3.4

7 days after the meeting Unlimited

CDRLs M003 Status Reports (Vendor reports to SLE) C.3.5

Monthly Unlimited

CDRL M023 Agendas C.3.3.2.3, C.3.3.2.5, C.3.3.2.6, C.3.4

10 days before meeting date Unlimited

CDRL E001 Interface Control Document C.3.4

30 days after identification of change

Unlimited

C-11

CDRL E002 Configuration Status Accounting Information C.3.3.2.4

As required Unlimited

CDRL E011 Version Description Document C.3.3.2.2, C.3.3.2.3, C.3.3.2.4

Delivered with software configuration item

Unlimited

CDRL E012 Technical Report- Study/Services includes Software Development Folders (SDF) C.3.3.2.2, C3.4

15 days after tasking Unlimited/Restricted (depending on report data)

CDRL E014 Software Requirements Specification C.3.4

15 days after tasking Unlimited

CDRL E015 Software Repository Documentation C.3.3.2.4

1 week after tasked by FAA, or longer if FAA approved, as needed

Unlimited

CDRL E016 Software Build Procedures C.3.3.2.3

1 week after tasked by FAA, or longer if FAA approved, as needed

Unlimited

CDRL E017 Build Letter C.3.3.2.3 1 week after tasked by FAA, or longer if FAA approved, as needed

Unlimited

CDRL E018 Software Design Review Package C.3.3.2.3

15 days after tasking, or longer if FAA approved, as needed

Unlimited

CDRL E019 Software Code Review Package C.3.3.2.3

15 days after tasking, or longer if FAA approved, as needed

Restricted

CDRL E020 Software Release Package/Binaries C.3.3.2.3

15 days after tasking, or longer if FAA approved, as needed

Restricted

CDRL T005 Test Procedure (Test Scenarios / Scripts) C.4.2.1.11

15 days after contract award (CDRL needs updated dates)

Unlimited

CDRL T008 Test Report C.3.3.2.5 and 3.3.2.6

Draft 7 days, Final 14 days after test completion (CDRL needs updated dates)

Unlimited

Acronyms

AJM Air Traffic Organization – En Route

AMS Acquisition Management System

ATS Air Traffic Services

CAS Commercially Available Software

CM Configuration Management

CO Contracting Officer

COR Contracting Officer's Representative

C-12

COTS Commercial Off-the-Shelf

FAA Federal Aviation Administration

FPGA Field Programmable Gate Array

GA Government Acceptance

IDSR Integrated Display System Replacement

IPT Integrated Product Team

LOE Level Of Effort

NAS National Airspace Systems

NDI Non-Developmental Item

NIDS NAS Information Display System

NTE Not To Exceed

PTR Program Trouble Report

POC Point of Contact

QA Quality Assurance

SSD System Support Directive

SOW Statement of Work

SRS Software Requirements Specification

TIM Technical Interchange Meeting

VDD Version Description Document

WJHTC William J. Hughes Technical Center