Attachment_1_-_Draft_RISE_Basic_SOW_-_26_Mar_18.pdf

R&D INTEGRATED SPACE EXPERIMENTS (RISE) CONTRACT

FA9453-18-R-0003, ATTACHMENT 1

BASIC STATEMENT OF WORK

26 MARCH 2018

1. Mission and Background The RISE contract supports the Air Force’s Space Superiority Service Core mission requirements and its Space Warfighter Construct growth areas by providing concept design, development, integration, test and evaluation of new space technologies, innovative, engineering prototypes, and demonstrating the viability of innovative space technologies. The Air Force Research Laboratory's Space Vehicles Directorate, Integrated Experiments and Evaluation Division (AFRL/RVE), conducts innovative research and development of ground, high-altitude balloon, near-space, and spaceflight experiments.

RVE’s work includes mission analyses, systems engineering, integration and testing of components and subsystems through system-level integration and test, and the execution of experiment mission operations. RVE collaborates with internal and external organizations.

2. Scope This contract provides the required research, engineering, and technical management for performing space technology concept development, analysis, development, integration, experimentation, demonstration, and evaluation in support of the AFRL/RV mission. When stated within task order (TO) requirements, the contractor shall be capable of performing quick reaction research, analysis, and development of engineering prototypes. This includes cradle-to-grave processes and functions for a range of experimental complexity as defined in the definitions section (section 2.1).

When provided Government-procured engineering prototype hardware/software, the contractor shall be capable of short timeline assembly, integration and test to space-qualify the engineering prototypes.

Components and subsystems requiring integration and test include, but are not limited to: power, thrusters, structures, mechanisms, sensors, optics, electronics, guidance, navigation, and controls, data processing, communication, ground support equipment, and associated software/firmware.

The Government seeks engineering and technical effort in the following RISE activities:

• Overarching Program Management o Program management, including attendance at technical meetings, reviews, off-sites, or technical conferences stated within TO specifications

• Mission Design o Analytic modelling of enterprise objectives and how they translate to individual mission formulation o Systems engineering in support of scoping of requirements and translation into initial concept and preliminary designs

• Implementation o Engineering, including systems, software, and test engineering o Systems engineering support to translate requirements to software and hardware and validate traceability from initial mission formulation o Flight hardware design, fabrication, and assembly o Flight software/firmware development and test

• Assembly, Integration, and Test (AI&T) o AI&T laboratory research, engineering, design, scheduling, test preparation, software, operation, personnel training, safety, and maintenance o Flight payload and experiment platform integration and test

• Experimental Demonstrations o Spacecraft launch integration, commissioning, and on-orbit experimentation o Integrated ground experiment, design, fabrication, and assembly o Ground system hardware/software development, integration, test, and deployment o Mission and operations planning, design and development

• Technology Transfer o Support the transfer of lessons learned and technology/mission capability to space enterprise partners

Figure 1 – AFRL/RVE Notional Experimental Lifecycle Process

For programmatic execution, AFRL categorizes on-orbit missions into three Classes of efforts that span the experiment process. Class 1 missions are rapid satellite efforts that can typically be realized in under one (1) year. These risk-tolerant missions leverage the large launch availability and reduced scope available to canisterized missions. Many of these missions would be under $1M. Class 2 missions may be fairly capable missions but do not require parts traceability and embrace tailored mission practices.

These missions would be in the $1-10M range. Many Class 1 and Class 2 missions would leverage the commoditized avionics suites that are available. Both Class 1 and Class 2 missions would generically be described as embracing “New Space” practices. Class 3 missions are built on the traditional space vehicle mission assurance paradigm with rigorous parts traceability and programmatic practices. The contractor shall support all phases of a program in all three areas of mission assurance classes. Some programs may only go through the first part of the process, or alternatively could enter partially through the process.

In addition to the on-orbit experiment classes, the contractor shall perform work in the following areas:

integrated ground experiments; ground support equipment; spacecraft; high-altitude balloon flights;

reduced gravity platforms; launch vehicles (e.g., orbital and suborbital rockets, space plane, International Space Station (ISS) deployments); platform and subsystem/component design; software design and development; analyses throughout the research and development system engineering process;

