RFP_Attachment_-_PWS_20181105.pdf

PERFORMANCE WORK STATEMENT

STCS Athena Upgrade at Joint Interagency Task Force South 05 November 2018

PART 1

GENERAL INFORMATION

1. GENERAL: This is a non-personal services contract to upgrade the Sensor Track and Correlation System (STCS) located at the Joint Interagency Task Force South (JIATFS) facility in Key West, Florida. For purposes of this document, “STCS” refers to the system currently installed at JIATFS and “STCS 3.0” refers to the upgraded system. The Government shall not exercise any supervision or control over the contract service providers performing the services herein. Such contract service providers shall be accountable solely to the Contractor who, in turn is responsible to the Government.

1.1 Description of Services/Introduction: The contractor shall perform services to upgrade the STCS system which contains the following two components: a Track Data Converter consisting of conversion software and the accompanying Sensor Control Panel and Athena 3.x consists of Multi-Source Correlator Tracker (MSCT), MSCT Display, Athena Extensions, Database Dashboard, and Commercial-Off-The-Shelf (COTS) PostgreSQL.

1.2 Background: The Government has a STCS that resides on NIPRNET and SIPRNET, onsite at Key West, Florida (STCS-J – primary system) and at the Alternate Command Post in Tampa, FL (STCS-C – contingency system). STCS is a radar/sensor fusion system that integrates a variety of radar and sensor feeds to include: radar (search and beacon), Relocatable Over-the-Horizon Radar (ROTHR), Tactical Data Links (Link-11 and SAT- TADIL-J), Federal Aviation Association (FAA) data, Eastern Clipper data, Ocean Surveillance Initiative (OSI) data, Automatic Identification System (AIS), and a high-fidelity bi-directional interface to Global Command and Control System (GCCS).

The STCS contract was awarded to Raytheon Integrated Defense Services in 2010 building on commercial products called Athena and MSCT. Athena provides a service oriented architecture, interfaces and configuration tools, while MSCT provides core fusion and correlation services. To date, STCS has been fully integrated on JIATFS’s SIPRNET enclave with a signed Authority to Operate (ATO) from SOUTHCOM.

A key component of STCS is the ability to ingest UNCLASSIFIED data. A Sensor Aggregation System (SAS) was developed, configured, and fully integrated on JIATF South’s NIPRNET enclave. The SAS consolidates all unclassified data feeds into a single data format and provides the data via one-way feed (low to high) to a Radiant Mercury Cross Domain Solution (CDS).

1.3 Objectives: The intention of this contract is to upgrade the STCS Athena. Upgrading to STCS 3.0 provides many benefits, including:

Maintains JIATF-S’ investment in the system Provides a simpler design Uses the most recent Athena Product Line Provides standard upgrades and improvements made to Raytheon Athena product without customization Aligns with other Raytheon programs Uses existing hardware Uses improved Athena Display and Athena Server Uses one display - Link operations are supported in all displays; therefore, there is no need for separate

STCS Display and Link Ops Display Replaces Portal with a Database Dashboard and Sensor Control Panel

1.4 Scope: The Contractor shall provide non-personal services to upgrade the STCS system. The STCS system contains the following components: (a) Track Data Converter consisting of conversion software and the accompanying Sensor Control Panel and, (b) Athena 3.x consists of MSCT, MSCT Display, Athena Extensions, Database Dashboard, and COTS PostgreSQL.

1.5 Period of Performance: The period of performance shall be for 18 months commencing on 01 January 2019 through 31 May 2019.

1.6 General Information:

1.6.1 Quality Control Plan (QCP): The Contractor shall develop, implement, and maintain a QCP and program to ensure all work described in this contract is performed at or above the standard defined in the Performance Requirements Summary (PRS). The QCP is developed by the contractor for its internal use to ensure that it performs and delivers high-quality service. The contractor’s QCP is the means by which the contractor ensures all work complies with the requirements of the contract. The QCP identifies and corrects potential and actual problem areas throughout the entire scope of the contract.

1.6.1.1 The contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services. The QCP shall be submitted within thirty (30) days of contract award. After acceptance of the QCP, the contractor shall receive the contracting officer’s (KO) acceptance in writing of proposed changes to the QC procedures. The contractor shall submit QCP changes within five (5) days to the KO and Contracting Officer’s Representative (COR) for review and approval prior to implementation.

1.6.1.2 The Quality Control Plan shall address as a minimum:

1.6.1.2.1 Inspection Program. Included shall be a quality control inspection program covering all general and specific tasks included in the contract scope of work. It shall specify tasks or areas to be inspected on a scheduled or unscheduled basis, the manner in which inspections are to be conducted, the titles of the individuals who will perform the inspections, and the percentage of the work that will be inspected on a recurring basis. In developing this inspection program, the Contractor shall identify the key activities and associated characteristics in each process that have a significant influence on specific services and provide for methods for evaluation of the selected characteristics.

1.6.1.2.2 Deficiency Identification. The QCP shall include a method of identifying deficiencies in the quality of services performed before the level of performance becomes unacceptable as defined in the PRS. This shall contain processes for corrective action without dependence upon Government direction.

1.6.1.2.3 Deficiency Correction. The program shall contain process control and process performance measurement procedures that shall include how the Contractor shall implement preventive corrective actions. The Contractor shall demonstrate that it has designed quality into the delivery of services thereby mitigating the risk(s) associated with delivery of deficient or nonconforming services.

1.6.1.2.4 Documentation and Enforcement. The QCP shall include a method of documenting and enforcing quality control operations of both prime contractor and subcontractor work; including inspection and testing.

1.6.1.2.5 Trend Analysis. The QCP shall include a method of performing trend analysis and assessments through the use of metrics.

1.6.1.2.6 Surveillance Methods. The QCP shall contain specific surveillance techniques for all contract services.

The surveillance methods shall be comprehensive and adaptable to the reporting system of the plan.

1.6.2 Quality Assurance (QA): The government shall evaluate the contractor’s performance under this contract in accordance with (IAW) the Quality Assurance Surveillance Plan. This plan is primarily focused on what the Government must do to ensure that the contractor has performed IAW the performance standards and contract quality requirements are met. “Contract quality requirements” means the technical requirements in the contract relating to the quality of the product or service and those contract clauses prescribing inspection, and other quality controls incumbent on the contractor, to ensure the product or service conforms to the contractual requirements. It defines how the performance standards will be applied, the frequency of surveillance, the minimum acceptable defect rate(s), and deductions, if applicable.

1.6.3 Recognized Holidays:

New Year’s Day Labor Day Martin Luther King Jr.’s Birthday Columbus Day President’s Day Veteran’s Day Memorial Day Thanksgiving Day Independence Day Christmas Day

1.6.4 Hours of Operation: The contractor is responsible for conducting business between the hours of 8:00 am to 4:00 pm Monday through Friday, except Federal holidays or when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings. For other than firm fixed price contracts, the contractor will not be reimbursed when the government facility is closed for the above reasons. The Contractor must, at all times, maintain an adequate workforce for the uninterrupted performance of all tasks defined within this PWS when the Government facility is not closed for the above reasons.

1.6.5 Place of Performance: The work to be performed under this contract will be performed at the Government’s facility, Joint Interagency Task Force South, Key West, Florida 33040 and at the contractor’s facilities.

1.6.6 Type of Contract: Firm-Fixed Price.

1.6.7 Access and General Protection Policy and Procedures:

1.6.7.1 Physical Security: The contractor shall be responsible for safeguarding all government equipment, information, and property provided for contractor use. At the close of each work period, government facilities, equipment, and materials shall be secured IAW Army Regulation (AR) 190-13, “The Army Physical Security Program.”

1.6.7.1.2 The Government has the right to remove any Contractor employee from the installation and to deny access to the installation by any Contractor employee who poses a potential threat to the health, safety, security, general wellbeing, or operational mission of the installation or its population.

1.6.7.1.3 The Contractor shall provide a roster of personnel expected to perform services under this contract to the COR, no later than ten (10) workdays prior to commencing work. This personnel roster shall include the employee's full name and position to be held. The Contractor shall update this roster within ten (10) calendar days if personnel changes occur during the duration of the contract.

1.6.7.1.4 Installation Access and Control. Truman Annex is a closed Installation with access restrictions. All vehicles and personnel are subject to search and seizure of contraband and/or unauthorized Government property.

Contractor vehicles (Contractor-owned and personal), Contractor personnel, and their personal property shall be subject to inspections and searches upon entering or leaving the Installation as authorized in Army Regulation (AR) 190-5, Motor Vehicle Traffic Supervision. The Contractor may be subject to installation closure exercises that may have an impact on performance.

1.6.7.1.5 Contractor's personnel shall not be permitted access to any JIATFS buildings during days or hours when no work is scheduled, except when prior arrangements have been made between the COR and Project Manager.

1.6.7.2 Personnel Security Clearance Requirements: Contractor personnel performing work under this contract must have an active personnel security clearance at the SECRET level in the Joint Personnel Adjudication System (JPAS) at time of the proposal submission, and must maintain the level of security required for the life of the contract. The security requirements are IAW with the attached DD Form 254, “Department of Defense (DOD) Security Classification Specification”. The Contractor shall ensure that contractor employees and sub-contractor employees performing services under this contract comply with FAR 52.204-2, Security Requirements when the employee has access to information classified “Confidential,” “Secret,” or “Top Secret.” The Contract will ensure the employee complies with the Security Agreement (DD Form 441), including the National Industrial Security Program

Operating Manual (DOD 5220.22-M), and any revisions to DOD 5220.22-M, notice of which has been furnished to the Contractor.

1.6.7.2.1 FCL procedures and security guidelines for adjudicative requirements are outlined in DOD 5220.22-M, DOD 5200.2-R, and AR 380-67. FCL’s and Interim FCL’s shall be awarded by the Defense Security Service (DSS) or DISCO. JIATFS will not provide sponsorship for FCLs. Final granted FCL’s are required at proposal submission.

1.6.7.2.2 Upon award, all names of contract employees shall be submitted to JIATFS J2 for vetting through JPAS to ensure investigative and clearance requirements have been satisfied. If a contractor employee does not have the appropriate investigative or security clearance requirement the contractor employee shall be denied the ability to work in support of this contract.

1.6.7.2.3 Any visit(s) by contract personnel not permanently assigned to this contract (company presidents, company security managers, contract employees not permanently assigned at JIATFS, etc.) shall require an electronic visit request in the Joint Personnel Adjudication Systems (JPAS).

