Task 37-7 Technology Advancement and Tech Transfer.pdf

Omnibus Multidiscipline Engineering Services II

(OMES-II)

All deliverables and requirements must follow the guidelines in NNG17CR69C with no exceptions

Task Order Statement of Work (SOW) Date: 2/9/2021 Task Name: Technology Advancement & Tech Transfer Task No. / Mod: 37/7 Task Monitor (TM): Redacted Contract number: NNG17CR69C Contract SOW Reference: Function 3, Sub Section

Mod Summary: this mod incorporates work that was previously done on OMES II Task 41, as per updates below.

I. Scope

a. Background – The purpose of this task is to provide management, engineering, and technical support to the Technology Advancement & Technology Transfer group within the Satellite Servicing Projects Division. The purpose is to advance and modify existing technologies and to work towards both transferring technology to industry and infusing technology into other governmental efforts. Elements of the work on this task may require TS/TK clearance in order to perform the work.

b. Summary of work – The work to be performed and completed on this task is summarized in the subtasks below. It includes engineering support for technology advancement and modification of existing flight hardware for purposes of on orbit refueling and servicing with the strategic effort of transfering technology to industry and infusing the technology into other government efforts. The work is primarily on-site work.

c. Required skills/knowledge - All positions must be comfortable working in a multi-contractor, civil service environment with the ability to communicate throughout the organization. Some work requirements may require the workforce to hold a clearance.

1) Space flight Senior Systems Engineering with scientific and hardware experience in writing requirements and building flight hardware (experience with NASA scientific payloads on various platforms including balloon payloads, serviceable space flight payloads, other NASA space flight programs) and developing science Level 1 requirements that are traceable to flight hardware requirements. Science advocacy experience is recommended.

2) Systems Engineering expertise with space flight hardware design, development, I&T, and operations experience for both on-orbit serviceable hardware as well as flight

All deliverables and requirements must follow the guidelines in NNG17CR69C with no exceptions hardware not designed for servicing is required. Flight hardware management experience for delivery of hardware to systems integration across many subsystems is required. Experience planning and developing complex integrated master schedules.

Experience establishing requirements and flowing them subsytems. On-site.

3) Systems Engineering expertise with on-orbit servicing thermal systems design, development, I&T and operations support experience. Thermal Model development and correlation experience required for complex space flight systems. This experience includes experience with passive control and active control systems for instrument and spacecraft systems. On-site.

4) Systems Engineering expertise with on-orbit servicing systems experience with instrument payload development, servicing mission design and implementation.

5) Mechanical design engineering expertise with experience developing space flight hardware for flight systems that includes experience working with composite flight structures and mechanisms. I&T experience, including space flight environmental testing is recommended. Interface definition and control experience is recommended.

On-site.

6) Engineering expertise to develop flight-like mock-ups with experience meeting schedules and low-cost constraints. Requires safety and GSFC handling restraints knowledge and ability to complete analysis to assure GSFC requirements are met.

Mock-ups will be of various levels of fidelity.

7) Project and Program Management support for SSPD.

8) Engineering expertise with on-orbit servicing mission design support for various systems as servicing capabilities are defined. This experience will preferably include some engineering experience with HST human servicing in areas such as mechanism design, electrical systems design including blind mate connector experience, space flight modular system experience. Flight system I&T of modular systems will be preferential for these required skills.

II. Period of Performance

Period of Performance begins 04/03/21, continuing through October 31, 2021.

III. Subtask Description

1) Project Management Support for SSPD

Provide programmatic support to the Satellite Servicing Projects Division as directed by the task monitor. When requested and authorized by the task monitor, this support will be specific to Division initiatives and will consist of resource analysis, program management support, inventory and property management, and technical advising. This subtask will also be used for as-needed engineering support at the determination of the task monitor. The support may be for electrical, mechanical, and other technical advisory support. This subtask does not include work that is specific to active Projects within the division.

There are four reporting IDs on this subtask:

• Exis project management: This effort supports general contractor management activities, as well as ad-hoc support requested by the task monitor. This low-level effort is for administrative support as well as general engineering advice and support.

• CTI Advancement: This is a contingent effort that is not expected to have on-going activity. The effort is to support as-needed engineering for the CTI optical sensor. This sensor flew on RRM3, and also resides within other areas on GSFC.

• NavCube: this is for low-level general support requested on an as-needed needed basis to support scoping and ordering NavCube part procurement.

• LIDAR technologies: this is for low-level engineering support requested on an as-needed basis to support LIDAAR technology development.

2) Technology Advancement & Tech Transfer:

Provide systems engineering support for advancing existing technologies and supporting both the transfer of those technologies to industry and infusing those technologies to other governmental entities. These efforts are in support of new concepts and potential redesigns of existing concepts for applications on missions of opportunity or as relate strategically or directly to satellite servicing. Provide analysis and design efforts to assess the viability of the potential concepts and provide systems engineering support to advance the concept to a viable design.

a. Assess potential concepts for implementation onto the missions of opportunity as identified.

b. Provide mechanical engineering and design support to evolve existing designs or develop alternative uses for existing designs for use on future serviceable spacecraft and payloads.

c. Support the design, development and build of mock-ups for designs as necessary.

d. Provide engineering expertise for specialized systems SSPD is developing from existing project technologies.

e. Work with SSPD management to customize, modify, or redesign SSPD technologies to accommodate other customer or missions requirements.

f. Support SSPD initiatives to commercialize technologies, transfer technologies to industry, and infuse these technologies to other government efforts.

There are three reporting IDs to this subtask:

• Technology Transfer: On an infrequent basis, the customer may request the contractor team to provide support to the division’s effort to develop technologies transferable to other government agencies or to commercial entities. This reporting ID is intended to capture the resources required for developing products (example- prototypes, presentations, documents, CAD drawings, edits to existing products, etc) to support this effort.

• SW Development for Technology Transfer: A small level of effort to provide software support on an ass needed basis.

• Unbilical Support: This is a specific effort to provide input, guidance, and advice regarding electrical and mechanical umbilical interfaces. This is anticipated to be systems engineering support, however when necessary the team may develop models, drawings, prototypes and hardware, presentations, and analysis products for various umbilical designs.

3) Refueling Adapters:

The contractor will provide engineering support in the advancement and modification of cooperative servicing valves and related technologies into next phase refueling adapters, used to facilitate on-orbit refueling. For example, the cooperative servicing value (CSV) is an SSPD developed refueling valve that can be modified to accommodate different on-orbit transfers at different flow rates and for different fluids/commodities. This work may also include the redesign or retasking of other existing SSPD technologies related to refueling and servicing, such as mechanical platforms, mechanisms, robotic interfaces, visual fiducials, fluid transfer and other items that facilitate refueling.

There are two reporting IDs for this effort. SSPD is working with NASA HQ and STMD to develop refueling adapters for multiple flight applications.

• Refueling Adapters: The contractor will support continued development of refueling adapters as requested by the division. In general, these adapters will bemechanical in nature and may have increased design tolerance. Additional adapters may be developed that may require electrical, mechanical, and fluid interfacing. When necessary, the team may develop models, drawings, prototypes and hardware, and analysis products for multiple adapter designs.

• Fluid Transfer Coupling: The contractor will support the continued development of the NASA Docking System Block 2 (NDSB2) Fluid Transfer Coupling (FTC) which consists of three different pairs of fluid couplings. The future of FTC is uncertain at this point. The design may or may not be selected as part of the final NDSB2 architecture. The GSFC FTC team will continue work on the FTC, as directed by the TM. The FTC Team will mature multiple CAD models, drawings, and analysis products for each FTC configuration as if proceeding to proto-flight ready status. Travel to support further development and providing development products and presentations may be required. Prior to a selection decision from NASA Docking System management, products and presentations for internal NASA peer review(s) may be required.

4) CAESAR Support:

The contractor will provide engineering and Robotic support for the CAESAR project in support of SSPD to complete the design, development and mission support of the robotic arm development for CAESAR. This includes support to assure that interfaces and performance of the robotic arm meet CAESAR mission requirements. The engineering support will provide documentation of the decisions and analysis required to support the mission decisions that assure that the design closes to meet mission requirements. This work is completed and the subtask can be closed effective July 2019.

5) Cooperative Client Study:

The contractor will provide engineering resources that will explore the addition of cooperative servicing features to various client vehicles. Cooperative servicing features are expected to facilitate cooperative rendezvous and refueling, servicing, and modularity of instrument and components. Engineers will need to evaluate client vehicles, perform assessments to identify applicable servicing features, recommend solutions, and robotically test recommended features in the customer’s robotics facilities. Travel and minimal ODCs may be required with task monitor’s approval and direction.

6) KArLE DALI Support:

KArLE DALI is the Potassium-Argon Laser Experiment (KArLE) as part of the Development and Advancement of Lunar Instrumentation (DALI). KArLE will determine the age of lunar rocks through potassium-argon dating. The KArLE instrument uses a mass spectrometer like the one developed for the Robotic External Leak Locator (RELL), previously under Task 16.002. The contractor will provide engineering oversight and technician support to complete the manufacture, integration, and test of the KArLE DALI instrument as defined by the TM per direction from the instrument development scientist.

7) Robot Operating Software:

This effort will support robotics software & algorithm development using open source code. The team is expected package existing software and algorithm products for open source deployment, as well as developing new software or algorithms as needed to advance the open source deliverable. The team may work in conjunction with ARC and JSC personnel to support activities. The contractor will provide resources that will develop appropriate code, corresponding support, code/algorithm documentation, and presentation products.

8) CCRS RTAS Support:

The contractor will provide low-level resources that will support the development of the CCRS robotic transfer arm system (RTAS). The work will be largely performed by other groups but will require assistance from the 480 contractor team as needed. This effort will consist of engineering and administrative support, as well as possible facility coordination. Contractor will coordinate robotic system procurements. There are two subtasks to this effort:

• The contractor shall provide basic low-level engineering, administrative, and facility support to the CCRS RTAS project team.

• The contractor shall study how the existing Alpha2 controller design can be adapted for CCRS.

This will include what changes are needed to meet the RTAS requirements and interface to the MUSTANG architecture. The team will also support the proposed development plan to support the CCRS schedule to meet deliverables for the controller to RTAS and Avionics. As needed, the contractor will also provide ROM cost/schedule estimates to provide the GSFC team the necessary information to determine a contractual path forward for utilizing the Alpha2 design in RTAS, which the team has concluded is the optimal programmatic and technical solution for

CCRS.

9) DREAM RACS:

This effort is for the development of a study plan, i.e. a Concept of Operations (CONOPs) for a mission to host a client vechicle (CV) on the host vehicle (HV), and for operational activities including pre-launch planning, rehearsals, and ground activities before, during, and after launch. To be included will be rendezvous proximity operations, docking, robotic activities, on-orbit operations, disposal and other activities required for the demonstration mission. The contractor team is expected to provide the following support:

1) As necessary, collaborate with other partners, including exchange of information written as well as verbal. Written information may include design documents such as ICD, CAD and other information identified in the course of the study.

2) The final product from this study shall be the necessary aspects of a CONOPs outlining a plan to enable the CV for the assembly space mission.

10) Robotic Engineering and Infrastructure Support

Provide the engineering, technical, and procurement support to allow for the daily operations of the robotic simulation platforms located in building 27N and building 29, room 150, and other facilities, for the ExIS. Responsibilities include managing, maintaining, controlling, and ensuring all robotic system safety procedures and policies are maintained and followed.

Provide the procurement support to acquire the systems and components needed to support the operations of the robotics team. Provide electrical/mechanical fabrication and assembly support to the robotics team. This effort also includes providing access to outside robotic consultants that have unique expertise that cannot be identified with the Goddard workforce.

11) REU JCB Support

Provide engineering support and maintenance for the delivered Robot Electronics Unit (REU)-Legacy Rack, Single Joint Actuator racks, and Advanced Tool Drive System Electronics Support Racks. This includes, but is not limited to:

• FPGA updates

Monthly Deliverable Report The contractor shall provide no later than the 10th working day following the close of the contractor’s monthly accounting period a 533M for each individual subtask and a summary 533M at the total task level. If it is not possible to provide the individual 533M at the subtask level, the contractor shall provide on the 10th working day following the close of the contractor’s monthly accounting period a break out of hours and costs by subtasks to the Contract Resource Analyst, Contracting Officer, and the Task Monitor. The report shall include current period hours and costs, cumulative to date hours and costs, and cumulative costs with a one-month cost plan. When needed, the contractor shall make adjustments to the distribution of costs, layout of the report and change reportable elements as specified by the Task Monitor and/or the Project Resource Analyst.

A supplemental excel-based monthly report spreadsheet shall be provided that includes by element of cost, by Subtask identified within the SOW, the current period hours and costs, cumulative-to-date hours and costs, cumulative costs with a one-month cost plan, and month+1 estimate-to-complete hours and costs. Additional Supplemental reporting may be requested as needed.

02) Management Approach

a. Staff Allocation, Expertise, and Skill Mix

The contractor shall staff this work item with the appropriate skill mix and staffing level for the work, including initiating paperwork for individuals to perform classified work at the Top Secret level if needed.

b. Configuration Management Systems and documents will be covered under the Satellite Servicing Projects DivisionConfiguration Management Plan.

c. Facilities Appropriate Information Technology devices to support the analyses, specification development, and report development are required. It shall be the contractor’s responsibility to provide and set up local workstations and network connections at the contractor’s off-site facilities as required, and to install any required tools and utilities on the contractor’s equipment.

d. Risk Management and Best Practices

The contractor shall manage schedule, cost, and technical risk through monitoring and reporting of progress and performance metrics, identifying issues well in advance of negative consequences, recommending corrective action to the TM, and implementing corrective actions with the compliance of the TM.

e. Performance Metrics

The work performed for this task will be evaluated by the TM based on the technical merit of the work complete. The TM shall develop detailed performance metrics that shall reflect the contractor’s performance in meeting specific mission requirements, deliverables and delivery schedule, and the contractor cost. Technical evaluation of the task performance is a subjective combination of performance metrics, technical quality of deliverables, cost control, significant events, innovations and meeting requirements set forth in the SOW.

Subtasks will be evaluated as follows:

1) Percent complete of subtasks

2) Planned vs Actual

3) Delivery dates

f. Government Furnished Facilities, Equipment, Software and Other Resources The Government will provide account and passwords to government-furnished workstations where existing versions of various relevant software packages shall be maintained. It shall be the contractor’s responsibility to complete any GSFC required security-related training courses.

g. Quality Assurance Requirements

(See Clause I.1 1852.216-80 TASK ORDERING PROCEDURE (d) (4) and QA plan)

The contractor shall comply with the SSPD Quality Assurance Plan, available on the SSPD Drive for flight hardware.

As applicable, the Contractor providing technical services shall comply with all CMMI Level 2 processes established for the Project and deliverable products. Applicable requirements include, but not limited to:

NPR 7120.5D NASA Space Flight Program and Project Management Requirements NPR 7123.1A NASA Systems Engineering Processes and Requirements GPR 7120.1C Project Management GPR 7120.5A Systems Engineering Note that due to the technology development nature of the work completed in Technology Advancement & Tech Transfer, the requirements of NPRs and GPRs may be tailored under risk-informed project direction and will be documented in the Project Plan for those projects.

03) ODC (Travel and Procurement) (See I.1 1852.216-80 TASK ORDERING PROCEDURE d(6), please provide a BOE for all proposed ODC’s to determine the reasonableness)