design optimization and review; testing and evaluation; deployment of experimental assets; and transition phases.

To execute spacecraft, ground, or high altitude balloon experiment integration, test, and mission development, technical work is required in the areas of:

• Information systems

• Information assurance

• Communications security (COMSEC) engineering

2.1 Definitions:

2.1.1 Cradle-to-Grave/Life Cycle: The term “cradle-to-grave,” as used in this contract, is 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 R&D technical report that captures the technical knowledge gained from the missions. The term “Life Cycle” is synonymous with Cradle-to-Grave.

The cradle-to-grave processes and functions include scientific, technical and systems engineering activities associated with integrated space experiments from the initial concept development stage through the technology transition phase. This includes, but is not limited to, developing and refining requirements, conducting concept design, engineering analyses, trades, and modeling/simulation, and supporting systems engineering reviews (from Alternative Systems Reviews and Preliminary Design Reviews through Critical Design Reviews and System Verification Reviews), with particular emphasis on systems-level integration.

2.1.2 Small Satellites: For the purpose of this contract, RVE defines small satellites as an effort captured by Class 1 and Class 2 missions. This effort reflects space experiments with masses less than 50kg; however, Class 3 missions may overlap into this mass-class as well.

2.1.3 Mission assurance/risk classes: Mission assurance classes are defined as Class 1, Class 2, and Class 3 as identified in section 2.0. Class 3 refers to the mission risk classification guidelines accepted and used for acquisitions in the National Security Space (NSS), Department of Defense (DoD), and NASA communities.

Figure 2 – AFRL Satellite Class Structure

2.1.4 Complexity of 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).

2.1.5 Surge capability/corporate flexibility to allocate resources: When mission requirements exceed 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.

2.1.6 Proven systems engineering standards and practices: A set of documented system engineering processes/practices anchored in Industry or Government best practices (such as but not limited to, “NASA’s rules for the design, development, verification, & operation of flight systems”)

2.1.7 Scaled mission assurance: The ability to tailor practices and processes against various risk acceptances positions (i.e., Class 1/2/3). This includes the historic model in section 2.1.3, as well as the evolving “new space” mission assurance paradigm.

2.1.8 New Space: New Space as defined in this SOW reflects the approach embodied by emerging commercial markets characterized by risk tolerance and the ability to trade requirements against constraints such as cost and schedule.

3. Compliance and Reference Documents 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 6.

4. Requirements The following requirements for the R&D activities are applicable to the listed RVE functional areas and concurrent technical effort. Per TO specifications, the contractor may 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.

4.1 Systems, Software, and Test Engineering

4.1.1 Systems engineering is integral to the development and successful execution of a flight experiment. The contractor shall perform systems engineering activities/functions for all aspects of flight experiments from concept definition through final evaluation, including 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. The contractor shall draft, prepare, revise, and review design documentation including, but not limited to: User’s guides, Interface Control Documents (ICDs), Specifications, Test Processes/Procedure, Safety Plans, and Risk Management Plans. All documents should reflect the current configuration of the final delivered item. Per CDRLs, the contractor shall provide documentation for all systems engineering activities related to individual flight experiments, to include technical input into development of Government Reference Designs (GRD) and transition of flight assets to operational users. (CDRL A015, A017, A018, A023)

4.1.2 Engineering disciplines/functions shall include but are not limited to:

• Systems engineering

• Electrical engineering

• Mechanical engineering

• Software engineering

• Test planning and design

• Test instrumentation design

• Modeling/simulation, analyses, and evaluation

• Design/planning (specification) of functional and environmental test requirements

• Performing functional and environmental tests

• Data reduction, analyses, and reporting

• Development and fabrication of ground support equipment and software

4.1.3 The mechanical, electrical, and information system’s design and planning functions shall encompass the following in any ground, high-altitude balloon, near-space or space flight experiment:

• Electronic circuit or power systems

• Structures and mechanisms

• Communications systems

• Optical and electromechanical systems

• Data acquisition and data processing

