PSS-T_Base_PWS.docx
DOCX document 144 KB Posted
- Attached to
- DRAFT Persistent Surveillance Systems - Tethered
- Solicitation number
- W56KGY18R0019
About this file
This special notice solicits industry feedback on draft documents to support a requirement for engineering, technical, logistics, and flight operations services for the Persistent Surveillance Systems - Tethered program. Services may include program management, engineering, logistics, operations, and facilities and infrastructure support at various locations in CENTCOM, AFRICOM, PACOM, EUCOM, SOUTHCOM, and NORTHCOM. The performance work statement outlines requirements for up to 58 Army Prepositioned Stock systems and 54 non-APS systems, to be operated 24/7. The notice states that the requirement may be set aside for small businesses or procured through full and open competition, with an anticipated solicitation issuance of June 2018. Feedback is requested to be submitted electronically to the listed points of contact by the projected RFP date.
Base PWS
View the file
Other files
| File | Type | Posted |
|---|---|---|
| PSS-T_Base_CDRLs.pdf | ||
| PSS-T_TO-0001_PWS-Appendix-A.docx | DOCX document | |
| PSS-T_TO-0002_QASP.docx | DOCX document | |
| PSS-T_TO-0002_PWS.docx | DOCX document | |
| PSS-T_TO-0002_PWS-Appendix-A.docx | DOCX document | |
| PSS-T_TO-0001_PWS.docx | DOCX document | |
| PSS-T_Base_QASP.docx | DOCX document | |
| PSS-T_Base_PWS-Appendix-A.docx | DOCX document | |
| PSS-T_TO-0001_CDRLs.pdf | ||
| PSS-T_TO-0001_QASP.docx | DOCX document | |
| PSS-T_TO-0002_CDRLs.pdf |
Show all 11
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
UNCLASSIFIED // FOR OFFICIAL USE ONLY
Contract # TBD Performance Work Statement 23 March 2018
PERFORMANCE WORK STATEMENT (PWS)
for
Persistent Surveillance Systems - Tethered (PSS-T) Engineering/Technical, Logistics, and Flight Operations Support Services Contract Number TBD Base Contract
Version 1.0
23 March 2018
Product Director (PD) Aerostats 6580 Surveillance Loop Aberdeen Proving Ground, MD 21005
PAGE INTENTIONALLY BLANK
Table of Contents
| 1. | Scope | 1 |
| 2. | Applicable Documents | 1 |
| 3. | Requirements | 7 |
| 3.1 | Program Management | 7 |
| 3.1.1 | Program Management Support (CLIN CPFF) | 7 |
| 3.1.2 | Contract Transition (CLIN CPFF) | 7 |
| 3.1.3 | Reporting (CLIN CPFF) | 7 |
| 3.2 | Engineering Services | 8 |
| 3.2.1 | Sustainment Engineering (CLIN CPFF) | 8 |
| 3.2.2 | System Engineering (CLIN CPFF) | 8 |
| 3.2.3 | Software Engineering (CLIN CPFF) | 10 |
| 3.2.4 | Network Engineering (CLIN CPFF) | 10 |
| 3.2.5 | Cybersecurity (CLIN CPFF) | 12 |
| 3.2.6 | Configuration Management (CM) and Planning (CLIN CPFF) | 13 |
| 3.2.7 | Technical Data Package (TDP) (CLIN CPFF) | 15 |
| 3.2.8 | Quality Program (CLIN CPFF) | 16 |
| 3.2.9 | Test and Evaluation (CLIN CPFF) | 16 |
| 3.2.10 | Ground Systems Interface Facility (GSIF) (CLIN CPFF) | 17 |
| 3.2.11 | Program Protection Plan (PPP) (CLIN CPFF) | 18 |
| 3.3 | Logistics | 18 |
| 3.3.1 | Integrated Product Support Management (CLIN CPFF) | 18 |
| 3.3.2 | Performance Based Logistics Metrics Monitoring and Reporting Requirements (CLIN CPFF) | 18 |
| 3.3.3 | Supply Support (CLIN CPFF) (CLIN FFP) | 19 |
| 3.3.4 | Provisioning (CLIN CPFF) | 20 |
| 3.3.5 | Package Handling, Storage, and Transportation (CLIN CPFF) | 22 |
| 3.3.6 | Field and Depot Level Repairs (CLIN CPFF) | 23 |
| 3.3.7 | Maintenance Planning and Management (CLIN CPFF) | 24 |
| 3.3.8 | Reset (CLIN CPFF) | 25 |
| 3.3.9 | Depot Public Private Partnership (CLIN CPFF) | 25 |
| 3.3.10 | System Safety and Health Hazards (CLIN CPFF) | 26 |
| 3.3.11 | Training (CLIN CPFF) | 27 |
| 3.3.12 | Technical Manual (TM) (CLIN CPFF) | 27 |
| 3.4 | Operations | 28 |
| 3.4.1 | Flight Operations Center Support (CLIN CPFF) | 28 |
| 3.4.2 | Aerostat Crew (CLIN FFP) | 29 |
| 3.4.3 | Aerostat Operations (CLIN CPFF) | 29 |
| 3.4.4 | Operations Reporting (CLIN CPFF) | 30 |
| 3.4.5 | Drawdown, Demobilization, and Surge (CLIN CPFF) | 30 |
| 3.5 | Other Requirements | 31 |
| 3.5.1 | Contract Deliverables (CLIN CPFF) | 31 |
| 3.5.2 | Facilities and Infrastructure (CLIN CPFF) | 31 |
Contract # TBD Performance Work Statement 23 March 2018 i
Scope The Contractor shall provide engineering, logistics, operations, and program management support for the PSS-T aerostat Family of Systems (PSS-T FoS). The contractor shall support up to 58 Army Prepositioned Stock (APS) PSS-T systems (29 PSS-T Large and 29 PSS-T Medium), and up to 54 non-APS systems, including PTDS, PGSS, and PGSS towers. The required services shall support operations 24 hours a day/seven (7) days.
Background PSS-T FoS provide persistent, integrated, networked, and multi-sensor information collection by operating for long periods at altitude to maximize line of sight and field of regard. PSS-T FoS are capable of detecting hostile fire, providing target coordinates to appropriate command and control/fire control centers, and marking ground targets for rapid engagement. PSS-T FoS provide weather-dependent, continuous support throughout the joint operational area, directly enhancing the commander’s situational understanding.
The current PSS-T FoS includes PSS-T Medium, developed as Persistent Ground Surveillance System (PGSS) aerostat (12 to 35 meters); PSS-T Large aerostat, developed as Persistent Threat Detection System (PTDS); and PGSS towers. The PSS-T FoS includes hardware, firmware, software, system, subsystems, cyber security functions, materials, and all associated interfaces. The major end items of the PSS-T Large, also known as the AN/DSY-1(V)1 Surveillance System, Elevated Sensor, are defined in Technical Manual (TM) 11-5895-2014-10-HR Hand Receipt. The major end items of the PSS-T Medium, also known as the AN/DSY-2(V)2 Surveillance System, Elevated Sensor, are defined in TM 11-5895-2017-10-HR Hand Receipt.
Applicable Documents Table 2.1: Army Regulations (AR) and Department of Army Pamphlets (DA PAM)
| Number |
| Title |
| Date |
| AR 25-2 |
| Information Assurance |
| March 2009 |
| AR 200-1 |
| Environmental Protection Enhancement |
| December 2007 |
| AR 385-10 |
| The Army Safety Program |
| February 2017 |
| AR 700-15 |
| Packaging of Materials |
| January 2004 |
| AR 750-1 |
| Army Material Maintenance Policy |
| August 2017 |
| DA PAM 73-1 |
| Test and Evaluation in Support of System Acquisition |
| May 2003 |
| DA PAM 385-40 |
| Army Accident Investigations and Reporting |
| March 2015 |
| United States Army Training and Doctrine Command (TRADOC) Pamphlet 350-70-14 |
| Training and Education Development in Support of the Institutional Domain |
| March 2015 |
Table 2.2: Hazardous Material (HAZMAT) Manuals
| Number |
| Title |
| Date |
| TM 38-250 |
| Preparing Hazardous Materials for Military Air Shipments |
| July 2017 |
| 29 CFR Part 1910 |
| Occupational Safety and Health Standards |
Table 2.3: Department of Defense (DoD) Regulations, Directives (DoDD), Instructions (DoDI), and Manuals
| Number |
| Title |
| Date |
| DoDI 4151.21 |
| Public-Private Partnerships for Product Support |
| November 2017 |
| DODI 4161.02 |
| Accountability and Management of Government Contract Property |
| September 2017 |
| DoDI 5000.64 |
| Accountability and Management of DoD Equipment and Other Accountable Property |
| July 2017 |
| DoDI 6055.07 |
| Mishap Notification, Investigation, Reporting, and Record Keeping |
| June 2011 |
| DoDI 8320.04 |
| Item Unique Identification (IUID) Standards for Tangible Personal Property |
| September 2015 |
| Risk, Issue, and Opportunity Management Guide for Defense Acquisition Programs |
| January 2017 |
| DoDI 8500.01 |
| Cybersecurity |
| Mar 2014 |
| DoDI 8510.01 |
| Risk Management Framework (RMF) for DoD Information Technology (IT) |
| Mar 2014 |
| - |
| Defense Acquisition Guidebook |
| February 2017 |
Table 2.4: Safety Guidance
| Number |
| Title |
| Date |
| - |
| United States (U.S.) Army Combat Readiness Center Unmanned Aircraft System Accident Report (Use and Preparation Guide) |
| January 2016 |
Table 2.5: Defense Handbooks (MIL-HDBK), Performance Specifications (MIL-PRF), and Defense Standards (MIL-STD)
| Number |
| Title |
| Date |
| MIL-PRF-32070 A |
| Test Program Sets |
| October 2016 |
| MIL-PRF-63029J |
| Manuals, Technical: Requirements for Operator's Manuals and Checklists for Manned and Unmanned Aircraft Systems |
| August 2014 |
| MIL-PRF-63002L |
| Performance Specification Manuals, Technical: Requirements for Preparation of Modification Work Orders (MWO) |
| April 2013 |
| MIL-STD-129R |
| Military Standard, Military Marking Standard Practices |
| February 2014 |
| MIL-STD-130N |
| Identification Marking of U.S. Military Property |
| November 2012 |
| MIL-STD-881C |
| Work Breakdown Structures for Defense Materiel Items |
| October 2011 |
| MIL-STD-882E |
| System Safety |
| May 2012 |
| MIL-STD-961E |
| Defense and Program-Unique Specifications Format and Content |
| October 2015 |
| MIL-STD-2073-1E |
| Standard Practice for Military Packaging |
| January 2011 |
| MIL-STD-2361C |
| Digital Publications Development |
| July 2010 |
| MIL-HDBK-61A |
| Configuration Management Guidance |
| February 2001 |
| MIL-STD-38784A |
| Manuals, Technical: General Style and Format Requirements |
| July 2016 |
| MIL-STD-31000A |
| Technical Data Packages |
| December 2017 |
| MIL-STD-40051-2B |
| DoD Standard Practice: Technical Manuals and General Assembly of Information |
| November 2012 |
| MIL-STD-40051-2C |
| Preparation of Digital Technical Information for Page Based Technical Manuals (TMs) |
| December 2015 |
| MIL-HDBK-338B |
| Electronic Reliability Design Handbook |
| May 2012 |
| Army TM 5-698-4 |
| Failure Mode Effects and Criticality |
| September 2006 |
| MIL-DTL-15024 |
| Plates, Tags, and Bands for Identification of Equipment, General Specification for |
| Nov 1997 |
| MIL-STD-3018(2) |
| Parts Management |
| June 2015 |
| Software Assurance Countermeasures in Program Protection Planning |
| March 2014 |
Table 2.6: Non-Government Documents
| Number |
| Title |
| Date |
| ANSI/EIA-649-1 |
| Configuration Management Requirements for Defense Contracts |
| November 2014 |
| ANSI/EIA-649-B |
| Configuration Management Standard |
| April 2011 |
| GEIA-STD-0007-B |
| Logistics Product Data |
| May 2013 |
| GEIA-HB-0007 |
| Logistics Product Data Handbook |
| March 2010 |
| TA-HB-0007-1 |
| Handbook and Guide for Logistics Product Data Reports |
| May 2013 |
| SO300-BT-PRO-010 |
| GIDEP Operations Manual |
| September 2010 |
| National Institute of Standards and Technology Special Publication (NIST) Special Publication (SP) 800-37 |
| Guide for Applying the Risk Management Framework to Federal Information Systems |
| February 2010 |
| NIST SP 800-53A |
| Security and Privacy Controls for Federal Information Systems and Organizations |
| April 2013 (includes updates as of 22 January 2015) |
| Institute for Electrical Electronics Engineers (IEEE) 29148-2011(E) |
| Systems and software engineering -- Life cycle processes -- Requirements engineering |
| IEEE 802 |
| IEEE family of standards for local area networks and metropolitan area networks |
| Intelligence Community Directive 503 |
| Intelligence Community Information Technology Systems Security Risk Management |
15 September 2008
| Committee on National Security Systems (CNSS) Instruction No. 1253 |
| Security Categorization and Control Selection for National Security Systems |
| October 2009 |
| ISO 9001-2015 |
| Quality Management Systems |
| 15 September 2015 |
Table 2.7: Current PSS-T Documentation
| Number |
| Title |
| Date |
| A3350096 |
| PD Aerostats Configuration Management Plan |
| November 2017 |
| A3350095 |
| PD Aerostats Configuration Control Charter |
| September 2017 |
| A3351220 |
| PD Aerostats Medium Reset Standard Operating Procedure (SOP) |
| A43351159 |
| Repair Data SOP |
| A3351221 |
| PD Aerostats Large Reset SOP |
| TM 11-5895-2014 |
| AN/DSY-1(V)1 Technical Manual Series |
| September 2016 |
| TM 11-5895-2071 |
| AN/DSY-1B(V)1 Technical Manual Series |
| - |
| TM 11-5895-2017 |
| AN/DSY-2(V)2 Technical Manual Series |
| - |
| - |
| PSS-T Training Program of Instruction (POI) |
| - |
| - |
| PSS-T Large TDP |
| - |
| - |
| PSS-T Medium TDP |
| - |
| Capability Production Document for Persistent Surveillance Systems – Tethered (PSS-T) Increment: 1 |
| 25 NOV 13 |
| AN/DSY-2(V)1 FMECA |
| 06 April 2016 |
| - |
| Technical Manual (TM) 11-5895-2014-10-HR Hand Receipt for PSS-T large |
| 15 August 2016 |
| - |
| TM 11-5895-2017-10-HR Hand Receipt for PSS-T med |
| 11 April 2017 |
Requirements Program Management Program Management Support (CLIN CPFF) The Contractor shall submit a management plan in accordance with (IAW) contract data requirements list (CDRL) item A001.
The Contractor shall host quarterly program management reviews (PMRs).
The Contractor shall submit the PMR presentation material IAW CDRL B001.
The Contractor shall host monthly business management reviews (BMRs). The management metrics and leading indicators the contractor uses internally to manage this effort shall be reported in the Contractor’s Progress and Status Report (CDRL A003) The Contractor shall submit the BMR presentation material to the Government IAW CDRL B001.
The Contractor shall provide conference minutes IAW CDRL B002.
The Contractor shall support in-process reviews to review contract deliverables as requested by the Government.
The Contractor shall be responsible for the administration of a Government furnished information management system, to include but not limited to management of user accounts as well as all applicable modules. The Contractor shall manage the Government furnished information management system IAW Repair Data SOP A43351159 The Contractor shall submit an operations security plan IAW CDRL A011 Contract Transition (CLIN CPFF) The Contractor shall develop and execute phase-in transition activities IAW CDRL A001. The duration of the transition period will be specified at the task order (TO) /delivery order (DO) level.
The Contractor shall develop a Phase-Out Transition Plan and execute phase-out transition activities IAW CDRL A002. The Phase-Out Transition Plan may be released to potential offerors for any follow-on efforts. The duration of the transition period will be specified at the TO/DO level.
Reporting (CLIN CPFF) The Contractor shall submit reports by TO/DO. The contractor shall deliver a Contractor’s Progress and Status Report IAW CDRL A003 and a Contract Funds Status Report IAW CDRL A004.
The Contractor shall submit invoices in Invoicing, Receipt, Acceptance, and Property Transfer (iRAPT) and provide email notification to the Contracting Officer’s Representative (COR) at the same time as the invoice is posted to iRAPT.
The Contractor shall provide supporting invoice documentation for service CLINs and sub-contract line item numbers (SLINs) and travel and other direct cost (ODC) CLINs and SLINs IAW CDRL A005.
The Contractor shall provide a personnel report IAW CDRL D001.
Engineering Services Sustainment Engineering (CLIN CPFF) The Contractor shall maintain the readiness of the PSS-T FoS.
The Contractor shall conduct, maintain and update failure mode, effects, and criticality analysis (FMECA) for PSS-T FoS. The Contractor shall deliver FMECAs IAW CDRL E001.
The Contractor shall establish a failure reporting, analysis, and corrective action system (FRACAS) and initiate the evaluation process within 24 hours of any incident or deviation in system performance. The report shall be submitted IAW CDRL F001.
The Contractor’s FRACAS shall establish a failure review board (FRB) to meet weekly with Government participation IAW MIL‐HDBK‐338B.
The Contractor shall deliver the root cause analysis resulting from the FRACAS for any incident failure identified for the PSS-T FoS, its operators, trainers, or field service representatives (FSR) IAW CDRL A006.
System Engineering (CLIN CPFF) The Contractor shall plan, analyze, organize, and integrate capabilities into the PSS-T FoS as directed by the Government.
The Contractor shall use the Government provided concept of operations, mission profile, and interface control documents for requirement or engineering change development.
Integration shall include, but not be limited to: analysis, design, prototyping, integration testing, documentation, acquisition, size, weight, power, and cost analysis of all payloads, support electronics, and deployment of changes to the PSS-T FoS.
The Contractor shall use International Organization for Standardization (ISO)/International Electrotechnical Commission/ IEEE 29148-2011(E) when developing all derived requirements (hardware, software, and cyber) under this contract.
The Contractor shall update the system requirements specification IAW CDRL G001. The Contractor shall derive each hardware and software component specification from the Government supplied performance requirements and prepare the specifications IAW CDRLs G001 and G002 as specified in MIL-STD-961.
The Contractor shall manage and develop system and subsystem requirements. The Contractor shall deliver requirements to the Government IAW CDRL G001.
The Contractor shall perform system verification, validation and manage systems engineering processes IAW with the DoD Defense Acquisition Guidebook Chapter 3, figure 2.
The Contractor shall provide a report demonstrating system verification IAW CDRL H001.
The Contractor shall conduct risk management for all engineering deliverables IAW DoD Risk, Issue, and Opportunity Management Guide for Defense Acquisition Programs section 3.
The Contractor shall prepare a systems engineering management plan IAW CDRL F002.
As directed by the Government, the Contractor shall perform a trade study and analysis to supplement the development of an ECP IAW CDRL D002.
The Contractor shall continuously assess and enhance part commonality across the PSS-T FoS. The Contractor shall identify part commonality opportunities across the PSS-T FoS and provide recommendations to the Government to reduce PSS-T FoS logistics and associated costs The Contractor shall host technical interchange meetings (TIMs) to discuss a variety of engineering/technical issues including, but not limited to:
Test and Evaluation:
The Contractor shall host up to two (2) testing working group meetings per test: one (1) kick off meeting 30 days prior to each test to determine test requirements and procedures, and one (1) status meeting at the discretion of the Government based on the complexity of the test.
The Contractor shall host a monthly test sync meeting to discuss upcoming tests, issues, and concerns.
The Contractor shall host one (1) test readiness review per test, one (1) week prior to each test event.
Cyber Security The Contractor shall conduct a weekly RMF call with the Government to discuss the sustainment of the Government’s cybersecurity functions.
Configuration Management The Contractor shall host a weekly meeting to conduct configuration management activities to review requests for variance (RFV) and engineering change proposals (ECP).
The Contractor shall provide an agenda for each TIM IAW CDRL B001.
The Contractor shall provide minutes for each TIM IAW CDRL B002.
Software Engineering (CLIN CPFF) As directed by the Government, the Contractor shall provide software engineering support to build, sustain and upgrade software and firmware configuration items, collectively referred to as computer software configuration items (CSCI).
The Contractor shall manage software development and provide their software metrics related to software development progress IAW with CDRL A003.
The Contractor shall use the Government furnished configuration management system to manage software requirements.
The Contractor shall obtain Government approval prior to closing out any tickets/bugs that will affect the PSS-T FoS configuration baseline, i.e., those that will render the software NMC if not corrected.
The Contractor shall ensure all software artifacts are continually inputted into the Government configuration management system throughout the software’s development process.
The Contractor shall provide their software development plan IAW CDRL G011.
The Contractor shall deliver software design description IAW CDRL G003 for each software release or at the request of the Government.
The Contractor shall maintain a software/firmware compatibility matrix on the Government-furnished software repository for all software releases that shall describe the software versions and compatible firmware to all system releases.
The Contractor shall deliver a software test plan IAW CDRL G005.
The Contractor shall deliver a software test description IAW CDRL G008, for each release of a CSCI.
The Contractor shall provide the executables, source code, and documentation IAW CDRL G006.
The Contractor shall deliver a software version description IAW CDRL G004 for each software release or at the request of the Government.
The Contractor shall deliver an interface design document IAW CDRL G009 with each software release or at the request of the Government.
The Contractor shall be responsible for maintaining access and licenses for commercial software products required to support the PSS-T FoS.
Network Engineering (CLIN CPFF) As directed by the Government, the Contractor shall modify internal and external PSS-T FoS networks utilizing the IEEE 802 family of standards.
The Contractor shall build network topology charts and establish how the network shall be created, configured, and integrated.
The Contractor shall integrate new or existing sensors onto the network.
The Contractor shall modify the data flow within the existing PSS-T systems.
The Contractor shall configure network switches, routers, firewalls, serial to internet protocol (IP) convertors, video encoders, IP multiviewer, and any other device that connects to the PSS-T FoS internal or external network.
The Contractor shall maintain the field modification procedures to reflect the current fielded network configurations. The Government may require modification to procedures to comply with cyber security best practices.
The Contractor shall submit all network designs to the PD Aerostats configuration control board (CCB). The CCB must accept and approve the network design before the Contractor can formally integrate the new design. The Contractor shall deliver this data IAW CDRL J001.
The Contractor shall document the internal and external network bandwidth limitations for all network baseline and connections. Network configurations must be controlled, documented, and distributed via the Government’s technical data repository.
The Contractor shall present the network architecture topology drawings, ports and protocols, port mapping, data flow drawings, and field installation/configuration procedures to the end users (N6 or J6) networking subject matter experts (SME) as directed by the Government.
The Contractor shall develop a network management plan IAW CDRL J002.
Cybersecurity (CLIN CPFF) Cybersecurity Requirements For systems that process Sensitive Compartmented Information (SCI)/Signals Intelligence (SIGINT) and/or connects to NSANet, the contractor shall follow DODI 8510.01 “Risk Management Framework (RMF) for DoD Information Technology (IT)”, National Institute of Standards and Technology Special Publication (NIST) 800-37 “Guide for Applying the Risk Management Framework to Federal Information Systems”, and Intelligence Community Directive (ICD) 503, “Intelligence Community Information Technology Systems Security Risk Management”. The contractor shall implement cybersecurity controls to safeguard the system, data and software IAW Certification and Accreditation, the Committee on National Security Systems (CNSS) Instruction No. 1253, “Security Categorization and Control Selection for National Security Systems” and NIST 800-53, “Recommended Security Controls for Federal Information Systems and Organizations” as well as any applicable overlays that are determined to be applicable to the system. The information system shall be configured IAW CS2 hardening guidelines. In some instances, the information system may be accredited by one authorizing official when a system operates at different classification levels/different connectivity. The authorizing agency/authority will be determined via coordination with the PM.
For systems that only process data at the SECRET classification level and below and/or connect to only SIPRNet/NIPRNet, the contractor shall follow DODI 8510.01 “Risk Management Framework (RMF) for DoD Information Technology (IT)”, National Institute of Standards and Technology Special Publication (NIST) 800-37 “Guide for Applying the Risk Management Framework to Federal Information Systems”, The contractor shall implement cybersecurity controls required to safeguard the data and software IAW Certification and Accreditation, the Committee on National Security Systems (CNSS) Instruction No. 1253, “Security Categorization and Control Selection for National Security Systems” and NIST 800-53, “Recommended Security Controls for Federal Information Systems and Organizations” as well as any applicable overlays that are determined to be applicable to the system and AR 25-2, “Information Assurance”. The information system shall be configured IAW the appropriate Defense Information Systems Agency (DISA) Security Technical Implementation Guides (STIGS). In some instances, the information system may be accredited by one authorizing official when a system operates at different classification levels/different connectivity. The authorizing agency/authority will be determined via coordination with the PM.
The Contractor shall ensure that changes, new hardware/software to the PSS-T FoS, information systems (e.g., Windchill and RepairData), and accountable property are configured IAW Defense Information Systems Agency (DISA) STIG hardening guidelines, NIST 800-53, and CNSS Instruction No. 1253.
The Contractor shall ensure that the changes and/or any new hardware/software to the PSS-T FoS, information systems and/or accountable property are coordinated with the Government cybersecurity point of contact and through the COR, and approved in advance by the Procuring Contracting Officer (PCO).
Maintaining Cyber Program & Product System Accreditations The Contractor shall update, sustain, and maintain PSS-T FoS accreditation under the RMF IAW DoDI 8500.01, DoDI 8510.01, and NIST 800-53A.
The Contractor shall report all information assurance vulnerability alerts (IAVA), STIGs, and bulletins within a system Plan Of Action & Milestones (POA&M) IAW CDRL A007. The contractor shall identify which IAVAs were implemented, those not implemented and justification, and how mitigated if mitigation was required. All non-implemented IAVAs and STIGs shall have Government concurrence.
The Contractor shall perform manual scans (Nessus, security content automation protocol, and security compliance checker) and provide results to the Government at least monthly to ensure the system is Federal Information Security Management Act and STIG compliant IAW CDRL A007.
Updates, Incident Reporting and Vulnerabilities Management (IAVMs) The Contractor shall apply exploit category A IAVAs within 14 calendar days of notification through the U.S. Army Network Enterprise Technology Command (NETCOM) SharePoint site.
The Contractor shall apply exploit category B IAVAs within 14 days, when possible, or within 30 calendar days if a system level POA&M to mitigate is provided.
The Contractor shall monitor all cybersecurity alerts and updates from vendor sites, mailing lists, third party sources, vulnerability scans and NETCOM SharePoint site for IAVMs.
The Contractor shall develop a POA&M to mitigate, patch, update, or modification recommendations and provide a POA&M IAW A007.
The Contractor shall implement corrective actions to mitigate findings as planned in the POA&M upon Government approval and direction.
Security Technical Implementation Guides (STIG) Contractor shall implement STIGs within 30 days from release of a new DISA STIG. If an update cannot be applied within 30 days, that STIG item shall be documented in POA&M with appropriate mitigations and submitted for Government approval IAW CDRL A007.
Configuration Management (CM) and Planning (CLIN CPFF) The Contractor shall establish a CM process to maintain the PSS-T FoS throughout the product life cycle IAW the PD Aerostats configuration management plan (CMP).
The Contractor shall maintain the PSS-T FoS and all sub-system requirements.
The Contractor shall execute configuration management IAW ANSI/EIA-649-1standard using the Government’s Windchill product lifecycle management (PLM) system. The Contractor shall prepare and submit a Contractor CMP IAW CDRL F003.
Configuration Control Only the PD Aerostats CCB is authorized to adjudicate RFVs or ECP through the Government’s CCB directives. The Contractor shall adhere to the PD Aerostats CCB charter.
Requests for Variance (RFV) For variances from the current approved configuration documentation, the Contractor shall adhere to the PD Aerostats CMP and shall submit a RFV IAW with CDRL F004.
For Critical or Major RFVs, the Contractor shall notify the Government no less than seven (7) calendar days in advance to participate in the PD Aerostats CCB. If accepted, the submitted items shall become part of the CCB agenda and scheduled at the discretion of the Government.
Engineering Change Proposal (ECP) The Contractor shall submit an ECP IAW CDRL F005 for any permanent change in the PSS-T FoS product configuration. ECP submissions shall be developed IAW MIL-HDBK 61A.
For Class I ECPs under the purview of the PD Aerostats CCB, the Government shall be notified by the submitting activity no less than seven (7) calendar days in advance to participate in the PD Aerostats CCB. If accepted, the submitted items shall become part of the CCB agenda and scheduled at the discretion of the Government.
The Contractor shall provide an assessment of third party intellectual property and data rights with all ECPs (CDRL F005).
Configuration Status Accounting The Contractor shall provide configuration status accounting reports IAW CDRL F006.
Configuration Audit The Contractor shall submit a configuration audit plan IAW CDRL F007.
The Contractor shall conduct configuration audits for RFVs and ECPs. The Contractor shall notify the Government of configuration audits 30 days prior to audits. The Government may choose to witness audits.
Functional Configuration Audit (FCA) The Contractor shall conduct FCAs to meet system requirements upon Government request. Testing includes verification and qualification tests performed on CIs and CSCIs.
Physical Configuration Audit (PCA) The Contractor shall support PCAs for any approved ECP to include planning, coordinating, executing the PCA, and resolving any findings as a result of the PCA.
The Contractor shall provide a configuration audit summary report IAW CDRL F008 and MIL-HDBK-61A.
Technical Data Package (TDP) (CLIN CPFF) Product Technical Data and Documentation The Contractor shall provide, maintain, and deliver a (Level III Equivalent) fully competitive production level TDP IAW CDRL F009 and MIL-STD31000A for any product configuration changes, special tooling, inspection, and special test equipment. The TDP shall consist of all data to support the sustainment and procurement of all necessary components: commercial off-the-shelf (COTS) components, Government off-the-shelf (GOTS) components, custom designed components, special tooling, and special test equipment.
The Contractor shall generate new product drawings/models and associated lists IAW CDRL F009 for any new designs resulting from changes.
As directed by the Government, the Contractor shall regenerate computer aided design source data for any drawing for which 3D models are not available and deliver IAW CDRL F009 for any existing designs resulting from changes.
Integrated Parts List and Component Selection The Contractor shall include parts lists on all drawings IAW CDRL F009.
The Contractor shall develop its parts management plan to include a parts selection list IAW CDRL K001.
The Government may perform inspections and audits to ascertain conformance to requirements and adequacy of the implementing procedures of the parts management plan.
The Contractor input bill of materials within the Government Windchill PLM system.
Source Control Drawings (SCDs) Prior to citing SCDs in the TDP, the Contractor shall obtain approval by the Government in writing. SCDs shall be limited to the greatest extent possible and should be processed IAW MIL-STD 31000A.
Software Product Data The Contractor shall submit all software documentation IAW CDRL G007.
The Contractor shall provide documentation to run software IAW CDRL G006.
The Contractor shall provide source code for any CSCIs resulting from configuration product changes for which the Contractor has created and/or modified the source code upon successful completion of testing IAW CDRL G006.
The Contractor shall submit installer as a compiled and execution ready object code for the Government specified computer and operating system IAW CDRL G006. An index list shall be provided with software submittals that details data items, data types, revisions, and data assertion rights.
The Contractor shall provide the Government rights to use, modify, and distribute software applications and source code for which the contractor has made modifications.
Quality Program (CLIN CPFF) The Contractor shall develop and maintain a quality program plan (QPP) IAW CDRL L001.
The Government may audit product and processes as well as the quality control system at any stage of contract performance. The QPP shall not be based on the Government’s QA surveillance plan, but on the Contractor’s internal controls to meet quality requirements.
Test and Evaluation (CLIN CPFF) The Contractor shall perform testing, including system integration testing, production acceptance testing, operational testing, electromagnetic interference and compatibility testing, verification and validation of all baseline changes and modifications, software testing, and IA security control assessor events IAW DA PAM 73-1. The Contractor shall notify the Government of testing events 30 days prior to events. The Government may choose to witness tests. Testing shall be conducted at the CONUS trainer/test systems currently located at Yuma Proving Ground (YPG), AZ which is comprised of PSS-T Large and PSS-T Medium systems. Alternate test locations may be authorized by the Government if there is an operational requirement that cannot be fulfilled in YPG.
The Contactor shall develop a comprehensive software test program IAW CDRL G011. All software testing planning events will be performed using tactical representative hardware where available.
The Contractor shall conduct all formal testing events with the finalized test configuration and pass the required exit criteria identified in the associated test plan prior to proceeding to an operational test.
The Contractor shall develop a T&E data collection plan IAW with DA PAM 73-1 Section 6-43 to determine test event duration, sample size required for collection based on the minimum amount of testing required to provide data to support test requirements to reach definitive conclusions concerning the system under test. Test data factors shall include, but not limited to: event variables, test controls, combining conditions, and the number of required trials. The Government at its discretion may request to view the T&E data collection plan.
The Contractor shall have appropriate test instrumentation systems to collect data to address the event issues and/or provide the necessary fidelity.
The Contractor shall identify the requirements for instrumentation support through the overall data requirements process, test control procedures development, and data collection and reduction planning. Instrumentation support includes ensuring adequate time for tasks to include but not limited to procurement of long-lead items.
The Contractor shall document and submit a test report IAW CDRL M001.
The Contractor shall deliver a software test report IAW CDRL G010.
The Contractor shall provide support for Government testing events. Such testing includes, but is not limited to: capabilities and limitations testing; U.S. Army Test and Evaluation Command testing; transportation of systems and components to the test site; personnel to perform system setup; personnel to operate and maintain test equipment at the test site; and troubleshooting to include reach-back support.
The Contractor shall participate in test and evaluation (T&E) integrated product teams.
The Contractor shall participate in the Government test working group. The contractor shall develop a test plan, test procedures, and system test entrance and exit criteria for testing. The test plan shall be reviewed, delivered IAW CDRL M002.
Ground Systems Interface Facility (GSIF) (CLIN CPFF) The Contractor shall maintain the PSS-T FoS in the GSIF daily, IAW preventative maintenance checks and services (PMCS) procedures.
The Contractor shall utilize the GSIF system to conduct demonstrations, software checkout, and training as required.
The Contractor shall notify the Government and provide mitigating courses of action within 24 hours of discovering problems affecting PSS-T FoS operations to include, but not limited to: parts ordering, problem tracking, troubleshooting, removal and installation of equipment, and operation of the equipment.
As directed by the Government, the Contractor shall implement corrective actions for problems affecting PSS-T FoS operations.
The Contractor shall maintain a list in a Government furnished information system that has open and resolved problems affecting system health, which shall include date the issue was discovered, when it was resolved, point of contact for the issue, and test report number for problems resolved.
The Contractor shall maintain the GSIF systems in a state of continual readiness.
The Contractor’s GSIF POC shall have an active TS/SCI clearance with a high level of experience in IT in a lab environment. This person shall be required to have PSS-T Large and Medium training.
Program Protection Plan (PPP) (CLIN CPFF) The contractor shall provide technical support in performing a critical functional analysis and CPI assessment on the PSS-T FoS at the direction of the Government. The Government shall provide the contractor with written guidance for implementation of countermeasures to protect CPI. The contractor shall implement Government directed supply chain risk management countermeasures. The contractor shall provide a Program Protection Implementation Plan (PPIP) to the Government within 30 days of receiving countermeasures and provide periodic PPIP status reports to program manager via CDRLs. The contractor shall provide periodic program protection implementation plan (PPIP) updates as directed by the Government IAW CDRL B003). The contractor shall support Government program protection surveys.
The Contractor shall have visibility into the supply chain for critical components. The contractor shall flow this requirement down to all subcontractors.
The Contractor shall conduct software assurance IAW Software Assurance Countermeasures in Program Protection Planning.
Logistics Integrated Product Support Management (CLIN CPFF) The Contractor shall host monthly product support manager (PSM) integrated product team (IPT) meetings.
The Contractor shall provide a PSM IPT meeting agenda IAW CDRL B001.
The Contractor shall provide minutes for each PSM IPT IAW CDRL B002.
Performance Based Logistics Metrics Monitoring and Reporting Requirements (CLIN CPFF) Level 1 Metrics The Contractor shall monitor and report Level 1 metrics IAW CDRL F010.
The Contractor shall perform to the following metrics:
a. Operational availability (Ao): 90%.
b. Fleet mission availability: 75%.
c. Mean time between operational mission failures (MTBOMF): performance standard to be defined in individual TO(s).
d. Depot maintenance workload distribution: 60:40 (Organic/Contract).
e. Depot flow days for depot reset: 180 days for PSS-T Large; 120 days for PSS-T Medium.
f. Mission-impaired capability awaiting parts for materiel: performance standard to be defined in individual TO(s).
Level 2 Metrics The Contractor shall monitor and report Level 2 metrics IAW CDRL F010.
a. Reliability: mean time between failure
b. Mean down time: mean down time
c. General: logistics footprint
d. Maintenance/repair: mean time to repair, repair turnaround time, depot flow days
e. Supply: logistics response time. The amount of time (measured in mean days) that elapses from the time a site establishes a requisition to the time the site receives the materiel that was ordered. When invoked by task order this metric may apply to system repair parts, site (prescribed load list) and hub (authorized stockage list), and other inventory control point’s spares fulfillment.
f. Supply: stock availability. The percentage of requisitions that is filled immediately from stock on-hand. Stock availability = 100 minus (backorders/net demands). When invoked by task order this metric may apply to site (prescribed load list), hub (authorized stockage list), and other inventory control point stock availability.
g. Supply: inventory accuracy. The extent to which the inventory of repair parts or spares corresponds to the required stock levels for those items expressed as a percentage. When invoked by task order this metric may apply to site (prescribed load list), hub (authorized stockage list), and other inventory control points inventory accuracy.
h. Transportation: retrograde ship time
i. Cost: cost per unit of operation (flight hours) Supply Support (CLIN CPFF) (CLIN FFP) The Contractor shall procure all parts and supplies necessary to maintain PSS-T FoS capability.
The Contractor shall maintain an inventory control point at Tobyhanna Army Depot (TYAD).
The Contractor shall utilize DoD FedMall as directed by the PCO for the purpose of requisitioning Defense Logistics Activity managed consumable materiel including: hardware piece-parts; petroleum, oils, and lubricants; compressed gases including nitrogen; industrial cleaning and office/administrative supplies; field/office hygiene and first aid products; and common hand tools.
The Contractor shall maintain, in a Government furnished information management system, complete PSS-T FoS inventory management for all supporting and operation locations.
The Contractor shall determine required stockage levels based on usage rates and reordering times, and shall set reorder points to meet the required minimum Ao.
The Contractor shall provide monthly inventory status reports for all hardware items being procured, stored, shipped, or handled under this contract, IAW CDRL D003.
The Contractor shall establish Sierra Army Depot (SIAD) as a product support provider for the following: equipment maintenance, supply support, materiel inventory activities; kit assembly; demilitarization and disposal; receiving; inspection; material handling equipment support; IUID cataloging, marking, and parent-child relationship building; materiel condition code classification, establishing materiel to an accountable property system of record, stock, store, and issue activities, and shipping assets world-wide.
The Contractor shall track and manage PSS-T FoS and associated items utilizing a Government approved information system. The Contractor shall support the program office in conducting 10% monthly and 100% annually cyclic inventories on all Government property and report the results to the Contracting Officer, COR, and Government Property Administrator IAW the terms and conditions of the contract and DODI 4161.02 and 5000.64. The Contractor shall submit Government property inventory reports IAW CDRL A012.
Provisioning (CLIN CPFF) The Contractor shall maintain provisioning technical data (PTD) to reflect all Government approved ECPs.
The Contractor shall develop and maintain the PTD using PowerLog-J for exportability IAW GEIA-STD-0007-B, GEIA-HB-0007, and TA-HB-0007-1. Exportability is defined as the ability to generate the following reports below free from error.
· LSA-004 Maintenance Allocation Chart (MAC) Report
· LSA-009 Support Items Report
· LSA-014 Training Task List
· LSA-018 Task Inventory Report
· LSA-019 Task Analysis Summary
· LSA-030 Repair Parts and Special Tools List (RPSTL) Report
· LSA-033 PMCS Report
· LSA-036 Provisioning Parts List Report
· LSA-040 Authorization List Report
· LSA-056 Failure Modes, Effects, and Criticality Report
· LSA-072 Test, Measurement, and Diagnostic Equipment Report
· LSA-074 Support Equipment Tools List
· LSA_076 Calibrated Items Report
· LSA-078 Hazardous Materiel Report
· LSA-080 Bill of Materials Report
· LSA-085 Transportability Report
· LSA-155 Recommended Spare Parts List for Spares Acquisition Integrated with Production The Contractor shall load the PTD to the Army’s logistics modernization program (LMP) in MIL-STD-1388-2B format with an accuracy rate of 100 percent for both content and data download as verified by sampling techniques and automated LMP tools.
The Contractor shall use PowerLog-J to export data to legacy MIL-STD-1388-2B and GEIA-STD-0007-B data formats.
The Contractor shall minimize materiel readiness risks and shall develop a Diminishing Manufacturing Sources and Material Shortages (DMSMS) strategy, based on Standardization Directory-22 – DMSMS Guidebook (January 2016), IAW CDRL A008.
The Contractor shall provide a DMSMS health analysis report that will contain data for each PSS-T FoS configuration IAW CDRL P001.
Government-Industry Data Exchange Program (GIDEP) The Contractor shall participate in the GIDEP IAW the GIDEP operations manual, SO300-BT-PRO-010.
The Contractor shall submit information concerning critical or major nonconformance, as defined in Federal Acquisition Regulation 46.407/Defense Federal Acquisition Regulation Supplement 246.407, to the GIDEP information system.
The Contractor shall insert paragraph 3.3.4.6.3 in any subcontract. When so inserted, the word “Contractor” shall be changed to “Subcontractor.” The Contractor shall provide the Subcontractor any GIDEP data which may be pertinent to items of its manufacture and verify that the Subcontractor utilizes any such data. The Contractor shall verify that the Subcontractor utilizes and provides feedback on any GIDEP data that may be pertinent to items of its manufacture.
The Contractor shall submit/provide a GIDEP Alert/Safe-Alert IAW CDRL Q001.
The Contractor shall submit/provide a GIDEP Response IAW CDRL Q002.
Package Handling, Storage, and Transportation (CLIN CPFF) The Contractor shall perform inspections of ISO-configured containers of PSS-T FoS IAW MIL-HDBK-138B, 49CFR 452, and Defense Transportation Regulation Part VI (chapter 604). The Contractor shall update the Joint Container Management System. If container fails convention for safe containers inspection, the Contractor shall notify and obtain disposition instructions from PD Aerostats.
The Contractor shall be responsible for demilitarization and disposal of Government property and to provide the appropriate documentation to the Government.
To achieve successful customs inspections and clearance, the Contractor shall perform aerostat system cleaning and packing.
To achieve successful inspections, the Contractor shall coordinate transportation inspections (joint inspection, weight and balance, etc.)
The Contractor shall provide and coordinate material handling equipment for transportation.
The Contractor shall supply shoring material IAW with Government provided air transportability test loading HAZMAT declaration paperwork.
The Contractor shall resolve frustrated cargo issues to enable continued movement of items through the Government transportation system.
The Contractor shall provide transportation of systems (to include sustainment parts) as directed by the Government.
The Contractor shall conduct tear-down (which includes above user level support at the aerostat sites), packaging, and preparing the system for shipment (which includes labor at the hub to perform concurrent retrograde operations).
The Contractor shall ensure that all parts requiring repair are prepared for shipment to CONUS within 15 calendar days of identification of need for repair.
The Contractor shall pack all items IAW AR 700-15, MIL-STD-2073-1E(1), or best commercial practices to prevent damage during shipment to CONUS and OCONUS locations.
The Contractor shall prepare/package HAZMAT for transport on military airlift IAW Air Force manual 24-204.
The Contractor shall mark and identify items IAW MIL-STD-129R and MIL-STD-130N (use Construct 2). The Contractor shall label all items for OCONUS delivery to the following shipping address unless otherwise directed by the Government:
DoDAAC SW310Z:
W1BG UEF DIST DEPOT TOBYHANNA
Second and Gibbs Street Warehouse 7 Bay 5 Tobyhanna, PA 18466-5059 Mark For: PTD In the event that the Contractor identifies transportation damage when receiving items, the Contractor shall provide SF 364 to the COR via e-mail within five (5) calendar days of receiving the item, IAW MIL-STD-2073-1(E1).
Field and Depot Level Repairs (CLIN CPFF) The Contractor shall provide field and depot level repair services for all CONUS and OCONUS PSS-T FoS to keep systems in fully mission capable (FMC) status. The Contractor shall perform these services IAW applicable PSS-T TMs, Department of the Army TMs, original equipment manufacturer manuals.
The Contractor shall provide electrical repair services at the component and sub-component level to including power source [mobile electric power (MEP) and commercial generators and/or shore/land power] and distribution, frequency conversion, transformers, and three (3) phase electric power.
The Contractor shall provide mechanical repair services to including total system maintenance for man-lifts, forklifts, utility vehicles, environmental control units, and MEP and/or commercial generators.
The Contractor shall provide IT repair services including to operating systems, servers, fiber optic installation and repair, and internet/network routing and switching IAW industry standards.
The Contractor shall provide services for complete system reconstitution from the tether up following an aerostat crash/accident within 72 hours to FMC.
The Contractor shall provide total system maintenance for PSS-T FoS payloads and sensors including MX series, Kestrel System, STARLite and Vista Radars, Unattended Transient Acoustic MASINT Sensor (UTAMS), High Antennas for Radio Communications (HARC), Tactical Common Data Link (TCDL), antennas, master control units and controllers.
The Contractor shall provide repair services for the mobile mooring system including electrical, mechanical, and hydraulic systems to include: complete assembly; disassembly; repair services for trailer; tower; mooring cone; winches; control console; slip rings; mooring cushions and blowers; power data interface; outriggers; tether; winch drum; platform drive assembly; level wind assembly; and sheaves.
The Contractor shall provide repair services for aerostat envelopes including rigging assemblies, temporary and permanent patching, and depot level repairs.
Maintenance Planning and Management (CLIN CPFF)
0. Maintenance Concept The Contractor shall perform two (2) level maintenance, consisting of field level and sustainment level maintenance IAW AR 750-1.
The Contractor shall perform field-level repair services IAW applicable PSS-T FoS TMs.
The Contractor shall provide FSRs and SMEs for repair or modification of PSS-T FoS, subsystems, and line replaceable unit (LRU)/shop replaceable unit.
Maintenance actions required to bring an inoperable system to a FMC shall be accomplished at the field level of maintenance by the crew or maintenance personnel. Field level maintenance is characterized as on-system maintenance for repair and its return to the user and shall consist of replacing LRUs. The LRUs will be evaluated for field repair or returned to the sustainment level of maintenance for repair or disposition. Sustainment level maintenance is characterized as off-system maintenance for repair and return to supply.
The Contractor shall apply field modification procedures and software modification procedures to fielded systems. Examples include, but are not limited to, installing software and installation/de-installation of equipment on ground stations and aerial platforms.
Supportability Analysis The Contractor shall develop, update, maintain, and deliver level of repair analyses (LORA) for PSS-T FoS product baselines as required per specific TO(s). The Contractor shall use the Army’s COMPASS application for developing, updating, maintaining, and producing deliverable LORA reports. The Contractor shall deliver LORA updates IAW CDRL E002.
The Contractor shall develop, update, maintain, and deliver maintenance task analyses (MTA) for PSS-T FoS product baselines IAW CDRL E003 as required per specific TOs.
As required per…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .