Enclosure_BB_-_RTOs.pdf

ENCLOSURE BB

REPRESENTATIVE TASK ORDERS

RFP 80GSFC18R0032

RTO 1 - New Lunar Mission

Task: New Lunar Mission Task Order: 1 Task Modification: 0

I. Summary of Changes in this Task Modification

This is a new task order under this contract.

II. Summary of Work This task is designed to provide Flight Dynamics support to the New Lunar Mission (NLM) program. The work described herein will cover both pre-launch analysis, ground system development, launch & early orbit operations, and routine mission operations for NLM. The NLM is the next step in the return to the Moon and will continue to build on our knowledge of the Moon by mapping resources, investigating possible landing sites for future human exploration, and understanding the history of the Moon.

III. Period of Performance The period of performance for this task will be from 01/01/2020 through 01/01/2021.

IV. Task Description The Flight Dynamics support for NLM will cover Phase C of the mission.

Current planning assumes an NLM launch date of January 1, 2023.

The current schedule for planning purposes is below.

• PDR: will have already been held on October 15, 2019

• CDR: July 15, 2020

The task support includes, but is not limited to, the following.

Meeting Support

• Technical meetings of the NLM Flight Dynamics Team will be biweekly

• The Task will provide a written monthly report assessing technical, staffing, and budget statuses

• Participate in Working Group meetings with Project and Science team members as directed by the task monitor

• Task personnel will participate in meetings related to operations planning and execution of mission rehearsals.

• The task will also help to coordinate support from the Flight Dynamics Facility (FDF).

• Provide support for Project reviews (e.g. SRR, MDR, PDR, CDR, MOR, ORR, FOR) as needed.

Documentation Support

Support will be required development and review of key mission documents.

These include but are not limited to the following.

• Critical Design Review (CDR) Package – development and review

• Flight Dynamics System (FDS) Requirements - development

• Interface Control Document (ICD) between the Project and the FDS – development and review

• Operations Procedures document – development

Analysis Support

The following lists the analyses that will be required from this task.

• Orbit Determination Error Analysis – Analysis will be performed to determine the amount of tracking data required to meet mission requirements for the different phases of the mission (e.g. cruise to lunar orbit capture, mission orbit, etc.).

• DeltaV Budget Analysis – Analysis will be performed to support in developing the DeltaV budget for the entire mission. This includes computing the deterministic and statistical maneuvers needed from separation through capture into lunar orbit. Also included will be an assessment of the stationkeeping DeltaV required for the 2- year lifetime.

All of maneuver analysis will be wrapped up to determine the DeltaV margin for the mission which can inform on the potential for an extended mission phase for NLM.

FDS Development

A Flight Dynamics System (FDS) will be developed to perform the duties necessary for operations with requirements collected in the FDS Requirements Document. The major functions of the FDS will include maneuver planning (for all phases), maneuver validation, maneuver

VI. Management Approach

Staff Allocation, Expertise, and Skill Mix

The contractor shall staff this work item with the appropriate skill mix and staffing level for the work.

Configuration Management

Flight Dynamics Systems and documents will be reviewed and signed-off by NLM Project Management.

Facilities

Appropriate IT devices to support the analyses, testing, 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.

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.

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.

VII. Travel Travel may be required to support working group meetings and reviews.

VIII. Work Location This work shall be performed at the contractor’s facility and at TBD Mission Operations Center located at GSFC.

IX. Reporting Requirements The contractor shall report status in person or via teleconference to the TM or designated alternates on a monthly basis. Reports shall include informal presentation of interim results, status of testing activities, and action item status. The contractor shall provide all 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 GSFC NMDB online library, as directed by the TM.

X. Security Requirements This task shall comply with IT security requirements as documented in the FDF IT security plan for all systems located in the FDF. FDF systems shall be maintained under the FDF Sustaining Engineering Task. Systems located outside of the FDF shall be covered under the Code 590 security plan and the Code 590 sustaining engineering support or the contractor sustaining engineering support depending on system location.

XI. Rights REQUIRED: The contractor shall adhere to the RIGHTS IN DATA – special works (FAR 52.227-17) as modified by NFS 1852.227-17. OR REQUIRED: The contractor shall adhere to the RIGHTS IN DATA – general (FAR 52.227-14) as modified by NFS 1852.227-14, Alternates II and III.

XII. References None

RTO 2 - VLST Flight Dynamics

Task: VLST Flight Dynamics Task Order: 2 Task Modification: 0

I. Summary of Changes in this Task Modification

Modification to Statement of Work for Very Large Space Telescope (VLST) Flight Dynamics Support. This modification extends the period of performance for one year.

II. Summary of Work

The Navigation and Mission Design Branch (NMDB) provides primary flight dynamics support to the VLST mission, which is a large observatory to be launched in May of 2020 into a Sun-Earth L2 libration point orbit. This task shall support NMDB in the areas of VLST orbit determination (OD) analysis, model and system development, trajectory and mission analysis, maneuver planning, analysis tools and ground system development, pre-launch, launch and early orbit operations activities. Prelaunch support includes supporting internal and Project-level simulations, rehearsals and testing, and preparation of launch products. Launch and early orbit operations support will continue into the Commissioning Phase, which is the first 6 months after launch.

III. Period of Performance

The period during which the work for this task shall be performed is from 10/15/2019 -10/15/2020.

IV. Task Description

The contractor shall maintain and follow a CMMI Level 2 compliant process for software development efforts. The contractor shall support the TM as needed including trade space analysis, requirements analysis, tools and techniques development, reporting to other project groups, as well as provide documentation for analyses performed, including mathematical models, and procedure/process and results. The contractor is expected to work in close coordination with government flight dynamics staff assigned to the mission, and with Flight Dynamics Facility personnel.

For each Subtask area, the contractor shall develop and maintain a repository which includes current and past documentation, an action item ticket system, as well as software code and scripts.

VLST Flight Dynamics Support

Ground System Development and Testing: The term ‘ground system’ encompasses all flight dynamics software used to support prelaunch analysis, testing and mission rehearsals, trending and trade analyses, and mission operations support. Analysis software packages, such as launch window analysis tools, are maintained separately from the flight dynamics ground system (FDGS), but are considered to be part of the overall ground system support for VLST.

The contractor shall maintain and update the VLST FDGS. This support includes developing requirements and specifications, defining interfaces, performing trade analyses, prototyping, and performing detailed design and specification creation as necessary to update the VLST FDGS. The FDGS shall support VLST during spacecraft testing, communications network and subsystems testing, mission rehearsals and eventually launch and mission operations.

The contractor shall maintain and update FDGS software and system components for a planned VLST Ground Segment Freeze Date of November 1, 2019. Maintenance shall begin immediately after Release 3.5, scheduled for delivery no later than the Freeze date, and may require negotiation and coordination with the Project for waivers during the overall Ground System Freeze. Release 3.5 shall include all functionality for launch, early orbit and the science mission support, and meet all Level 5 & 6 requirements.

Release 3.5 shall generate all products as required in the FDF to VLST Project ICD and will be completely integrated into the FDF and with FDF systems interfaces.

Development shall be coordinated through an online GIT Configuration-managed repository and via work item tracking in Atlassian Confluence and JIRA. Work items shall be mapped to use cases, requirements, design specifications and operations procedures developed during mission rehearsals and simulations. Work items shall be documented as needed via work item tickets, sections in larger documents, or individual documents.

These materials shall then form the core of operations and system documentation.

The contractor shall continue execution of a build/test/release plan (with associated schedule) for the FDGS and other ground system software, and update the plan at least every month. The contractor shall generate and maintain the requirements and functional specifications for the VLST FDGS and other ground system software.

Verification and validation methods shall be included as part of the requirements development process. Flight dynamics ground system requirements for the FDGS and other ground system software shall be developed in conjunction with Project teams, and submitted to and managed via the VLST DOORS system. The contractor shall lead a broad-based review of all Project requirements to fully establish which requirements the FDGS must comply with and to allow for traceability to those requirements from FDGS requirements.

Mission Analysis: The contractor shall perform mission analysis. Analysis efforts shall include updating and refining launch window analysis, evaluating ESA-provided launch vehicle mission analysis updates including the DAM-F delivery, Ariane 5 delta-qualification deliveries, and 2nd stage collision avoidance plans. Analysis also encompasses optimizing mid-course correction delta-V allocations to meet mission constraints, updating finite burn propulsion system models when additional data is available from the Project, updating contact predictions for tracking stations and networks, performing orbit determination analysis for launch, early orbit, MCC and stationkeeping (SK) maneuvers with various tracking scenarios as well as the mission science orbit. Other analysis may be required via Working Group support, if approved by the Task Monitor (TM). Analysis shall be fully documented as a technical memorandum.

Informal presentations of analysis results shall be made at the FDT internal team meeting; more formal Project-level presentations may be required. The contractor shall prototype and perform trade analyses as necessary. Analysis shall be planned and tracked in a task plan and schedule updated at least monthly.

Launch Window Analysis: The contractor shall support all effort related to launch window opportunity analysis and any software development required to support this effort. Analysis shall be as required from the VLST Project, but once required, this shall become an official deliverable item. Enhancement of launch window tools and software shall be as negotiated with the TM or their designee and shall strive to improve the quality, ease of use, and speed of producing results. Finally, support shall include documenting and reporting results to the Project and supporting TM presenting results to the Project and/or international partners.

Meeting and Review Support: The contractor shall participate in Project reviews and meetings as required. These reviews include Flight Operations System reviews, Technical Interchange Meetings, Commissioning Timeline meetings, Ground Systems Operations weekly meetings, Architecture, Rehearsal, Launch Segment, Contingency, MCC, Limits and Constraints and other various Project Working Group (WG) meetings.

The contractor shall participate in and record minutes for all official meetings supported and for the weekly Flight Dynamics Team (FDT) meeting, the monthly NMDB status meeting, the weekly FDT Management/Leadership meeting and other internal team meetings.

The contractor shall produce documentation and present at Operations Readiness Reviews, (ORR) dry run and final review, and support Project-level launch and mission operations readiness reviews and any peer reviews required by the NMDB.

Documentation for each review shall be delivered 2 weeks prior to the review. The contractor shall support in the resolution of review Requests for Action (RFAs) within 3 months or the next review, whichever is earlier unless otherwise directed by the TM.

As part of the review and meeting support, the contractor shall provide input and support for Level 4 and above requirements verification at the Project level, which may include writing and submitting Requirements Verification Reports and participating in the Requirements Verification Working Group.

Document Review: The contractor shall review and provide comments on relevant Project documents, including propulsion system modeling documents, DSN Operations ICD, the PSLA, the SN Interface Agreement Document, the Ground System Requirements

Document, the Flight Operations Document, the Launch Vehicle Interface Control Document (DCI), Mission Operations Documents (MODs), the Mission Operations Plan and other relevant documentation as required.

CCSDS Standards Implementation: The task shall work closely with NMDB CCSDS government and contractor personnel to promote usability of current standards in review and standards in development for VLST mission operations.

Pre-Launch Operations Support: The contractor shall support Spacecraft/Mission data flows, rehearsals, simulations and tests as required, including product generation and in-person realtime and offline support as approved by the TM. Product support shall leverage 3.5 materials and tools. Rehearsal, simulation and test support shall be provided from the FDF via the CIL and other operational interfaces, and may involve the backup FDF facilities and procedures. The contractor shall create an internal test plan, complete with test documentation, ‘truth’ test data to train FDT/FDF personnel and to ensure local operating procedures (LOPs) and software can support the nominal mission, as well as the most likely contingencies. The contractor shall generate post-test reports for internal and Project-level simulations. The contractor shall create and maintain a training test plan and matrix for FDT personnel, assessing the team’s abilities to support nominal and contingency mission operations. The contractor shall work closely with the TM, NMDB and FDSS III management to ensure the VLST FDT and the FDF is ready to support mission operations.

The contractor shall provide at least one trained FD Liaison person for support of Project rehearsals, simulations and tests; this person(s) is expected to be one of the FD Liaisons at the Science and Operations Center (S&OC) for the actual launch and early orbit operations.

