J-1 TnT SOW Amendment 0003.pdf

DTFACT-16-R-00001-0003

PART I - SECTION C

DESCRIPTION/SPECS/WORK STATEMENT

Terminal And Technical Operations Second Level Maintenance Support (TnT)

TABLE OF CONTENTS

1.1 Purpose

1.2 Background

1.2.1 Maintenance of Existing NAS Systems

1.3 Systems and Services Designated for TnT Support

1.3.1 Baselining and Maintenance of Capital Improvement Program Systems

2 REFERENCED DOCUMENTS

2.1 Commercial Standards

2.2 Government Documents

2.3 Instructions to Obtain Government Documentation/Information

3 REQUIREMENTS

3.1 General Requirements

3.2 Labor Category Skill Levels and Descriptions

3.2.1 Contractor Work Team

3.2.2 Secret Security Clearance Requirements

3.3 Government Furnished Property List

3.4 General Task Definitions

3.4.1 System Support Directives (Support Role)

3.4.2 Engineering Studies

3.4.3 Maintenance Handbooks (HBKs)

3.4.4 Document/Data Analysis and Review

3.4.5 Optimization and Restoration of NAS Facilities

3.4.6 Information Systems Security Requirements

Information System Security (ISS) Support ............................................. 17 3.4.6.1

3.4.7 Conformance to FAA ISS Standards

3.4.8 Business Operations Support

3.5 Program and Technical TnT Program Requirements

3.5.1 Program/Project Management

Program Manager ...................................................................................... 19 3.5.1.1

Contractor Lead ......................................................................................... 19 3.5.1.2

3.5.2 Post-Contract Award Orientation Conference

3.5.3 Program Planning

3.5.4 Automated Management System

3.5.5 Labor and Material Processing Procedures

Labor Reporting ........................................................................................ 21 3.5.5.1

Material ..................................................................................................... 21 3.5.5.2

3.5.6 Progress Review

DO/NAS-System Review .......................................................................... 21 3.5.6.1

Program Status Review ............................................................................. 21 3.5.6.2

Program Management Review (Mandatory) ............................................. 22 3.5.6.3

DO Completion Report (Mandatory) ........................................................ 22 3.5.6.4

DO Completion Conference (As required by the Government) ............... 22 3.5.6.5

Program Reports (Mandatory) .................................................................. 22 3.5.6.6

Monthly Progress, Financial Summary, and Invoice Reporting ........... 22 3.5.6.6.1

Delivery Order Reporting ..................................................................... 24 3.5.6.6.2

Routine Reporting........................................................................... 24 3.5.6.6.2.1

Out of Cycle Reports ...................................................................... 24 3.5.6.6.2.2

Technical Meetings, Reviews, Demonstrations, Tests and Audits ........... 24 3.5.6.7

Design Reviews, Preliminary and Critical ............................................ 25 3.5.6.7.1

Test Reviews, Readiness and Post-Test ................................................ 25 3.5.6.7.2

Production Readiness Review (PRR) ................................................... 25 3.5.6.7.3

3.5.7 Configuration Management (Mandatory)

3.5.8 Engineering (Mandatory)

3.5.9 Logistics, per each individual DO

Maintenance .............................................................................................. 27 3.5.9.1

Interim Maintenance Support ............................................................... 27 3.5.9.1.1

Full Scale Development (FSD) Phase ............................................ 27 3.5.9.1.1.1

Production Phase ............................................................................ 27 3.5.9.1.1.2

Equipment Shipping.............................................................................. 27 3.5.9.1.2

Design-Disclosure/Reprocurement Data Package ................................ 28 3.5.9.1.3

Support Equipment/Software ................................................................ 29 3.5.9.1.4

Initial Spare Parts .................................................................................. 29 3.5.9.1.5

3.5.10 Training, per each Individual DO

Training Plan ............................................................................................. 30 3.5.10.1

Academy Training ..................................................................................... 30 3.5.10.2

3.5.11 TnT Installation Plans, per each Individual DO

3.5.12 Production, per each Individual DO

3.6 Documentation For Each Individual DO

3.7 Commercial, Industry-Standard Availability

4 QUALITY ASSURANCE REQUIREMENTS, AS SPECIFIED IN INDIVIDUAL

DELIVERY ORDERS

4.1 General Test Requirements

4.2 Test Documentation

4.2.1 Test Plan

Requirements Verification Traceability Matrix (RVTM) ......................... 33 4.2.1.1

4.2.2 Test Records and Reports

4.3 Inspections, Demonstrations and Tests

4.3.1 Workmanship Inspection

4.3.2 Reliability Verification

4.3.3 Maintainability Verification

4.3.4 Key Site Testing

4.3.5 Site Acceptance Testing

5 PREPARATION FOR DELIVERY

6 RESERVED

APPENDICES

Appendix 1 Acronyms and Abbreviations

Appendix 2 TnT Deliverables

Mandatory TnT Deliverables

Typical DO Schedule/Deliverables (per each DO)

