1

Gov 2.0: Business Transformation for EPA Enterprise Architecture

Implemented in Web 2.0 Wikis

Brand NiemannSenior Enterprise Architect

Enterprise Architecture TeamU.S. Environmental Protection Agency

April 25, 2008

2

Gov 2.0 Business Transformation

Transform Before After Activity (Wiki)

EPA EA Multiple Silos (1)

Web 2.0 Wiki (2)

Inventory & Refresh

OMB FEA Paper Documents & CD-ROMs

Web 2.0 Wiki (2)

Submission & Assessment

Transition Briefing Books and Slides

Web 2.0 Wiki (2)

Harvard Seminar (3) Wiki

3

Gov 2.0 Business Transformation

• Three Objectives:– (1) Transform the way we do EPA Enterprise Architecture (EA).– (2) Transform the way we deliver the EPA EA to the

OMB/Federal Enterprise Architecture Program Management Office (FEA PMO) and to our partners.

– (3) Transform the way we communicate the EPA EA to the Transition Team.

• Footnotes:– (1) Email, Share drive, QuickPlace, Intranet Web Site, WebArt,

etc.– (2) An Application Integration Platform and an Application

Development Platform. Also a DRM 2.0 - compliant data architecture & implementation.

– (3) In support of Leadership and Strategic Management for Chief Information Officers, June 16-18, 2008, John F. Kennedy School of Government, Harvard University, Cambridge, MA.

4

Overview

• 1. FedTech Interview: February 2008• 2. Google Searches for EPA and EPA Enterprise

Architecture• 3. EPA’s Internal Dialogue on Access to

Environmental Information• 4. Business Transformation for EPA Enterprise

Architecture• 5. Inventory and Refresh• 6. Evolving Solution• 7. List of Presentations and Web 2.0 Wikis

5

1. FedTech Interview: February 2008

• FedTech Editor in Chief Lee Copeland spoke with O’Neill about her goals and initiatives:– One of Molly O’Neill’s top priorities is making government more

collaborative and more responsive to the public, so she’s looking at how Web 2.0 technologies can help. If government agencies don’t learn to use these tools, she says, “we’re going to be left behind; we’re going to be on Page 18 of the search engines.” In the coming months, O’Neill hopes to improve access to data — both for the public and for internal users — and to lead the Environmental Protection Agency toward delivering more services that the public wants. And she’s planning to ask the taxpayers what they want and need through a national dialogue.

6

1. FedTech Interview: February 2008

• FedTech Editor in Chief Lee Copeland spoke with O’Neill about her goals and initiatives:– FedTech: In terms of enterprise architecture, what are you looking for?

Someone with a lot of network infrastructure expertise? What things were especially important to you?

– O’Neill: Specifically, people who can work with other people in the EPA to understand and plan out their systems and relate it to how it fits into the enterprise architecture — actually, the customer service piece of that. A lot of federal agencies, and the EPA is no different, do really well with writing plans for what enterprise architecture looks for, but equating that down to a business level is where we sometimes struggle, so talking the language of IT enterprise architecture at a business level is a real skill. Does that make sense to you?

– FedTech: Yes, it does, because you have a lot of big ambitious plans, but you need someone who can talk to different folks in the business unit and understand their practical needs and then bring that knowledge into something that’s operational.

– O’Neill: Right!

7

2. Google Search: EPA

8

2. Google Search:EPA Enterprise Architecture

9

3. EPA’s Internal Dialogue on Access to Environmental Information

https://nationaldialogue.epa.gov/blog/

10

3. The National Dialogue Jam Session: Categories

• Challenges: What Has to Change?• Content: What information do customers want?• Customers: Who should we serve better?• Guest Bloggers: See Slides 12-15• Partners: Who can help us work better?• Road Map: How Do We Get There?• Site Information: Employees are invited to use this site to identify and share

their best resources, tools, and ideas for improving access to EPA’s environmental information.

