CRCTYQ23ACLS2PWS6Dec.docx

PERFORMANCE WORK STATEMENT

FOR

CONTRACT LOGISTICS SUPPORT

FOR

CONTROL AND REPORTING CENTER (CRC)

CONTRACT LOGISTIC SUPPORT

Prepared By:

Hill Air Force Base Aerospace Dominance Enabler Division (HBZ) Control and Reporting Center (HBZIC –CRC Operations Section)

Preparer:

AFLCMC/HBZIC – CRC Operations Section

As of 14 November 2019

Contents

Part 1 General Information

1. GENERAL INFORMATION

1.1 General:

This is a service contract to provide Contract Logistics Support and unscheduled maintenance/repairs on various configurations, technologies and manufacturers of Tactical Air Operations Module AN/TYQ-23A(V)1, ancillary equipment for the United States Air Force (USAF) and Government Agencies Worldwide. Maintenance of these systems is critical to ensure that the systems will function as designed for operations and mission success. Repairs, including emergency repairs, are required to keep these systems in fully functional condition. All Performance Work Statement (PWS) and contractual discrepancies shall be identified, clarified and negotiated with the Procurement Contracting Officer (PCO). The PCO is the only individual who can legally bind the Government.

1.2 Description of Services:

The contractor shall provide all personnel, labor, equipment, supplies, transportation, tools, materials, technical data/manuals, expertise, supervision, and services necessary to perform maintenance as defined in this PWS except for those items provided by base support. The contractor shall employ a worldwide service organization, trained and experienced in providing Contract Logistics Support such as but not limited to diagnosis and repair on all covered equipment. The contractor is ultimately responsible for problem resolution during maintenance activities, i.e., the contractor shall be responsible for aspects of maintenance activities to include associated hardware and software to a fully operational status, troubleshooting, and resolution diagnosis. The contractor shall ensure internal coordination and correction of problem resolution with the Government Point-Of-Contact (POC) and CRC Program Office (PMO), prior to work performance.

1.3 Background:

The CRC is a deployable battle management command and control (BMC2) system employed at the tactical level to support air operations execution across the entire range of operations, from Homeland Security to major combat operations.

· CRC mission is to provide Battlespace Awareness (BA) and tactical BMC2 in an assigned area. CRC network of systems are a tactical C2 element that operates independently or in combination with other tactical joint/coalition C2 elements.

· CRC manages the theater’s integrated air defense system, conducts air surveillance, participates in-theater data link operations, and controls air operations in accordance with the Air Tasking Order (ATO) and Airspace Control Order (ACO).

· CRC is a deployable battle management command and control (BMC2) system employed at the tactical level to support air operations execution across the entire range of operations, from Homeland Security to major combat operations.

1.3.1 CRC Functions:

Battle Management Command and Control (BMC2).

The CRC provides the air/ground operations in a decentralized execution mode, by managing, disseminating, and assigning mission tasks defined in appropriate tasking orders.

Weapons Control:

Support and/or coordination of Offensive Counter Air/Defensive Counter Air (OCA/DCA), Air Interdiction (AI), Aerial Reconnaissance (AR), Close Air Support (CAS), Combat Search and Rescue (CSAR), High-Value Airborne Asset (HVAA) protection, Electronic Warfare (EW), Intelligence, Surveillance, and Reconnaissance (ISR), special operations, and the direction of air defense artillery systems.

Surveillance:

Detection, identification, classification, and tracking of airborne/ground objects (sensors detect and provide cueing to engage hostile manned and unmanned aircraft/vehicles as well as cruise missiles).

Combat Identification:

Capability to disseminate timely, accurate, and relevant identification information to weapon system operators to allow engagement of hostile targets and avoid fratricide.

Airspace Management:

Implementation of the Air Tasking Order and Airspace Control Order.

Tactical Data Link (TDL) Management:

Consolidate sensors into the Common Tactical Picture (CTP) for distribution over Tactical Data Link (TDL).

1.4 Scope:

The contractor shall furnish all labor, tools, equipment, technical data/manuals, materials, supplies, parts, Original Equipment Manufacturer (OEM) service bulletins, and services necessary to perform Contractor Logistics Support on TYQ-23A(V)1 In Accordance With (IAW) OEM standards (commercial standards if third party is performing service/repair), including software/firmware upgrades. This support includes but is not limited to: Engineering Support, Project Services, R&M Tracking Analyses, Procurement of Spares (Spares Parts Usage Report), Depot Supply Support, Depot Maintenance Support for Hardware/Software (HW/SW), Technical Orders/Manuals, TCTO’s, Packaging, Handling, Storage and Transportation (PHS&T), Item Unique Identification, Warranty Management, Government Furnished Property and any component that compromises the “TYQ-23A System”, for the USAF and Government Agencies worldwide. This support shall also include Emergency and Preventative Maintenance for any future technologies designed to be implemented in the TYQ-23A. This sustainment effort may substantially increase in cost due to future capability advancements on the TYQ-23A and related systems through a bilateral modification.