Appendix 3 List of Current Systems

TERMINAL SYSTEMS

TECHNICAL OPERATIONS SYSTEMS

SCOPE

1.1 Purpose

This document specifies the responsibilities of the contractor to ensure the timely accomplishment of the requirements defined within Terminal and Technical Operations

Second Level Maintenance Support (TnT) contract and its Delivery Orders (DO).

1.2 Background

The National Airspace System (NAS) is the air traffic controller's tool that enables the

Federal Aviation Administration (FAA) to fulfill its mission to provide safe and efficient use of national airspace. The NAS is comprised of the following systems and subsystems:

a. Radar target, and weather detection,

b. Flight data and supporting processing systems,

c. Air traffic processing and display systems within the Flight Service and Terminal air traffic control environments,

d. Communications systems, flight plan data information systems, and

e. NAS maintenance and support systems.

The NAS is identified in the FAA configuration control document NAS-MD-001. FAA

Order 1100.157A requires Operations Support Services to perform second-level maintenance engineering upon many NAS systems/subsystems. Personnel at NAS field facilities perform first-level NAS maintenance functions of on-site repairs, preventative maintenance, system certification, and generation of trouble reports and casefiles. National second-level maintenance typically consists of providing:

a. Restoration assistance, remotely or on-site when requested to support first level personnel.

b. Development, testing, and production of engineering solutions in response to NAS problem reports and approved casefiles.

c. Engineering studies and alternative analysis solutions:

d. Configuration and documentation maintenance, release and control.

e. Assurance of the supportability of new systems before they become deployed into the NAS.

FAA orders and procedures that describe maintenance functions are identified in Section 2 below. Second-level maintenance requires skills and knowledge of the exact detailed as-built construction of the hardware, software, and documentation of the mission and support systems for each NAS system in order to respond to its mission for Terminal, Technical

Operations, Oceanic and NAS Maintenance Systems (referred to herein as Second Level

Engineering (SLE)). Each of the NAS systems is a uniquely constructed application, and is supported by both common and unique support equipment and software tools. The contractor may be tasked to support Second Level Engineering in all aspects related to the functions that follow.

The FAA also supports executive level and agency level initiatives and policies to include:

a. Safety Management

b. Information System Security

c. Integrated Capability Maturity Model (iCMM)

d. Process Improvement

e. Test & Evaluation Gold Standard

f. Air Traffic Organization (ATO) Best Practices

g. Program Management Office (PMO)

h. Administrative System Support

1.2.1 Maintenance of Existing NAS Systems

The NAS contains many diverse systems, the age of which often presents obsolescence-driven supportability problems that require engineering solutions. Spare components with which to repair failed modules may be unobtainable and spare units may be depleted.

Some systems contain software that was developed with peculiar languages, compilers and support platforms that are no longer used or supported. Supportable, functionally identical replacement items may need to be designed, developed, tested, acquired and implemented to keep the NAS functioning. Other NAS systems include more advanced technology and state-of-the-art hardware and software.

New hardware, software and support items must be functionally interchangeable with the items being replaced to minimally impact existing performance standards and to minimize expensive requalification testing. Specific FAA requirements are identified through analysis of field facilities problem reports, and as NAS Configuration Control Decisions

(CCD) for casefiles are approved for system implementation.

1.3 Systems and Services Designated for TnT Support

It is not possible to define and describe the many unforeseen requirements that may occur during the course of this contract. There may be requirements for other related types of tasks to be performed under this contract not yet known to the FAA. These tasks could include but not be limited to such things as quality assurance, process improvement plans of the FAA, information security, NAS facility security and others. These type tasks may not be considered related to the technical aspects of the NAS. However, they are intimately related to system performance, system integrity and system security of the NAS.

As a result, the contractor may be required to perform a variety of these type tasks during the period of this contract.

The list below is the Government’s best estimate to date of the systems and services intended for support under this contract. This list is not all-inclusive and, when in the best interest of the Government, is subject to change to allow optimum use of the FAA’s resources. It may also be necessary for the contractor to support systems under other FAA organizations to help support the NAS environment.

It is intended that the TnT contractor must provide capability to support the following FAA organizations and activities:

a. Terminal

b. Communication, Flight Service and Weather Engineering

c. National Airway Systems Engineering

d. Information Systems Security

e. Administrative Computer Systems

f. Business Operations

Note: See Appendix 3 for a full list of systems

1.3.1 Baselining and Maintenance of Capital Improvement Program Systems

The FAA is modernizing and improving the performance and supportability of the NAS to meet the agency’s short and long-term goals. During the acquisition phase of modernization programs, selected contractors will produce deliverables pertaining to system-baseline descriptions, installation, and testing that will necessitate a considerable review and audit effort. SLE will contribute to definitions of supportability requirements, monitor development, perform system testing to ensure the system's supportability, receives the program library baselines, support NAS integration/testing and commissioning, and then assume level-2 maintenance responsibility.

2 REFERENCED DOCUMENTS

References provide direction, guidance, or information for the development, delivery, or maintenance of NAS products or services. Since references may evolve, become ineffective, or obsolete, the contractor may request a waiver from the Administrating

Contracting Officer (ACO) for relief from adherence to particular references. Similarly, the ACO may impose a requirement for adherence to new references during the life of the contract. New references will be limited to those that are a natural outgrowth of changing system support requirements or those that should have been included initially, based upon current industry standards and guidelines. The contractor is expected to have the technical and administrative flexibility to comply with evolving support requirements. Each

Delivery Order is expected to identify exceptions or new requirements. To be valid, each

DO must be approved by the ACO.

2.1 Commercial Standards

Document Title

ANSI/EIA 748C Earned Value Management Systems

ASTM D3951-98(2004) Standard Practices for Commercial Packaging

2.2 Government Documents

Title

MIL-HDBK-217F(2) DoD Guide for Achieving Reliability, Availability and

Maintainability

MIL-HDBK-470A Designing and Developing Maintainable Products and

Systems

MIL-HDBK-781D Reliability Test Methods, Plans and Environments for

Engineering Development, Qualification and Production

OMB Circular A-11 Preparing and Submitting Budget Estimates

OMB Circular A-130 Management of Federal Information Resources

ISS Order 1370.83 Internet Access Points

ISS Order 1370.84 Internet Services

ISS Order 1370.79A Internet Use Policy

ISS Order 1370.81A Electronic Mail

ISS Order 1370.82A Information Systems Security Program

ISS Order 1370.92A Password and PIN Management Policy

NAS-MD-001 National Airspace System Master Configuration Index

FAA Acquisition Management System (AMS)

FAA Capital Investment Plan

HRPM V12 WLB 12.3 FAA Telework Program

2.3 Instructions to Obtain Government Documentation/Information

Specifications, standards, and specification amendments/supplements that are referenced in approved Requests for Proposals (RFPs) can be obtained from the sources identified below.

Requests should fully identify: FAA as the procuring agency, the William J. Hughes

Technical Center (WJHTC) as the procuring organization, name of the FAA contracting officer, RFP number, and the material desired, i.e., specifications, standards, amendments, supplements. Request all items by document number. Electronic versions of the documents should be obtained if available.

If DoD/Military specifications are cited in FAA documents, copies of Military specifications and standards can be obtained from:

Document Automation and Production Service

Building 4/D

700 Robbins Ave.

Philadelphia, PA 19111-5094

Telephone: (215) 697-2664

Fax: (215) 697-9398

Department Of Defense (DoD) Single Stock Point Web Site (DODSSP) everyspec.com

Federal Standards referenced in FAA specifications are available at:

http://f10011.eos-intl.net/F10011/OPAC/Index.aspx

If the contractor does not have access to an identified referenced documents, please contact the Contract Specialist.

3 REQUIREMENTS

3.1 General Requirements

The contractor must provide all necessary qualified personnel, services, tools, and materials to satisfy the TnT requirements consisting of management, engineering, specific custom hardware and software/firmware design, production, installation and integration, testing, reporting and documentation as specified within: this document; SLE internal procedural control guidance (SSD/iCMM)); and the specific clarifications, quantifications and instructions of each individual Delivery Order (DO) related to NAS systems identified herein to enable immediate response to NAS problem reports and restoration requirements, as directed by SLE. When numbers of days are identified in delivery requirements, days are calendar days unless otherwise specified. This document describes two types of requirements:

a. Mandatory TnT requirements for program planning, contract transition, and contract management.

b. General requirements for level-2 maintenance and the range of possible requirements for individual DOs. A large-scale complex DO may specify all of the requirements herein, while a small DO may specify only a few.

The articles acquired under this contract must be provided by the contractor, fully assembled and complete in all details upon delivery to the destinations identified within each DO. Installation at the FAA field facilities will normally be performed by local FAA personnel.

Additionally, The contractor will be supporting the FAA as it monitors the progress of

FAA development efforts outside of this contract. In this role, the contractor is not expected to originate many aspects of a development contract including, but not limited to

Preliminary Design Reviews/Critical Design Reviews (PDR/CDR), Inspections, First

Article Test, Production Readiness Reviews (PRR), Configuration Management, System

Support directives (SSD), or Earned Value Management (EVM). The contractor is expected to understand the concepts behind these activities and have to the expertise to assist the FAA in effectively monitoring and supporting these activities.

3.2 Labor Category Skill Levels and Descriptions

See attachment for a list of detailed labor category definitions and levels that the FAA considers appropriate for the TnT effort. Other positions may be required at the discretion of the FAA.

3.2.1 Contractor Work Team

Personnel provided under this TnT contract may be required to work with other contractors and personnel from other Federal agencies in support of their DO.

Personnel such as secretaries, administrative assistants, accountants, and business managers whose primary responsibility is corporate rather than Government support are not directly billable to the contract.

Contractors are also required to comply with dress code requirements comparable to the

FAA facility they support.

3.2.2 Secret Security Clearance Requirements

When a contractor is required to have access to classified national security information

(CNSI), the government will inform the vendor by DO. The contractor must obtain and maintain a DOD issued Secret Security Clearance, hereafter referred to as Clearance but not to be confused with a NACI and at no cost to the FAA, for the employee and certify that employee’s clearance to the FAA Servicing Security Element (identified in item 13 of the DD Form 254.) A government issued personnel security clearance is not required for access to Sensitive Security Information (SSI). SSI is not classified information as defined under Executive Order 13526.

The contractor staff is prohibited from accessing or being afforded access to CNSI [by federal law, Executive Order and federal regulation] until the appropriate clearance is granted by the Defense Industrial Security Clearance Office (DISCO) and the person has executed the SF-312 Classified Information Non-Disclosure Agreement, and the contractor has certified the clearance to the FAA SSE. Contractors only requiring access to SSI do not require a personnel security clearance. If an interim Clearance is requested by the FAA for work to begin until a full clearance is either completed, or denied, then the vendor will adhere to the process for obtaining required level interim clearance to be issued by

DOD/DISCO and the Clearance certified to FAA security.

The contractor staff will need to discontinue classified work if a final Clearance is denied or pulled, but may continue on SSI/non-classified work if NACI clearance is received at the discretion of the FAA.

The FAA has determined the following labor categories may require a Secret Security

Clearance: Engineer, Computer Scientist, Technical Specialist, and Information

Assurance/Information Security Specialist (IA/IS). The FAA will advise the vendor by way of DO which positions require a Clearance.

On a quarterly basis the contractor must provide to ACT-8, or the FAA equivalent, and to the Contracting Officer Representative (COR), a report detailing the Clearance status of each individual employed on the DO who is required to possess a Clearance. The FAA will not responsible for any costs associated with obtaining a Clearance. When individuals are not able to obtain and maintain the required Clearance, they may no longer be approved for employment and to work on that DO. The contractor is still obligated to fulfill the requirements of the DO.

3.3 Government Furnished Property List

The Government provides telecommunications, furnishings, equipment and tools as can be made available to the contractor onsite at the Government’s facility. The contractor is expected to provide to its offsite employees all other telecommunications, furnishings, equipment, tools, computers and all other equipment required to perform under this contract. This hardware and software must be compatible with FAA's systems, equipment, and policies. If Government Furnished Equipment (GFE) is provided to an offsite employee as identified in a DO, the contractor must maintain property records of the GFE and comply with requirements for procuring and handling material.

The contractor may use the agency’s Local Area Network (LAN), maintenance systems that are used to support the NAS, hard and soft tools to support the engineering and manufacturing effort, and the software that is made accessible to them within those services.

The contractor will require access to the FAA systems for installation, checkout and testing. The contractor must follow FAA procedures and policies for scheduling those accesses and activities and for obtaining the necessary clearances. System time and resources will be furnished, as available, by the Government subject to the contractor's requests. The contractor's plans and requests must identify the specific FAA resources and their amounts that are required for each part of their work. The contractor's requests must identify personnel, tools and equipment that require access to Government property. The contractor must protect all items from damage and must follow prescribed FAA maintenance and procurement procedures regarding property.

The contractor must supply, maintain and calibrate all items of general-purpose test equipment required for the performance of the tasks.

3.4 General Task Definitions

In conducting the following activities in support of the FAA’s mission, the contractor must follow the FAA’s SLE processes and practices to resolve NAS issues or implement new requirements. The following consists of general information and requirements that must be used by the contractor (Specific clarification and quantification will be provided by the

Delivery Order when problem reports or requirements are requested to be resolved.):

a. System Support Directives (SSD) and Maintenance Handbooks – SSDs and

Handbooks are the governing documents defined in applicable FAA Orders, which describe the SW/HW development, delivery and distribution as well as equipment preventative maintenance and certification. Second Level Engineering is committed to the use of the SSD and Handbook methodology and the requirement is imposed upon the contractor to support its utilization.

Current SSD components include:

SSM - Transmits system hardware, software, and plant modifications to the field.

SDR - Delivers technical issuance documents or document change pages.

STR - Delivers technical system information that does not qualify as an SSM, Commercial-Off-The-Shelf (COTS) patches, and configuration changes.

b. iCMM – is adopted by SLE as the guiding standard for use in product development/delivery. The contractor will be required to implement iCMM principles into its support processes.

c. The Test and Evaluation (T&E) Gold Standard has been adopted by SLE as the guiding standard for use in product development/delivery. The contractor will be required to implement the FAA T&E Gold Standard principles into its support processes.

d. Safety Management System (SMS) – The SMS integrates current FAA safety-related operational policies, processes and procedures as well as introduces new elements necessary for a systems approach to managing the safety risk of providing

ATC and navigation services.

e. Information System Security is a required component of the operational lifecycle for information systems in the NAS. System Security includes, but is not limited to, components such as Network Intrusion Detection Systems (NIDS), firewalls, smart cards, and COTS security. The FAA requires a Security Authorization Package