1.6.7.2.4 Upon completion of work under this contract, the contractor shall surrender all Government supplies, materials and equipment to the Government. Contract members assigned to JIATFS shall return any security badges to JIATFS J2 upon out-processing. This shall be accomplished on the last day of the contract or upon any termination/reassignment of contract employees.

1.6.7.2.5 The contractor shall ensure the roles/privileges assigned to contract employees on the Government computing platforms are limited to the roles/privileges essential to that individual’s performance of his/her assignments. These roles/privileges can be limited or revoked by the Government for any reason.

1.6.7.2.6 Upon contract awarded, all names of contract employees shall be submitted to JIATFS, J2 for vetting through JPAS to ensure investigative and clearance requirements have been satisfied. This shall be completed prior to the Contracting Officer (KO) / Trusted Agent (TA) accesses the DoD Trusted Associate Sponsorship System (TASS) and submits the contract employees for their Common Access Card (CAC). If a contract member does not have the appropriate investigative or security clearance requirement the contract employee shall be denied the ability to work in support of this PWS and not be loaded into TASS. Contract personnel will be loaded in TASS with the expiration on their CAC for the initial contract year. Upon approval for the option year(s) a new CAC will be issued with new dates for the subsequent option period. The CAC expiration process will be repeated for the duration of the contract.

1.6.7.2.6.1 Visit Authorization Letter (VAL) or Visit Authorization Request (VAR) shall be required for contract personnel who are assigned to JIATF South for short durations. The VAL/VAR request shall be received 48 hours prior to start of the contractor employee. VAL/VAR requests can be submitted to JIATFS J2 via email or fax. An example copy of the VAL or VAR can be obtained from JIATFS J2.

1.6.7.2.6.2 Upon completion of this contract, the employee shall surrender all Government supplies, materials and equipment to the Government. All contractor employee CAC’s shall be turned into the KO during out-processing for all contract personnel. Additionally, contractor employees shall also return any security badges to JIATFS J2 upon out-processing. This shall be accomplished on the last day of the contract or upon any termination/reassignment of contract employees. Due to the sensitive nature of operations at JIATF South, the failure of contractor employees to return CAC’s and Security badges back to JIATF South may result in administrative penalties/fees levied against the contractor as well as an incident reporting against the contract employee’s clearance.

1.6.7.2.7 Security Regulation Compliance: The contractor shall be required to comply with all security regulations and directives as identified herein and other security requirements in this contract specific to site locations of work.

The contract members are required to attend required security training outlined in the PWS upon start of the contract.

1.6.8 Post Award Conference/Contract Periodic Progress Meetings: The contractor shall attend the post award conference convened by the contracting activity or contract administration office IAW Federal Acquisition

Regulation (FAR) Subpart 42.5. The KO, COR, and J6 Program Manager with other Government personnel, as appropriate, may meet periodically with the contractor to review the contractor's performance. At these meetings the KO will apprise the contractor of how the government views the contractor's performance and the contractor will apprise the Government of problems, if any, being experienced. Appropriate action shall be taken to resolve outstanding issues. These meetings shall be at no additional cost to the government.

1.6.9 Contracting Officer Representative (COR): The COR will be identified by separate letter. The COR monitors all technical aspects of the contract and assists in contract administration. The COR is authorized to perform the following functions: ensure the Contractor performs the technical requirements of the contract; perform inspections necessary in connection with contract performance; maintain written and oral communications with the Contractor concerning technical aspects of the contract; issue written interpretations of technical requirements, including Government drawings, designs, specifications; monitor Contractor's performance and notifies both the KO and Contractor of any deficiencies; coordinate availability of government furnished property; and provide site entry of Contractor personnel. A letter of designation issued to the COR, a copy of which is sent to the Contractor, states the responsibilities and limitations of the COR, especially with regard to changes in cost or price, estimates, or changes in delivery dates. The COR is not authorized to change any of the terms and conditions of the resulting order.

1.6.10 Key Personnel: The following personnel are considered key personnel by the government: Project Manager and Alternate Project Manager. The contractor shall provide a Project Manager who shall be responsible for the performance of the work. The name of this person and an alternate who shall act for the contractor when the manager is absent shall be designated in writing to the contracting officer. The contract manager or alternate shall have full authority to act for the contractor on all contract matters relating to daily operation of this contract.

1.6.11 Identification of Contractor Employees: Contractor employees shall identify themselves as contractor personnel and shall avoid representing themselves as Government employees. This identification includes meeting attendance, answering Government telephones, email communications, and working in other situations where contractor status is not obvious. Contractor personnel identification shall be easily identifiable through the display of badges, name tags, lanyards, etc.

1.6.11.1 Appearance of Personnel. The Contractor shall ensure that Contractor personnel present a neat and professional appearance at all times. At all times during contract performance Contractor personnel shall wear as outer wear a shirt or vest with the company logo and name. This includes shirts with sleeves (short or long sleeves).

Contractor personnel shall wear long pants, safety shoes, and hard hats in designated areas as required by Occupational Safety and Health Administration (OSHA) requirements and Army regulations. Offensive pictures, sayings, tank tops, tee shirts, and spandex or similar fabric worn as outerwear are strictly prohibited.