1.4.1 Purpose:

The CLS contractor will supply engineering, logistical support, and technical support for the system. The level three maintenance may be performed in the field with the Site Support Team (SST) or at the contractor facility providing depot level repairs to the system. This will include testing, parts repair, parts replacement and shelter maintenance, help maintain Authority to Operate and licenses to meet the system Availability Rate (AR) standard minimum of 92%.

1.5 Basic Requirements:

· The contractor shall maintain an adequate workforce for the uninterrupted performance of all tasks defined within this PWS for the duration of the period of performance.

· The contractor shall achieve a complete, effective, structured preventative maintenance program for the TYQ23A(V)1 to include ancillary equipment.

· The contractor shall comply with all country, federal, installation, state, local, industry, and national codes.

· Certain locations require U.S. Citizen’s to service and maintain TYQ23A(V)1.

· All Intelligence Surveillance Reconnaissance (ISR) missions shall be serviced by U.S. Citizens and require constant U.S. Control for parts utilized.

1.6 Small Business Subcontracting Plan:

If the awardee is a large business, the contractor shall submit a small business subcontracting plan.

1.7 Labor Reporting:

In compliance with Section 8108 of Public Law 112-10 of the Department of Defense and Full Year Continuing Appropriations act of 2011, the contractor shall report contractor labor hours (including subcontractor labor hours) as required for performance of services provided under this contract for the CLS contract via a secure data collection site. The contractor is required to fill in all required data fields at http://www.ecmra.mil.

1.7.1 Reporting Inputs:

Reporting inputs will be for the labor executed during the period of performance for 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. Contractors may direct questions to the Contract Manpower Reporting Application (CMRA) help desk.

1.7.2 Uses and Safeguarding of Information:

Information from the secure government web sites is considered to be proprietary in nature when the contract number and contractor identity 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.

1.7.3 User Manuals:

Data for Air Force service requirements must be input at the DOD CMRA link, http://www.ecmra.mil, along with user manuals for government personnel and contractors.

1.8 Additional General Information:

1.8.1 Period of Performance:

The period of performance of this contract will be a five year ordering period of 23 Mar 2020 – 22 Mar 2025.

1.8.2 Quality Control (QC):

The contractor shall develop a Quality Control Program (QCP) to ensure services are performed IAW this PWS. The contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services. The contractor’s QCP must comply with the PWS requirements. The QCP shall be delivered Not Later Than (NLT) 30 calendar days after contract award (CDRL A005). Any changes to the QCP shall be submitted to the Procurement Contracting Officer (PCO) within five business days when changes are made after the initial proposal. After acceptance of the QCP, the contractor shall receive the PCO’s acceptance in writing of any proposed change to his quality control system. Once the QCP is accepted, the QCP shall be implemented NLT 30 calendar days after acceptance.

1.8.3 Quality Assurance:

The Government shall evaluate the contractor’s performance IAW the Quality Assurance Surveillance Plan (QASP). The plan defines how the performance standards shall be applied, the frequency of surveillance, and the minimum acceptable defect rate(s). The contractor shall develop and maintain a Quality Plan, IAW Contractor Quality Control, (CDRL A006), to ensure services are performed IAW commonly accepted OEM practices, Commercial Standards if Third Party is selected, and PWS requirements. The contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of incomplete maintenance services and provide within 30 calendar days after the contract is awarded. As a minimum, the contractor shall develop a QC plan that addresses the areas identified in the PWS. The CRC Program Manager shall be the Government liaison in the event of customer complaints.

1.8.4 Recognized Holiday:

The contractor may be required to perform service on holidays including but not limited to:

Holidays specific to host country

1.8.5 Hours of Operation:

The contractor shall be responsible for conducting business except when the Government facility is closed due to local or national emergencies, acts of Nature, acts of War, administrative closings, or similar Government directed facility closings. The contractor shall not be reimbursed when the Government facility is closed for the above reasons and shall not file a request for equitable adjustment.

1.8.5.1 Program Manager and Contract Manager and Key Personnel and Administrative Duty Hours:

The contractor shall designate a prime and alternate Program Manager. The Program Manager shall be responsible for the daily operations of the contract. The Program Manager or alternate shall be available during administrative duty hours identified as between 7:00 a.m. to 3:30 p.m. Mountain Time (MT), Monday thru Friday except Federal holidays or when the Government facility is closed for administrative reasons. The CLS contractor shall provide a Contract Manager. The Contract Manager shall have full authority to act for the contractor on all contract matters. The contractor shall provide the names of key personnel identified above and involved with the operations of this contract. Notifications shall be provided in writing to the Government NLT 15 calendar days after contract award and within 10 calendar days after any changes or replacements. (CDRL A017).

1.8.6 Location of Work:

Contractor travel and work may be performed at, but not limited to, all Air Control Squadrons, Major Commands, CRC Program Office, Depots, and Contractor’s facility. No travel and work will be performed in a Combat Zone. If the contractor performs duties outside the United States, the contractor shall procure Defense Base Act (DBA) Insurance in accordance with the FAR. Contractor shall observe the safety rules IAW Appendix C (as required). Appendix A illustrates, but is not inclusive of all primary travel locations.

1.8.7 Contractor Employee:

When hiring personnel, the Contractor shall keep in mind that stability and continuity of the workforce are essential. The contractor shall not employ persons for work on this contract if such employee is identified to the contractor by the PCO as a potential threat to the health, safety, security, and/or general well-being to the operational mission of the installation and its population. Contractor personnel shall meet site access requirements which may require, in some instances, US Citizenship and elevated clearance. Contractor personnel may be required to undergo a background investigation to perform their duties. Contractor personnel shall comply with all regulations for overseas travel.

1.8.8 Place of Performance:

The work pursuant of any contract associated with this PWS shall be performed at various industrialized, non-industrialized, and remote locations worldwide.

1.9 Health and Safety; Security and Property Damage:

1.9.1 Worker’s Health and Safety:

The contractor shall comply with all applicable Country, Federal, State, Territorial, and local requirements regarding workers’ health and safety. The contractor is solely responsible for determining the legal requirements and compliance that apply to their activities. These include but are not limited to all Occupational Safety and Health Administration (OSHA) safety rules and regulations, arc flash training, personal protection training and equipment to protect themselves and others from unsafe work conditions. The contractor shall report any accidents or OSHA violations immediately to the appropriate authorities and within one (1) business day to the PCO and comply with (CDRL A007).

1.9.2 Security Requirements:

The Contractor shall meet personnel, information, system, property, and facility security requirements. The contractor personnel shall meet site access requirements which may require, in some instances, US Citizenship, i.e. JPAS Request. This may include but not limited to vehicle and equipment access requests, Visit Access Request (VAR) submittals, and electronic media device submittals to include mobile telephone, camera devices, etc. The contractor shall also comply with all Foreign Disclosure Office (FDO) requirements. Contractors’ identification shall be in compliance with the REAL ID act. Personnel in possession of state issued identification, which is not in compliance with this act, may not be granted access to facilities. Contractor shall contact the base they desire entry for specific requirements, should contractor personnel not possess REAL ID act compliant identification. Please visit https://www.dhs.gov/real-id-public-faqs for additional information.

1.9.2.1 Operations Security (OPSEC):

The purpose of OPSEC is to reduce the vulnerability of USAF missions to adversary collection and exploitation of critical information. The contractor shall comply with DoDD 5205.02E, DoDM 5205.02-M, and other applicable Government security regulations to protect classified information and/or Controlled Unclassified Information (CUI), Government projects and/or programs.

1.9.2.2 Communication Security (COMSEC):

The contractor shall use only secure communications methods and/or equipment to transmit or otherwise transfer classified information and/or CUI IAW DoD 5220.22-M. Applicable Government property, including equipment, shall be safeguarded, maintained, and operated IAW DoD 5220.22-M.

1.9.2.3 Security Clearance:

The contractor shall possess a facility clearance IAW the DD Form 254. The contractor shall ensure personnel have SECRET security clearances for proper accomplishments of contract requirements. Contractor personnel shall obtain clearances IAW the DD Form 254, Department of Defense Contract Security Classification Specification. The contractor shall inform the CRC Program Management Office (CRC PMO) of all clearance requests. The contractor shall immediately deny access to classified information and CUI to contractor personnel whose clearances have been suspended or revoked or no longer have a need-to-know.

1.9.2.4 Security Incident or Violation:

The contractor shall notify the COR HBZIC of any potential or actual security incident or violation including potential or actual unauthorized disclosure or compromise of classified information and/or CUI no later than the next business day after the contractor discovers the incident or violation.

1.9.2.5 Access to Government System(s):

The contractor will obtain forms from the COR to gain access to system(s) necessary to perform tasks under the contract. Contractor personnel who require access to unclassified or classified Government systems shall have the appropriate background check or security investigation conducted. Access can be revoked or restricted at any time.

1.9.2.6 Security of Contractor Systems:

The contractor shall provide security of automated information systems at the contractor’s facility to preclude potential security incidents or violations including potential unauthorized disclosure or compromise of classified and/or CUI.

1.9.2.7 Common Access Card (CAC):

In accordance with AFFARS 5352.242-9001, Common Access Cards (CAC) for Contractor Personnel, all contractor or subcontractor personnel who require access to DoD computer networks and systems, DoD installation entry control or physical access to facilities and buildings to perform tasks under the contract shall obtain a CAC. The contractor shall provide via an email notification a list of contractor or subcontractor personnel who require a CAC to the COR. The contractor shall notify the COR of any change to the list and provide an updated list within ten calendar days.

In accordance with AFFARS 5352.242-9001, the contractor shall report a lost or stolen CAC no later than the next business day. The contractor shall return CACs within seven working days once contractor personnel no longer require computer network/system access and/or installation access. The contractor shall return an expired CAC within seven working days after the expiration date.

1.9.2.8 Cyber Security and Information Assurance (IA):

The contractor shall ensure all facilities, computer and data systems to include TYQ-23A(V)1 technician diagnostic equipment, used to store and process data will implement and maintain administrative, physical, technical, and procedural safeguards and industry best practices at a level sufficient to secure total Data Loss Prevention (DLP) such as cyber security, unauthorized access, destruction, use, modification, disclosure and overall vulnerability.

Contractor shall leverage industry expertise, state of the art technology, tactics, techniques and industry best practices regarding risk management frameworks. Contractor shall develop, validate and implement cybersecurity mitigation strategies and security controls. Contractor shall implement industry-standard and up-to-date security tools, technologies and procedures including, but not limited to:

· Anti-virus and anti-malware protections

· Intrusion detection

· User accounts (local, system, service, active directory)

· Encryption at a level equivalent or stronger than 128-bit level at rest and in motion.

· Physical accountability safeguards

1.9.3 Physical Security:

The contractor shall be responsible for safeguarding all Government equipment, information and property provided for contractor use. The contractor shall provide protection to Government property to prevent damage during the period of time the property is under the control or possession of the contractor.

1.9.4 Government Property Damage:

The contractor shall record and report, within one (1) business day, to the CRC Program Manager, PCO and designated Government site POC, all available facts relating to each instance of accidental damage to Government property or injury to either contractor or Government personnel (CDRL A014). The contractor shall not perform any work on the damaged equipment/property until released by an authorized Government representative. If the Government elects to conduct an investigation of the accident, the contractor shall cooperate fully and assist the Government personnel until the investigation is completed.

1.9.5 Program Protection:

The contractor shall integrate cybersecurity into systems security engineering (as part of systems engineering), program protection, anti-tamper, and design processes. The contractor shall ensure that the cybersecurity portions of the overall system design are included in system engineering and design documents, test plans, procedures, and reports. The contractor shall clearly and consistently identify cybersecurity boundaries in program documents and drawings. The contractor shall ensure that the development environment and processes support cybersecurity implementation. For all cybersecurity testing, regression testing, etc, any procedures deemed unnecessary shall require Government approval prior to omission.

The contractor’s cybersecurity workforce shall maintain compliance with the cybersecurity contractor training and certification requirements in DoD 8570.01-M and meet the investigative level requirements established in Enclosure 3 of DoDI 8500.01.

1.9.6 Cybersecurity Strategy:

The contractor shall implement the Government-developed Cybersecurity Plan for the system, its subsystems, components and support systems/equipment IAW DoDI 8510.01.

The contractor shall adhere to the following definitions for patches and configuration changes for all requirements:

A patch shall be defined as a piece of software designed to adjust a computer program, or its supporting data, in order to fix security vulnerabilities and other bugs. Applying a security patch corrects the vulnerability since patches contain code that repair the software application to address and eliminate the problem. Patches are not limited to patches released by Microsoft (i.e., KBs).

A configuration change shall be defined as a change that modifies the system’s existing configuration posture. Some common configuration change examples include: disabling services and modifying privileges, removing or updating affected software, making changes to registry settings, changing firewall rules, adjusting file attributes, and modifying router access controls.