(SAP) as well as a Certification and Accredidation (C&A) audit for all information systems to analyze security risks and recommend mitigation activities. The C&A audit and the SAP are based upon standards developed by the National Institute of

Standards and Technology (NIST) and require in-depth technical assessments, including extensive security testing.

f. Engineering Studies – to research issues, develop solutions to hardware/software issues, provide alternative analysis for sustainment programs or develop prototypes.

3.4.1 System Support Directives (Support Role)

1. The SSD is a transmittal used to issue system modifications, safety modifications, technical data, and documentation releases for a particular system (or systems). The contractor must provide resources to accomplish the analysis, need/change request, requirements packaging, design, development, production testing, system testing, documentation, keysite testing, delivery and installation of modifications to NAS systems. These modifications may be to software, hardware, firmware, or COTS and will be implemented via an SSD performed In Accordance With (IAW) the applicable order. The transmittal may be as a result of an approved Change

Vehicle such as a NAS Change Proposal (NCP), Program Technical Report (PTR), or Hardware Discrepancy Report (HDR). In performing design and development, every effort must be made to minimize the changes required to implement the resultant fielded SSD. The SSD must be designed and implemented so as to require only minimal changes to the hardware or impacted software programs. Any suggested changes to hardware or software programs must be defined during the engineering analysis of the work efforts. The impact on the hardware and software programs must be defined in sufficient detail to allow the DO FAA designated official to provide direction. The reliability, maintainability, operational effectiveness, operator interface, and documentation must be provided to the

Delivery Order Contracting Officer Representative (DOCOR) or DO FAA designated official for use in determining the course of action. When appropriately authorized IAW the procedures herein this SOW, the contractor will design and develop/fabricate prototypes, including printed circuit boards and other hardware and/or software components as deemed necessary.

2. An analysis of the affected software/hardware must be made. The affected areas must be identified and corrective action proposed. A thorough analysis of the proposed corrections must be made to assure that a new problem is not introduced.

The contractor must conduct a formal design review. In the event that a non-reproducible problem is being resolved, the contractor must be able to demonstrate, through analysis, that the suspected error would, in fact, cause the problem that had been experienced.

3. No degradation to the hardware, software program, or operation must result due to the SSD method used for implementation. Any suspected impact or risk must be made known and must be documented to the DO FAA designated official when uncovered.

4. The contractor must develop a test plan, test documentation and test report to be approved by the DO FAA designated official to verify that the problem has been resolved and no new problems have been introduced.

5. The contractor must provide configuration control on the source code, object code, drawings, and accompanying engineering documentation in accordance with SLE

Processes.

6. The contractor must provide quality control to assure that the approved Change

Vehicle is resolved, the documentation is updated and reflects the resolution, and the testing is performed so that the output is correct, verifiable, validated, repeatable, and error free. In addition to modification testing, full system testing may also be required. The contractor may also be asked to update system test procedures.

7. The contractor must perform the following documentation and configuration management tasks:

a. The contractor must record and track all assigned Change Vehicles and prepare appropriate discrepancy report for all software/hardware problems that the contractor identifies in accordance with the FAA Second Level Engineering processes.

b. The contractor must prepare and coordinate through the DO FAA designated official all document publications and related art work through all stages of processing.

c. The contractor must provide technical editing and proofreading for all documents delivered as part of the SOW and all documents generated for SLE.

d. The contractor must provide for the typing and data entry of all text from draft documents, with subsequent delivery of updated documents.

e. The contractor must provide for the drafting of any art work or software flowcharts, including briefing materials, and drawings, as required.

f. The contractor must provide, as needed, electronic and mechanical drawings using Computer Aided Design (CAD) software (such as PCAC, Autocad) for the production of manufacturing data packages.

g. The contractor must be responsible for performing configuration management

IAW SLE practices and policies. This applies to all data delivered.

h. The contractor must follow the FAA process for the review and delivery of

SSDs. Following the official FAA approval of Change Vehicles , and assignment of SSD number, the contractor may have the primary responsibility for the preparation of all SSD documentation. The following must be provided/updated as required in support of SSD preparation:

1). Details of required hardware/software changes

2). Logic, schematics, diagrams and drawings, parts list, flowcharts

3). Test procedures and personnel for verification of modification

4). Test report following completion of testing

5). Personnel for field installation of modification

6). Installation procedures

7). NAS documentation, page control charts

i. The contractor must submit copies of the draft SSD to the DO FAA designated official for review and approval, disapproval or recommended changes. The

DO FAA designated official will review the SSD for technical accuracy and completeness at the time of approval of the SSD, the DO FAA designated official must also assure that any required forwarding addresses are provided.