• Technical Feedback: Blog or Website• Trends: What Are the Trends and Drivers for Information Access?• Uncategorized: Photos from RTP Jam Session on Thursday April 3, 2008• Vision: Where Do We Want to Go?• What Works: What Is Working for EPA and Others?• What's Hot: What We Learned

Note: These categories worked for the National Dialogue but not for organizing EPA content!

11

3. The National Dialogue Jam Session: What We Learned

• People had mixed opinions about what OEI’s number one information management priority should be for the next 2 to 3 years:– Improving internal data and resource sharing: 27%– Helping people find what they want on EPA’s site:

20%– Making EPA’s data downloadable and usable: 13%– Explaining what the information means: 13% – Using new technologies for collaboration: 13%– Other: 14%

Note: Over the course of three days they received over 300 comments from more than 100 people.

12

3. The National Dialogue Jam Session: What We Learned

• Individual Comments (excerpts):– Learning makes me happy…..:

• April 4th, 2008 by Molly O'Neill– We need to evaluate some of these new Web 2.0 tools (in this

case blogging) for usability on collaborative efforts. And, we need experience in how to manage the content.

– Changing the Course:• April 4th, 2008 by Jerry Johnston

– I would like to turn the tables on this discussion a bit and ask people to think about how we might take advantage of these same technologies to help us make improvements in the many datasets we hold and make available. And the best news is that many of the most important advancements might come without an additional price tag – we can achieve a lot through simple changes to what we are already doing.

13

3. The National Dialogue Jam Session: What We Learned

• Individual Comments (excerpts):– Machines and People:

• April 4th, 2008 by Mike Flynn– Wow, I’m impressed with all the great comments! I’m

pleased to see folks identify the public as the top group we need to better serve. Sometimes I think we forget that we are public servants.

– Many of our folks across the Agency play a critical role in “connecting the dots” and help people get to and understand the information and tools they need. What are your thoughts about the EPA information corps for the future?

14

3. The National Dialogue Jam Session: What We Learned

• Individual Comments (excerpts):– Demand vs. Supply:

• April 4th, 2008 by Web Man– Another approach would be to develop a more federated

environmental resource that crosses all Federal Agencies.

– Embracing New Tools and Technologies• April 2nd, 2008 by Myra Galbreath

– I think we all agree and are poised to help with this and we look forward to the challenge of adopting new collaborative tools and technologies for the Agency.

– One area of particular interest to me is what tools or methods are available, or becoming available, that EPA should embrace and adopt to help people gain access to information?

15

3. The National Dialogue Jam Session: What We Learned

• Individual Comments (excerpts):– Our Collective Strength:

• April 2nd, 2008 by Andrew Battin – One area of particular interest to me is how terminology and

metadata can improve the ability to discover and ultimately access information? What are we doing across OEI in these areas and how can we leverage these activities together?

– Get Me to the Data:• April 2nd, 2008 by Mike Flynn

– The information world is changing fast, and quite simply, we either change in response to the times or we’ll be left behind.

16

3. The National Dialogue Jam Session: Some Web 2.0 Solutions

• Improving internal data and resource sharing:– EPA use of Web 2.0 Wikis for Gov 2.0.

• Helping people find what they want on EPA’s site:– Repurposing Selected EPA Content into a Web 2.0 Wiki to Get

the Wikipedia – Google Effect!• Making EPA’s data downloadable and usable:

– See epametadata.wki.is!• Explaining what the information means:

– Combine the data and the metadata (DRM 2.0/Web 2.0 and DRM 3.0/Web 3.0)

• Using new technologies for collaboration:– EPA use of Web 2.0 Wikis for Business Transformation in

Enterprise Architecture, Data Architecture, Geospatial Line of Business, E-Rulemaking, etc.

Note: These also address the Individual Comments.

17

3. The Wikipedia – Google Effect!

18

4. Business Transformation for EPA Enterprise Architecture

• Goals:– To become more than a planning activity;– To become more than a compliance-driven activity;– To know better what we know;– To use that to be more transparent and collaborative;– To use that to manage for greater impact in 2008-2009; and– To even build our own agile enterprise mashups for information

sharing and integration.

• Method: Look at everything you produce and how you document it to see how it can be improved (email, attachments, documents, Web sites, collaboration spaces, meetings, reports, etc.)

19

5. Inventory and Refresh

• 5.1 EPA's Enterprise Architecture Web Site

• 5.2 EPA's Enterprise Architecture Web Site

• 5.3 EPA's Enterprise Architecture QuickPlace

• 5.4 Conclusion

20

5.1 EPA's Enterprise Architecture Web Site

http://intranet.epa.gov/architec/

21

5.1 EPA's Enterprise Architecture Web Site

• Categories:– Home Page: Only a Graphic.– Enterprise Architecture: Nine Subtopics.– Governance: Five Subtopics.– Site Map: A Web 2.0 Wiki automatically

generates and updates this!– Contacts: A Web 2.0 Wiki allows comments

on every page and email alerts and RSS feeds for every page (see example).

22

5.1 EPA's Enterprise Architecture Web Site

• Enterprise Architecture Sub-Topics:– About EA: Five Sub-Sub-topics– Enterprise Architecture Coordination Workgroup (EAWG): All these file

attachments can be authored directly in the Wiki and commented upon there!

– EA Policy, Procedure, and Guidance: Probably want fully digital versions of these in the Wiki (see example 2120.3!)

– Enterprise Architecture Reports and Presentations: Same comment as above.

– Federal Laws and Guidance: Just links.– Reference Models: Just links.– Related Links: Just links.– WebArt: EPA Architecture Repository and Tool: Could/should be

integrated with the Web 2.0 Wiki– Enterprise Architecture Archives: Could/should be integrated with the

Web 2.0 Wiki.

23

5.1 EPA's Enterprise Architecture Web Site

• About EA: Five Sub-Sub-topics:– What is an EA? – Why create an EA? – How will individual EPA organizations benefit

from an EA? – What is EPA's approach to EA? – EA Conceptual Framework Descriptions

24

5.1 EPA's Enterprise Architecture Web Site

• Governance Subtopics:– IT Capital Planning (CPIC)– IT Human Capital Development– IT Policies, Directives and Guidance– IT Security– Information Management Officers (IMOs) and

Senior Budget Officers (SBOs)

Note: Address this later.

25

5.1 EPA's Enterprise Architecture Web Site

http://intranet.epa.gov/architec/sitemap.html

26

5.1 EPA's Enterprise Architecture Web Site

http://intranet.epa.gov/architec/contacts.html

27

5.1 EPA's Enterprise Architecture Web Site

http://intranet.epa.gov/architec/eawg.html

28

5.1 EPA's Enterprise Architecture Web Site

http://intranet.epa.gov/architec/ea_governance.html

29

5.2 EPA's Enterprise Architecture WebART

http://jaguar.rtpnc.epa.gov/Default.aspx?index=0

30

5.2 EPA's Enterprise Architecture WebART

• About• Enterprise Architecture Links• EPA Business

– Strategic Plan – Environmental Programs – Environmental Information – Organizations – Budget – Business Service Catalog

• EPA Architecture– Service Component Catalog – Architecture Layers – Redundancies and Gaps

• Launch Metis Model - Opens a Metis Model Browser to navigate the Architecture visually

31

5.2 EPA's Enterprise Architecture WebART

http://jaguar.rtpnc.epa.gov/Strategic.aspx?index=2&architectureIndex=2

Segments: See next slide.

32

5.2 EPA's Enterprise Architecture WebART

• Segments:– Disaster Management and Emergency Response– Environmental Remediation– GEO Segment– OW - Office of Water– Office of Environmental Information (OEI) – Office of Prevention, Pesticides, and Toxic

Substances (OPPTS)– Office of Solid Waste and Emergency Response– Research and Science Architecture– Waste Management

33

5.2 EPA's Enterprise Architecture WebART

http://jaguar.rtpnc.epa.gov/Data.aspx?index=2&architectureIndex=4

Taxonomies: No result!

Data Assets: See next slide.

See next slide.

34

5.2 EPA's Enterprise Architecture WebART

