Statement of work overview

well as revisions and change notices to the Common Hardware Specifications to each of the locations identified. Traceability from the common component Hardware and Software shall be completed to the Node 2 PIDS (SSP50290) by NASA as Government Furnished Data (GFD)

I&O b. TIMs to assist NASA/Alenia in understanding and integrating the PG-3 developed component hardware.

I&O b. The Contractor shall support Interface Control Working Group (ICWG) meetings to finalize the PIRNs with the affected parties.

1. 
   identification of those Node 2 Prime Item development Specification (PIDS) requirements that are allocated to the Node 2 CSCI’s,
   

2. 
   requirement analysis,
   

3. 
   analysis of test plans and procedures to ensure the tests verify compliance with PIDS requirements, and
   

4. 
   traceability analysis to verify every PIDS requirement has been tested.
   

I&O These tasks shall be accomplished by a review of the Node 2 PIDS, SSP 50290.

1. 
   Review plan/procedures,
   

2. 
   Provide on-site support for the testing,
   

3. 
   Support the Test Readiness Review - to be held in Torino, Italy,
   

4. 
   Develop and validate the Internal Element SIM to ensure the operability of the Internal System CSCI during the testing.
   

This storage shall be a controlled and bonded storage facility that meets all provisions required for flight hardware. The Common Component Hardware shall be DD250’s to NASA at the vendor location prior to shipment to the storage facility.

b. Adjusting knee brace settings.

c. Attaching/removing knee brace to a rack.

d. Attaching/removing the rack (lower attach points) to the MPLM.

5. 
   Provide support for drawings to resolve Government issues and
   

prior to delivery.

installation into the USL.

point for UF-2.

1. 
   CAS/Payload Interface Verification
   

OPD 1. The Contractor shall deliver a Passive Common Attach System Simulator (PCASS) in accordance with S684-11320, Non-Complex Item Development Specification for the PCASS.

DDT&E, I&O 1.16 YEAR 2000 COMPLIANCE

Spares, OPD
“Year 2000 compliant,” as used herein, means that the information technology (hardware, software and

firmware, including embedded systems or any other electro-mechanical or processor-based systems used in accordance with its associated documentation) accurately processes date and date-related data (including, but not limited to, calculating, comparing, and sequencing) from, into, and between the

twentieth and twenty-first centuries, and the years 1999 and 2000 and leap year calculations, to the extent that other information technology, used in combination with the information technology being acquired, properly exchanges date and date-related data with it.
Any information technology provided, operated and/or maintained under this contract must be Year 2000 compliant. To ensure this result, the Contractor shall provide Year 2000 documentation describing how the IT items or services demonstrate Year 2000 compliance, consisting of standard product literature or test reports for commercial items, and test procedures and test reports for integrated systems.
Milestones for Renovation, Validation and Implementation: Any IT determined to be non-Year 2000 compliant shall be replaced, retired, or repaired in accordance with the following schedule:

• 
  “Renovation” includes making and documenting software and hardware changes, developing replacement systems, and decommissioning systems to be retired. The Contractor must complete renovation of affected software, hardware and firmware by September 30, 1998.
  

• 
  “Validation” includes unit, integration, system, and end-to-end testing for Year 2000 compliance. The Contractor must complete validation and testing of converted or replaced systems by January 31, 1999.
  

• 
  “Implementation” includes acceptance testing and integration of converted and replaced systems into a production environment. The Contractor must complete implementation by March 31, 1999.
  

At a minimum, the Contractor shall provide documentation, including project plans and status reports, which demonstrate that the Contractor is meeting the milestones listed above.

1. 
   Develop a Draft Node 3 Specification that is compliant with the Type B1 specification guidelines in SSP 41171 based on the architecture developed for Node 3 and deliver in accordance with DR VE07 by April 9, 1998.
   

2. 
   Develop a Draft Type C specification for the ARS rack and deliver by April 9, 1998.
   

3. 
   Develop draft PIRNs (part 1 only) to the following ICDs: SSP 42007, SSP 42097, SSP 42003, SSP 42004, SSP 41143, SSP 41142, SSP 42137, and SSP 41140 in accordance with DR VE05 by April 9, 1998.
   

4. 
   Develop Draft ICDs (new) (part 1 only) for the following interfaces: ARS Rack to Node 3 (Standard ICD/IDD), and the preliminary draft of the Node 3 to Hab, ICDs in accordance with DR VE05 by April 9, 1998.
   

5. 
   Document the architecture that is developed for Node 3 in draft versions of the architecture notebooks.
   

6. 
   Develop 3 Draft Software Requirements Specifications for the two new CSCIs that are compliant with the Node 3 PIDS requirements and update the PMCUA SRS and deliver to NASA by June 5, 1998.
   

7. 
   Support NASA in the development of Bilateral documentation (BIVP, BDEA, BHSEALS only).
   

8. 
   Develop updates to SSP 30459 and D684-10015-01 to reflect responsibilities for revised/new ICD’s.
   

I&O b. The contractor shall support the Reference Configuration Review (RCR).

1. 
   Support NASA in the resolution of RCR issues with the RCR
   
2. 
   Provide technical support to NASA by traveling to the Node 3 RCR. This shall consist of the following areas of support as a minimum: Requirements, ICDs, Thermal, C&T, ECLS, Structures, C&DH (Huntsville) EVR, Microgravity, EPS.
   
3. 
   Document and provide a listing of all open RCR issues after completion of the RCR against the Node 3 Specification and element to element Part I ICDs. This is to be completed by 30 days after RCR.