continue --

24
1 Enterprise Architecture Driven E-Government with XML Web Services: Open Collaboration with Open Standards Open Standards/Open Source for Federal and State eGovernment Programs Conference, George Washington University Susan Turnbull, GSA, Chair, Universal Access http://ioa-qpnet-co.gsa.gov/UA-Exp Brand Niemann, EPA, Chair, Web Services Work Group http://web-services.gov March 17-19, 2003

Upload: aamir97

Post on 14-Dec-2014

387 views

Category:

Technology


3 download

DESCRIPTION

 

TRANSCRIPT

Page 1: continue --

1

Enterprise Architecture Driven E-Government with XML Web Services: Open Collaboration with Open Standards

Open Standards/Open Source for Federal and State eGovernment Programs Conference,

George Washington UniversitySusan Turnbull, GSA, Chair, Universal Access

http://ioa-qpnet-co.gsa.gov/UA-ExpBrand Niemann, EPA, Chair, Web Services Work Group

http://web-services.govMarch 17-19, 2003

Page 2: continue --

2

Overview• The joint theme for the March Universal Access

Collaboration Workshop and the XML Web Services Work Group meeting, "Enterprise Architecture Driven E-Government with XML Web Services: Open Collaboration with Open Standards" was prepared as a conference track within the "Open Standards/Source for Federal and State eGovernment Programs" Conference at George Washington University on March 17-19. This EA/XML Web Services conference track includes seven pilots of the XML Web Services WG of the Emerging Technologies Subcommittee for the CIO Council Architecture and Infrastructure’s Governance and Components Subcommittees and the Federal Enterprise Architecture’s (FEA) Data and Information Reference Model (DRM).

• Dates for future Collaboration Expedition Workshop and XML Web Services Work Working Group meetings at the National Science Foundation are: April 15, May 14, and June 17.

Page 3: continue --

3

Presidential Memo on the Importance of E-Government, July 10,2002

• Three principles:– Citizen-centered.– Results oriented.– Market-based.

• Five Government-wide reform goals:– Strategic management of human capital.– Budget and performance integration.– Competitive sourcing.– Expanded use of the Internet and computer resources

(E-Government).– Improved financial management.

Page 4: continue --

4

Presidential Memo on the Importance of E-Government, July 10,2002

• “Our success depends on agencies working as a team across traditional boundaries to better serve the American people, focusing on citizens rather than individual agency needs. I thank agencies who have actively engaged in cross-agency teamwork, using E-Government to create more cost-effective and efficient ways to serve citizens, and I urge others to follow their lead.”

Page 5: continue --

5

Briefing for Web-Enabled E-Gov Conference, Bob Haycock, Acting Manager, FEA-PMO, February 10, 2003

• The Federal Government has a multi-billion dollar consolidation opportunity:– Citizen Centered: Consolidation and Migration to the 24 E-

Government Initiatives.– Lines of Business: Overlap and Leverage Assessment on IT

Spending for Common Functions (focus on 6):• Financial Management.• Human Resources.• Data and Statistics Development.• Public Health Information.• Criminal Investigations.• Monetary Benefits.

– Office Automation and Infrastructure: Leveraging Enterprise Licensing and Buying at Commercial Benchmarks or Less.

• This is being “operationalized” in the CIO Council’s Architecture and Infrastructure Committee (AIC).

Page 6: continue --

6

The CIO Council’s Architecture and Infrastructure Committee

• Leadership:– John Gilligan, USAF CIO, Co-Chair– Laura Callahan, Department of Homeland Security, Deputy CIO, Co-

Chair– Norman Lorentz, OMB CTO, Advisor

• Subcommittees:– Governance:

• Provide policy guidance, advice, and assistance in the definition, design, and implementation of the Enterprise Architecture discipline and practice throughout the Federal Government.

– Robert Haycock, OMB, and John Przysucha, DOE

– Components:• Foster the identification, maturation, and use and reuse of Component-

Based Architectures and Architecture Components in the Federal Government.

– Reynolds Cahoon, NARA, and Robert Haycock, OMB.

– EmergingTechnology:• Identify technologies with the potential to improve the value and quality of

the FEA.– Dawn Meyerriecks, CTO, DISA, and Mark Day, EPA, DCIO.

Page 7: continue --

7

Mapping the Federal Enterprise Architecture Into the CIOC/AIC

• FEA:– Performance Reference

Model (PRM)– Business Reference Model

(BRM).– Service Component

Reference Model (SRM).– Technical Reference Model

(TRM).– Data and Information

Reference Model (DRM).– Solution Architects Working

Group (SAWG).

• AIC Subcommittees:– Governance.

– Governance.

– Components.

– Components.

– Components.

– Components.

Page 8: continue --

8

Emerging Technology Working Groups

• Working Groups:– Public Key Encryption (PKI):

• Judith Spencer, GSA.– XML

• Owen Ambur, DOI/FWS, and Marion Royal, GSA.– Universal Access

• Susan Turnbull, GSA.– XML Web Services.

• Brand Niemann, EPA.

• Relationship to Other Subcommittees:– The Governance and Components Subcommittee will

request (procure) and the Emerging Technology Subcommittee will suggest (pilot).

Page 9: continue --

9

Some Emerging Technology Subcommittee Principles

• Open Collaboration with Open Standards:– Open up communication circles among

diverse stakeholders.– Include University and federal laboratory

researchers.– Accelerate commitments and maturation of

open standard components for e-government.– Collaborative “incubator” process.

Page 10: continue --

10

Transforming How We Work Together To Better Serve the Public

Federal Enterprise Architecture

Model to"Connect the Dots"

CIOC Incubator workshops for faster formation of Communities

of Interest and shared development processes to

leverage technology using open collaboration and open standards technologies

Public Health Gov Benefits

SafecomDisaster Management

Transforming How We Work Together to Better Serve the Public

FEAPMO.govFederal

Enterprise Architecture

(EA)

2.What do we need next? Business lines integrated by Communities of Interest

through pilots that result in credible agreements on sharable business sub-

function components

3. Outcome: Public experiences safe

and sound interactions with seamless government.

characterized by transparency and accountability

Achieve credible agreements on

component architecture for business sub-

functions through "proof of concept"

pilots using innovative

technologies

Business Line and Business Components

Inventory

Anticipating the development of global and nationally adopted intergovernmental components by Communities of Interest formed to support

EA governance and business subfunction needs of the Architecture and Infrastructure Committee, Chief Information Officers Council (CIOC)

1. Today, egov payoff accelerates only

when business sub-function components are tuned up,

collaboratively, by Communities of Interest (being formed now)

stove-piped institutions lack credible commitments and processes to work together

Page 11: continue --

11

Collaboration Expedition Workshop Series #22:Potential and Realities for Emerging Discovery

Processes, March 4, 2003• 8:45 a.m. - Welcome and Introductions:

– Susan Turnbull, GSA, Chair, Universal Access WG.– Brand Niemann, EPA, Chair, XMLWeb Services WG.

• 9-9:45 a.m. - Online rulemaking: a Step toward E-governance, Robert D. Carlitz and  Rosemary W. Gunn, Information Renaissance.

– Dialogue 9:45-10:15 a.m.• 10:15-11 a.m. - How can we Build a Distributed Intelligence Information

Infrastructure to Leverage Synergies between Local Government Asset Accountability (Government Accounting Standards Board 34) and National Response Capability?, Bruce Cahan, President, Urban Logic.

– Dialogue 11-11:30 a.m.• 11:30-12:15 p.m. -The Promise of Ontology-based Knowledge Technologies

for Enabling Citizens: An Exploration with Scenario-based "Capability Cases“, Ralph Hodgson, Co-founder and Executive Partner, TopQuadrant, Inc.

• Dialogue 12:15-12:45 p.m.• 12:45-1:15 p.m. - Who is Here? Who is Missing?• 1:15-2 p.m. - Lunch and Networking.• 2-5 p.m. - XML Web Services Working Group Meeting

Page 12: continue --

12

XML Web Services Working GroupMarch 4, 2003

• 1. Introduction:– Updates and Announcements.– Some Coming Attractions.

• 2. Business:– “Distributed Components, Metadata Models, and Registries”, ListServ Discussion

Summary, Joe Chiusano, Booz Allen Hamilton.– "Eforms for E-Gov Pilot", Rick Rogers, Fenestra, Team Lead, Charter.– “Topic Maps for the FEA”, Michel Biezunski, Coolheads Consulting, Proposed

Pilot, Cognitive Topic Map Web Sites (CTW): Aggregating Information Across Individual Agencies and E-Gov Initiatives.

• 3. Presentations:– Organizations - IRS Topic Map Pilot, David Brown, IRS, and IRS Integrated

Navigation System, Michel Biezunski, Coolheads Consulting.– Education/Analysts - The Business Case for XML Web Services - Scott

Christiansen, Seattle Pacific University and Boeing Company (via telephone).– "Eforms for E-Gov" Pilot Team, The eGrants SF 424 XML Schema in the XML

Collaborator, Kevin Williams, Blue Oxide Technologies.– Pilots/Priorities: XML Data Exchange Across Multiple Levels of Government

Using Native XML Databases (Tamino 4.1 with UDDI and WebDAV Server), Joel Patterson, SoftwareAG.

Page 13: continue --

13

Upcoming Meetings

• April 15, 2003, in conjunction with the Universal Access Collaboration Workshop #23 at the National Science Foundation (Ballston, VA Orange Line Metro Station). Agenda in process. Digital Talking Books, VoiceXML, and Taxonomies.

• May 5-7, 2003, FedWeb Spring 03, Tutorial: Using the Generalized Instrument Design System (GIDS-XML Standards-based Forms), the XML Collaborator, and the MetaMatrix System to Build E-Gov Projects and Session: "Eforms for E-Gov" Pilot Project.

• May 14, 2003, in conjunction with the Universal Access Collaboration Workshop #24 at the National Science Foundation (Ballston, VA Orange Line Metro Station). Agenda in process.

Page 14: continue --

14

Agenda-Morning• Monday, March 17th:

– 1. 8:30 a.m. Susan Turnbull, GSA, and Brand Niemann, EPA: Introductions and Overview.

– 2. 9:00 a.m. Tod Jackson and Steve Wheat, Enterprise Architects for Administrative IT at the University of Illinois and Co-Founders of the OpenEAI Software Foundation: The OpenEAI Project - Open Source Enterprise Application Integration Software and Methodology.

– 3. 9:45 a.m. John Rehberger, USDA, Managing EAMS As An Open Source Project.

– 4. 10:30 a.m. Farrukh Najmi, SUN Microsystems, and Joseph Potvin, Public Works And Government Services Canada, An Open Source ebXML Registry For eGov.

– 11:15-11:45 a.m. Break– 5. 11:45 a.m. Joseph Chiusano, Booz Allen Hamilton: Web

Services Security and More: The Global XML Web Services Architecture (GXA).

– 12:30-2:00 p.m. Lunch

Page 15: continue --

15

Agenda-Afternoon• Monday March 17th (continued):

– 6. 2:00 p.m. Robert Haycock, Office of Management and Budget's Federal Enterprise Architecture Program Management Office: The Federal Enterprise Architecture (FEA) - An Overview of Vision and Progress.

– 7. 2:45 p.m. Rick Rogers, Fenestra: E-Forms for e-Gov: The Use of XML Standards-based Applications.*

– 3:30-4:00 p.m. Break– 8. 4:00 p.m. Kevin William, Blue Oxide Technologies: The XML

Collaborator-Industry Standards Interoperability and Applicability to E-Gov Initiatives.*

– 9. 4:45 p.m. Michael Lang and Ed Falkner, MetaMatrix: The MetaMatrix System for Model-driven Integration with Enterprise Metadata.*

– 10. 5:30 p.m. Michel Biezunski, Coolheads Consulting: Cognitive Topic Map Web Sites-Aggregating Information Across Individual Agencies and E-Gov Initiatives.*

*Formal pilots of the XML Web Services Working Group for the Governance and Components Subcommittees and the Data Reference Model (DRM).

Page 16: continue --

16

Agenda-Tomorrow Morning• Tuesday, March 18th:

– 11. 9:00 a.m. Jeff Harrison, Open GIS Consortium: Open Web Services Demonstration and Geospatial One-Stop Portal E-Gov Initiative.

– 12. 9:45 a.m. Sam Hunting, eTopicality, Inc.: Goose 1.0: The Open Source, RESTful Topic Map Server.

– 13. 11:00 a.m. Brian Behlendorf and Michael Kochanik, CollabNet, Collaboration and CoSourcing: Designing Intergovernmental Services and Sharable Components.

– 14. 11:45 a.m. Brian Behlendorf, The Apache Experience.

– 15. 4:45 p.m. Ralph Hodgson, TopQuadrant, Inc., The Potential of Semantic Technologies for E-Gov.

Page 17: continue --

17

Joint Governance, Components & Emerging Technology Subcommittees Pilot Projects

Purpose of XSD

Pilot Tool Description Status Subcommittees/Pilots

Data Collection and Validation

GIDS(Generaliz-ed Instrument Design System)

XML Standards- based electronic and paper forms.

Launched by Census Bureau in January 2003.

Components (DRM)/”Eforms for E-Gov”

Web Services XML Collaborator

Collaborative design and registry platform.

To be launched in February 2003.

Components (DRM) )/”Eforms for E-Gov” and Others

Information Integration

MetaMatrix System and XML Collaborator

Model-driven integration with enterprise metadata.

Latest version supports both OMG and W3C standards.

Components (DRM) /”Distributed Registries and Metadata Models”

Page 18: continue --

18

Joint Governance, Components & Emerging Technology Subcommittees Pilot Projects (continued)

Purpose of XSD

Pilot Tool Description Status Subcommittees/

Pilots

Information Aggregation

Cognitive Topic Map Web Sites (CTW)

Using the BRM to aggregate information across individual agencies & E-Gov Initiatives.

ISO/IEC13250 Standard 2000-2002.

Governance and Components (DRM)/”Topic Maps for the FEA”

Semantic Integration

An Open Standard Ontology Tool and Platform

Web services to provide agencies with semantic access to reusable capabilities to support the eGOV initiatives.

Semantic standards (RDF, RDFS, OWL)

Governance /Semantic FEA Capabilities Advisor

Intergovernmental Services and Sharable Components

SourceCast Host GIDS and other reusable E-Gov Components

Canadian Government, DISA, etc.

Components (DRM) /”Distributed Components

Page 19: continue --

19

Example of Components*: Eforms• Components

Subcommittee Process:– Target Agency Pilot.– Provide Incentive.– Create Sharable Item.– Involve Industry.

• XML Web Services WG “Eforms for E-Gov” Pilot:– Census’s GIDS.– Cost Savings.– Open Source.– Vendor Support for

Open Standards (XSD, XForms, and SVG)

*An Enterprise Architecture Component is a self-contained business processor service with predetermined functionality that may be exposed through abusiness or technology interface.

Page 20: continue --

20

Example of Components*: Eforms

• Components Subcommittee Process:– Identification.– Classification.– Standardization.– Publication.– Utilization.

• XML Web Services WG “Eforms for E-Gov” Pilot:– eGrants SF424.– eGrants(BRM & XNS).– XML Schema.– XML Collaborator.– XML Web Service.

*An Enterprise Architecture Component is a self-contained business processor service with predetermined functionality that may be exposed through abusiness or technology interface.

Page 21: continue --

21

Example of Components: Federation (loosely coupled)

• Granularity:– Components– Metadata Models

– Registries

• Examples:– Eforms (e.g. eGrants)– Data Elements and

XML Schema (e.g. DOD ISO 11179 Registries)

– ebXML (e.g. GSA-NIST XML Registry)

E.g. Subcomponent of XML Schema to E-Gov Portal (e.g. Geospatial One-Stop) to Complete Line of Business (e.g. Data and Statistics Development, Health Informatics, etc.).

E.g. The XML Collaborator Pilot is federating components, metadata models, and registries by supporting XML, ebXML, and UDDI standards.

Page 22: continue --

22

Agenda-Morning• Monday, March 17th:

– 1. 8:30 a.m. Susan Turnbull, GSA, and Brand Niemann, EPA: Introductions and Overview.

– 2. 9:00 a.m. Tod Jackson and Steve Wheat, Enterprise Architects for Administrative IT at the University of Illinois and Co-Founders of the OpenEAI Software Foundation: The OpenEAI Project - Open Source Enterprise Application Integration Software and Methodology.

– 3. 9:45 a.m. John Rehberger, USDA, Managing EAMS As An Open Source Project.

– 4. 10:30 a.m. Farrukh Najmi, SUN Microsystems, and Joseph Potvin, Public Works And Government Services Canada, An Open Source ebXML Registry For eGov.

– 11:15-11:45 a.m. Break– 5. 11:45 a.m. Joseph Chiusano, Booz Allen Hamilton: Web

Services Security and More: The Global XML Web Services Architecture (GXA).

– 12:30-2:00 p.m. Lunch

Page 23: continue --

23

Agenda-Afternoon• Monday March 17th (continued):

– 6. 2:00 p.m. Robert Haycock, Office of Management and Budget's Federal Enterprise Architecture Program Management Office: The Federal Enterprise Architecture (FEA) - An Overview of Vision and Progress.

– 7. 2:45 p.m. Rick Rogers, Fenestra: E-Forms for e-Gov: The Use of XML Standards-based Applications.*

– 3:30-4:00 p.m. Break– 8. 4:00 p.m. Kevin William, Blue Oxide Technologies: The XML

Collaborator-Industry Standards Interoperability and Applicability to E-Gov Initiatives.*

– 9. 4:45 p.m. Michael Lang and Ed Falkner, MetaMatrix: The MetaMatrix System for Model-driven Integration with Enterprise Metadata.*

– 10. 5:30 p.m. Michel Biezunski, Coolheads Consulting: Cognitive Topic Map Web Sites-Aggregating Information Across Individual Agencies and E-Gov Initiatives.*

*Formal pilots of the XML Web Services Working Group for the Governance and Components Subcommittees and the Data Reference Model (DRM).

Page 24: continue --

24

Agenda-Tomorrow Morning• Tuesday, March 18th:

– 11. 9:00 a.m. Jeff Harrison, Open GIS Consortium: Open Web Services Demonstration and Geospatial One-Stop Portal E-Gov Initiative.*

– 12. 9:45 a.m. Sam Hunting, eTopicality, Inc.: Goose 1.0: The Open Source, RESTful Topic Map Server.

– 13. 11:00 a.m. Brian Behlendorf and Michael Kochanik, CollabNet, Collaboration and CoSourcing: Designing Intergovernmental Services and Sharable Components.*

– 14. 11:45 a.m. Brian Behlendorf, The Apache Experience.

– 15. 4:45 p.m. Ralph Hodgson, TopQuadrant, Inc., The Potential of Semantic Technologies for E-Gov.*

*Formal pilots of the XML Web Services Working Group for the Governance and Components Subcommittees and the Data Reference Model (DRM).