Statement of Work Requirements: for Contracts That Require Operations And/Or Maintenance

OMB Approval No. 2700-0042 AMENDMENT OF SOLICITATION/ 1. CONTRACT ID CODE PAGE OF PAGES MODIFICATION OF CONTRACT NAS 9-98100 1 16 2. AMENDMENT/MODIFICATION NO. 3. EFFECTIVE DATE 4. REQUISITION/PURCHASE REQ. NO. 5. PROJECT NO. (If applicable) Modification 38 See Block 16C N/A N/A 6. ISSUED BY CODE 7. ADMINISTERED BY (If other than Item 6) CODE NASA LYNDON B. JOHNSON SPACE CENTER Attn: Lawrence A. Kenyon, PCO, Mail Code: BN 2101 NASA Road One Houston, TX 770588. NAME AND ADDRESS OF CONTRACTOR (No., street, county, State, and ZIP Code)LOCKHEED-MARTIN SPACE OPERATIONS COMPANY Attn: David F. Bruce, Manager of Contracts 501 Gemini Avenue Houston, TX 77058 CODE FACILITY CODE (x) 9A. AMENDMENT OF SOLICITATION NO. 9B. DATED (SEE ITEM 11)10A. MODIFICATION OF CONTRACT/ORDER NO. 10B. DATED (SEE ITEM 13) X NAS 9-98100 Originally dated: 10/01/98 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. 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 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offor submitted; or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGEMENT 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 telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified. 12. ACCOUNTING AND APPROPRIATION DATA (If required)13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS, IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.(x) (x) A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT ORDER NO. IN ITEM 10A. B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, 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: X FAR 52.243-2 Alt. II (Apr 84) Changes & FAR 52.232-22, LOF, H.5, Special Provision for Contract Changes d. OTHER (Specify type of modification and authority)X E. IMPORTANT: Contractor is not, X Is required to sign this document and return 3 copies to the issuing office.14. description of amendment/modification (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)Pursuant to clause H.5, Special Provision for Contract Changes, this action is less than $1.0 million and therefore does not give rise to an equitable adjustment to contract NAS 9-98100 in cost or fee. The purpose of this modification 38 is to authorize mission and data services in support of the OSP/JAWSAT mission per the attached Project Service Level Agreement. The estimated value of this work is $45,000. This modification represents full and equitable adjustment for the subject work. 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. 15A. NAME AND TITLE OF SIGNER (Type or print) 16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print) David F. Bruce, Contracts Manager Michelle Isermann, Contracting Officer 15B. CONTRACTOR/OFFEROR 15C. DATE SIGNED 16B. UNITED STATES OF AMERICA 16C. DATE SIGNED Original signed by David F. Bruce 10/18/99 BY Original signed by Michelle Isermann 10/19/99 (Signature of person authorized to sign) (Signature of Contracting Officer) NSN 7540-01-152-8070 30-105 STANDARD FORM 30 (Rev. 10-83) PREVIOUS EDITION UNUSABLE JSC MS Word (Aug 95) Prescribed by GSA FAR (48 CFR) 53.243 NATIONAL AERONAUTICS AND SPACE ADMINISTRATIONSPACE OPERATIONS MANAGEMENT OFFICEPROJECT SERVICE LEVEL AGREEMENTTO: Space Operations Management OfficeVIA: SOMO Mission Service Manager Code S720 Goddard Space Flight Center Greenbelt MD 20771FROM: Space & Missile Systems Center, Small Launch Vehicle Division SMC/TEBL 3550 Aberdeen Avenue SE, Kirtland AFB, NM 87117-5776Lt. Luis Marina, OSP-SLV(Minotaur)/JAWSAT Mission Manager (505) 846-5659, [email protected]Author/Point of Same Contact (if different from above)CMSM: Richard Harris, GSFC Code 450, (301) 286-5974, [email protected]SUBMISSION DATE: MISSION TITLE: OSP/SLV Support (Joint Air Force Academy AUGUST, 1999 Weber State Satellite (JAWSAT) Mission)VERSION:  Initial  Change Number______2 Form Rev 1/19/1999TABLE OF CONTENTSSection I CUSTOMER INFORMATION Section II CUSTOMER REQUIREMENTS AND STANDARD SERVICES A. Mission Services1. Mission Planning 2. Mission Control 3. Flight Dynamics 4. Spacecraft Analysis 5. Payload Analysis 6. Science Data Processing 7. Data StorageB. Data Services1. Ground Network 2. Space Network 3. Deep Space 4. Data Distribution 5. Special Network Management Services 6. Supporting Services B. Center Unique Services1. GSFC Unique Services 2. JSC Unique Services 3. KSC Unique ServicesSection III CUSTOMER REQUIREMENTS AND NON-STANDARD SERVICESA. Non-CSOC SOMO ServicesB. Non-NASA ServicesC. PCD RequirementsSection IV Service Price, Metrics and Schedule SummarySection V Agreement Signatories3 Project Service Level AgreementSection I Customer InformationMission Title: OSP/SLV Support (Joint Air Force Academy Weber State Satellite (JAWSAT) Mission)Category/Sponsor:  NASA  U.S. Commercial  NASA Cooperative  Foreign Commercial  Non-NASA Government  Foreign Government  DOD  Other (If Other, Describe]Mission Objectives: To demonstrate the capability of the OSP Space Launch Vehicle by placing working satellites into functional orbitsTo baseline the vehicle characteristics in support of using OSP Space Launch Vehicle vehicles to support launch services for small U.S. Government satellitesTo prove the viability of the both the JAWSAT Multi-payload Adapter and the AFRL Soft Ride SystemLaunch/Flight  Space Shuttle LV  Aircraft  RLV Information:  Expendable LV  Other Specify: Vehicle – Orbital/Suborbital Program Space Launch Vehicle (OSP SLV) – “Minotaur” Upper Stage: N/A Launch/Operations Site: Western Range, Spaceport Systems International Commercial Launch Facility Trajectory Regime Description: The satellite will be placed into a 100.0 degree inclined sun synchronous orbit of 750 km altitude Launch/Flight Date(s): 04 Oct 99Orbit/Flight Path  Aeroflight  High-Earth Orbit Data::  Suborbital  Deep Space  Low-Earth Orbit  OtherORBITAL PARAMETERS AS APPLICABLE: SPECIFYApogee: 750 km Perigee: 750 km Inclination: 100.0 degrees4／6／2018 4 Project Service Level AgreementOther Trajectory Information: Circular Orbit ______Key Mission Events and Dates:Approved Mission Start Date: Sept, 1997 Phase C/D Start Date: Sept, 1997 Present Phase of Development: Implementation, proceeding into operations Requirements Maturity Assessment:  >80%  >50%  <50% Funding Approval Status: ApprovedMission Duration: (mo/yr) Prime: 10/00 Extended: n/aProgram Duration (mo/yr) - (mo/yr): 10/99-10/00Other: Not applicable4／6／2018 5 Project Service Level AgreementSection II Customer Requirements and Standard ServicesA. Mission Service 1. Mission Planning – 1.a. Customer RequirementsThis mission requires support for only one pass of the OSP SLV fourth stage after completing the separation sequence. Launch date and time, as well as pre-mission testing and launch rehearsals, will be coordinated with NASA.1.b. Catalog Services2. Mission Control – No Requirements 2.a. Customer Requirements 2.b. Catalog Services3. Flight Dynamics – No Requirements 3.a. Customer Requirements 3.b. Catalog Services4. Spacecraft Analysis - No Requirements 4.a. Customer Requirements 4.b. Catalog Services5. Payload Analysis - No Requirements 5.a. Customer Requirements 5.b. Catalog Services6. Science Data Processing - No Requirements 6.a. Customer Requirements 6.b. Catalog Services7. Data Storage 7.a. Customer RequirementsThe received telemetry recorded at the McMurdo Ground Station will be stored at NASA/WFF for a period of six months. NASA/WFF will provide a magnetic copy of the recorded data to START Treaty Offices at VAFB as soon as possible following mission completion. Data is to be IRIG Group 2 provided on 14 track using reels no greater than 14 inches in diameter. Recorder bandwidth should be 2.0 MHz at 120 ips.7.b. Catalog Services4／6／2018 6 Project Service Level Agreement4／6／2018 7 Project Service Level AgreementB. Data Services 1. Ground Network 1.a. Customer Requirements 1.b. Catalog Services 1.b.1. GN Data Acquisition, Formatting and Transfer1.b.2. GN Command Handling and Transmission1.b.3. GN Tracking Data Generation1.b.4. GN Scheduling1.b.5. GN Real-Time Control and performance Data Monitoring1.b.6. GN Testing1.b.7. Summary DataThe following tabular information is a summary of the ground network services requirements: i. Low Earth Orbit/Launch Data Services - SPEC/Sub-Orbital - Ground NetworkBasic Description of Support Required: [Including duration/passes per day]MGS will acquire, receive, retransmit, and record OSP SLV store-and-forward S-band telemetry during overflight of the MGS facility. The telemetry stream consists of onboard vehicle data that has been stored at various intervals and sampling rates between a few seconds prior to LOS from Vandenberg Air Force Base to 10 seconds after payload separation.McMurdo AOS is approximately 30 minutes after liftoff and overflight duration is approximately 15 minutes.There are no commanding requirements.The received data will need to available on an FTP site for recovery by Orbital via the Internet. The telemetry recorded on the FTP site will contain two raw telemetry files:(1) From MGS AOS to AOS+5 minutes (2) From MGS AOS to LOSStations Required: Mila, FL  Ponce de  Alaska Other4／6／2018 8 Project Service Level AgreementLeon, FL SAR ______Facility __  McMurdo,  Svalbard,  Mobile Antarctica Norway (LEO-T)[Station includes all antenna resources located at a site.] Standard Telemetry Requirements  No. Of Links: 1 [If Non-standard, Explain Below] Frequency Bandwidth Modulation Coding Subcarrier Data Type Format 2288.5 MHz 0.504 MHz PCM/FM RNRZ-L Engineering 1.44 Mbps (@ 3 dB)Standard Command Requirements  No. Of Links: 0 [If Non-standard, Explain Below] Frequency Bandwidth Modulation Subcarrier EIRP FormatStandard Metrics Requirements  Radar:  [If Non-standard, Explain Below] Ranging Doppler Angle Optical Special Data HandlingSpecial Data Links, Radio Metrics, or Optical Metrics, Destruct, Voice Communication:[Explain Below]Special Communications Links to Other Facilities ; Special Data Handling: 1. Voice communication day of launch with MGS, GSFC, WFF and VAFB. 2. Forward OSP SLV downlinked data to FTP siteOther Special Requirements: Radar [No] Beacon/Skin [No]_ No. Of Radars ______Data Communication Requirements: Pre-mission Support [P/L Checkout/Simulations/Compatibility] - Two (2) Search and Acquisition tests, using a test vehicle such as COBE (or until successful acquisitions can be demonstrated), at approximately L-45 days. Each test involves ½ hour pre-pass and 15 minutes for the actual support (45 minutes total). No TLM data will be relayed or recorded for the Search and Acquisition Testing. The antenna AZ and EL data will be recorded at MGS and E-mailed to SMC/TEBL after each test. - Launch Rehearsal, approximately L-30 days (include L-1 dataflow)4／6／2018 9 Project Service Level Agreement- Mission Dress Rehearsal, L-2 days (include L-1 dataflow)Type, location, and duration of support:MGS will receive, retransmit, and record OSP SLV store-and-forward S-band telemetry during overflight of the MGS facility. This pass is approximately 15 minutes in duration. Telemetry will be transmitted when the Launch Vehicle is approximately 6 deg in elevation from the MGS and continue for 5 minutes.The duration that services will be required from NASA on day of launch is a one-time span of approximately 5 hours. Three (3) hrs. before nominal liftoff and two (2) hrs. after nominal liftoff. The downlinked data stream is composed of only data. Additional periods of support on subsequent days may be required in the case of launch scrubs and recycle. Special Data Handling Requirements: NoneSecurity Requirements: NoneCommand Guidance/Destruct Requirements: NoneRadio Communication Requirements: NoneControl Center Requirements: NoneReal Time Data Display Requirements: NoneMeteorological Requirements: NoneOptical Support Requirements: None ii. Low Earth Orbit/Launch Data Services - SPEC/Sub-Orbital - GSFCBasic Description of Support Required: [Including duration/passes per day]None4／6／2018 10 Project Service Level Agreement iii. Low Earth Orbit/Launch Data Services - SPEC/Sub-Orbital - DrydenDescription of Support Requirements: None2. Space Network – No Requirements3. Deep Space Network – No Requirements4／6／2018 11 Project Service Level Agreement4. Data Distribution 4.a. Customer Requirements a. Data Distribution Services Received data will be available on an FTP site for recovery by Orbital via the Internet.Data Transport Facility Requirements: Brief Data Transport Network Description:Terminal Locations: VAFB, GSFC, MGSNISN Requirements:  VOICE  DATA ? VIDEO ? MiscellaneousHighest Data Rate: 1.44 MbpsOther Distribution Services:4.b. Catalog Services5. Special Network Management Services 5.a. Customer Requirements 5.b. Catalog Services6. Supporting Services 6.a. Customer Requirements 6.b. Catalog Services 6.b.1. spectrum licensing 6.b.2. systems engineering 6.b.3. end-to-end testing and mission readiness testing 6.b.4. simulators 6.b.5. service management {planning, scheduling, controlling, …} 6.b.6. other4／6／2018 12 Project Service Level AgreementA. Center Unique Services1. GSFC Unique Services 1.a. Customer Requirements 1.b. Catalog Services2. JSC Unique Services 2.a. Customer Requirements 2.b. Catalog Services3. KSC Unique Services 3.a Customer Requirements 3.b. Catalog ServicesSection III CUSTOMER REQUIREMENTS AND NON-STANDARD SERVICESA. Non-CSOC SOMO ServicesB. Non-NASA ServicesC. PCD Requirements4／6／2018 13 Project Service Level AgreementSection IV Service Price, Metrics and Schedule Summary4／6／2018 14 Project Service Level AgreementSection V Agreement SignatoriesMission Title: OSP/SLV Support (Joint Air Force Academy Weber State Satellite (JAWSAT) Mission)Approved by:CMSM Richard N. Harris SOMO/GSFCCustomer Lt Luis Marina OSP SLV/JAWSAT Mission Manager USAF SMC/TEBL4／6／2018 15

Statement of Work Requirements: for Contracts That Require Operations And/Or Maintenance

Details

Download

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

Support