Attachment A - Statement of Work - 03-23-23 - Final.pdf

RANGE OPERATIONS CONTRACT II

ATTACHMENT A

NATIONAL AERONAUTICS AND SPACE

ADMINISTRATION (NASA)

GODDARD SPACE FLIGHT CENTER (GSFC)

WALLOPS FLIGHT FACILITY (WFF)

STATEMENT OF WORK

CONTRACT 80GSFC19C0013

March 23, 2023

TABLE OF CONTENTS

1. DESCRIPTION OF SERVICES

2. GENERAL

3. PERFORMING RANGE SAFETY FUNCTIONS IS NOT THE RESPONSIBILITY OF THE CONTRACTOR.

HOWEVER, MANY SYSTEMS THAT ARE USED BY RANGE SAFETY PERSONNEL SHALL BE MAINTAINED, SUSTAINED AND SOMETIMES OPERATED BY THE CONTRACTOR. PROGRAM MANAGEMENT

3.1 PROGRAM MANAGEMENT REPORTING

3.1.1 Weekly Activity Report

3.1.2 Monthly Status Report

3.2 MISSION PREPARATION PRODUCTS AND REVIEWS

3.2.1 Instrumentation Support Review

3.2.2 Range Readiness Reviews

3.2.3 Launch Readiness Reviews

3.2.4 Post Mission Summary Report

3.2.5 Post Mission Report

3.3 PERFORMANCE METRICS AND REPORTING

3.3.1 Instrumentation System Availability

3.3.2 Data Systems Performance and Reliability

3.3.3 Radar Systems Performance

3.3.4 Telemetry Systems Performance

3.3.5 Mission Success Criteria

3.4 CONFIGURATION MANAGEMENT

3.5 ALTERNATE FACILITIES OPERATIONS

3.6 HEALTH AND SAFETY MANAGEMENT

3.7 PHYSICAL SECURITY MANAGEMENT

3.8 HUMAN CAPITAL MANAGEMENT

3.9 SPECIAL CONSIDERATIONS

3.10 FINANCIAL MANAGEMENT

3.11 EDUCATION AND OUTREACH

4. INTEGRATED RANGE SERVICES MANAGEMENT

4.1 OPERATIONS PROJECT MANAGEMENT

5. RANGE SERVICES

5.1 MAINTENANCE AND SUSTAINMENT SERVICES

5.2 RANGE ENGINEERING AND TECHNOLOGY DEVELOPMENT

5.3 NEW SYSTEMS TRANSITION TO OPERATIONS

5.4 TELECOMMUNICATIONS ENGINEERING

5.5 INFORMATION TECHNOLOGY AND RANGE NETWORK ENGINEERING SERVICES

6. TELEMETRY OPERATIONS SERVICES

6.1 MOBILE TELEMETRY OPERATIONS

7. RADAR OPERATIONS SERVICES

7.1 PRECISION TRACKING RADAR OPERATIONS

7.2 SURVEILLANCE RADAR OPERATIONS

7.3 RESEARCH WEATHER AND SCIENCE RADAR SERVICES

8. RANGE CONTROL CENTER AND MISSION OPERATIONS CONTROL CENTER SERVICES

8.1 RANGE CONTROL CENTER SERVICES

8.2 MISSION OPERATIONS CONTROL CENTER SERVICES

8.3 RANGE DATA PROCESSING AND DISPLAY OPERATIONS

8.4 RANGE DATA SYSTEMS

8.5 RANGE SURVEILLANCE AND RECOVERY OPERATIONS

9. RANGE COMMUNICATIONS, TIMING, AND COMMAND SERVICES

9.1 RANGE COMMUNICATIONS AND FREQUENCY MONITORING OPERATIONS

9.2 AIR-TO-GROUND COMMUNICATIONS OPERATIONS

9.3 COMMAND OPERATIONS

9.4 RANGE TIMING AND COUNTDOWN OPERATIONS SERVICES

10. VIDEO/PHOTOGRAPHY (OPTICAL)

10.1 VIDEO/PHOTOGRAPHY REQUIREMENTS

10.2 OPTICAL TRACKING OPERATIONS

10.3 VIDEO SURVEILLANCE OPERATIONS

10.4 DIGITAL PHOTOGRAPHY AND VIDEO SERVICES REQUIREMENTS

10.5 VIDEO DISTRIBUTION REQUIREMENTS

10.6 GRAPHIC SERVICES REQUIREMENTS

11. METEORLOGICAL SERVICES

12. MOBILE ELECTRIC POWER AND HYDRO-MECHANIC SERVICES

13. WIDE AREA NETWORK (WAN) SERVICES

14. LOGISTICS SUPPORT SERVICES

14.1 SHIPPING SERVICES

14.2 RESEARCH AND PROCUREMENT SERVICES FOR SPARE PARTS

14.3 EQUIPMENT DEPOT SERVICES

14.4 PROPERTY MANAGEMENT SERVICES

14.5 EQUIPMENT CALIBRATION SERVICES

14.6 CHEMICAL LABORATORY SERVICES

15. GROUND OPERATIONS

15.1 LAUNCH SITE SUPPORT PLAN

15.2 LAUNCH PAD AND BLOCKHOUSE

15.2.1 Launch Pad and Blockhouse Requirements

15.3 VEHICLE PROCESSING

15.3.1 Vehicle Processing Requirements

