NASA TECHNICAL STANDARDS WORKING GROUP MEETING
This presentation is the property of its rightful owner.
Sponsored Links
1 / 104

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


  • 65 Views
  • Uploaded on
  • Presentation posted in: General

NASA TECHNICAL STANDARDS WORKING GROUP MEETING JUNE 11 – 12, 2007 COCOA BEACH, FL. Monday, June 11, 2007 8:30 – 8:45Welcome/Agenda Gill/Matthews 8:45 – 9:30 Program Status Gill Key Points Relationship Between NASA Technical Fellows and the

Download Presentation

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

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


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


Agenda

Monday, June 11, 2007

8:30 – 8:45Welcome/Agenda Gill/Matthews

8:45 – 9:30 Program StatusGill

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:15NASA Lessons Learned Initiative KSC/Henderson

10:15 - 10:30Break

10:30 – 11:00 Mandatory Engineering Standards HQ/West

Implementation Status/Via Teleconference

11:00 – 12:00Discussion on NASA Interim Directive Weinstein

for NASA Mandatory Engineering Standards

12:00 – 12:30Safety and Mission Assurance (S&MA) Harkins Standards Activities

Mandatory Standards

- Process for Mandatory Standards

- Traceability of Use by Program and Projects

12:30 – 1:30Lunch

1:30 – 2:15Office 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:00Break

3:00 – 3:30Consultative/Committee on Space Data Systems Kearney

(CCSDS) Standards Activities

3:30 – 4:00 Agency-wide Part Management System USA/Zook

4:00 – 4:30New Features in the NASA Technical Garcia/Johnston

Standards System’s Document Search and Retrieval

4:30 – 5:00NASA Engineering Network (NEN) / IHS/Davis

Integrated Technical Standards System (ITSS) and

Standards Reference Linking Solution

5:00Adjourn

Tuesday, June 12, 2007

8:00 – 8:30Common NASA Taxonomy for Problem Reporting KSC/Beil

Analysis, and Resolution Standard

8:30 – 9:00NESC Technical Fellows Terrone

9:00 – 9:15Break

9:15 – 9:45Center 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:00Wrap-up (Actions, Other Issues, Concerns) All

11:00 – 12:00Lunch

12:00KSC Tour

AGENDA


Nasa technical standards working group meeting june 11 12 2007 cocoa beach fl

PROGRAM STATUS

Paul Gill


