1. NCSX Interface Control Management Plan and Implementing Procedure 003 Peer Review December 19, 2002

2. ICMP & Procedure 0032 Background An interface is a common boundary between activities or WBS elements Interface Control is the process of developing a technical agreement between two or more activities or WBS elements that documents the functional and physical characteristics required to exist at a common boundary As the design evolves, increasing more detailed interfaces will also evolve and be documented.

3. ICMP & Procedure 0033 Responsibility NCSX Engineering Manager responsible for the NCSX Interface Control and Management (ICM) Program Systems Engineering Support Manager responsible for implementation and administration of the ICM Program WBS Managers and Project Engineers responsible for identifying and agreeing on interfaces

4. ICMP & Procedure 0034 Definition of Interfaces Primary Interfaces Primary interface exists between two separately deliverable items when the mutual boundary is not controlled by a single developmental or “design to” specification ICMP controls and manages primary interfaces only Secondary interfaces Secondary interfaces can be defined by a single developmental or “design to” specification Methods for controlling secondary interfaces left to WBS managers

5. ICMP & Procedure 0035 Physical and Functional Interfaces and Design Studies Physical interface – defines the physical envelope and will eventually be reflected in an ICD Functional interface – defines performance requirements and will eventually be reflected in analyses and developmental or “design to” specifications Design studies – will probably not immediately impact interfaces, but should demonstrate that we have done enough “homework” to consider the potential impact on either physical or functional interfaces.

6. ICMP & Procedure 0036 ICM Process Scope sheet agreements are the precursors to ICDs or “design to” specifications Really only a planning document (can be in form of e-mail, excel spreadsheet, or work table) Defines the proposed interface in general terms, who is responsible for taking the lead, what WAF tasks these items are needed to support, and specific references to WAF tasks Needed early in the design process to organize effort ICDs and “Design to” specs are the deliverables for a PDR

7. ICMP & Procedure 0037 Scope Sheet

8. ICMP & Procedure 0038 ICD Identification Scheme

9. ICMP & Procedure 0039 ICD Title & Approval Page

10. ICMP & Procedure 00310 ICD Details Page (Sections 1 & 2)

11. ICMP & Procedure 00311 ICD Details Page (Sections 3 & 4)

12. ICMP & Procedure 00312 ICD Tracking Log

13. ICMP & Procedure 00313 Partial Resolution of Comments Question whether there is a need for a separate ICMP outside the CMP => ICMP is a subset of the CMP Question about the number of acronyms => NCSX Procedure 001 now captures all acronyms and terms Question about physical interfaces that could exist between two components not yet designed – envelope needs to be reserved => facility model will accomplish this Question about the capability to sort interfaces individually and by WBS => tracking log is an excel spreadsheet with the capability for multiple sorts Remainder of comments incorporated in current draft (dD)