15.4 PAYLOAD PROCESSING

15.4.1 Payload Processing Requirements

15.5 SUPPLEMENTAL GROUND OPERATIONS SERVICES

15.6 MOBILE CRANES & RIGGING

16. ACRONYM LIST

STATEMENT OF WORK

for NASA’s WFF

1. DESCRIPTION OF SERVICES

The overall scope of this contract is to provide Wallops Range operations and maintenance; support services; training; command, control, communications, information and computer systems services; testing, modifying and installing communications and electronic systems at launch facilities, launch control centers and test facilities; range sustaining engineering services, and ground operations support. This effort provides direct customer support to NASA WFF’s Range by providing qualified personnel, equipment, tools, materials, vehicles, specialized test equipment, supervision, and other services. NASA’s WFF requires an innovative, integrated, flexible and effective management approach and the contractor must provide technical support in a planned and coordinated manner which will ensure essential Wallops Range support systems are ready to support user requirements, and cause no impact to Wallops Range program schedules due to equipment degradation, failures, system problems or reprioritization of preexisting program requirements. The wide variety of support systems involves flexible workload planning, cost management, and scheduling of resources to identify and resolve technical systems problems.

Available capacity for operations, maintenance, and sustaining engineering may be made available to other WFF organizations with the permission of the Contracting Officer’s Representative (COR), and RMMO Management.

Instrumentation systems are permanently located at WFF, Bermuda, and in Alaska. In addition, mobile instrumentation is deployed to locations worldwide, including but not limited to Norway; Kwajalein Atoll; Coquina, NC; Australia; and French Guiana to meet Range customer requirements.

The Wallops Range receives and provides Range support from and to various agencies.

The Wallops Range constantly strives to ensure it is prepared to accommodate the current and future needs of its customers. To that end, the contractor shall pursue ongoing preventive and corrective maintenance and sustaining engineering tasks to ensure readiness and mitigate the effects of obsolescence of its current Range equipment and systems. The contractor shall also work with RMMO in cooperation with other NASA Centers and organizations to maintain and sustain Range systems to common standards.

The contractor shall work with WFF organizations and provide operational requirements to support new engineering and/or technology development activities approved by the Range. Such activities enable the evolution of the Range architecture to include space-based metric tracking, telemetry, and command relay, and mission planning systems. The contractor shall also provide operational requirements and support transitioning new engineering or technology developments to operations.

For the purposes of this document, the following definitions apply:

• Operations – to turn on; to control the function of a system per existing procedures and obtain output.

• Maintenance – to enable a system to continue functioning (e.g. lubricate, calibrate, and repair) per existing procedures and parts.

• Sustainment – to repair and maintain with new parts or subsystems but operating procedures do not change and no new capabilities are added.

• Engineering Development – Upgrades to existing systems that add capabilities, including new parts and procedures. Engineering Development is typically led and provided by the Wallops Civil Servant Engineering Organization (Code 500).

Engineering Development support may be in the scope of work of this contract with the permission of the COR and Chief of the Range after discussions with Range Chief Engineer.

• Technology Development – Upgrades to existing systems or wholesale development that adds or develops capabilities or technologies that exceed the current state of the art or changes that are considered revolutionary, rather than evolutionary, to systems. Technology Development is not in the scope of work of this contract.

2. GENERAL

The Government will use Cost Reimbursement task orders to address the majority of requirements in this Contract and Statement of Work. In the limited circumstances where the contractor can reasonably estimate the price of a discrete activity in advance (e.g.

purchase of spare parts), the Government will issue a Firm Fixed Price task order.

The instrumentation systems that make up the Wallops Range include aging infrastructure existing in a highly corrosive environment that must continue to successfully support missions subject to schedule and requirements variability common on test ranges. These systems are located at WFF, and deployed to sites around the world which sometimes requires simultaneous operations management and staffing.

The contractor shall provide timely and reliable systems operations and maintenance while achieving systems performance excellence, continuously improve customer support, and proactively pursue overall cost reductions.

The contractor shall ensure system configuration integrity and reliability, mission readiness, and service excellence.

The contractor shall work with the Wallops Flight Facility (WFF) Regional IT Services and Solutions Division, Code 780, to define the intra-building cable plant requirements and transmission and distribution of data, voice, and video communications at the WFF for missions that require these services.

The contractor shall provide long-range planning for all systems.

The contractor shall comply with all Agency CIO and Communications Services Office (CSO) directives for the development, implementation, and operation of communications systems, network systems, and computer systems.

The contractor shall utilize the Agency I3P contracts or the SEWP contract for the procurement of any communications systems, network systems, and computer systems components.

The contractor shall ensure customer products and services are provided when needed and minimize the impact system maintenance has on the range operations schedule with a balanced program of effective preventative maintenance and operational load using the technical workforce proposed.

The contractor shall provide qualified personnel, equipment, tools, materials, supervision, training, certifications and other items and services necessary to manage range services requirements and perform tests, launch operations and maintenance. Available capacity for training, qualification, and certification may be made available to other WFF organizations with the permission of the COR and Chief of the Range. Qualifications shall be specific to each service area supported such as: radar, telemetry, video/photo

(optical), communications, timing, command, control centers, meteorological, and ground operations.

