693KA8-23-R-00014.pdf

SOLICITATION, OFFER AND AWARD

3. SOLICITATION TYPE1. CONTRACT NO. 2. SOLICITATION NUMBER

6. ISSUED BY CODE 7. ADDRESS OFFER TO (If other than Item 6)

5. REQUISITION/PURCHASE NUMBER

NOTE: In sealed bid solicitations "offer" and "offeror" mean "bid" and "bidder"

NEGOTIATED BID (RFP)

SEALED BID (IFB)

4. DATE ISSUED

PAGE OF PAGES

1 2

C. E-MAIL ADDRESS

EXT.NUMBERAREA CODE

B. TELEPHONE (NO COLLECT CALLS)A. NAME

9. FOR

INFORMATION

CALL

CAUTION: LATE Submissions, Modifications and Withdrawals. All offers are subject to all terms and conditions contained in this solicitation.

(Date)(Hour) local timeuntildepository located in copies for furnishing the supplies or services in the Schedule will be received at the place specified in Item 7, or if hand carried, in the

SOLICITATION

8. Sealed offers in original and

PART IV - REPRESENTATIONS AND INSTRUCTIONS

OTHER STATEMENTS OF OFFERORS

EVALUATION FACTORS FOR AWARD

INSTR., CONDS., AND NOTICES TO OFFERORS

REPRESENTATIONS, CERTIFICATIONS AND

LIST OF ATTACHMENTS

CONTRACT CLAUSES

PART III - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACH.

I

J

K

L

M SPECIAL CONTRACT REQUIREMENTS

CONTRACT ADMINISTRATION DATA

DELIVERIES OR PERFORMANCE

INSPECTION AND ACCEPTANCE

PACKAGING AND MARKING

DESCRIPTION/SPECS./WORK STATEMENT

SUPPLIES OR SERVICES AND PRICE/COST

SOLICITATION/CONTRACT FORM

PART II - CONTRACT CLAUSESPART I - THE SCHEDULE

H

G

F

E

D

C

B

A

SEC. DESCRIPTION PAGE(S) (X) DESCRIPTION SEC. (X)

10. TABLE OF CONTENTS

17. OFFER DATE16. SIGNATURE

SUCH ADDRESS IN SCHEDULE.

IS DIFFERENT FROM ABOVE - ENTER

14C. CHECK IF REMITTANCE ADDRESS

EXT.NUMBERAREA CODE

14B. TELEPHONE NUMBER

(Type or print)AND

ADDRESS

OF

OFFEROR

CODE FACILITY

15. NAME AND TITLE OF PERSON AUTHORIZED TO SIGN OFFER14A. NAME

DATEAMENDMENT NO.DATEAMENDMENT NO.

and related documents numbered and dated):

amendments to the SOLICITATION for offerors

(The offeror acknowledges receipt of

13. ACKNOWLEDGEMENT OF AMENDMENTS

CALENDAR DAYS (%)30 CALENDAR DAYS (%)20 CALENDAR DAYS (%)10 CALENDAR DAYS (%)12. DISCOUNT FOR PROMPT PAYMENT the designated point(s), within the time specified in the schedule.

by the offeror) from the date for receipt of offers specified above , to furnish any or all items upon which prices are offered at the price set opposite each item , delivered at