• Information systems/information assurance/cyber security/COMSEC engineering

• Subsystem and system modeling

• Subsystem and system integration

• Component-to-system testing

• Functional and environmental testing

• Laboratory design, setup, measurement, experimentation

• Satellite system simulation

• Troubleshooting at any phase of development, test, or mission operations

• Setup and calibration of standard and custom test and fabrication equipment

• Training for participants in the University NanoSats Program (UNP) in spacecraft fabrication, assembly, integration, and test

4.1.4 The contractor shall incorporate cyber security throughout all architectural segments. Further cyber security requirements will be detailed in the Task Orders.

4.2 Mission Development and Execution of Experiments

4.2.1 The contractor shall perform research, mission analyses, and documentation for flight and/or ground experiments to facilitate the Government’s development of mission/system requirements, objectives, constraints, and alternatives. Mission analyses or evaluations shall be accomplished through relevant experimental testing, modeling and simulation, and/or engineering analyses. (CDRL A022)

4.2.2 The contractor shall provide documented data acquisition, processing, analysis, and modeling/simulation tools to be used in the experiment, research, or analysis effort for evaluations. The scope of the document shall include the ability of a third party to independently reproduce the above processes.

4.2.3 The contractor shall assist the Government in the assessment of historical programs for lessons learned to be leveraged into current or future space program experiments for AFRL/RVE’s programs.

4.2.4 The contractor shall 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.5 The contractor shall prepare monthly status reports and document lessons learned. Additionally, the contractor shall prepare briefings and present the research results as directed by the Government.

(CDRL A002)

4.3 Assembly, Integration and Test

4.3.1 The contractor shall provide engineering and technical support for safe handling, assembly, integration, and testing of flight and ground components/systems. The contractor shall assemble and integrate the various systems/subsystems mechanically, electrically, and through software. The contractor shall work with the test and integration personnel to troubleshoot and resolve any related system or subsystem incompatibilities.

4.3.1.1 AI&T shall be conducted in the AFRL/RVE AI&T Laboratories or at field locations, test ranges, and other Government locations.

4.3.1.2 The contractor shall support the Government in shipping and receiving of hardware/software.

4.3.2 The contractor shall perform ground/laboratory test planning and procedures development, test design and fabrication, test preparation and coordination, and arrange equipment and logistics for the test effort. (CDRL A004)

4.3.2.1 The contractor shall perform systems-level tests to evaluate performance of spacecraft, balloon, and ground systems/subsystems.

4.3.2.2 The contractor shall perform data reduction, analyses, and review the results of functional and environmental testing of spacecraft, balloon, and ground systems/subsystems.

4.3.2.3 The experimental test results shall be documented and used to validate analytical predictions and mission performance, and to space-qualify the systems/subsystems.

4.3.3 The contractor shall use Department of Defense (DoD), NASA, and commercial regulations and standards in the performance of spacecraft assembly, integration and testing when using the AI&T Laboratory equipment to perform space worthiness testing (thermal/vacuum/vibration/etc.). The contractor shall document the procedures and results of the tests.

4.3.4 The contractor shall conduct research, develop and plan for future space system AI&T objectives and programs to be conducted in RVE’s AI&T Laboratories, as required. This includes:

• Development of innovative AI&T capability designs to provide agility and flexibility

• New AI&T plans that include projected cost, schedule, and technical requirements

• Test operations plans and concepts of operations, to include lessons learned

• Advanced test data reduction, data analysis, reporting, and distribution

• Revised program security guides, mission assurance plans, safety plans, facility management plans, and other documentation required in support of AI&T programs

4.3.5 The contractor shall design, plan, schedule, prepare, upgrade, repair, operate, inspect, and maintain the RVE AI&T Laboratories’ assembly, integration, and test equipment, instrumentation, tools, and data acquisition and reduction systems. This shall include any space technology systems/subsystems currently located in the laboratory and/or under test.

4.3.6 The contractor shall define test requirements for spacecraft integration and testing per TO or external customer specifications and plan, schedule, and de-conflict test equipment operations. In consultation with technical leads/task order leads, the contractor shall organize, coordinate, and manage a test schedule for all tests to be conducted in the AFRL/RVE AI&T Laboratories. Contractor shall de-conflict and accommodate multiple flight programs’ test schedules in accordance with RVE mission priorities. The contractor shall document all schedules and processes and coordinate and report them to the AI&T Task Order lead.

4.3.7 The contractor shall operate and maintain all AI&T Laboratory equipment, clean rooms, and work sites in accordance with applicable manufacturer’s specifications, Air Force compliance documents in Attachment 1, or as stated within TO specifications. The contractor shall perform hardware/software configuration management and documentation control for the equipment, instrumentation, tools, and space technology systems/subsystems under test.

4.3.8 The contractor shall provide personnel training, documentation, and laboratory safety instruction to cover such issues as 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.

(CDRL A005, A006)

4.3.9 In support of the operations and maintenance of the AI&T Laboratories, the contractor shall be able to procure materials and services after approval by the AI&T Task Order lead, in coordination with the Contracting Officer, and following the internal RVE Purchasing Requirements process.

Justifications for such purchases usually include: a) as specified by or derived from TO experiment testing requirements, b) as a consequence of breakage, damage, or malfunction of existing instrumentation/equipment, c) as a result of finding instrumentation/equipment inoperable during a maintenance inspection and d) consumables as required by periodic maintenance. (CDRL A012)

4.4 Mission Operations, and Transition

4.4.1 The contractor shall provide engineering and technical support for experiment mission development and operations to include:

• Mission planning

• Safety (personnel, facility, launch/space vehicle) and security planning and procedures

• Environmental regulation and policy compliance

• Test and evaluation equipment and laboratory adequacy and applicability

• Risk analysis and risk management

• Pre-ground test equipment deployment, setup and operations

• Pre-launch and launch operations

• On-orbit, high-altitude, or ground-based experiment operations and management

• Hardware/software configuration management and control

• Test data acquisition, reduction, analysis, and verification

• Identification of Command, Control, Communications and Computer Systems (C4) systems compatibility prior to transition

• Transition of ground or space assets to end users, as required by the Government

4.4.1.1 Pre-launch and ground operations include but are not limited to: packing, protecting, and shipping complete spacecraft and support equipment to the launch site. The contractor shall perform all pre-launch activities required to integrate the spacecraft onto a rocket, including mechanical installation, functional testing, blanketing, fueling, inspection, fairing closeout, range safety procedures, and day of launch processes. After launch, required functions involve conducting mission/experimental flight operations, anomaly resolution, telemetry archive and analysis, as well as reporting and documentation (e.g., through procedure red-lining and memograms).

4.4.2 The technology transition phase includes: documenting the research based on the ground test and flight experiment results, conclusions, and lessons learned as part of the program final report. Contractor shall support specific technical requirements as identified by the Government to transition flight operations to external organization(s) as required. (CDRL A003)

4.5 Ground and Flight Experiment Hardware Design, Fabrication, Assembly and Test During the AI&T phase, the contractor shall analyze, design, document, fabricate or acquire, inspect, assemble, perform functional and environmental tests on and validate spacecraft/balloon parts, subassemblies, and components, and the supporting test equipment, fixtures and aerospace/ground systems. Performance requires expert knowledge in the design, fabrication, use, and/or assembly of aerospace and spaceflight-quality parts/components.

4.6 Ground and Flight System Software/Firmware Development for Test & Operations The contractor shall design, develop, implement, and test software/firmware required for operation of experimental ground systems, payloads, and flight platforms as well as software/firmware to be used in test and evaluation efforts. This involves activities such as modifying existing software/firmware, architecting, writing and documenting new code, integrating and testing new or modified code, programming Field Programmable Gate Arrays (FPGAs), sensor systems and other embedded systems, maintaining software and related databases, and performing software configuration management.

(CDRL A007, A008, A009, A013, A014)

4.7 Meetings, Conferences, Presentations, and Reviews

The contractor shall participate in and prepare presentations, papers, and posters. Examples include but are not limited to (CDRL A021):

• Concept and design reviews: System Requirements Review (SRR); Preliminary Design Review (PDR); Critical Design Review (CDR); Final Design Review (FDR); Test Readiness Review (TRR);

Pre-ship Review (PSR)

• Technical interchange meetings

• Conferences: as required at the Task Order level.

4.8 Safety and Systems Operability

The contractor shall report, evaluate, and provide recommendations for addressing potentially hazardous situations found in workspaces, manufacturing areas, test facilities, integration areas, storage facilities, pre-launch areas, launch facilities, and post-launch processing to support system safety tasks (e.g., trade studies, risk assessments, design reviews, risk management, reports, and waivers and deviations). The contractor shall monitor execution of engineering plans and analyze human factors engineering status in order to recommend how to optimize ground system interfaces, maintain the system at required levels, and eliminate design induced errors and inefficiencies.

5. Contract Management

5.1 The contractor shall 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. This shall include planning, organizing, staffing, directing and controlling cost, schedule, and performance at the prime and subcontract level to insure compliance with the requirements of multiple, concurrent task orders. The contractor shall have the ability to respond to and manage quick reaction task orders (e.g., 15-day response turnaround), technical work surge requirements, risk assessment and management, and knowledge capture and documentation, as required by the Government. (CDRL A016, A019)

5.2 Management of Personnel

5.2.1 General: The contractor shall provide for all management and support of contractor personnel.