8. The contractor must support the production of SSD kits. An SSD kit is generally defined as the physical elements (hardware, firmware, etc.) which must be provided to change the form fit, function, or performance of NAS equipment to meet a required change, upgrade, or reconfiguration. The SSD text includes the documentation necessary to accomplish the modification, identify software/system impact, update revision/configuration data, and provide for diagnostic and maintenance support (theory, parts lists, etc.). An SSD package is defined as all products (kit, documentation, etc.) required to complete the modification to electronic equipment such that the change will be supportable over an extended period of time. To the extent specified by the DO FAA designated official in a formal assignment, the contractor will be responsible for design, development, verification, documentation, packaging, delivery, and installation of all items in support of modifications to equipment in support of an SSD activity. The contractor assumes responsibility for all SSD products or services that may be obtained through subcontractor(s).

SLE’s process documents provide the technical and managerial guidelines for SSD design, development, testing, keysite testing, packaging, and delivery. The contractor, as a professional and skilled support organization, has a responsibility to make the DO FAA designated official aware of conflicts between SLE’s processes, the contract, or other guidance in the development of SSDs.

When necessary the ACO will resolve outstanding conflicts. The COR will provide the

ACO with technical information to help in conflict resolution. The COR, with technical input from the DOCOR, may challenge any element of SSD development. Only the ACO can make decisions that affect the contract cost or intent.

The contractor must apply iCMM principles, T&E Gold Standard, SMS, Operations

Support Team processes, and SSD practices in SSM development, unless otherwise directed by the DO FAA designated official.

The contractor must use the guidance of references in this SOW, and best software/hardware development practices in SSD design, development, documentation, testing, delivery, and packaging.

The contractor has a responsibility to meet with the DO FAA designated official prior to work initiation to seek approval/concurrence in standards/approaches for SSD development. The contractor must document the agreement through minutes of a meeting, as required.

The contractor must use the software and hardware design practices used by the SLE organization for the design and development of the SSD. The contractor has the responsibility to ensure that, over the life of the contract, software and hardware engineering practices are consistent with the standards used by the the SLEs..

The contractor must consult with the DO FAA designated official before using unproven technological items or approaches. With respect to SSDs, unproven technology refers to technology not currently used within the NAS or not widely used in the commercial arena.

3.4.2 Engineering Studies

An Engineering Study is an assignment to investigate problems, collect information, develop prototypes/proof of concept and/or provide recommendations to resolve existing problems.

In support of the FAA mission the contractor must provide resources to accomplish required analysis, alternatives and provide a recommendation. The contractor must follow the engineering study process provided by the SLE organization.

3.4.3 Maintenance Handbooks (HBKs)

As part of the FAA mission, Maintenance Handbooks will be developed in accordance with applicable orders and processes. The contractor must provide all necessary services to accomplish this task, including but not limited to technical writing, typing/word processing, technical illustration, proofing, preparation of camera ready copy, electronic files, or other format, as required. In addition, the contractor must provide testing, delivery, and packaging support, as needed. Timelines associated with development and update of the

Maintenance Handbook are identified in the awarded DOs.

3.4.4 Document/Data Analysis and Review

The contractor must provide resources to accomplish analysis of NAS system documentation, SLE documentation, FAA documentation, and documentation associated with new technologies that will support the FAA mission. The reviews and comments must provide a detailed analysis of the approach, validity of data used in the document, analysis of the document’s discussions and conclusions as well as its compliance with the specifications and standards. In addition, the contractor may be required to accompany

FAA personnel to design review meetings Technical Interchange Meetings and in process reviews as a technical advisor. Following the meeting, the contractor must provide the DO

FAA designated official with a written report detailing the results of an analysis of the data acquired in the meeting.

3.4.5 Optimization and Restoration of NAS Facilities

The contractor must provide engineering services for the restoration, integration, optimization and maintenance of NAS systems in support of the FAA mission. SLE provides field restoration support for NAS systems. This support is available 24 hours a day and may require telephone support or travel to the facility. The DO FAA designated official authorizes all field support activities. The contractor must use the following guidelines whenever a visit to the site is required in support of this task.

1. The contractor must participate in a pre-investigative meeting involving site/regional members to:

a. Develop a plan of action

b. Define roles

c. Develop a schedule

2. Prior to departing the site, the contractor must support the activity to:

a. Debrief site personnel

b. Determine status of the facility

c. Determine required follow-up actions

3. The contractor must prepare a comprehensive trip report of the activities performed during the trip and any required follow up actions. The trip report is due to the DO

FAA designated official who authorized the on-site support, within three working days after return.

The Contractor must be reimbursed for actual reasonable transportation costs and actual reasonable subsistence costs incurred during performance of the contract, not to exceed those rates applicable to Government employees. See Section G of the Screening

Information Request (SIR) for additional details.

3.4.6 Information Systems Security Requirements

Information System Security (ISS) Support 3.4.6.1

As part of its support for the FAA mission, the contractor must provide security support and services in any or all of the 10 security domains as defined and described by The

International Information Systems Security Certification Consortium (ISC²) ® Certified

Information Systems Security Professional (CISSP) ® certification. The ten domains are as follows:

1. Access Control – a collection of mechanisms that work together to create security architecture to protect the assets of the information system.