Launch Operations Support: The contractor shall provide a cross-trained team consisting of at least 13 people (two 13-hr shifts plus backup) who can perform FDF liaison and shift lead support, orbit determination, tracking data evaluation, maneuver monitoring, reconstruction and calibration, maneuver planning and product generation during prelaunch and launch critical operations: prelaunch preparations, launch and early orbit, mid-course corrections, sunshield deployment, stationkeeping maneuvers, anomalies and contingencies. This period is expected to last between 1 to 6 weeks. The team will be reduced after this period to an early mission routine operations level of support, and then further to the routine operations support level of about 4 full time people.

The contractor shall provide at least one trained FD Liaison person he at the Science and Operations Center (S&OC) for the actual launch and early orbit operations (up to 72 hours).

Operations Integration and Coordination: The contractor shall coordinate across the entire FD team and with operations facility personnel to ensure all designs, operational agreements, and interfaces are within the capabilities of the FDF operations facility. The contractor shall coordinate with other FDF Operations Tasks and management to enable integration of FDGS and other software needed to support pre-launch support for rehearsals and simulations and preparation for launch and for actual launch operations.

The contractor shall also coordinate hardware and facilities needs for the VLST FDT during the prelaunch and postlaunch periods.

V. Deliverable Items and Schedules

At a minimum, the contractor shall deliver the items specified below. The delivery dates are based on the current Project schedule of and may change if the launch slips:

• Launch Readiness Date (LRD) of May 1, 2020

• Ground System Freeze at LRD minus 6 months, November 1, 2019

Deliverable Due Date

Final Launch Window update (based on Project providing final DAM-F data by L-6 months)

Due ~3 months after receipt of DAM-F trajectory data, but no later than (NLT) LRD minus 3 months.

Prelaunch operational products for S&OC, DSN, Malindi and SN

As documented in FDF-to- VLST ICD, DSN, SN and Malindi Project agreements

FDGS Release 3.5 Delivery and Materials NLT November 1, 2019

FDGS Verification and Validation post-Release 3.5 NLT February 1, 2020

FDGS and other VLST operations software freeze VLST GS software freeze date

Monthly Detailed work items Schedule/Plan update Monthly, or as negotiated with TM

Monthly Status Report input for NMDB and Project Monthly Status Reports, including a high level version of the Schedule/Plan

Monthly, or as negotiated with TM

Materials for FDT Operations Readiness Review NLT review minus 2 weeks

FDT Operations Readiness Review NLT LRD minus 5 months

Ready for launch April 28, 2020

Launch Support L-1 day through L+6 weeks

Early Mission Support L+6 weeks through L+6 months

Routine Operations Support L+6 months through end of task POP

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

b. Configuration Management

Systems and documents shall be covered under the Configuration Management Plan.

Configuration management for the FDGS shall be documented in the FDGS CM Plan, which shall be updated as necessary. The contractor shall configuration control and maintain the Mongo Database containing VLST data, the FDGS and the supporting tools.

Raw tracking data measurements, telemetry, and products sent and received shall be archived for no less than end of mission plus 5 years.

b.2 IT Security

a. Data shall be protected per NASA standards (this is for ITAR, EAR, CIU data).

c. Facilities

Appropriate IT 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 on-site and off-site facilities as required, and to install any required tools and utilities on the contractor’s equipment.

The contractor shall explore options for high performance computing including cloud services.

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. Government Furnished Facilities, Equipment, Software and Other Resources

The Government shall provide accounts 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.

The government shall provide computing resources in the building 11 MESA Lab, as well as storage of data on the MESA file server.

VII. Travel

Local travel to STScI and GSFC will be required.

There may be non-local travel for this task. Possible trips include the following:

• LV TIM in Paris France, 4-day meeting (1 person)

• VLST Project-level meeting in Los Angeles, CA (1 person)

Other travel may be required for this task and shall be negotiated with and pre-approved by the

TM. This includes conference attendance to venues such as ISSFD, AIAA/AAS Astrodynamics

