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

Slides:



Advertisements
Similar presentations
15June’061 NASA PKI and the Federal Environment 13th Fed-Ed PKI Meeting 15 June ‘06 Presenter: Tice DeYoung.
Advertisements

FIPS 201 Personal Identity Verification For Federal Employees and Contractors National Institute of Standards and Technology Information Technology Laboratory.
Architecture Decision Group Group Organization & Processes April 7, 2015 | Tuesday.
IT Governance Committee on Research Technology January 11, 2011.
Client/Server Computing Ajay Kumar Shrivastava. Network Operating System (NOS) It manages the services of the server It exists at the session and presentation.
Smart Grid - Cyber Security Small Rural Electric George Gamble Black & Veatch
UNCLASSIFIED 1 Enterprise Architecture Career Path Working Group Walt Okon Senior Architect Engineer Architecture & Infrastructure Directorate Office of.
Shared Technical Architecture’s Role within the ECIO Organization “Arkansas Shared Technical Architecture”
DESIGNING A PUBLIC KEY INFRASTRUCTURE
A.Vandenberg August 7, 2001 HE PKI Summit State of Georgia and PKI Art Vandenberg Director, Advanced Campus Services Information Systems & Technology.
IT PLANNING Enterprise Architecture (EA) & Updates to the Plan.
Enterprise Architecture The Arkansas Approach. Key Areas What is enterprise architecture? Why is it important? How you can participate Current status.
Strategic Planning Framework Programs & Projects ArchitectureRoadmaps Agency Goals & Objectives National Policy and Direction.
Secure System Administration & Certification DITSCAP Manual (Chapter 6) Phase 4 Post Accreditation Stephen I. Khan Ted Chapman University of Tulsa Department.
Considering an Enterprise Architecture for the NSDI
Change Advisory Board COIN v1.ppt Change Advisory Board ITIL COIN June 20, 2007.
NASA Personal Identity Verification (PIV) NASA Personal Identity Verification (PIV) High Level System Overview Tice F. DeYoung, PhD 14th Fed/Ed Workshop.
April 2, 2013 Longitudinal Data system Governance: Status Report Alan Phillips Deputy Director, Fiscal Affairs, Budgeting and IT Illinois Board of Higher.
SWIS Digital Inspections Project (SWIS DIP) Chris Allen, Information Management Branch California Integrated Waste Management Board November 5, 2008 The.
IWCE Conference - Project 25 Compliance Assessment Program and Beyond Wednesday, March 26, 2014 – 4:15-5:30 PM Chris Essid Deputy Director DHS Office of.
Engineering, Operations & Technology | Information TechnologyAPEX | 1 Copyright © 2009 Boeing. All rights reserved. Architecture Concept UG D- DOC UG D-
Thirteenth Lecture Hour 8:30 – 9:20 am, Sunday, September 16 Software Management Disciplines Process Automation (from Part III, Chapter 12 of Royce’ book)
UNCLASSIFIED Joint and Coalition Warfighting Mr. John Vinett March 2012 Technical Baseline Capability.
Developing an accessibility strategy. In this talk we will discuss an accessibility strategy an accessibility policy getting started - steps to consultation.
NASA IT Governance Overview Gary Cox August 18, 2010.
Important acronyms AO = authorizing official ISO = information system owner CA = certification agent.
IT PMB: Executive Oversight and Decision Authority for Application and Infrastructure Projects at NASA Larry Sweet Chair, IT PMB JSC CIO August 2010.
Mandatory Technical Standards Engineering Management Board Goddard Space Flight Center July 10, 2003 Updated October 7, 2003 HQ/Code AE R. Weinstein.
Certification and Accreditation CS Phase-1: Definition Atif Sultanuddin Raja Chawat Raja Chawat.
Relationships July 9, Producers and Consumers SERI - Relationships Session 1.
DRAFT – For Discussion Only HHSC IT Governance Executive Briefing Materials DRAFT April 2013.
7 June 2012 Guidelines for the Compilation of Water Accounts and Statistics Guidelines for the Compilation of Water Accounts and Statistics UN Statistics.
Configuring Directory Certificate Services Lesson 13.
U.S. Department of Agriculture eGovernment Program February 5, 2003 eGovernment Working Group Meeting Chris Niedermayer, USDA eGovernment Executive.
普 华 永 道 Phase 1: Project Preparation Phase 1: Project Preparation Phase Overview Phase Overview.
IT Governance Committee on Education Technology January 13, 2011.
HIT Policy Committee Information Exchange Workgroup NwHIN Conditions for Trusted Exchange Request For Information (RFI) May 18,
IT Governance Steering Committee January 7, 2011.
FEA DRM Management Strategy Presented by : Mary McCaffery, US EPA.
Project Kick-off Meeting Presented By: > > > > Office of the Chief Information Officer.
Cesg-1 CSS Area Report -- Super BOF Background From A. Hooke to CESG: (CSS AD emphasis ) Date: Fri 02 Oct 2009 To: CESG cc: CMC Subject: Proposed.
© 2003 The MITRE Corporation. All rights reserved For Internal MITRE Use Addressing ISO-RTO e-MARC Concerns: Clarifications and Ramifications Response.
Health eDecisions Use Case 2: CDS Guidance Service Strawman of Core Concepts Use Case 2 1.
United States Department of Justice Achieving Information Interoperability and Business Agility The Justice Reference Architecture:
EGovOS Panel Discussion CIO Council Architecture & Infrastructure Committee Subcommittee Co-Chairs March 15, 2004.
Data Science for NIST Big Data Framework Dr. Brand Niemann Director and Senior Data Scientist/Data Journalist Semantic Community
Technical Standards NPR Presented to Technical Standards Working Group June 11, 2007.
Information Security IBK3IBV01 College 2 Paul J. Cornelisse.
Evaluate Phase Pertemuan Matakuliah: A0774/Information Technology Capital Budgeting Tahun: 2009.
25 April Unified Cryptologic Architecture: A Framework for a Service Based Architecture Unified Cryptologic Architecture: A Framework for a Service.
PS -0 System Architecture Working Group RASDS Status 14 June 2006 Peter Shames NASA / JPL
ELECTRONIC SERVICES & TOOLS Strategic Plan
HHS CEA Executive Briefing HHS Enterprise Performance Life Cycle (EPLC) and Program/Project Manager (PM) Certification NIH PM Forum September 12, 2007.
Presented by Eliot Christian, USGS Accessibility, usability, and preservation of government information (Section 207 of the E-Government Act) April 28,
Concepts/ definitions/ meanings of program plan, program scheme, program development, concept paper Program plan is a systematic arrangement of elements.
Quality Assurance and Risk Management Services, Inc. 
International Planetary Data Alliance Registry Project Update September 16, 2011.
Software Reviews Ashima Wadhwa.
Shared Technical Architecture’s Role within the ECIO Organization
Safeguards- Feedback on Safeguards ED-2 and Task Force Proposals
Enterprise Content Management Owners Representative Contract Approval
The Open Group Architecture Framework (TOGAF)
Engineering Processes
Group Meeting Ming Hong Tsai Date :
Vijay Rachamadugu and David Snyder September 7, 2006
, editor October 8, 2011 DRAFT-D
Item 7.11 SDMX Progress report
Security Policies and Implementation Issues
(Project) SIGN OFF PROCESS MONTH DAY, YEAR
Alignment of Part 4B with ISAE 3000
Presentation transcript:

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 , Managing Information Technology, states: –NASA organizations and NASA contractors, for which a standard and/or architecture apply (see paragraph 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 , 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

From April 25, 2007 SMC Briefing 10

From April 25, 2007 SMC Briefing 11

From April 25, 2007 SMC Briefing 12

From April 25, 2007 SMC Briefing 13

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

Backup

16 EA Review Inclusion Flow Source: NPR

17 NASA IT Standards Snapshot IT Standard IDTitleDate Viewable in NASA Technical Standards System?* NASA-STD-2801 NASA STRATEGY FOR WINDOWS NT DOMAIN 5/1/1997No NASA-STD-2802INTRACENTER NETWORKING ARCHITECTURE STANDARDS AND PRODUCTS 5/1/1997No NASA-STD-2803INTRANET STRATEGY5/1/1997No NASA-STD-2804MINIMUM INTEROPERABILITY SOFTWARE SUITE 7/11/2006Yes NASA-STD-2805MIIMUM HARDWARE CONFIGURATIONS 7/11/2006Yes NASA-STD-2806NETWORK PROTOCOL10/23/1995No NASA-STD-2804 and 2805 have been recently updated and will be posted soon

18 NASA IT Standards Snapshot IT Standard IDTitleDate Viewable in NASA Technical Standards System?* NASA-STD-2807THE NASA DIRECTORY SERVICE - ARCHITECTURE, STANDARDS, AND PRODUCTS (SUPERSEDING NASA-STD-2807B) 9/6/2001No NASA-STD-2808INTEROPERABILITY PROFILE FOR NASA CLIENTS 1/23/1998No NASA-STD-2810UNIX INTEROPRABILITY 4/28/1997No NASA-STD-2811STANDARD WORKSTATION MANAGEMENT TOOLS 4/28/1997No

19 NASA IT Standards Snapshot IT Standard IDTitleDate Viewable in NASA Technical Standards System?* NASA-STD-2812INTRANET FUNCTIONAL REQUIREMENTS 5/12/1997No NASA-STD-2813NASA FIREWALL STRATEGY, ARCHITECTURE, STANDARDS AND PRODUCTS 5/12/1997Yes NASA-STD-2814NASA INTEGRATED INFORMATION TECHNOLOGY ARCHITECTURE TECHNICAL FRAMEWORK TECHNICAL ARCHITECTURE VOL 1-2 (SUPERSEDING NASA-STD-2814) 6/27/2000No NASA-STD-2815NASA ELECTRONIC MESSAGING ARCHITECTURE, STANDARDS AND PRODUCTS 8/31/1998No

20 NASA IT Standards Snapshot IT Standard IDTitleDate Viewable in NASA Technical Standards System?* NASA-STD-2817COMPUTER-AIDED ENGINEERING, DESIGN AND MANUFACTURING DATA INTERCHANGE STANDARDS 9/15/1998No NASA-STD-2818DIGITAL TELEVISION STANDARDS FOR NASA 4/4/2000No NASA-STD-2819COLLABORATIVE TOOLS STANDARD 1/4/2000No NASA-STD-2820ENCRYPTION AND DIGITAL SIGNATURE STANDARDS 7/29/2001Yes A new version of NASA-STD-2819 is nearing completion

21 Policy-Rooted Standards Process Develop New GuidanceRetire Outdated Guidance

22 Mapping Standards/EA/Policy to NPR 2800 NPD 2800.a (IT Planning)NPD 2800.b (IM)NPD 2800.c (Infrastructure) CPICNPD 2220 (STI)End User Devices NPR 2200 (STI)NASA-STD-2804 NASA-STD-2805 NASA-STD-2810 (Unix) NASA-STD-2811 (Mgmnt Tools) EANPD 1440 Rec MgmntData Centers Service Reference ModelNPR 1441 Rec MgmntNASA-STD-2814a (Vol 1 Technical Reference Model NASA-STD-2830 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