2. Telecommunications and Network Security – discusses network structures, transmission methods, transport formats and security measures used to provide availability, integrity and confidentiality.

3. Information Security Governance and Risk Management – the identification of an organization’s information assets and the development, documentation and implementation of policies, standards, procedures and guidelines.

4. Software Development Security – refers to the controls that are included within systems and applications software and the steps used in their development.

5. Cryptography – the principles, means and methods of disguising information to ensure its integrity, confidentiality and authenticity.

6. Security Architecture and Design – contains the concepts, principles, structures and standards used to design, implement, monitor, and secure, operating systems, equipment, networks, applications, and those controls used to enforce various levels of confidentiality, integrity and availability.

7. Operations Security – used to identify the controls over hardware, media and the operators with access privileges to any of these resources.

8. Business Continuity and Disaster Recovery Planning – addresses the preservation of the business in the face of major disruptions to normal business operations.

9. Legal, Regulations, Investigations and Compliance – addresses computer crime laws and regulations; the investigative measures and techniques which can be used to determine if a crime has been committed and methods to gather evidence.

10. Physical (Environmental) Security – addresses the threats, vulnerabilities and countermeasures that can be utilized to physically protect an enterprise’s resources and sensitive information.

When required by the tasking organization, the Contractor must participate in providing consultation with and technical support to other FAA organizations and FAA project partners. This may include working with employees of other contracting companies or other government agencies in order to achieve the FAA’s project requirements.

3.4.7 Conformance to FAA ISS Standards

In all tasks performed, the contractor must adhere to ISS policies, standards, orders, guidelines and directives. FAA tasks performed at a Contractor’s facility are subject to the same requirements levied on tasks performed in an FAA facility. This includes:

1. Methods of storing, handling, marking, and disposing of classified and sensitive unclassified information.

2. Conformance with rules of behavior for network access and use including Virtual

Private Networks (VPNs) and telework.

3. Certification and authorization support activities in conformance with ISS Program

Office methods and directives and applicable NIST Special Publications.

4. Auditing of configurations of security devices and processes.

5. Recommendations for and adherence to physical security as it applies to IT and ISS.

6. Application development and updates.

3.4.8 Business Operations Support

Business Operations Support addresses process improvement, ATO/PMO best practices, and office automation tools including, but not limited to Microsoft Word, Excel, and

Project. The contractor must support policy and standards planning including: resources, approach, schedules and risk. The contractor must prepare plans in accordance with FAA forms and templates. The contractor must support policy and standards definition and development including: technical documentation research, interviews, data analysis, engineering studies and pilot studies. The contractor shall develop, manage and maintain policy and standards documentation in accordance with FAA forms and templates. The contractor must support policy and standards implementation including: notification, coordination and control, familiarization and training and field support. The contractor must support policy and standards monitoring, reporting and improvement definition and analysis, compliance/non-compliance and recommendation reporting. The contractor shall assist FAA personnel in the performance of financial, quality assurance, and property and security audits. Additionally, the contractor may be required to perform these audits independent of government supervision.

3.5 Program and Technical TnT Program Requirements

3.5.1 Program/Project Management

Work is ordered and managed under the TnT contract by DO. DOs break down the contract scope and cost into specific, manageable elements of the overall contract SOW requirement. SLE identifies and defines all requirements within DOs and that guides the contractor efforts. The contractor must report on the percentage of DO work performed by budget expenditure for each DO as specified in 3.6.6.1.

Program Manager 3.5.1.1

The Program Manager (PM) must meet the Program Manager labor category description provided in Part I - Section J, Labor Category and Skill Level.

Contractor Lead 3.5.1.2

The contractor must designate personnel with Contractor Lead responsibility. Contractor

Leads are responsible for assignment of work, management of personnel, financial, operations and technical programs within the specific area and ensures that projects are fully planned and controlled, that goals and objectives are set. Prepares responsive proposals and may participate in the negotiation of its proposals with the ACO/COR, ensures that program responsibility is assigned, and fully records and documents the events and results. Possesses specific knowledge of all technical and management requirements within the specific area in which they lead. This designated contractor lead is considered a

“Working Lead” wherein about 10% to 20% of their time is devoted to administrative functions and the remainder is applied directly to the delivery order labor category in which they bill. The following conditions apply:

1. The Contractor will nominate a Contractor Lead for FAA approval.

2. For large, high value or complex DOs, the Contractor Lead must be an employee of the prime contractor. For Other DOs, the Contractor Lead may be employed by a subcontractor.

3. The COR and the DOCOR must approve in writing the designated Contractor

Leads.

4. Every person on the contract must have a designated Contractor Lead.

The contractor must submit to the COR, quarterly, a report identifying the Contractor

Leads and the personnel for whom they are responsible.

3.5.2 Post-Contract Award Orientation Conference

The purpose of the conference is to aid both Government and contractor personnel to:

1. Achieve a clear and mutual understanding of all contract, management, and technical requirements.

2. To identify and resolve potential problems.

3.5.3 Program Planning

