WMSS3 Section C.docx

WEATHER AND RADAR PROCESSOR (WARP)

MAINTENANCE AND SUSTAINMENT SERVICES

(WMSS III)

DTFAWA-17-C-00001

Part I, Section C Statement of Work

Table of Contents

Scope This Statement of Work (SOW) defines the effort required to sustain the Weather and Radar Processor (WARP) hardware, software, firmware and adaptation data, and provide support to sustain existing WARP services. The Government intends to maintain the current capabilities and functionality of the WARP system as defined with the completion of the WMSS II Engineering Change Proposal (ECP) 01 and ECP02. This contract is designed to ensure that the WARP system availability is maintained in accordance with (IAW) the requirements of Attachment J-03, the WARP System Specification, "U.S. Department of Transportation Federal Aviation Administration Specification Weather and Radar Processor, FAA-E-2898" and Attachment J-07, the Weather Information Network Service (WINS) specification, “U.S. Department of Transportation Federal Aviation Administration Specification Weather Information Network Service, FAA-E-3031, herein referred to as the “WARP System Specifications.”

The WARP system is defined by the system requirements in Section 3 of J-03 and J-07, the WARP System Specifications. This SOW also includes provisions for program management, maintenance support, systems engineering, system test and evaluation, quality assurance, configuration management, helpdesk support, and logistics support.

The WARP system is a computer-based interactive, meteorological data processing system that simultaneously and continuously receives, processes, stores, distributes, and displays aviation-related weather information and radar products. Each WARP consists of the Weather Server, the Communications Subsystem, the Meteorologist’s Workstation, Briefing Terminals, the Monitor & Control (M&C) workstation, the Weather Information Network Service (WINS), and the Radar Acquisition and Mosaic Processor (RAMP). The WINS consists of Central Distribution Nodes (CDN) at two (2) Air Route Traffic Control Centers (ARTCC), Regional Distribution Nodes (RDN) at four (4) ARTCCs, and Local Distribution Nodes (LDN) at all ARTCCs and three (3) Center Radar Approach Control (CERAP) facilities. WARP also includes the Federal Aviation Administration (FAA) Bulk Weather Telecommunications Gateway (FBWTG) Server at the Air Traffic Control System Command Center (ATCSCC).

WARP provides four (4) primary functions:

1) Timely and accurate weather displays to Air Traffic Controllers (ATCs) integrated with controller display systems. These displays are WARP generated mosaics of Weather Surveillance Radar 1988 Doppler (WSR-88D) weather radar data.

2) Support to the Traffic Management Unit (TMU) and the Air Traffic Control Specialists and Supervisors at the ARTCC, the ATCSCC, and CERAPs.

3) Provision of weather information and forecasts via the workstation display to the Center Weather Service Unit (CWSU) meteorologist. This capability facilitates a common situational awareness in the en route environment.

4) Dissemination of weather information to other National Airspace System (NAS) subsystems.

The WARP system is deployed at 21 ARTCCs and the ATCSCC, three (3) CERAPs, with three (3) test development systems located at the William J. Hughes Technical Center (WJHTC). In addition to the full WARP system deployments at the aforementioned locations, Briefing Terminals are deployed at three (3) Terminal Radar Approach Control (TRACON) facilities.

C.1.1 Decommissioning of WARP The WARP system will be replaced by a combination of features provided by the Common Support Services – Weather (CSS-Wx) system and the Nextgen Weather Processor (NWP) system. Attachment J-11 NWP System Implementation – Site Operational Readiness Decision (ORD) Milestones shows the major milestones that will enable the WARP system to be decommissioned.

The level of effort required to execute the tasks described in this SOW will assume a fully deployed WARP system across all option periods (no sites decommissioned). However, the Government reserves the right to enter into a future bilateral de-scoping of the SOW taking into account these anticipated milestones or variations thereof. It is expected that the deployment of NWP and the corresponding draw down of the WARP system will be reflected in at a minimum the following CDRL items:

· A008 Integrated Master Schedule

Applicable Documents Documents listed in Attachment J-4, Applicable Documents, form a part of this SOW to the extent specified herein, except as specifically noted. In the event of a conflict between the text of this SOW and a referenced document, the text of the requirement stated in the SOW will take precedence. After the SOW, the WARP System Specifications will take precedence over a referenced document.

Requirements The supplies and services required by this contract must be performed IAW this SOW and the WARP System Specifications. The Contractor will provide systems engineering, program management, logistics support, quality assurance, configuration management, operational support, material and support to test, deliver and install WARP system hardware, software modifications, and adaptation data changes to support the tasks and products described in this SOW. The Contractor must maintain staffing levels to respond to hardware, software, and adaptation data maintenance calls to meet the availability requirements set forth in the WARP System Specifications.

Data items in J-02 referenced by their Contract Data Requirements List (CDRL) titles in J-01 must be performed IAW the CDRL of the same name, even when the CDRL number is not specified. All data deliverables must be prepared and delivered IAW the corresponding CDRL items specified under the SOW requirement.

The Contractor must perform IAW all plans developed in response to this SOW. All references to the "Government" in this SOW must mean by authority of the Contracting Officer or designee. All CDRL items identified in this SOW must be placed on the FAA’s Knowledge Shared Network (KSN) site, and be compatible with the Microsoft Office suite of products, (unless otherwise specified).

Program Management C.1.1.1 Program Management Organization The Contractor must maintain a formal organization to manage this contract and all subcontracts and subcontractors related to this effort. The Contractor must develop and implement a Management Program to efficiently and effectively execute the requirements of this contract to include: program control, configuration management, subcontract management, management of Government furnished resources, risk management, project status reporting, and security, taking into account Section C.1.1 Decommissioning of WARP C.1.1.2 Program Control The Contractor must assign a Program Manager for the duration of this contract period of performance. The Program Manager must have resources and authority to ensure efficient, effective, and timely project execution and must be the single focal point within the Contractor's activity for all required project tasks.

If subcontractors are used, the Contractor must be responsible for ensuring that all requirements are fulfilled for subcontracted items.

Project Status Reporting The Contractor must prepare Contract Performance Reports beginning at contract award and continuing until contract end and report status at the Project Management Reviews.

CDRL Item:

A009 Contract Performance Report Risk Management The Contractor must establish a risk management process to identify and mitigate all risks associated with program cost, schedule and technical scope.

The Contractor must assess the likelihood of occurrence and the impact of each risk identified, and assign a risk rating of either Low, Medium, or High. The Contractor must perform risk management throughout the duration of the contract, and communicate all Low, Medium and High Risk to the FAA during status reporting meetings such as PMRs. The Contractor must develop risk mitigation plans for risks considered medium or high priority.

The Contractor must provide the status and risk mitigation plans in the Program Management Reviews (PMRs).

Meetings The Contractor must conduct project status meetings and reviews IAW this SOW. At each management review or audit, the Contractor must provide backup data regarding assumptions made and methodologies used in arriving at specific recommendations or conclusions. For all meetings, the Contractor must prepare and submit a meeting agenda including all presentation materials, and record and submit meeting minutes that document decisions and action items originating from the meeting. Management and formal reviews and audits must not be considered complete until approval by the Government is granted in writing.

Support provided by the Contractor must include facilities, materials, office equipment, clerical personnel, mockups, technical data, and subcontractor participation (when requested by the Government). For all meetings, the Contractor must provide teleconferencing services that include an on-demand, self-service collaboration environment with both web and video-based multi-media conferencing. The Contractor must provide an agenda for each management and formal meeting IAW B001. For any scheduled meeting that includes a briefing deck or slide package, the Contractor must provide an advance copy to the Government at least three business days before the scheduled meeting date. The minutes, accompanied by a summary of action items, decisions made, and all presentation materials used must be provided by the Contractor IAW B002 for Government approval.

CDRL Items:

Initial Kickoff Meeting The Contractor must plan for, host, support, and participate in an Initial Kickoff Meeting to be held at the Contractor’s facility within one month after contract award. The FAA will determine the actual date within two (2) weeks after contract award. At this meeting, the Contractor must address the plans and schedules for the WARP Maintenance work efforts.

Program Management Reviews (PMRs) The Contractor must conduct PMRs every three months, or as agreed upon with the Contracting Officer Representative (COR), to present program status to the Government Program Office. The Contractor must present a status of the overall performance of this contract to include: cost, schedule, and technical performance status, provide performance measurement information including all program risks, issues and program variances, and must present current and anticipated technical and implementation problems, and corrective action(s). The Contractor must identify and report on the status of the overall performance of any subcontractor activity as it applies to the performance of this contract. The Contractor must report on the status of all Government Furnished Property (GFP).

The review location may alternate between a virtual meeting and the Contractor's facility or as agreed upon with the COR. Half of the PMRs, rounding down if an odd number, must be at the contractors site. The Contractor's PMRs must be targeted for no more than one (1) day in length. Attendance will generally be limited to 4-5 key FAA personnel and 4-5 Contractor personnel.