Key points for discussion during the meeting

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?


  • Nasa technical standards working group meeting june 11 12 2007 cocoa beach fl

    PROCESS FOR DEVELOPING

    NASA TECHNICAL STANDARDS

    INITIATE

    DEVELOP

    REVIEW / REVISE

    APPROVE

    IMPLEMENT

    NASA Technical Standards Program Paul Gill, Manager

    May 4, 2007


    Process for developing nasa technical standards with nasa technical fellow participation

    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


    Process for developing nasa technical standards with nasa technical fellow participation continued

    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


    What s new in approved standards as of 05 30 2007

    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-7009Standard for Models 12/01/2006

      and Simulations (Interim)

    • NASA-STD-6002CApplying Data Matrix Identification03/21/2007 Symbols on Aerospace Parts

    • NASA-STD-4005LEO Spacecraft Charging 06/03/2007

      Design Standard

    • NASA-HDBK-4006LEO Spacecraft Charging 06/03/2007

      Design Handbook


    Nasa technical standards working group meeting june 11 12 2007 cocoa beach fl

    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


    Nasa standards in development revision status

    NASA STANDARDS IN DEVELOPMENT / REVISION STATUS


    Nasa technical standards working group meeting june 11 12 2007 cocoa beach fl

    NASA STANDARDS IN DEVELOPMENT / REVISION STATUS (Continued)


    Nasa standards in development revision status continued

    NASA STANDARDS IN DEVELOPMENT / REVISION STATUS (Continued)


    Nasa standards in development revision status continued1

    NASA STANDARDS IN DEVELOPMENT / REVISION STATUS (Continued)


    Nasa standards in development revision status continued2

    NASA STANDARDS IN DEVELOPMENT / REVISION STATUS (Continued)


    Nasa standards in development revision status continued3

    NASA STANDARDS IN DEVELOPMENT / REVISION STATUS (Continued)


    Nasa standards in development revision status continued4

    NASA STANDARDS IN DEVELOPMENT / REVISION STATUS (Continued)


    Nasa standards in development revision status continued5

    NASA STANDARDS IN DEVELOPMENT / REVISION STATUS (Continued)


    Nasa standards in development revision status continued6

    NASA STANDARDS IN DEVELOPMENT / REVISION STATUS (Continued)


    Nasa standards in development revision status continued7

    NASA STANDARDS IN DEVELOPMENT / REVISION STATUS(Continued)


    Vcss in development status continued

    VCSs IN DEVELOPMENT STATUS (Continued)

    (/c — with comments)


    Vcss in development status

    VCSs IN DEVELOPMENT STATUS

    (/c — with comments)


    Nasa interim standards conversion status

    NASA INTERIM STANDARDS CONVERSION STATUS


    Nasa interim standards conversion status1

    NASA INTERIM STANDARDS CONVERSION STATUS


    Nasa interim standards conversion status2

    NASA INTERIM STANDARDS CONVERSION STATUS


    Technical standards requiring for revalidation revision or cancellation 4

    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.


    Standards due for cancellation 1

    STANDARDS DUE FORCANCELLATION(1)


    Standards due in 2008 for revalidation revision or cancellation 4

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


    Project selection schedule start process time

    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


    Nasa technical standards working group meeting june 11 12 2007 cocoa beach fl

    NEW PROPOSAL FORMAT


    Adoption vs use of approved applicable document lists from programs projects

    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.


    Nasa tailoring requirements document for non nasa standards

    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


    Nasa tailoring requirements document for non nasa standards continued

    NASA TAILORING REQUIREMENTS DOCUMENT FORNON-NASA STANDARDS (Continued)

    Utilize Tailoring Guidance in Draft NPR 8070.X


    Nasa technical standards working group meeting june 11 12 2007 cocoa beach fl

    PROCESS FOR CANCELLATION OF NASA TECHNICAL STANDARDS


    Use of revision indicators on nasa technical standards applicable documents

    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.


    Nasa technical standards working group meeting june 11 12 2007 cocoa beach fl

    BUDGET UPDATE (OBS COST, FY07)

    93% Obs Plan

    82% Cost Plan


    Ecss a new phase j asquier

    ECSS: A NEW PHASE-J. Asquier

    URL:http://www.ecss.n/


    Content

    CONTENT

    • ECSS facts

    • Development phase ->maintenance phase?

    • Transition implementation

    • New ECSS Organization

    • Content reorganization according to 3 types of documents

    • ECSS 2007 Work-plan


    Ecss facts

    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?


    Development maintance

    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)


    Transition implementation

    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


    New ecss orginazation

    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


    Three types of documents

    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.


    Ecss 2007 work plan

    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


    Nasa technical standards working group meeting june 11 12 2007 cocoa beach fl

    CONSULTATIVE/COMMITTEE ON SPACE DATA SYSTEMS (CCSDS) STANDARDS ACTIVITIES

    Mike Kearney


    Nasa technical standards working group meeting june 11 12 2007 cocoa beach fl

    CCSDS Report

    Mike Kearney

    CCSDS Acting General Secretary

    NASA MSFC EO-01

    256-544-2029

    [email protected]

    June 2007


    Ccsds quick look

    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


    Nasa technical standards working group meeting june 11 12 2007 cocoa beach fl

    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


    Ccsds technical context six focus areas

    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


    Ccsds overview organization

    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


    Ccsds technical context six focus areas1

    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


    Ccsds technical context six focus areas2

    CCSDS Technical Context: Six Focus Areas

    ISO

    Other

    TCs

    Technical Committee 20 (ISO/TC20): Aircraft and Space Vehicles

    Subcommittee 13

    (ISO/TC20/SC13):

    Space Data and

    Information Transfer

    Systems

    Subcommittee 14

    (ISO/TC20/SC14):

    Space Systems

    and Operations

    Other

    SCs

    TC20/SC13

    Heads of Delegation

    (CCSDS CMC)

    (Secretariat: AIAA)

    (Secretariat: NASA)

    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


    Nasa technical standards working group meeting june 11 12 2007 cocoa beach fl

    Current CCSDS Program of Work: Area Directors and Working Group Chairs

    52


    Nasa technical standards working group meeting june 11 12 2007 cocoa beach fl

    CCSDS: open international standards for space mission interoperability

    CCSDS: international focal pointfor space interoperability standards

    • IETF/IRTF: open international standards for IP suite and Disruption Tolerant Networking (DTN)

    • OMG: industry standards for exchange of application information among vendor products

    • IOAG: interoperable mission support infrastructure

    • ECSS: European regional standards for space mission support

    • AIAA: North American regional standards for space mission support

    • SFCG: space agency frequency management forum

    53


    Www ccsds org

    www.ccsds.org

    54


    Www ccsds org1

    www.ccsds.org

    55


    Www ccsds org2

    www.ccsds.org

    56


    Www ccsds org3

    www.ccsds.org

    57


    Current ccsds status

    Current CCSDS Status

    • CCSDS Management Council workshop in Brussels

      • June 25-27. Follows IOAG meeting

        • Expect IOAG actions to CCSDS

      • Major IOAG issue: Cross Support Actions

        • IOAG wants CCSDS-developed cross-support architecture, catalog

        • NASA SCaN is developing NASA Consolidated Network Service Architecture for DSN, GN, SN

        • At IOAG meeting in Spain, NASA’s future SCaN architecture meets ESA’s equivalent

        • Expect much fallout for CCSDS to work

      • Business processes: Enable Web-based chartering, document project management, better RID accountability

      • OMG co-located at this meeting

        • Plan to discuss overlap, conflicts, collaboration, etc.

    58


    Current ccsds status1

    Current CCSDS Status

    • ISO TC20/SC13 topics:

      • Closing in on agreement to have joint Navigation Orbit Data Message format with ISO TC20/SC14

        • Had major issues at outset. Finally prevented issue of two competing standards from the two groups

      • Reopening proposal to ISO to put SC13 and SC14 under a new ISO Technical Committee (TC999)

        • Would consolidate Space Standards, separate from aviation standards

    • Technical topics

      • Some ESA momentum to drive towards plug-n-play and application portability, versus interoperability (NASA focus)

      • ESA driving very “prescriptive” solutions because of their multinational contracting approach

      • NASA preferring more interoperability focused topics, more loosely coupled architecture

    59


    Current ccsds status2

    Current CCSDS Status

    • Constellation (C3I) and CCSDS:

      • C3I has adopted a mix of standards, some CCSDS, some not

        • Adopted AOS, CFDP, NASA Experimental LDPC coding

      • Constellation approach to IP encapsulation is an issue with internationals and some NASA orgs (including DSN)

        • RIDs to IP over CCSDS take issue with Cx’s IPHDLCAOS approach (from ESA, CNES, BNSC, and NASA)

      • CCSDS Spacecraft Monitor & Control (SM&C) group is very ESA oriented, started with minimal NASA participation

        • Initial NASA/C3I assessment: focus is on application portability, not interoperability

          • Serves ESA needs for multinational contracting approaches

          • NASA concerns about constraining application functionality and innovation

        • Cx has become engaged in SM&C, ESA responding well to NASA comments.

          • New versions of draft documents due soon

    60


    Ccsds future plans

    CCSDS Future Plans

    • CCSDS Working Group meeting schedule

      • Fall 2007 in Heppenheim Germany: 10/1 to 10/5

        • Between Darmstadt and Heidelberg

      • Spring 2008 in Colorado Springs: 4/22 to 4/27

      • Fall 2008 in Berlin, Germany

    • Take-home message:

      • Much work to be done

        • Enabling Interoperability

        • Stimulating COTS development to meet needs of space programs

      • Critical to NASA’s Exploration programs

      • More NASA centers and programs should be encouraged to log onto CCSDS website, participate in review and comment to CCSDS documents

    61


    New ntsp document search system overview danny garcia

    NEW NTSP DOCUMENT SEARCH SYSTEM OVERVIEWDanny Garcia


    Nasa technical standards working group meeting june 11 12 2007 cocoa beach fl

    A PRACTICAL SOLUTION FOR EFFECTIVE STANDARDS MANAGEMENT

    Specs & Standards is changing…

    From

    Simply a document search

    and retrieval tool.

    To

    A powerful search engine

    that helps manage your

    standards.

    Why the change?

    IHS listened to customers who told us they needed a more intuitively designed interface that helps them better locate standards, and manage their use of standards.


    What is changing

    WHAT IS CHANGING?

    • Improved Search Results – making it harder to inadvertently get the wrong results

    • New Look & Feel – easy-to-use design and navigation

    • Personalization – quick access to favorite documents and lists, personal notifications, and the ability to set preferences

    • Easily Locate the Right Standard – enhanced search filters, recently viewed documents, and referenced standards

    • Simpler Tools for Standards Management – favorites, watch lists, saved searches, and alerts


    Nasa technical standards system comparision

    Current System

    Document Search

    SUNS

    Lessons Learned

    Application Notes

    Training Modules

    Fasteners eCatalog

    4D Parts Universe

    Document Locator

    New System

    Document Search

    SUNS

    Lessons Learned

    Application Notes

    Training Modules

    Fasteners e Catalog

    4 D Parts Universe

    Document Locator

    Favorites List

    Watch List

    Print Results Capability

    Recently Viewed Documents

    Linked Applicable References

    ASME-BPVC Table of Contents

    System Updates and Enhancements

    NASA TECHNICAL STANDARDS SYSTEM COMPARISION


    Technical standards system rfp contract events

    TECHNICAL STANDARDS SYSTEM RFP/CONTRACT EVENTS

    • Released RFPNovember 2005

    • Old contract expiredApril 31, 2006

    • Contract extension (2 months)May/June, 2006

    • Awarded new contract to IHSJune 30, 2006

    • Modified contractNovember 14, 2006

      • From custom ITSS to IHS common platform

      • Same platform used by NASA contractors

      • Saved Agency $412,000

    • New System Beta testMay 2007

    • Agency-wide system deploymentJun 2007


    Technical standards system rfp contract events1

    TECHNICAL STANDARDS SYSTEM RFP/CONTRACT EVENTS

    • Released RFPNovember 2005

    • Old contract expiredApril 31, 2006

    • Contract extension (2 months)May/June, 2006

    • Awarded new contract to IHSJune 30, 2006

    • Modified contractNovember 14, 2006

      • From custom ITSS to IHS common platform

      • Same platform used by NASA contractors

      • Saved Agency $412,000

    • New System Beta testMay 2007

    • Agency-wide system deploymentJune 2007


    Future plans

    FUTURE PLANS

    • Deploy Document Search and Retrieval System to Agency

    • Work on an approach to track which standards are being used by the Agency’s programs/projects

      • Tracking of changes

      • Performing Trend analysis in order to facilitate smart updates to standards

      • Make this information available through the system

    • Reenergize effort of linking LL to Technical Standards working closely with the Agency’s LL Program

    • Use Reference Linking tool as a viable method to link to requirements and applicable documents


    Nasa technical standards working group meeting june 11 12 2007 cocoa beach fl

    DOCUMENT SEARCH

    AND

    RETRIEVAL SYSTEM

    DEMONSTRATION


    New search page

    NEW SEARCH PAGE


    New search results page

    NEW SEARCH RESULTS PAGE


    Document view page

    DOCUMENT VIEW PAGE


    Document details page view 1

    DOCUMENT DETAILS PAGE VIEW 1


    Document details page view 2

    DOCUMENT DETAILS PAGE VIEW 2


    Nasa technical standards working group meeting june 11 12 2007 cocoa beach fl

    NASA Technical Standards System (NTSS) Metrics Dashboard

    Danny Garcia

    NTSWG Meeting June 11-12, 2007

    Cocoa Beach, Florida


    Background

    Background

    • Description

      • NTSP delivers standards documents and publications to NASA and Contractor entities Agencywide.

      • The metrics pertaining to the usage and delivery of those documents and publications provide insight agency wide.

      • Metrics also provide the ability to do reporting to agency leadership including the NASA Chief Engineer.

    • Purpose

      • Metric data must be current, relevant, and accurate.

      • NTSP has contracted UNITeS to create web site content.

      • Metrics on utilization is a crucial factor of the effectiveness of the NTSP.

    • Web site Demonstration


    Nasa technical standards working group meeting june 11 12 2007 cocoa beach fl

    Data Flow

    srvweb04 boundary

    Read Access Path

    MSFC Private LAN

    Write Access Path

    0

    User Accesses Site

    Metric Data

    Loaded

    By NTSP

    Process*

    • NTSP Process:

    • IHS creates XML files of access information

    • NTSP process retrieves XML and parses data into the SQL container

    Browser Display Updated

    With graph of metric data

    0

    MSSQL

    msbravo05

    User Requests

    Metric Data


    Nasa technical standards working group meeting june 11 12 2007 cocoa beach fl

    METRIC DASHBOARD DEMO

    Jay Johnston


    Nasa technical standards working group meeting june 11 12 2007 cocoa beach fl

    NESC TECHNICAL FELLOWS

    Mark Terrone


    Nasa engineering and safety center nasa technical fellows program

    NASA Engineering and Safety CenterNASA Technical Fellows Program

    March 2007


    Background1

    Background

    • Safety philosophy has 3 tenets:

      • Strong in-line checks and balances

      • Healthy tension

      • “Value added” independent assessment

    • NESC provides independent assessment of technical issues for NASA programs and projects

    Apollo Saturn 5 Launch Vehicle

    The NESC is cultivating a Safety culture focused on engineering and technical excellence, while fostering an open environment and attacking challenges with unequalled tenacity.


    Nesc model

    NESC Model

    • Simple, straightforward concept – institutionalize the “Tiger Team” approach

      Bring together some of NASA’s best engineers with experts from industry, academia, and other government agencies to address our highest risk, most complex issues

    • Decentralized organizational structure across all Centers reporting to the NESC management office at Langley Research Center

    • Engineers need to be where the problems are to stay sharp

    • Synergy gained by using diverse, expert technical teams to develop robust technical solutions

    Space Shuttle on Mobile Launch Platform


    Nesc model continued

    NESC Model (Continued)

    • Small core of engineering experts at Centers for insight into respective programs

    • Recognized Agency discipline experts, selected as NASA Technical Fellows, leading Technical Discipline Teams (TDT)

      • Use “ready” experts from across NASA, industry, academia and other government agencies to staff TDTs

      • Tap “ready” experts to attack “trouble spots”

    Hubble Space Telescope

    • Strong Systems Engineering function for proactive trending and identification of problem areas before failures occur

    Focus on technical rigor and engineering excellence


    Nasa technical standards working group meeting june 11 12 2007 cocoa beach fl

    NESC Organization

    • 50+ fulltime NESC-badged employees

    • Current NESC employees selected from across the Agency, four external to NASA (as of March 2007)

    • Encourage NESC members to remain actively engaged at their respective Centers

    • Technical Discipline Teams (TDT) led by NASA Technical Fellows

      • 15 to 30 matrixed employees per team

    • Three cross-cutting Technical Discipline Teams

    • Contracts and partnerships include industry, academia and other Government agencies on our teams

    Where Current NESC Employees Came From

    (as of March 2007)


    Nasa technical standards working group meeting june 11 12 2007 cocoa beach fl

    Office of the Director (C1)

    Ralph R. Roe -- Director

    Timmy R. Wilson -- Deputy Director

    Kenneth D. Cameron -- Deputy Director for Safety

    Charles Camarda -- Deputy Director for

    Advanced Projects

    NASA HQ Senior

    S&MA Integration

    Manager

    Wayne R. Frazier

    NASA HQ Chief

    Engineer Representative

    Dennis B. Dillman (acting)

    Management and Technical Support Office (C101)

    Patricia L. Dunnington -- Manager

    Systems Engineering Office (C102)

    Dawn M. Schaible -- Manager

    Principal Engineers Office (C103)

    Three Principal Engineers and Six Back-up Principal Engineers

    NASA Technical Fellows Office (C104)

    One NASA Technical Fellow for Each Disciplines

    NESC Chief Engineers

    Office (C105)

    One NESC Chief Engineer for Each Center and HQ

    NESC Organization

    7/10/06


    Partnerships collaborations

    Partnerships / Collaborations


    Nesc and nasa technical fellows goals

    NESC and NASA Technical Fellows Goals

    • Provide a resource for independent test, analysis and evaluation of NASA’s most difficult problems

    • Provide leadership, stewardship, and role models for NASA discipline engineering communities

    • Increase the focus on technical excellence Agency-wide

    • Provide technical consistency across NASA

    • Recognize outstanding engineers and scientists who have distinguished and sustained records of technical achievement

    • Improve Safety and Mission Success


    Responsibilities

    Responsibilities

    • Serve as senior technical expert for the Agency in support of the Office of the Chief Engineer and the NESC

    • Lead NESC Technical Discipline Team

    • Serve as an independent resource to the Agency and industry to resolve complex issues

    • Lead Agency-wide discipline working groups

    • Foster consistency of Agency-level standards and specifications (including “core” standards) and involved in levying standards & specs on major programs/projects

    • Promote discipline stewardship through workshops, conferences and discipline advancing activities

    • Ensure Lessons Learned are identified and incorporated into Agency processes


    Program details

    Program Details

    • Infrastructure of the NESC will be used to fund, manage, and support

    • NASA Technical Fellows are NESC employees, but remain resident and actively engaged at their Centers

    • Senior Grade (ST) positions, competitively selected

      • Incorporate new Agency ST criteria process

    • Temporary tenure (Up to 5 years – 2 years, then reviewed each year)

    • Phased implementation

      • 12 NESC Discipline Experts (NDEs) become Technical Fellows

      • 7 additional Technical Fellows will be advertised and selected near-term

      • 25 Technical Fellows maximum at full implementation

    • Funding of Discipline Activities to be provided through approval of the NESC Review Board

      • EMB will review Discipline Activities Plan

      • Activities follow NESC processes and procedures


    Implementation phase 1

    Implementation – Phase 1

    • Existing 12 NESC Discipline Experts to be appointed as Technical Fellows:

      • Avionics / Electronics - Mitch Davis

      • Aerosciences (was Flight Sciences) - Dave Schuster

      • Loads and Dynamics - Curt Larsen

      • Non-Destructive Evaluation - Bill Prosser

      • Propulsion - George Hopson

      • Software - Mike Aguilar

      • Guidance, Navigation, and Control - Neil Dennehy

      • Life Support / Active Thermal - Hank Rotter

      • Materials - Bob Piascik

      • Mechanical Systems - John McManamen

      • Structures - Ivatury Raju

      • Human Factors - Cynthia Null

    • Advertise and select an additional 4 Technical Fellows (FY-07):

      • Electrical Power (split from original NESC Power and Avionics NDE)

      • Flight Mechanics (split from original NESC Flight Sciences NDE)

      • Passive Thermal (split from original NESC Life Support/Fluids/Thermal NDE)

      • Space Environments


    Implementation phase 2 and 3

    Implementation – Phase 2 and 3

    • Phase 2 - Advertise and select an additional 2 Technical Fellows in FY-08:

      • Cryogenics

      • Sensors / Instrumentation

    • Phase 3 - Advertise and select Systems Engineering Technical Fellow in FY-09 (to be a part of the existing NESC Systems Engineering Office)

    • The need for additional Technical Fellows will be evaluated semi-annually and reviewed at the Engineering Management Board (EMB)

    • NASA Technical Fellows are competitively selected:

      • Use Agency ST criteria

      • Selection panel to include Senior Grade employees and EMB representatives

      • NESC Director recommends selection for NASA Chief Engineer’s approval


    Nasa technical fellow disciplines

    NASA Technical Fellow Disciplines

    • Aerosciences

    • Avionics

    • Cryogenics

    • Electrical Power

    • Flight Mechanics

    • Guidance, Navigation, and Control

    • Human Factors

    • Life Support / Active Thermal

    • Loads and Dynamics

    • Materials

    • Mechanical Systems

    • Non-Destructive Evaluation

    • Passive Thermal

    • Propulsion

    • Sensors / Instrumentation

    • Software

    • Space Environments

    • Structures

    • Systems Engineering

    Blue: Phase 1 additions

    Red: Phase 2 & 3 additions


    Nesc academy

    NESC Academy

    • The NESC Academy captures the experience of the NESC experts and passes that experience along to NASA’s next generation

    • Each NASA Technical Fellow will conduct a course during their tenure

    • Six courses already completed

      • Space Life Support Systems taught by Hank Rotter at the University of Houston, Clear Lake

      • Space Propulsion Systems taught by George Hopson at Alabama A&M

      • Power and Avionics taught by Robert Kichak at the University of Maryland

      • Satellite Attitude Control Systems taught by Neil Dennehy at the University of Maryland

      • Human Factors taught by Cynthia Null at George Mason University

      • Software as an Engineering Discipline taught by Michael Aguilar at George Mason University

    Satellite Attitude Control Systems, June 2006

    Hank Rotter (R) and Student

    Neil Dennehy (R) and Student


    Summary

    Summary

    • Goals of NESC and NASA Technical Fellows Program:

      • Provide a resource for independent test, analysis and evaluation of NASA’s most difficult problems

      • Provide leadership, stewardship, and role models for NASA discipline engineering communities

      • Increase the focus on technical excellence Agency-wide

      • Provide technical consistency across NASA

      • Recognize outstanding engineers and scientists who have distinguished and sustained records of technical achievement

      • Improve Safety and Mission Success

    • An induction ceremony for the first 12 NASA Technical Fellows will be held near the Langley Research Center on April 11, 2007

    • Selection of the four Phase 1 NASA Technical Fellows to be completed by Summer 2007

    • Phase 2 and 3 NASA Technical Fellows will also be advertised


    Thank you

    Thank You

    Additional information about the NESC and its activities can be found at:

    www.nesc.nasa.gov

    For general questions and requests for NESC technical reviews:

    Email: [email protected]

    For anonymous requests write:

    NESC

    NASA Langley Research Center

    Mail Stop 118

    Hampton, VA 23681


    Nasa technical standards working group meeting june 11 12 2007 cocoa beach fl

    CENTER REPORTS


    Nasa technical standards working group meeting june 11 12 2007 cocoa beach fl

    “QUAD CHART” STATUS REPORT

    JPL TECHNICAL STANDARDS PROGRAM

    David Oberhettinger

    Technical Standards Program

    Office of the Chief Engineer

    Jet Propulsion Laboratory

    June 11, 2006


    Nasa technical standards working group meeting june 11 12 2007 cocoa beach fl

    STATUS REPORT FOR STANDARDS SUPPORTTechnical Standards Assessment, Review, and Support Date: April 2007 through June 2007

    TWG Chair: Paul Willis

    Center: JPL

    Phone: 818-393-6998

    Proposal No.: N/A

    If VCS, Standards Developing Org: N/A

    Start: October 2006

    Deliver to NTSPO: Ongoing task

    Task Description: (1) Identify and review replacement specifications for cancelled government specifications; (2) support review, coordination and center approval of NASA technical standards; and (3) support NASA technical standards subtask & M&P working groups.

    • Plans

    • Support standards action items as requested by

    • the NTSPO

    • Continue to support the NASA Office of the Chief

    • Engineer, as needed, in developing and

    • reviewing ISO standards.

    • As funding allows, JPL will continue to

    • participate in meetings of the NTSWG and the

    • Technical Standards NPR drafting committee.

    • Issues

    • ●Budget has been cut and some AI response may

    • not be possible during the latter part of the year.

    • ● NASA has issued a stop work order for JPL

    • standard development projects

    Accomplishments

    Major accomplishments this quarter included:

    ●Evaluated the proposed set of NASA core standards and

    participated on the RSR Team

    ●Provided re-justification information for ongoing JPL

    standard development projects, and rated Center tasks

    ●Prepared a center concurrence letter approving a NASA

    standard. Initiated review of a number of draft OCE and

    OSMA standards

    ●Active participation on the NTSWG

    ●Responded to action items, including the above

    reviews.

    5/25/07 Draft


    Nasa technical standards working group meeting june 11 12 2007 cocoa beach fl

    ACTION STATUS

    As of 06/07/2007


    Nasa technical standards working group meeting june 11 12 2007 cocoa beach fl

    ACTION STATUS


    Nasa technical standards working group meeting june 11 12 2007 cocoa beach fl

    ACTION STATUS


    Nasa technical standards working group meeting june 11 12 2007 cocoa beach fl

    ACTION STATUS


    Nasa technical standards working group meeting june 11 12 2007 cocoa beach fl

    ACTION STATUS


  • Login