The contractor is instructed to produce detailed planning which must include:

1. Current organizational charts

2. Staffing Plan, and supporting written commitments that includes:

a. Personnel assignments in each labor category utilized in each technical system/area and administrative functions.

b. Utilization of full-time dedicated, part-time staff, and short-term hires allocated to technical and administrative functions.

3. Facilities and Resources plan and its physical and performance relationship to the staffing, as required.

4. Mileage reimbursement policy. The Government will not allow local travel reimbursed within a 30-mile radius of the WJHTC or other assigned duty station.

5. Off-site Management Plan will be submitted to the COR for acceptance at the contract Kick-Off Meeting. In it the contractor will detail its corporate provisions and approach for the management and monitoring of telecommuting (telework) or remote site TnT contractor employees. At a minimum the contractor plan will meet the requirements of the FAA Telework Policy.

6. In the case of conflict, the FAA Continuity Of Operations (COOP) plans will take precedence over the contractor’s Off-site Management plan.

3.5.4 Automated Management System

A COR-approved automated database must be used to record the complete record for every

DO, from the initial entry of a DO through the generation of the DO Completion Report.

This information must include:

1. DO number

2. Title

3. Milestones

4. Contact persons

5. Travel requests

6. Purchase requests

7. Cost estimate breakdown (labor, travel, and materials)

8. Actual cost breakdown (labor, travel, and materials)

9. Reports and other records, as needed.

Reports are generated which contain fully loaded categorical and total costs.

As directed by FAA DOs, the contractor must:

1. Diagnose defects in the operation of the database and repair the defective software to restore it to effective accurate operation.

2. Implement functional improvements.

3. Maintain a backup of the database, which complies with FAA Disaster Recovery directives.

3.5.5 Labor and Material Processing Procedures

Labor Reporting 3.5.5.1

The contractor must allocate, record and report every hour for every person, including its subcontractors, that is directly charged to the contract to the correct assigned DO. A time reporting procedure must be used by the contractor to satisfy this requirement.

Material 3.5.5.2

The contractor must report all DO material charges by DO reference to comply with contract reporting and billing requirements.

See Section G of the SIR for additional details.

3.5.6 Progress Review

DO/NAS-System Review 3.5.6.1

The FAA may identify requirements within a DO for periodic progress reviews. The FAA and the contractor may see the need for periodic progress reviews regarding an individual

DO or a group of DOs within a system segment. The contractor must follow the guidelines for reviews and meetings above, document its compliance and problems, and satisfy the informational requirements.

Program Status Review 3.5.6.2

The DOCOR(s) may request a Program Status Review meeting. Participants include, at a minimum, the DOCOR(s) or DO FAA designated officials and the Contractor Lead(s).

The Program Manager may also be requested to attend. The frequency of meetings is dependent upon the complexity and scope of the program efforts at the time and the degree of difficulty being experienced. The frequency of these meetings is identified in the DO.

The COR or DOCOR is responsible for alerting the contractor of the requirement for the meeting. The FAA prepares the agenda, schedules and locates the meeting, and provides the agenda to the contractor two working days in advance of the meeting. The contractor may suggest additional agenda items following its review of the agenda. The contractor must record meeting minutes and action items and publish the meeting report including agreements, action items and status.

Program Management Review (Mandatory) 3.5.6.3

The contractor must make a presentation to SLE management twice per contract year regarding overall status, funding analysis/expenditure report, significant performance variances, non-compliance and corresponding corrective actions being taken, expenditures and progress and other issues. Additional presentations may be requested by the FAA if deemed necessary. The contractor will provide a written version of the presentation one-day in advance to the COR and the designated SLE management.

DO Completion Report (Mandatory) 3.5.6.4

Within sixty (60) days following completion, secession of work or deobligation of funds on a DO, the contractor will provide to the ACO, COR and the DOCOR a DO Completion

Report. The Completion Report (CR) transmits final deliverables, identifies the delivered items and their acceptance status, identifies the categorical (i.e., purchase, travel, labor and total) estimated costs and the actual categorical costs at completion, and defines the contractor's DO compliance to enable closing the DO. The DOCOR, Contractor Lead, and the Program Manager must sign the CR before the DO can be closed.

DO Completion Conference (As required by the Government) 3.5.6.5

The COR or DOCOR may require a conference to discuss the DO completion and other requirements for DO completion.

Program Reports (Mandatory) 3.5.6.6

All contract/DO reports and invoices must contain the following elements:

1. Prime contract number

2. Number and date of transmittal letter

3. Approval required or not required

4. Scheduled due date

5. Approval status (i.e., scheduled approval date and actual approval date)

Reports reflect the recording of DO pertinent information and status and are distributed to the FAA ACO, the COR, Operations Support Team managers, and FAA DOCOR persons as applicable.

Invoices will be delivered in accordance with the instructions in the contract. The contractor must deliver invoice backup data along with an electronic copy of the invoice to the COR and the DOCOR at the time of delivery of the invoice to the Office of…