Technical Interchange Meetings (TIMs) At any point during the effort, the Government or the Contractor may request a Technical Interchange Meeting (TIM). The Contractor must conduct and/or attend TIMs with FAA representatives and others, as required, to review technical issues and problem areas. The TIM location may be a virtual meeting and the Contractor's facility During the TIMs, the Contractor and the Government will discuss specific technical activities, including studies, test plans, test results, design issues, technical decisions, and implementation concerns to ensure continuing FAA visibility into the technical progress of this contract. The Contractor must make available cognizant technical personnel, including subcontractor personnel, in each of the areas to be covered during the meeting. There must be free and unlimited exchange of technical information between the Government, Contractor, and subcontractor(s) during the meetings. Whenever practicable, TIMs will be held in conjunction with project status meetings. The Contractor must prepare agendas and minutes for each TIM for review and approval by the Government. The Government anticipates requesting two TIMs per year but may direct additional TIMs.

C.1.1.3 Planning and Reporting Contract Work Breakdown Structure (CWBS) The Contractor must maintain a Contract Work Breakdown Structure (CWBS) and CWBS Dictionary. The Contractor must use FAA Standard Work Breakdown Structure Version 5.1 and this SOW for guidance. The CWBS must be maintained at the third level to identify problems associated with describing potential non-conforming issues or conditions. The Contractor must use the CWBS as the framework for project planning, budgeting, managing, and reporting the status of cost, schedule, configuration management, and technical achievements. The Contractor must identify within the CWBS all subcontracted elements or tasks. During the performance of this contract, the Contractor must not change the CWBS or associated definitions at level three or above without the express written approval of the Contracting Officer. Changes deemed necessary by the Contractor may be made at lower levels without Government approval; however, the changes must be within the constraints set forth in the definitions of the higher-level CWBS elements.

CDRL Item:

A007 CWBS and CWBS Dictionary Program Schedule The Contractor must develop a resource-loaded and resource-balanced Program Schedule utilizing Microsoft (MS) Project. The schedule must be generated using a logical and efficient sequence of events designed to accomplish all of the tasks described in this SOW. The Program Schedule must include all tasks and deliverables at a detailed level up to the finalization of the maintenance release in progress. The next maintenance release must be in the schedule at a rolling wave planning level. The next maintenance release must be in the schedule at the detailed level within one month after receipt of the task order for the next maintenance release. The Program Schedule must be delivered IAW CDRL A008. The Contractor must provide the Government online access to the most current Program schedule. Updates to the online Program schedule must be made as changes occur to the schedule, but not less than once a week.

Sufficient detail must be employed to permit accurate progress monitoring and reporting of the planned tasks and subtasks and their logical sequences and relationships. In general, the Program Schedule must be modeled to levels of detail sufficient to identify and define manageable units of work. The Program Schedule must include planned and actual start and completion dates for SOW tasks such as the development, test, and installation of each software modification. The Program Schedule must be used to identify, define, and control schedule risk.

CDRL Item:

A008 Integrated Master Schedule

System Engineering The Contractor must conduct an integrated, iterative systems engineering program IAW the applicable sections of EIA-632 tailored to accomplish the tasks necessary to maintain and document the WARP system activities to meet the requirements of the WARP System Specifications. The Contractor must include in the systems engineering program: analysis and engineering activities required to satisfy the WARP System Specifications.

System engineering must include all aspects of performance, quality, life cycle costs, maintainability, reliability, availability, schedule, data processing reserves, de-commissioning activities and any future requirement changes. The Contractor must provide WARP subject matter expertise to address operational system performance, functions, requirements, operations, test, interfaces, deployment, and PTR and /or issues support as directed. The expertise can be via email, phone call, discussions, and attending meetings as directed by the government. The Contractor must specify a single authority that will serve as the point of contact for system engineering issues.

C.1.1.4 Software Engineering The Contractor must describe in the PMP the continuation of its plans for acquiring, developing, or maintaining the required software to meet this contract’s requirements. The PMP must identify the single point of contact for software engineering issues. The Contractor must acquire/develop/maintain, document, test, and manage all WARP system software. The Contractor must perform software development/enhancement IAW FAA-STD-026A. As part of implementing FAA-STD-026A, all Institute of Electronic and Electrical Engineers (IEEE)/EIA 12207 requirements must be reviewed, tailored, and agreed upon by the Contractor and Government to reflect the SOW requirements applicable to maintenance activities. The contractor must update the existing Software Development Plan (SDP) and associated CDRLs to reflect this tailoring. All software tools must be identified and approved for implementation including hardware and software IAW the SDP (CDRL Item A012) and this SOW.

The Contractor must design, develop, integrate, test, implement, maintain, and document modified software IAW their internal Software Development Plan (SDP).

The Contractor must permit authorized FAA personnel or designees to inspect all software documentation. The Contractor must provide authorized FAA personnel or designees access to the Contractor’s WARP CM database, Program Tracking Report (PTR) database, and/or other applicable databases. The Contractor must make available to the FAA for review, the information, practices, procedures, or documentation developed or purchased by the Contractor or its subcontractors in connection with the WARP software program. The Contractor must allow the FAA or designated persons to witness any test associated with the software development or integration.

A093 Software Quality Assurance Plan (SQAP) C.1.1.5 Architecture The Contractor must maintain the overall WARP system architecture, including the hardware architecture, software architecture, and communications architecture, to satisfy the requirements of the WARP System Specifications.

C.1.1.6 Systems Releases The Contractor must maintain control over the modification and acceptance of all configuration items through an engineering release system IAW with EIA-649-B. The contractor must develop public maintenance and emergency releases to correct error in code identified by PTRs. The Contractor must develop emergency releases for unplanned work that requires changes to the operating system, data files or site configurations. For planning purposes it is assumed there will be one final maintenance release and one emergency release in OY7, followed by one emergency release per year thereafter.

An emergency release is defined as a small, targeted release correcting a specific problem, or adjusting a specific adaptation parameter. For planning purposes an emergency release will require 160 or fewer hours of software development time. The contractor will perform a test at the contractor’s facility, but the contractor is not required to participate in a site release, or key site test for an emergency release. No CDRL documents are expected to be updated as a result of an emergency release.

Configuration Management The Contractor must maintain a Configuration Management (CM) program IAW EIA-649-B, National Consensus for Configuration Management. The CM program must provide an organizational structure with configuration identification and control methods, configuration audits, and configuration status accounting procedures for hardware, software, and adaptation data. The Contractor must place under configuration management all modified Computer Software Configuration Item (CSCIs) and Hardware Configuration Item (HWCIs). The Contractor must identify a focal point who will serve as the primary point of contact for all communication on CM- related issues. The contractor must maintain the CM program to reflect changes in the WARP/WINS system configuration due to the execution of planned decommissioning activities in line with Section C.1.1 Decommissioning of WARP.

The Contractor must maintain configuration control of hardware, software, adaptation data, firmware, and developmental/commercial documentation IAW the Configuration Management Plan (CMP). The Contractor must maintain configuration control of the hardware to the line replaceable unit (LRU) level and software to the version level.

Configuration Identification The configuration identification must be documented in the functional, allocated, and product baselines, developed and maintained IAW EIA-649-B. The WARP System Specification, FAA-E-2898, defines the WARP functional baseline and the WINS System Specification, FAA-E-3031, defines the WINS functional baseline.

The Contractor must maintain a Program Document Library that retains all documentation for identification, control, and status accounting of all Configuration Items (CIs) throughout the program life cycle. Any item subject to replacement in a site, used without modification from a subordinate vendor, or used as a serialized end item for tracking or Government acceptance purposes, must be designated a CI. The Contractor must assign a discrete part number or item identification number to each CI.

The Contractor must assign a discrete part/identification number to each software medium, (e.g. magnetic or optical storage media) containing release or build type software executables. The medium thus identified must be inclusive and contain all software segments, thereby providing easy identification of software releases after the product baseline is established.

Baseline Management and Review Support The Contractor must maintain a baseline management process to freeze the configuration identification in conjunction with the project’s reviews and audits and to control changes to those baselines. This control must include hardware, software, firmware, databases, adaptation data, and documentation.

Baseline Change Control The Contractor must maintain a Change Control Board (CCB) and develop CCB procedures to adequately establish baselines and support baseline management. Following Government approval, the Contractor must maintain traceability and currency of the baselines and consistency between program documentation for requirements, hardware, software, firmware, databases, adaptation data, and their respective versions. The Contractor must comply with the requirements of EIA-649-B, National Consensus for Configuration Management in proposing and accomplishing changes to each approved specification/baseline.

Changes to baselines and/or Requests for Deviations/Waivers (RDWs) must be done IAW EIA-649-B and FAA-STD-067. RDWs must be approved by the Government prior to implementation.

CDRL Items:

A044 Request for Deviation/Waiver A045 Engineering Change Proposal (ECP) Government CCB Support The Contractor must support Government CCBs held to maintain the system/software at all sites. The Contractor support must include:

· Bringing proposed changes to WARP software and adaptation data to the Government CCB via PTRs,

· Presenting PTRs properly documented with sufficient details of the problems, along with an estimate of resources required to implement the change at the CCB,

· Discussing design solutions and how the PTRs will be implemented,

· Discussing progress of the PTRs,

· Obtaining Government approval to work on PTRs, and

· Supporting the Government in establishing a maintenance release schedule and releasing software and adaptation data to the sites.