• The below links provide lists for the entities modeled in the repository. Click on an object-type to view the corresponding report matrix.– Lots are blank!

• Partner Data Asset (just one):– Emergency Notifications

• Coast Guard

35

5.2 EPA's Enterprise Architecture WebART

http://jaguar.rtpnc.epa.gov/Data.aspx?index=2&architectureIndex=4

36

5.3 EPA's Enterprise Architecture QuickPlace

https://epaqpx.rtp.epa.gov/enterprisearchitecture

37

5.3 EPA's Enterprise Architecture QuickPlace

• Welcome to the Enterprise Architecture Quickplace

• FY2008 EA Self- Assessment Status Report

• About Enterprise Architecture* • EA Home Page*• 2008 EPA EA Self Assessment

Documents • FEA Practice Guidance*• Data Architecture*• Reference Models*• WebART*• Q3 Quarterly Milestone

Documents to OMB • EPA IT Tools (IP)

• EPA Solution Architecture Training Course

• EA Outreach • 2008 Documents for Review*• 2007 Documents for Review

(BPMN)• Presentations • Index • Library • Solution Architecture Business

Case Integration Milestones (2007)

• Calendar • Tasks • Members • Discussion

* Links to Original Source or Duplicates Same Elsewhere.

38

5.3 EPA's Enterprise Architecture QuickPlace

39

5.4 Conclusion

• Lots of different files formats in lots of different categories in multiple places that are not all accessible to everyone that needs them.

• Asked to help with a new taxonomy, but also need an application integration platform and an application development platform.

• A Web 2.0 Wiki deals with the above two points by allowing users to realize more value from existing systems and human resources by supporting IT in exposing legacy systems and other applications through the Wiki!

40

6. Evolving Solution• Work with the EA Team (its contractors and

stakeholders) and IT Staff to demonstrate in a Web 2.0 Wiki:– Making lots of different files formats in lots of different

categories in multiple places more accessible and useful.

– Better organization, management, and search of content.

– Use as both an application integration platform and an application development platform.

• The Emergency Management Segment for Data Architecture.

Note: I could have said make it work better than everything else in current use!

41

6. Evolving Solution

• Solution Technology Requirements Indicators Crosswalk Template Snapshot (next slide):– Land Quality Management Segment has captured the

information flow and interface profile table. Each solution architect could use the information flow in the table to create this diagram as a supporting artifact.

• My Comment: Even better, the interface could be to an executable application that linked information architecture to data architecture according to slide 43.

42

Architecture Development Standards and Guidance2008 Distinctions – Solution Architecture

Solution Technology Requirements Indicators Crosswalk template snapshot

• This template will be pre-populated with existing information from the Transition Strategy and QTS Milestone Analysis

See Handouts

43

Validated Data

Updates

Portal Applications access Data

Marts

ApplicationsLeverage

Web Services

System of Registries

FRS

SRS

EDR

TRS

Validated Data

Validated Data

DATABASES

OSWERHR Data

Other Smaller Databases

CLPSS Data

ACRES Data

OERRWA Data

ECMS

SEMS Data

RCRAInfo Data

Web Services access data from Databases

Ext

ract

, Tra

nsfo

rm, L

oad

Non-OSWERData Marts

OSWER Data Marts

GEOSPATIAL

DOCUMENT

LAND AREA

Portal ApplicationsApplications access data directly from Databases

Non-Portal Applications

GRANT DATANon-Portal

Applications access

Data Marts

WEB SERVICES

Oth

erT

ools

BIA

TE

CM

SG

eosp

atia

lT

ool

Envirofacts

eGov Initiatives

FDW

Other Data Marts

DATA REPOSITORIES DATA / APPLICATION SERVICES

Iden

tity

& A

cces

s M

anag

emen

t

EP

AP

AR

TN

ER

S / IN

DU

ST

RY

PU

BLIC

EPA HQ

EPA Regions

Other EPA Locations

APPLICATION INTERFACES (Data Access)

USERS

EPA Contractors

Regulated Community /

Industries

Tribes

States

Grant Applicants / Recipients