Certification examples would include but not limited to: crane and mobile aerial platform operations, high pressure operations, cryogenics, oxygen systems, precision cleaning, metalizing coatings, Self-Contained Atmospheric Protective Ensemble (SCAPE), Hazardous Waste Operations and Emergency Response (HAZWOPER), NASA Soldering, NASA Crimp and Cabling, Department of Transportation Commercial Driver’s License with hazardous endorsement, tubing fabrication, medium pressure fittings, and orbital tube welding.

The Contractor’s maintenance and sustainment activities shall comply with the following four Section 508 standards:

• 1194.21 Software applications and operating systems

• 1194.22 Web-based intranet and internet information and applications

• 1194.23 Telecommunications products

• 1194.24 Video and multimedia products

• 1194.26 Desktop and Portable Computers

The contractor’s maintenance and sustainment efforts shall comply with requirements from NASA Procedural Requirements (NPR) 7123.1 NASA Systems Engineering Processes and Requirements, 7150.2 NASA Software Engineering Requirements, STD

8739.8 NASA Software Assurance Standard, and STD 8719.13 NASA Software Safety Guidebook. The contractor is responsible for providing requirements associated with life cycle phases (typically operation and maintenance) for Class B to E software. The contractor’s maintenance and sustainment efforts shall support NASA in meeting acquirer software assurance and safety requirements by complying with 800-PG- 7150.4.1, Software Safety and Mission Assurance Process Interface, which serves as a software assurance and safety plan. As of this SOW release date, the current version of all standards and procedural requirements listed above are to be used.

The contractor is not responsible for the permanent buildings located at WFF, Alaska, or Bermuda that house the majority of the range instrumentation support systems. The contractor is responsible for various containers for mobile instrumentation, equipment, and/or systems. The Wallops Institutional Consolidated Contract (WICC) provides typical institutional services for buildings at the Wallops Flight Facility.

Other traditional institutional services such as physical security, shipping, etc., are provided by the WICC contractor unless otherwise stated in this Statement of Work

(SOW).

3. Performing Range Safety functions is not the responsibility of the contractor.

However, many systems that are used by Range Safety personnel shall be maintained, sustained and sometimes operated by the contractor.

PROGRAM MANAGEMENT

Program Management shall be proposed by the contractor for each task initiated under the contract. The program management required for the contract will not be initiated under a separate task order.

The contractor shall plan for, conduct, and administer a comprehensive integrated management program.

The contractor shall appoint a Program Manager who shall have the authority to make any necessary decisions (real time, if required) related to the performance of this contract and shall be the contractor’s primary point-of-contact with NASA.

The contractor shall administer functions which include: program management, contractor ethics, range projects management, continuous risk management, contract management, material management, cost control management, operations and future planning, contract administration, performance measurement, mission setup, quality control, data management, integrated logistics support, property management, facility management, employee safety, and employee training programs.

The contractor shall review and develop draft directives, monitor work in progress and coordinate with designated Government interfaces or other vendors and contractors.

The contractor shall develop and implement an innovative management philosophy to meet evolving mission requirements for the Wallops Range and its customers.

Customers include NASA, other Government Agencies and commercial entities with range requirements. The customers’ requirements are defined and provided by the Contracting Officer’s Representative (COR), NASA WFF Range and Mission Management Office, or NASA WFF Project Managers

The contractor shall establish, maintain, and implement a Quality Assurance Plan (QAP) to ensure compliance with quality management requirements in this SOW and/or established by the contractor. The QAP will be an attachment and become part of the contract.

The contractor shall establish and maintain a quality management program that facilitates the accomplishment of total work responsibility including management and technical interfaces between the Government and the associated customers and other contractors.

The quality management program shall document and implement a quality system that substantiates that all products and services conform to contractual requirements.

A Risk Management Plan, including how the contractor will be performing continuous risk management, shall be delivered by the contractor with their proposal. Continuous risk management practices shall be documented, implemented, and evaluated for effectiveness.

The contractor shall establish and maintain a work control system as part of their overall quality management system. This system shall use appropriate work authorization documents to provide adequate controls and reports, ensuring effective, efficient, and prompt responses to workload requirements and proper reporting of costs incurred. The contractor shall use Government-furnished Maximo® software to perform work control management and if they choose to use Maximo® for any other services, they shall use the same version of Maximo®. The Government will retain ownership of all electronic data in Maximo® upon contract completion.

The contractor shall adhere to NPR 7120.5E, NASA Space Flight Program and Project Management Requirements for operations, maintenance, and sustaining engineering activities. Missions supported may involve NPR 7120.5E, NASA Space Flight Program and Project Management Requirements or NPR 7120.8, NASA Research and Technology Program and Project Management Requirements. Additional management standards required to be followed will be defined in mission specific requirements documents and NASA project plans.

Mission specific management standards will be defined in mission specific requirements documents and project plans.

The contractor shall develop and maintain a Program Management Plan (PMP) for tracking programs supported, range services customer requirements, services provided, maintenance activities, actual labor hours, material costs, special projects, work requests, configuration management, and other areas the program office requires visibility. The PMP shall define the tools and processes to be utilized by the contractor to perform the program management functions required for this contract. The completed PMP shall be delivered with the proposal and the plan shall be updated and delivered to the COR and Chief of the Range upon completion of each contract year. The Government will retain ownership of all PMP related data in an electronic, open source format upon contract completion.

3.1 Program Management Reporting

3.1.1 Weekly Activity Report

The Mission Support Coordinator point of contact for each project shall report status of all activities to the RMMO Project Manager as requested by the RMMO PM. This communication will be defined by the RMMO PM for each project IDIQ task order and may include but is not limited to: phone call, email, formal report, or meeting.

3.1.1.1 Range Project Schedule

The Contractor shall support the development and weekly maintenance of the Range overall project schedule. This effort is to be reported weekly to the Chief of the Range and others as directed. The Range overall project schedule is to be presented in MS

Projects or other platform as defined by the Chief of the Range and shall represent all of the projects that the Range is supporting currently and into the future as far as can be projected. The Range project schedule shall have data fed to it from multiple outside sources; for example SRPO’s Master Mission Schedule, Code 802 mission projection schedule, and other missions that the Range would be supporting. The final product shall have the following components:

• Missions listed by title

• Resource loaded schedule assigned for NASA Project Managers / Deputy Project

Managers. Other key resources to be added as defined by the Chief of the Range.

• Major mission milestones back calculated from the planned Initial Launch

Capability (ILC) date:

o Mission Initiation Conference (MIC) o Instrumentation Support Brief (ISB) / Integrated Project Initiation Review

(IPIR)

o Range Readiness Review (RRR) o Launch Readiness Review (LRR) o Authorization to Proceed (ATP)

• Other items as defined by the Chief of the Range

3.1.2 Monthly Status Report

The overall program management status shall be provided to the COR and RMMO management as a Monthly Status Report (MSR), in PowerPoint with specific content identified below and updated over the course of the contract life as defined by the COR and RMMO management. The MSR shall be delivered electronically by the 28th of each month unless otherwise defined by the COR and RMMO Management.

The MSR shall be provided electronically and, at the option of RMMO management, be presented monthly to an audience defined by the Government.

If the task order defining the work is awarded beyond the 15th of a month, the following MSR does not have to status that work, unless otherwise defined in the task order.

The MSR package shall provide detailed range support operations and systems upgrade activities, financial status, and risk and issue status.

In summary, the MSR shall contain the following information:

• Covers significant contract activities;

• Consolidated report of sustaining engineering, operations and maintenance accomplishments and upcoming projected work activities with specific Red/Yellow/Green (RYG) issue and/or risk status for each mission defined and specific RYG issue and/or risk status for each sustaining engineering effort using the NASA/GSFC Problem/Issue/Risk RYG definitions and presentation process defined by the Chief of the Range;

• Contract performance metrics;

• Discrepancy Report (DR) status;

o Average open time for DRs assigned to the contractor o Worst case open time for DRs assigned to the contractor

• Status of Deliverables;

• Plan for large (over $50K) material purchases (including purchase date, invoice date, and cost);

• Develop schedule for each mission/project with key milestones;

• Major accomplishments for each mission/project;

• Mission/project priorities;

• Staffing changes with justifications/reasoning;

• New Mission/projects as a Result of Government Request or contractor initiated effort;

• Cancellation or Postponement of Mission/projects with

Justification/Reasoning;

• Outdated systems recommended for consideration by RMMO for upgrade along with rationale such as lack of vendor support, low reliability (high failure rate), high maintenance costs, etc.;

• Proposed maintenance or sustaining activities along with personnel resources applied to each activity, materials, implementation schedule and estimated costs;

Note: given that it is difficult to accurately forecast precise operational mission schedules (and therefore costs associated with overtime, premium, and travel), it is critical for the contractor carefully consider and plan for wide variations in available funds for maintenance and sustaining activities and to plan for likely contingency scenarios.

• Current and projected period of performance end cost and obligation variance;

• Monthly Range Summary Schedule defining additions or deletions since the last report as well as completed mission/projects and activities.

• Instrumentation System Availability (see Section 3.3.1)

3.2 Mission Preparation Products and Reviews

For each mission assigned, the contractor shall provide a plan to the NASA Project Manager that describes in detail how they will meet mission operational requirements.

The contractor shall participate in meetings and reviews as requested by the Government to ensure adequate communication to range operations personnel, NASA and Wallops Range customers. Participation may occur as part of a combined NASA/contractor team and may involve other contractors. Examples of the meetings and/or reviews requested by the Government are:

• Monthly Engineering Status Review (MESR)

• Weekly Range Instrumentation Working Group (RIWG)

Unless mission specific requirements dictate otherwise, the contractor shall provide a single review spokesperson, typically the RSM, defined in Section 4.1, covering all areas of instrumentation; however, each operational area lead shall be present during all formal reviews to answer detailed questions as needed.

3.2.1 Instrumentation Support Review

In support of the NASA Project Manager, the contractor shall present at a boarded NASA Instrumentation Support Review (ISR) for each mission. The ISR shall be held prior to Range Readiness Review to provide a detailed implementation plan to meet mission operational requirements of all in-scope activities.

At the ISR, the contractor shall clearly define their understanding of pertinent mission requirements and the implementation plan to meet the mission’s operational requirements. The contractor shall seek concurrence from the review board to move forward with the proposed implementation plan to satisfy mission operational requirements.

The ISR, as defined in mission specific documents, shall provide a brief overview of the mission, mission operational requirements, range instrumentation systems and configurations to satisfy the requirements, first use items, planned deliverables, applicable issues, and risk associated with each major function of the plan.

3.2.2 Range Readiness Reviews

In support of the NASA Project Manager, the contractor shall be present at a boarded NASA Range Readiness Review (RRR) for each mission.

The range operations contractor portion of the RRR shall clearly define the contractor’s understanding of pertinent mission requirements, the implementation plan, primary and backup equipment for major Range instrumentation service areas, and how the systems and personnel were verified as being ready to support the mission’s operational requirements.

The RRR, as defined in mission specific documents, shall include a presented summary perspective providing a brief overview of mission, applicable issues identified, issues closed, issues open, remaining risk items, status of actions being worked, and recently closed or recently opened applicable discrepancy reports and their complexity (number of, effort required to close, substance)

At the RRR the contractor shall present the results of system level simulation and testing, and results of the contractor’s operational performance (systems and personnel) evaluated against mission support requirements resulting from integrated simulations and tests.

3.2.3 Launch Readiness Reviews

In support of the NASA Project Manager, the contractor shall be present at a boarded NASA Launch Readiness Review (LRR) for each mission.

At the LRR, the contractor shall present the status of systems and personnel readiness to support the mission’s operational requirements.

The contractor shall present any system or personnel modifications/changes since the

RRR.

3.2.4 Post Mission Summary Report

The contractor shall provide a Post Mission Summary Report (PMSR) to the COR, Range Project Manager, and Range Chief Engineer and the Chief of the Range within 15 business days following the completion of a simple mission and 30 business days following the completion of a complex mission. Mission complexity and completion will be defined in mission specific requirements documents or by the Chief of the Range.

Critical components of the PMSR shall be at least the following:

• Results that include the performance of prime and backup systems and includes formal post-mission summary reports

• Work performed

• Lessons learned

• Results obtained

• Recommendations

• Assessment of performance against mission success criteria

3.2.5 Post Mission Report

THIS REPORT IS NOT REQUIRED FOR EVERY MISSION AND WILL BE

SPECIFICALLY TASKED IN THE REQUIRING MISSION TOs.

The contractor shall provide a Post Mission Report (PMR) to the COR, Range Project Manager, and Range Chief Engineer, and the Chief of the Range within 45 business days following the completion of a mission. Critical components of the PMR shall be at least the following:

• Post-mission summary reports of all participating range systems

• All tracking assets (TM or Radar) shall include details on:

o Initial acquisition method o Time and cause of all loss of track o For final loss of track include LOS azimuth and elevation o Time and acquisition method for all reacquisition of track o All times shall be in UTC and Mission Elapsed Time o Finalized plots from Post Flight Data Review o Disposition of all anomalies or failures identified at the Post Flight Data Review o Mission snapshot including launch vehicle description, mission name, mission ID, launch location, launch date and time (UTC), vehicle first motion time, and payload information.

o Summary of all launch attempts including reason for any launch scrubs o Launch weather information o Pre-launch testing summary o Launch day support summary including times of significant events o Results obtained o Work performed o Recommendations o Requirements disposition o Assessment of performance against mission success criteria o Lessons learned

3.3 Performance Metrics and Reporting

Additional mission-specific performance metrics beyond those defined in Section 3.2 will be defined in mission requirements documents or in specific IDIQ task orders.

3.3.1 Instrumentation System Availability

The contractor shall collect and provide monthly systems availability metrics, last six months availability metrics, and cumulative systems availability to date in the MSR.

Service Hours Not Scheduled shall not include planned system downtime when impacting customer support requirements. Planned system downtime shall be authorized by the Range Chief. Service Hours Not Scheduled shall include unplanned system downtime when impacting customer support requirements.

The contractor shall collect and present planned and unplanned system downtime and include in the MSR, mission-specific readiness reviews and associated reports.

The availability requirement across all systems defined below shall be 98% and in no case impact the mission.

The availability shall be met across any 6-month sliding window with the window updated in one-month increments.

Availability shall be defined by the following formula:

Availability = 100% * (Service Hours Required – Service Hours Not Scheduled)/Service Hours Required.

The systems, including any accompanying instrumentation systems/trailers, that at a minimum shall be reported for availability metrics are as follows:

• Fixed Telemetry 7.3-meter System #1

• Fixed Telemetry 7.3-meter System #2

• Fixed Telemetry 10-foot System

• Fixed Telemetry 8-meter System

• Fixed Telemetry 9-meter System

• Fixed Telemetry Redstone 9M-1 (at PFRR Alaska)

• Fixed Telemetry Redstone 9M-2 (at PFRR Alaska)

• Fixed Telemetry 11M (at PFRR Alaska)

• Mobile Telemetry 8-meter System (at PFRR, Alaska)

• Mobile Telemetry 20-foot System

• Mobile Telemetry 7-meter System #1

• Mobile Telemetry 7-meter System #2

• Mobile Telemetry 10-foot System

• Mobile Telemetry 20-foot System

• Mobile Telemetry 40-foot System

• LowG1 (2.4M) Antenna

• LowG2 (2.4M) Antenna

• Mobile Integrated Telemetry System (MITS)

• Mobile Power Systems

• Fixed Radar #3

• Fixed Radar #5

• Fixed Radar #18

• Doppler Radar Systems

• ASR-8

• LSTAR (at PFRR Alaska)

• SPANDAR Radar System

• UHF Radar System

• Mobile Radar #2

• Mobile Radar #8

• Mobile Radar #10

• Mobile Radar #11

• Mobile Command Systems

• RADAC System

• Fixed Command System (U-55 Building Systems)