C.1.1.7 Interface Control The Contractor must provide for the modification of documentation and control of all physical and functional interfaces of systems, equipment, software, and facilities. Modifications to interface control documents, when required, must be prepared IAW FAA-STD-025F. The Contractor must review, update as needed, and submit as needed for Government approval, the data specified in the following CDRLs for system engineering in support of maintenance release activities IAW J-01:

CDRL Items:

A018 WARP to WINS Interface Control Document (ICD) A024 WINS Web Coverage Service (WCS) Web Service Description Document (WSDD) A027 WINS to Weather Message Switching Center Replacement (WMSCR) ICD

A029 WINS to Advanced Technologies and Oceanic Procedures (ATOP) ICD A032 WSR-88D to WINS ICD A035 WINS to Dynamic Ocean Tracking System Plus (DOTS+) ICD A037 WINS to Flight Data Processor 2000 (FDP2k) ICD A042 NWS Alaska Regional Headquarters to WINS ICD A062 System Implementation Requirements A063 Site Preparation, Installation, and Check-Out Plan A078 NWSTG to FBWTG (ICD) A080 WINS to ITWS ICD A086 WINS to En Route Automation Modernization (ERAM) ICD A087 WARP to User Display System (UDS) ICD A088 WARP to National Airspace System (NAS) Cyber Management System (NCMS) ICD C.1.1.8 Specification Maintenance The Contractor must maintain those specifications under Contractor jurisdiction pertaining to the configuration items to be modified and delivered under this contract. Specification maintenance must be accomplished IAW FAA-STD-067. A proposed Specification Change Notice (SCN) must be submitted as required. An ECP must completely detail the necessity and impacts of the proposed change.

CDRL Items:

A045 Engineering Change Proposal (ECP) A046 Specification Change Notice (SCN) C.1.1.9 Data Management The Contractor must comply with applicable sections of EIA-632, Systems Engineering and EIA-649-B in terms of the Contractor's overall data management program, policies, and procedures. The Contractor must prepare, update, publish, package, and distribute all data as indicated in the Contract Data Requirements List.

Data Management Program The Government requires full visibility into the Contractor’s systems engineering and development processes. The Contractor must provide the Government access to all data generated under this contract, including all Government-owned, Contractor-developed, public/open source code with software documentation and design information. Data must include program metrics, software development folders, public source code with software documentation and design information, hardware (HW) and software (SW) test procedures, engineering or logistics documentation, and databases, including requirements used or generated by the Contractor in the performance of this contract. The most recent version of all released data must be made available within five business days of being updated. The Contractor must archive all current and previous versions of documentation. Any restrictions on the use of electronic data must be as prescribed in the Data Rights Clause of the contract. For electronic documents, the Contractor must provide an on-line web site access for reviewing documents to authorized FAA personnel (read-only mode) via a secure socket layer using 128-bit encryption. The Contractor must restrict access to the site only to individuals authorized by the COR.

The Contractor must perform this contract IAW all Government-approved plans developed in response to this SOW. All reference to the "Government" in this SOW must mean by authority of the Contracting Officer or designee. Throughout this SOW, the requirement to record information or data must be interpreted to mean, "set down in a manner that can be retrieved and viewed.” The result may take many forms, including, hand-written notes, hard copy or electronic documents, and data recorded in computer-aided software engineering (CASE) and specific project management tools.

All CDRL items identified in this SOW must be delivered to the Government in electronic media compatible with the Microsoft Office suite of products, (unless otherwise specified). The Government will identify certain CDRLs or deliverables to be delivered in hard copy format (i.e. final SW test procedures, etc.). Attachment J-1 CDRLs and Attachment J-2 Data Item Descriptions, identify the delivery format for each CDRL. By the last day of each month, the Contractor must provide the Government a list of all CDRLs due for the following month.

Copyrights The Contractor must ensure that the FAA is authorized to copy all materials and documents used for this contract, unless restricted by third-party software license agreements.

Data Rights All software developed under this contract will be fully owned by the FAA. Any new software reused that has licensing agreements attached must be approved by the FAA. The FAA must be provided with access and maintenance rights to all source code for any new software reused for the WARP system. New software is any software that was not part of the WARP system baseline at the time of contract award.

The Contractor must ensure that the Government and others acting on behalf of the Government are granted a paid-up, nonexclusive, irrevocable, worldwide license for all public data exclusive of computer software, to reproduce, prepare derivative works, distribute copies to the public, and perform publicly and display publicly all such data by or on behalf of the Government.

