1 / 22

NASA CIO Standards Activities

NASA CIO Standards Activities. Presentation to NASA Technical Standards Working Group June 11-12, 2007. HQ/R. Benedict. Topics. Process for mandatory IT technical standards Traceability of use of mandatory IT technical standards by programs and projects (and other initiatives)

sereno
Download Presentation

NASA CIO Standards Activities

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. NASA CIO Standards Activities Presentation to NASA Technical Standards Working Group June 11-12, 2007 HQ/R. Benedict

  2. Topics • Process for mandatory IT technical standards • Traceability of use of mandatory IT technical standards by programs and projects (and other initiatives) • IT Technical Authority

  3. Mandatory IT Technical Standards • NASA’s IT technical standards focus on integration and interoperability to achieve secure information exchange and resource sharing • NPR 2800.1, Managing Information Technology, states: • NASA organizations and NASA contractors, for which a standard and/or architecture apply (see paragraph 2.2.3 for a definition of the criteria for contractor applicability), must comply with the standard and/or architecture unless a waiver is obtained” • As a result, all NASA IT technical standards are mandatory unless waived

  4. Process for IT Technical Standards • The process for development and approval of IT technical standards consists of three major steps • Informal review • Formal review • Approval

  5. Process for IT Technical Standards • Informal review • The group responsible for a particular standards area works internally to determine key NASA and industry trends that need to be addressed and which standards require revision. • After a proposed standard has been drafted by the cognizant standards group, it is released to the NASA IT community for comment; comments are requested from NASA civil service, our contractors, vendors, etc. • Comments do not require Center or Project level consolidation since we are seeking unbiased and unfiltered input • Because of the range of comments received during this phase, the standards group may not always disposition comments during this phase

  6. Process for IT Technical Standards • Formal review • After the informal comments have been integrated into the proposed standard, a revised draft of the standard is created. • The revised draft is released to the CIO community and comments are solicited from each center through the Center CIO. Certain Agency level IT groups such as IEMP, ODIN, and PKI are encouraged to comment directly. • Each comment received during the Formal Review Process must be dispositioned. • The cognizant standards group works with Center CIO's and their representatives to address any outstanding issues and prepare for the Final Review and Ratification

  7. Process for IT Technical Standards • Approval • After the formal comments have been dispositioned, the cognizant standards group prepares the final draft standard for the approval of the CIO's. • At this point, any outstanding issues or concerns are noted along with recommendations. • The final draft standard is presented to the CIO Board for final approval and subsequently signed into policy by the CIO • The CIO Board is comprised of the Mission Directorate and Center CIOs, and is chaired by the NASA CIO • The NASA CIO solicits input from the CIO Board members but makes the final acceptance decision

  8. Traceability of Use • Today, we have limited insight into the use of applicable IT technical standards by programs, projects, and other initiatives • Enterprise Architecture reviews may uncover some issues • Since IT technical standards are intended to enable integration, interoperability, and secure exchange of information, we may become aware of issues when something “breaks” • A bigger issue is unnecessary duplication of IT infrastructure, addressed in NPR 2830.1, NASA Enterprise Architecture Procedures

  9. IT Technical Authority • OCIO plans to implement an IT Technical Authority (TA) modeled after the OCE TA • The NASA CIO has presented an IT TA concept to the Agency SMC and OMC • A final approach and plan for implementation are due by July 31, 2007

  10. From April 25, 2007 SMC Briefing 10

  11. From April 25, 2007 SMC Briefing 11

  12. From April 25, 2007 SMC Briefing 12

  13. From April 25, 2007 SMC Briefing 13

  14. From April 25, 2007 SMC Briefing Please note that this is a conceptual model! 14

  15. Backup

  16. EA Review Inclusion Flow Source: NPR 2830.1

  17. NASA IT Standards Snapshot NASA-STD-2804 and 2805 have been recently updated and will be posted soon

  18. NASA IT Standards Snapshot

  19. NASA IT Standards Snapshot

  20. NASA IT Standards Snapshot A new version of NASA-STD-2819 is nearing completion

  21. Develop New Guidance Retire Outdated Guidance Policy-Rooted Standards Process

  22. Mapping Standards/EA/Policy to NPR 2800 This matrix is an extract of an in-work spreadsheet that maps OCIO standards, EA, and derivative policy documents to NPR 2800, the document that defines OCIO top-level requirements for managing IT

More Related