Lyndon B. Johnson Space Center ISS Payload Label Approval Process Habitability & Human Factors (SF3 ) Rich Ellenberger (281-483-5238)5/19/2015 ISS Payload.

Slides:



Advertisements
Similar presentations
ASTM OFFICERS CONFERENCE SUBCOMMITTEE CHAIRMENS DUTIES AND RESPONSIBILITIES.
Advertisements

Configuration Management
More CMM Part Two : Details.
ITIL: Service Transition
 Every stage from phase DESIGN in Software Development Process will have “design document” especially in analysis and design phases.  “Design document”
Project Close Out CTC-470.
DITSCAP Phase 2 - Verification Pramod Jampala Christopher Swenson.
UNDERSTANDING, PLANNING AND PREPARING FOR THE SCHOOL-WIDE EVALUATION TOOL (SET)
ISO 9000 Certification ISO 9001 and ISO
The Project AH Computing. Functional Requirements  What the product must do!  Examples attractive welcome screen all options available as clickable.
Release & Deployment ITIL Version 3
SYSTEM ANALYSIS AND DESIGN
3 Dec 2003Market Operations Standing Committee1 Market Rule and Change Management Consultation Process John MacKenzie / Darren Finkbeiner / Ella Kokotsis,
University of Palestine software engineering department Testing of Software Systems Fundamentals of testing instructor: Tasneem Darwish.
Degree and Graduation Seminar Project Management Processes
Accessibility Resources: An Introduction to the Memo Professor and student sitting and talking.
S/W Project Management
The Key Process Areas for Level 2: Repeatable Ralph Covington David Wang.
CHAPTER 5 Infrastructure Components PART I. 2 ESGD5125 SEM II 2009/2010 Dr. Samy Abu Naser 2 Learning Objectives: To discuss: The need for SQA procedures.
Copyright Course Technology 1999
Introduction to Software Quality Assurance (SQA)
Commissioning of Fire Protection and Life Safety Systems Presented by: Charles Kilfoil Bechtel National Waste Treatment Plant Richland WA.
Software Configuration Management
Software Quality Assurance Activities
From Research Prototype to Production
Serious Accident Investigation REPORTS. Lesson 12 Objectives Use a template to correctly fill out a 24-Hour Preliminary Report and list all the steps.
Lecture #9 Project Quality Management Quality Processes- Quality Assurance and Quality Control Ghazala Amin.
Project Management Methodology Project Closing. Project closing stage Must be performed for all projects, successfully completed or shut off by management.
Configuration Management Matti Kuikka CONFIGURATION MANAGEMENT by Matti Kuikka, Unit Manager, Ericsson, Turku, Telecom R&D, Wireless Charging.
ISO 9001: 2000 Certified Audit Process What to do.
TRANSPORTATION FEFP PREPARING FOR THE “DREADED” OFFICIAL STATE AUDIT.
SENG521 (Fall SENG 521 Software Reliability & Testing Software Product & process Improvement using ISO (Part 3d) Department.
1.  Describe an overall framework for project integration management ◦ RelatIion to the other project management knowledge areas and the project life.
MD Digital Government Summit, June 26, Maryland Project Management Oversight & System Development Life Cycle (SDLC) Robert Krauss MD Digital Government.
Software Quality Assurance
Software Development Cycle What is Software? Instructions (computer programs) that when executed provide desired function and performance Data structures.
Contract Training Class I
Systems Analysis and Design
© Mahindra Satyam 2009 Configuration Management QMS Training.
ISO 9001 – an overview Tor Stålhane IDI / NTNU. ISO 9001 and software development ISO 9001 is a general standard – equally applicable to software development.
Project quality management. Introduction Project quality management includes the process required to ensure that the project satisfies the needs for which.
Software Configuration Management (SCM). Product Developer Disciplines One view of the world is that there are three types of activities are required.
Quick Recap Monitoring and Controlling. Lesson 11: Monitoring and Controlling Project Work Topic 11A: Identify the Monitor and Control Project Work Process.
Project management Topic 1 Project management principles.
Project management Topic 7 Controls. What is a control? Decision making activities – Planning – Monitor progress – Compare achievement with plan – Detect.
Integrated Change Control 1 MEC-8. Processing of a Change Processing of a Change 2 Assess Impact within KA Change Request Implemented Change Create a.
Software Configuration Management (SCM) Source: Pressman, R., Software Engineering: A Practitioner ’ s Approach. Boston: McGraw Hill, Inc., 2005; Ghezzi,
CABLING SYSTEM WARRANTY REGISTRATION. PURPOSE OF CABLING REGISTRATION.
Doc.: IEEE /xxxxr0 Submission July 2007 Terry Cole, AMDSlide Common Editorial Comment Resolution Process Date: Authors:
Quality Assurance for LHC Gas Systems Stefan Haider / EP-TA1.
IPLFOR POIF Process Review Eric Melkerson Payload Operations Director Operations Directors’ Office / EO03 Marshall Space Flight Center
BSBPMG501A Manage Project Integrative Processes Manage Project Integrative Processes Project Integration Processes – Part 2 Diploma of Project Management.
Crew Operations Team Alexia R. Matthews Cold Stowage CPE (256)
July 26, 2005 Nelda Allen/Colsa1 Configuration Management Process 2 Minor Changes (pages 2 & 5)
CACI Proprietary Information | Date 1 PD² v4.2 Increment 2 SR13 and FPDS Engine v3.5 Database Upgrade Name: Semarria Rosemond Title: Systems Analyst, Lead.
USDA 2016 Financial Management Training Transforming Shared Services Change Management Presented by Ron Gros.
Page No. 1 ISS_CM_019 (Rev 09/2011) Pre-decisional, For Internal Use Only Introduction to the Human Factors Implementation Team (HFIT) Process for Payload.
National Aeronautics and Space Administration (NASA) Glenn Research Center SAMS KU Forward Lessons Learned 1 Kevin McPherson NASA GRC Payload Operation.
Planning meetingCertification audit, stage 1 Pre-audit (optional) Document review Prior to every certification audit a planning meeting is conducted where.
Payload Inventory Management & Stowage Operations Processes 10/19/99 Point of Contact Gordon Boswell MSFC/POIF/OI (256)
Introduction for the Implementation of Software Configuration Management I thought I knew it all !
ITIL: Service Transition
Software Project Configuration Management
Workplace Projects.
Software Configuration Management
PREPARATION FOR GMP INSPECTION
GMP Inspection Process
TECHNOLOGY ASSESSMENT
Software Reviews.
What is a System? A system is a collection of interrelated components that work together to perform a specific task.
Presentation transcript:

Lyndon B. Johnson Space Center ISS Payload Label Approval Process Habitability & Human Factors (SF3 ) Rich Ellenberger ( )5/19/2015 ISS Payload Label Approval Process

Lyndon B. Johnson Space Center ISS Payload Label Approval Process Habitability & Human Factors (SF3 ) Rich Ellenberger ( )5/19/2015 Charter: The ISS Payload Label Approval Team (IPLAT) is responsible for verifying that ISS payload labels meet the requirements in SSP Appendix C. The goal is the standardization of payload labels to facilitate the crew’s understanding, thereby increasing the amount of time spent on science.

Lyndon B. Johnson Space Center ISS Payload Label Approval Process Habitability & Human Factors (SF3 ) Rich Ellenberger ( )5/19/2015 Scope Of Work (Which Labels IPLAT Must Review). IPLAT must review all labels on payload hardware/equipment that the crew will interface with (nominal operations, planned maintenance, contingency). –This includes, but is not limited to: Rack/subrack front panel type hardware All experiment equipment, loose or mounted other than in rack/subrack formation All equipment cables, fluid lines, hoses, etc. All equipment controls, switches, ports, LEDs, containers, etc –This does not include: Items which the crew will not interface with (e.g. internal circuit boards, etc.) Labels contained within software displays. These are handled by the Payload Display Review Panel (PDRP). Procedures, Cue Cards, etc. These are handles by the Payload Operations Data File (PODF).

Lyndon B. Johnson Space Center ISS Payload Label Approval Process Habitability & Human Factors (SF3 ) Rich Ellenberger ( )5/19/2015 Early Coordination –IPLAT provides payload developer with information about the label approval process and answers questions regarding requirements. –Payload developer provides IPLAT with basic information about the payload. Initial Label Evaluations (see diagram) –Payload developer requests an initial label evaluation as early as possible, and provides IPLAT with pre-released engineering drawings. Note: IPLAT suggests developers request the initial label evaluation before engineering drawings are officially released, because the cost to make final changes after release will be greater. –IPLAT performs the initial label evaluation on the pre-released drawings. –Developer adjusts label designs per IPLAT’s recommendations, or develops additional or alternate solutions to requirements violations. –The bulk of label design corrections should be done at this stage, as the cost of changes should be minimal.

Lyndon B. Johnson Space Center ISS Payload Label Approval Process Habitability & Human Factors (SF3 ) Rich Ellenberger ( )5/19/2015 Final Acceptance/Disposition of Payload Labels (see diagram) –Once the payload’s design matures to the point where the developer has released engineering drawings and desires final acceptance of the label designs, the developer will contact IPLAT to request the final evaluation. –Developer supplies IPLAT with formal released engineering drawings. –IPLAT reviews released drawings to ensure IPLAT’s previous recommendations were implemented and checks any additional changes made to the labels. The developer should inform IPLAT of such changes prior to the review. The Final Disposition Form (JSC Form 732) is the formal record of whether or not the labels are approved. –If the released drawings contain no label requirements violations, Form 732 will be returned listing the drawings that were approved. –If the released drawings contain label requirements violations, Form 732 will be returned citing the drawings that are disapproved.

Lyndon B. Johnson Space Center ISS Payload Label Approval Process Habitability & Human Factors (SF3 ) Rich Ellenberger ( )5/19/2015 Final Acceptance/Disposition of Payload Labels (continued) –It is possible for some drawings to be approved, and some disapproved, on the same Form 732. –If there is a good reason the letter of a requirement can’t be met, IPLAT will make a determination as to whether or not the violation is serious enough to warrant disapproval. The developer and IPLAT will try to work toward a solution that is acceptable to both parties. –If there are any outstanding disagreements between IPLAT and the developer, the developer can appeal to the ISS Payload Office (OZ3) PIRN Technical Review (PTR) board for disposition.

Lyndon B. Johnson Space Center ISS Payload Label Approval Process Habitability & Human Factors (SF3 ) Rich Ellenberger ( )5/19/2015 Fairness Principle (for both PDs and IPLAT) –IPLAT has a “fairness principle” in its process. This means that, if a payload developer implements all of the recommendations from the initial label evaluation, IPLAT does not like to change the rules or recommendations for the final label evaluation. IPLAT wants just one opportunity to make label recommendations. Logical exceptions to this would be for cases where a safety issue exists. Also, this principle applies only to hardware IPLAT has actually reviewed and already given recommendations for. New hardware is treated as an initial label evaluation. –The other side of this principle is that it is not acceptable for a payload developer to come for an initial label evaluation saying the drawings and hardware are baselined and not open to comment. IPLAT needs one opportunity to make label recommendations.

Lyndon B. Johnson Space Center ISS Payload Label Approval Process Habitability & Human Factors (SF3 ) Rich Ellenberger ( )5/19/2015 Labels Meet Rqmts? Yes No PTR Board PD to correct labels? Yes No PD = Payload Developer IPLAT = ISS Payload Label Approval Team PTR = PIRN Technical Review (PTR) Board PD Corrects Label Design IPLAT Performs Initial Label Evaluation 1 1 Completed within 10 working days 2 To support h/w and sim development, prelim proc delivery. 3 Supports preparation for bench reviews. 4 Only if IPLAT and PD disagree on resolution 1st Stage: Initial Review 2 PD provides Pre-released Engineering Drawings START 2nd Stage: Final Acceptance Review 3 PD provides Released Engineering Drawings Return JSC Form 732 Approved IPLAT Re-evaluates Engineering Drawings for  ’s 1 Return JSC Form 732 Disapproved STOP 3rd Stage: PTR Board 4 PD requests waiver PTR Grant Waiver? Yes PD Corrects Label Design No Payload’s OpNom is baselined Prelim OpNom for Prod dev

Lyndon B. Johnson Space Center ISS Payload Label Approval Process Habitability & Human Factors (SF3 ) Rich Ellenberger ( )5/19/2015 IPLAT Initial or Final Label Evaluation Internal Process Primary Evaluator evaluates labels, documents non-compliances & suggested solutions in Requirements Checklist (initial eval) or draft Form 732 (final eval). Meeting with Secondary Evaluators Discuss issues, evaluate labels, provide comments Note: This process is to take up to 10 working days, maximum. Knowledge Database (consisting of drawings, images, etc., from previous evaluations) consulted to ensure consistency with previous reviews. Primary Evaluator finalizes Requirements Checklist or Form 732. IPLAT lead reviews it. Primary Evaluator assigned Requirements Checklist or Form 732 provided to PD Consult with Crew Office for their comments/concurrence. Get their opinion when there are several options to meeting the requirements.

Lyndon B. Johnson Space Center ISS Payload Label Approval Process Habitability & Human Factors (SF3 ) Rich Ellenberger ( )5/19/2015 Payload Developer Vs. IPLAT Responsibilities –Payload Developer Responsibilities: It is the payload developer’s responsibility to ensure that it provides IPLAT with all of the drawings containing labels that the crew will interface with. The 10 day approval cycle begins when all of the drawings for a system/subsystem are received. The developer is responsible for collecting all IPLAT Final Disposition Forms to attach to a Verification Data Sheet (VDS) as proof that SSP Section has been satisfied. This is the requirement that specifies that IPLAT shall verify the payload’s labels. The developer is also responsible for notifying IPLAT if label designs change, and for providing updated drawings to IPLAT to review. –IPLAT responsibilities: IPLAT is responsible for reviewing drawings it receives against the SSP Appendix C labeling requirements, and for providing formal verification on such drawings. This is the only role IPLAT plays in formal verification. IPLAT will maintain a record of which drawings were reviewed and approved or disapproved (Final Disposition Forms). The developer can ask IPLAT if it received and reviewed certain drawings, to aid the developer in determining whether all drawings containing labels have been properly reviewed and approved.

Lyndon B. Johnson Space Center ISS Payload Label Approval Process Habitability & Human Factors (SF3 ) Rich Ellenberger ( )5/19/2015 OpNom Plan –For U.S. ISS Payloads, Operations Nomenclature (OpNom) includes all acronyms and abbreviations, and text on IMS labels. The PD is responsible for coordinating their OpNom with the PODF. Contact Mercedes Galloway at , –For International Partners (IPs), contact your ODCFB component control board representative for OpNom registration. If there are any questions, contact Kent Adams at , –Operations Nomenclature must be baselined final IPLAT approval. IMS Plan –IPLAT will instruct payload developers to contact OC2 (Jennifer Jenkins, , directly for IMS label requests/questions. IPLAT is not responsible for IMS (assigning numbers, etc.). However, IPLAT will ensure that the IMS labels are placed in their proper locations, according to SSP Appendix

Lyndon B. Johnson Space Center ISS Payload Label Approval Process Habitability & Human Factors (SF3 ) Rich Ellenberger ( )5/19/2015 Related Interfacing Organizations (for U.S. payloads only). –Payload Operations Data File (PODF). The PODF is responsible for payload OpNom, procedures, and related materials (e.g. Cue Cards). IPLAT is a mandatory evaluator of OpNom and shares information with the PODF. –Payload Display Review Team (PDRT). The PDRT is responsible for approving all payload software displays. IPLAT will work with the PDRT to discuss any issues where hardware labels (IPLAT jurisdiction) and software displays (PDRT jurisdiction) interface.