The contractor shall accomplish tasks by providing qualified personnel possessing the appropriate combinations of education, training, security clearance and experience/skills. The contractor shall maintain a stable workforce while minimizing the impact of any turnover and/or disruptions to the Government and/or mission. The contractor shall 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.2 Key Personnel: The personnel listed below are considered essential to the work being performed on contract. Prior to proposing, substituting, removing, replacing, or diverting any of the specified individuals, the contractor shall notify the Contracting Officer ten (10) working days in advance and shall submit a written request and justification (including proposed substitutions) in sufficient detail to permit evaluation of the impact on this contract. No change in key personnel shall 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 five (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 for the individuals specified below.

The key personnel listed below may, with the consent of the contracting parties, be amended from time to time during the course of the contract to either add or delete personnel, as appropriate. In the case of a no-notice departure, the contractor shall immediately inform the CO and Government Technical Lead.

This written notification shall include the date and time the position shall be vacant, anticipated replacement date, and management corrective action, if needed, to ensure task mission remains on schedule toward completion.

Key Personnel positions include:

• Program Manager o Desire 10+ years program management experience related to DoD & major space systems/programs o Top Secret SCI clearance/eligibility o Desired education: Master’s degree in Business/Engineering/Other technical field from a regionally accredited institution o Desired certification: Program Management Professional certification equivalent to Defense Acquisition Workforce Improvement Act Level 3 Program Manager Certification, or demonstration of continued education.

• Chief Engineer o Desired 10+ years systems engineering experience related to DoD & major space systems/programs o Top Secret SCI clearance/eligibility o Desired education: Master’s degree in Science, Technology, Engineering, or Mathematics (STEM) from a regionally accredited institution o Desired Certification: Professional engineering certification equivalent to Defense Acquisition Workforce Improvement Act Level 3 Systems Engineering Certification, or, or demonstration of continued education.

• Lead Software Engineer o Desired 10+ years systems engineering experience related to space and/or ground systems o Top Secret SCI clearance/eligibility o Desired education: Master’s degree in Science, Technology, Engineering, or Mathematics (STEM), Information Technology, computer science or similar from a regionally accredited institution o Desired Certification: Professional software certifications or similar, as well as demonstration of continued education.

5.2.3 Transition-In Planning: The contractor will be given a transition period of up to 30 calendar days to provide qualified personnel that meet or exceed the stated requirements per Section 4. The transition period will begin from the effective date of the Basic Contract. During the transition period, all on-site contractor personnel shall 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, in order to fulfill contract requirements. The contractor shall follow the transition plan submitted as part of the proposal and inform the CO, Task Order Technical Manager and Government Technical Lead of progress throughout the transition period.

5.2.4 Transition-Out Planning and Future Contracts: The Contractor shall participate in organizational, system, process and information knowledge transfer from the Government team (Government, FFRDC, A&AS members), to include 30 days of overlap with existing contractors, as applicable. The contractor shall 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 CO, Government Technical Lead, and Task Order Technical Manager as part of the Task Order Management Plan (TOMP) to track progress to provide adequate transition training to the follow-on contractor. (CDRL A019)

5.2.5 Training: The contractor shall 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 CO prior to attending the training. These personnel shall 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.2.6 Identification: All contractor employees shall clearly identify themselves as “contractors” at all times. This includes all communications (telephone, mail, electronic mail (email) and faxes), meetings, attendance sheets, and documents. In addition, contractor personnel shall identify their company affiliation in email signature blocks. All contractor personnel shall 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.2.7 Surge requirement: Per section 2.1.5, the contractor shall be able to temporarily adjust manpower to support increased/decreased mission activities in order to meet customer needs. The contractor must ensure they can provide this type of flexibility. In the event of a change to mission activities, the CO will notify the contractor through an RFP, contract/task order modification, or contracts letter.

5.2.8 Cross-cutting support: The Contractor shall provide cross-cutting support, which optimizes the Government’s cost, schedule, and/or performance efficiencies. Cross-cutting personnel may support multiple task orders based on their functional expertise. Cross-cutting support is the integration of standard and surge workload functional expertise to support multiple mission areas and task orders within AFRL/RV.

5.3 Reviews, Meetings, and Conferences

5.3.1 Contract Kick-off Meeting: The Contractor shall arrange and attend a contract kick-off meeting with the CO, RV Director, Government Program Manager, Task Order leads, and other Governmental organizational representatives within ten (10) calendar days of contract award. The contractor shall coordinate the date, time and location via e-mail notification to the CO, RV Director and Government Program Manager and prepare a suggested agenda and presentation. The contractor shall take meeting minutes and provide these to the Government to capture actions and activities that transpired during the kick-off meeting.

5.3.2 Program or Task Management Reviews: The contractor shall conduct periodic Program or Task Management Reviews with the Government Technical Lead and relevant RVE Task Order Technical Managers as specified in the TOs. The agenda, date, and location of the review(s) will be mutually agreed to by RVE and the contractor. The contractor shall take meeting minutes and provide these to the Government to capture actions and activities that transpired at the review. The Government reserves the right to call in emergency reviews of specific tasks with a 1-day notice when mission requirements warrant such off-calendar reviews. (CDRL A020)

5.3.3 The contractor shall participate in design reviews, off-sites, technical interchange meetings, working groups, or technical conferences with Government and contractor organizations, as required by TOs.

5.4 Release of Information

5.4.1 Public Release: Any briefings, technical reports, papers, or presentations prepared by the contractor for public presentation shall comply with DFARS 252.204-7000, Disclosure of Information.

The contractor shall provide one copy each to the Contracting Officer, the Government Technical Lead, and to the TO Technical Manager at least 45 days prior to the scheduled release date for OPSEC review.

5.4.2 Acknowledgement of Sponsorship: In the release of information relating to this contract, such release shall 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 shall affect compliance with the requirements of the clause (if applicable) of this contract entitled "Security Requirements," FAR 52.204-2. The contractor shall include this requirement in any subcontracts awarded as a result of this contract.

5.4.3 Non-Disclosure Agreements: 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 shall provide a copy of each NDA to the CO and Government Program Manager.

5.5 Contract Performance: The Government Technical Lead for the RISE contract will conduct semi-annual (6 months) performance assessments for input into the Contractor Performance Assessment Reporting System (CPARS). Contractor performance will be assessed at the TO level in the following areas: schedule, cost management, program management, subcontractor management, and other areas determined relevant to the TO. TO performance evaluations will support the overall contract evaluation and performance rating. These findings will be synthesized and documented annually in CPARS.

Interim CPAR submission may be submitted to document excellent or subpar performance.

5.6 Subcontractor Management: The contractor shall be responsible for any subcontract management necessary to integrate work performed on this contract and shall be responsible and accountable for subcontractor performance on this contract. The contractor shall 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 CO.

5.7 Cost Control: The contractor shall demonstrate effectiveness in forecasting, managing, and controlling task order costs. The contractor shall provide total accountability, accuracy, disclosure, control, forecasting, estimating, and overall management of all cost-based control activities, including monthly status report, trip reports, invoices, proposals, and limitation of funds. (CDRL A001, A010, A011)

5.8 Location of Primary Performance: Performance shall 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 TOs. Specific sites will be identified in TOs and will address location support, facility access, and security requirements.

The Contractor shall collaborate with other contractors to work side by side within Government laboratories. These contractors may include summer students, interns, visiting professors, and collaborators from other institutions.

5.9 Temporary Duty (TDY) Travel: The contractor may be required to travel using commercial air, Government air, and other conventional modes. Travel arrangements will be based on individual tasks, and the cost of travel will be directly reimbursed from task funding. All travel (Outside Continental United States and Continental United States (OCONUS & CONUS)) requires prior coordination by the Government Technical Lead. Additionally, all OCONUS travel must be approved in advance by the CO or Government Technical Lead designated by the CO. Minimal local travel may be required. Travel to other Government facilities or other contractor facilities may be required. All travel requirements (including plans, agenda, itinerary, dates) shall be pre-approved by the Government Technical Lead or CO; and is on a strictly cost reimbursable basis. Costs for travel shall be billed in accordance with the regulatory implementation of Public Law 99-234, Federal Civilian Employee and Contractor Travel Expense Act of 1985 and FAR 31.205-46 Travel Costs and Joint Travel Regulations.

Billable travel costs are airfare, ground transportation, and per diem costs – not labor hours. The contractor shall, 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. The contractor shall be responsible for obtaining passports or visas and making travel arrangements to and from any CONUS location. The travel CLIN is intended to pay for travel occurring at the direction of the Government performed in conjunction with a specific trip authorized in a task order. Travel by clerical support personnel shall be approved in advance by the Government Technical Lead or CO.

5.10 Ethics: The Contractor shall present an unblemished appearance in regards to 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.

5.11 Data Rights: The Government shall retain unlimited rights to all data and deliverables developed under the RISE 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 shall be available for review at any time per Government request. Further data rights specifications will be documented in each Task Order.

6. Security Requirements

6.1 Clearance Requirements: The contractor shall establish and implement information and physical security programs governing their efforts in accordance with the applicable DD254 Contract Security Classification Specification. The contractor shall have the ability to process up to TS/SCI cleared personnel to perform the work required on this contract. At a minimum, contractor personnel shall be eligible to obtain a Secret clearance. Where certain task order activities have higher security requirements, the contractor personnel shall have a current DoD Top Secret/SCI clearance or higher, per

TO specifications. The Government will provide the contractor with system security classification guidance and instructions as required.

6.2 Technical Assistance Agreement (TAA): The contractor shall 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 shall obtain a TAA with each of the foreign nations identified by the Government Technical 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 shall maintain the TAA for the duration of the contract.

6.3 Traffic Laws: The contractor shall ensure all contractor employees comply with base traffic regulations.

6.4 Weapons, Firearms and Ammunition: Transport of personally owned firearms is governed in accordance with the Memorandum for Kirtland Air Force Base Personnel signed by the 377th Air Base Wing Commander dated February 16, 2017, Subject: Kirtland Air Force Base Privately Owned Weapons Guidance. A copy can be obtained by contacting the Government Program Manager or the Contracting Officer.

6.5 Government Data Systems Access

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

6.5.2 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.

6.5.3 Contractor personnel using any PRS information technology assets shall comply with all PRS computer security requirements. In addition, should contractor personnel require access to PRS computer networks or databases, they shall 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 shall notify the PM or Deputy PM within one workday of any contractor personnel who no longer requires an open account and shall take action to close the computer account with the appropriate PRS office within that same workday.

6.5.4 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 shall attend mandatory C4 systems security training.

6.5.5 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.

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

6.5.7 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). The contractor may submit a request to the PM that the Government grant contractor employee(s) interim access to the PRS C4 network while awaiting the results of a NAC. Interim access to the PRS C4 network will only be granted after the contractor employees obtain at least a local background file check, and have submitted the appropriate documentation to obtain a NAC. These requests will be processed in accordance with Government information security regulations and policy.

6.5.8 Communications Security (COMSEC) Monitoring. All communications with DoD organizations are subject to Communications Security (COMSEC) review. Contractor personnel shall be aware that telecommunications networks are continually subject to interception by unfriendly intelligence organizations. The DoD has authorized the military departments to conduct COMSEC monitoring and recording of telephone calls originating from or terminating at DoD organizations.

Therefore, contractor personnel are advised that any time they place a call to or receive a call from a USAF organization they are subject to COMSEC procedures. The Contractor shall assume the responsibility for ensuring wide and frequent dissemination of the above information to all employees dealing with official DoD information.

7. Associate Contractor Agreements

7.1 The contractor shall enter into Associate Contractor Agreements (ACA) for any portion of the contract requiring joint participation in the accomplishment of the Government's requirement. The agreements shall include the basis for sharing information, data, technical knowledge, expertise, and/or resources essential to the R&D Integrated Space Experiments (RISE) program, which shall ensure the greatest degree of cooperation for the development of the program to meet the terms of the contract.

7.2 ACAs shall include the following general information:

(1) Identify the associate contractors and their relationships.

(2) Identify the program involved and relevant Government contracts of associate contractors.

(3) Describe the associate contractor interfaces by general subject matter.

(4) Specify the categories of information to be exchanged or support to be provided.