• WISSRDS Sea Surveillance Radar System (X-band and S-band)

• Mission Graphics System

• Wind Weighting System

• Master Timing System

• RF Communication Systems

• RFDF/EMCON Systems

• NASCOM

• Meteorological Systems

• Optical Systems

• STING Surveillance System

• Ship Surveillance System

• Range Data Systems (such as VTARS, RAPS, STARSS, PCDQS, PCGDS)

The contractor shall present this list to the Range Chief and Range Chief Engineer for their review and approval annually.

3.3.2 Data Systems Performance and Reliability

Assurance (quality, safety, reliability, verification and validation) requirements apply to all system life cycle phases including design, implementation, test, operations, and maintenance. Assurance activities include reviews, audits, and tests. Assurance activities for maintenance and sustaining are tailored based on the classification and criticality of hardware and software systems. NASA directives list requirements for both the software acquirer (e.g., NASA) and the software provider (e.g., the contractor).

To meet NASA directives, the contractor shall document software management plans, configuration management plans, test plans, test procedures, maintenance plans, operation plans, users’ manuals and retirement plans. The contractor shall create one management plan to cover multiple similar systems. The contractor shall either comply with the provider software assurance and safety process requirements defined by 800-PG-

7150.4.1 or document an alternate process to meet STD 8739.8 and STD 8719.13 provider requirements.

Following approved processes, the contractor shall maintain code and associated files and documents as needed, requirements, metric reports, peer review/inspection reports, software/data/interface descriptions, version descriptions, change requests, problem reports, and test reports as applicable to each system’s classification and lifecycle phase.

Safety-critical software systems shall also require the documentation and maintenance of a hazard analysis (e.g., fault tree or failure modes and effects analysis).

Activities associated with safety-critical software systems require coordination with the Wallops Safety Office. Safety-critical reliability requirements will be specified by the Wallops Safety Office for each safety-critical system. The Range and Mission Management Office may also specify mission-critical reliability requirements. Test plans for safety-critical software systems shall cover functional requirements, potential failure modes (identified by the hazard analysis), and multiple (typically 30 to 100) operation scenario tests designed to provide evidence of system reliability.

To allow NASA insight, the contactor shall participate in twice yearly process audits for mission-critical and safety-critical software systems. To allow NASA oversight, the contractor shall include the Wallops Safety Office in reviews and tests for safety-critical software systems.

3.3.3 Radar Systems Performance

Precision tracking radars shall acquire the intended target in auto-track mode within 10 seconds of presentation of intended target unless defined otherwise in mission specific requirements documents.

The precision tracking radars shall track the Radar Calibration (RADCAL) and Defense Meteorological Satellite Program (DMSP) satellites and report monthly or as required by mission specific requirements documents and meet the following RMS tracking error performance standards:

• ±0.10 milliradian for Radar #5

• ±0.15 milliradian for Radar #18

• ±0.20 milliradian for Radars #3, #10, #11

• ±0.25 milliradian for Radars #2, #8

The range error shall be less than 40 meters.

The precision tracking radars shall track 6-inch spheres monthly to maximum range and report monthly or as required by mission specific requirements documents.

The results shall meet minimum loop gain specifications for each system.

Mission-specific metrics shall be reported for each sensor and shall include:

• Target assignment(s) per radar aperture;

• Acquisition success and time of acquisition;

• Quality of track;

• Quality of data supplied to the end customer and Wallops Range Control Center;

• Quality of recorded data;

Radar operations services reporting shall be included in the PMSR.

3.3.4 Telemetry Systems Performance

The telemetry systems shall perform the following performance testing and report monthly or as required by mission specific requirements documents:

• G/T

• EIRP

• Error gradient (tracking error)

The results shall meet minimum specifications for each system.

For all telemetry systems, mission-specific performance metrics shall be reported for each antenna system and shall include:

• Target assignment(s) per telemetry aperture

• Acquisition success and time of acquisition

• Quality of track

• Quality of data supplied to the end customer and Wallops RCC

• Quality of recorded data

3.3.5 Mission Success Criteria

The success criteria requirements that shall be met by the contractor and demonstrated by reporting specific performance metrics as defined in this SOW are:

• Metric tracking, range safety, surveillance, telemetry, command and control, and other instrumentation objectives shall be satisfied for each mission. The primary equipment shall perform without data loss impacting mission objectives, resulting in unplanned safety risks or missed surveillance targets for each mission. The trend over time shall show a reduced dependence on backup instrumentation equipment for assuring mission success. Over time the requirement for backup equipment shall be reduced, lowering the cost of operations and maintenance and increasing availability of equipment for parallel missions. These trends shall be documented and demonstrated to the Government to achieve comprehensive success.

• No mission delays or unplanned safety risk occur due to instrumentation, project management, preventive maintenance, configuration checkout, and operational procedures are performed per approved plans. Critical maintenance and sustainment shall be completed with adequate time to test prior to the mission utilizing the change as demonstrated with a regimented project management approach.

• Operations, maintenance, and/or sustainment cost savings are identified and realized.

• New, mission specific operational systems are transitioned into use with no delays or unplanned risks.

3.4 Configuration Management

A regimented Configuration Management (CM) process shall be implemented and followed for all aspects of the Wallops Range instrumentation and ground operations services including, operations, maintenance, and sustainment activities.

The contractor shall comply with the governing Goddard Procedural Requirements (GPR) GPR-1410.2, for Configuration Management.

The contractor shall provide their approach to configuration identification, change control, status and accounting, and configuration audits.

The contractor shall provide configuration management of all documentation, software, hardware, mission configurations, and test scenarios.

The contractor shall utilize the existing Government-owned CM system integrated into Range Operations Management System (ROMS).

The CM system including all CM managed data shall be made available using NASA Data Center (NDC) user name and password protected access using the ROMS.

The Government will maintain Chairmanship of the Configuration Control Board (CCB) and majority on the board but the contractor shall support the balance of the CCB with individuals proposed by the contractor to be appropriate CCB members.

The contractor shall hold a biweekly CCB meeting.

The contractor shall obtain Independent Verification and Validation (IV&V) services as required in task orders or detailed mission requirements documents.

3.5 Alternate Facilities Operations

The contractor shall provide Alternate Facilities Operations Manager (AFOM) services by acting as Alternate FOMs for certain Wallops Range facilities.

Contractor Alternate FOMs shall be recommended by the contractor and approved by the Range Chief.

The duties associated with being an Alternate FOM are minimal and can be accomplished by existing contract personnel residing at those respective locations. AFOM duties are described in GPR-8830.1B.

Any required training for these positions will be provided by the Government.

3.6 Health and Safety Management

A comprehensive and proactive health and safety program is required. The contractor shall perform the requirements of this contract using the safety and health guidelines provided within the Occupational Safety and Health Act, NASA Safety Manual, NPR 8715.3, the GSFC Environmental Policy and Program Management, GPD 8500.1, and any other directives contained in this contract.

The contractor shall ensure that employees are aware of and trained relative to safety and health requirements associated with their jobs and positions.

The contractor shall ensure employees are medically fit and undergo medical examinations in accordance with NPR 1800.1D, Appendix C, A3. Certification Exams, Matrix O for Security and are physically and medically capable of performing the essential duties of their positions efficiently and without hazard to themselves or others.

The contractor shall reimburse the Government for any civil or criminal fines or penalties resulting from any health and safety or environmental infractions caused by the contractor’s negligence.

Contractor shall comply with all applicable NASA and Occupational Safety and Health Administration (OSHA) standards related to smoking while on duty. Compliance with all posted signs is mandatory.

3.7 Physical Security Management

The Contractor shall safeguard all Government property provided for contractor use in accordance with the clauses of this contract.

Government facilities, support equipment, and material shall be secured when not in use.

The GSFC Security Manual, GHB 1600.1, will be utilized in evaluating performance under this requirement.

3.8 Human Capital Management

The contractor shall provide qualified personnel with the necessary training, security clearances, and technical expertise in the functional support areas required.

Personnel requiring certification on specialized equipment, or systems, shall be certified by the vendor, a vendor approved organization, Government organization, or as otherwise required.

The Wallops Range supports a diverse set of customer mission requirements and therefore the operational hours shall vary as individual mission requirements dictate.

The contractor shall abide by all work-hour limitation rules in accordance with NASA Procedural Requirements (NPR) 1800.1 NASA Occupational Health Program Procedures, for their own employees and manage within these bounds to maintain service availability.

Normal duty hours of operation shall be 0800 – 1630 local time, Monday – Friday.

The contractor shall be prepared to change work schedules to preserve a normal 40-hour/week workload while meeting mission requirements outside of the normal duty hours.

The contractor shall be prepared to shift work schedules and provide overtime services necessary to meet individual mission requirements.

Contractor personnel are required to travel as directed. The contractor shall perform associated travel to and from site locations for equipment and systems requiring contractor actions. Cost associated with this travel shall be defined under the travel line item on Government cost reports and on work orders. All travel shall be in conducted accordance with applicable Federal, Joint, State Department, and NASA Travel Regulations (NPR 9700.1 and NID 9700.2) as applicable for each travel destination unless a deviation is requested and approved by the Contracting Officer. All Contractor personnel travel requirements shall be the responsibility of the Contractor including medical certifications, immunizations, passports, ticketing and transportation, and lodging.

Appendix A (NID 9700.2): FMR NASA Federal Travel Regulations Supplement (NFTRS) Chapter 301 Subpart C: Reduced Per Diem is applicable to this contract.

3.9 Special Considerations

The contractor shall obtain all licenses and permits required for the performance of this contract.

Unless otherwise stated in this SOW, the contractor shall provide, upon completion of Phase In, the list of recommended special equipment/operations capabilities requiring specialized licensing, permits, training and certifications, and the proposed method and schedule for obtaining them.

All personnel proposed shall have at a minimum, a National Agency Check (NAC), or current equivalent as required by HSPD-12, either completed or in process.

Certain mission data such as flight profile data, vehicle radar signatures, vehicle performance data, etc. are known classified data for certain missions. Contract personnel exposed to classified data or work closely with NASA and their customers for requirements planning, etc., shall have at least a TOP SECRET-level security clearance to meet unique classified mission requirements support at the Wallops Range unless otherwise approved by the Government.

Certain missions shall require the contract to establish remote sites and mobile instrumentation capabilities including the processing of classified information. The contractor shall provide the appropriate clearances to handle, store, and safeguard classified information to the SECRET level as appropriate to the mission requirements.

The contractor shall maintain compliance with the following Security Policies and Internal Directives:

1. DOD 5220.22-M, National Industrial Security Program Operating Manual (NISPOM) (05/18/2016)