General Public

Portal Applications

Applications enter data into databases

Validation

CDX / NEIEN

Iden

tity

& A

cces

s M

anag

emen

t

EP

AP

AR

TN

ER

S /

IND

US

TR

YP

UB

LIC

EPA HQ

EPA Regions

Other EPA Locations

Users

EPA Contractors

Regulated Community / Industries

Tribes

States

Grant Applicants / Recipients

General Public

APPLICATION INTERFACES (Data Entry)

ACRES

Cleanup (CU)

Validation

CERCLIS SDMS

ICTS

RCRAInfo (Corrective Actions)

CLPSSOERRWA

ACRES

Other Smaller Applications

RCRAInfo

SEMS (ICTS)

SEMS

Public Access Systems

Information Discovery

Geospatial

Tracking and Workflow

Grants Management

Content/Document Management

Reporting/Business Intelligence

eGov Initiatives

IC DATA

PERFORMANCE MEASURES

PERSONNEL

ANALYTICAL SAMPLES

Web Services Access Data Marts

Cleanup (CU)

CERCLIS SDMS

ICTS

RCRAInfo (Corrective Actions)

CLPSSOERRWA

eFacts

Other Smaller Applications

SEMS

CPADX

X XX

X XX

Public Access Systems

CIMC Envirofacts

CLU-IN

OERRWA

RCRAOnline Other Applications and Websites

Application Retired ApplicationX

Ent

erpr

ise

Too

l

Data Mart Database

Data Flow

Legend

Architecture Development Standards and Guidance2008 Distinctions – Solution Architecture

Segment System Interface Diagram Template snapshot

The following diagram will help show each segment’s IT portfolio, and its dependency upon other segments, as well as the Agency’s set of Enterprise Tools. Defining target information in this way allows the segment architect an opportunity to illustrate areas of reuse, consolidation and retirement in their target architecture.

See Handouts

44

6. Evolving Solution

• Business Transformation Framework (see next slide):– Expected Impacts on Technology are (1) Data

Optimization, (2) Data Management & Communications, and (3) Metadata Management and External Access and Data Sharing.

My Comment: This again could be realized in a real application that provides actual “line of sight” and Emergency Management data and information (see next slides for pilot example).

45

Architecture Development Standards and Guidance2008 Distinctions – Segment Architecture

Business Transformation Framework

See Handouts

46

6. Evolving Solution

• Integrate Architectures: Data Architecture Pilot:– Enterprise (subject matter expertise and peer

review): EPA Report on the Environment – Segment (topics and subtropics): Five

Categories and 89 Indicators.– Solutions (data tables and metadata):

Standardized and DRM 2.0 Compliant.

My Comment: We have really done is now called a Web 2.0/3.0 Enterprise Mashup.

47

6. Evolving Solution

• Web 2.0/3.0 Enterprise Mashups:– Enterprise Mashups are application hybrids combining content

and functions from more than one existing source to create powerful Web applications, integrated Web experiences and expanded customer value networks. Mashups are the fastest growing enterprise ecosystem on the Web by far. Mashups are social, role-based, network-centric, complex, distributed and essential to all knowledge-based networks, models and businesses. Source: Open Enterprise 2.0 Mashup Summit - Expanding Customer Value Networks

My Comment: So we would like all the Segment Architectures to be “Solutioned” (implemented) in such a way that EPA and its stakeholders can mash them up at will to solve needs that we haven’t yet thought existed.

48

6. Evolving Solution

• Specific Suggestions:– See EPA Data Architecture Pilot:

• Enterprise Data Architecture and Implementation: Federated, Faceted, Semantic Search of Both EPA Metadata and Data with Governance, March 26, 2008, Updated April 4, 2008.

– See Best Practices:• Enterprise Mashup: A Practical Guide to Federal Service

Oriented Architecture.

– Collaborate to Pilot This for Emergency Management (with Joan Karrie) for the next EA Working Group Session.

49

7. List of Presentations and Web 2.0 Wikis

