NCSX Interface Control Management Plan and Implementing Procedure 003

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

2. 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. ICMP & Procedure 003

3. 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 ICMP & Procedure 003

4. 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 ICMP & Procedure 003

5. 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. ICMP & Procedure 003

6. 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 theproposed 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 ICMP & Procedure 003

7. Scope Sheet ICMP & Procedure 003

8. ICD Identification Scheme ICMP & Procedure 003

9. ICD Title & Approval Page ICMP & Procedure 003

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

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

12. ICD Tracking Log ICMP & Procedure 003

13. 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) ICMP & Procedure 003