80AFRC19R0022 Amend 2.pdf
PDF 2 MB Posted
- Attached to
- Research Facilities and Engineering Support Services (RF&ESS) Federal contract opportunity
- Solicitation number
- 80AFRC19R0022
About this file
This is a request for proposals from the National Aeronautics and Space Administration Armstrong Flight Research Center for research facilities and engineering support services. The solicitation seeks proposals to provide engineering and technical services to support the Center's Mission Operations Directorate, including Dryden Aeronautical Test Range operations and engineering, Simulation Lab support, and center-wide information technology services. Proposals are due in accordance with the communication and submission instructions provided. The North American Industry Classification System code is 541513 for computer facilities management services, and the procurement has a 100% small business set-aside. Offerors should monitor the Government Point of Entry for any amendments. The Center Ombudsman contact information is also included.
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| 80AFRC19R0022 Amend 3.pdf | ||
| RFP Q and A.pdf | ||
| 80AFRC19R0022 Amend 3.pdf | ||
| 80AFRC19R0022 Amend 1.pdf | ||
| 80AFRC19R0022.pdf |
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
For the best experience, open this PDF portfolio in
Acrobat X or Adobe Reader X, or later.
Get Adobe Reader Now!
http://www.adobe.com/go/reader
Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:
(a) By completing items 8 and 15, and returning or (c) By separate letter or electronic communication which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by letter or electronic communication, provided each letter or electronic communication makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.
E. IMPORTANT: Contractor is not is required to sign this document and return copies to the issuing office.
AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 1. CONTRACT ID CODE
2. AMENDMENT/MODIFICATION NUMBER 3. EFFECTIVE DATE 4. REQUISITION/PURCHASE REQUISITION NUMBER 5. PROJECT NUMBER (If applicable)
7. ADMINISTERED BY (If other than Item 6) CODE
STANDARD FORM 30 (REV. 11/2016)
Prescribed by GSA FAR (48 CFR) 53.243
FACILITY CODE
9A. AMENDMENT OF SOLICITATION NUMBER
9B. DATED (SEE ITEM 11)
10A. MODIFICATION OF CONTRACT/ORDER NUMBER
10B. DATED (SEE ITEM 13)
11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS
The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offers is extended. is not extended.
12. ACCOUNTING AND APPROPRIATION DATA (If required) copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;
13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.
IT MODIFIES THE CONTRACT/ORDER NUMBER AS DESCRIBED IN ITEM 14.
CHECK ONE A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT ORDER
NUMBER IN ITEM 10A.
B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation data, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).
C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:
D. OTHER (Specify type of modification and authority)
Revisions to the PWS are listed in the Document History log and are identified in red font.
Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.
15C. DATE SIGNED
15A. NAME AND TITLE OF SIGNER (Type or print)
16C. DATE SIGNED
16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)
14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)
PAGE OF PAGES
6. ISSUED BY CODE
8. NAME AND ADDRESS OF CONTRACTOR (Number, street, county, State and ZIP Code) (X)
CODE
15B. CONTRACTOR/OFFEROR
(Signature of person authorized to sign)
16B. UNITED STATES OF AMERICA
(Signature of Contracting Officer)
Previous edition unusable
00002
Lisa A. Jackson, Contracting Officer
The purpose of this amendment is to correct the due date on attachment L03 Past Performance Questionnaire and revise the
PWS.
The L03 Past Performance Questionnaire due date is hereby changed from "...no later than December 23, 2019" to "...no later than January, 23, 2020"
NASA/Armstrong Flight Research Center P. O. Box 273 M/S 4811-140 Edwards CA 93523-0273
ALL PROSPECTIVE OFFERORS
80AFRC19R0022
80AFRC19R0022
1 1
12/17/2019
12/06/2019
PERFORMANCE WORK STATEMENT
Research Facilities and Engineering Support Services
(RF&ESS)
ENGINEERING AND TECHNICAL SERVICES FOR AERONAUTICAL FLIGHT TEST
RANGE, SIMULATION, AND INFORMATION TECHNOLOGY SUPPORT
Mission Operations Directorate, Code 600
November 4, 2019
National Aeronautics and Space Administration Armstrong Flight Research Center Edwards, California
DOCUMENT HISTORY LOG
Revision Number Date Brief Summary of Changes
12/17/2019 1. Added Microsoft Project Server Support. Reference paragraph 5.9, WBS 310 and Appendix A.
2. Added JIRA support. Reference 5.9, WBS 310 and Appendix A.
3. Added language for individual office monitor mounting, para. 5.15, WBS 420.
Table of Contents
1.0 Research Facilities and Engineering Support Services (RF&ESS) Contract
1.1 Scope
2.0 RF&ESS Vision, Goals, and Objectives
2.1 Performance Requirement Summary (PRS)
3.0 General Requirements
3.1 Export Control
3.2 Place of Performance
3.3 Travel
3.4 Work Schedule
3.5 Government Furnished Property (GFP) and Contractor Supplied Vehicles
3.6 Work Breakdown Structure (WBS)
4.0 Contract Administration and Business Management
4.1 Staffing
4.2 Compliance: Regulatory, Statutory, Agency, and Center
4.3 Quality
4.4 Security
4.5 Safety
4.6 Training
4.7 Property Control
4.8 Purchasing
4.9 Facility Management
4.10 Contract Management Information Systems
4.11 Deliverables
4.12 Interface with Other Organizations
5.0 Work Breakdown Section (WBS)
5.1 WBS 110 DATR TRAPS and MCC Systems and Software Engineering
5.2 WBS 120 Range Specialized Engineering Services
5.3 WBS 130 Range Engineering Support
5.4 WBS 140 Dryden Aeronautical Test Range Video Systems
5.5 WBS 150 DATR Tracking and Mobile Systems
5.6 WBS 160 DATR Communications
5.7 WBS 210 Simulation Systems Engineering Sustaining Support
5.8 WBS 220 SIM Custom Computer System Buildup and Support
5.9 WBS 310 Applications Development and Operational Support Services
5.10 WBS 330 Data Center and System Administration Services
5.11 WBS 340 Service Desk and Business Support Services
5.12 WBS 350 IT Systems Engineering Services
5.13 WBS 360 Office of Protective Services (OPS) Support Services
5.14 WBS 410 Administrative and In-Flight Photography Services
5.15 WBS 420 Administrative-Audio/Video and In-Flight Video Support Services
5.16 WBS 430 Graphics and Illustration Services
5.17 WBS 510 Program Management Services
Appendix A Systems/Applications/Locations Appendix B: Acronyms and Abbreviations Appendix C Certifications Table
1.0 Research Facilities and Engineering Support Services (RF&ESS) Contract NASA requires engineering and technical services to support the Armstrong Flight Research Center (AFRC) Mission Operations Directorate.
The Directorate’s mission is to provide NASA with efficient and effective Dryden Aeronautical Test Range (DATR) operations and engineering, Simulation Lab (SIM) support, and center-wide information technology (IT) services. The Research Facilities and Engineering Support Services contract (RF&ESS) (hereafter referred to as “the contract”) provides engineering and technical services required to meet the mission.
1.1 Scope
The contractor shall provide labor and materials to perform development, test, engineering, analysis, specification, design, development, installation, integration, operation, maintenance, documentation, training, customer outreach, change management, configuration control, troubleshooting and related functions. These responsibilities branch across three primary functional areas:
DATR operations and engineering services, SIM support services, and Center-Wide IT Services
1.2.1 DATR Operations and Engineering
The DATR mission is to support flight research operations and low-Earth-orbiting (LEO) missions.
Operations and missions include aerospace flight research and technology integration, space exploration concepts, airborne remote sensing and science missions, and range operations of the International Space Station (ISS).
The DATR supplies a comprehensive set of resources for the control and monitoring of flight activities, real-time acquisition and reduction of research data, and effective communication of information to flight and ground crews. DATR systems and facilities include:
Telemetry Systems Time Space Position Information Systems (TSPI) Video Systems Radio Frequency (RF) Communication Systems Ground Voice Communication Systems Data Distribution Systems Data Archival Systems Real-Time Data Processing/Monitoring Systems Range Safety Ground Flight Termination Systems Post-Flight Systems
See figure 1 below for an example DATR configuration.
Figure 1. Example of DATR configuration
1.2.2 Simulation Support Services
SIM Engineering supports flight research at various AFRC sites by providing aerospace simulation, hardware in-the-loop (HIL) testing, and remotely augmented vehicle computer systems to the research staff. Contractor support includes system and mechanical engineering, system administration, and computer aided design and modeling (CAD/CAM) support.
Examples of simulation can be seen in Figure 2.
Figure 2. Example of Simulation (SIM)
1.2.3 Center-Wide IT Services
Center-Wide IT supports AFRC missions and business functions by providing a broad range of information technology and multimedia services. This support includes:
Management and operations of the primary data center and related server rooms System administration and support for centrally-managed servers as well as uniquely-configured lab and engineering computers Application development and programming support
Application administration and analysis Database design and administration Web design and maintenance IT security operations and expertise System Security Plan (SSP) development and administration IT systems engineering IT consulting and training IT research and infusion Operations and maintenance of physical security systems and infrastructure Help Desk and conference room support Multimedia including graphics, photo, and video services Graphics illustration services
2.0 RF&ESS Vision, Goals, and Objectives
Vision-Partners for Mission Success
The AFRC Mission Operations Directorate partners with other AFRC and NASA organizations for mission success. The RF&ESS contract will augment the directorate with a proficient staff to enable Mission Operations to provide effective, efficient and secure Range, SIM, and IT solutions.
Goals
Build and sustain a reputation as a trusted partner with NASA organizations, programs, and projects, in the areas of Range Operations and Engineering, SIM support, and Center-Wide IT services.
Produce high quality flight test data solutions and products which meet project and NASA requirements.
Proactively manage all assets through the complete life cycles.
Produce and maintain flight simulations for multiple vehicles and multiple phases of flight test, in alignment with project and NASA requirements.
Seamlessly and transparently implement IT security management and Center-Wide IT systems and applications solutions and support.
Objectives
Proficiently operate and maintain AFRC’s mission control rooms, telemetry, radar, video systems, Flight Termination Systems (FTS), multichannel ground intercom and radio frequency communications, supporting real time monitoring of flight research vehicles and other targets.
Provide mission critical range engineering services which:
o Enable flight research customer specific real-time calculations, displays, and capabilities o Advance range capabilities to meet future demands and improve operational efficiency
Develop, operate and maintain high-fidelity flight simulations which support various research phases. Phases range from conceptual studies through flight test, and provide research tools which enhance the application of simulation data to achieve research objectives.
Develop, operate, and maintain IT hardware and software systems to support collaboration and data/information management as well as enabling center and project management/business processes.
Incorporate evolving NASA and Federal Government cybersecurity requirements.
Recommend and implement strategies and solutions to improve the effectiveness, efficiency, and security of AFRC-managed IT infrastructure. Strategies and solutions enable a dynamic flight test environment.
2.1 Performance Requirement Summary (PRS)
The Performance Requirement Summary (PRS) lists and defines the work that the PM and COR determine are most important to monitor and evaluate, the acceptable quality and frequency of inspections for all Work Breakdown Structures (WBS). Metrics are identified in detail in the Quality Assurance Surveillance Plan. Metrics are summarized in PWS Attachment 1.
2.1.1 Surveillance
Work is monitored by the COR as delegated by the CO. The COR delegates Technical Monitors (TMs) for each WBS, who establish goals and priorities within the WBS. The TM interfaces directly with WBS personnel as needed for detailed technical matters or daily operational issues.
The COR also delegates Performance Monitors (PMs), who oversee and report on performance for multiple WBS areas.
NASA retains the right to review and approve processes, procedures, plans, and documentation for operations, maintenance and repair, configuration control, and engineering development associated with the WBS.
3.0 General Requirements
The Contractor shall comply with all requirements which apply to all functions, services, and products of this contract. Unless specified otherwise herein, the Contractor shall comply with these requirements at the commencement, and throughout the duration, of contract. NASA will provide government-furnished facilities, workspace, process information and equipment.
3.1 Export Control
NASA contractors and subcontractors are subject to U.S. export control laws and regulations, including the International Traffic in Arms Regulations (ITAR), 22 CFR Parts 120 through 130, and the Export Administration Regulations (EAR), 15 CFR Parts 730 through 799.
3.2 Place of Performance
The permanent duty location is AFRC, Edwards, California. Work is performed at AFRC Building 703 in Palmdale, California on an as needed basis. The duty location is determined by NASA.
3.3 Travel
Travel may be required in conjunction with the performance of work requirements. Allowable travel costs are determined in accordance with Federal Acquisition Regulations (FAR) 31.205-46 the Federal Travel Regulations (FTR), and the Joint Travel Regulation (JTR). Travel must be coordinated through the Contracting Officer’s Representative (COR) and is not authorized until approved by the Contracting Officer
(CO).
For any foreign program travel related to this contract, the Contractor shall comply with NASA Procedural Requirements (NPR) 9710.1, chapter 7.2 entitled Foreign Travel. The Contractor shall submit all foreign travel requests to the AFRC Foreign Travel Coordinator for review/approval a minimum of four weeks before the planned departure date, so that an electronic country clearance (eCC) can be obtained.
The AFRC Foreign Travel Coordinator information can be located at the following link: https://afrcshare.ndc.nasa.gov/orgs/XM/C/Pages/Portal.aspx.
The contractor shall arrange and coordinate all travel required. The contractor shall submit requests in writing for all travel to the COR before the contractor incurs the costs.
3.4 Work Schedule
AFRC operates under a flexible work schedule. The schedule permits employees to work 80 hours in 9 days (known as a 9/80 schedule) and have a non‐work day every other Friday. The core hours are between 8:00 am and 3:00 pm Pacific Standard Time (PST) Monday through Thursday and the second Friday of the NASA pay period.
The nature of NASA’s and AFRC’s missions may require support outside of the core hours. Exceptions to core hours may include weekend hours or alternate shift hours in support of project specific schedules.
Exceptions to the schedule will be on a case-by-case basis.
3.5 Government Furnished Property (GFP) and Contractor Supplied Vehicles
3.5.1 Special Use Vehicles
Special use vehicles are government furnished. The contractor shall be responsible for the maintenance of the mission support systems installed in special use vehicles, such as mobile range support systems and sub systems, video and frequency vans. The contractor shall operate these special systems and vehicles. The contractor is not responsible for performing the automotive maintenance and repair of the vehicle. The Contractor shall ensure the vehicle receives the required maintenance; the maintenance is provided by NASA.
3.5.2 Standard Use Vehicles
The Contractor shall provide transportation (non-specialized vehicles) for the transport of personnel and equipment in performance of this contract. Establishment of vehicle lease with GSA is authorized.
3.5.3 Government Furnished Listing
Property, including special use vehicles, is listed in Contract attachment J-02. Also reference section 4.7, Property Control.
3.6 Work Breakdown Structure (WBS)
WBS describes and organizes requirements into discreet sections, see section 5.0 Work Breakdown Structure. WBS elements are subject to revision or deletion, or new WBS elements may be added or deleted by contract modification as requirements and funding availability change.
Services required may involve the delivery of new systems capability, additional temporary services, engineering studies or projects. This may require expertise or services beyond the capability or capacity of the resident staff and/or available equipment and materials. The contractor shall be capable of performing and supporting these services.
All documentation developed in support of this contract is the property of the Government and may be retained and redistributed as necessary in support of current and future work. Exceptions to this requirement must be documented and accepted by the CO in advance.
3.7 Submission of Vouchers/Invoices for Payment
The contractor shall submit vouchers/invoices in accordance with 1852.232-80. Additionally, the voucher/invoice structure shall be formatted to reflect charges per WBS.
4.0 Contract Administration and Business Management
The Contractor shall provide on-site management and establish a management plan to fulfill the requirements. The Management Plan shall describe the contractor’s concept plans, practice, and approach for accomplishing the requirements set forth in the contract, i.e., managing and controlling WBS and management interfaces. (Ref. DRD 2 Management Plan). The Contractor shall manage its workforce to ensure that quality products and safe operations are provided to NASA and NASA customers.
4.1 Staffing
The contractor shall staff in accordance with the requirements established in the PWS. The contractor shall adjust their schedules to minimize overtime and premium pay in accordance with the schedules and priorities set by NASA.
4.1.1 Key Personnel
The contractor shall staff key personnel positions as follow:
1. RF&ESS Program Manager-WBS 510
2. Systems Engineering Manager-WBS 110
3. Operations and Maintenance (O&M) Manager – Range Services-WBS 510
4. Operations and Maintenance (O&M) Manager – IT – WBS 510
4.1.2 Temporary Staff Augmentation
The contractor shall have the capability to provide qualified staff to support peak workloads, short-term (surge) requirements, or temporary absence of permanent staff.
NASA expects to require future increases in services as the AFRC mission portfolios change and grow.
The contractor shall have the capability to augment staff until on-site staff becomes proficient.
4.1.3 Overtime
Overtime hours are required to respond to emergencies, unusually heavy workloads, and unexpected situations which may occur due to unforeseen service requirements. The contractor shall minimize the use of overtime, particularly as a regular employment practice. Overtime pre-approval is required by the government; requests for work hours in excess of the designated work schedule shall be submitted in writing to the TM.
4.1.4 Employee listing
The contractor shall provide an organization chart displaying the contractor structure by WBS. Each WBS shall include the supervisor/lead, and employee names. The report shall also provide a spreadsheet with a breakout of each WBS by employee and include percentage of time for each of the WBS’ supported. The report shall provide the total number of employees for the contract by WBS and by Code 600 Directorate Branches for each month of the contract. References DRD-3.
4.2 Compliance: Regulatory, Statutory, Agency, and Center
The contractor shall adhere to all Federal, Agency, and AFRC policies. Requirements include NASA Directives and NASA standards as well as the policies and procedures listed in the Armstrong Management System (AMS). As these governance documents are revised, the contractor shall comply with the current version.
4.3 Quality
The Contractor shall provide, implement, maintain and continuously utilize a comprehensive International Organization for Standardization (ISO) Quality Assurance Program (QAP). The Contractor's QAP shall be AS9100 third party certified to the current American National Standards Institute (ANSI)/American Society for Quality (ASQ)/ISO Quality Management Systems Requirements. (DRD 6 Quality Control Plan)
In the event of conflict between the Contractors QAP and NASA governance, NASA governance shall takes precedence.
Evidence of Offeror’s compliance with AS9100 shall be submitted with Proposals. Third Party Certification for AFRC RF&ESS scope is required within 3 months after contract start date.
4.4 Security
The Contractor shall meet the minimum security requirements listed in the “Contract Security Classification Specification”, DD Form 254. Access to Communications Security (COMSEC) material is required during performance of this contract. Required COMSEC material will be furnished by the NASA COMSEC Manager. Personnel accessing COMSEC material must have a final secret clearance.
The contractor shall ensure adherence to NASA guidance for classification and safeguarding classified information, NASA security program procedural requirements, and applicable NASA and Department of Defense (DoD) directives. The contractor shall perform investigations and submit reports related to security incidents, infractions, and/or adverse information.
Work in support of classified projects/programs and Personally Identifiable Information (PII) requires that contractor personnel be able to obtain a secret clearance. All WBS 100 and 200 personnel require secret clearances. Most WBS 300 and 400 personnel require secret clearances.
4.4.1 Contractor Access
Access to the facility Contractor personnel shall be made available as required per AFOP-1620.3-001, Authorization for Access to Controlled Areas. The contractor will provide a point of contact, an “Identity Requester”, who will coordinate the access level submissions.
Visit requests are handled in accordance with AFOP-1600.1-001, Visitor Control.
4.5 Safety
The Contractor shall provide, implement, maintain and continuously follow a comprehensive Safety and Health Plan, in accordance with NASA Federal Acquisition Regulation (FAR) Supplement (NFS) 1852.223-72, Safety and Health Plan (Short Form), and with DRD 1, Safety and Health Plan. The plan shall address all WBSs
4.5.1 Personal Protective Equipment (PPE)
The contractor shall provide Personal Protective Equipment (PPE). PPE shall be at no additional cost to NASA and in accordance with OSHA safety practices. Examples of PPE are hearing protection, safety shoes, clothing, helmets, and goggles.
4.5.2 Radiating Equipment
The contractor shall comply with all NASA RF management directives and guidelines. The contractor shall receive prior approval before operating or procuring any radiating equipment. Obtain approvals from AFRC RF Spectrum Manager or designated alternate, in accordance with AFOP-2570.1-001.
4.6 Training
The Contractor shall provide trained, qualified and certified personnel. The level of expertise shall be equal to or greater than equivalent government-accepted labor classifications for all WBS elements. The Contractor shall develop, document, and implement a training and certification process that assures all Contractor personnel are properly trained, qualified and certified for the tasks required which includes the operation of special purpose Government equipment and all associated safety requirements.
The Contractor shall maintain training and certification records for each employee and make the records available to the government. The Contractor shall provide environmental, health, and safety training to ensure employee compliance with NASA, Federal, State, and local laws, regulations, and instructions. The Contractor is responsible for paying for all required training, licenses, or other qualifications, unless the training is identified as NASA specific or is available from NASA. The contractor is authorized to attend NASA provided training classes on a space available basis.
The Contractor shall be responsible for scheduling the attendance of Contractor personnel at training, obtaining Government approval as needed. The Contractor shall minimize the interruption of NASA operations.
Employees that require access to the Flight Line and areas controlled by the Air Force require specialized training. Personnel requiring special area access must be cleared and badged appropriately.
4.6.1 NASA Specific Training
NASA specific training will be identified by and paid for by NASA. Examples of NASA specific training include altitude chamber, climbing towers up to 150 feet, and survival training for photographers and videographers.
Request for NASA specific training shall be submitted in writing to the TM prior to the contractor's incurring training expenses.
4.6.2 Training of Center Employees
The Contractor shall train both systems-level and general users on the systems for which they support.
The persons to be trained may be either NASA employees or NASA contract employees (on either this contract or other contracts) who use or otherwise interface with the systems to be supported under this contract. Systems supported under this contract are located at Appendix A.
4.7 Property Control
The successful offeror/contract awardee shall conduct a 100% Property Inventory with the incumbent contractor during Contract Phase-In. A complete Property Inventory is due at contract start date.
The Contractor shall develop and implement an effective management approach for monitoring and tracking Government Furnished Property (GFP). The contractor shall comply with all NASA rules and regulations regarding property management. ‘Equipment’ shall be used as the equipment control system.
Property shall be managed in accordance with NASA Procedural Requirement (NPR) 4200.1H NASA Equipment Management Procedural Requirements.
The Contractor shall report annually NASA property inventory in the Contractor’s custody which was government furnished or which was acquired by the Contractor under the terms of the contract. (Reference DRD 12). The Contractor shall be responsible for safeguarding all government equipment, information and property provided for Contractor use. At the close of each work period, government facilities, equipment, and materials shall be secured. Also reference paragraph
4.8 Purchasing
The contractor shall purchase supplies to meet the requirements of the contract. All materials purchased become the property of NASA. The acquisition of centrally reportable items requires thirty (30) days prior notice of the purchase to the NASA Contracting Officer using DD Form 1419, "DoD Industrial Plant Equipment Requisition." Upon receipt of the equipment, the contractor shall submit to the Property Officer
DD 250, "Material Inspection Report," so the equipment can be tagged as Government property and entered into the NASA Property System titled “Equipment”.
The contractor shall have and utilize a Government-approved purchasing system for purchasing materials and services in support of this contract.
Purchased equipment entered in an equivalent approved system shall be cross-referenced by tag number to ‘Equipment’.
Contractor-procured equipment shall be delivered to NASA shipping and receiving facilities. All processing of delivered items shall be the contractor's responsibility, including prompt disposal of shipping boxes, crates, and packing materials. The contractor shall assure that all new equipment received is properly identified and tagged.
4.9 Facility Management
The contractor shall implement and maintain a uniform process of managing the use of the following NASA-provided areas:
DATR Third Floor (Building 4800) DATR Second Floor (Building 4800) DATR COMMUNICATIONS (Building 4824) DATR Aeronautical Tracking Facility (ATF) 1 and ATF 2(Building 4982 and 4720) Warehouse (Building 4857)
4.10 Data Management
The contractor shall provide and utilize an electronic method for submitting, tracking, and efficiently reporting to NASA the services, material, and training necessary to support the contract.
4.11 Deliverables
Reports generated shall meet NASA requirements for tracking and reporting contractor effort. The Contractor shall provide reports digitally except as identified for hard copies of reports.
4.12 Interface with Other Organizations
NASA, as well as other Government agencies and Government contractors, perform related functions and services that provide inputs to, services for, or require outputs or services from the contractor. In all cases, the contractor shall be required to functionally interface/collaborate with, other organizations to satisfy operational requirements of the systems and services supported.
WBS 100 SERIES GENERAL DATR REQUIREMENTS
The following are applicable to all WBS 100 series requirements. Work in these WBS may require climbing towers up to 150 feet.
DATR Mission Support Services The DATR functional tasks during flight/mission support services are to acquire downlink telemetry data, radar tracking data, audio and video while utilizing government provided ground based equipment. A real-time mission is a flight or ground test with a vehicle. A non-real-time mission is data recaptures from ground-based telemetry and TSPI recordings or telemetry data playbacks to the MCC.
There are ground-based tracking and MCC systems that are mobile (See Appendix A). These mobile assets may be moved to locations other than at Edwards Air Force Base, Edwards, California and Palmdale, California. In those cases, contractor personnel may need to travel to these sites to maintain and operate these assets.
The Contractor shall provide support for project-owned ground-based systems (e.g. ground control station display workstations, voice and video systems, satellite communications equipment) necessary for operation of current flight projects, both local missions and remote deployments. This support shall include, but is not limited to, the power up, configuration, operations monitoring, and shut-down of these project-specific systems, as defined in a DATR Range Support Agreement (RSA).
Some missions utilize Unmanned Aerial Vehicles (UAVs) that require onboard Flight Termination System (FTS) or Enhanced Flight Termination System (EFTS). The Contractor shall install, maintain, repair and operate ground-based FTS and COMSEC compliant EFTS Transmitter and control systems.
The Contractor shall, record and distribute the downlink telemetry data, video, radar tracking data, and audio data; distribute, process, and display the data in the MCC. After a flight, the Contractor shall post flight processes telemetry and TSPI data, and posts the post-processed data to the Centers post flight data portal; makes copies of downlink flight video and voice recordings and distributes.
The contractor shall provide personnel to be able to simultaneously support at least two real time missions.
DATR Operations, Maintenance, and Repair Requirements The contractor shall operate and maintain systems identified in Appendix A. The contractor shall purchase spare parts, maintenance supplies, tools, and equipment, which are not otherwise provided as Government-furnished property.
The contractor shall perform the technical analysis, interpretation, and evaluation of problem areas to determine if the problem is hardware, software or procedural. The contractor shall analyze problems, recommend and implement solutions, and shall be proactive in taking measures to avoid potential problems.
The contractor shall ensure that NASA is informed in advanced of any current or potential shortfalls in spares or equipment end of life issues.
The contractor shall perform maintenance, troubleshooting, installation, diagnosis, 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 systems is achieved, (or as otherwise specified in a particular WBS) not including scheduled downtime such as for preventative maintenance or configuration changes.
Systems Operations and Maintenance program Upon contract transition, the Contractor will receive the existing NASA-owned Systems Operation and Maintenance Plans (SOMP) and Work Instructions (WI). Using this NASA-provided information, the Contractor shall establish and conduct an operations and maintenance program for each of the required WBS areas. Each program consist of multiple SOMPs and WIs. These procedures shall comply with manufacturers' specifications and NASA operating standards, and shall be updated when new equipment or requirements dictate. Revised SOMPS shall include a revision number and shall identify the changes.
These plans shall be approved by NASA. Unless otherwise specified each SOMP or WI shall, as a minimum, include procedures for:
Maintaining an accurate inventory and status.
Tracking, ordering, and stocking materials and spare parts necessary for equipment/system operation and maintenance. Assuring delivery of replacement parts to maximize operational readiness and repair capabilities.
Complying with configuration control on all equipment.
Maintaining current system operations logs.
Maintaining a log for each system in Appendix A. The log shall identify what was done, why, when and by whom.
Performing file backup and archiving.
Scheduling preventative maintenance tasks including, but not limited to, system alignment and running diagnostic programs.
Determine when support from the Original Equipment Manufacturer (OEM) or outside experts is required.
Handling and disposing of hazardous materials.
DATR Operations The Contractor shall provide personnel to configure, support, and operate DATR systems during mission operations. The Contractor shall perform system maintenance on DATR systems and adhere to all policies, SOMPs, and WIs during all phases of mission support.
The Contractor shall maintain a mission and maintenance log of all work performed on all systems including preventative maintenance. This information shall be captured in NASA’s Business Information Tracking System (BITS). The contractor shall verify and validate all work performed on mission critical systems.
The verification and validation must be electronically signed. The verifier must be a separate individual from the validator.
The contractor shall perform a system functional checkout after maintenance or modifications are performed. 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 maintain a stock of working spares sufficient to achieve a 95% uptime on each mission system or as otherwise specified in the particular WBS element.
5.1 WBS 110 DATR TRAPS and MCC Systems and Software Engineering Contractor performs systems engineering, software engineering, and network engineering for networked computers used to process radar and telemetry data (TRAPS) for real time display and monitoring by researchers in the Mission Control Centers (MCC). This system of networked PC-based platforms is called DATR WATR Integrated Next Generation System (WINGS). The contractor, also, can be tasked to perform these services for the development, enhancements of DATR range systems and of project-owned ground-based systems used and operated by projects.
WINGS allows projects to monitor real time data for test point clearance and data quality, and monitor aircraft situational awareness in a MCC. WINGS archives flight data and made available for post flight long term data storage.
The contractor shall:
Develop and track technical specifications.
Develop and track cost, schedule, estimates, and actuals.
Collect, generate, and distribute weekly reports required by the TM.
Participate in and adhere to the DATR CCB process AFOP 7123.1-003.
Application Software Support WINGS in-house software is developed to process a project telemetry map specification and project defined software algorithms and generate WINGS setup files. In-house software is also developed to automate the distribution of setup files, automate startup and shutdown of PC based computers on the day of the mission using a MCC. In-house software is developed to time stamp, format, and archive flight data stored on near-term data storage. In-house developed software supports WINGS and WINGS capability enhancements to meet specific project real time and post flight requirements. Software engineering support can also be performed for the development, enhancements of DATR range systems.
Software developed uses information about RCC IRIG 106 standards, about the telemetry front end system and data time tagging used in WINGS, about processing and displaying TSPI data for situational awareness, real time data processing and displaying, and about post processing formats. Software is developed in the Microsoft .Net Framework and Linux environments. Programming languages used: C, C#, and C++. Use object-oriented programming paradigm.
Software is developed, configuration controlled, and maintained. Software is maintained for current fielded systems while going through the software development life cycle for the development of the next set of software releases for the next system release.
Develop, test in-house software in accordance with AFOP-7150.2-001. Develop supporting documentation to support process.
Perform the requirements analysis.
Prepare and implement validation and verification (V&V) plans in support of AFOP-7150.2.
Perform required porting of software from existing platforms to new technologies.
Perform software beta testing and prototyping.
Determine software performance.
Write and develop documents to support DATR Configuration Change Request (CCR) and DATR
System Test Report (STR).
The contractor shall port code or implement algorithms provided by projects for use in WINGS real time and post flight data processing. Implement algorithms in or port calculations (ex. written in Matlab, Python, etc.) to C programming language. Support V&V of developed software. Serve as the expert in the developed code (also known as “project specific” user-defined derived calculation) implementation.
Modify and maintain ported calculations.
The contractor shall provide calibration/telemetry map information subject matter expertise (SME) and provide troubleshooting/workarounds to instrumentation engineers and CIMS II software operators to meet project deadlines.
Systems Engineering Support WINGS consists of a telemetry front end performing telemetry data decommutation and engineering units conversion implemented by a third party hardware and software product. WINGS also consists of a real time data display system in the MCC and is implemented by a third party software product.
Systems engineering is used to integrate third party and in-house software to develop a real time data processing, data archiving system, see Appendix A. Systems developed uses information about RCC IRIG 106 standards, IRIG time formats and timing systems, data distribution system, about the telemetry front end systems (vendor provided hardware and software), about time-space-position-information (TSPI) data, real time data processing, about data archiving, networking and network protocols, and data storage technologies. Familiar with Consultative Committee for Space Data Systems (CCSDS) standards for space data and information systems data. System and processes are developed for operational use by DATR Operations group. Processes are developed for transferring archived flight data to IT for long term flight data storage.
WINGS enhancements are made to meet NASA IT requirements and MCC project real time and post flight data requirements.
Technology changes in the following typically results in enhancements:
RCC IRIG 106 standards, a comprehensive telemetry standard to ensure interoperability in aeronautical telemetry application at RCC member ranges
Third party vendor hardware/software supportability NASA IT approved network equipment NASA IT approved Intel and Linux operating systems, 32-bit and 64-bit architectures Near-term data storage (on the order of gigabytes), such as Redundant Array of Independent Discs
(RAID), Network Attached Storage (NAS), etc.
Consequently, prototyping advanced capabilities will require the development of new subsystems and interfaces to support communication with entities external to the test range. Prototyping is staged and evaluated in a development lab. Furthermore, current fielded systems are maintained while going through the systems engineering development life cycle for the development of the next system release.
Systems engineering support can be performed for the development, enhancements of DATR range systems and of project-owned ground-based systems used and operated by projects.
Perform system architecture design, systems engineering, software engineering, and mission network engineering services.
Perform systems engineering in accordance with AFOP-7120.1-002. Develop supporting documentation to support process.
Perform trade-off studies.
Perform requirements analysis.
Design new or modify existing systems and subsystems.
Assist in the preparation of software and system development plans that encompass system overview, objectives, justification, approach, resource requirements, and scheduling.
Prepare implementation plans that encompass system overview, objectives, justification, approach, resource requirements, and scheduling.
Prepare and implement V&V plans in accordance with AFOP-7120.1-002.
Configure Linux and Windows computers with third party software, interface hardware, and in-house developed software according to system requirements.
Provide computer system administration, system backups and network administration for Linux and Windows PC based systems in the MCCs, TRAPS, development lab and DATR engineering systems.
Integrate third party software into the DATR operational environment.
Develop methods and determine materials required for system installations.
Assess and evaluate system and subsystem performance during design, V&V, or operational use, document findings, and make recommendations.
Provide operational support of systems in engineering status when required to obtain information and data necessary for troubleshooting system issues and/or for running development systems in-parallel for system, integration, and acceptance testing. (Such as serving as a TRAPS Operator on systems that are in in-active operational status)
Assist DATR operations personnel in the installation checkout process.
Support system transition to operational status.
Provide initial training on new operational systems.
Provide operational support to the projects as required.
Perform system-level troubleshooting. Provide troubleshooting support to DATR operations personnel.
Provide troubleshooting support for third party software. Apply systems and software engineering analysis to identify and resolve issues that involve multiple third party system and/or software vendors.
Support maintenance and repair inquiries from the DATR operational personnel.
Sustain and upgrade existing and future TRAPS and MCC systems.
Maintain Configuration Item (CI) identification for all system and software releases, revisions and documentation.
Develop and maintain a library of current and archived documentation required for the operation and development of TRAPS and MCC systems for hardware and applications. Documentation includes users/operators guides.
Propose system changes and additions that improve the operational environment, expedite system releases, and enhance the development processes identified in AFOP-7150.2-001 and AFOP- 7120.1-002.
Consult with project representatives to provide system capabilities and isolate discrepancies.
Maintain the development lab in a configuration that provides a development and test environment. The environment will need to accommodate currently floored configurations and next generation research and development projects.
DATR Information Assurance Engineering Services The DATR range assets require Information Assurance engineering support services to evaluate, implement, test and document the current IT system information assurance capabilities in support of Armstrong Information Assurance requirements. Assurance services ensures real time and post flight data integrity.
Requires a working knowledge of IT Security and Local Area Network (LAN) policies and directives, NIST, FISMA and ISC2’s 10 domains of information security for analysis and application to SSP.
Define and provide suggestions and author LAN and IT Security system policies, procedures and guidelines
Implement IT Security controls specified in NPD 2810.1E, NPR 2810.1A, NIST SP 800-53 https://nvd.nist.gov/800-53, and FIPS-199 https://csrc.nist.gov/publications/detail/fips/199/final
Test and evaluate compliance with specified security controls relative to system requirements and document risk assessment.
Create the DATR IT SSP’s and assist with NASA Assessment and Accreditation (A&A) documentation preparation and audits.
Document issues identified with security audits and plans for addressing the issues and present plans to the Authorizing Official (AO)
Document justifications and reasoning for not addressing security audit issues and present justifications to AO.
Edit and maintain computer security documentation in the NASA information assurance database.
Provide guidance on the A&A process and track SSP progress and deadlines.
Perform monthly security audits and assessments including network infrastructure and network connected equipment Coordinate with NASA Security Operations Center (SOC) regarding security incidents Responsible for reporting and task tracking for IT security related local activities
5.2 WBS 120 Range Specialized Engineering Services
This WBS is to be utilized by field service engineers for reporting engineering type work. This WBS utilizes staffing assigned to other 100 series WBSs.
Radar, telemetry tracking, range safety flight termination, voice communications, video optics, and associated data recording and data distribution systems need to be modified, upgraded to increase system capability, capacity, to provide up-to-date systems and services, and to ensure system stability. These systems are located at AFRC DATR facilities or at remote locations, configured as fixed assets, as part of Mobile Operations Facilities (MOFs) or as part of Ground Control Stations (GCSs).
Perform systems engineering tasks directed by the TM.
Provide engineering development services that requires highly specialized technical knowledge regarding radar and telemetry tracking systems, voice communications systems, video optics systems, data distribution networks, data processing systems, ground-based range safety flight termination systems, and data recording systems.
Develop software and system following process AFOP-7150.2-001 and AFOP-7120.1-002.
Analyze and document functional requirements.
Make design recommendations. Conduct and present design reviews.
Provide technical documentation in support of process AFOP-7150.2-001 and AFOP-7120.1-002 Develop and track technical specifications.
Develop and track cost, schedule, estimates, and actuals.
Implement system design and modifications.
Determine and document system performance limits.
Evaluate, test, checkout and install new equipment.
Participate in the testing to evaluate the accuracy, interoperability and suitability of operational support hardware and software.
Conduct processes required to ensure the hardware/software systems still meet the current established requirements and any additional requirements due to upgrades and or modifications.
Develop operational procedures.
Adhere to established Configuration Control procedures AFOP-7123.1-003.
5.3 WBS 130 Range Engineering Support
This element encompasses configuring control room data processing and data display buildup, monitoring of real-time systems and applications, processing of post-flight mission data, and providing mission systems support for the DATR. Mission systems support responsibilities include, but are not limited to, the buildup, real-time and post-flight support, maintenance, repair, fabrication, integration, assembly, installation, calibration, test, reconfiguration, modification, and develop and modify operational documentation of all TRAPS and MCC systems and direct support equipment. This includes Range timing, Time-Space- Position-Information (TSPI), and GPS systems.
Provide real-time and post-flight engineering, maintenance, and repair support. Support procedures shall be described in the SOMP and comply with manufacturers' specifications and NASA standards, and shall be updated as necessary to reflect any new equipment, software, or requirements changes. Each SOMP shall describe engineering support procedures, maintenance procedures, or repair procedures for systems and subsystems. SOMPs and WIs shall be developed and maintained by the contractor, and approved by NASA.
Perform weekly backups of project files.
Maintain an effective emergency action plan, to include procedures for shutting off electrical power and air conditioning; evacuating personnel and records; and other actions as required in fire emergencies, bomb threats, and natural…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .