Leveraging ET'gov for Collaboration

1
Leveraging ET.govfor Collaboration

• Owen Ambur, Project Manager
• CIO Councils ET.gov Site/Process
• September 20, 2005

2
Topics

• Conception
• Authority
• Leadership
• Purpose
• Status
• Relationships
• Demo

3
Conception

• Co-Chairs of CIO Councils Architecture
  Infrastructure Committee (AIC)
• John Gilligan, USAF CIO
• Norm Lorenz, OMB CTO
• Charged the ET Subcommittee to
• Develop a process whereby the emerging technology
  life-cycle can be better managed on a
  governmentwide basis
• Norm said
• We cant deal with all of the vendors coming at
  us with intergalactic solutions

4
Authority
Chief Information Officers (CIO)
Council Architecture and Infrastructure Committee
(AIC) FY 2005 Tasks (FY 2005 Spend Plan)

• Task 6. Develop identification and validation
  processes for emerging technologies.
• Description/Justification - The Emerging
  Technology Subcommittee of the CIO Councils
  Architecture and Infrastructure Committee is
  charged with examining crosscutting emerging
  technology components and developing
  recommendations for their use in the Government.
  This task will focus on defining a process that
  will allow the IT innovation lifecycle to be
  managed on a Government-wide basis that
  accelerates the discovery, validation, and
  maturation of components that improve performance
  and the delivery of services to citizens.
• A relationship between the overall proposed
  process and CORE.gov is envisioned, along with
  the ability to accept submissions from the
  vendor/integrator community. While CORE.gov will
  focus on submissions from the Government
  community, there is value in having a process
  through which a component would graduate to
  CORE.gov once a sufficient level of subscription
  and commitment to the component exists within the
  Government community.
• Lead Staff John McManus, Susan Turnbull, and
  Owen Ambur

5
Current Leadership

• CIOC AIC Co-Chairs
• Kim Nelson, CIO, EPA
• Reynolds Cahoon, CIO, NARA
• ET Subcommittee Co-Chairs
• John McManus, DCIO CTO, NASA
• Susan Turnbull, GSA

6
Purpose

• To enable
• Identification Discovery of ET Components
• By anyone
• Regardless of whether component exists yet or not
• Formation, Identification Discovery of CoPs
• By .gov folks with business expertise
• In partnership with .com, .edu .org technical
  experts
• Potential Direction of Additional Resources
• By CIOC leaders
• Based upon need, interest priorities
• Demonstration of Practical Viability Utility
• By ET CoPs
• Through proofs-of-concept, pilots, etc.
• Delivery of Proven Components for Consideration
• By Components Subcommittee /or
• Governance Subcommittee

7
Home Page
8
Identify a Component
9
Register a Component
10
Status

• Demoed March 30, 2005, at GovCon05
• First component registered April 14
• Strategy Markup Language (StratML)
• About 20 registered as of August
• PDF by Adobe
• X-UDED by Urban Institute/NASACT
• Three ET CoPs at Stage 2
• XML NDRG, X-UDED NIST Tools

11
Search Components
12
Relationships

• ET CoPs can use any collaborative tools they
  choose, such as
• CORE.gov
• http//gsa.gov/collaborate
• Components graduating from Stage 4 become
  candidates for
• Inclusion in CORE.gov by Components Subcommittee,
  or
• Consideration by the Governance Subcommittee
• Channel for input into CIOCs FEA model
  maintenance process for SRM TRM
• http//et.gov/pagehelp.aspxservicetype
• http//et.gov/pagehelp.aspxtechnicalstandard

13
SRM Components
14
TRM Components
15
Questions

• http//et.gov/help.aspx
• Owen_Ambur_at_ios.doi.gov
• Project Manager, ET.gov