1 / 18

Tuning Emerging Technologies…Making Them Play Together: From Stovepipes to Wind Chimes!

Tuning Emerging Technologies…Making Them Play Together: From Stovepipes to Wind Chimes!. Jim Disbrow, Project Manager Susan Turnbull, Co-Chair, ET Subcommittee Richard Spivack, Co-Chair, ET Subcommittee Owen Ambur, Former Project Manager Blue Sky Forum, Department of Energy October 24, 2007.

martha
Télécharger la présentation

Tuning Emerging Technologies…Making Them Play Together: From Stovepipes to Wind Chimes!

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. Tuning Emerging Technologies…Making Them Play Together: From Stovepipes to Wind Chimes! Jim Disbrow, Project Manager Susan Turnbull, Co-Chair, ET Subcommittee Richard Spivack, Co-Chair, ET Subcommittee Owen Ambur, Former Project Manager Blue Sky Forum, Department of Energy October 24, 2007

  2. CIOC Emerging Technology Life-Cycle Management Process • Overview • Authority • FY08 Activities • Benefits • Discussion

  3. Emerging Technology Subcommittee, Architecture and Infrastructure Committee, CIO Council • Tuning ET Together - From Stovepipes to Wind Chimes • Purpose: An “incubator” organizing process to accelerate discovery, maturation, and validation of capabilities that leverage FEA principles and priorities. The key components of charter : • Greater foresight and discernment as established and emerging technologies compete and converge • Longer life-cycles through market-based, open standards technologies • Common understanding of business scenarios to anticipate performance outcomes and mitigate risks. • Improve strategic foresight and collaboration capacity around strategic IT assets. • Key FY08 Activities • Conduct ET Life-cycle process http://ET.gov • Conduct Collaborative Expedition Workshops with GSA and Subcommittee on Networking for IT Research and Development ET SC Co-chairs

  4. CIOC ET Life-Cycle Management: ET.gov FY05 CIOC - Develop identification and validation processes for emerging technologies • Examine crosscutting emerging technology components and develop recommendations for government use • Governmentwide IT innovation lifecycle management process to accelerate discovery, validation, and maturation of components • Accept submissions from vendor/integrators • Approved components in governmentwide repository: CORE.gov FY07-09 CIOC Strategic Plan • Interoperable IT solutions, identified and used efficiently and effectively across the Federal Government. Goal 3 • Continue to develop more efficient and effectivemethods for sharing information on emerging technologies. Obj. 9 • Continue to implement & refine life-cycle management process and website (ET.gov) to enable the identification and discovery of emerging technology components and specifications, via full-text searching as well as mappings to the FEA Service Component Reference Model (SRM) and Technical Reference Model (TRM). Major Activity • History, Principles and Authority

  5. Key FY08 Activities • Conduct http://ET.gov • Purpose: “Continue to develop more efficient and effective methods for sharing information on emerging technologies.” CIOC Strategic Plan • ET.gov stages: • 1. Identification:anyone registers ET component using XML schema >80 • 2. Subscription:community forms around high potential component 14 • 3. Stewardship:community recognized by ET SC (i.e. IPv6, StratML)) 5 • 4. Graduation:component recognized by Services SC for inclusion in CORE.gov 2 • Key FY08 Actions • Explore partnering with other federal settings involved in technology evaluation and transfer • Conduct Collaborative Expedition workshops to support networking among ET communities Contact Information

  6. Key FY08 Activities • 2. Conduct Collaborative Expedition Workshops • Purpose: Monthly open workshops to encourage collaboration among government and community implementers of IT and to demonstrate promising capabilities emerging from IT research that aligns with FEA principles • “Facilitate strategic dialogue among communities of interest. Through the Expedition Workshops, sponsored by AIC, interested participants experience and learn about new opportunities to adhere to sound architectural principles and implement shared, service-oriented solutions.” from CIOC Strategic Plan • Leadership in virtual collaboration (i.e. Data Reference Model, Geospatial Profile) • Key FY08 Activities/Deliverables • Organize around business scenarios from ET.gov & IT R&D communities that address CIOC Strategic Plan and Architecture Principles for the US Government. • Organize around CIO requests. ET SC co-chairs SEW CG co-chairs

  7. Key FY08 Activities – Graduation to Services SC • 3. Strategy Markup Language - StratML • Purpose: To facilitate collaboration around shared missions and reduce the number of duplicative performance metrics • XML vocabulary and schema Federal agency strategic plans and potential for performance plans, and performance reports all aligned with FEA • More than 50 Federal strategic plans rendered in StratML • Support strategic alignment among partners and maintain currency readily • 4. IPv6 • Purpose: To provide leadership and coordination in the adoption of IPv6 • Explore business scenarios to anticipate performance outcomes and mitigate risks. • Key FY08 Actions • Establish agreement with Services SC for ET components graduating to CORE.gov • Explore interest in StratML from science & IT R&D agencies StratML IPv6 XML CoP

  8. ET.gov Enables…. • Identification & Discoveryof 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 • Collaboration to Assess Viability & Utility • By ET CoPs • Through proofs-of-concept, pilots • Delivery of Proven Components • For Consideration By Services Subcommittee & Governance Subcommittee, Agencies, LOBs & eGov Projects

  9. ET.gov - Built to SharePotential Innovation Partnerships • IC Vendorpedia • Followup to 9/13/06 conversation with Gen. Meyerrose (Ambur) • 8/16/07 telecon with DNI/OCIO staff (Turnbull & Ambur) • DHS IT Products & Services Database • IPV6 WG inspired enhancements • Other agencies/systems? National Labs?

  10. Home Page

  11. Identify a Component

  12. SRM Components

  13. TRM Specifications

  14. Register a Component

  15. Search Components

  16. Enhanced Search Prototype

  17. Questions? http://et.gov/help.aspx JIM.DISBROW@eia.doe.gov Project Manager

  18. ET.gov Additional Background • 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 Services Subcommittee, or • Consideration by the Governance Subcommittee • Relatively low-risk usage by agencies • Channel for input into CIOC’s FEA model maintenance process for SRM & TRM: • http://et.gov/pagehelp.aspx#servicetype • http://et.gov/pagehelp.aspx#technicalstandard

More Related