Attachment a performance work statement

Download 0.5 Mb.

Page	2/3
Date	23.04.2018
Size	0.5 Mb.
	#46373

1 2 3

The contractor shall perform maintenance, troubleshooting, installation, diagnosis, fabrication, layout, modification, and repair of all systems, sub-systems, and electronic equipment. The equipment shall be maintained in such a manner that a minimum of 95% uptime on each mission-critical systems is achieved, (or as otherwise specified in a particular WBS) not including scheduled downtime such as for preventive maintenance or configuration changes.

The contractor shall use the BITS to schedule and perform preventative and remedial maintenance. The BITS database shall maintain a history of maintenance activities. BITS shall also maintain a database of personnel training, skill level and certification on maintenance activities.

The contractor shall schedule and perform all preventive maintenance and remedial maintenance so that no missions are impacted.
The contractor shall maintain a spares, and equipment inventory database. The contractor shall prepare purchasing information that may result in generating either a contractor Purchase Request or a NASA Purchase Request for materials or services.
The contractor shall maintain a stock of working spares sufficient to achieve a 95% uptime on each mission-critical systems or as otherwise specified in the particular WBS element. Spare parts and equipment shall be properly labeled at all times identifying their status. All storage areas shall be kept in a clean and orderly fashion.
The contractor shall maintain a maintenance log of all work performed, including preventive maintenance, on all systems. The contractor shall have a second technician inspect all work performed on mission critical systems and initial or stamp next to the log entry to verify the work is satisfactory. These logs shall be made available to NASA upon request.
The contractor shall perform a system functional checkout each and every time maintenance or modifications are performed. This checkout could be a diagnostic check or routine power up, in the case of a simple board replacement, or a full-blown systems checkout including a data playback to the MCC in the case of a modification or systems configuration change.
The contractor shall document all changes made to the systems supported. This documentation shall include wire lists, schematics, block diagrams, and any other pertinent information required to maintain the system after being placed into operation.
The contractor shall perform tests to evaluate equipment performance or the effectiveness of procedures.
6.1.1.3 Sustaining Engineering
Sustaining engineering is comprised of those engineering efforts required to sustain a viable operational environment. The purpose of this support is to ensure that the operational systems are adequate to satisfy existing requirements. This includes investigating requirements, troubleshooting problems, proposing solutions, and modifying, replacing or upgrading existing systems.
The contractor shall be required to perform sustaining engineering tasks to provide up-to-date systems and services. The contractor shall:

Analyze and document functional requirements.

Develop technical specifications, and cost and schedule estimates for new systems.

Determine and document system performance limits.

Design, develop, and document systems, which most efficiently satisfy the requirements.

Evaluate, test, checkout and install new equipment.

Recommend, design, and implement equipment modifications.

Conduct design reviews, develop and track project schedules, and make presentations for NASA review.

Adhere to established Configuration Control procedures.

6.1.1.4 Development Engineering
Development engineering is comprised of those engineering efforts required to significantly advance the capabilities of the operational environment. The purpose of this support is to provide operational systems that are adequate to satisfy future requirements. This includes investigating requirements, proposing solutions, developing new systems, and replacing, modifying, or significantly upgrading existing systems.
The contractor shall be required to perform development engineering tasks to provide up-to-date systems and services. The contractor shall perform all functions listed in Section 6.1.1.3.

6.1.2 Real-Time Processing And Display Systems
General

Computer systems operations and software maintenance services are required for the Mission Control Center (MCC) Systems Group section of the Range Operations Branch. This element is in support of the MCCs, Stand Alone Facility(SAF), Telemetry and Radar Acquisition Processing Systems (TRAPS), Telemetry tracking system, and Operations (OPs) computer system. The NASA technical monitor (TM) will provide oversight and guidance over all systems and sub-systems. Software maintenance services include the modification, testing, and verification of “project specific” software as well as the preflight setup and operation of all equipment associated with these areas.