• February 20, 2008, Shift Happens! Briefing for the EPA Enterprise Architecture Team.– http://semanticommunity.wik.is/@api/deki/files/501/=BNiemann0220200

8.ppt

– http://semanticommunity.wik.is/People/Brand_Niemann/5._Past_Events/1_2008

• February 22, 2008, Improved Access to EPA Information: Before and After with Web 2.0-Part 1– http://semanticommunity.wik.is/@api/deki/files/568/=BNiemann0222200

8.ppt– http://semanticommunity.wik.is/People/Brand_Niemann

• March 6, 2008, The CollaborationProject.org & Semanticommunity.net. Update March 10, 2008– http://semanticommunity.wik.is/@api/deki/files/1111/=BNiemann030620

08.ppt– http://semanticommunity.wik.is/People/Brand_Niemann – http://semanticommunity.wik.is/The_Gov_2.0_Collaboration_Project

50

7. List of Presentations and Web 2.0 Wikis

• March 8, 2008, Improved Access to EPA Information: Before and After with Web 2.0-Part 2– http://semanticommunity.wik.is/@api/deki/files/1108/=BNiemann

03082008.ppt– http://semanticommunity.wik.is/People/Brand_Niemann

• March 14, 2008, Enterprise Data Architecture and Implementation: We Have What Our CIO Wants! (see Blog: Restricted Access)– http://epametadata.wik.is/@api/deki/files/5/=BNiemann03142008

.ppt– http://epametadata.wik.is

51

7. List of Presentations and Web 2.0 Wikis

• March 19, 2008, Getting to SOA and Semantic Interoperability for DoD Architectures– http://semanticommunity.wik.is/@api/deki/files/1132/=BNiemannIDGA03

032008.ppt

– http://semanticommunity.wik.is/Best_Practices/6th_Annual_DoD_Architectures_Conference

• March 19, 2008, DoDAF 3.0: A Web 2.0 and SOA Mashup! (March ??, 2009)– http://semanticommunity.wik.is/@api/deki/files/1135/=BNiemannArmyP

D03192008.ppt

– http://semanticommunity.wik.is/Best_Practices/6th_Annual_DoD_Architectures_Conference

• March 21, 2008, Improved Access to EPA Information: Before and After with Web 2.0-Part 3– http://semanticommunity.wik.is/@api/deki/files/1147/=BNiemann032120

08.ppt

– http://semanticommunity.wik.is/People/Brand_Niemann

52

7. List of Presentations and Web 2.0 Wikis

• March 26, 2008, Enterprise Data Architecture and Implementation: Federated, Faceted, Semantic Search of Both EPA Metadata and Data with Governance. Slides. (Collaboration with EPA Contractors and Vendors) Updated with CentrifugeSystems to show connection of data architecture with Exploratory Data Analysis (Statistics), Business Intelligence, and GIS (April 5, 2008). – http://semanticommunity.wik.is/@api/deki/files/1170/=BNiemann032620

08.ppt– http://semanticommunity.wik.is/People/Brand_Niemann/2008_Semantic

_Technology_Conference• March 29, 2008, Data Architecture Subcommittee: A

Knowledgebase with Implications for EPA Data Architecture. Slides. (Collaboration with EPA Contractors and Vendors).– http://semanticommunity.wik.is/@api/deki/files/1175/=BNiemannDAS03

292008.ppt

– http://semanticommunity.wik.is/People/Brand_Niemann/2008_Semantic_Technology_Conference

53

7. List of Presentations and Web 2.0 Wikis

• April 1, 2008, Improved Access to EPA & Interagency Information: Before and After with Web 2.0, FDLC, Kansas City, MO.– http://semanticommunity.wik.is/@api/deki/files/1179/=BNiemann

FDLC04012008.ppt

– http://semanticommunity.wik.is/Best_Practices/Depository_Library_Council_Spring_2008_Meeting

• April 1, 2008, EPA's National Dialogue on Access to Environmental Information: Before and After with Web 2.0, FDLC, Kansas City, MO:– http://semanticommunity.wik.is/@api/deki/files/1185/=BNiemann