(5) Include the expiration date (or event) of the ACA.

(6) Identify potential conflicts between relevant Government contracts and the ACA; include agreements on protection of proprietary data and restrictions on employees.

7.3 A copy of such agreement shall be provided to the CO for review before execution of the document by the cooperating contractors.

7.4 Nothing in the foregoing shall affect compliance with the requirements of the clause at 5352.209-9000, Organizational Conflict of Interest.

7.5 The contractor is not relieved of any contract requirements or entitled to any adjustments to the contract terms because of a failure to resolve a disagreement with an associate contractor.

7.6 Liability for the improper disclosure of any proprietary data contained in or referenced by any agreement shall rest with the parties to the agreement, and not the Government.

7.7 All costs associated with the agreements are included in the negotiated cost of this contract.

Agreements may be amended during the performance of this contract.

8. Contract Data Requirements List (CDRLs) The following list captures the applicable contract data requirements for deliverables:

Item Title A001 Contract Funds Status Report A002 Status Report A003 Scientific, Tech Reports A004 Test/Inspection Report A005 System Safety Hazard Analysis Report A006 Programmatic Environmental Safety and Health Evaluation Plan A007 Software Design Description A008 Software Requirements Spec A009 Software Test Report A010 Funds and Man-Hours Expenditure Report A011 Integrated Program Management Report A012 Purchase Order A013 Computer Software Products A014 Software User’s Manual A015 Systems Engineering Management Plan A016 Technical and Management Work Plan A017 Contractor’s Risk Management Plan A018 Data Accession List A019 Management Plan A020 Conference Minutes A021 Presentation Material A022 Scientific and Technical Reports Summary A023 Interface Control Document

A024 Government Property Inventory Report

9. Base Support

9.1.1 The Government will provide base laboratory support to the contractor. The contractor shall use base support on a rent-free, non-interference basis to include Government-controlled working space, material, equipment, services, or other support (excluding use of the Defense Switched Network (DSN)) which the Government determines can be made available at, or through, any Air Force installation where this contract shall be performed. Specific base support AI&T laboratories and equipment to be furnished are listed in Attachment 7. However, the specific building number and associated base support equipment listed are subject to revision upon notification by the Government.

Unless otherwise stipulated in the contract schedule, the contractor will use base support on a no-charge-for-use basis and the value shall be a part of the Government’s contract consideration. The contractor shall immediately report inadequacies, defective base support, or non-availability of support stipulated by the contract schedule, together with a recommended plan for obtaining the required support. The contractor is not authorized to incur any costs resulting from nonsupport prior to CO direction.