Travel may be proposed for special training needs and other engineering support task activities as directed by the Project. Significant travel is not expected.

Other Direct Costs may arise as needed but are not expected to be significant.

04) Work Location This work shall be performed primarily on-site at the Goddard Space Flight Center, but the contractor may be required to perform some work at the contractor’s facility, and at other NASA/non-NASA facilities.

05) Reporting Requirements

a. Weekly or Bi-weekly status report The contractor shall generate the Performance Reports every week to be delivered to the TM.

The weekly reports shall include, as a minimum, a summary of the weeks highlights/accomplishments, milestones/schedule/deliverables, risks and customer meetings.

In addition, reports in person or via teleconference to the TM or designated alternates on a weekly basis.

b. Monthly Progress Reports The contractor shall provide monthly technical and schedule progress reporting to adequately describe the activities of the contractor team to the TM. The contractor shall provide monthly cost reporting in accordance with the WBS and subtask elements. The contractor, including subcontractors, shall be available to attend monthly status meetings as necessary. Monthly Reports shall include informal presentation of interim results, status of development activities, and action item status. The contractor shall provide all monthly reports at least one day in advance of the monthly meeting via email, and maintain an email distribution list with the concurrence of the TM. The contractor shall also support the TM in the preparation of status reviews for internal and external funding agencies. The contractor shall comply with any and all additional requests for status meetings and reports. The contractor shall deliver all documents in portable document format (PDF) electronic form to the TM, or as directed by the TM.

c. Monthly Subtask Report Spreadsheet

The contractor shall provide a break out of hours and costs by close of business on the 15th of each month to the Contract Officer, Contract Resource Analyst, and the Task Monitor. The report spreadsheet shall include current period hours, costs, cumulative-to-date hours and costs, and cumulative costs with a one-month cost plan. When needed, the contractor shall make adjustments to the distribution of costs, layout of the report and change reportable elements as specified by the Task Monitor and/or the Project Resource Analyst.

06) Security Requirements

The contractor shall comply with Information Technology Security procedures and requirements as defined by NPR 2810.1A in the performance of this task. In addition, the contractor shall comply with all applicable federal rules and regulations and agency directives.

The Contractor shall adhere to project requirements regarding ITAR related information, as controlled by the ITAR, 22 CFR 120-130, by the U.S. Department of State. Any transfer of controlled information to a foreign person or entity requires an export license issued by the U.S.

Department of State or an ITAR exemption to the license requirement prior to the export or transfer.

This task may require personnel to have clearance at the Top Secret Level, with SCI to handle classified data and participate in classified meetings.

07) Safety

The OMES-II Safety/Mission Assurance Officer shall:

• Ensure all contractor personnel understand their safety responsibilities and follow safe practices for all lab and office operations.

• Ensure branch training requirements for contractor employees are implemented.

• Attend safety related training applicable to the operations under their area of responsibility.

The contractor personnel shall:

• Follow safety requirements when performing any task, keeping their workplace in a safe manner.

• Attend all required training, set forth by the OMES-II Safety/Mission Assurance Officer, ensuring certifications are current.

08) Data Rights This SOW shall adhere to the following Data Rights clause, as stated in this contract: “the default Data Rights clause under this contract is FAR 52.227-14 RIGHTS IN DATA-GENERAL as modified by NASA FAR Supplement 1852.227-14-Alternate II and Alternate III and GSFC 52.227-90. Any exceptions to this clause will be covered by FAR 52.227-17 RIGHTS IN DATA-SPECIAL WORKS as modified by NASA FAR Supplement 1852.227-17, and, if applicable, GSFC 52-227.93.”

09) Applicable Documents

In the performance of this task, the contractor shall comply with NASA and GSFC policy documents as they apply to the flight and developmental work, including but not limited to:

NPR 7120.5, NPR 7120.8, NPR 7123, GEVS, NPR 7150.2, GSFC Technology Development Constitution.

10) References

None.