2. NPR 1600.1A NASA Security Program Procedural Requirements, May 12, 2019

3. NPR 1600.2 NASA Classified National Security Information (CNSI) w/Change 2 (2/12/2014), March 31, 2020

4. NPR 1600.3 Personnel Security (Change 2, April 29, 2013), April 30, 2019

5. NPR 1600.4A Identity and Credential Management, April 8, 2021

6. NPR 1620.2A Facility Security Assessments, October 7, 2020

7. NPR 1620.3A Physical Security Requirements for NASA Facilities and Property, February 28, 2019

8. NPR 1660.1C NASA Counterintelligence and Counterterrorism w/Change 1, May 28, 2015, May 7, 2020

9. NPR 2810.1A Security of Information Technology (Revalidated with Change 1, dated May 19, 2011), January 16, 2019

10. NPD 1600.2E NASA Security Policy (Revalidated on 4/2/2015 w/Change 1), March 31, 2020

11. NPD 1600.4 National Security Programs (Revalidated with Change 1 on July 28, 2016), July 28, 2021

12. GPR 1600.1, Goddard Space Flight Center (GSFC) Protective Services Program Requirements, June 20, 2022

13. GPR 1600.2 GSFC Protective Service Division Classified National Security Information and Industrial Security, June 29, 2023

14. GPR 1600.3 GSFC Protective Service Division Personnel Security, June 19, 2023

15. GPR 1600.4 Identity and Credential Management (12/04/2013), June 22, 2023

16. Federal Information Security Management Act of 2014

17. OMB Circular A.130, Appendix III, Security of Federal Automated Information Resources

18. NPD 2810.1E NASA Information Security Policy, July 14, 2020

In accordance with HSPD-12 and NASA processes, the contractor is responsible for completing all visitor requests for any individuals requiring access to NASA facilities or requiring access to Government IT systems in support of assigned tasks and for completing/supporting any associated access support requirements (such as visitor escort requirements, etc.).

The contractor shall provide personnel to support incident response and mishap investigations as required in accordance with NPR 8621.1.

3.10 Financial Management

The contractor shall participate in a monthly Financial Status Review to provide financial status and planning to support the Government budget planning process.

The contractor and Government shall jointly discuss planned material purchases and projected work force resource requirements and evaluate against the mission schedule.

At each monthly Financial Status Review the contractor shall provide the financial status of planned versus actual spending, review materials budget by discipline and the status of procurements in each area, discuss any vendor or supply chain issues, summarize costing of major acquisitions if funds extend through multiple fiscal years, and review the projected cost and work force requirements for the next reporting period.

The format and content of the contractor’s inputs and supporting rationale will include all formulas and work products associated with the final product as directed by the COR and shall be in accordance with the budget or and reporting format specified by NASA.

3.11 Education and Outreach

The Education and Outreach program is part of a Wallops-wide effort to inspire the next generation of explorers and engineers through communications and opportunities offered in the rich hands-on environment at WFF. Wallops supports NASA’s strategic objective to share NASA with the public, educators, and students to provide opportunities to participate in our Mission, foster innovation, and contribute to a strong national economy.

The Contractor shall support various conferences, events and activities related to education and outreach.

The Contractor shall provide support including informational booths and associated equipment from Wallops’ programs at conferences. Informational booth support includes building, expanding, or modifying a booth; storing the booth offsite;

shipping/transporting the booth to and from conference sites; set-up, staffing, and tear-down of the booth at conferences and other events.

The Contractor shall implement an Internship program that includes various career fields across the Wallops Range.

4. INTEGRATED RANGE SERVICES MANAGEMENT

The contractor shall use and maintain the Government-owned Range Operations Management System (ROMS) that enables accurate, timely, and coordinated project planning, and is accessible by authorized personnel.

The contractor shall have a process to allow efficient access and control of tracking and reporting systems by the contractor and the Government.

The ROMS shall support planning, budgeting, performance measurement, resource obligations, Range mission and operational requirements, Range system improvement efforts, and special projects as requested by the Chief of the Range.

The contractor shall provide range scheduling services for Wallops Range mission activities that are conducted at the WFF and at other ranges that are established or exist worldwide. The contractor shall support other Wallops organizations operational scheduling as required. Non-Range operational activities will include sounding rockets, aircraft, balloon, and special orbital and suborbital projects deployments and operations.

The contractor shall respond to range schedule requests from NASA Range Project Managers and the NASA WFF Test Directors. The response will include confirmation of receipt and any impacts to current operational plans.

Range scheduling services shall include:

• assigning unique project numbers to Wallops Range missions

• tracking project start/stop dates for the Wallops Range monthly calendar

• integrating Sounding Rocket, aircraft (including UAS), balloon and other suborbital and special orbital project schedules into the range schedule

• scheduling individual Wallops Range assets/resources for specific project requirements so resource deconfliction can occur

• assisting with frequency coordination by scheduling operational frequencies in use and reporting potential conflicts to the Government

• distribution of the above products to enable tracking and scheduling facilities maintenance schedules around mission operations and these services shall include scheduling project reviews, and presentation of any above information at various meetings and reviews.

ROMS schedules shall include comprehensive Wallops Range mission instrumentation systems preparation and implementation milestones in support of Range operations.

The Government shall retain conflict resolution authority for the operations schedule whether that is an automated de-confliction process or manual.