Upgrading is the process of replacing a product with a newer or better version of the same product in order to bring the system up to date or to improve its characteristics. Patches are typically included in service agreements while upgrades are not. Upgrades shall be considered configuration changes.

The contractor shall apply cybersecurity requirements to networked assets used to support TYQ-23A (e.g., unclassified test bed, Base Stations, SIPR workstations).

1.9.7 Cybersecurity Controls:

The contractor shall identify, manage, and verify adherence to cybersecurity requirements in the same manner as all other system requirements.

The contractor shall implement, per PMO direction, the applicable cybersecurity controls from Committee on National Security Systems Instruction (CNSSI) No. 1253 for the system using the Risk Management Framework (RMF) process, or other DoD approved equivalent process, developed by the program. The contractor shall update the System Security Profile (SSP) to document the controls as implemented in the system design. The contractor shall update and deliver a SSP IAW National Institute of Standards and Technology (NIST) SP 800-18 and IAW the RMF CDRL. The contractor shall ensure and document bi-directional traceability between security controls and requirements. (CDRL A021)

The contractor shall ensure, per PMO direction, that technical data developed for the program address any cybersecurity controls (e.g., administrative, procedural, inherited) or requirements that affect system operation, maintenance, repair, or other support activities. As needed, the contractor shall develop and update technical documents with new processes to meet these requirements.

1.9.8 Cybersecurity Risk Management:

The contractor shall conduct an assessment of the system configuration to identify and quantify cybersecurity risks introduced by the addition of new hardware and software to the system. In the assessment, the contractor shall include a completed Security Controls Traceability Matrix and a quantitative risk assessment supported by an architecture analysis with data flows explaining how the controls, as described in CNSSI No. 1253, are applied to the information, architecture, and underlying hardware and software. (CDRL A021)

The contractor shall identify and manage cybersecurity risks as part of the overall program risk management process (consisting of cost, schedule, and performance risks). The contractor shall ensure cyber risk management activities are consistent with guidance provided in Committee on National Security Systems Policy (CNSSP) No. 22 (Policy on Information Assurance Risk Management for National Security Systems), including the applicable implementation guidance documents in Appendix B. (CDRL A021)

The contractor shall ensure that the cybersecurity risk management activity frequently reexamines threats, exposures, and vulnerabilities to assess changes to system architecture and design. The contractor shall, as appropriate, recommend changes to cybersecurity controls for the system. The contractor shall ensure that no documentation conflicts with the program’s cybersecurity strategy and the SSP. (CDRL A021)

1.10 Quality and Post Award Information:

1.10.1 Post Award Conference/Periodic Progress Meetings:

The Contractor shall attend any post award conference convened by the contracting activity or contract administration office. The PCO, Contracting Officers’ Representative (COR), and other Government personnel, as appropriate, may meet periodically with the contractor to review the contractor's performance. At these meetings the PCO shall apprise the contractor of how the Government views the contractor's performance and the contractor shall apprise the Government of problems, if any, being experienced. Appropriate action shall be taken to resolve issues.

1.10.2 Contracting Officer Representative (COR):

The COR shall be identified in a separate letter. The COR monitors 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 notify both the PCO and Contractor of any deficiencies; and coordinate availability of Government furnished property. A letter of designation issued to the COR, a copy of which shall be 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 task order/contract.

1.10.3 Identification of Contractor Employees:

All contract personnel attending meetings, and working in environments, where contractor status is not obvious to third parties are required to identify themselves as such, to avoid the impression they are Government officials. Contract personnel must also ensure that all documents or reports produced by contractors are suitably marked as contractor products or that contractor participation is appropriately disclosed. Contractor personnel may be required to obtain and wear identification badges, or other identifying attire, in the performance of this service.

1.11 Contractor and Freight Travel/Transportation:

1.11.1 Travel Regulations:

Contractor personnel shall comply with all regulations for travel including, but not limited to, compliance with the Department of Defense (DOD) Foreign Clearance Guide (FCG) for travel overseas. The FCG may be accessed at: https://www.fcg.pentagon.mil/. Contractor shall be responsible for submitting all required entries in the various systems including but not limited to, the Travel Tracker (https://iatp.pacom.mil) and the Aircraft and Personnel Automated Clearance System (APACS) (https://apacs.dtic.mil). Instructions can be found within the FCG website.

1.11.1.1 Travel and Other Direct Costs:

Travel in support of this effort must be pre-approved by the Contracting Officer Representative (COR) by email. The contractor shall have Defense Base Act (DBA) coverage for all work performed outside the United States prior to travel start, which will be considered an ODC and reimbursable to the contractor. Travel is billed in accordance with Uniformed Travel Determination (UTD/civilian Travel Determination (CTD) – revised JTR 2017.

If any United States Government approved ODC is Contractor Acquired Property (CAP), the purchase of CAP shall comply with all appropriate clauses and provide the Administrating Contracting Officer (ACO) requisitioned information and any other information that the ACO requires to issue a contract modification properly identifying the CAP.(CDRL A022)

1.11.2 Travel:

1.11.2.1

Overseas and identified OCONUS location travel costs shall be IAW the Federal Acquisition Regulation (FAR) 31.205-46. The contractor shall minimize Government expense by consolidating Preventative Maintenance services at sites located in the same geographic area, whenever possible. Contractor shall provide a deliverable stating travel costs incurred for each travel effort overseas and identified OCONUS locations. This deliverable shall report all travel hours and expenses incurred to include, at minimum, airfare, rental cars, any additional transportation costs, taxes, fees, and lodging to be incurred (while traveling). (CDRL A016)

1.11.2.2

Overseas and identified OCONUS location travel costs shall be IAW the Federal Acquisition Regulation (FAR) 31.205-46. The contractor shall minimize Government expense by consolidating Preventative Maintenance services at sites located in the same geographic area, whenever possible. Contractor shall provide a deliverable stating travel costs incurred for each travel effort overseas and identified OCONUS locations. This deliverable shall report all travel hours and expenses incurred to include, at minimum, airfare, rental cars, any additional transportation costs, taxes, fees, and lodging to be incurred (while traveling). (CDRL A009)

1.11.3 Parts, Materials, and Supplies Delivery:

Parts, materials, and supplies shall be properly packaged to foster an undamaged delivery. Contractor shall coordinate with the site POC for delivery at a mutually agreed time.

1.11.4 Freight Charges:

Contractor shall be responsible for freight/delivery charges completed under this contract unless special circumstances are identified by the CRC Program Manager and/or PCO. DoD Transportation Protective Services approved carrier. Tracking and shipping numbers shall be provided to the CRC PMO through e-mail for each transaction. This service is invoiced under the Other Direct Costs (ODC).

1.11.4.1 Special Freight:

The U.S. Government has certain missions that require special freight handling, packaging, and delivery requirements for the interests of national security. These requirements may dictate, but are not limited to: constant U.S. control, special freight channels/contractors, freight packaging and sealing, freight tracking and escorting. These sites and requirements shall be identified to the contractor by mission and task order level. Special freight handling/shipping requirements shall be billed Firm Fixed Price (FFP) billed against CLIN 0006 for these specially identified requirements/missions.

1.12 Contractor Responsibility:

1.12.1 Internet Database with Reporting:

The contractor shall establish, maintain and provide access to an internet database accessible by CRC Program Managers. This database shall include, but not be limited to: POC information for both the site and technician, FMR’s, Spares Inventory Listing, Time Compliance Technical Order (TCTO), Request for Deviation (RFD), CDRL’s, Updated Schedule, Trip Reports, End of Day Reports, Meeting Materials, Trend Analyses, all PM reports, and documentation relating to the completion of the TYQ23A(V)1 on all task orders. The contractor shall permit Government “read only” access to the data contained in the contractor’s electronic database 24X7X365. (CDRL A010).

1.12.2 Records/Data:

The USG will retain unlimited data rights to all data/material developed under this effort. Data requirements and deliverables are identified in section 5 (Monthly Technical Status, Monthly Financial Status, Travel Authorization Request (TAR), Control Chart Reporting, and Trip Reports).

1.12.3 Weekly Conference Call:

The contractor shall implement a Weekly conference call with the CRC Office to discuss the status of all CLS activities including, service work, Spares, to include percentages, quantities, schedules, concerns and issues. A summary of all actions, in the form of a report (CDRL A012), shall be obtained to the CRC Program Manager two business days prior to conference call. The contractor shall be responsible for providing the call-in number. The call shall be held at a mutually agreed time.

1.12.4 Program Management Review (PMRs), Technical Interchange Meeting, Staff Assistance Visits (SAV):

The contractor shall participate in Technical Interchange Meetings, Staff Assistance Visits and semi-annual PMRs, with the Government at a mutually agreed location, time, which shall be coordinated through CRC PMO. PMR’s may be held at contractor’s location or a mutually agreed location at the discretion of the CRC Office. The government reserves the right to hold or cancel PMR’s, TIM’s, and SAV’s. During the reviews the contractor shall address any and all issues/concerns with the program. The contractor shall develop agendas for the reviews and include topics requested from the government. The topics shall be reviewed and approved by CRC prior. The contractor shall also record minutes of reviews and meetings and place documents in Internet Database IAW Section 1.12.1. The contractor shall provide the minutes within 3 business days after the conclusion of the event. The contractor shall provide an advance electronic copy of all PMR slides, 5 business days prior to scheduled meeting, to CRC Program Managers. (CDRL A013).

1.13 CDRL Listing

Part 2 Government Furnished Property, Equipment, and Services

2. Government Furnished Property, Equipment, and Services

2.1 Services:

The contractor shall manage and maintain all GFP, including Government Furnished Information (GFI), Government Furnished Equipment (GFE), and Government Furnished Material (GFM) in its possession IAW FAR Part 45. The contractor shall manage the warehousing, and receiving of GFP, including as applicable: software, technical data/TOs, consumable and non-consumable spares. The contactor shall update GFP inventory as changes occur. The contractor shall account for all Government property on a monthly basis. The contractor shall account for and track all GFP using the OEM part number and OEM cage code, if applicable. The contractor shall provide an inventory to DCMA and the CRC PMO of all Government property in the control of the contractor at the beginning of the contract term and provide updates every month. This monthly update shall list all Government property in the support of this contract. The contractor shall ship all GFP to other locations as directed by the CRC PMO during any future transition efforts. The contractor shall provide to the Government a GFP inventory report that shall include GFP in possession of subcontractors. The contractor/subcontractor shall not modify or alter GFP from the approved configuration baseline for this CLS contract effort without prior written approval from the Government. (CDRL A008)

2.2 CLS TYQ-23A GFP Disposition:

The contractor shall identify TYQ-23A items in an inventory excess position, items identified as having exceeded their shelf/service life, and/or obsolete item candidates to the CRC PMO for disposal IAW DoD 4160.28. The contractor shall also accomplish recommended disposal actions and ensure disposal process is complete, when approved by the CRC PMO.

The contractor shall verify with the CRC PMO the items requiring disposition to ensure they are no longer needed for performance. Disposition requests shall be submitted through DCMA who will further coordinate with the COR for disposition instructions. (FAR 52.245-1)

Part 3 Contractor Furnished Items and Services

3. Contractor Furnished Items and Services:

3.1 Contractor Acquired Property:

With the exception of any government furnished property identified elsewhere within this PWS, the contractor shall provide everything needed to accomplish PWS requirements (i.e. - office and lab space, office equipment [desks, chairs, etc.] and supplies, computer equipment/software [desktop and/or laptop], telephones and telephone services [including the 1-800 service], internet services, and reproduction facilities (except those required for producing specific training manuals or materials). All materials purchased by the contractor for the use or ownership of the Federal Government, becomes the property of the Federal Government. The transfer of materials shall be documented by the contractor in the monthly status report. The contractor must furnish the COR copies of such documents monthly, through E-mail. (CDRL A022)

Part 4 Work Requirements, Task, and Transition

4. Work Requirements, Task, and Transition:

4.1 Work Requirements:

· The contractor shall provide support services to accomplish Direct Mission Support (DMS) services as outlined in this PWS.

· The contractor shall provide all services and incidental supplies required to plan, manage, and execute the tasks in accordance with this PWS.

· The contractor shall appoint Contractor Man hour Equivalent (CME) as the Lead in writing to effectively execute the tasks and requirements.

· The contractor shall not exceed 1920 hours per year per CME. The contractor shall provide sufficient manpower to complete the requirements outlined in this PWS.

4.2 Task Requirements & Technical Capabilities:

· The Contractor shall provide services that will support, review, analyze, refine, and provide feedback periodically determined by the government on current and evolving TYQ-23A issues, technical requirements, and/or related issues for TYQ-23A equipment as directed by the CRC SPO.

· Provide subject matter expertise to fielded units of the TYQ-23A system.

· Contractor shall have capabilities to troubleshoot/maintain servers/clients, switches, IP copper and fiber networks, and display equipment for the duration of the contract.

· Contractor shall have capabilities to troubleshoot/maintain knowledge of Communications systems to include RF, microwave, multiplexers/de-multiplexers, and IP based transmissions for the duration of the contract.

· Contractor shall provide engineering support and have the technical knowledge to configure the current and future TYQ23A base line configuration in order to provide technical refresh’s, modification, understand the integration and configuration of current and future systems, i.e. 3-Dimensional Expeditionary Long Range Radar (3DELRR), Mode 5/Mode S.

· Contractor shall have the capability to execute the scope of a project service, which is any distinctive service that the Government cannot accomplish organically and deems necessary for the sustainment of the TYQ-23A. The project service may have incidental supplies that are undertaken to accomplish sustainment activities that are related to the TYQ-23A. Project requirements are salient characteristics, conditions, or tasks that must be completed to ensure the sustainment of the TYQ-23A. This may include, but is not limited to, replacement of air ducts, delamination issues, mobilization concerns, etc. The contractor solution for the project requirement must provide a clear picture of what needs to be done.

· Contractor shall provide technical solutions (troubleshoot) and recommendations in solving TYQ-23A equipment through a corrective action plan within 30 days to CRC PMO.

· Write, review, edit, update and correct technical order publications affecting current, modified, or proposed TYQ-23A requirements.

· Contractor shall be the CRC depot facility IAW Depot level T.O. This includes but is not limited providing capability, parts and labor to completely disassemble, inspect, maintain, repair, rebuild and test the systems that come to Depot for full depot level system maintenance according to the T.O.

4.3 Knowledge, Skill and Abilities/Qualifications:

· Personnel understand the CRC mission and its role within the Battlefield Management Command and Control (BMC2) arena and shall provide technical subject matter expertise and engineering support to the CRC System Program Office (SPO) pertaining to the manufacturing, inspection, testing, integration, validation, verification, installation, implementation, troubleshooting, maintenance, and operation of TYQ-23A system. Contractor shall have an established retention plan which addresses methods for assuring personnel remain versed on current and evolving technologies.

· Personnel must possess current security clearance IAW paragraph 1.3.7.

· Travel required in support of TYQ-23A systems.

· The contractor shall ensure personnel have comprehensive knowledge in interpreting technical data such as drawings, schematics, blueprints, and specifications of complete electronic systems.

· The contractor shall ensure personnel collectively have experience as an administrative assistant, virtual assistant or office admin assistant, knowledge of office management systems and procedures, working knowledge of office equipment, computer proficiency, excellent time management skills and the ability to prioritize work, coordinate travel arrangements, prepare required reports, attention to detail and problem solving skills, excellent written and verbal communication skills, and strong organizational skills with the ability to multi-task.

4.4 Automated Data Processing Equipment (ADPE), Teleprocessing, Shipping and Telephone Systems.

4.4.1 ADPE Hardware/ Software:

The contractor shall have access to and be proficient in the use of computer devices, and in using current Microsoft Office suite, Adobe suite, and other software necessary to meet program support requirements.

4.4.2 Teleprocessing:

The contractor shall be able to use compatible email to transfer electronic documents and information.

4.4.3 Packaging/Packing/Shipping Instructions:

Standard commercial practices shall be utilized for packaging, handling, and shipping. The contractor shall provide shipping by establishing an account with FedEx, UPS, or DoD Transportation Protective Services approved carrier. Tracking and shipping numbers shall be provided to the CRC PMO through e-mail for each transaction. This service is invoiced under the Other Direct Costs (ODC).

4.4.4 Telephone Support:

The contractor shall maintain a toll-free number with recording capability providing access for the Air Control Squadrons, Test Agencies, Fixed Sites, Training Locations and Peripheral Sites. The toll free number shall be manned 8 to 5 Mountain Standard Time

4.5 Government System Accounts:

The contractor shall establish accounts with the appropriate government agency for Technical Orders access and Joint Engineering Data Management Information and Control System (JEDMICS) for drawings. The COR will assist the contractor to ensure these accounts are requested within the first 60 days after contract award.

4.6 Repair and Maintenance Analysis:

Shall monitor fleet wide system issues and failures in order to:

· Assist with accurate provisioning

· Redefine spares requirements based upon known Mean Time between Failure (MTBF)

· Understand system complexity as it relates to COTS software integration/configuration issues

· Implement quality controls into the manufacturing process based on known deficiencies

· Build instructions into organizational TOs to safeguard against damage

· Compare trends on high failure items and take proactive measures to ensure extended warranties are purchased prior to expiration and material/components are ordered in advance

· Ensure that alternate parts are available to prevent/reduce system downtime due to long lead times

(CDRL A018)

4.7 Maintenance Data Collection:

The contractor shall maintain a searchable excel file for the TYQ-23A…