Project Interface Requirements Process including Shuttle Lessons Learned AIAA Techn IcAl Sy mp oSIum 2010 Garland T. Bauch, Ph. D. NASA-Johnson Space Center April 30, 2010 4/15/2010 1 https://ntrs.nasa.gov/search.jsp?R=20100015497 2018-08-03T02:33:14+00:00Z
30
Embed
Project Interface Requirements Process including Shuttle ... · Project Interface Requirements Process including Shuttle Lessons ... Interface Control Documents (ICDs) ... Space Shuttle
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Most failures occur at interfaces between organizations and hardware.Processing interface requirements at the start of a project life cycle will reduce thelikelihood of costly interface changes/failures later. This can be done by addingInterface Control Documents (ICDs) to the Project top level drawing tree, providingtechnical direction to the Projects for interface requirements, and by funding theinterface requirements function directly from the Project Manager's office. Theinterface requirements function within the Project Systems Engineering andIntegration (SE&I) Office would work in-line with the project element designengineers early in the life cycle to enhance communications and negotiatetechnical issues between the elements. This function would work as the technicalarm of the Project Manager to help ensure that the Project cost, schedule, and riskobjectives can be met during the Life Cycle. Some ICD Lessons Learned during theSpace Shuttle Program (SSP) Life Cycle will include the use of hardware interfacephotos in the ICD, progressive life cycle design certification by analysis, test, &operations experience, assigning interface design engineers to Element Interface(EI) and Project technical panels, and linking interface design drawings with projectbuild drawings.
4/15/2010 2
Synopsis
• This presentation will provide you withspecific "lessons learned" approaches toensure Interface Requirements lead the way incommunicating Project element requirementsacross the interfaces.
4/15/2010 3
Space Shuttle Program ICDs Began asSpecifications
MISSIONPROGRAM FLIGHT KIT^DEVEL^O MEN ^ SPECIFICATIONSP,ECIF.ICATiION
Volume IV - Book 1 3-5CHANGE NO. 213Revision L
4/15/2010 4
Specification Definition
• Statement of particulars such as performance,characteristics, requirements, andconfiguration for a given element ofhardware/software.
4/15/2010 5
Verification
• Process used to verify that the specificationshave been met
• Occurs during development , test, andevaluation phases
4/15/2010 6
Certification
• Approval of the verification results bymanagement
4/15/2010 7
Interface Control Document/Interface Revision Notice Definition
• Drawings/Documentation that record thecommon design features between two ormore interfacing designs.
• Standard IRN form used to record changes toan approved ICD
4/15/2010 8
Program ICDs Used To ControlInterfaces Between Elements
• Shuttle System/Vertical Assembly Building
• Shuttle System/Launch Pad
• Flight Vehicle/LPS Computational Systems
• Space Shuttle/KSC RF Comm & Tracking C/O
• JSC/USAF Space Shuttle SCF RF Comm & Track
• Shuttle/GSFC Space Shuttle RF Comm & Track
• Shuttle Vehicle/Ground Range Safety System
• Shuttle Vehicle Mold Lines and Protuberances4/15/2010 9
Program ICDs Used To ControlInterfaces Between Elements
• Orbiter/KSC Landing Station
• Orbiter Processing Facility/Orbiter Main & C/O
• Orbiter/Hypergolic Station
• Orbiter Landing/Safing & Deservicing Stations
• Orbiter & Carrier Aircraft/Mate-Demate I/F
• Orbiter Vehicle/External Tank
• Orbiter Vehicle/Solid Rocket Booster
• Orbiter Vehicle/Carrier Aircraft4/15/2010 10
0
Program ICDs Used To ControlInterfaces Between Elements
• Eventually, Technical Direction was given toIntegration in the contract
4/15/2010 26
Audit Process Periodically
• Use Product Development Plan to auditprocess
• Send questions to contractor
• Face to face meeting on-site best
• Obtain answers from contractors
• Issue NASA findings
• Track the implementation change
4/15/2010
27
Reduce Change Authority DuplicationWhere Process Integrity Remains
• SICB controls ICDs• SPRCB controls OMRSDs• Waivers come in on OMRSDs that also affect ICDs• Rationale is heard at SPRCB• Waiver is approved at SPRCB• IRN/ICD can be OSB based on previous authority• Can also simply establish a log of documentation
only waivers approved by IWG chair as delegatedby the SICB Chair.
4/15/2010 28
Add Interface Photos to ICDs
Orbiter/ET Forward Attachment
4/15/2010 29
Conclusions
• Excellent Design Engineering and InterfaceControl is needed early in the Program lifecycle to minimize costs and hazards.
• Program SE&I Integration Design Engineersshould work as a team with the ProjectSystems Engineers starting early in theProgram Life Cycle –design, development,test, verification, production, and operations.