LDPE_SOW_For_FBO_Posting_13_Sep19.docx
DOCX document 495 KB Posted
- Attached to
- Modification to Contract (FA8818-18-C-0001) Long Duration Propulsive Evolved Expendable Launch Vehicle (EELV) Secondary Payload Adapter (ESPA) LDPE 3A Federal contract opportunity
- Solicitation number
- FA8818-18-C-0001
About this file
LDPE-3A SOW
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| SYNOPSIS.pdf |
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Statement of Work (SOW) for Long Duration Propulsive Evolved Expendable Launch Vehicle (EELV) Secondary Payload Adapter (ESPA)
(LDPE)
For Official Use Only (FOUO) Distribution C January 12, 2017
| 1. | Scope | 1 |
| 1.1. | Phases | 2 |
| 1.2. | Phase-1 Description | 3 |
| 1.3. | Phase-2 Description | 3 |
| 1.4. | Phase-3 Description | 4 |
| 1.5. | Applicable Documents | 4 |
| 1.6. | Government Furnished Equipment, Information and Data | 8 |
| 2. | Program Management | 10 |
| 2.1. | Program Office: | 10 |
| 2.2. | Program Level Cost/Schedule Management | 10 |
| 2.3. | Contracts and Subcontracts Management | 10 |
| 2.4. | Property Management | 11 |
| 2.5. | Program Security | 11 |
| 2.6. | Cyber Security | 11 |
| 3. | Task/Technical Requirements for the LDPE Platform | 14 |
| 3.1. | Program Technical Reviews | 14 |
| 3.2. | Configuration and Data Management | 14 |
| 3.3. | Systems Engineering | 14 |
| 3.3.1. | Systems Engineering Technical Management | 14 |
| 3.3.2. | System Design and Analysis | 15 |
| 3.3.3. | Technical Budgets | 15 |
| 3.3.4. | Requirements Development and Verification | 15 |
| 3.3.5. | Interface Control Documents | 16 |
| 3.3.6. | Risk Management | 16 |
| 3.3.7. | Flight Assurance | 16 |
| 3.3.8. | Flight Assurance Management | 16 |
| 3.3.9. | Specialty Engineering | 16 |
| 3.3.10. | LDPE article | 17 |
| 3.3.11. | Structures | 17 |
| 3.3.12. | LDPE article Mechancial Design Verification | 18 |
| 3.3.13. | LDPE article Analysis | 18 |
| 3.3.14. | Subsystem Procurement and Fabrication | 18 |
| 3.3.15. | Thermal | 18 |
| 3.3.16. | Power | 19 |
| 3.3.17. | Avionics | 19 |
| 3.3.18. | Avionics Engineering | 19 |
| 3.3.19. | Telemetry, Tracking, and Command | 20 |
| 3.3.20. | Guidance, Navigation, and Control | 20 |
| 3.3.21. | GN&C Subsystem Engineering | 20 |
| 3.3.22. | Propulsion | 21 |
| 3.3.23. | Propulsion Assembly and Test | 21 |
| 3.3.24. | Harness | 21 |
| 3.4. | Flight Software | 22 |
| 3.4.1. | FSW Subsystem Engineering | 22 |
| 3.4.2. | Flight Software Updates for the LDPE article | 23 |
| 3.4.3. | Flight Software Deliverables: | 24 |
| 3.5. | Ground Support Equipment | 24 |
| 3.5.1. | Delivery | 24 |
| 3.5.2. | Hardware-in-the-Loop LDPE Simulator | 24 |
| 3.5.3. | Electronic Ground Support Equipment | 24 |
| 3.6. | Deliverables | 24 |
| 3.6.1. | Hardware Deliverables List: | 24 |
| 3.6.2. | Software Deliverables | 25 |
| 3.6.3. | Contract Data Requirements | 25 |
| 3.7. | Reviews | 27 |
| 3.7.1. | System Requirements Review (SRR) / Preliminary Design Review (PDR) | 27 |
| 3.7.2. | Critical Design Review (CDR) | 27 |
| 3.7.3. | Test Readiness Review (TRR) | 27 |
| 3.8. | I&T Management | 27 |
| 3.9. | Engineering Support to I&T | 28 |
| 3.10. | I&T Facilities | 28 |
| 3.11. | LDPE Bus Assembly, Integration and Test | 28 |
| 3.12. | Close-out | 29 |
| 4. | Payload Integration and Launch Vehicle Integration Support | 30 |
| 4.1. | Payload Accommodation Design, Development, Integration and Test (I&T) | 30 |
| 4.2. | Payload Accommodation Design and Development | 30 |
| 4.3. | Payload I&T Engineering Support | 30 |
| 4.4. | Payload I&T Management | 31 |
| 4.5. | Payload Harness | 31 |
| 4.6. | Integrated Payload/System-Level Tests | 32 |
| 4.7. | Launch Vehicle Integration Support | 33 |
| 4.7.1. | Travel Costs | 33 |
| 4.7.2. | Launch Vehicle Integration Effort | 33 |
| 4.7.3. | Launch Site Operations | 34 |
| 4.8. | Launch Operations Support | 34 |
| 4.8.1. | Launch Support Documentation | 34 |
| 4.8.2. | Meetings | 34 |
| 4.9. | Deliverables | 34 |
| 4.9.1. | Launch Site Hardware Deliverables | 35 |
| 4.9.2. | Contract Data Requirements | 35 |
| 4.10. | Review: | 36 |
| 4.10.1. | Payload Accommodation Design Review | 36 |
| 4.10.2. | Pre-Ship Review | 36 |
| 4.10.3. | Meetings and Reviews | 36 |
| 4.11. | Close-out | 37 |
| 5. | Space Segment Operations | 38 |
| 5.1. | On-Orbit Operations Handbook | 38 |
| 5.2. | Technical Support | 38 |
| 5.3 Information Assurance Engineer | 41 | |
| 5.3.1 Operations Readiness Campaign | 41 | |
| 5.4 Operations | 41 | |
| 5.3. | Location | 42 |
| Annex A: Enabling Requirements for Government Program Contracts Requiring Interface with Aerospace FFRDC Contract Support FOR | 43 | |
| Appendix A: LDPE Technical Requirements | 46 | |
| Appendix B: Minimum Platform to Payload Interface Capability Matrix | 47 | |
| Appendix C: Ground, Handling, and Transportation Requirements | 48 | |
| Appendix D: LDPE Payload Reference Classes | 52 | |
| Appendix E: Payload Interface Guide | 53 | |
| Appendix F: Acronym List | 54 |
Scope This Statement of Work (SOW) defines the effort required by the Contractor for the Long Duration Propulsive ESPA (LDPE) Program. Unless otherwise specified, the Contractor shall provide all personnel, facilities, materials, and services necessary to meet the requirements of this SOW.
LDPE is intended to entail, and support, Mission Risk Class C and D missions; Class B payloads on LDPE would be the exceptions. However, LDPE is also intended to be co-manifested with Class A/B missions for launch, therefore “Do No Harm,” and supporting safety and risk processes shall assume satisfaction of both these standards and levels during all phases (see next section) of work.
LDPE extends Air Force Space Command’s (AFSPC) standard service policy for rideshare, leveraging previous propulsive ESPA development. LDPE will be controlled using Enterprise Ground Services as the baseline for command and control. The effort will include spacecraft payload integration services, and one year of early orbit checkout and operations. The nominal profile for LDPE missions is illustrated in Figures 1.1 and 1.2.
The term “ESPA” (EELV (Evolved Expendable Launch Vehicle) Secondary Payload Adapter) is used to describe a payload adapter class whose development was sponsored and demonstrated by the Air Force Research Laboratory (AFRL); it is not intended to indicate a specific article or vendor. Any equivalent, qualified, payload adapter technologies or structures may be used, but the ESPA is the government’s reference instance.
Figure 1.1 -- LDPE Launch to Orbit
Figure 1.2 -- LDPE On-Orbit Operations Phases There are three major phases of effort defined for the LDPE: Phase-1, LDPE Platform Assembly, Integration, and Test; Phase-2, Payload Integration & Test (I&T), and Launch Vehicle Integration Support & Launch Support; and Phase-3, Early Orbit Checkout and On-Orbit Support. The work in each of the three activities is not entirely serial; information or effort may be required from later phases for satisfactory completion of work in earlier phases. The complete effort also involves system-level management, engineering, and other associated support activities across all phases.
Table 1.1. Contract Structure
| Vehicle |
| Phase |
| Activities |
| LDPE Vehicle #1 |
| Phase-1 |
| Assemble, Integrate, Test and Deliver |
| Basic |
| Phase-2 |
| Payload I&T, Launch I&T Support and Launch Support for LDPE #1 |
| Option |
| Phase-3 |
| Early Orbit Checkout Support and On-Orbit Support |
| Option |
| LDPE Vehicle #2 |
| Phase-1 |
| Assemble, Integrate, Test and Deliver |
| Option |
| Phase-2 |
| Payload I&T, Launch I&T Support and Launch Support for LDPE #2 |
| Option |
| Phase-3 |
| Early Orbit Checkout Support and On-Orbit Support |
| Option |
| LDPE Vehicle #3 |
| Phase-1 |
| Assemble, Integrate, Test and Deliver |
| Option |
| Phase-2 |
| Payload I&T, Launch I&T Support and Launch Support for LDPE #3 |
| Option |
| Phase-3 |
| Early Orbit Checkout Support and On-Orbit Support |
| Option |
| LDPE Vehicle #3A |
| Phase-1 |
| Assemble, Integrate, Test and Deliver |
| Option |
| Phase-2 |
| Payload I&T, Launch I&T Support and Launch Support for LDPE #3A |
| Option |
| Phase-3 |
| Early Orbit Checkout Support and On-Orbit Support |
| Option |
Phase-1 Description LDPE Assembly, Integration & Test (Phase-1) includes any design and development required for satisfaction of SOW requirements, followed by assembly, integration and test of the LDPE article, and culminates in a platform ready for payload/s integration at the system level. Successful completion of a Bus Level-Baseline Function Test (BL-BFT) demonstrates that the LDPE is fully functional and is ready for environmental testing and/or the integration of payload/s. Details of work to be accomplished in Phase-1 are detailed in Section 3. Major milestones in this phase are:
Kickoff Design reviews, as required for verification per SOW section 3 (includes documentation) -- contractor led; govt as observers only Bus-Level Test Readiness Review (BL-TRR) -- govt acceptance of test proceedures & levels consistent with CDRL A/B/C003 Bus Level-Baseline Functional Test (BL-BFT) complete -- govt observation of article test performance to SOW Bus I&T complete -- govt acceptance & readiness for auxillary payload integration Phase-2 Description Payload Integration & Test and Launch Vehicle Integration & Test Support (Phase-2) includes the payload/s I&T phases for both separable and non-separable auxillary payloads; successful full system level testing (system functional test, environmental test, compatibility testing, ground control function testing, etc.); launch vehicle interface development; and launch vehicle integration and launch support for the LDPE mission. Payload processing may drive TS or above program levels. Successful completion results in a fully operational LDPE, including all payloads, that meet all requirements. Details of work to be accomplished in Phase-2 are described in Section 4. Major milestones in this phase are:
Payload ICDs delivered Payloads delivered Payload I&T complete System Level-Baseline Functional Test (SL-BFT) System Level-Test Readiness Review (SL-TRR) System Level Test complete Pre-Ship Review (PSR) Launch Integration support Launch support (pre-launch) Launch
Phase-3 Description Early Orbit Checkout and On-Orbit Support includes mission planning development, ground system development, exercise support, rehearsal support, Launch & Early Orbit (LEO) support and on-orbit operations support. Payload Processing may drive TS or above program levels. Work to be accomplished in Phase-3 are detailed in Section 5. Major milestones in this phase are:
Mission Planning Tool Ground System Refinement for Mission Operations (MMSOC 2.1 compliant) On-Orbit Handbook Complete Development of contingency procedures LDPE Launch and Early Orbit (LEO) Checkout Complete Transition to Government Operators: Launch + 120 days Final Report - End Item Data Package (EIDP) Submittal: End Technical PoP + 74 days Applicable Documents These documents shall be considered included in the SOW, by reference; compliance to full or tailored levels, as specified in Table 1.5, is required for acceptance.
Table 1.5 Applicable Documents
| Document |
| Title |
| Date |
| Type |
| Comments/Tailoring |
| MMSOC GSA |
| Multi-Mission Satellite Operation Center (MMSOC) Service Interface Specification Document |
| 2016 |
| Compliance |
| Full Compliance; tailoring within allowed parameters to support mission specific requirements – Submit tailored approach for Government approval. Final version NLT CDR, iterations preferred. |
| AFPAM 63-113 |
| Program Protection Planning for Life Cycle Management |
| 2013 |
| Compliance |
| Tailoring Authorized - Submit tailored approach for Government approval. At a minimum, must include Critical Program Information (CPI), Critical Components (CC), and Program Protection Survey (PPS) approaches. |
| ASTM E 1548-2009 |
| Standard Practice for Preparation of Aerospace Contamination Control Plans |
| 2009 |
| Compliance |
| Full compliance requires tailoring – submit tailored approach for Government approval. |
| DOD 4145.26-M |
| DOD Contractor's Safety Manual for Ammunition and Explosives. |
| 2008 |
| Compliance |
| Requirement specified in DFARS clauses 252.223-7002 and 252.223-7003 |
| DoD 5220-22M |
| National Industrial Security Program Operating Manual |
| 2016 |
| Compliance |
| Full Compliance |
| DoDI 8510.01 |
| Risk Management Framework (RMF) for DoD Information Technology (IT) |
| 2014 |
| Compliance |
| Full Compliance, submit tailored approach for Government approval |
| EELV SIS Rev. B |
| Launch Systems Directorate Evolved Expendable Launch Vehicle Standard Interface Specification, Rev B |
| 2016 |
| Compliance |
| Full Compliance for all medium EELV configurations (i.e., excludes heavy) |
| EELV RUG |
| Evolved Expendable Launch Vehicle Rideshare User’s Guide |
| 2016 |
| Reference |
| EIA 649-1 |
| Configuration Management Requirements for Defense Contracts |
| 2015 |
| Compliance |
| Full Compliance IAW SMC-T-007 |
| ANSI/EIA 748-C |
| Earned Value Management Systems |
| 2013 |
| Compliance |
| Tailoring Authorized - Submit tailored approach for Government approval (for CPFF CLINs only) |
| IEEE-15288.2 |
| Technical Reviews & Audits for Systems, Equipment and Computer Software |
| 2014 |
| Compliance |
| Compliance requires tailoring to need – mandatory contractor documentation of integrated tailoring approach and coverage consistent with mission assurance (as described in SMC-G-007). |
| IEEE-15288.1 |
| Application of Systems Engineering on Defense Programs |
| 2014 |
| Compliance |
| Compliance requires tailoring to mission need -- Submit tailored approach for Government approval |
| MIL-STD-882E |
| System Safety Program Requirements |
| 2012 |
| Compliance |
| Compliance requires tailoring to need – however, Section 4 may not be tailored without MDA and CAE authorization. Submit proposed contractor tailoring approach for Government Program Office and SMC Safety approval. |
| MIL-STD-461F |
| Requirements for the Control of Electromagnetic Interference Characteristics of Subsystems and Equipment, Department of Defense |
| 2007 |
| Compliance |
| Full Compliance IAW SMC-S-008 |
| MIL-STD-464A |
| Electromagnetic Environmental Effects Requirements for Systems, Department of Defense |
| 2002 |
| Compliance |
| Full Compliance IAW SMC-S-008 |
| NAS 411 |
| Hazardous Materials Management Program |
| 2013 |
| Compliance |
| Full Compliance |
| NASA-STD-8719.14A (with Change 1) |
| Process for Limiting Orbital Debris |
| 2012 |
| Compliance |
| Full Compliance IAW SMC-T-003 and SMCI 62-110 |
| SAE AS9100 |
| Quality Systems - Aerospace - Model for Quality Assurance in Design, Development, Production, Installation and Servicing |
| 2009 |
| Compliance |
| Full Compliance IAW SMC-S-003 (tailored) |
| AFI 63-101/20-101 |
| Integrated Life Cycle Management |
| 2015 |
| Compliance |
| Compliance with respect to Paragraphs 3.5 and 3.6. |
| AFI 91-217 |
| Space Safety and Mishap Prevention Program |
| 2014 |
| Compliance |
| The contractor is responsible for supporting program office efforts to perform space debris and range safety analysis. Contractor data will be added to the Space Debris Analysis Report and End of Life Plan (SDAR/EOLP). The contractor’s design will be informed by End-of-Life and passivation requirments. The government is responsible for mission design and the associated collision analysis and risks. |
| SMCI 62-110 |
| Space Debris Mitigation Management |
| 2014 |
| Compliance |
| Full Compliance |
| SMC-S-003 |
| Quality Space and Launch Requirements Addendum to AS9100C |
| 2015 |
| Compliance |
| Full Compliance, requires tailoring to need. Submit tailored approach for Government approval |
| SMC-S-008 |
| Electromagnetic Compatability Requirements for Space Equipment and Systems |
| 2008 |
| Compliance |
| Full Compliance requires tailoring – Submit tailored approach for Government approval |
| SMC-S-009 |
| Parts, Materials, and Processes control program for space vehicles |
| 2013 |
| Compliance |
| Full Compliance requires tailoring – Submit tailored approach for Government approval |
| SMC-S-010 |
| Technical Requirements For Electronic Parts, Materials, And Processes Used In Space Vehicles |
| 2013 |
| Compliance |
| Full Compliance requires tailoring – Submit tailored approach for Government approval |
| SMC-S-012 |
| Software Development |
| 2015 |
| Compliance |
| Full Compliance |
| SMC-S-013 |
| Reliability Program for Space Systems |
| 2008 |
| Compliance |
| Tailoring authorized – Submit tailored approach for Government approval |
| SMC-S-015 |
| End-of-Life Disposal of Satellites in Geosynchronous Altitude |
| 2010 |
| Compliance |
| Full Compliance |
| SMC-S-016 |
| Test Requirements for Launch, Upper-Stage and Space Vehicles |
| 2014 |
| Compliance |
| Compliance requires tailoring to need – Submit tailored approach for Government approval |
| SMC-T-003 |
| SMC Tailoring of NASA-STD-8719.14 |
| 2010 |
| Compliance |
| Full Compliance |
| SMC-T-004 |
| Tailoring Instructions For MIL-STD-882E |
| 2013 |
| Compliance |
| Compliance requires tailoring to need – mandatory contractor documentation of integrated tailoring approach and coverage consistent with mission assurance (as described in SMC-G-007). |
| SMC-T-005 |
| SMC Risk Management Supplement to IEEE 15288.1 |
| 2015 |
| Compliance |
| Compliance requires tailoring to need – mandatory contractor documentation of integrated tailoring approach and coverage consistent with mission assurance (as described in SMC-G-007). |
| SMC-T-006 |
| Specialty Engineering Supplement to IEEE 15288.1 |
| 2015 |
| Compliance |
| Compliance requires tailoring to need – mandatory contractor documentation of integrated tailoring approach and coverage consistent with mission assurance (as described in SMC-G-007). |
| SMC-T-007 |
| Tailoring of EIA 649-1 |
| 2015 |
| Compliance |
| Full Compliance |
| SMC-G-007 |
| Mission Assurance Tailoring Guide |
| 2013 |
| Reference |
| SMC-G-1202 |
| Space Flight Worthiness Criteria (SFWC) |
| 2009 |
| Reference |
Government Furnished Equipment, Information and Data Table 1.6 Government Furnished Equipment, Information and Data
| Item |
| When Provided |
| Duration |
| Payload Input to ICDs |
| ILC - 11 months (threshold) |
ILC-15 months (objective) N/A
| Launch Vehicle ICD |
| ATP + 6 months |
| N/A |
Frequency (AFSCN) Allocation Authority to Operate
ATP+6 months ILC-1 month
Mission Life Mission Life
COMSEC
Unit Test Keys Flight keys
ATP+12 months ATP+12 months ILC-1 month
Permanent Through ILC Mission Life
| Energetic Charged Particle instrument(s) (ECP) |
| ILC -12 months |
| Mission Life |
| Security Classification Guide |
| ATP+3 months |
| Mission Life |
| Separation Systems |
| ILC-6 months |
| Permanent |
Program Management The Contractor shall provide the technical and management expertise necessary to plan and direct the development of the LDPE through program completion to include: management and business operations planning, cost and schedule control, administration of travel, property management, contracts and subcontracts management, weekly and monthly project status, and administrative support.
Program Office:
The Contractor shall manage, control, and approve all work performed under the contract to accomplish the requirements of this SOW in support of the program objectives. This task covers the support required for the Program Manager to monitor program task execution, track program and Government property, track program costs, and monitor the program schedule throughout the period of performance of the contract. In order to convey the management philosophy and codify business rhythms, the Contractor shall prepare and administer a Program Management Plan (PMP) (CDRL A/B/C/D026) and Project Planning Chart. The Project Planning Chart shall be delivered at Basic ATP + 15 days. An updated Project Planning Chart shall be delivered at major reviews.
Program Level Cost/Schedule Management The Contractor shall conduct program finance, scheduling support, and reporting activities to meet all program technical and scope requirements. The Contractor shall manage and control Program finances in accordance with government approved tailoring of ANSI/EIA 748-C compliant Contractor policies. Effort in this element shall include support of the following Contractor Data Requirements List (CDRL) items:
Technical Status Report (Monthly) (CDRL A/B/C/D001) Project Planning Chart (CDRL A/B/C005) Integrated Master Schedule (IMS) (CDRL A018, Phase 1) Man-Hours Expenditure Chart (Monthly) (CDRL A028, Phase 1) Integrated Program Management Report (IPMR) (CDRL B/C/D002, Phases 2 & 3) Contract Invoicing and Payment Report (CDRL B/C/D029, Phases 2 & 3) Contracts and Subcontracts Management The Contractor shall conduct contract administration, subcontracts administration, and export control activities in accordance with internal company procedures and contractually required FAR clauses throughout the contract to include the following activities:
Contract and subcontract management and administration activities to support the execution of the contract.
Interaction with the Government Contracting Officer (CO), subcontractors (executive management, program management, and technical support personnel).
Flow down of direction and communication with subcontractors.
Tracking of subcontractor performance against contract requirements, continuing contract administration, management, and direction throughout the program.
Patent Reports.
Property Management The Contractor shall manage property associated with the program in accordance with Contractor policy for the storage and identification of Government property. The Property Manager shall be the primary point of contact with the Government Property Manager. In addition, the Contractor shall provide a Unique Identification Designator (UID) for all deliverable Government property. The Contractor shall monitor and report all Government property through the annual Government Property Physical Inventory Count or Custodial Balance Report (CDRL A/B/C009).
Program Security The Contractor shall develop a Program Protection Implementation Plan (CDRL A/B/C008) and implement and manage the security processes necessary to protect LDPE Program material per the SCG. If required by the classification of the program, or secondary payloads, hardware, or software, the contractor shall provide any required facilities and procedures for protecting, processing and handling Unclassified (including ITAR) up to TS/SCI items or data.
Cyber Security Cyber Security is a significant concern to the Government, therefore the following requirements shall be incorporated with other program data and program security processes to ensure the security of the system and data concerning the system.
The contractor shall document their cybersecurity process in the Systems Engineering Management Plan (SEMP) (Contract Data Requirements List (CDRL A/B/C036).
The contractor shall participate in the Government-led System Security Working Group (SSWG) (or Cybersecurity IPT, Systems Engineering IPT, etc.).
The contractor shall integrate cybersecurity activities into the overall systems engineering and design efforts. The contractor shall incorporate cybersecurity into all lifecycle activities for which the contractor is responsible. The contractor shall include cybersecurity requirements and artifacts within systems engineering and design contract data requirements list (CDRL) items.
The contractor shall ensure that cybersecurity considerations are included in operational and maintenance documentation.
The contractor shall perform cybersecurity trade-offs of design concepts and potential alternative countermeasures to minimize vulnerabilities, weaknesses, and implementation costs.
The contractor shall conduct SSE analysis to identify cybersecurity risks the system may induce upon the environment (e.g., enterprise) or may inherit (e.g., trust chains) and shall include these risks in their overall risk management processes.
The contractor shall identify any cybersecurity vulnerability or limitation induced by policy, law, regulation, or other governance.
The contractor shall ensure training materials, technical manuals, and other technical data developed for the program address any security controls (e.g., management, operational, technical) or requirements that affect system operation, maintenance, repair, or other support activities.
The contractor shall consider cybersecurity requirements in their design and development processes to minimize the threat exposure of the system Only store sensitive, non-public DoD information on contractor information systems that are in compliance with DoD Instruction 8582.01;
Encrypt sensitive, non-public DoD information on portable electronic devices (e.g. laptops, etc.) and/or removable storage media (e.g. CD, DVD, etc.);
The contractor shall conduct analysis for any COTS and/or non-developmental items (NDI) to ensure that they are appropriately configured, software/hardware/firmware is controlled, and any unique risks they pose are mitigated. Protect system design-related documents and operational data at least to the level provided by Secure Sockets Layer (SSL)/Transport Security Layer (TSL)-protected web site connections with certificate and or userid/password-based access controls. In either case, the certificates used by the Contractor for these protections shall be DoD or Intelligence Community (IC) approved Public Key Infrastructure (PKI) certificates issued by a DoD approved External Certification Authority (ECA) and shall make use of at least 128-bit encryption; and Advise the CO and/or COR of any unauthorized release of such information.
Contractor Furnished Equipment (CFE) employed for remote access to a Government network must meet or exceed equivalent Government Furnished Equipment (GFE) cybersecurity computing requirements. CFE will not be authorized to connect with GFE via Virtual Private Network (VPN) or direct connection. Additionally, CFE will not be used to accomplish GFE system administration duties.
The Contractor shall report, at a minimum, the information detailed within 252.204-7012 as well as under the Incident Report Content heading below, within 72 hours of discovery of any cyber incident to the Department of Defense via (http://dibnet.dod.mil/). In addition, the contractor shall also notify the COR and cognizant US Government ISSM within 4 hours of any suspected cyber intrusion event even if full details are not yet available and provide follow-on detailed reporting within 24 hours per direction from either the COR or US Government ISSM:
A cyber intrusion event appearing to be an advanced persistent threat.
A cyber intrusion event involving possible data exfiltration, manipulation or unauthorized disclosure of any DOD information resident on or transiting the contractor's (or its subcontractors') unclassified information systems or networks;
Intrusion activities that allow unauthorized access to the Contractor's unclassified information system(s) or networks(s) on which DOD information is resident or transiting.
The Contractor shall design to requirements and evaluate compliance with security controls IAW CNSSI-1253 and National Institute of Standards and Technology (NIST) SP 800-53 to support Assessment and Accreditation (A&A). The Contractor shall implement required security functions IAW DoDI 8500.01 Cybersecurity, ICD 503 IC Security, and DoDI 8510.01 Risk Management Framework (RMF) for DoD Information Technology (IT). The Contractor shall conduct Security Test and Evaluation (ST&E) to verify the NIST security controls captured in the LDPE controls list to establish a Cybersecurity baseline prior to DT&E. The Contractor shall conduct A&A activities, including application of NIST security controls and development of A&A artifacts, for all hardware and software delivered to the Government under this LDPE project. The Contractor shall provide evidence of implementation of all security controls assigned to the Contractor in the RMF A&A Package which will be evaluated by the Authorizing Official (AO) resulting in an Interim Authorization To Test (IATT), an Interim Authorization To Operate (IATO), and an Authority To Operate (ATO) [CDRL A040]. The Contractor shall support A&A efforts with key stakeholders, including the AD Information Systems Security Manager (ISSM) and the PMO security team.
Previous LDPE ATO and program security documents may be provided to help with RMF and program security documentation.
The Contractor shall comply with the SMC/AD Security Classification Guide (SCG) and the LDPE Program Protection Plan (PPP). The Contractor shall develop and deliver the LDPE System Security Plan (SSP). The Contractor shall ensure the delivered system implements and is compliant with all technical security controls assigned to the Contractor in the LDPE Payload to Port Interface Control Document (PPICD). The Contractor shall ensure the SSP includes plans for Communications Security (COMSEC), Key Management, and Program Protection Implementation. The Contractor shall ensure the SSP captures interfaces to NSA-controlled components and include procedures for handling and controlling NSA keys [CDRL A020].The Contractor shall coordinate the security plans and security coverage with the ISSM and representatives of the PMO, and integrate security testing requirements.
Task/Technical Requirements for the LDPE Platform Program Technical Reviews The Contractor shall demonstrate completed exit criteria in their delivered materials for the reviews identified in Section 3.7 and in accordance with cited compliance document and good industry practice. For CDR and pre-test reviews, the Contractor shall provide meeting venue and presentation material per CDRL A003. Milestone and pre-test reviews can be held as a telecom, VTC or other form of meeting depending on the Governments discretion. Draft presentation data for all major milestone reviews shall be submitted no later than 10 business days before each review.
In the course of this contract, the government will have occasions for more rapid reporting and/or insight into the contractor’s processes. Yet the government does not want to overburden the contractor with additional formal meetings or reporting. For those instances, the government will send their trusted technical representatives to visit the contractor’s facility(ies) for real time in situ observations and data review. These are neither official meetings nor are there CDRL requirements. It should be understood that no preplanning or special arrangements will be required from the contractor except to arrange access and allot minimal office space for the visitors’ administrative purposes. The government’s technical representatives shall be granted access to the contractor’s data source, the freedom to attend the contractor’s technical discussions and permission to interface with the contractor’s engineers. Occasions in which these visits are most prevalent will be during major systems testing and critical anomaly resolutions.
Configuration and Data Management The Contractor shall conduct all activities required to control, maintain and audit the system and component design. This effort includes application of Contractor Configuration Management Standards in accordance with EIA-649-1 and SMC-T-007 (tailored) for the generation and control of all contractor generated program documentation to ensure all internal and external program participants are working with the proper data. The Contractor shall provide Data Management to facilitate coordination and submission of all Contract Data Requirements List (CDRL) items as detailed in the RFP.
Systems Engineering The Contractor shall perform the necessary systems engineering required to ensure a successful program execution from program ATP through Phase-1, Phase-2, and Phase-3 in accordance with IEEE 15288.1 and 15288.2 (both tailored) and DoDI 8510.01 (tailored). The Contractor shall provide cost and schedule tracking for systems engineering activities.
Systems Engineering Technical Management The Contractor shall provide systems engineering management across all work for this contract from ATP through Phase-1, Phase-2, and Phase-3.
Activities shall include:
Manage system-level design and analysis.
Manage and support the technical budget tracking and allocation process.
Manage requirements development and verification.
Manage ICD development.
Identify risks, perform risk analysis, and provide risk mitigation plans.
Manage development of platform's fault protection system.
Provide support for monthly status and performance reports.
Support design reviews, to include action item resolution.
Perform cost and schedule management for systems engineering efforts.
Support Program Office System Safety Group (SSG) meetings and Wording Group (SSWG) meetings, to include action item resolution.
System Design and Analysis The Contractor shall deliver the detailed design of the Long Duration Propulsive ESPA (LDPE) article that meets all requirements in the LDPE SOW. System-level Activities shall include the development of a LDPE platform functional block diagram and of interface specification(s) for separating and non-seperating auxillary payloads, and for the launch vehicle and primary payload (to include accomodations). The Contractor shall support the government's mission planning activities leading up to selection of auxiliary payloads for the LDPE; e.g. LDPE hosting capabilities and limitations for payloads under consideration, integration issues, and considerations of payload-unique on-orbit checkout & operations.
Technical Budgets The contractor shall develop technical budgets, tracking them throughout the program and performing allocation to the various subsystems.
Budgets shall include:
Mass budget Power budget Thermal budget Delta-V budget Link budget Payload resource budget Requirements Development and Verification The Contractor shall perform requirements analysis, definition, and verification. This effort includes the activity of converting the program system objectives into comprehensive system requirements, and then decomposing and allocating these requirements into subsystem level requirements. The Contractor shall document these requirements in a Recurring Hardware Requirements Verification Document (CDRL A010) and conduct a Systems Requirements Review (SRR). The Contractor shall provide an Assembly, Integration and Test Plan that outlines the methodology, approach and verification/validation process to be used to demonstrate all requirements are met (CDRL A006). The Contractor shall provide a Comprehensive Functional and Performance Test Report, to include requirements traceability and verification (CDRL A012 and SMC-S-016 (per approved tailoring). The contractor shall develop and maintain a Requirements Verification Matrix to demonstrate at each major review that the system meets all requirements (CDRL A010).
Interface Control Documents The Contractor shall develop external Interface Control Documents (ICDs) where no existing ICD exists, or shall develop ICDs that comply with existing ICDs specified by the government. The drafts shall be delivered at CDR + 5 days and final versions prior to hardware delivery (CDRL A013). The Contractor shall perform external and internal interface management throughout Phase-1 and any exercised options.
Risk Management Contractor shall perform risk management in accordance with SMC-T-005 (tailored) to include risk identification, risk mitigation plan development, risk status tracking to burn down all risks, and residual mishap risk reporting to the Government authorities referenced by MIL-STD-882E (i.e. as defined by DoDI 5000.02) prior to hardware delivery. The contractor shall provide Government Purpose access rights to the contractor’s risk management environment and MIL-STD-882E compliant Hazard Tracking System to the government program management team.
Flight Assurance The Contractor shall perform the necessary flight assurance activities to ensure successful design, and subsystem manufacture activities.
Flight Assurance Management The Contractor shall plan, develop, manage, and review the design assurance, quality assurance, and configuration management activities for the LDPE program.
Specialty Engineering The Contractor shall provide reliability in accordance with SMC-S-013 (tailored) and safety engineering activities in accordance with Mil-Std-882E and SMC-T-004 (tailored) for the LDPE program in order to meet the RFP requirements and objectives.
The Contractor shall perform EMI/EMC analysis IAW SMC-S-008 with approved tailoring.
The Contractor shall perform contamination control analysis IAW ASTM E 1548-2009 (tailored).
The Contractor shall provide parts and materials engineering activities for the LDPE Program in order to meet the program objectives. Specific Activities shall include: review lists of materials, parts, and processes IAW SMC-S-009 and SMC-S-010 (both tailored).
The Contractor shall identify parts, materials, or processes that pose a risk to flight assurance.
The Contractor shall provide an initial list of expected long lead procurement items at the kickoff meeting and shall update the list at PDR, to include item descriptions, lead times, costs and when item will be needed in LDPE development.
The Contractor shall provide quality engineering activities in accordance with SMC-S-003, as tailored to leverage internal company policy for quality management/audit of component subcontractors and/or vendors and the monitoring of workmanship within the Contractor facilities.
The Contractor shall provide (1) Critical Program Information (CPI) and Critical Components (CC) and (2) cooperate with Program Protection Survey (PPS) for system security.
The Contractor must identify safety-critical components, systems, or hardware (as defined by MIL-STD-882E), and software interfaces with those components. The contractor must test and verify the safety critical hardware and software for formal safety risk acceptance by the Air Force risk acceptance authorities defined by MIL-STD-882E (i.e. as defined by DoDI 5000.02).
The Contractor shall not preclude either horizontal or vertical integration of the SV to the LV, to include transportation of the mated assembly to the launch pad.
LDPE article The Contractor shall perform design, analysis, build, assembly, and test activities required to deliver a LDPE article and the components and subsystems required to meet LDPE program requirements from ATP through BL-BFT and through Phase-2.
Structures The Contractor shall conduct mechanical design and analysis and develop the mechanical systems required for LDPE compliance with SOW requirements, and through Phase-2.
LDPE article Mechancial Design Verification The Contractor shall verify mechanical design of the LDPE. Activities shall include documentation and verification of final design, detailed drawings, installation drawings, and interface control drawings. The Contractor shall provide a detailed mechanical layout and packaging to include field of view analysis.
LDPE article Analysis The contractor shall demonstrate mechanical analysis of the LDPE.
Activities shall include:
Completion of detailed structural analysis, which will include the following as required to support verification to SOW, secondary payloads and integration with primary launch vehicle and primary payload (including adapters and separation systems specified):
Preliminary Primary Structural Analysis Final Primary Structural Analysis Preliminary Secondary Structural Analysis Final Secondary Structural Analysis Finite Element Model (FEM) Development PCLA Support (Preliminary Coupled Loads Analysis) FCLA Support (Final Coupled Loads Analysis) Component Mounting Analysis Deployed Modal Analysis Stowed Modal Analysis Develop correlated modal model Subsystem Procurement and Fabrication The Contractor shall demonstrate detailed component requirements and procure all the subsystem's components in accordance with the Hardware Deliverables List. The Contractor shall fabricate, assemble, and test the LDPE structure. The Contractor shall develop test plans for deliverable component level tests, conduct and/or verify and validate component level tests, and generate reports.
Thermal The Contractor shall provide system and subsystem thermal requirements definition, detailed system/subsystem design, and detailed system/subsystem documentation for the LDPE from ATP through BL-BFT and through Phase-2.
Activities shall include:
Development of system, subsystem, payload interface, and component thermal requirements.
Completion of detailed thermal analysis.
Detail drawing development.
Installation drawing development.
Procurement and fabrication of all thermal components.
Completion of test plans for component level tests.
Procure the Thermal Subsystem components IAW the Hardware Deliverables List.
Support of Design and Test Reviews.
Power The Contractor shall provide Electrical Power Subsystem (EPS) engineering support to, analysis, integration and test planning, and any specialty engineering work relative to the subsystem for the LDPE from ATP through BL-BFT and through Phase-2.
Activities shall include:
Development of component requirements.
Development of detailed block diagrams and schematics.
Development of detailed power budget.
Procure the Electrical Power Subsystem components IAW the Hardware Deliverables List.
Support of Design and Test Reviews.
Development of a Charge Control Unit (CCU) for up to 12 separable payloads 2 per port (not required during launch and ascent).
Avionics The Contractor shall provide technical and management expertise for the effective planning and coordination of resources necessary for satisfaction of SOW requirements of the delivered LDPE avionics subsystem components and system from ATP through BL-BFT.
Avionics Engineering The Contractor shall provide engineering support to requirements allocation, analysis, integration and test planning, and specialty engineering work relative to the Command and Data Handling (C&DH) Avionics subsystem through BFT and through Phase-2.
Activities shall include:
Technical requirements allocation.
Electrical System Analysis.
I&T planning.
Development of avionics and C&DH specifications.
Preparation of electrical ICDs.
Support development of EGSE for EDU and FM testing.
Electrical harness development.
Procure the Avionics Subsystem components.
Oversee fabrication, assembly, and testing of the LDPE avionics unit.
Providing and managing the required payload 1/0 resources.
Support for CDRLS and monthly reports.
Support of Design Reviews.
Telemetry, Tracking, and Command The Contractor shall provide the technical and management expertise for the effective planning and coordination of resources necessary for satisfaction of SOW requirements of the LDPE Telemetry, Tracking, and Command (TT&C) subsystem components and system. The Contractor shall provide engineering support for work related to the TT&C system/subsystem from ATP through BL-BFT and through Phase-2.
Activities shall include development of design notes, analyses, and technical support for the following :
Ground System Development for Mission Operations (MMSOC 2.1 compliant).
LDPE to mission operations Ground Station Compatibility Test.
Initial and final link budgets.
Space-to-ground ICD inputs.
Frequency management application support.
Development of component requirements.
Development of detailed design for the TT&C subsystem.
Development of detailed block diagrams and schematics.
Procure the TT&C Subsystem components IAW the Hardware Deliverables List.
Analysis and testing of omni-directional antennas and HGA.
Completion of test plans for component level tests.
Conduct component level tests and generate reports.
Support for CDRLS and monthly reports.
Support for design reviews.
Draft and support development of all required frequency management documentation.
Develop a COMSEC Management Plan (CDRL A020).
Guidance, Navigation, and Control The Contractor shall provide GN&C system requirements definition, detailed system design, and detailed system documentation for LDPE from ATP through BL-BFT and through Phase-2.
GN&C Subsystem Engineering The Contractor shall develop the technical design and architecture of the GN&C system, including specification development and requirements verification. Activities shall include development of component requirements, detailed block diagrams and schematics, analysis and simulation of the GN&C algorithms, technical budget generation, and attitude performance analysis.
The Contractor shall develop the GN&C FSW architecture to be compliant with the platform's specifications.
The Contractor shall generate FSW documentation and test the GN&C FSW at the component level, leveraging existing verified GN&C software and models.
The Contractor shall develop mission scenarios and test the integrated system/subsystem software in evaluation environments for functional verification.
The Contractor shall integrate the GN&C FSW and perform processor in the loop (PITL) testing against defined verification scenarios.
The Contractor shall document the results of the tests.
Propulsion The Contractor shall provide propulsion system/subsystem requirements definition, detailed system design, and detailed system documentation for LDPE from ATP through BL-BFT and through Phase-2.
Activities shall include:
Procure the propulsion system components.
Completion of test plans for all system, subsystem and component level tests.
Conduct component level tests and generate reports.
Conduct system level tests and generate reports.
Technical interchange with propulsion vendors and adjudication of vendor End Item Data Packages.
Support for CDRLs and monthly reports.
Support of Design Reviews.
Propulsion Assembly and Test The Contractor shall provide Propulsion Assembly and Test activities including the build-up of the propulsion system and all testing to be completed prior to delivery. The activity shall include development of work instructions for the manufacture of the propulsion system.
Harness The Contractor shall provide Harness Subsystem engineering support to component requirements definition, analysis, and I&T planning, specialty engineering work relative to the component, and detailed component documentation for LDPE from ATP through BL-BFT.
Activities shall include:
Development and fabrication of a payload harness interface.
Procure the platform harness subsystem materials.
Fabrication and assembly of the platform harness.
Completion of test plans for all platform subsystem and component level tests.
Conduct component level tests and generate reports.
Support for monthly status and performance reports.
Support of Design Reviews.
Development and fabrication of payload harnesses if Phase-2 is exercised Flight Software The Contractor shall provide the technical activities required for developing the flight software in order to meet all LDPE mission objectives and requirements. The Contractor shall perform the flight software development effort, provide configuration and data management of the software deliverables and provide software verification and validation of the integrated software system.
FSW Subsystem Engineering The Contractor shall provide technical management in support of all software development.
The Contractor shall support milestone reviews: CDR, TRR and PSR.
The Contractor shall perform software configuration management and software quality assurance.
The Contractor shall provide inputs to CDRLs and develop a Software Requirement Specification (CDRL A015), Software Development Plan, Software Design Document, Software Test Plan, and Software Test Report.
The Contractor shall design, implement, and test fault detection and correction software and mission sequencing.
The Contractor shall develop software design documentation and a Mission Ground Database.
The Contractor shall develop and maintain a Command and Telemetry List (CDRL A011).
The Contractor shall develop and maintain a Mission Simulation environment (MSIM) to be used in the development, test, verification and validation of the LDPE flight software. The MSIM is a means to simulate the LDPE system and its on orbit operations. The system simulation will be used to establish and verify command sequencing, operations procedures, experiment planning and system performance. Additionally, the system simulation will be used to support training of operations personnel in the execution of nominal activities as well as anomaly and fault response conditions and to validate and verify any flight software modifications required during on-orbit operations. In order to support these critical tasks the following requirements shall be met:
1.1.1.1.1. PC based, preferably Linux, or Windows, operating system
1.1.1.1.2. Accurate representation of LDPE flight system (e.g., processor model, memory, memory management, command functions, control functions, etc.)
1.1.1.1.3. Capable of performing flight software development
1.1.1.1.4. Capable of performing flight software validation and verification
1.1.1.1.5. Ability to run at least 1X real-time operation (threshold), 4X real-time operations (objective)
1.1.1.1.6. Simulation of core bus functionality is required
1.1.1.1.6.1. Actuator and sensor models
1.1.1.1.6.2. Environment models
1.1.1.1.6.3. C&DH, GNC, Command and Telemetry processing
1.1.1.1.7. Capable of interfacing with the ground system
1.1.1.1.8. Capability to provide for simulation of payload command and data handling interfaces and memory management functions for both separable and non-separable interfaces.
Payload simulations can be modeled as static data sets or as dynamic models. Assume payload models are provided by the individual payload program via the program office or payload vendor.
1.1.1.1.9. Capability to support remote connections for training, ops command verification or troubleshooting. More than a single instance and/or configuration is allowable to meet these requirements.
Flight Software Updates for the LDPE article Activities shall include:
Develop payload interface software.
Update and test FSW drivers for star tracker, reaction wheels, inertial measurement unit, and avionics boards.
Integrate the GN&C software to the simulation environments and the flight software application.
Update and configure simulation models for use in the LDPE MSIM.
Update the scripts for FSW full functional verification.
The Contractor shall perform FSW full functional verification on non-flight hardware.
Flight Software Deliverables:
Software delivered shall include instructions, or be ready-to-run, on FlatSat. Software deliverables during the design phase shall include (CDRL A014):
Command and Telemetry List (CTL). Note, Complete description of final command set (including bounds, I/O tests, state dependencies, and resulting behaviors) shall be delivered.
Dynamic Satellite Simulator (MSIM and Flatsat) Software Build 1 Software Build 2 (content of Builds 1 & 2 are for contractor to define) Flight Software (aka Build 3) Ground Support Equipment Delivery The Contractor shall provide Ground Support Equipment (GSE) necessary for the build-up, test, and integration of the full system (e.g. shipping containers, fixtures, etc.). This equipment will be delivered to the government for continued use and shall have unique identification as described in AFI 63-101/20-101.
Hardware-in-the-Loop LDPE Simulator The Contractor shall provide a hardware-in-loop LDPE Simulator (FlatSat) capable of modification to meet program's software verification & validation, and complete test plan procedure requirements. At a minimum, the FlatSat shall consist of an EDU IAU with all other functions (e.g., star trackers, IMUs, solar array, transponders, sensors, etc.) and flight software. Upon completion of the LDPE article integration, the Contractor shall deliver and support the FlatSat for use in payload integration, test, operations rehearsal, and on-obit operations as Phases 2 & 3 are exercised.
Electronic Ground Support Equipment The Contractor shall provide / reuse available electronic ground support equipment (EGSE) required to develop and test the integrated avionics unit (IAU). Upon contract completion, the IAU EGSE unit shall be delivered to the government.
Deliverables Hardware Deliverables List:
The Contractor shall supply components harness and…
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.