SSHINE IDIQ SOW 10 Sep 24.docx

SPACE SYSTEMS AND HARDWARE INTEGRATION FOR NOVEL EXPERIMENTS (SSHINE) CONTRACT

FA9453-24-R-X006 ATTACHMENT 4

BASIC STATEMENT OF WORK

10 Sep 2024

1.0 Mission and Background

Air Force Research Laboratory (AFRL)/ Integrated Experiments and Evaluation Division (RVE) provides concept design, development, integration, test and evaluation, and engineering prototypes to demonstrate the viability of innovative space technologies along with cradle-to-grave support to ground, high-altitude balloon, near-space and spaceflight experiments and mission concepts, including concept development, requirements analysis, requirements definition, modeling and simulation, design, assembly, integration, and testing (AI&T), launch vehicle integration, ground system development/support, flight operations, user segment support, data acquisition, post-experiment analysis, technical reporting, technology transition, and/or decommissioning. Support processes and functions include, but are not limited to, scientific, technical, systems engineering, ground system development/support, flight operations, user segment support, and program advocacy activities associated with integrated flight experiments. The diversity of spacecraft configurations and/or science and military missions in flight experiment programs can range from single-mission nano/CubeSats to multi-satellite, multi-payload, or multi-mission applications on an Evolved Expendable Launch Vehicle Secondary Payload Adapter (ESPA) or similar class of spacecraft (to include, but not limited to ground systems and test beds).

1.1 Definitions:

1.1.1 Cradle-to-Grave: The term “cradle-to-grave,” as used in this contract, describes an end-to-end systems engineering process that begins with concept development, requirements analyses, then matures into documented design, build, and test of the experiment, followed by launch vehicle integration, on-orbit experiment operations, data acquisition, post-experiment analyses, and concludes with a Government-approved final Research and Development (R&D) technical report that captures the technical knowledge gained from the missions.

1.1.2 Small Scale: For the purposes of this contract, a small-scale mission refers to a spacecraft or payload the size and/or complexity of a CubeSat based mission and follows a nominal life cycle of half a year in Mission and Space System Development, one year in Flight Experiment Prototyping, Assembly, Integration, and Testing, and half a year in Flight Experiment Operations.

1.1.3 Large Scale: For the purposes of this contract, a large-scale mission refers to a spacecraft or payload the size and/or complexity of an ESPA based mission and follows a nominal life cycle of two years in Mission and Space System Development, two years in Flight Experiment Prototyping, Assembly, Integration, and Testing, and one year in Flight Experiment Operations.

1.1.4 Systems engineering: For the purposes of this contract, systems engineering activities/functions include all aspects of space technology and flight experiment design from concept definition through final evaluation. This also includes research, development, design of components, subsystems, and fully integrated aerospace systems (ground, launch, and space segments) for flight and test support equipment, to include design trades, risk analyses, and system effectiveness evaluation related to any of the following areas of expertise:

1.1.4.1 Systems engineering.

1.1.4.1.1 Subsystem and system modeling.

1.1.4.1.2 Subsystem and system integration.

1.1.4.1.3 Satellite system simulation.

1.1.4.1.4 Mission design and evaluation.

1.1.4.2 Electrical engineering.

1.1.4.2.1 Electronic circuit or power systems.

1.1.4.2.2 Communications systems.

1.1.4.2.3 Optical and electromechanical systems.

1.1.4.3 Mechanical engineering.

1.1.4.3.1 Thermal management systems.

1.1.4.3.2 Structures and mechanisms.

1.1.4.4 Software engineering.

1.1.4.4.1 Information systems/information assurance/cyber security/Communications Security (COMSEC) engineering.

1.1.4.4.2 Flight software development.

1.1.4.4.3 Ground software development.

1.1.4.4.4 Testing software development.

1.1.4.4.5 Software testing, maintenance, and integration.

1.1.4.5 Test planning and design.

1.1.4.5.1 Component-to-system testing.

1.1.4.5.2 Functional and environmental testing.

1.1.4.5.3 Test instrumentation design.

1.1.4.5.4 Laboratory design, setup, measurement, experimentation.

1.1.4.6 Modeling/simulation, analyses, and evaluation.

1.1.4.7 Performing functional and environmental tests.

1.1.4.8 Data reduction, analyses, and reporting.

1.1.4.9 Development and fabrication of ground support equipment and software.

1.1.5 Surge Capability: For the purposes of this contract, surge capability refers to the ability to meet requirements when mission needs have exceeded baseline resource capacity. This may occur as a result of in-scope changes or extending task periods of performance, as well as short-term labor fluctuations due to unanticipated increases in concept development, mission design, integration, test, delivery, or operations requirements.

1.1.6 Meeting Support: Where this contract requires the support of a conference, technical exchange, design review, program review, briefing, or any other meeting, that support includes:

1.1.6.1 Attendance and participation in the meeting.

1.1.6.2 Taking meeting minutes and providing these to the Government to capture actions and activities that transpired at the meeting.

1.1.6.3 At the government’s request, scheduling, and coordination of meetings.

1.1.7 Temporary Duty (TDY) Travel: The contractor may be required to travel to meet contract requirements using commercial air, Government air, and other conventional modes. The following rules apply to all such tasks:

1.1.7.1 Travel arrangements will be based on individual tasks, and the cost of travel will be directly reimbursed from task funding.

1.1.7.2 All travel (Outside Continental United States and Continental United States (OCONUS & CONUS)) requires prior coordination by a government lead.

1.1.7.3 All OCONUS travel must be approved in advance, in writing, by the contracting officer.

1.1.7.4 Minimal local travel may be required.

1.1.7.5 Travel to other Government facilities or other contractor facilities may be required.

1.1.7.6 All travel requirements (including plans, agenda, itinerary, dates) will be pre-approved by a government lead.

1.1.7.7 All travel is on a strictly cost reimbursable basis. Costs for travel will be billed in accordance with the regulatory implementation of Public Law 99-234, Federal Civilian Employee and Contractor Travel Expense Act of 1985 and Federal Acquisition Regulation (FAR) 31.205-46 Travel Costs and Joint Travel Regulations.

1.1.7.8 Billable travel costs are airfare, ground transportation, and per diem costs – not labor hours. The contractor will, at no charge to the Government, submit a Notice of Excess Commercial Airline Ticket Cost report when the use of other than least costly air travel is required to complete a Government directed task.

1.1.7.9 The contractor will be responsible for obtaining passports or visas and making travel arrangements to and from any CONUS location.

1.1.8 Contractor Procured/Acquired Property: The contractor may be required to procure/acquire property or equipment during the performance of a task order. The following rules apply to all such tasks:

1.1.8.1 Purchases must be authorized by a Government Technical Lead.

1.1.8.2 Purchases exceeding the Standard Simplified Acquisition Threshold must be authorized by the contracting officer.

1.1.8.3 Any equipment or property procured and all Government-provided records, files, documents, and work papers or those generated in support of this work effort are Government property.

1.1.8.4 All property and materials associated with these efforts will be coordinated with a Government technical lead and be managed in accordance with the contractor’s property management policies, procedures, practices, and systems.

1.1.8.5 The contractor will maintain a current inventory of Government Property (including Contractor Acquired Property).

1.1.8.6 If the contractor wishes to reutilize any government property not meeting the abandonment or destruction criteria of FAR 45.603, the proposed reutilization will be submitted to a government technical lead for concurrence.

1.1.9 Functional Area: The work under SSHINE is described as belonging to specific functional areas. Each functional area contains a grouping of tasks requiring similar knowledge, skills, and ability, as well as close coordination with other tasks in the functional area. Task orders may support one or more functional areas.

1.1.10 Space Technology: The work under SSHINE concerns the development of space technology. This includes, but is not limited to:

1.1.10.1 System models and simulations.

1.1.10.2 Spacecraft.

1.1.10.3 High Altitude Balloons.

1.1.10.4 Spacecraft or High-Altitude Balloon Payloads.

1.1.10.5 Ground Control Systems and Infrastructure.

1.1.10.6 Ground Support Equipment.

1.1.10.7 Ground-based demonstrations and experiments.

1.1.10.8 Supporting network and communications infrastructure.

1.1.10.9 Laboratory and flight hardware.

1.1.10.10 Assembly, Integration, and Testing infrastructure.

1.1.10.11 Space Networking Technologies.

2.0 Scope

The scope of this work is to support the required research, engineering, and technical management for performing space technology concept development, analysis, development, integration, experimentation, demonstrations, and evaluation in support of the AFRL/RV mission, including cradle-to-grave processes and functions for a range of experimental complexity. The Government seeks engineering and technical effort in the following functional areas and specific activities:

2.1 Mission and Space System Development.

2.2 Flight Experiment Prototyping, Assembly, Integration, and Testing.

2.3 Flight Experiment Operations.

2.4 Ground System Development.

2.5 Program Support.

3.0 Compliance and Reference: Compliance Documents are listed in Attachment 1 and Reference Documents are listed in Attachment 2. Reporting and documenting requirements are described in the Contract Data Requirements List (CDRL), Section 8.

4.0 Requirements: The following requirements are applicable to the listed RVE functional areas in Section 2. The contractor will be required to travel to other Government agencies and/or other contractor locations to perform design, integration, and test activities in support of AFRL/RVE integration and test programs, as described in individual task orders.

4.1 Mission and Space System Development.

4.1.1 The contractor will support direct technical and systems engineering tasks to RVE Program Managers, Deputy Program Managers, Chief Engineers, Systems Engineers, or other designated program leads.

4.1.2 The contractor will support systems engineering and analytical tasks to AFRL mission and space system designs.

4.1.2.1 The contractor will support in the development of government flight experiment and space technology requirements, mission scope, design tradeoffs/alternatives, concepts of operation, mission constraints, conceptual designs, and mission analyses, including:

4.1.2.1.1 Refinement of programmatic objectives into actionable requirements.

4.1.2.1.2 Analyses and documentation for laboratory, range, ground, near-space, and/or space flight experiments.

4.1.2.1.3 Iteration of requirements, flow-downs, concept of operations; the refining of objectives; and interface management.

4.1.2.2 The contractor will perform analyses and evaluations accomplished through relevant experimental testing, modeling and simulation, and engineering analysis.

4.1.2.3 The contractor will prepare documentation for all systems engineering activities related to space technology programs and individual flight experiments, to include technical input into development of Government Reference Designs (GRD).

4.1.3 The contractor will support Model Based Systems Engineering (MBSE) when/where applicable/requested, including requirements definition, design, analysis, and verification/validation activities beginning in the conceptual design phase and continuing throughout program life cycle, including:

4.1.3.1 Development of MBSE models.

4.1.3.2 Evaluation of models delivered by outside performers.

4.1.3.3 Exercise and test of models in support of RVE objectives.

4.1.4 The contractor will support modeling and simulation tasks, including:

4.1.4.1 Development of modeling capabilities to simulate, emulate and evaluate technology options identified by RVE.

4.1.4.2 Testing and operation of modeling and simulation capabilities.

4.1.4.3 Analyses comparing model and simulation results to experimental findings.

4.1.4.4 Analyses identifying requirement shortfalls, missing functionality, and model improvements.

4.1.5 The contractor will support Systems Engineering tasks, including mechanical, thermal, electrical, structural, and other specialized engineering to support mission development for space technology, spacecraft, and high-altitude balloon experiment designs.

4.1.6 The contractor will support Hardware/Software-in-the-Loop and Cloud Computing Architecture development and administration tasks including:

4.1.6.1 Design and development of cloud computing architectures supporting RVE hardware/software-in-the-loop testing environments.

4.1.6.2 Implementation of cross-domain solutions to move data between different classification levels, external connections, and point-to-point transmissions.

4.1.6.3 Develop, maintain, and upgrade RVE hardware/software-in-the-loop testing environments.

4.1.6.4 Comprehensive cybersecurity and information assurance support, including compliance with Department of Defense (DoD) risk management frameworks, and other security requirements.

4.1.7 The contractor will support in the development of space technology and flight experiment requirements, design, and interface control documentation.

4.1.8 The contractor will support with program management tasks, including attendance at technical meetings, reviews, off-sites, or technical conferences.

4.1.9 The contractor will support procurement assistance with long lead hardware/software critical to future space experiment program success.

4.1.9.1 The contractor will support the procurement of available commercial and non-commercial space-rated/grade related hardware.

4.1.10 The contractor will support miscellaneous tasks such as trade studies, demonstrations and various analysis as directed by the Government Program Manager.

4.1.11 The contractor will support technology transfer planning and decommissioning support, to include planning in support of technology transition to external mission partners.

4.1.12 The contractor will support the design and fabrication of ground-based proofs-of-concept, experiments, and demonstrations.

4.1.12.1 The contractor will prepare documented data acquisition, processing, analysis, and modeling/simulation tools to be used in the experiment, research, or analysis effort for evaluations.

4.1.12.2 The contractor will document experimental processes and results to allow third parties to independently reproduce the experiment, research, or analysis effort.

4.1.13 The contractor will support direct analytical, systems engineering, and administrative tasks to the University Nanosatellite Program (UNP) when requested.

4.1.13.1 The contractor will lead event planning, venue rental/booking, and procurements for UNP activities when requested.

4.1.14 The contractor will travel to other Government agencies and/or other contractor locations, as required, in support of design and test requirements reviews, briefings to industry, conferences and other meetings related to RVE integration and test programs.

4.1.15 The contractor will prepare monthly status reports on activity under the scope of section 4.1 and document lessons learned.

4.1.15.1 The monthly status report may be combined with the other monthly status reports in section 4.

4.1.15.2 The contractor will present monthly status reports and lessons learned to internal and/or external audiences as directed by the government.

4.2 Space Experiment Prototyping, Assembly, Integration, and Testing:

4.2.1 The contractor will support direct analytical, technician, and systems engineering tasks of the RVE Assembly, Integration, and Testing Infrastructure Lead(s).

4.2.2 The contractor will draft, prepare, revise, and review design documentation including, but not limited to:

4.2.2.1 User’s guides.

4.2.2.2 Interface Control Documents (ICDs), Specifications.

4.2.2.3 Test Processes/Procedures.

4.2.2.4 Safety Plans.

4.2.2.5 Risk Management Plans.

4.2.2.6 Attendance and participation in programmatic, technical and safety reviews.

4.2.2.7 Reliability, operability, interoperability, and performance assessments.

4.2.3 The contractor will support full life-cycle technology implementation tasks, including:

4.2.3.1 Space technology, spacecraft, and high-altitude balloon flight hardware design and fabrication.

4.2.3.1.1 Hardware development and integration.

4.2.3.1.2 Hardware testing and experimentation.

4.2.3.1.3 Technology transition support.

4.2.3.2 Space technology, spacecraft, and high-altitude balloon flight software/firmware design and development.

4.2.3.2.1 Modifying existing software/firmware.

4.2.3.2.2 Writing and documenting new code.

4.2.3.2.3 Integrating and testing new or modified code.

4.2.3.2.4 Maintaining software and related databases.

4.2.3.2.5 Software configuration management.

4.2.3.3 Laboratory research, test and assessment design, technology validation testing and experimentation.

4.2.3.3.1 Ground/laboratory test planning and procedures development, test design and fabrication, test preparation and coordination.

4.2.3.3.2 Arrangement of equipment and logistics for the test effort.