Specialist Conference, IEEE, and FD Operations support conferences.

VIII. Work Location

This work shall be performed at the contractor’s facility and the Goddard Space Flight Center, primarily in the Flight Dynamics Facility (FDF). FD Liaison support will be at the STScI S&OC in Baltimore.

Reporting Requirements

The contractor shall report status in person or via teleconference to the TM or designated alternates on a weekly basis at the FDT meeting. Reports shall include informal presentation of interim results, status of development activities, and action item status. The contractor shall provide all reports at least one day in advance of the monthly NMDB or VLST Project meetings 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 report technical and management status including Risk, Schedule and Staffing at the weekly FDT Management/Leadership meeting. The schedule/plan shall be reviewed and updated at least every month.

Within 14 calendar days of award of this Task Modification, the contractor shall submit to the TM a candidate schedule/plan structure to serve as the VLST FDT schedule of record. This candidate structure shall include:

• Relevant VLST Project milestones and the expected FDT support required as understood at the time of schedule/plan creation or update. The Project milestones shall be provided by the TM or representative twice a month, based on the VLST Project Calendar. Project milestones include operations reviews, spacecraft test bed/simulator releases, launch vehicle TIMs, data flow tests, simulations, tests and rehearsals, etc.

• All VLST FDT milestones, including those related to development of the FDGS, Launch Window Analysis support, internal and external testing and simulations, and software/hardware/team integration into the FDF shall be included.

• A list of activities at both the 1) components and system feature-level and 2) detailed activities (of no more than 4-weeks duration) required to support analysis, internal and external tests/simulations/rehearsals, FDGS documentation, development, quality review, testing, and integration of components into appropriate systems. This level includes resources or organizations responsible for the activity.

• Dependencies on work items leading up to all milestones shall be included. In particular, milestones and activities that drive and/or are driven by external interactions, as they are understood at the time of planning or update, will be connected appropriately in the scheduled work items, to properly gauge inter-relations between the VLST Project and FDGS development, as well as operations planning and support.

The candidate schedule structure will be reviewed and returned within 5 business days with one of three status ratings

• Approved as submitted – The schedule structure shall become the schedule structure of record

• Approved with comments – The schedule structure, when modified to align with comments then becomes the schedule structure of record

• Rejected – The candidate schedule must be updated and re-submitted for approval

Monthly, an updated schedule/plan shall be submitted to the TM in MS Project format illustrating the VLST lifecycle through commissioning (L+180 days) at the components and system feature-level. The schedule/plan shall include all work activities updated with proper status (%complete, dependencies, relevance to critical path). This schedule/plan shall be included in the FDSS-II Monthly report.

Monthly, an updated schedule/plan shall be submitted to the TM in MS Project Format showing detailed activities required to support analysis, internal and external tests/simulations/rehearsals, FDGS documentation, development, quality review, testing, and integration of components into appropriate systems illustrating the current week and the next two calendar months.

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 GSFC NMDB online library (Docushare) as directly by the TM.

IX. Security Requirements

This task shall comply with IT security requirements as documented in the FDF IT security plan for all systems located in the FDF. FDF systems shall be maintained under FDSS II Task 1 FDF Sustaining Engineering Task. Systems located outside of the FDF shall be covered under the Code 590 security plan and the Code 590 sustaining engineering support or the contractor sustaining engineering support depending on system location.

X. Rights

REQUIRED: The contractor shall adhere to the RIGHTS IN DATA – special works (FAR 52.227-17) as modified by NFS 1852.227-17. OR

XI. References

NONE

RTO 3

Flight Dynamics Facility (FDF) Mission Development and Operations

Summary of Work

This task order statement of work (SOW) describes hypothetical support requirements for missions new to the FDF. The purpose of including an RTO for FDF operations support is to allow the contractor to illustrate the range of experience, skills, and innovative processes that it would apply to the development of the capabilities needed to support these missions.

The support required by this statement of work covers two areas, described in detail in Section V of the SOW below:

Ground System Development and Launch Support for the Achilles Launch Vehicle (ALV)