1.6.12 Data Rights: The government has unlimited rights to all documents/material produced under this contract. All documents and materials, to include the source codes of any software, produced under this contract shall be Government owned and are the property of the Government with all rights and privileges of ownership/copyright belonging exclusively to the Government. These documents and materials may not be used or sold by the contractor without written permission from the Contracting Officer. All materials supplied to the Government shall be the sole property of the Government and may not be used for any other purpose. This right does not abrogate any other Government rights.

1.6.13 Non-Disclosure Requirements: Performance under this contract may require the Contractor to access data and information proprietary to a Government agency, another Government Contractor, or of such nature that its dissemination or use other than as specified in this work statement would be adverse to the interests of the Government or others. Neither the Contractor, nor Contractor personnel, shall divulge, nor release data or information developed, or obtained under performance of this work statement, except to authorize Government personnel or upon written approval of the KO. The Contractor shall not use, disclose, or reproduce proprietary data, which bears a restrictive legend, other than as specified in this PWS. All documentation showing individual names or other personal information shall apply, and shall be controlled and protected under the provisions of the Privacy Act of 1974, Public Law 93-579, and 5 United States Code (U.S.C.) Section 552a.

1.6.13.1 Non-Disclosure Statements: The contractor shall provide signed non-disclosure agreements to the Government prior to commencement of work under the contract. Disclosure of information by Contractor personnel may result in Contractor personnel removal from performance of duties under this contract.

1.6.13.2 Contractor is prohibited from the use of cellular telephones and other electronic devices while inside of the JIATFS premises.

1.6.13.3 Advertisement and Social Media: The contractor shall NOT post information to public website or social media locations, personal or professional, that in any way disclose names, locations, hotel data, participants, discussions, pictures, etc. before, during or after the contract period of performance without the express consent of the Government. The use of propaganda violates DOD Commercial Use of Imagery Guidelines stated at (http://www.defenseimagery.mil/products/DODimagery/commercialuse.html). The Contractor shall not cite any information (e.g., contract information, pictures, locations, etc.) obtained through this contract on any marketing tools to include its company website.

1.6.13.4 The provisions of the Privacy Act of 1974 protect information included in this contract. The contractor performing to this PWS will take the proper precautions to protect information subject to the Privacy Act from unauthorized disclosure.

1.6.14 Organizational Conflict of Interest (OCI): The government shall require Contractor personnel to sign a non-disclosure statement to protect non-public information of other Contractors and/or Government. Contractor and subcontractor personnel performing work under this contract may receive, have access to or participate in the development of proprietary or source selection information (e.g., cost or pricing information, budget information or analyses, specifications or work statements, etc.) or perform evaluation services which may create a current or subsequent Organizational Conflict of Interests (OCI) as defined in FAR Subpart 9.5. The Contractor shall notify the KO immediately whenever it becomes aware that such access or participation may result in any actual or potential OCI and shall promptly submit a plan to the KO to avoid or mitigate any such OCI. The Contractor’s mitigation plan will be determined to be acceptable solely at the discretion of the KO and in the event the KO unilaterally determines that any such OCI cannot be satisfactorily avoided or mitigated, the KO may affect other remedies as he or she deems necessary, including prohibiting the Contractor from participation in subsequent contracted requirements which may be affected by the OCI.

1.6.15 General Training Requirements:

1.6.15.1 Information Assurance (IA)/Information Technology (IT) Training: All Contractor employees and subcontractor employees requiring access to Government information systems must complete the DoD IA awareness training before issuance of network access and annually thereafter. All employees working IA/IT functions must comply with DoD and Army training requirements in Per DoD 8570.01, DOD 8570.01-M, and AR 25-2, within 30 days of employment. Training is available at https://ia.signal.army.mil/DoDIAA/default.asp.

PART 2

DEFINITIONS & ACRONYMS

2. DEFINITIONS AND ACRONYMS:

2.1 Definitions:

2.1.1 Area of Responsibility. The Joint Interagency Task Force South area of responsibility (AOR) includes the building complex within the Truman Annex, Key West, Florida.

2.1.2 Contractor. The total contractor organization or a separate entity of it; such as an affiliate, division, or plant that performs its own purchasing.

2.1.3 Contracting Officer (KO). A person with the authority to enter into, administer, and/or terminate contracts and make related determinations and findings.

2.1.4 Contracting Officer’s Representative (COR). An individual designated and authorized in writing by the contracting officer to perform specific technical or administrative functions.

2.1.5 Defective Service. A service output that does not meet the standard of performance associated with the Performance Work Statement.

2.1.6 Deliverable. Anything that can be physically delivered, but may include non-manufactured things such as meeting minutes or reports.

2.1.7 Key Personnel. Contractor personnel that are evaluated in a source selection process and that may be required to be used in the performance of a contract by the Key Personnel listed in the PWS. When key personnel are used as an evaluation factor in best value procurement, an offer can be rejected if it does not have a firm commitment from the persons that are listed in the proposal.

2.1.8 Performance Work Statement (PWS). A statement of work for performance-based acquisitions that describes the required results in clear, specific, and objective terms with measurable outcomes.

2.1.9 Physical Security. Protection of the perimeter area, government property, and assets that prevent the loss or damage of Government property.

2.1.10 Quality Assurance. The various functions, including inspection, performed by the government to determine whether a contractor has fulfilled the contract obligations pertaining to quality and quantity.

2.1.11 Quality Assurance Surveillance Plan (QASP). A plan describing how the agency will survey, observe, test, sample, evaluate and document the contractor’s performance in meeting critical performance standards identified in the contract.

2.1.12 Quality Control (QC). Tasks performed by the contractor to improve the quality of the organization’s output.

2.1.13 Shall. Imperative.

2.1.14 Subcontractor. Any supplier, distributor, vendor, or firm that furnishes supplies or services to or for a prime contractor or another subcontractor.

2.1.15 Work Day. The number of hours per day the Contractor provides services in accordance with the contract.

2.1.16 Work Week. Monday through Friday, unless specified otherwise.

2.1.17 Athena 3.x. MSCT, MSCT Display, Athena Extensions, Database Dashboard, and Sculpt.

2.1.18 Track Data Converter. Consisting of Sensor Control Panel and track data conversion software.

2.1.19 Sensor Control Panel. Consisting of software to monitor and administer the interfaces connected to the TDC.

2.1.20 Sensor Track Correlation System. Includes Athena, the Track Data Converter and the Sensor Control Panel

2.2 Acronyms:

AD Active Directory ADSI Air Defense Systems Integrator AIS Automatic Identification System AO Authorizing Official AQL Acceptable Quality Level ATO Authority To Operate AOR Area of Responsibility AR Army Regulation ATCTS Army Training Certification Tracking System AT Anti-Terrorism CAC Common Access Card CDS Cross Domain Solution CFR Code of Federal Regulations CFM Customer Furnished Material CFR Customer Furnished Requirements CIO Chief Information Officer CLIN Contract Line Item Number CMR Contract Manpower Reporting CONUS Continental United States (excludes Alaska and Hawaii) COR Contracting Officer Representative COT Cursor On Target COTS Commercial-Off-The-Shelf DD Form 254 Department of Defense Contract Security Requirement List DERG Data Extraction Reduction Guide DIA Defense Intelligence Agency DISA Defense Information Systems Agency DHCP Dynamic Host Control Protocol DNS Domain Name Service DOD Department of Defense DODD Department of Defense Directive DODI Department of Defense Instruction

ESB Enterprise Service Bus ETF Extended Track Format FAA Federal Aviation Association FAR Federal Acquisition Regulation FY Fiscal Year GBR Ground Based Radars GCCS Global Command and Control System GFE Government Furnished Equipment GFP Government Furnished Property GFS Government Furnished Services GTM Ground Targeting Mode HEAT Helpdesk Expert Automation Tool IA Information Assurance IAT Information Assurance Technician IAW In Accordance With IBS Integrated Broadcast Service IT Information Technology ITAR International Traffic in Arms Regulations JPAS Joint Personnel Adjudication System JREAP Joint Range Extension Applications Protocol JTR Joint Travel Regulation KML Keyhole Markup Language KMZ Keyhole Markup Language, Zipped KO Contracting Officer MSCT Multi-Source Correlator Tracker NCIC-III National Crime Information Center Interstate Identification Index NIPRNET Non-classified Internet Protocol Router Network NIST National Institute of Standards and Technology OCI Organizational Conflict of Interest OCONUS Outside Continental United States (includes Alaska and Hawaii) ODC Other Direct Costs OPSEC Operation Security OSI Ocean Surveillance Initiative OTH-G Over-The-Horizon-Gold PDF Portable Document Format PKI Public Key Infrastructure PM Program Manager PRS Performance Requirements Summary PWS Performance Work Statement QA Quality Assurance QASP Quality Assurance Surveillance Plan QCP Quality Control Program RA Requiring Activity RMF Risk Management Framework ROTHR Relocatable Over-the-Horizon Radar SAN Storage Area Networks SOP Standard Operating Procedures SAS Sensor Aggregation System SECREL Secret Releasable SIPRNET Secret Internet Protocol Router Network SOP Standard Operating Procedure STCS Sensor Track Correlation System STCS-C Alternate Command Post STCS System (STCS-Contingency) STCS-J Primary STCS System (STCS-JIATFS) TADIL-J Tactical Digital Information Link - also known as Link 16 TCNOS Time Compliance Network Orders

TE Technical Exhibit TFMDG Traffic Flow Management Data to Government TPOC Technical Point of Contact TS SCI Top Secret/Sensitive Compartmented Information USSOUTHCOM United States Southern Command VM Virtual Machine VMD Virtual Machine Disk XML Extensible Markup Language

PART 3

GOVERNMENT FURNISHED EQUIPMENT (GFE), GOVERNMENT FURNISHED PROPERTY (GFP), AND

GOVERNMENT FURNISHED SERVICES (GFS)

3. GOVERNMENT FURNISHED ITEMS AND SERVICES:

3.1. Services: The Government will provide telephone services onsite through standard Government assets.

Contractor employees shall be permitted the use of full-service Government telephones/computers and secure and non-secure, Local Area Networks (LAN), ILAN, and Wide Area Networks (WAN), supporting JIATFS only in direct support of the contract and for official Government use only.

3.2 Facilities: The Government will provide the necessary workspace for the onsite Contractor staff to provide the support outlined in the PWS. This will include but not be limited to a desk, chair, computer, and application software; access to copiers, facsimile machines, conference table and chairs, bookcases, shelves, and other items necessary to maintain an office environment.

3.3 Utilities: The Government will provide utilities within the onsite facility that are required in performance of tasks outlined in this PWS. The Contractor shall instruct employees in utilities conservation practices. The contractor shall be responsible for operating under conditions that preclude the waste of utilities, which include turning off the faucets, turning off lights, and powering off equipment at the end of the work day.

3.4 Equipment: The Government will provide the following materials and access to the following equipment:

VMDK images of the system to be deployed on will be provided to the Contractor on disk as a place for them to host the SW for testing purpose.

Two representative servers to host the virtual machines provided in item 3.1.

Two display workstations equivalent to hardware hosted in JIATFS.

GCCS Server hardware and GCCS software consistent with what is deployed at JIATFS.

Sample recorded data for the below sensor interfaces:

Rough Widow in XTrack XML FAA in TFMData XML Unitrac in Unitrac XML ROTHR in OTH-G Brown Ale in CoT XML Pale Ale in XTrack XML (might be classified) IBS in CMF XML (I think this is classified) GBRs in CD-2, ARSR-4, FPS-117, TPS-70

GCCS in ETF

PART 4

CONTRACTOR FURNISHED ITEMS AND SERVICES

4. CONTRACTOR FURNISHED ITEMS AND RESPONSIBILITIES:

4.1 General: The Contractor shall furnish all supplies, equipment, facilities and services required to perform work under this contract that are not listed under Part 3 of this PWS.

4.2 Facility Security Clearance: The contractor shall possess and maintain a SECRET facility security clearance from the Defense Security Service. The Contractor’s employees, performing work in support of this contract, shall have been granted a Secret personnel security clearance from the Defense Industrial Security Clearance Office. The DD Form 254 is provided as Attachment 3.

4.3 Upon award, all names of contract employees shall be submitted to JIATFS J2 for vetting through JPAS to ensure investigative and clearance requirements have been satisfied. If a contractor employee does not have the appropriate investigative or security clearance requirement the contractor employee shall be denied the ability to work in support of this contract.

PART 5

SPECIFIC TASKS

5. Specific Tasks: The Contractor shall provide non-personal services to upgrade the Sensor Track and Correlation System (STCS). The STCS system contains the following components: (a) Track Data Converter consisting of conversion software and the accompanying Sensor Control Panel and, (b) Athena 3.x consists of MSCT, MSCT Display, Athena Extensions, Database Dashboard, and COTS PostgreSQL.

5.1 Program Management Administration. The Contractor’s Project Manager (PM) shall be responsible for oversight, management, and control of all activities STCS Software System Upgrade. Contractor Program Management functions include the following:

5.1.1 Integrated Master Schedule (IMS). The contractor shall provide the IMS with their proposal. The Contractor PM shall maintain an IMS by logically networking detailed program activities. The schedule shall contain the planned events and milestones, accomplishments, exit criteria, and activities from contract award to contract completion. Updates to the IMS shall be coordinated and approved by the Government PM and COR.

5.1.2 Program Meetings. The Contractor PM shall participate in status meetings, scheduled upon request of the Government PM, COR, and/or KO, to formally or informally discuss or review the Contractor’s efforts, accomplishments and progress toward completion. During the meetings, the Contractor PM shall present necessary data to enable a joint review of its various assigned tasks, schedules, and deliverables.

5.1.2.1 Technical Meetings. The Contractor shall support technical meetings via telecon, which will be held monthly. The Contractor shall present and participate in technical discussions and shall inform, in a timely fashion, the KO, Government PM and/or COR of any problems with contract execution and any proposed solutions regardless of whether a specific meeting time is established.

5.1.3 Monthly Progress Report (MPR). The Contractor shall provide by the 15th a month report summarizing overall contract performance and shall include, at a minimum, the activities for the previous month, upcoming activities, schedule updates and changed with rationale, issues, concerns, high interest items, lessons learned, and recommendations.

5.2 System Upgrade Requirements.

5.2.1 NIPRNet/SAS to Track Data Converter. Contractor shall replace the Sensor Aggregation System (SAS) on NIPRNet with a Track Data Converter, which is responsible for translating data to XTrack XML and sending it to Radiant Mercury CDS for processing.

Track Data Converter shall convert Cursor on Target (COT) XML to XTrack XML.

Track Data Converter shall convert Rough Widow XML to XTrack XML.

Track Data Converter shall convert FAA TFMData XML to XTrack XML.

Track Data Converter shall convert Unitrac XML to XTrack XML.

Track Data Converter shall convert ROTHR OTH-G to XTrack XML.

Track Data Converter shall convert AIS/NMEA 0183 to XTrack XML.

Track Data Converter shall be able to generate "test" track data (i.e. simulated) and output via XTrack

XML.

Track Data Converter shall process "recent historical data" batch track reports.

Track Data Converter shall forward the XTrack XML to the Radiant Mercury CDS for processing.

5.2.1.1 Sensor Control Panel. Contractor shall install a Sensor Control Panel on NIPRNet, to monitor and administer the interfaces supported in the Track Data Converter. The Sensor Control Panel shall support two different display configurations - a read-only display for view only Operators and a read/write display for Administrators.

The read/write configuration of the Sensor Control Panel shall allow an administrator to add a new instance of a supported interface (input and output) to the system.

The read/write configuration of the Sensor Control Panel shall allow an administrator to remove an existing interface from the system

The read/write configuration of the Sensor Control Panel shall allow an administrator to configure an existing interface to the system

The read/write configuration of the Sensor Control Panel shall allow an administrator to activate (start) an interface

The read/write configuration of the Sensor Control Panel shall allow an administrator to deactivate (stop) an interface

Both configurations of the Sensor Control Panel shall display the health and status of input interfaces, including but not limited to, connection status, last data receive time, and data rate.

Both configurations of the Sensor Control Panel shall display the health and status of output interfaces, including but not limited to, connection status, last data transmit time, and data rate.

5.2.2 SIPRNet/STCS to Track Data Converter. Contractor shall replace ESB on SIPRNet with a Track Data Converter responsible for translating data to XTrack XML and sending it to the MSCT.

Track Data Converter shall convert Pale Ale XML/OTH-G to XTrack XML.

Track Data Converter shall convert AIS CMF XML to XTrack XML.

Track Data Converter shall convert Cursor-on-Target XML to XTrack XML.

Track Data Converter shall convert Pale Ale data to XTrack XML.

Track Data Converter shall convert ROTHR OTH-G to XTrack XML.

Track Data Converter shall convert AIS/NMEA 0183 to XTrack XML.

Track Data Converter shall be able to generate "test" track data (i.e. simulated) and output via XTrack

XML.

Track Data Converter shall process "recent historical data" batch track reports.

Track Data Converter shall forward the XTrack XML to MSCT for processing.

5.2.2.1 Sensor Control Panel. Contractor shall install a Sensor Control Panel on SIPRNet, to monitor and administer the interfaces supported in the Track Data Converter. The Sensor Control Panel shall support two different display configurations - a read-only display for view only Operators and a read/write display for Administrators.

The read/write configuration of the Sensor Control Panel shall allow an administrator to add a new instance of a supported interface (input and output) to the system.

The read/write configuration of the Sensor Control Panel shall allow an administrator to remove an existing interface from the system.

The read/write configuration of the Sensor Control Panel shall allow an administrator to configure an existing interface to the system.

The read/write configuration of the Sensor Control Panel shall allow an administrator to activate (start) an interface.

The read/write configuration of the Sensor Control Panel shall allow an administrator to deactivate (stop) an interface.

Both configurations of the Sensor Control Panel shall display the health and status of input interfaces, including but not limited to, connection status, last data receive time, and data rate.

Both configurations of the Sensor Control Panel shall display the health and status of output interfaces, including but not limited to, connection status, last data transmit time, and data rate.

5.2.3 Athena/STCS

STCS shall accept and process XTrack XML from the Track Data Converter.

STCS shall accept and process XTrack XML from the Radiant Mercury CDS.

STCS shall accept and process GCCS ETF messages.

Athena shall accept and process Sensis radar data from the Ground Based Radars (GBRs).

Athena shall accept and process a minimum of 12 simultaneous JSTARS JREAP C MIL-STD-3011B Link

16 message connections with room to grow to 24 simultaneous connections.

Athena shall accept and process ASTERIX CAT -21 messages.

STCS shall be capable of outputting data in GCCS ETF format.

STCS shall be capable of outputting data in XTrack XML format.

STCS shall be capable of outputting data in KML/KMZ format.

Athena shall be capable of outputting data in Link 16 JREAP-C format.

Athena shall be capable of outputting data in OTH-G format.

STCS shall be capable of outputting CoT data.

STCS shall be capable of supporting configurable, priority-based, mapping to/from GCCS/ETF track attributes.

STCS shall be capable of supporting configurable, priority-based, track naming.

STCS shall be capable of modifying track attributes (e.g. Vessel Name, Track Category, and Track

Callsign) via operator or doctrine action.

STCS shall be capable of modifying GCCS/ETF track attributes (e.g. ETF Track Type, ETF Track

Category) via operator or doctrine action.

Shared Doctrines shall be supported between Athena Displays.

Athena shall be capable of supporting a 14,000 peak track load.

Athena shall support two different display configurations - a Standard display configuration for

Administrators and a Limited display configuration for other Operators.

The Standard display configuration of Athena shall allow an administrator to edit doctrines.

The Standard display configuration of Athena shall allow an administrator full access to the Link 16 management and controls.

Athena shall include a mechanism to monitor and administer its connected interfaces.

Athena shall support filtering and throttling on output sessions.

Athena shall display Connection Status (Active/Inactive) and the number of messages received for each input interface to the MSCT Server.

Athena shall display Connection Status (Active/Inactive) and the number of messages transmitted for each output interface from the MSCT Server.

Athena shall allow an administrator to add a new instance of a supported interface (input and output) to the system.

Athena shall allow an administrator to remove an existing interface from the system.

Athena shall allow an administrator to configure an existing interface to the system.

Athena shall allow an administrator to activate (start) an interface.

Athena shall allow an administrator to deactivate (stop) an interface.

5.2.4 Database. Contractor shall include a PostgreSQL Database and accompanying Database Dashboard. The Administrator shall have full permissions to use the database dashboard. The Database Dashboard shall allow the user to create a database playback session.

5.2.5 Information Assurance. Contractor shall provide input to the Customer's Port, Protocols and Services Management (PPSM) and SSP documents. All components of STCS shall support installation in a RedHat 6 environment. The PPSM provides all ports, protocols, and services that are accessible to our STCS software. This document is required for software installed on both NIPRNet and SIPRNet and shall be submitted one (1) month prior to Site Acceptance Test (SAT).

5.2.6 STCS-C. The STCS-C system shall contain the same software build and functionality as the STCS-J system.

5.3 Testing Requirements. The Contractor shall provide an Acceptance Test Plan (ATP) to the Government PM and COR one (1) month prior to SAT. The ATP must include acceptance test procedures, inspection, analysis, and demonstration activities performed on site at JIATFS to meet all system requirements as defined in the contractor’s technical proposal.

5.4 Training. The Contractor shall provide one (1) week of user and administrator training for up to 10 students following SAT. Training material must be provided to the Government PM and COR one (1) month prior to training event. Training documents must contain presentation material used for operator training.

5.5 STCS Operator Manual. The Contractor shall provide the STCS Operator Manual one (1) month prior to SAT.

This manual provides an overview of the Sensor Tracking Correlation System (STCS) software applications that provide operator interfaces in support of track surveillance, multi-source correlation, information sharing, and other JIATFS operations. Basic system operator procedures, advanced system operator procedures, operations examples, and troubleshooting guidance are provided for STCS operators at the JIATFS Joint Operation Command Center

(JOCC).

5.6 STCS System Administrator Manual. The Contractor shall provide the System Administrator Manual to the Government PM and COR one (1) month prior to SAT. This manual provides information and procedures for administering, maintaining, and troubleshooting STCS. STCS is a complex system and has many components. Each of these components requires routine maintenance and can be configured to better meet the needs of its users.

Procedures are provided for maintenance, configuration changes, troubleshooting, and recovery.

5.7 Athena Software, Licenses, and User Documentation. The Contractor shall provide the following software, licenses, and user documentation to the Government PM and COR at SAT.

PRODUCT

NUMBER

DESCRIPTION QTY

0403003 Minor Release Version upgrade for Multi Source Correlator Tracker Perpetual Right to Use License Failover Configuration includes upgrades up to 3 MSCT Display Right to Use

0403001 Minor Release Version upgrade for Multi Source Correlator Tracker Perpetual Right to Use License includes upgrades up to 3 MSCT Display Right to Use

0103008-02 Perpetual Right to Use License. MSCT Display

Custom MSCT 5.8-Athena 3.0 extension 2 Custom TDF-Athena 3.0 extension 10

5.8 Contractor Manpower Reporting (CMR):

5.8.1 The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract the Office of the Assistant Secretary of the Army (Manpower & Reserve Affairs) via a secure data collection site. The contractor is required to completely fill in all required data fields using the following web address: http://www.ecmra.mil/, and then click on the “Department of the Army CMRA” or the icon of the DoD organization that is receiving or benefitting from the contract services.

5.8.2 Reporting inputs will be for the labor executed during the period of performance during each Government fiscal year (FY), which runs 1 October through 30 September. While inputs may be reported any time during the FY, all data shall be reported no later than 31 October of each calendar year, beginning with 2013. Contractors may direct questions to the help desk by clicking on “Send an email” which is located under the Help Resources ribbon on the right side of the login page of the applicable Service/Component’s CMR website.

5.8.3 The required information includes:

Contracting Office, Contracting Officer, Contracting Officer’s Representative;

Contract number including, if applicable, task or delivery order number;

Beginning and ending dates covered by reporting period;

Contractor name, address, phone number, e-mail address, identity of contractor employee entering data;

Organizational title associated with Unit Identification Code (UIC) for the Army:

Requiring Activity = W453AA;

Command = HQDA;

Predominant Federal Service Code (FSC) reflecting services provided by contractor (and separate predominant FSC for each sub-contractor if different);

Estimated Direct labor hours (including sub-contractors);

Estimated Direct labor dollars paid this reporting;

Total payments (including sub-contractors);

Locations where contractor and sub-contractors perform the work (specified by zip code in the United States and nearest city, country, when in an overseas location, using standardized nomenclature provided on website);

Estimated data collection cost;

Number of contractor and sub-contractor employees deployed in theater this reporting period (by country).

5.8.4 Contract number and contractor identity will be treated as proprietary information when they are associated with the direct labor hours and direct labor dollars. At no time will any data be released to the public with the contractor name and contract number associated with the data.

5.8.5 There is no minimum dollar amount for the data collected. The Accounting for Contract Services requirement applies to all purchases and contracts regardless of the dollar value.

5.8.6 As part of its submission, the Contractor shall also provide the estimated total cost incurred (if any) to comply with this reporting requirement. Reporting period will be the period of performance not to exceed 12 months ending 30 September of each government fiscal year and must be report by 31 October of each calendar year.

PART 6

APPLICABLE PUBLICATIONS

6. APPLICABLE PUBLICATIONS (CURRENT EDITIONS)

6.1. The Contractor must abide by all applicable regulations, publications, manuals, and local policies and procedures.

6.1.1 DOD Commercial Use of Imagery Guidelines

6.1.2 AR 190-13, The Army Physical Security Program

6.1.3 Army Directive 2014-05, Policy and Implementation Procedures for CAC Credentialing Access for Uncleared Contractors