Preventive and remedial maintenance, repair, modification, fabrication, installation, and diagnostic troubleshooting of systems and equipment are also required. These systems collect, transfer, process, and display critical mission data and provide the capability to monitor mission activity in real-time.
Additionally, the maintenance of all instrument recording equipment/systems is included in this work element. These recording instruments and systems are located in various areas within the facility such as the Range, the Flight Simulation Facility/Remotely Augmented Vehicles Laboratory (SIM/RAV), and the Avionics Section. Systems consist of both ground based and airborne magnetic tape recording systems.
6.1.2.1 System Description
The Dryden Flight Research Center (DFRC) Western Aeronautical Test Range (WATR) has the responsibility to acquire and process mission data in support of flight research. System and software engineering services are required to maintain and progress these systems to satisfy dynamic project requirements. The Telemetry/Radar Acquisition and Processing System (TRAPS) is a collection of subsystems which act together to acquire multiple data sources, process the data, distribute the data, and store the data. The information generated in the TRAPS is provided to one or more Mission Control Centers (MCCs). It is the responsibility of the MCCs to present the data on a variety of display devices that are monitored by project and range personnel. The data is used to monitor the status and performance of the research vehicle.
These systems will focus on PC-based platforms, using a version of Microsoft Windows (XP, Server 2003 and others), all networked together. Contractor personnel should be fully proficient in the development and maintenance of software in the Microsoft Visual Studio .Net environment. In the area of programming languages, the primary language is C#, with some development in FORTRAN, Visual Basic and C++.
The WATR Integrated Next Generation Systems (WINGS) will increasingly be involved in network-distributed processes, assets, and customers in support of integrated advanced telemetry projects such as Global Test Range, Network-Enhanced Telemetry (iNET). Some of these assets will be located on the other side of the globe and some may be space-based. Consequently, prototyping advanced capabilities will require the development of new subsystems and interfaces to support communication with entities external to the test range
The contractor shall provide systems, software and hardware engineering services for the WATR Data Acquisition and Processing Systems (BASS, Telemetry Processing, Data Server, Compute Server, Archive, Data Display, and external interfaces) and support systems (BITS and WATR CCB Tool). Information processed includes PCM data, Engineering Units data, time FM/FM data, GPS data, and Time/Space Position Information (TSPI). Currently supported systems require that the contractor be skilled with the following:

Concepts – Telemetry, PCM data, FM data, CCSDS data, IRIG Standards, Decommutation, Network Protocols, GPS, Object Oriented Programming, and the software development life cycle.

Platforms – PC, Wyle Omega, Linux

Operating Systems – Windows XP & Windows Server 2003, Windows 7 and Linux

Programming Languages – C/C++, C#, ASP .Net, Windows, Visual Basic, SQL, Fortran 77/90.

Tools – Wyle Omega Manager and Clients, Visio, SourceSafe, Visual Studio, Active Server Pages .Net, MS Access, SQL Server, and Crystal Reports.

Future WATR systems will include the following technologies:

Standardization on the Intel platform. In the future, this could include both 32-bit and 64-bit architectures.

Standardization on Windows XP and Windows Server 2003 (and beyond) Operating Systems. This encompasses a lot of software development technologies, including: C++, C#, Visual Basic, COM+, XML, ADO+, DirectX

Advanced network technologies, standardizing on packet-based data distribution. The technologies may include Gigabit Ethernet, Wireless, TCP/IP, SOAP, …

Use of Web technology for data access. This includes ASP .Net, Visual Basic, IIS, SQL Server, Oracle, …

Future telemetry technologies, including: FQPSK, CCSDS, iNET and other packet technologies,

Advanced storage technologies, including: RAID, Network devices,

6.1.2.2 TRAPS and MCC Operations
In addition to those tasks outlined in Section 6.1.1.1, the contractor shall:

Perform pre-mission set-up and calibrations to the TRAPS and MCC's, including the Auxiliary MCC's, to meet specific mission or project requirements, while maintaining strict configuration control.

Operate the TRAPS computers during all phases of mission support (pre-mission, post-mission, and during the mission). The TRAPS will be staffed at all times during real-time mission support. During non-real-time missions, the TRAPS may be left alone while the technician performs other duties.

Capture real-time data and archive both raw unprocessed data (PCM, FM, radar, voice, IRIG, etc.) as well as processed data.

Maintain the flight data tape library located in Building 4857, storing tapes away in a neat and orderly fashion, and maintaining a database for all archived data tapes; retrieving tapes from storage when playbacks are required or if a user requests a copy; periodically, upon approval from the Project Manager and the NASA Technical Monitor, degaussing old tapes and surplusing them through the NASA warehouse.

Perform daily, weekly, and monthly backups of all systems software, application software, and all associated files for all systems supported in the WATR.

Provide prompt response to the RCO (less than 2 minutes) to any MCC equipment failure or data discrepancy or request for help by the users during real-time mission support.

6.1.2.3 Range Data Recording Systems
6.1.2.3.1 Systems Description
All pertinent data is recorded on analog and digital recording systems in various Dryden facilities and on research aircraft. There are approximately 77 recording systems that record many tracks of telemetry, voice, timing, and radar data.
6.1.2.3.2 Recording Systems Operations
The contractor shall:

Pre-flight all data recorders prior to each mission and report the system status to the Range Control Officer (RCO).

Operate all ground-based recorders during real-time mission support, recording the appropriate signals as requested by the project or RCO.

Copy data tapes in response to official requests.

Maintain the WATR data tape library (including, but not limited to, archiving, organizing, loaning, and tracking data tapes), and retrieve and play back data tapes upon request.

6.1.2.3.3 Recording Systems Maintenance
The contractor shall perform all tasks as specified in Section 6.1.1.2 for this functional area.
6.1.2.3.4 Recorder Systems Engineering
The contractor shall perform all tasks as specified in Section 6.1.1.3 for this functional area.
6.1.2.4 TRAPS and MCC Application Software Support
In addition to those tasks outlined in Section 6.1.1.1, the contractor shall:

Develop, test, validate, and verify application software to meet specific project requirements in accordance with DOP-M-109. In this context, application software means a special or project specific configuration, setup, or compilation of processing and display software systems. Software includes in-house and third party products. All products must be understood, documented and integrated into the system. The software provides data acquisition, routing, processing, distribution, status, archival, storage, and display services for the system.

Perform beta testing on new software or versions of old software. The contractor shall provide feedback to NASA WATR engineering on the performance of the software.

Schedule, test, validate and verify new application software releases as well as MCC workstation software releases. Software releases shall be covered by a WATR Configuration Change Request (CCR) and when tested documented by a System Test Report (STR).

Maintain, and provide to NASA upon request, documentation on all projects and systems supported. This documentation will include a complete audit trail for every change made to the application or systems software.

6.1.2.5 TRAPS and MCC Maintenance
The contractor shall perform all tasks as specified in Section 6.1.1.2 for this functional area.
6.1.2.6 TRAPS and MCC Engineering
In addition to those tasks outlined in Sections 6.1.1.3 and 6.1.1.4, the contractor shall:

Develop methods and provide the materials for the installation and checkout of new system installations, assist operations personnel in the checkout process when requested, and perform system-level troubleshooting.

Propose system changes and additions that improve the operational environment, expedite system releases, and enhance the development processes identified in DOP-M-109.

6.1.2.7 TRAPS and MCC Validation and Verification Support

In addition to those tasks outlined in Section 6.1.1.1, the contractor shall:

Prepare and implement validation and verification (V&V) plans for the Real time Display and Processing Systems and applications. Install, integrate and support software for V&V process and transition to operational status. Maintain Configuration Item identification for all system and software releases, revisions and documentation.

6.1.3 Range Tracking and Range Mobile Systems
6.1.3.1 Systems Description
The Aeronautical Tracking Facility (ATF-1) located at the NASA Dryden Flight Research Center is used to support real-time aeronautics research and low earth orbiting (LEO) space vehicles. ATF-1 houses two seven meter telemetry antenna systems both capable of receiving data in “L” and “S” bands. Video is received in “L,” “S,” and “C” band. These systems also provide a tunable uplink command in “L” and “S” band. In addition two RIR-716 radar systems are also located in ATF-1. These radar systems operate in “C” band and have a one-megawatt output. A third, and smaller, TM system on the roof of Building 4800 is used primarily for flight line support and as a backup tracking system. This system has L- and S-band telemetry and video downlink capabilities.
NASA also has several mobile telemetry assets, a four-foot portable system, which is capable of receiving data and video in the “L” and “S” band. The Mobile Operations Facility #1(MOF 1) houses a six-foot transportable antenna system along with a best source select capability (PTP), data processing and display, data communications, a tunable uplink command in “L” and “S” band uplink, differential global positioning system, data/voice recording, UHF/VHF radios, internal UPS and RCO/RSO stations. All of this is housed in a 30 - foot semi-trailer. Dryden also has four - portable T-1 microwave systems.
6.1.3.2 Radar Systems Operations
In addition to those tasks outlined in Section 6.1.1.1, the contractor shall:

Perform pre-mission set-up and calibrations of the RIR-16 radar's to meet specific mission or project requirements, adhering to strict configuration control.

Operate the radar systems during real-time mission support and, as required, perform pre-mission checkouts of aircraft beacons and radio frequency interference sweeps during Combined System Test (CST). The radar shall be staffed by contractor personnel at all times during mission support.

Capture and archive real-time data radar data onto tape recorders or computer hard disks.

Operate the radar data system in support of real-time and post-mission radar data formatting.

6.1.3.3 Radar Systems Maintenance
The contractor shall perform all tasks as specified in Section 6.1.1.2 for this functional area.
6.1.3.4 Radar Systems Engineering
In addition to those tasks outlined in Section 6.1.1.3, the contractor shall:

Interface with the established Instrumentation Radar Support Program (IRSP) contacts to negotiate for and acquire Depot Level Maintenance (DLM) and upgrades for the Radar systems.

Coordinate with other areas at Dryden to accomplish the effective transfer of radar TSPI data to real-time and post flight users.

Coordinate with other ranges to ensure that data interchange continues and improves.

6.1.3.5 Telemetry Tracking Systems Operations
In addition to those tasks outlined in Section 6.1.1.1, the contractor shall:

Perform pre-mission set-up and calibration of the three telemetry tracking systems to meet specific mission or project requirements, adhering to strict configuration control.

Operate the telemetry tracking systems during real-time mission support, and perform pre-mission checkout of aircraft transmitters during CSTs. The tracking systems will be staffed at all times during mission support.

Operate Space Transportation Systems (STS) equipment, such as the Command Telemetry Processor (CTP) and the Dryden Apple Replacement System (DARS) during all phases of space shuttle operations.

Operate data distribution equipment to ensure the proper signal is being sent down the proper line to the appropriate destination.

6.1.3.6 Telemetry Tracking Systems Maintenance
In addition to those tasks outlined in Section 6.1.1.2, the contractor shall maintain Shuttle-specific systems to the board level, including the Command Telemetry Processor (CTP) and the Dryden Apple Replacement System (DARS) in support of Shuttle operations at Dryden and Edwards. Component-level maintenance on these systems is performed by Goddard personnel under a separate contract and is coordinated by NASA personnel.

6.1.3.7 Telemetry Tracking Systems Engineering
In addition to those tasks outlined in Section 6.1.1.3, the contractor shall propose changes and additions to the Dryden systems based on advances in telemetry system technology that will improve performance, lower costs and keep up with current technology.
6.1.4 Range Communication Systems
6.1.4.1 Systems Description
The Range Audio Communication Systems include the Digital Integrated Communications Electronics System (DICES) , and the RF Audio System (air-to-ground system) used to communicate with aeronautical and LEO space vehicles. These systems are necessarily interrelated, in that they receive feeds from each other. These systems are operated and controlled from Buildings 4824 and 4720.
The RF systems include UHF, VHF, and HF transceivers and antenna systems. There are three directional UHF high-gain dish antennae that are positioned on the target by "slaving" to radar data.
NASCOM is managed and maintained by the Goddard Space Flight Center (GSFC) and is used for operational (mission) telecommunications, this includes routing voice and data between NASA centers. It is the global system of circuits, switching, and terminal facilities, which support NASA technical missions, programs, and projects.. The contractor shall only be responsible for interfacing Dryden systems and circuits to the NASCOM controlled system. NASCOM may, however, contact Dryden and have contractor technicians perform circuit checks or a circuit board exchange.

6.1.4.2 Communications Systems Operations
In addition to those tasks outlined in Section 6.1.1.1, the contractor shall:

Operate NASCOM equipment located at Dryden, including circuit termination equipment and teletypes, send and receive test messages, report and resolve circuit problems, and coordinate with the GSFC NASCOM Network Control Center on use of circuits.

Operate all equipment in conformance with Federal Communications Commission (FCC) regulations for those audio signals to be released to the commercial networks and as otherwise required.

Configure the NASCOM audio circuits based on inputs from the Range Control Officer (RCO), for distribution to other NASA Centers during real-time mission support.

Pre-flight and document the Communications Facility status and configuration prior to each mission and report the system status to the RCO.

Operate radios and ground audio equipment during real-time mission support.

Record all mission audio as requested by the project or RCO.

Operate the audio distribution system.

Copy mission audio recordings in response to official requests

Directory: eps -> eps data

Download 0.5 Mb.

Share with your friends:

1 2 3