Launch and Early Orbit Support to the Three Blind Mice (TBM) Mission

The contractor shall expect to work closely with the Government’s Task Monitor (TM) for this task, and to work with NASA and contractor personnel as well as NASA’s partners in other Government agencies, industry, and academia when needed to accomplish the technical objectives of the task.

Details of the work by subtask are provided below. This work will generally require the contractor to utilize a mix of GSFC in-house and commercial-off-the-shelf orbit determination and mission planning software in performance of the work items. The contractor may, in some situations, propose the use of their own proprietary software.

The technical and cost advantage to the Government should be clearly justified.

Period of Performance

The period during which the work for this task shall be performed begins January 1, 2020 and ends on December 31, 2020.

Work Location

All (100%) of this work is expected to occur at the FDF at Goddard Space Flight Center

(GSFC).

Government Property

The Government will provide the facility and facility services for mission support functions performed onsite at GSFC. Within these onsite facilities, the Government will provide office and workstation furniture that are required to manage and operate the spacecraft and its ground support elements.

A summary of other Government-furnished equipment that may be applicable to this task is available in the FDSS Bidder’s Library.

Specific Tasks The contractor shall perform the following specific tasks during the period specified in Section II.

Ground System Development and Launch Support for the Achilles Launch Vehicle (ALV)

The ALV is a new launch vehicle being developed by NASA to deliver large payloads to low earth orbit. The organization at Kennedy Space Center (KSC) that is responsible for building the vehicle has just entered into an agreement with the Space Network (SN) and the Near Earth Network (NEN) to provide vehicle command and telemetry capabilities to the operations center at KSC for the maiden flight on November 15, 2020. The SN and the NEN have just required the FDF to provide the acquisition data for the vehicle.

Nothing else is currently known about the ALV.

The contractor shall perform the following activities:

• Develop an assessment of infrastructure (hardware, software, interfaces, etc.)

requirements needed to support the vehicle’s maiden flight.

• Develop the capabilities (including proposing and performing relevant tests) needed for this support, as identified in the above assessment.

• Support prelaunch preparations, including testing, simulations, training, documentation, reviews, and analysis as needed.

• Launch day support, including relevant product deliveries.

• Post launch analysis, assuming support to future ALVs.

Launch and Early Orbit Support to the Three Blind Mice (TBM) Mission

The TBM mission consists of three university-built cubesats being deployed from the ALV during its maiden launch on November 15, 2020. The university has been planning to use Joint Space Operations Center (JSpOC) Two Line Elements (TLEs) for navigation.

The university has recently been told that these TLEs may not meet their navigation requirements and has reached out to the FDF for support.

The contractor shall perform the following activities:

• Provide a report of recommendations to the TM by February 28, 2020 addressing options for meeting the mission’s navigation requirements.

Deliverable Items and Schedules

All deliverables are specified in Section V.

Travel

Non-local travel is not required for this task. The contractor may propose non-local travel for technical meetings or other activities that enable the completion of tasks listed in this SOW.

Reporting Requirements The contractor shall report status to the TM and the FDF Operations Director on a daily basis. The contractor shall propose the process by which these Government representatives are apprised of the status of the activities on this task and the process by which open actions and concerns are tracked to closure. The contractor shall support the preparation of materials for technical discussions and presentations when needed. The contractor shall compile the results of technical analyses into technical reports for archival purposes and when appropriate, into conference-quality papers for external audiences.

Security Requirements When working inside the GSFC perimeter or online any GSFC networks, the contractor shall maintain compliance with all GSFC IT security guidelines. Access to classified information is not required for this task.

Risk Management Requirements The contractor shall perform risk management according to all applicable NASA policy directives, including, but not limited to, the applicable versions of NPR 8000.4 and/or

NPR 7120.5.

Electronic Information Technology Compliance The contractor shall maintain compliance with all applicable NASA policies concerning electronic and information technology accessibility, including, but not limited to, 36 CFR Part 1194, Section 508 of the Rehabilitation Act of 1973, etc., or document exemptions based on NASA-approved rationale and documentation, including but not limited to NASA Procurement Information Circular 05–01.