Information System Security The Contractor must follow system security requirements identified in WARP System Specifications, and all security guidance contained in FAA Order 1370.121B, Information Systems Security Program, as revised. Contractor implemented security must be subject to Government approval and the system may be subject to independent penetration testing. The Contractor must assist the Government with the maintenance of security related documentation such as the System Characterization document and the Information System Security Plan (ISSP) when requested by the COR.

The Overall Impact Level for a system is defined in Federal Information Processing Standards Publication (FIPS PUB) 200, Minimum Security requirements for Federal Information and Information Systems. WARP is a Low Impact System and its minimum security requirements will be based on the Low baseline defined in National Institute of Standards and Technology (NIST) Special Publication (SP) 800-53 Revision (Rev.) 5, Security and Privacy Controls for Federal Information Systems and Organizations. The Contractor must meet these requirements as negotiated and funded separately.

Other FAA Information Security Standards will include the following policy documents as applicable:

· Information Systems Security and Privacy, Policy 1370.121B

· System Access Control, Policy 1370.96

· NIST SP-800-53 Revision 5, FY17 ATO Tailored Requirement AU-6.a.1

· NIST SP-800-53, Revision 5, AU-12.a.1.

The Contractor must generate, safeguard, control, and dispose of FAA sensitive security information in accordance with the guidance stated in FAA Order 1600.75, Protecting Sensitive Unclassified Information. The contractor must password protect all data pertaining to the WARP system or external user IP addresses.

The Contractor must maintain the following steps to ensure the physical and operational security of the WARP System as applicable:

1. Maintain a security certification process that ensures only authorized personnel have access to software codes, documentation, passwords, authentication processes, hardware, and associated components (subsystems) of the WARP System.

2. Safeguard WARP System components, including hardware, software, and documentation against damage, pilferage, and unauthorized access or modification.

3. Test WARP System in a manner that maintains security against damage, pilferage, and unauthorized access or modification.

4. Protect sensitive data, software, and hardware from unauthorized disclosure, access, or corruption at all times. Notify the Government immediately if unauthorized disclosure, access, or corruption occurs or is suspected.

5. Document and review all software changes to ensure that security is not compromised.

6. Provide the Government authorized FAA System administrators with the capability of customizing the default security parameters at any time as applicable to interface with all known and authorized systems (e.g., ATOP, MEARTS, ERAM, etc.).

7. The Contractor must provide documented system security management procedures that must be available for Government review upon request. Security procedures must include Access Control procedures for managing user and system access; Auditing, Accountability and Logging procedures for system security events, collect specified security event data in audit logs for reporting to NCMS; System and Communications protection procedures for authenticating system interfaces; and System and Information Integrity procedures including malicious code protection.

System Test and Evaluation The Contractor must conduct a formal Test Readiness Review (TRR) prior to all Contractor conducted formal maintenance release testing IAW EIA-632. The Contractor must conduct a dry run of all maintenance release tests prior to TRR and must identify all issues uncovered to the attention of the COR. At the TRR, the Contractor must identify all tasks associated with performing test readiness activities IAW approved test plans and procedures. The Contractor must demonstrate its readiness to commence formal testing. Upon successful completion of the TRR, the FAA will approve the initiation of formal testing. The Contractor must prepare an agenda for the TRR IAW CDRL B001. The Contractor must record the minutes and submit them for review and approval by the Government IAW B002.

CDRL Items:

The Government reserves the right to witness or verify testing at any level on a non-interference basis. The Contractor must maintain a WARP system conforming to the current operational baseline for system analysis, investigation, and troubleshooting of field issues.

C.1.1.10 Maintenance Release Test Contractor Release Test (CRT) The Contractor must conduct testing for each planned and approved WARP maintenance release. The scope of release testing and the meaning of the allocated requirements as they pertain to a release will be determined and approved by the Government prior to Contractor Release Test (CRT) in the Government approved test procedures. The CRT will be formally witnessed by the Government and must verify the capability of the modifications to meet functional, interface, and performance requirements of the WARP System Specifications. The system power and product receipt functions must remain on for the full duration of CRT. The Contractor must supply a CM certified closed system with any deviations from the standard ARTCC and/or ATCSCC configurations identified prior to the start of CRT.

The CRT must include a continuous 48-hour closed-system stability test. The purpose of the test is to measure the WARP system performance over an extended period while performing those functions routinely used in an ARTCC and ATCSCC environment. The Contractor must prepare a base test load scenario pertinent to the stability test. The scenario may be different between the Contractor’s facility and the WJHTC. This load scenario must be run on the current operational baseline (at both the Contractor’s facility and the WJHTC) and performance and load data captured, analyzed, and documented. For each release (CRT and Site Release Test (SRT)) this same load scenario must be executed, and the data captured and compared with the benchmark that was previously captured and documented.