4.2.3.3.3 Systems-level tests to evaluate performance of spacecraft, balloon, and ground systems/subsystems.

4.2.3.3.4 Data reduction, analyses, and review the results of functional and environmental testing of spacecraft, high-altitude balloon, and ground systems/subsystems.

4.2.3.3.5 Documented data acquisition, processing, analysis, and modeling/simulation tools to be used in a technology validation effort.

4.2.3.3.6 Documenting experimental processes and results to allow third parties to independently reproduce the evaluation effort.

4.2.3.4 Re-engineering and re-design of software and hardware after testing.

4.2.4 The contractor will support assembly and integration tasks, including:

4.2.4.1 Space technology assembly and integration support.

4.2.4.2 Government integration facility management, including personnel training, facility security, and safety compliance.

4.2.4.3 Spacecraft bus, payload, and experiment assembly and integration within government facilities.

4.2.4.4 High-altitude balloon, payload, and experiment assembly and integration within government facilities.

4.2.4.5 Assistance with hardware/software procurement and other direct costs during assembly and integration.

4.2.4.6 Maintenance and upgrade support for government integration facility capabilities.

4.2.4.7 The contractor will prepare documentation and laboratory safety instruction (e.g. vehicle operations, crane operations, hazardous materials, waste management, explosives, laser radiation, welding, cutting, brazing, chemicals, and electrostatic discharge) in accordance with the Programmatic Environmental Safety and Health Evaluation Plan.

4.2.4.8 The contractor will identify and provide recommendations to the Government for addressing hazardous situations found in workspaces, manufacturing areas, test facilities, integration areas, storage facilities, pre-launch areas, launch facilities, and post-launch processing.

4.2.4.9 Research, development, and planning for future space system assembly, integration, and testing needs, objective, and programs. Including:

4.2.4.9.1 New assembly, integration, and testing capabilities.

4.2.4.9.2 Planning tools.

4.2.4.9.3 Test operation, plans, and concepts.

4.2.4.9.4 Data reduction, analysis, and reporting tools.

4.2.5 The contractor will support flight experiment launch integration tasks, including:

4.2.5.1 Support of integration studies, interface control documents, and briefings.

4.2.5.2 Packing, protecting, and shipping flight experiment and support equipment to the launch site.

4.2.5.3 Support of hardware and software integration efforts in preparation for flight experiment launch, including mechanical installation, functional testing, blanketing, fueling, inspection, fairing closeout, range safety procedures, and day of launch processes.

4.2.5.4 Support of post launch anomaly resolution, telemetry archiving and analysis, and documentation.

4.2.6 The contractor will support the Government in shipping and receiving of flight experiment and assembly, integration, and testing hardware/software.

4.2.7 The contractor will have the ability to support a surge capability to meet requirements of section 4.2 within unexpected or tightened program constraints.

4.2.7.1 In the event surge requirements drive a change to the contract, the contractor will be notified through a Request for Proposal (RFP), contract/task order modification, or contracts letter, as appropriate.

4.2.8 The contractor will travel to other Government agencies and/or other contractor locations, as required, in support of design and test requirements reviews, briefings to industry, conferences and other meetings related to RVE integration and test programs.

4.2.9 The contractor will prepare monthly status reports on activity under the scope of section 4.2 and document lessons learned.

4.2.9.1 The monthly status report will be combined with the other monthly status reports in section 4.

4.2.9.2 The contractor will present monthly status reports and lessons learned to internal and/or external audiences as directed by the government.

4.3 Flight Experiment Operations.

4.3.1 The contractor will support direct analytical, systems engineering, and technical tasks of the RVE Operations Cadre lead, or mission-specific operations lead as delegated.

4.3.2 The contractor will support flight experiment mission and operations planning including:

4.3.2.1 Procedure development for all phases of the mission.

4.3.2.2 CONOPS development.

4.3.2.3 Launch and Early Operations (LEOps) plan

4.3.2.4 Operational testing via simulator (to include setup, configuration, and use of various virtual simulations and flatsats).

4.3.2.5 Ground system testing to include operations acceptance testing, factory compatibility tests, and launch-base compatibility tests.

4.3.2.6 Mission operations center planning to include facility planning, layout, and preparation.

4.3.2.7 Training material generation to support crew readiness events.

4.3.2.8 Coordination with systems team on various operational documents such as launch and early orbit

4.3.2.9 Participation in events such as day in the life tests, exercises, rehearsals, and mission dress rehearsals as an operator, systems expert, or mission planner (see section 2.1.3.2.3).

4.3.2.10 Completion of required AFRL training to certify as a member of the flight operations team. Assume ~8 hours of classroom training, 8 hours of practical training, and ~40 hours of on-console event training spread across ~6 months.

4.3.2.11 Participation in (and leading as appropriate) various operations IPT’s on a weekly basis.

4.3.2.12 Participation in a weekly Ops Cadre internal meeting.

4.3.2.13 Software tool development and test in support of operational needs.

4.3.2.14 Development of automatic functions or scripts to support operations as required.

4.3.2.15 Completion and coordination of on-boarding actions associated with various antenna networks including both SCN, commercial, and AFRL networks.

4.3.2.16 Assisting the operations lead in crew logistics management such as badging, entry-access lists, 2875 account creation, and training event planning.

4.3.3 The contractor will directly support flight operations, including:

4.3.3.1 Spacecraft on-orbit operations and experimentation including on-call support as required.

4.3.3.1.1 Reference section 2.1.2.7 for completion of required training for certification purposes.

4.3.3.1.2 The minimum number of shifts per month for currency will be tracked and adhered to.

4.3.3.1.3 Operations may include (but not limited to): Antenna resource scheduling, vehicle planning, systems support, command block building, command block verification, and release of commands to the vehicle at the direction of a government flight director.

4.3.3.2 Operations acceptance testing to include regression testing of new operational components and processes.

4.3.3.3 Development of forward-looking anomaly prediction and detection algorithms and software.

4.3.3.4 Development of historical data aggregation and trending analysis algorithms and software.

4.3.3.5 Development of vehicle fault detection reporting systems.

4.3.3.6 Support configuration management processes of procedures, scripts, vehicle tables, vehicle parameters, vehicle fault detection and response trees, and ground software items throughout the life of the mission.

4.3.3.7 Anomaly resolution support and reporting.

4.3.3.8 In the event the government requests a root cause analysis for a specific issue occurring during operations, the contractor will produce within 30 days of notice the following:

4.3.3.8.1 A root cause analysis by an independent party to collect and document information leading up to failure including identifying contributing factors, identifying a mitigation plan, and providing other recommendations as needed.

4.3.4 The contractor will support government technology transfer efforts, including:

4.3.4.1 Training of external mission partners on flight operations.

4.3.4.2 Technical reach back support for mission partners after technology transition.

4.3.4.3 The contractor will prepare documentation for all systems engineering activities related to transition of flight assets to operational users.

4.3.5 The contractor will have the ability to support a surge capability to meet requirements of section 4.3 within unexpected or tightened program constraints.

4.3.5.1 In the event surge requirements drive a change to the contract, the contractor will be notified through a Request for Proposal (RFP), contract/task order modification, or contracts letter, as appropriate.

4.3.6 The contractor will travel to other Government agencies and/or other contractor locations, as required, in support of design and test requirements reviews, briefings to industry, conferences and other meetings related to RVE integration and test programs.

4.3.7 The contractor will travel to conduct work covered under section 4.3 at other laboratories, field locations, test ranges, other Government locations, and other industry locations.

4.3.8 The contractor will prepare monthly status reports on activity under the scope of section 4.3 and document lessons learned.

4.3.8.1 The monthly status report may be combined with the other monthly status reports referenced in this task order and the basic contract statement of work.

4.3.8.2 The contractor will present monthly status reports and lessons learned to internal and/or external audiences as directed by the government.

4.4 Ground System Development.

4.4.1 The contractor will support direct analytical, systems engineering, and software development tasks for the RVE Ground Systems requirements.

4.4.2 The contractor will support ground system infrastructure development and testing, including:

4.4.2.1 Design and implementation of software tools.

4.4.2.1.1 Modifying existing software/firmware.

4.4.2.1.2 Writing and documenting new code.

4.4.2.1.3 Integrating and testing new or modified code.

4.4.2.1.4 Maintaining software and related databases.

4.4.2.1.5 Software configuration management.

4.4.2.2 Management of agile and emerging division directed ground system requirements.

4.4.3 The contractor will support RVE in-house ground system integration and deployment tasks, including:

4.4.3.1 Physical and cloud-based ground system maintenance.

4.4.3.2 Maintenance and upkeep of Mission Operations Center connections and equipment.

4.4.3.3 Procurement of cloud computing access and storage.

4.4.3.3.1 Support of RVE disaggregated development network

4.4.3.3.2 Support RVE ability to contract with other commercial ground stations for mission support.

4.4.4 The contractor will accomplish ground architecture cybersecurity accreditations on behalf of RVE, including:

4.4.4.1 Obtaining and maintaining compliance with Authorities to Operate.

4.4.5 The contractor will travel to other Government agencies and/or other contractor locations, as required, in support of design and test requirements reviews, briefings to industry, conferences and other meetings related to RVE integration and test programs.

4.4.6 The contractor will prepare monthly status reports on activity under the scope of section 4.4 and document lessons learned.

4.4.6.1 The monthly status report will be combined with the other monthly status reports in section 4.

4.4.6.2 The contractor will present monthly status reports and lessons learned to internal and/or external audiences as directed by the government.

4.5 Program Support.

4.5.1 For AFRL led space technology experiments with a total anticipated value over $10M, the contractor will provide direct analytical, systems engineering, and technician support to RVE Program Managers, Deputy Program Managers, Chief Engineers, Systems Engineers, or other designated program leads.

4.5.1.1 Program support will align with the functional areas and requirements listed in 4.1 through 4.4 but will instead be funded and tracked within the scope of a specific program and task order.

4.5.1.2 Monthly status reporting and presentation objectives for these programs will be documented in separate reports from the monthly status report.

5.0 Contract Management

5.1 Administrative Management.

5.1.1 Contractor will implement contract administrative, financial, and task planning and management functions to ensure the on-time, on-budget accomplishment of all authorized TOs and work effort described in Section 4.0. Including:

5.1.1.1 Planning, organizing, staffing, directing, and controlling cost, schedule, and performance at the prime and subcontract level to ensure compliance with the requirements of multiple, concurrent task orders.

5.1.1.2 The ability to respond to and manage task orders requiring responses as short as 15 days.

5.1.1.3 Surge support requirements as required by the Government.

5.2 Personnel Management.

5.2.1 The contractor will be responsible for management of contractor personnel. The contractor will accomplish tasks by providing qualified personnel possessing the appropriate combinations of education, training, security clearance and experience/skills.

5.2.2 The contractor will maintain a stable workforce while minimizing the impact of any turnover and/or disruptions to the Government and/or mission.

5.2.3 The contractor will ensure continuation of support during personnel absences due to sickness, leave, and voluntary or involuntary termination from employment such that there is no negative impact to the Government mission.

5.2.4 The Contractor will provide cross-functional support, which optimizes the Government’s cost, schedule, and/or performance efficiencies. Cross-functional personnel may support multiple task orders based on their functional expertise.

5.3 Key Personnel.

5.3.1 The personnel listed below are considered essential to the work being performed on contract.

5.3.1.1 Program Manager

5.3.1.1.1 10+ years program management experience related to DoD & major space systems/programs.

5.3.1.1.2 Active Top Secret SCI clearance

5.3.1.1.3 Desired education: Master’s degree in Business/Engineering/Other technical field from a regionally accredited institution.

5.3.1.1.4 Desired certification: Program Management Professional certification equivalent to Defense Acquisition Workforce Improvement Act Level 3 Program Manager Certification, or demonstration of continued education.

5.3.1.2 Chief Engineer

5.3.1.2.1 10+ years systems engineering experience related to DoD & major space systems/programs.

5.3.1.2.2 Active Top Secret SCI clearance

5.3.1.2.3 Desired education: Master’s degree in Science, Technology, Engineering, or Mathematics (STEM) from a regionally accredited institution

5.3.1.2.4 Desired Certification: Professional engineering certification equivalent to Defense Acquisition Workforce Improvement Act Level 3 Systems Engineering Certification, or, or demonstration of continued education.

5.3.1.3 Lead Software Engineer

5.3.1.3.1 10+ years systems engineering experience related to space and/or ground systems.

5.3.1.3.2 Active Top Secret SCI clearance

5.3.1.3.3 Desired education: Master’s degree in Science, Technology, Engineering, or Mathematics (STEM), Information Technology, computer science or similar from a regionally accredited institution

5.3.1.3.4 Desired Certification: Professional software certifications or similar, as well as demonstration of continued education.

5.3.2 Prior to proposing, substituting, removing, replacing, or diverting any of the specified individuals, the contractor will notify the Contracting Officer 10 working days in advance and will submit a written request and justification (including proposed substitutions) in sufficient detail to permit evaluation of the impact on this contract.

5.3.3 No change in key personnel will be made by the contractor without the prior written consent of the Contracting Officer and the RVE Director. The Contracting Officer will notify the contractor within 5 working days after receipt of all required information of the decision on the substitution(s). The Government reserves the right to require continued performance of previously approved key personnel or to require substitution of acceptable replacements.

5.3.4 The key personnel listed within this contract may, with the consent of the contracting parties, be amended to either add or delete personnel, as appropriate.

5.3.5 In the case of a no-notice departure, the contractor will immediately inform the contracting officer and Government leads. This written notification will include the date and time the position will be vacant, anticipated replacement date, and management corrective action, if needed, to ensure task mission remains on schedule toward completion.

5.4 Transition-In Planning.

5.4.1 The contractor will be given a transition period of up to 45 calendar days to provide qualified personnel that meet or exceed the stated requirements per Section 4. The Key personnel positions identified are required to begin performance at the beginning of the transition period. The transition period will begin from the effective date of the Basic Contract. During the transition period, all on-site contractor personnel will obtain required ID/CAC cards, computer system access requests, and receive workplace and task orientation to ensure the entire team is in-place for period of performance start, to fulfill contract requirements. The contractor will follow the transition plan submitted as part of the proposal and inform the contracting officer of progress throughout the transition period.

5.4.2 The Contractor will arrange and attend a contract kick-off meeting with the contracting officer, and other Governmental organizational representatives within 10 calendar days of contract award. The contractor will coordinate the date, time and location via e-mail notifications and prepare a suggested agenda and presentation. The contractor will take meeting minutes and provide these to the Government to capture actions and activities that transpired during the kick-off meeting.

5.5 Transition-Out Planning and Future Contracts.

5.5.1 The Contractor will participate in organizational, system, process and information knowledge transfer from the Government team (Government, Federally Funded Research and Development Centers, Advisory and Assistance Services members), to include 45 days of overlap with existing contractors, as applicable. The contractor will facilitate organizational, system and process knowledge and information transfer from the contractor to any new contractors or Government entities performing portions of this contract during the close out of this contract. A Transition-Out plan must be provided to the contracting officer and, Government technical leads, to track progress to provide adequate transition training to the follow-on contractor.

5.5.2 The contractor will be responsible for the employment, training, guidance, and supervision of contractor personnel assigned to perform tasks under awarded task orders. However, if Government-unique training is identified to perform their duties, then written approval must be obtained from contracting officer prior to attending the training. These personnel will be knowledgeable of and be able to independently apply the guidance found in the compliance and reference documents identified in Attachments 1 and 2.

5.6 Identification.

5.6.1 All contractor employees will clearly always identify themselves as “contractors”. This includes all communications (telephone, mail, electronic mail (email) and faxes), meetings, attendance sheets, and documents. In addition, contractor personnel will identify their company affiliation in email signature blocks. All contractor personnel will display their identification badge, which identifies them as contractor personnel. Contractor-occupied facilities on Government installations such as offices, separate rooms, or cubicles must be clearly identified with contractor supplied signs, name plates or other identification, showing that these are work areas for contractor or subcontractor personnel.

5.6.2 The contractor is responsible for obtaining and providing all Non-Disclosure Agreements (NDAs) for personnel supporting AFRL under this contract to protect all proprietary, restricted, competition sensitive, or any other restricted (e.g. non-foreign disclosure due to public law) data that will be used or accessed during the execution of this contract. The contractor will provide a copy of each NDA to the contracting officer.

5.7 Subcontractor Management.

5.7.1 The contractor will be responsible for any subcontract management necessary to integrate work performed on this contract and will be responsible and accountable for subcontractor performance on this contract.

5.7.2 The contractor will manage work distribution to ensure there are no Organizational Conflicts of Interest (OCI). Contractors may add subcontractors to their team after examination of information that there is no OCI issue or submission and approval of mitigation plan by the contracting officer.

5.8 Cost Control.

5.8.1 The contractor will demonstrate effectiveness in forecasting, managing, and controlling task order costs through providing cost-based controls including:

5.8.1.1 Monthly status reports as required in section 4.

5.8.1.2 Trip reports

5.8.1.3 Invoices

5.8.1.4 Proposals

5.8.1.5 Limitation of Funds notices.

6.0 Release of Information

6.1 Public Release.

6.1.1 Any briefings, technical reports, papers, or presentations prepared by the contractor for public presentation will comply with Defense Federal Acquisition Regulation Supplement (DFARS) 252.204-7000, Disclosure of Information. The contractor will provide a final document to the Contracting Officer Manager at least 45 days prior to the scheduled release date for Operations Security (OPSEC) review.

6.1.2 In the release of information relating to this contract, such release will include a statement to the effect that the project or effort depicted was or is sponsored by the Air Force Research Laboratory. For the purpose of this clause, "information" includes but is not limited to material presented in news releases, articles, manuscripts, brochures, advertisements, still and motion pictures, speeches, presentations, meetings, conferences, and symposia. Nothing in the foregoing will affect compliance with the requirements of the clause (if applicable) of this contract entitled "Security Requirements," FAR 52.204-2. The contractor will include this requirement in any subcontracts awarded as a result of this contract.

7.0 Location of Primary Performance:

7.1 Performance will primarily be conducted at the Phillips Research Site (PRS) laboratories located at Kirtland AFB, NM. On occasion, work may be performed at Holloman AFB, NM, remote field sites, or other research, integration and launch facilities in the U.S. and/or overseas, as specified in task orders.

7.2 Work accomplished at the Contractor’s facility must maintain the appropriate facility clearance requirements for the work to be performed. In such cases, the Contractor will be responsible for providing adequate facilities, equipment, and support for off-site Contractor personnel. The Government is responsible for all Information Technology (IT) equipment and support (including software licenses) for all Contractor owned and managed activities conducted off-site, or at alternate locations.

7.3 Hours of work.

7.3.1 Normal workdays are Monday through Friday except U.S. National Federal Holidays. Normal hours of work are from 0800-1600 daily. The Contractor’s staff typically work eight (8) hours per day, 40 hours per week. All employees are expected to be available during normal hours. The Contractor work hours should not exceed 40 hours per week without express written consent of the CO. This does not preclude the Contractor from performing at other times or days when reasonably necessary to accomplish the objectives described herein. The Contractor personnel working at Government facilities will conform to customer agency normal operating hours. The Contractor personnel are restricted from opening and closing secured areas within the on-site Government facility.

7.3.2 Federal Holidays for On-Site Personnel

7.3.2.1 The Contractor will not have staff present at the Government installation facilities on federal holidays. The federal holidays observed are, as follows: New Year’s Day, Martin Luther King Jr.'s Birthday, Washington's Birthday, Memorial Day, Juneteenth, Independence Day, Labor Day, Columbus Day, Veteran’s Day, Thanksgiving Day, and Christmas Day.

7.3.3 Other Holidays

7.3.3.1 On occasion, the President has been known to declare a federal holiday on a day that is not recognized in this SOW. If such an occasion arises, the Contractor will provide alternate work options for employees according to their corporate policy regarding Government office closures. The Contractor personnel will follow their corporate policy in these situations. Weather and Emergency Situations for On-site Personnel

7.3.4 The Contractor will provide alternate work sites for Contractor personnel during local emergency situations when the Base Commander has declared an emergency and has stated personnel should not report to the Base or should leave the Base during a workday. The Contractor is not authorized to perform any work that may require access to classified information outside of AFRL provided facilities. The Contractor will follow their corporate policy and the guidance of the installation containing their place of performance to determine reporting schedules due to a base closure, inclement weather, or shelter-in-place scenarios.