11. In compliance with the above, the undersigned agrees, if this offer is accepted within ______________ calendar days (60 calendar days unless a different period is inserted

NOTE: Item 11 does not apply if the solicitation includes Minimum Bid Acceptance Period .

OFFER (Must be fully completed by offeror)

IMPORTANT - Award will be made on this Form, or by other authorized official written notice.

27. AWARD DATE

(Signature of Contracting Officer)

26. CONTRACT AUTHORITY

24. PAYMENT WILL BE MADE BY

25. NAME OF CONTRACTING OFFICER (Type or print)

CODE 23. ADMINISTERED BY (If other than Item 6)

ITEM

(4 copies unless otherwise specified)

22. SUBMIT INVOICES TO ADDRESS SHOWN IN21. AUTHORITY FOR USING OTHER THAN FULL AND OPEN COMPETITION:

20. ACCOUNTING AND APPROPRIATION19. AMOUNT18. ACCEPTED AS TO ITEMS NUMBERED

AWARD (To be completed by CONTRACT AUTHORITY)

CODE

04/12/2023 X

AAQ310-AFN

AAQ-310 AT FACILITIES & ATC TECH TR

Orville Wright Bldg. (FOB10A), Room 406 FAA National Headquarters 800 Independence Ave., SW Washington DC 20591

1300 ES 05/15/2023

Manish Patel manish.patel@faa.gov

PAGE(S)

Manish Patel

693KA8-23-R-00014

1-2 Excel File

C1-C39 D1 E1-E2

F1-F3

G1-G4

H1-H11

I1-I35

J1

K1

L1-L23 M1-M14

X X X X

X

X X X

X

X

X

X

X

ITEM NO. SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

NAME OF OFFEROR OR CONTRACTOR

2 2

CONTINUATION SHEET

REFERENCE NO. OF DOCUMENT BEING CONTINUED PAGE OF

(A) (B) (C) (D) (E) (F)

693KA8-23-R-00014

This solicitation is for the operation, maintenance, support, and supply of the FAA Tower

Simulation Systems (TSS) used for technical/operational training of controllers at selected FAA air traffic control towers (ATCTs).

The requirements, instructions, and evaluation criteria are described in sections B through M of this solicitation.

693KA8-23-R-00014

PART I - SECTION C

DESCRIPTION/WORK STATEMENT

C-1

Table of Contents

1. SCOPE

1.1. Background

2. APPLICABLE DOCUMENTS

3. REQUIREMENTS

3.1. General

3.2. Program Management (CLIN X001)

3.2.1. Program Control and Status Reporting

3.2.2. Contract Post Award Conference

3.2.3. Program Management Review (PMR) Meetings

3.2.4. Technical Review Meetings

3.2.5. Contractor Spares Management Requirements

3.2.6. Inventory Control of Spares and Repair Parts

3.2.7. Monitor of Vendors for Spares Availability

3.2.8. Risk Mitigation for Parts End-of-Service-Life (EOSL)/Obsolescence

3.2.9. Risk Management Plan (RMP)

3.2.10. Configuration Management (CM) Program

3.2.11. Hardware Configuration Management

3.2.12. Software Configuration Management

3.2.13. Quality Assurance Plan (QAP)

3.3. Integrated Logistics Support (ILS)/RM&A (CLIN X002)

3.4. Training and Training Material Management (CLIN X016)

3.5. Contractor Logistics and Technical Support (CLIN X002)

3.5.1. Support Operation Requirements

3.5.2. Support Operation Tasks

3.6. Training System Support Center (TSSC) (CLIN X002)

3.7. On-site Field Support (CLINs X003)

3.7.1. Field Service Technician (FST)

3.7.2. Field Service Representative (FSR)

C-2

3.8. TSS Installations & Relocations (CLIN X013)

3.9. TSS SDL (CLIN X008)

3.10. TSS Mobile Units (CLIN X006)

3.11. TSS Suitcase (CLIN X007)

3.12. TSS Hardware Components (CLINs X010/X011/X012)

3.13. TSS Maintenance and Technical Support Transition Plans

3.13.1. TSS Transition-In Plan

3.13.2. Transition-In Staffing Plan

3.13.3. Transition-In Execution

3.13.4. TSS Transition-Out Plan

3.13.5. TSS Transition-Out Inventory

3.14. Engineering Services (CLINs X017)

3.15. Purchase of Additional TSS Equipment (CLINs X004 – X011)

3.16. Integration/Acceptance Testing

3.17. Property Management (CLIN X001)

3.18. Other Direct Costs (ODCs) (CLIN X018)

4. ACRONYM LIST

C-3

1. SCOPE

This Statement of Work (SOW) defines the tasks required by the Federal Aviation Administration (FAA) for the operation, maintenance, support, and supply of the FAA Tower Simulation Systems (TSS) used for technical/operational training of controllers at selected FAA air traffic control towers (ATCTs). For clarity purposes the term “Contractor” in this document refers to the company selected to perform the work described in this SOW. All other companies that provide proprietary or Commercial Off The Shelf (COTS) software and/or hardware/equipment used in the TSS will be referred to by name in this document. The tasks required of the Contractor include establishing and maintaining a TSS Program infrastructure that consists of program management, engineering design and support services, equipment purchase, training, depot support, installation and test, and maintenance management of a Contractor Logistics Support (CLS) Program. The TSS CLS Program includes a Help Desk function with technical and Air Traffic Control (ATC) subject matter experts (SMEs), a Training System Support Center (TSSC), on-site Contractor Field Service Representatives/Technicians (FSRs/FSTs), and a Web-Based Integrated Data Environment (WIDE) data repository capability. The TSSC function includes the depot repair and testbed facility for the support of operational TSS equipment. The Contractor for this contract award must establish and maintain a WIDE service. The Contractor is also responsible for providing TSS training and operating, maintaining, and supporting the COTS hardware and software aspects of the TSS. The Contractor must implement a Tech Refresh of all major components in the TSS Large and Small Systems, TSS Mobile Units, and TSS Suitcases. A list of the hardware components required for the Tech Refresh for TSS Large and Small Systems and TSS Mobile Units is provided in Section 3.12 of this SOW and in Section B of this contract. A list of the hardware components required for the Tech Refresh of TSS Suitcases is provided in Section 3.11 of this SOW and in Section B of this contract.

The quantities of each TSS hardware component required for the Tech Refresh for TSS Large and Small Systems, TSS Mobile Units, and TSS Suitcases are provided in Section B of this contract. The Government may provide some or all of the TSS hardware components required on this contract as Government Furnished Equipment (GFE). The system software to be used for all TSS systems on this contract will be provided by the Government as GFE.

1.1. Background

The FAA has fifty-seven (57) TSS Large and Small systems which are deployed at forty (40) ATCTs; two (2) FAA support sites; and one (1) contractor support site. The FAA support sites are the FAA ATC Training Academy in Oklahoma City, OK and the William J. Hughes Technical Center in Atlantic City, NJ. The locations of each of the TSS Large and Small Systems are provided in Attachment J-4 of this contract. The FAA also has forty-two (42) transportable TSS Mobile Units and ten (10) transportable TSS Suitcases which are periodically rotated among smaller ATCT facilities for ATC training purposes. The TSS Large system and the TSS Mobile Unit located at the current TSS contractor support site will be provided to the TSS Contractor as GFE on this contract for TSS engineering design, test, and maintenance support. The TSS training simulators provide a high-definition, realistic simulation of air traffic movements at an airport. A visual database (VDB) which describes the unique physical characteristics of an airport has been developed for each of the forty (40) ATCTs which have a permanently installed TSS system. An additional one hundred and ninety-four (194) airport VDBs have been developed for other ATCTs that are hosted by the forty

(40) ATCT “hub” sites. A ‘hub and spoke’ system utilization concept was instituted by the TSS

C-4

Program to allow the larger airports to host the TSS equipment and provide an ATC training service for the one hundred and ninety-four (194) surrounding smaller airports.

2. APPLICABLE DOCUMENTS

The following documents provide additional information and guidance for the TSS contract and SOW. The version of the following documents in effect on the date of the FAA Screening Information Request (SIR) for this contract form a part of this TSS SOW and are applicable to the extent specified herein this SOW. Applicable documents are subject to revision and it is the Contractor’s responsibility to ensure that the most current version of each document is used and that new applicable documents are adopted. It is the Contractor’s responsibility to notify the Government if any changes in the applicable documents affect the cost, schedule, or performance of this contract.

In the event of conflict between documents referenced herein and the contents of this SOW, the contents of this SOW shall be considered a superseding requirement.

• Federal Travel Regulations (FTR)

• ISO 9001 - Quality Management System – Requirements

3. REQUIREMENTS

3.1. General

This SOW describes the management, technical and logistics support, processes, data, tests, resources, and effort required to support the FAA TSS Program during the contract period of performance. The system performance and operational requirements of the TSS system are specified in the TSS Specification (TSSS), included as Attachment J-1 of the contract. The locations of the TSS Large and Small systems and a list of the TSS VDBs are specified in Attachment J-4 of the contract. The hardware configurations of the TSS Large systems and TSS Small systems are specified in Attachment J-5 of the contract. Other TSS requirements of this contract are specified in additional contract Attachments which are referenced in the related section in this SOW. TSS individual hardware components that may be procured in support of this effort under Contract Line Item Numbers (CLIN) X010, X011, and X012 during the life of the contract are specified in Section

3.12 of this SOW and Section B. TSS Large Systems, TSS Small Systems, TSS Mobile Units, and TSS Suitcases which may be procured on this contract are specified in CLINs X004, X005, X006, and X007 in Section B. The Contractor must submit data in accordance with the Contract Data Requirements List (CDRL) in Attachment J-2 of the contract and the corresponding Data Item Descriptions (DID) in Attachment J-3.

3.2. Program Management (CLIN X001)

3.2.1. Program Control and Status Reporting

The Contractor must establish and provide the program management, control, and reporting functions necessary to manage and direct the tasks required under this SOW. This includes maintaining cost, schedule, and administrative control over the program for both internal and external management of the tasks within this SOW. Program management in support of this contract will also include asset management, data management, financial management, schedule management, risk management, and other related program management functions.

C-5

The Contractor must develop a Program Management Plan (PMP) in accordance with the PMP CDRL A001. The PMP must describe how the requirements and tasks of the contract will be managed, accomplished, and reported by the Contractor during the contract period of performance.

During this period, the Contractor must establish program management controls and procedures required for accomplishing the tasks under this contract. The Contractor must use all tools necessary to provide the progress of the program to the Government’s TSS Program Management Office

(PMO).

The Contractor must designate a Program Manager (PM) with overall program responsibility and who acts as the single point of contact (POC) between the Contractor and the FAA for all matters pertaining to this SOW. The Contractor’s PM will be designated as Key Personnel under this contract and must have the authority to commit corporate resources to ensure the successful completion of authorized tasks. The Contractor must provide a Program Manager with the following minimum qualifications:

• Education – at a minimum, the Program Manager must have a Bachelor of Science (B.S.)

degree from an accredited university in a technical field (e.g., engineering, computer science, etc.)

• Experience – the Program Manager must have a minimum of fifteen (15) years of experience as a project manager for a system or systems similar to, or greater than, the complexity of the

TSS

• Certifications – a Program Manager Professional (PMP) certification from the Project Management Institute (PMI) is preferred but not required

The Contractor’s TSS PM must provide the status of technical and managerial efforts through written monthly reports, telephone conversations, and meetings. The meetings will be held at locations mutually agreed to when requested by the Government’s TSS PMO and the Contractor will be required to provide meeting agendas and take meeting minutes as requested. The Contractor’s PM must provide the monthly reports, meeting agendas, and meeting minutes in accordance with the Monthly Program Status Report CDRL A002, Meeting Agenda CDRL A004, and Meeting Minutes CDRL A005.

3.2.2. Contract Post Award Conference

A Post Award Conference for the TSS contract will be held no later than thirty (30) calendar days after the award of this contract. The conference will be held at a location mutually agreeable to the Contractor and the Government. The Post Award Conference will not exceed two (2) work days.

The Contractor must provide a meeting agenda and meeting minutes for the Post Award Conference in accordance with the Meeting Agenda CDRL A004 and the Meeting Minutes CDRL A005. At a minimum the following topics and their current status must be addressed at the Post Award Conference:

• Contractor Key Personnel

• Contractor Organization Chart and Roles & Responsibilities

• Key Sub-Contractor Team Members

• Staffing Status of Personnel To Work On This Contract

• Summary of each CLIN

C-6

• Contract Questions/Clarifications o Section B o Schedule o SOW o Specification o CDRLs & DIDs o Funding o Contract Risks

3.2.3. Program Management Review (PMR) Meetings

The objective of the PMR Meetings is to address any program management, technical, operation, maintenance, and support issues that occur during the contract period of performance. PMR meetings will be held semi-annually and will not exceed one (1) work day. The PMR meetings will be held at a location mutually agreeable to the Contractor and the Government. The Contractor must submit agendas for these meetings to the FAA for approval and the Contractor must provide meeting minutes in accordance with the Meeting Agenda CDRL A004 and Meeting Minutes CDRL A005.

At a minimum, the following topics and their current status must be addressed at PMR meetings:

• TSS Program status and schedule including the TSS Tech Refresh program in accordance with SOW Section 3.12 and CLINs X010 and X011

• Integrated Logistics Support (ILS) in accordance with the Integrated Logistics Support Plan (ILSP) CDRL A012.

• Training and Training Materials in accordance with Training Materials CDRL A029.

• Risk Management in accordance with PMP CDRL A001

• TSS Service Requests, Deficiency Reports, and Feature Requests

• Quality Assurance in accordance with PMP CDRL A001

• Configuration Management (CM) in accordance with CM Plan CDRL A007.

• System Utilization to include frequency and type of use on a per site basis in accordance with the Monthly Program Status Report CDRL A002

• TSS Operation, Maintenance, and Technical Issues/Concerns

• Installation/integration/acceptance status of changes to existing or new TSS systems/sites (if applicable)

• Action Item Status/Review

3.2.4. Technical Review Meetings

Technical reviews may be requested by either the TSS PMO or the Contractor and will be scheduled and led by the Contractor’s TSS PM or TSS Technical Lead. The Contractor must submit agendas for these meetings to the FAA for approval and must produce meeting agendas/minutes in accordance with the Meeting Agenda CDRL A004 and Meeting Minutes CDRL A005. At a minimum, the following topics must be addressed at technical review meetings:

• Definition and control of modeling issues for site-specific visual databases, if applicable.

C-7

• Review existing or recommended scenario data changes, if applicable, to be included in the scenario database.

• Review changes and additions to the existing VDB design applicable to a specific site visual database or for all sites.

• Define, recommend, and review baseline attributes across the various visual database software builds such as changes in the graphical representation of an item(s) or attribute(s) within a visual database software build.

• Review status of hardware/software trouble report (i.e., Service Requests, Deficiency Reports, or Feature Requests), resolutions, and testing results at affected TSS sites.

• Define, recommend, and review any TSS hardware/software configuration baseline changes, if applicable.

• Identify and review test requirements/strategy provided as Government Furnished Information (GFI) (e.g., factory/site/system acceptance test plans, procedures, standards, etc.) for o The integration/test of resolved hardware/software trouble reports, o Any new hardware/software functionality for the TSS, and

• Review and provide status of any technical issues/concerns that affect or may affect the operation, maintenance, or performance of the TSS. This information must also be reported at TSS PMR meetings.

3.2.5. Contractor Spares Management Requirements

During TSS scheduled operation, it is imperative that there be minimal impact to the FAA ATCT training cycle at each TSS site. If the Contractor determines that on-site spare parts are required to achieve the individual TSS system reliability, maintainability, and availability (RM&A) requirements specified in this contract, and the FAA approves this determination, then the Contractor must implement a spares management process in accordance with their Recommended Site Spares List CDRL A014. The Contractor must ensure that each deployed TSS meets or exceeds the TSS Operational Availability (Ao) and TSS Mean-Time-To-Repair (MTTR) requirements specified in Section 3.3 of this SOW and include these TSS requirements when determining if onsite spare parts are required at each TSS site. The spares inventory may include consumable items if required to be located on-site at each FAA TSS facility (as well as at the TSSC) and must be replenished as items are used to ensure each TSS meets or exceeds the specified TSS Ao and MTTR requirements.

3.2.6. Inventory Control of Spares and Repair Parts

The Contractor must establish an inventory control system and manage a TSS Spare Parts Process from the TSSC in accordance with the Recommended Site Spares List CDRL A014 if on-site spare parts are determined by the Contractor (and approved by the FAA) to be required in order to achieve the TSS Ao and MTTR requirements. All TSS hardware and software components must be managed in accordance with contractor procedures established in the Government approved TSS ILSP CDRL A012. Licensed shipping companies (e.g., Federal Express, United Parcel Post, etc.) must be used to ship all Government owned TSS hardware and software components.

C-8

The Contractor must create and maintain a TSS spare parts inventory/repository based upon the Government approved ILSP CDRL A012, detailing spares availability at the TSSC and at each TSS location. A list of hardware spares must include the manufacturer’s name, model, and serial numbers, be maintained, and be available to the TSS PMO upon request.

Effort associated with the development and delivery of CDRL A014 is covered under the Program Management CLIN X001. Efforts associated with performing requirements of the Integrated Logistics Support are covered in CLIN X002.

3.2.7. Monitor of Vendors for Spares Availability

The Contractor must subscribe to vendor product service bulletins where available to obtain notices on product availability. Additionally, the Contractor must contact the TSS equipment vendors on a semi-annual basis to monitor spares availability and advise the TSS PMO in accordance with the Obsolete Parts List CDRL A013 (for any part that may become obsolete within three (3) years) should there be an obsolescence issue that needs attention, resolution, and potential need for future procurement.

3.2.8. Risk Mitigation for Parts End-of-Service-Life (EOSL)/Obsolescence The Contractor must assess and ensure, on a semi-annual (i.e., every six (6) months) basis, that spares exist to fully support each deployed TSS to include TSS Systems, TSS Mobile Units, TSS Scenario Development Laptops (SDL), TSS Suitcases, and possible additional TSS installations at any new sites in accordance with the Obsolete Parts List CDRL A013.

As part of the semi-annual assessment, a technology evaluation must also be conducted. When the technology evaluation determines that a TSS part or component will become obsolete within the next twelve (12) months the Contractor must notify the TSS PMO within thirty (30) calendar days of the completion of each semi-annual Obsolete Parts List (CDRL A013) and provide an itemized list, cost, justification, and recommendation to perform an EOSL/obsolescence upgrade/purchase for each affected TSS. The recommendation for the upgrade must also include a plan for the purchase, installation, integration, and test to validate TSS operation for each affected TSS.

The purchase of EOSL/obsolescence upgrades must be authorized by the Government Contracting Officer. Upon integration and test at the Contractor TSSC testbed and approval by the FAA, these upgrades must be delivered to the designated TSS site(s) and installed by either the on-site Contractor FSR/FST or a contractor designated representative in coordination with the FAA site POC in accordance with the Test Plan – SIV CDRL A026, Test Procedures – SIV CDRL A027, and Test Report – SIV CDRL A028. Effort associated with the development of CDRLs A026, A027, and A028 is covered under the Program Management CLIN X001. Efforts associated with performing the requirements of CDRLs A026, A027 and A028 are covered under the Equipment/Hardware – TSS Components CLINs X010 and X011, CLS – TSSC, Help Desk and WIDE CLIN X002, and TSS On-site Support – Field Technicians CLIN X003.

Once installed and deemed operational, the Contractor must prepare new or update existing, if available, site as-built drawings in accordance with Site As-Built Drawings, CDRL A020, and any other impacted training/maintenance/equipment documentation in accordance with SOW Sections 3.2.9-3.2.11. Effort associated with the development and delivery of CDRL A020 is covered under

C-9 the Program Management CLIN X001. Efforts associated with performing the requirements of CDRL A020 are included in the CLS – TSSC, Help Desk & WIDE CLIN X002.

The Contractor disposition of any spares (located on-site or at the Contractor TSSC) that are deemed obsolete, or no longer necessary, must be itemized and a request for disposition must be submitted to the FAA for approval.

3.2.9. Risk Management Plan (RMP)

The Contractor must develop, establish, manage, and maintain a Risk Management Plan (RMP) for the TSS Program in accordance with the PMP CDRL A001. The RMP must clearly define how identified risks will be managed on a continuous basis and mitigated. The Contractor must ensure that a management process is in place to capture and provide ongoing program status with respect to risk and risk mitigation. The Contractor must also address all risk management issues at each PMR.

3.2.10. Configuration Management (CM) Program

The Contractor must develop, establish, manage, and maintain a CM Program to perform the CM efforts required to configuration manage all parts, media, documentation, data, software, and other materials received or produced under this contract. The CM Program must be delineated in a Configuration Management Plan (CMP) prepared in accordance with the CM Plan CDRL A007.

Effort associated with the development and delivery of CDRL A007 is covered under the Program Management CLIN X001. Efforts associated with performing the requirements of CDRL A007 are covered under the CLS – TSSC, Help Desk & WIDE CLIN X002. The Contractor’s CM program must provide configuration identification, configuration control, verification, and configuration status accounting/audits of all existing, new, and/or modified simulator hardware, firmware, software, and documentation received or used for the duration of the contract. This includes, but is not limited to, the following for each TSS:

• User manuals

• System level operation and maintenance manuals

• Development, update, and maintenance of TSS facility configuration baselines and as-built drawings

• System Configuration Manual identifying all TSS site documents that will be configuration managed and providing guidance, inventory, and structure for how they will be configuration managed

• System Administration Guide containing the Standard of Acceptable Performance Checklist to verify the TSS system or parts/components have been received, installed and work as part of the installation and checkout of a TSS system installation or upgrade.

• System component level manuals

• Documentation for all COTS software/hardware equipment installed or received

• Training documentation

3.2.11. Hardware Configuration Management

The Contractor must support the following hardware configuration management activities:

C-10

• Establish and maintain hardware configuration management and a hardware configuration baseline with respect to the TSS hardware at the TSSC and each TSS system, TSS Mobile Unit, TSS Suitcase, and TSS SDL

• Identify, monitor, manage, and document changes to the configuration baseline following Site Installation Verification (SIV) testing, when applicable, for all sites

• Document and report all hardware changes to the TSS Program office and the site FAA POC once completed

• Record the hardware changes into the TSS system hardware configuration management database described below

• Maintain a system hardware configuration management database for each installed system at an individual TSS site that must contain at a minimum:

Item Description, model number, and version Serial Numbers Assigned System Position (e.g., Local Control, Ground Control, Flight Data, Pseudo Pilot, etc.)

Dates – In-Service/Out-of-Service/Repair/Warranty Part History Vendor and Vendor Contact Information System maintenance history to include a description/resolution of all failures/repairs done

Hardware and software configurations of each TSS must be maintained in the TSS WIDE as described in SOW Section 3.5.2.10. Any changes to the previously approved site hardware and software baseline items must be documented, controlled, and approved as followed:

• Contract changes must be submitted in accordance with Contract Change Proposal CDRL A011. Effort associated with the development of CDRL A011 is covered under the Program Management CLIN X001. Efforts associated with performing the requirements of CDRL A011 are covered under the Engineering Services CLIN X017 and the ODC CLIN X018.

• Specification and engineering changes must be submitted in accordance with Specification Change Notice CDRL A009 and Engineering Change Proposal CDRL A010. Effort associated with the development of CDRLs A009 and A010 is covered under the Program Management CLIN X001. Efforts associated with performing the requirements of CDRL A009 and CDRL A010 are covered under the Engineering Services CLIN X017 and ODC CLIN X018.

• Requests for deviation must be submitted in accordance with Request for Deviation/Waiver CDRL A008. Effort associated with the development of CDRL A008 is covered under the Program Management CLIN X001. Efforts associated with performing the requirements of CDRL A008 are covered under the Engineering Services CLIN X017 and the ODC CLIN X018.

C-11

3.2.12. Software Configuration Management

The Contractor must establish, maintain, and support the following software configuration management activities:

• Establish and maintain software CM and a software configuration baseline for each TSS System, TSS Mobile Unit, TSS Suitcase, and TSS SDL;

• Software CM must be inclusive of, but not limited to, the following software work products:

COTS product specifications

COTS product software

Collaboration with third party proprietary software vendors (includes operating system and application software)

Computer Based Instruction (CBI) related training material

• Managing, reporting, and recording changes to the approved TSS software configuration baseline and the above software work products on an individual TSS site basis

The software configurations of each TSS must be maintained in the TSS WIDE as described in SOW Section 3.5.2.10. The Contractor must support access to all installed TSS software configurations for use in testing site modifications.

The Contractor must provide the FAA all the necessary installation files, licenses, and installation documentation for each version of software installed. This includes the COTS operating system software, application software, and any third-party software installed. This information must be available, managed, and accessible via the TSS WIDE.

3.2.13. Quality Assurance Plan (QAP)

For the performance of the TSS work, the Contractor’s quality system must reflect the principles of ISO 9001 Quality Management System and the Government approved PMP CDRL A001. Efforts associated with the development of the TSS QAP in CDRL A001 are covered under the Program Management CLIN X001. Efforts associated with performing the requirements of the TSS QAP are covered under the CLS – TSSC, Help Desk & WIDE CLIN X002.

3.3. Integrated Logistics Support (ILS)/RM&A (CLIN X002)

The Contractor must establish and maintain an ILS capability to review problem ticket reports, monitor status and resolution of trouble tickets, and ensure that each TSS [i.e., TSS System, TSS Mobile Unit, TSS Suitcase, and TSS SDL] meets or exceeds the TSS Ao and MTTR requirements specified in this contract. The TSS Ao requirement is defined for TSS Systems and TSS Mobile Units as each TSS System and TSS Mobile Unit must be operationally available to conduct ATCT certification, qualification, and recurrent training a minimum of 95% of the time, 24 hours a day, and 365 days a year. The Ao requirement for TSS Suitcases and TSS SDLs is defined as each TSS Suitcase and TSS SDL must be operationally available at least 95% of time, 24 hours a day, and 365 days a year. The Contractor must provide all maintenance actions (i.e., repair and or replacement of

C-12 all failed or inoperable TSS components) necessary to ensure each TSS meets or exceeds the system operational and maintenance requirements specified in this SOW and in the TSSS (Attachment J-1).

The locations of the TSS Large and Small systems are specified in Attachment J-4 of this contract.

The configurations of the TSS Large and Small systems are specified in Attachment J-5 of this contract. Additionally, the ILS capability must include the establishment/management of a TSSC for depot repair/testbed support of deployed TSS systems, TSS Mobile units, TSS Suitcases, and TSS SDLs. The TSSC must also meet or exceed the TSS system Ao and MTTR requirements specified in this SOW. The detailed description of this ILS capability must be delineated in the TSS ILSP in accordance with CDRL A012.

Key service level metrics include: system availability, system reliability, and response time compliance. The Contractor must evaluate, apply, and document key service level metrics on a per system per site basis, and reported in accordance with the Monthly Program Status Report CDRL A002. Additionally, the data collected must be summarized and presented by the Contractor at the PMRs, and based upon each site’s TSS configuration, the Contractor must establish a system operational availability baseline and spares management concept whereby the MTTR of all failures for each TSS must not exceed seventy-two (72) hours. The Contractor must collect the data for each TSS and ensure the repair time cited includes, but is not limited to, the following work tasks:

• Diagnostic time

• Removal of the failed part

• Installation of a new part

• Checkout of the TSS equipment, and

• All adjustments required to return the TSS to normal operation

The ILS capability must include, but not be limited to:

• Operation and maintenance planning

• Spares management and storage

• Training and training materials

• Supply support

• Monitoring of CLS and TSSC processes

• General TSS installation requirements at FAA facilities

• Packaging, handling, storage, and transportation (PHS&T)

3.4. Training and Training Material Management (CLIN X016)

The Contractor must prepare and maintain the following operational and training documents for the TSS during the contract period of performance in accordance with Training Materials CDRL A029 as it relates to TSS operations/maintenance; scenario generation, database and model utilization, and any TSS site specific aspects. Effort associated with the development of CDRL A029 is covered under the Engineering Services CLIN X017. Efforts associated with performing the requirements

C-13 of CDRL A029 are covered under the Training Courses CLIN X016. Specific documents that must be developed and maintained are:

• TSS System Operator Manual

• TSS System Administrator and Maintenance Manual

• Manual (Hard Copy) and Content Delivered using CBI for Designing and Creating TSS Training Scenarios

The Contractor must attend TSS operational and maintenance training courses to be provided by the Government as necessary subsequent to contract award. The Contractor must report on the status of all training received, developed, or provided at scheduled PMRs. The Contractor must execute training on a per day basis and the training may be ordered on a Task Order in varying quantities throughout the duration of the contract.

3.5. Contractor Logistics and Technical Support (CLIN X002)

3.5.1. Support Operation Requirements

The Contractor must provide all necessary management, resources, and effort to maintain contractor logistics and technical support in accordance with this SOW. The Contractor must report services provided in accordance with the Engineering and Technical Services Report CDRL A034. Effort associated with the development of CDRL A034 is covered under the Program Management CLIN X001. Efforts associated with performing the requirements of CDRL A034 are covered under the CLS – TSSC, Help Desk & WIDE CLIN X002. The TSS system software to be provided as GFE for this contract may have the capability to remotely access the TSS system software via the internet for TSS software and hardware maintenance, implementation of updates, data retrieval, scenario programming and other TSS operational and support tasks. The Contractor must install and checkout new system software and software releases provided as GFE for this contract in all TSS systems.

3.5.2. Support Operation Tasks

3.5.2.1. Help Desk Support

The Contractor must operate a 24x7 TSS Help Desk service to provide technical and administrative support for the TSS program. The Contractor must operate the TSS Help Desk service in a fully staffed mode on a twelve (12) hour per day schedule, Monday through Friday, 7:00 AM to 7:00 PM Eastern Time basis. For days and times outside the above specified timeframes, the Contractor must operate the TSS Help Desk in a non-staffed on-call/standby basis using an automated telephone transfer process or by email using the Contractor established and maintained TSS WIDE. The TSS Help Desk must be staffed with individuals that have expert knowledge of the TSS hardware and software functionality. The Contractor must provide and ensure staffing levels and expertise are consistent with meeting the technical and administrative support required under this contract.

The Contractor must respond on the next regularly scheduled work day to phone calls made or emails received after the TSS Help Desk is closed. Help Desk calls must be tracked through a trouble ticketing system established by the Contractor. The Government must have access to the ticketing system to obtain status of reported problems; who submitted the problem; who resolved the problem;

how the problem was resolved; when the problem was resolved; and the time it took to resolve each

C-14 problem. The Contractor must analyze and resolve identified deficiencies; manage the support process throughout the contract period of performance; and submit Engineering and Technical Services Reports in accordance with the Engineering and Technical Services Report CDRL A034.

Effort associated with the development of CDRL A034 is covered under the Program Management CLIN X001. Efforts associated with performing the requirements of the TSS Help Desk service are covered under the CLS – TSSC, Help Desk & WIDE CLIN X002.

3.5.2.2. Hardware Support/Development Updates

Included under the CLS, the Contractor must provide hardware support. In addition to the management/use of spares to ensure system operational availability, the Contractor may need to replace or upgrade TSS hardware components to improve/maintain overall TSS system performance, reliability, maintainability, and availability. The Government will identify the TSS hardware components to be replaced or upgraded by the Contractor on a site by site basis. The Government will direct the Contractor to purchase these TSS hardware components. The Government may provide some or all of the TSS hardware components required on this contract as GFE.

When a TSS is upgraded with a new version of TSS system software, the Contractor must perform Site Installation Verification (SIV) testing to ensure system operation/performance in accordance with the Test Plan – SIV CDRL A026 and Test Procedures – SIV CDRL A027 and the test results are reported in accordance with the Test Report – SIV CDRL A028. Upon successful completion of the SIV for each TSS, the Contractor must perform a configuration audit that establishes a new hardware configuration baseline for that TSS site; update all related documentation; upload/maintain this information on the TSS WIDE; and identify/request disposition instructions for all hardware replaced to include any associated documentation.

3.5.2.3. Software Support/Development Updates

Included under the CLS, the Contractor must provide software support. As software deficiencies or functional/performance related issues are identified, a determination will be made by the Government as to where the correction responsibility lies. Since the TSS consists of both proprietary and non-proprietary software, the Contractor must collaboratively engage with the owner of the proprietary software and the TSS PMO to determine how the corrections must be prioritized and a plan of action developed.

The Contractor must date and classify all software deficiencies as to their level of impact and importance to the operational performance of the TSS. All software deficiencies must be logged in;

remain open until resolved; archived upon remediation; and available and maintained in the TSS

WIDE.

The Contractor must make all TSS system software releases approved by the Government TSS PMO available on the TSS WIDE for distribution and installation in each TSS. For TSS sites that have a Contractor provided FSR or FST on-site (see SOW Section 3.7), the Contractor FSR or FST must install and test the software releases. For TSS sites that do not have an onsite Contractor FSR or FST, the Government will determine if the Government or a Contractor SME will install and test the software releases. If a problem occurs when the Government installs and tests the software releases, the Government will contact the Contractor for assistance.

C-15

The Contractor will install, test, and verify the functionality/performance of the software release as soon as possible in accordance with the Test Plan – SIV CDRL A026, Test Procedures – SIV CDRL A027, and Test Report – SIV CDRL A028 taking into consideration the operational needs of the facility.

3.5.2.4. Support Databases and Moving Models Library

The Contractor must support the development and management of new airport VDBs; expanded moving models library; and the approved modification/update of existing airport VDBs, aircraft, vehicle, models, and liveries specified in Section 3.5.2.7 of this SOW.

A VDB design describes the graphical portrayal of a specific airport such as runways, gates, elevation, weather conditions, and other airport characteristics. Most of these types of information will be unique for each airport. However, some of the graphical representations will be identical or similar at many or all airports such as the graphical representation of airport surveillance landing radars.

The Contractor must date and classify database and model deficiencies as to their level of impact and importance to the operational performance of the TSS. The Contractor must maintain the status of the deficiencies on the TSS WIDE and all database and model deficiencies currently logged into this system will remain valid indefinitely until remedied. Once remedied, the database and model deficiencies must be closed out and archived on the TSS WIDE. Plans and the estimated cost/time for correction of these database and model deficiencies must be jointly prioritized by the Contractor and the Government based upon their level of impact and importance to the operational performance of the TSS.

The Contractor must test and verify database and model updates using the TSS Depot/Test Bed System provided by the Government as GFE to the Contractor for their TSSC Depot/Testbed function. The TSS Depot/Test Bed system is specified in Attachment J-5 of this contract. Upon acceptance/approval, database and model updates must be integrated into site specific databases for each TSS; documented into each TSS site’s configuration baseline; and maintained in the TSS

WIDE.

The Contractor must develop, document, manage, and provide all software and licensing rights for aircraft, liveries, and visual database modeling in accordance with the CM Plan CDRL A007 and ILS CDRL A012. In accordance with this SOW and Section I AMS clause 3.5-13 Rights in Data – General (Oct 2014), the FAA has the authority to modify any aircraft, vehicle, or airport model provided by the Contractor to the FAA. Also in accordance with this SOW and clause 3.5-13, the FAA has the authority to use and distribute site specific databases, models, and liveries without restriction. The Contractor must maintain all aircraft, liveries, and vehicle models that have been developed or received from approved third party vendors. At a minimum, the Contractor must maintain all models and liveries listed in Attachments J-11 and J-12 and all airport visual databases listed in Attachment J-4.

The Contractor must develop a site installation plan and conduct a site survey for the creation of new airport visual databases in support of new TSS sites when tasked in accordance with the Site Survey Plan CDRL A015. (NOTE: Database updates may follow a different process depending on the level or percentage of upgrade.) The survey must include determining the airport and surrounding area’s physical characteristics to be modeled in the visual database. The survey must also include

C-16 collecting aircraft and vehicular movement information necessary to create a realistic operational scenario. The Contractor must coordinate with the FAA to obtain permissions to take photographs and videos from selected vantage points to aid in the TSS database creation.

The Contractor must create and send the airport survey questionnaire and Facility Design Criteria Report, both specified by the Facility Design Criteria CDRL A017, to the FAA ATC facility POC for completion prior to the site survey. During the site survey, the Contractor must verify data gathered by the site POC.

The Contractor must prepare a Site Notification Letter in accordance with Site Notification Letter CDRL A016 and submit it to the site POC no later than two (2) weeks prior to start of the site survey visit. The Government’s TSS PMO will coordinate all site visits with the appropriate FAA organizations and facilities.

The Contractor must prepare a Site Survey In-Brief in accordance with the site installation plan as required by the Site Survey In-Brief CDRL A018 and hold the briefing with site personnel at the beginning of the site survey. The in-brief must provide an overview of the TSS Program, a site activation schedule, and a review of site and Contractor responsibilities for implementation.

The site survey must last no more than three (3) calendar days and must result in a Contractor-prepared out-brief which presents the results of the survey for review and approval by TSS PMO representatives. A Site Survey Report must be prepared and submitted to the TSS PMO as specified by the Site Survey Report CDRL A019.

The Contractor must provide configuration management for all government furnished data collected from the site survey in accordance with the CM Plan CDRL A007.

The Contractor must prepare a Visual Database Design Document (VDDD) in accordance with VDDD CDRL A032 from data gathered during the site survey. The initial VDDDs and visual databases must be submitted for review/approval by the Government’s TSS PMO. Any non-conformance items must be rectified and resubmitted within fifteen (15) business days.

An approved visual database must be baselined in accordance with the CM Plan CDRL A007 and be subject to site testing in accordance with the Test Plan – SIV CDRL A026, Test Procedures – SIV CDRL A027, and Test Report – SIV CDRL A028.

The Contractor must install and operate Government furnished models, liveries, visual databases, and scenarios. The Contractor must maintain and modify the Government furnished models, liveries, visual databases, and scenarios when changes are requested by the TSS PMO.

The Contractor must develop new VDBs for FAA airports as required by the TSS PMO under CLIN X015. The Contractor must also modify existing TSS VDBs for FAA airports as required by the TSS PMO under CLIN X015. Efforts associated with the development and modification of TSS VDBs are covered under the TSS VDB CLINs X015.

The list of TSS VDBs is provided in Attachment J-4 of the contract. The list of TSS Models (Aircraft & Vehicle List) is provided in Attachment J-11 of the contract. The list of TSS Models (Ground Objects) is provided in Attachment J-12 of the contract.

C-17

3.5.2.5. Support Scenario Development

The Contractor must support the creation of operational scenarios based on the scenario scripts provided by the FAA.

The Contractor must test the newly created scenario using the TSSC and, upon approval from the TSS PMO, must distribute the new scenario database. The Contractor must also ensure that the newly created scenario is incorporated into the TSS site’s configuration baseline and updated and maintained in the TSS WIDE.

3.5.2.6. Updates to TSS Documentation (CLIN X016)

The Contractor must maintain documentation updates that include, but are not limited to, modifications identified/received of the following:

• TSS System Operator Manual

• TSS System Administrator and Maintenance Manual

• Manual and CBI for Designing and Creating TSS Training Scenarios

As documentation updates are made available, the Contractor must maintain and manage them in accordance with the CM Plan CDRL A007, SOW Section 3.2.9-3.2.11. All documentation updates must be uploaded and made available on the TSS WIDE.

3.5.2.7. Maintaining and Distributing Site-Specific Data Files The Contractor must maintain a record of all site-specific data files for backup and debugging purposes in accordance with the CM Plan CDRL A007, SOW Sections 3.2.9 - 3.2.11, and Attachment J-1, TSS Specification. The site-specific data files the Contractor must maintain include:

• Visual Data Base(s) – 3D graphical image of the airport and its surroundings

• Visual models – graphical image of aircraft, vehicles, physical obstructions, etc.

• Liveries – paint scheme of a model, e.g., airline…