Download
slide1 n.
Skip this Video
Loading SlideShow in 5 Seconds..
NASA TECHNICAL STANDARDS WORKING GROUP MEETING JUNE 11 – 12, 2007 COCOA BEACH, FL PowerPoint Presentation
Download Presentation
NASA TECHNICAL STANDARDS WORKING GROUP MEETING JUNE 11 – 12, 2007 COCOA BEACH, FL

NASA TECHNICAL STANDARDS WORKING GROUP MEETING JUNE 11 – 12, 2007 COCOA BEACH, FL

149 Vues Download Presentation
Télécharger la présentation

NASA TECHNICAL STANDARDS WORKING GROUP MEETING JUNE 11 – 12, 2007 COCOA BEACH, FL

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. NASA TECHNICAL STANDARDS WORKING GROUP MEETING JUNE 11 – 12, 2007 COCOA BEACH, FL

  2. Monday, June 11, 2007 8:30 – 8:45 Welcome/Agenda Gill/Matthews 8:45 – 9:30 Program Status Gill Key Points Relationship Between NASA Technical Fellows and the NASA Technical Standards Process NASA Technical Standards Development Status Results of EMB Action to Assess 42 Engineering Standards for Continued Development NASA Interim Technical Standards Proposals for Technical Standards Adoption vs. Use of Approved Applicable Document List Process for Cancellation of NASA Technical Standards Use of Revision Indicators on Applicable Documents in NASA Technical Standards Budget Update (Obs Cost, FY07) 9:30 – 10:15 NASA Lessons Learned Initiative KSC/Henderson 10:15 - 10:30 Break 10:30 – 11:00 Mandatory Engineering Standards HQ/West Implementation Status/Via Teleconference 11:00 – 12:00 Discussion on NASA Interim Directive Weinstein for NASA Mandatory Engineering Standards 12:00 – 12:30 Safety and Mission Assurance (S&MA) Harkins Standards Activities Mandatory Standards - Process for Mandatory Standards - Traceability of Use by Program and Projects 12:30 – 1:30 Lunch 1:30 – 2:15 Office of the NASA Chief Engineer Activities Weinstein Discussion on Revising the Technical Standards NPD/NPR Technical Authority Status Aerospace Safety Advisory Panel (ASAP) Report Actions TC20/SC14 Status; ECSS Monday, June 11, 2007 Continued…. 2:15 – 2:45 Chief Information Officer (CIO) Standards Activities Benedict Mandatory Standards - Process for Mandatory Standards - Traceability of Use by Program and Projects 2:45 – 3:00 Break 3:00 – 3:30 Consultative/Committee on Space Data Systems Kearney (CCSDS) Standards Activities 3:30 – 4:00 Agency-wide Part Management System USA/Zook 4:00 – 4:30 New Features in the NASA Technical Garcia/Johnston Standards System’s Document Search and Retrieval 4:30 – 5:00 NASA Engineering Network (NEN) / IHS/Davis Integrated Technical Standards System (ITSS) and Standards Reference Linking Solution 5:00 Adjourn Tuesday, June 12, 2007 8:00 – 8:30 Common NASA Taxonomy for Problem Reporting KSC/Beil Analysis, and Resolution Standard 8:30 – 9:00 NESC Technical Fellows Terrone 9:00 – 9:15 Break 9:15 – 9:45 Center Reports All Action Status Document Development Status (Quad Charts) for NASA Technical Standards and VCSs by Your Center Issues Technical Authority Implementation at Each Center 9:45 – 11:00 Wrap-up (Actions, Other Issues, Concerns) All 11:00 – 12:00 Lunch 12:00 KSC Tour AGENDA

  3. PROGRAM STATUS Paul Gill

  4. KEY POINTS FORDISCUSSION DURING THE MEETING • NPR: What revisions does the NPR require prior to pre-NODIS review? • NPR: Which organization is responsible for audits to ensure that Programs/Projects follow procedure? • What, as an Agency, should we standardize? • Revised Proposal Format to obtain clearer justification for NASA-Development vs. VCS development/use. • Proposal: How should the cost of a proposed project that crosses over multiple Centers be scoped? • Revised NASA Standards Development Process by obtaining “beginning” and “ending” consensus by EMB. • Discuss the timeframes for review of NASA Technical Standards; are they sufficient for timely responses: - 45 Working Days for Agency-wide Review (Note: “Doesn’t apply to my Center” is not acceptable.) - 4 to <8 Weeks for OPRD Comment Resolution • 3 Weeks to Obtain EMB Concurrence 8. If NASA can use a VCS by tailoring rather than developing a NASA Technical Standard: -How will this be documented? - What will the process be? • Use of Revision Indicators on Applicable Documents in NASA Technical Standards. • Chief Engineer’s Approval of NASA Engineering Standards and VCSs in Development. • NASA’s “Mandatory Engineering Standards” List. • Identify experts across the Agency to develop standards. • Use of “Preferred” Standards. • Each Center should establish a documented process for reviewing NASA Technical Standards to ensure adequate reviews that include programs/projects. • What is the Process for cancellation of NASA Technical Standards?

  5. PROCESS FOR DEVELOPING NASA TECHNICAL STANDARDS INITIATE DEVELOP REVIEW / REVISE APPROVE IMPLEMENT NASA Technical Standards Program Paul Gill, Manager May 4, 2007

  6. PROCESS FOR DEVELOPING NASA TECHNICAL STANDARDS(WITH NASA TECHNICAL FELLOW PARTICIPATION) NASA TECHNICAL STANDARDS PROGRAM (Center Reps – Engineering, and Projects) ENGINEERING MANAGEMENT BOARD (CENTERS AND MISSION DIRECTORATES) NASA TECHNICAL FELLOWS Solicit Inputs on Priority Issues Identify Priority Issues Prioritize Issues Annual Call for Proposals INITIATE Centers Submit Proposals “Tuning” Priorities, Expert Resources Center Weighted Evaluation Topic Working Group (TWG) Formed Concurrence with Proposed Projects DEVELOP TWG Develops Consensus Draft Consultant to TWG as Required Agency-wide Review of Draft By Center Experts/Programs; Comments Submitted Review Draft in Responsible Discipline Area REVISE/ REVIEW See Next Page See Next Page

  7. PROCESS FOR DEVELOPING NASA TECHNICAL STANDARDS(WITH NASA TECHNICAL FELLOW PARTICIPATION) (Continued) NASA TECHNICAL STANDARDS PROGRAM ENGINEERING MANAGEMENT BOARD (CENTERS AND MISSION DIRECTORATES) NASA TECHNICAL FELLOWS (AND COMMUNITIES OF PRACTICE) See Previous Page See Previous Page Agency-wide Review of Draft By Center Experts/Programs; Comments Submitted No Unresolved Issues? Resolve Issues? TWG Chair Dispositions Comments REVISE/ REVIEW Yes Yes Resolve Issues No Yes Resolution Matrix/ Final Draft Center Concurrence Technical Concurrence NASA Chief Engineer Approval APPROVE Publish in NASA Technical Standards System Guide/Advise/Resolve UseConflicts IMPLEMENT Implement Lessons Learned in Standards Trending/Lessons Learned Identification

  8. WHAT’S NEW IN APPROVED STANDARDS(As of 05/30/2007) Four NASA Technical Standards have been Approved This FY: Document No.TitleDate Approved • NASA-STD-I-7009 Standard for Models 12/01/2006 and Simulations (Interim) • NASA-STD-6002C Applying Data Matrix Identification 03/21/2007 Symbols on Aerospace Parts • NASA-STD-4005 LEO Spacecraft Charging 06/03/2007 Design Standard • NASA-HDBK-4006 LEO Spacecraft Charging 06/03/2007 Design Handbook

  9. SUMMARY OF STANDARDS IN DEVELOPMENT • 33 Documents in Various Stages of Development (Includes NASA-STD-3001, Vol. 2 and NASA-HDBK-6022) • 13 in Draft Preparation • 4 in Format/Edit by NTSP Office • 1 in OPRD Review Prior to Agency Review • 3 in Agency-wide review • 5 OPRD Resolving Comments from Agency-wide Review • 1 in Edit by NTSP Office Prior to EMB Concurrence • 1 in OPRD Review Prior to EMB Concurrence • 5 in EMB Concurrence • 9 VCSs in Development

  10. NASA STANDARDS IN DEVELOPMENT / REVISION STATUS

  11. NASA STANDARDS IN DEVELOPMENT / REVISION STATUS (Continued)

  12. NASA STANDARDS IN DEVELOPMENT / REVISION STATUS (Continued)

  13. NASA STANDARDS IN DEVELOPMENT / REVISION STATUS (Continued)

  14. NASA STANDARDS IN DEVELOPMENT / REVISION STATUS (Continued)

  15. NASA STANDARDS IN DEVELOPMENT / REVISION STATUS (Continued)

  16. NASA STANDARDS IN DEVELOPMENT / REVISION STATUS (Continued)

  17. NASA STANDARDS IN DEVELOPMENT / REVISION STATUS (Continued)

  18. NASA STANDARDS IN DEVELOPMENT / REVISION STATUS (Continued)

  19. NASA STANDARDS IN DEVELOPMENT / REVISION STATUS(Continued)

  20. VCSs IN DEVELOPMENT STATUS (Continued) (/c — with comments)

  21. VCSs IN DEVELOPMENT STATUS (/c — with comments)

  22. NASA INTERIM STANDARDS CONVERSION STATUS

  23. NASA INTERIM STANDARDS CONVERSION STATUS

  24. NASA INTERIM STANDARDS CONVERSION STATUS

  25. TECHNICAL STANDARDSREQUIRINGFOR REVALIDATION, REVISION, OR CANCELLATION (4) Per NPD 8070.6B: Review each NASA-developed Technical Standard at Least Once Every 5 Years to Determine if it (1) Is Still Needed, (2) Needs to be revised or updated, and (3) Can be Replaced by a VCS. Cancel Standards No Longer Needed or that are Replaced by VCSs.

  26. STANDARDS DUE FORCANCELLATION(1)

  27. STANDARDSDUEIN 2008FOR REVALIDATION, REVISION, OR CANCELLATION (4)

  28. Project Selection Schedule(Start/Process Time) • Call for top priority issues to Centers, Tech Fellows, Programs – May 18 (2 wks) • Solicitation to Centers – June 1(6 weeks) • Proposals Due – July 13 • Not limited to priority topics • Center Evaluations – July 18 (4 weeks); due 8/17 • Tech Fellows Integration – August 21 (2 weeks) • EMB review – Sept 5 (2 weeks) • Chief Engineer Approval – October 1

  29. NEW PROPOSAL FORMAT

  30. ADOPTION VS. USE OF APPROVED APPLICABLEDOCUMENT LISTS FROM PROGRAMS/PROJECTS • Adoption of Technical Standards • Early in the NTSP, standards were adopted as “preferred” standards—endorsed for use by the Agency—NOT MANDATORY. • Purpose was to provide data for the A-119 annual report. • Process has been discontinued by the NTSP Office based on purpose they served and labor costs associated with review, approval, and maintenance. • Use of Program/Project Approved Applicable Document Lists • A-119 states: “Many VCSs are appropriate or adaptable for the Government’s purposes.” • Standards are adapted by tailoring, based on program/project needs, as requirements are identified, selected, documented, and approved for use by appropriate authorities. • Compliance with the following requirement (Draft NPR 1.4.d) would be more beneficial to the Agency than adoption: “Program/project managers shall submit the approved listing of all selected technical standards from which program/project technical requirements will be derived to the OCE prior to the SRR. • Note: This data, only required down to the second tier (see Appendix E), will be used to provide NASA’s annual report to NIST and will be designated in the NASA Technical Standards System for reference.” • Tailor Non-NASA Mandatory Engineering Standards with a “Tailoring Requirements” companion document (see example) accessible with the non-NASA document on the website. • RECOMMENDATIONS • Eliminate Adoption Process and Designation. • Remove Reference to Adoption from the Technical Standards NPR. • Submit the Draft NPR in Pre-NODIS Review.

  31. NASA TAILORING REQUIREMENTS DOCUMENT FORNON-NASA STANDARDS NASA TAILORING REQUIREMENTS DOCUMENT NO. OCE-1 Electronic Industry Association (EIA)-649-A—2004 NASA has issued the attached Tailoring Requirements Document No. OCE-1 for EIA-649-A, NATIONAL CONSENSUS STANDARD FOR CONFIGURATION MANAGEMENT, dated 10/28/2004, for use by NASA Programs and Projects This Notice is accessible in the NASA Technical Standards System under EIA-649-A. Approved By: _________________________________ Christopher J. Scolese NASA Chief Engineer

  32. NASA TAILORING REQUIREMENTS DOCUMENT FORNON-NASA STANDARDS (Continued) Utilize Tailoring Guidance in Draft NPR 8070.X

  33. PROCESS FOR CANCELLATION OF NASA TECHNICAL STANDARDS

  34. USE OF REVISION INDICATORS ON NASA TECHNICAL STANDARDS’ APPLICABLE DOCUMENTS PROS— FOR USING REVISION INDICATORS: • To maintain configuration control of the parent document and its children’s requirements—determined by NASA experts. • All requirements of a specific NASA standard version will be the same unless waived. • Once selected and revision applied, no requirement to change requirements every time the standard is updated exists: • Only review the changes and determine if change in requirements is warranted. • Then take appropriate action. • Updates, especially in non-NASA standards, could be incompatible with the citation in the NASA Technical Standard. • When reviewed for update and revised, use latest version —unless there is a technical reason not to. CONS—AGAINST REVISION INDICATORS: • NPD 8070.6 requires that the most recent version of standards be used—an effort to keep people from using obsolete standards and ignoring revisions that generally reflect improvements. PROPOSED RESOLUTION: Specify the current/correct version when a standard is written. Users of the standards should check revisions for useful/necessary improvements made—and act accordingly.

  35. BUDGET UPDATE (OBS COST, FY07) 93% Obs Plan 82% Cost Plan

  36. ECSS: A NEW PHASE-J. Asquier URL:http://www.ecss.n/

  37. CONTENT • ECSS facts • Development phase ->maintenance phase? • Transition implementation • New ECSS Organization • Content reorganization according to 3 types of documents • ECSS 2007 Work-plan

  38. ECSS FACTS • Established to support the space manufacturing industry in Europe • Primary strength is to facilitate standardization of contract requirements in customer/provider relations throughout all levels of space activities • Catch-up production of standards during past two years (mainly in the engineering branch)has led to an almost coherent and complete set of ECSS standards • Fully recognised by all European space entities • Call-up of ECSS as applicable standard in contracts has become a recognised practice in European space business => ECSS ready to go from development phase to maintenance phase?

  39. DEVELOPMENT -> MAINTANCE? • Important to gather user feedbacks: • Organized several events, i.e. User day • Collection of feedback from finished and ongoing projects • Confirmation approaching to maintenance phase (less development needed). However, points to be improved gathered from user feedback: • Some Standards need to be thinner and direct application to business (i.e. tailoring) can be improved, i.e. • Avoid mixing requirements & informative material • Focus on requirements improving their identification and avoid recommendations • Resolve identified overlapping ofrequirements on the same subjects in various documents • Ensure that all requirements can be automatically imported into data bases (e.g. they are uniquely identified)

  40. TRANSITION IMPLEMENTATION • Task Force #1 - Organization of ECSS, tasked to: • Assess the current ECSS organization for the maintenance phase, including identification of specific aspects/resources for the transition • Propose recommendations and a new ECSS organization • Task Force #2 - ECSS Content, tasked to: • Analyze the existing published standards and the draft documents included in the ECSS ongoing Work-Plan. • Propose generic actions on the ECSS structure and type of documents (e.g. differentiation amongst Standards/Handbooks and technical memo) and specific actions per document

  41. NEW ECSS ORGINAZATION Steering Board (SB): Delegates from member organisations. Responsible for policy and strategy issues and for overall supervision. Does not approve individual Standards. Technical Authority (TA): Delegates from members organizations. Set up and implement Work-plan. Authorize Public Review and approval of documents. Executive Secretariat (ES): Performed by ESA/ESTEC. Provide support to SB & TA. Support WGs in drafting documents in accordance with ECSS rules / procedures. Custodians of ECSS docs. Collect and analyze of Change Requests, New Work Items Proposals, feedback … Monitor schedule and budget Steering Board (SB) Executive Secretariat (ES) Technical Authority (TA) Working Group Network of experts Working Group Working Group Working Group

  42. THREE TYPES OF DOCUMENTS • Standard • Normative document written specifically for direct use in invitation to tender and business agreements for implementing space related activities having its content strictly limited to the statement of verifiable customer requirements, supported by the minimum descriptive text necessary for understanding their context. • Handbook • Non-normative document providing background information, e.g. orientation, guidelines, technical data, advice or recommendations, which contains information about how to implement space related activities. • Note: Handbook contains data recognized as valid for use by the ECSS community. • Technical Memorandum • Non-normative document providing useful information to the space community on a specific subject, prepared to record and present non-normative data, which are not relevant for a Standard or for a handbook, or not yet mature to be published as handbook or standard.

  43. ECSS 2007 WORK-PLAN • All standards to be reissued in one batch • Few new standards • Reorganization of information leading to the creation of HBs and TMs Management Branch Engineering Branch Quality Branch Space Debris

  44. CONSULTATIVE/COMMITTEE ON SPACE DATA SYSTEMS (CCSDS) STANDARDS ACTIVITIES Mike Kearney

  45. CCSDS Report Mike Kearney CCSDS Acting General Secretary NASA MSFC EO-01 256-544-2029 Mike.Kearney@nasa.gov June 2007

  46. CCSDS “quick look” OBSERVER AGENCIES ASA/Austria CAS/China CAST/China CRC/Canada CRL/Japan CSIR/S.Africa CSIRO/Australia CTA/Brazil DSR/Denmark EUMETSAT/Europe EUTELSAT/Europe FSST&CA/Belgium HNSC/Greece IKI/Russia ISAS/Japan ISRO/India KARI/Korea KFKI/Hungary MOC/Israel NRL-NCST/USA NOAA/USA NSPO/Taipei SSC/Sweden TsNIIMash/Russia USGS/USA MEMBER AGENCIES ASI/Italy BNSC/UK CNES/France CSA/Canada DLR/Germany ESA/Europe FSA/Russia INPE/Brazil JAXA/Japan NASA/USA • Founded in 1982 (25th Anniversary!) • Agency-based international committee • Currently 10 Member agencies • Currently 23 Observer Agencies • Currently 28 nations • Also functions as ISO Committee • TC20/SC13 • Represents 17 nations • Producing Voluntary Consensus Standards • NASA Program Exec is John Rush • NASA HQ – SOMD – SCaN • Has temporarily delegated some roles to MSFC • NASA “principal delegate” • CCSDS General Secretary • ISO TC20/SC13 Secretary 46

  47. NASA Data Standards Program Organization ISO NASA Data Standards Program Executive NASA-HQ, SOMD, SCaN Office NASA Technical Standards Program NASA-HQ, OCE CCSDS External Liaisons US Gov. Agencies CCSDS/ISO Secretariat (AIAA - MSFC contract) NASA Data Standards Program Office JPL Adrian Hooke US National Standards GSFC Space Data Standards Office Madeline Butler JPL Space Data Standards Office Peter Shames MSFC Space Data Standards Office Mike Kearney JSC Space Data Standards Office John Saiz 47

  48. CCSDS Technical Context: Six Focus Areas • Systems Architecture • Security • Information Architecture • Space Addressing and Naming Systems Engineering Systems Engineering Spacecraft Onboard Interface Services Spacecraft Onboard Interface Services Space Link Services Space Link Services Cross Support Services Cross Support Services Mission Operations & Info. Management Mission Operations & Info. Management Space Internetworking Services Space Internetworking Services • Onboard Subnet. Services • Onboard Application Services • RF & Modulation • Space Link Coding & Sync. • Data Compression • Space Link Protocols • TC Channel Coding • Ranging • High Rate Uplink • Data Archive Ingestion • Navigation • Info. Pack. & Registries • Spacecraft Monitor & Control • CS Service Management • CS Transfer Services • CFDP Testing • Cislunar Space Internet. • Space Packet Protocol • Asynchronous Messaging • IP-over-CCSDS Links Twenty-four working groups 48

  49. CCSDS Overview: Organization ISO Liaisons Stakeholders Infrastructure providers Missions / Programs CCSDS CCSDS Secretariat CCSDS Management Council (CMC) Space Assigned Numbers Authority CCSDS Engineering Steering Group Systems Engineering Space Link Services Mission Operations & Info. Management Spacecraft Onboard Interface Services Cross Support Services Space Internetworking Services WG’s WG’s WG’s WG’s WG’s WG’s WG’s WG’s WG’s WG’s WG’s WG’s WG’s WG’s WG’s WG’s WG’s WG’s

  50. CCSDS Technical Context: Six Focus Areas ISO Other TCs Technical Committee 20 (ISO/TC20): Aircraft and Space Vehicles CCSDS Subcommittee 14 (ISO/TC20/SC14): Space Systems and Operations Other SCs CCSDS Secretariat CCSDS Management Council (CMC) Space Assigned Numbers Authority CCSDS Engineering Steering Group (Secretariat: AIAA) CCSDS Engineering Steering Group Systems Engineering Spacecraft Onboard Interface Services Mission Operations & Info. Management Operations & Ground Support Space Debris Interfaces, Integration & Test Design Engineering & Production Space Link Services Space Internetworking Services Cross Support Services Environment (natural & induced) Program Management Materials and Processes WG’s WG’s WG’s WG’s WG’s WG’s WG’s WG’s WG’s WG’s WG’s WG’s WG’s WG’s WG’s WG’s WG’s WG’s