04012008.ppt– http://semanticommunity.wik.is/Best_Practices/Depository_Librar

y_Council_Spring_2008_Meeting

54

7. List of Presentations and Web 2.0 Wikis

• April 1, 2008, Updated April 12, 2008, EPA Data Architecture Wiki: Tutorial– http://epadatarchitecture.wik.is/ – http://epadatarchitecture.wik.is/@api/deki/files/13/

=BNiemannDA04012008.ppt – To Nathan Wilkes to Help Mike Pendelton Setup a Wiki

• April 6, 2008, Improved Access to EPA and Interagency Information: Before and After with Web 2.0 – Part 4– http://semanticommunity.wik.is/@api/deki/files/1256/

=BNiemannPart404072008.ppt – http://semanticommunity.wik.is/Best_Practices/Role_Reversal

%3a_Before_and_After_Web_2.0

55

7. List of Presentations and Web 2.0 Wikis

• April 9, 2008, EA Taxonomy for Improved Information Access and Reuse– http://gov2.wik.is/@api/deki/files/18/

=BNiemann04092008.ppt – http://gov2.wik.is/

• April 1, 2008, Improved Access to EPA and Interagency Information: Before and After with Web 2.0 – Part 5– http://semanticommunity.wik.is/@api/deki/files/1257/

=BNiemannPart504072008.ppt – http://semanticommunity.wik.is/Best_Practices/

Role_Reversal%3a_Before_and_After_Web_2.0

56

7. List of Presentations and Web 2.0 Wikis

• April 10, 2008, Enterprise Architecture Working Group Session: Suggestions– http://epadatarchitecture.wik.is/@api/deki/files/22/

=BNiemannEA04102008.ppt– http://epadatarchitecture.wik.is– Help Emergency Management (Joan Karrie) at next EAWG

Meeting.• April 14, 2008, A New Enterprise Data Management

Strategy for the U.S. Government: Support for the Semantic Web and Semantic Technology:– http://semanticommunity.wik.is/@api/deki/files/1264/

=BNiemannSTC04142008.ppt– http://semanticommunity.wik.is/People/Brand_Niemann/

2008_Semantic_Technology_Conference

57

7. List of Presentations and Web 2.0 Wikis

• April 14, 2008, EPA E-Rulemaking: Pilot Application of Blogs in Wikis– http://epaerulemaking.wik.is/@api/deki/files/2/=BNiemannER041

42008_(1).ppt

– http://epaerulemaking.wik.is/ • April 16, 2008, CIO’s Learning Web 2.0 Wikis: A Tutorial

– http://cioslearning.wik.is/@api/deki/files/14/=BNiemannKSG04162008.ppt

– http://cioslearning.wik.is/• April 18, 2008, Geospatial Line of Business Wiki: A

Tutorial– http://geolob.wik.is/@api/deki/files/14/

=BNiemannGeoLoB04172008.ppt – http://geolob.wik.is/

58

7. List of Presentations and Web 2.0 Wikis

• April 25, 2008, Gov 2.0: Business Transformation Though Enterprise Mashups of Enterprise, Segment, and Solutions Architectures Implemented in Web 2.0 Wikis (also Improved Access to EPA, Interagency, and Non-government Information: Before and After with Web 2.0 – Part 6):

– http://semanticommunity.wik.is/@api/deki/files/1288/=BNiemannGov204252008.ppt

– http://semanticommunity.wik.is/Best_Practices/Role_Reversal:_Before_and_After_Web_2.0

• April 25, 2008: Gov 2.0: Business Transformation for EPA Enterprise Architecture Implemented in Web 2.0 Wikis

– http://gov2.wik.is/@api/deki/files/20/=BNiemannEPAEA04252008.ppt – http://gov2.wik.is/

• April 30-May 1, 2008, 5th SOA for E-Government Conference Welcome:– http://semanticommunity.wik.is/@api/deki/files/1248/=SOAEGOV04302008.ppt – http://semanticommunity.wik.is/Government_SOA_Community_of_Practice/Conf

erences/5_2008_April_30-May_1