The Contractor must prepare test documentation IAW FAA-STD-024b. The CRT procedures must include a list of all test equipment and test software used, and for test equipment, make, model, serial number, and certification data must be identified. The Contractor must explicitly describe in graphical and textual form the test equipment interconnection with WARP equipment under test. The Contractor must define and identify in the test procedures the functions, data interfaces, and interactions of test software. The Government will evaluate any and all issues arising from CRT testing to determine the suitability of SRT activities. If further investigation into the nature and/or cause of said issues is required, the Government will determine which repair or rework must be completed prior to SRT activities. The Contractor must complete repair or rework as requested by the Government prior to SRT activities. Delivery will be through installation of corrected CRT software to be used for SRT. The Government will determine the extent of retest that is required. Procedural requirements apply to all classes and levels of testing.

Site Release Test (SRT) The Contractor must conduct a SRT on the WARP system after successful delivery and installation of a CRT baseline maintenance release at the WJHTC, and at the operational sites, if required by the FAA. The scope of release testing and the meaning of the allocated requirements as they pertain to a release will be determined and approved by the Government prior to SRT in the Government approved test procedures. The Contractor must certify the FAA test system prior to the load and installation of the release, to ensure proper configuration and baseline prior to commencement of SRT activities. The SRT must verify the capability of the modifications to meet functional, interface and performance requirements of the WARP System Specifications, with live interfaces, and demonstrate the corrections associated with any PTRs contained in the release.

The SRT must include a continuous 48-hour closed-system stability test. The purpose of the test is to measure the WARP system performance over an extended period while performing those functions routinely used in an ARTCC, ATCSCC, and CERAP environment. The Contractor must prepare a base test load scenario pertinent to the stability test. The scenario may be different between Contractor’s facility and the WJHTC. This load scenario must be run on the current operational baseline (at both the Contractor’s facility and the WJHTC) and performance and load data captured, analyzed, and documented.

The system power and simulated product receipt functions must remain on for the full duration of SRT. During SRT, the Contractor must provide hardware and software maintenance support. The Government will evaluate any and all issues arising from SRT testing to determine the suitability of acceptance of the baseline. SRT activities must demonstrate that the WARP system is correctly installed and operating to specification.

C.1.1.11 Test Equipment All test equipment (and test software), required for use during tests conducted at the test facility must be provided by the Contractor or Subcontractor. During tests conducted on-site, the Contractor must be responsible for assuring that all test equipment is available, on time, calibrated, and fully operational to support all tests. Use of Government test equipment may be possible where Government test equipment is on site, is available, and meets all specified test equipment requirements. All test equipment used during the CRT or SRT, tests must be standard commercial equipment and must not be modified. The test equipment must operate in the manner specified by the test equipment manufacturer. Use of custom test equipment or modified commercial test equipment requires approval in writing by the Government.

C.1.1.12 Retest The Contractor must conduct retesting of failed tests that occur. The Contractor must complete all repair or rework prior to submission for retest. The Contractor must perform corrective action to assure full specification compliance. The Contractor must submit in writing all information concerning the non-compliance and corrective action. The Government will determine the extent of retest required and timing of the retest. If a review of the reasons for failure to comply with specification requirements indicates that the cause may exist as latent defects in items previously accepted, the Contractor must be responsible to correct the defects in all units in a time period identified by the Government, even those previously accepted by the Government. The Contractor must re-verify, by testing, that the defect(s) have been corrected and no new defects have been introduced.

Logistics Support The Contractor must execute a Logistics Support program IAW the requirements contained in this SOW. The Logistics Support program must consist of the total set of tasks, both management and executive, required to accomplish supporting and maintaining all WARP systems installed. The Logistics Support effort must be conducted as an integral part of the WARP System maintenance process.

C.1.1.13 Depot Level Support The Contractor must provide depot level logistics support for all identified WARP hardware and software configured items. This support must include stocking, storing, issuing, and shipping expendable, consumable and repairable items. Those items covered by warranty must be replaced at no cost to the Government. The Contractor must repair, if it is cost effective, all repairable Expendable and Replaceable (E&R) LRUs returned from FAA field sites. The Contractor shall take into consideration to Section C.1.1 Decommissioning of WARP when stocking, shipping and repairing items. The Contractor must furnish all labor, tools, test equipment, parts, software, and any other technical or administrative support necessary to provide the required Contractor Depot Logistics Support (CDLS). The Contractor must submit monthly status reports for the CDLS support IAW the CDRLs.

The Contractor must designate a WARP Depot Level Support manager. The WARP Depot Level Support manager must serve as the focal point for interface with the Government in all matters relating to the management of the WARP System Depot Level Support program.

CDRL Item:

M002 Service Report C.1.1.14 Government Furnished Property (GFP) The Contractor must manage, control, identify, protect, and maintain all GFP in its possession. The Contractor must maintain the processes, systems, procedures, records, and methodologies necessary for control of GFP. The Contractor must conduct and perform an audit of all GFP inventory transferred onto this contract within thirty (30) DACA. The Contractor must prepare an inventory report associated with this audit and submit to the Contracting Officer Representative (COR) and the Quality Reliability Officer (QRO) at the first PMR associated with this contract. The Contractor must segregate all GFP from its own property to prevent unauthorized use, loss, or degradation. The Contractor must ensure that all WARP hardware stays available throughout the life of this contract to ensure the WARP software architecture does not require modification.

C.1.1.15 Integrated Support Plan (ISP) The Contractor must maintain the ISP to reflect the current program status and must update the plan to reflect changes resulting from program changes, de-commissioning activities, reviews and other actions affecting the logistics aspects of the program. The ISP must be reviewed and updated IAW attachment J01. The initial submission and all updates of the ISP require Government approval. Once approved, the plan must be the controlling document for the Contractor's Logistics Support program.

C.1.1.16 Parts Obsolescence The Contractor must monitor for parts obsolescence. If, at any time during contract performance, the unavailability of a part is expected to impact the Contractor’s ability to perform to this SOW the Contractor must immediately inform the FAA so that a cost effective work around (to include, as appropriate, contract price adjustments and replacement parts costs) can be implemented. The parties (Government and Contractor) must agree that there is a potential issue with parts obsolescence.

C.1.1.17 Spares Buy under Fixed Price The pricing for Fixed Price includes the purchase of various spare parts required to ensure that potentially obsolescent parts will be available through the period of performance of the contract for use in support of WARP system maintenance. This spares purchase is intended to ensure that needed WARP spare parts will be available for the duration of this contract. Therefore, it is agreed that at the conclusion of this contract, the FAA will have title for all unused WMSS/WARP spare parts purchased under this contract.

In addition, the Government authorizes the contractor to purchase and use reconditioned, or remanufactured parts or equipment when new parts or equipment are no longer available. The contractor must adhere to the following process:

· Purchase parts or equipment new, when available.

· If the equipment is not available new, purchase reconditioned/remanufactured parts or equipment from the original manufacturer.

· If the reconditioned/remanufactured parts or equipment is not available from the original manufacturer, purchase from a third party.

“Reconditioned” means restored to the original normal operating condition by readjustments and material replacement.

“Remanufactured” means factory rebuilt to original specifications."

The Contractor must notify the Government via a formal Contracts letter of each instance that remanufactured or reconditioned parts are initially purchased. The Contractor must request completion of Form 4500-1 ten (10) business days prior to shipping any new model LRU.

C.1.1.18 Management of Site Spares The management of the WARP site spares must be conducted as follows:

1. When an on-site replacement part is required from the site spares cabinet, the Contractor, must maintain the inventory record in contractor format.

2. The Contractor must ship a replacement part to the site for placement in the site spares cabinet as soon as possible but not later than the two business day.

3. Defective parts will be returned to the Contractor, and all shipping records will be kept at site.

4. Reserved

5. The Contractor must be accountable for replacement of all parts used by the Contractor or its authorized representative.

6. In the event that a part was not recorded as used and is determined to be missing, the following process must be followed:

Quality Control C.1.1.19 Quality Assurance The Contractor must maintain a quality program as a means of assuring compliance with all requirements of this contract and SOW. The Contractor must maintain a Quality System IAW American National Standard Institute (ANSI)/ASQC Q9001-2008 and ISO 9000-3. The Contractor must assure, as a minimum, that the following items and guidelines are included in the Contractor’s Quality System Program:

1. Sufficient, independent responsibility, and authority are granted to assigned quality personnel so that quality problems can be identified and evaluated, reported upon, and solutions recommended without fear of reprisal, intervention, or adverse action.

2. Software quality evaluations and internal in-process reviews are conducted, results are documented, and recommendations acted upon.

3. Adequate configuration management is performed throughout the life cycle.

4. All tests and inspections are performed in compliance with contract requirements and all test data is complete, correct, traceable, repeatable, and acceptable.

5. Calibration systems and measuring and test equipment: The QSP must describe the methods, procedures, and controls to be utilized to maintain measuring and test equipment.

6. Government Furnished Property (GFP): The QSP must be updated to provide for the above procedures and controls for the added GFP.

7. Site maintenance, and support services: The QSP must describe the methods, procedures, and controls to ensure the services meet the contract requirements.

The Contractor must require of sub-tier suppliers a quality system achieving quality control of the services and supplies provided.