8.0 Ethics:

8.1 The Contractor will present an unblemished appearance regarding ethics, discretion, and protection of information, including the guidelines for electronic mail use listed in AFI 33-119 and Internet use of AFI 33-129 AFOSISUP.

9.0 Data Rights:

9.1 The Government will retain unlimited rights to all data and deliverables developed under the SSHINE contract exclusively at Government expense. For all other data, the Government requires Government Purpose Rights (GPR) or better. If the contractor identifies technical data to be delivered with restrictions, the contractor must assert in accordance with DFARS 252.227-7017. Throughout the period of performance of the contract, records, documents, and associated papers will be available for review at any time per Government request. Further data rights specifications will be documented in specific Task Orders.

10.0 Security Requirements

10.1 Clearance Requirements: The contractor will establish and implement information and physical security programs governing their efforts in accordance with the applicable DD254 Contract Security Classification Specification. The contractor will have the ability to process up to TS/SCI and hire/retain cleared personnel to perform the work required on this contract. At a minimum, contractor personnel will be eligible to obtain and maintain a Top-Secret/SCI clearance for the duration of the contract. Where certain TO activities have higher security requirements, the contractor personnel will have a current DoD Top Secret/SCI clearance or higher and be eligible for Special Access Programs (SAP), per TO specifications. The Government will provide the contractor with system/program Security Classification Guidance and other instructions on adherence to security requirements.

10.2 Classified Networks: The contractor will be required to access and perform duties on government provided classified networks such as SIPR, JWICS and other classified networks as necessary. The contractor will be required to access these networks in government provided facilities such as Sensitive Compartmented Information Facilities (SCIF) and Special Access Program Facilities (SAPF).

10.3 Justification for Classified Access: Due to the nature of the contract efforts and scope of work, necessary access to classified information and data is required by the contractor to adequately satisfy contractual obligations, conduct research and development, and provide technical support. Information such as technical reports, final reports, inspection reports, technical specifications/manuals, and intelligence reports are needed to fully understand technical contract requirements, to build upon subsequent classified efforts and apply lessons learned to current efforts. Without having access to classified information, the contractor will be at a great disadvantage in being able to conduct their duties thus delivering a sub-par product to the Government.

11.0 Technical Assistance Agreement (TAA):

11.1 The contractor will comply with the U.S. State Department’s International Trafficking in Arms Regulations (ITAR) (22 CFR Parts 120-130 and Amendments), the Arms Export Control Act, Defense Trade Security Initiatives, State Department, USAF, and Department of Defense policies relative to the ITAR and exporting and importing data especially for non-Foreign Military Sales cases. The contractor will obtain a TAA with each of the foreign nations identified by a Government lead at the time of any resulting contract and for the duration of this contract within 90 days after notification, with the appropriate agencies, such as the Department of State, to export and receive technical data (direct commercial sales) to Federal Acquisition Regulation (FAR) Part 12/FAR Part 15 contract activities. The contractor will maintain the TAA for the duration of the contract.

12.0 Government Data Systems Access:

12.1 Performance under this effort will require access to unclassified Air Force computer systems (standalone and networked). The contractor will comply with local procedures for obtaining approval for employees to access required Air Force computer systems.

12.1.1 The contractor is prohibited from attaching any computer hardware to the PRS network or running any computer software unless it 1) is Government furnished equipment, or 2) has been certified and accredited according to current PRS Operating Instructions. Any such requests for reconfiguration, upgrade, or addition of computer hardware or software must be approved by the PRS Designated Approval Authority (DAA) Representative via the contractor's submission of a written request to the Program Manager (PM). Contractor use of computer modems on any machine attached to the PRS network is prohibited unless prior written approval is obtained from the PRS DAA Representative. Use of commercial internet service providers is prohibited unless prior written approval is given by the PRS DAA Representative.

12.1.2 Contractor personnel using any PRS information technology assets will comply with all PRS computer security requirements. In addition, should contractor personnel require access to PRS computer networks or databases, they will inform the PM or Deputy PM, who will arrange for the contractor personnel to complete the required documentation for a new computer account. The contractor will notify the PM or Deputy PM within one workday of any contractor personnel who no longer requires an open account and will take action to close the computer account with the appropriate PRS office within that same workday.

12.1.3 All contractor personnel who will be using Command, Control, Communications, and Computer (C4) systems belonging to the federal Government to generate, process, store, transfer, or communicate information will attend mandatory C4 systems security training.

12.1.4 All contractor personnel who perform daily network management control or administration of information flow responsibilities (i.e., Workgroup Manager or System Administrator) are required to be certified Information Assurance (IA) network professionals, a certification that is obtained by completing Air Force provided interactive computer-based training (CBT). These IA CBTs are in addition to the mandatory C4 systems security training mentioned above.

12.1.5 The contractor will notify the PM of any Government C4 system problems or issues which come to their attention that may impact the contractor's task schedule.

12.1.6 All contractor personnel who require access to PRS C4 systems are required to obtain a National Agency Check (NAC) consistent with Public Trust Positions (Standard Form 85P or most current form).