1 wssc/intrusionworld gov 2.0: business transformation though enterprise mashups of enterprise,...

1

WSSC/IntrusionWorld

Gov 2.0: Business Transformation Though Enterprise Mashups of Enterprise, Segment, and Solutions Architectures

Implemented in Web 2.0 Wikis

Brand NiemannSenior Enterprise Architect

U.S. Environmental Protection AgencyWeb Services Security & SOA Conference

Baltimore Convention Center, Baltimore, MDMay 12-13, 2008

http://gov2.wik.is

2

Abstract• The Federal Enterprise Architecture has evolved

from compliance-driven to value-driven with the addition of Segment and Solutions Architectures and increased coordination with the DoD Architectural Framework (DoDAF).

• However, the DoDAF 1.5 is evolving to 2.0 with a focus on Business Transformation with SOA.

• In addition, the author has suggested in a recent presentation at the DoD Architectures Conference (Blueprints of Today-Architectures of Tommorrow) that next year we could be talking about DoDAF 3.0 as a Web 2.0 and SOA Mashup!

3

Abstract

• Business Transformation has become the new paradigm for Gov 2.0 because Enterprise Architecture is usually just planning.

• Web 2.0 and SOA have become the way to implement distributed, but connectable Web Services in Communities of Practice using Wikis that can be federated with semantic interoperability for data sharing and integration.

4

Abstract

• This presentation will feature a series of Business Transformation services created for the press, CIO's, and everyone else.– Please see our Semantic

Community.net: Community Infrastructure Sandbox:

• Role Reversal: Before and After Web 2.0.

– And go to next slide for the seven examples.

5

Abstract

Name Before AfterQuality Environmental Indicators Web Sites Web 2.0 Wiki

Tutorial

A New Enterprise Data Management Strategy for the U.S. Government: Support for the Semantic Web and Semantic Technology

Web Sites and Wikis

Web 2.0 Wiki

Tutorial

E-Rulemaking Web Site Web 2.0 Wiki Tutorial

CIO's Learning Web 2.0 Wikis (Harvard Government I/T Curriculum and Tools Seminar, Harvard Policy Group, Spring 2008)

Web Site and Wiki Web 2.0 Wiki

Tutorial

6

Abstract

Name Before AfterMAX Federal Community

(formerly the Budget

Community)

Web Site (Wiki)

(government only-

password required)

Tutorial

Semantic Web for Financial Data

Tutorial (in process)

Geospatial Line of Business

Web Sites and Wiki Web 2.0 Wiki

Tutorial

Gov 2.0: Business Transformation Though Enterprise Mashups of Enterprise, Segment, and Solutions Architectures Implemented in Web 2.0

Web Sites Web 2.0 Wiki

Tutorial

7

Gov 2.0 Business Transformation

Transform Before After Activity (Wiki)

EPA PARS Paper-based (4) Web 2.0 Wiki (2)

Ongoing record & journal

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

8


• Four Objectives:– Transform the way we do EPA Enterprise

Architecture (EA).– Transform the way we deliver the EPA EA to

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

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

– Transform the way we do EPA Performance Appraisal and Recognition System (PARS) so employees can show how their elements and standards link to and provide a clean line of sight to EPA's strategic goals.

9


• Footnotes:– (1) 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) Employees are encouraged to maintain an ongoing record or journal of major achievements and contributions throughout the appraisal cycle so as to have ready access to the information needed to complete their self assessment narrative.

10

Preface

• Learning Objectives:– What is Business Transformation?– What Are the Architectural Levels and

Attributes?– What are Web 2.0 Wikis?– What are Enterprise Mashups?– How Does This Relate to Web Services

Security and SOA?– What are the Seven (proven practice)

Examples?– What are Your Questions and My Answers?

11

What is Business Transformation?

• Business transformation is a key executive management initiative that attempts to align People, Process and Technology initiatives of a company more closely with its business strategy and vision to support and help innovate new business strategies. Business transformation is achieved through efforts from alignment of People, Process and Technology strategies towards a strategic end-state.

• Business transformation can be achieved through new technology, business models and management practices. Business transformation is now considered an essential part of the competitive business cycle.

Source: Wikipedia. Suggestion: Google it for more!

12

Introduction• The Organisation for

Economic Co-operation and Development has defined four stages of e-government, each more demanding than the last. After information comes “interaction”, then “transaction” and eventually “transformation. The more transformational the change, the bigger the benefits. But it turns out that, at all stages, the biggest beneficiaries will be governments, so they may have to work at persuading users to accept the changes.

http://www.economist.com/surveys/displaystory.cfm?story_id=10638121

13

What Are the Architectural Levels and Attributes?

Source: FEA Practice Guidance, Federal Enterprise Architecture ProgramManagement Office, OMB, November 2007. See next slide for definitions.

14

What Are the Architectural Levels and Attributes?• Enterprise Architecture: A management practice

for aligning resources to improve business performance and help agencies better execute their core missions. An EA describes the current and future state of the agency, and lays out a plan for transitioning from the current state to the desired future state.

• Segment Architecture: Detailed results-oriented architecture (baseline and target) and a transition strategy for a portion or segment of the enterprise.

• Solution Architecture: An architecture for an individual IT system that is part of a segment. A solution architecture is reconciled to the segment architecture above it.

15

What Are the Architectural Levels and Attributes?Architectural Level

Tools Web 2.0 Wiki

Enterprise Word, PowerPoint,

Visio, etc.

Yes*

Segment Word & Web Databases

Yes*

Solutions Word & Spreadsheets

Yes*

* If application integration and application development platform.

16

What are Web 2.0 Wikis?

• Web 2.0 Crucial to New Information Workplace, CIO Magazine, November 29, 2007, C.G. Lynch, CIO:– Forrester reports that from blogs to wikis to

virtual worlds, the modern information worker wants a seamless user experience and more and more, IT will be forced to deliver.

– The Seven Tenets of the Information Workplace: Contextual, Individualized, Seamless, Visual, Multimodal, Social, and Quick.

• And more in the tutorial coming.

17

What are 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.

• Examples later.

Source: Open Enterprise 2.0 Mashup Summit - Expanding Customer Value Networks.

18

How Does This Relate to Web Services Security and SOA?Web Services SOA Web 2.0

Wikis*Publish Standards and XML Email Wiki URL &

Page Link

Find Registry (UDDI) Google: Try “Deki Wiki EPA”

Bind WSDL RSS and API

Consume Quality of Service Hosted Service

User Management

* Faster and cheaper and already supports security and federation.Also see Dapper Web Services and Semantify Your Site.

19

What are the Seven (proven practice) Examples?• Please Recall Slides 5-6.• The Tutorial Will Show How I Create One.• Then Tutorial Will Show Some Enterprise

Mashups of Them!– The Mashup possibilities are endless!

• Please Bear With Me Because This Is Different From the Way That Most of You Have Done Web Services Security and SOA Until Now.

20

Step 1: Decide on Name

http://wik.is/

21

Step 2: Register Name

http://wik.is/register/?sitename=gov2&x=51&y=13

22

Step 3: Login

http://wik.is/success/?sitename=gov2

23

Step 3: Login

Private Email

24

Step 4: Set Preferences

http://gov2.wik.is/Welcome

25

Step 4: Set Preferences

http://gov2.wik.is/Special:Preferences

Change Password

Change Time Zone

26

Step 5: Control Panel

http://gov2.wik.is/Admin:

27

Step 5: Control Panel

http://gov2.wik.is/Admin:Settings

A Security Setting

28

Step 6: Design Home Page

http://gov2.wik.is/

Background and Purpose

29

Step 6: Design Home Page

http://gov2.wik.is/

Structure and Interface

30

Step 7: Create Subtopics

http://gov2.wik.is/2008_EPA_Architecture_Development_Standards_and_Guidance_v1.0

31

Step 8: Repurpose Web Content Into Wiki

http://gov2.wik.is/

32

Step 9: Attach Files

http://gov2.wik.is/Documents

33


http://gov2.wik.is/Documents File Descriptions

34


http://gov2.wik.is/Documents

35

Step 10: Insert Images and Links

http://gov2.wik.is/Learning_Objectives/What_Are_the_Architectural_Levels_and_Attributes%3f

36

Step 10: Insert Images and Links

http://gov2.wik.is/Learning_Objectives/What_Are_the_Architectural_Levels_and_Attributes%3f

37

Step 11: Create Web Log(Blog)

http://gov2.wik.is/Blog

38

Step 12: Set Security

http://gov2.wik.is/

39

Step 12: Set Security• Public: everybody can view and edit.• Semi-Public: everybody can view, but only

selected users can edit.• Private: only selected users can view and edit

this page.• Note: Deki Wiki has one of the most advanced

permission systems available. Deki Wiki administrators can make wikis public or private, anonymous or not. There is user groups support. Users can permission entire hierarchies to create private or non-editable workspaces or permission single pages.

40

Step 13: Monitor Users

http://gov2.wik.is/Special:Recentchanges

41

Step 14: Revise/Reorganize• To soon for this new Wiki, but for another EPA

Web 2.0 Wiki Project I did the following quickly:– Moved content from Wiki to another Wiki.– Implemented a set of topics and subtopics.– Created a new user interface.– Updated the Tutorial slides and uploaded them.

• Note: This shows how agile and flexible the Web 2.0 Wiki environment is to respond to requests that would be more difficult (or impossible) and time consuming with Web 1.0 collaboration technology.

42

Context

Source: Mills Davis, Four Stages of the Web at http://project10x.com/about.php

43

Context• Some basic functionalities of Web 2.0 Wikis:

– Author like Word– Edit/comment on every page– Some level of security for every page– Tagging– Versioning– Watchlist– RSS/XML between applications– Search– etc.

• Doing data models (ontologies) in Web 3.0 Semantic Wikis (see next slide).

44

For the Best Presentation at the3rd SOA for E-Government Conference, May 1-2, 2007,

at The MITRE Corporation, McLean, VA.

Special RecognitionMichael Lang, Revelytix

SOA in Semantic Wikis: A Story About Communication

Federal CIO Council’s Service-Oriented Architectures Community of Practice (SOA CoP)

Produced in Collaboration With

By SOA CoP Co-Chairs, Greg Lomow, Bearing Point & Brand Niemann, US EPA

SOA CoP Best Practices and Architecture & Infrastructure Committeesof the Federal Chief Information Officers Council

45

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 created by combining internal sources such as enterprise data with external Web resources such as Google Maps.

• Mashups are created when different application program interfaces (API) are combined or 'mashed' to create an entirely new application.

46

Enterprise Mashups

47

Enterprise Mashups

48

Enterprise Mashups

http://semanticommunity.wik.is/Best_Practices/Enterprise_Mashup:_A_Practical_Guide_to_Federal_Service_Oriented_Architecture

49

Enterprise MashupsPGFSOA Topic (1)

AIC (2) DoD (3) NCIOC (4) OMG (5) SOA CoP

SICoP (6)

Audience Chief Architects, CIOs, etc.

Agency & Coalition Partners

Open Membership & Clients

Open Membership & Clients

Open Communities

Rationale Performance Improvement

Information Sharing

Interoperability Standards Collaboration to get the Medici Effect (7)

SOA & Semantic Interoperability

Target Architecture

SOA, SOA, & SOI (8)

DoDAF 2.0 Adaptable Computing Infrastructure CoP

SOA Consortium

Adaptable Computing Infrastructure CoP

See Footnotes in slide 51.

50

Enterprise Mashups

PGFSOA Topic (1)

AIC (2) DoD (3) NCIOC (4) OMG (5) SOA CoP

SICoP (6)

Implementation Examples CoI and EA Activities

Continuously increasing levels of interoperability

RFIs & RFPs (9)

Pilots

MITRE SOA Lab (10)

Center of Excellence?

Roadmap Maturity Model & Assessment

SOA SCOPE, etc. Government Information Days

Conferences

Conferences

See Footnotes in slide 51.

51

Enterprise Mashups• Footnotes:

– (1) Practical Guide to Federal Service Oriented Architecture – (2)

Architecture & Infrastructure Committee of the Federal CIO Council

– (3) Department of Defense – (4) Network Centric Operations Industry Consortium – (5) Object Management Group – (6) Semantic Interoperability Community of Practice– (7) December 10, 2007, Social networking and the Medici Effect

, Government Computer News 25th Anniversary Issue.– (8) Service Oriented Enterprise (SOE), Service Oriented

Architecture (SOA), & Service Oriented Infrastructure (SOI)– (9) Requests for Information & Requests for Proposals– (10) See Bob Sadler, May 1st, 1-1:50 PM,

5th SOA for E-Government Conference.

52

Enterprise Mashups

http://semanticommunity.wik.is/Government_SOA_Community_of_Practice/Conferences/5_2008_April_30-May_1

53

Enterprise Mashups

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

54

Vision and Implementation

Data Architecture Component Specific Artifact Example

DRM 2.0 (1)

Description Metadata (4) Spreadsheet *

ContextTaxonomy/Ontology (5)

Web 2.5 Wiki

Sharing Data (4) Spreadsheet *

DRM 3.0 (2)

Semantics (3)

RDF/SPARQL (6) Middleware

SOA Services (7)Web 2.5 Wiki (8)Web 3.0 Wiki (9)

Footnotes: See next slide.

Our initial objective is to see if this Web 2.0 Wiki can be useful in bringing about collaboration across the Metadata Management Functions Matrix, Teams-Tasks Matrix, and DataArchitecture Documents.

A longer range goal would be to see if this Web 2.0 Wiki could be used as an EnterpriseMetadata Management and Application Development Tool (e.g. data and metadata mashups).

Note: Web 2.0 does DRM 2.0 and Web 3.0 does DRM 2.0/3.0!

55

Vision and Implementation• Footnotes:

– (1) FEA DRM 2.0 and Report to Congress (2005).– (2) February 6, 2007, and February 5, 2008.– (3) Combines Description and Context from DRM 2.0. See (2).– (4) The data and metadata are combined together (see Brand

Niemann).– (5) Information Architecture (topics and subtopics) and Data

Architecture (data tables and data elements) are integrated. See Web 2.0 Wiki Pilot: Information Classifications.

– (6) This specification defines the syntax and semantics of the SPARQL query language for RDF. SPARQL can be used to express queries across diverse data sources.

– (7) EPA Data Architecture Enterprise Metadata.– (8) Video on data reuse in mashups that will revolutionize EPA

data architecture, data management, and data reuse applications!

– * Note: This also works with relational databases.

56

Demonstrations• Federated• Faceted• Semantic Search• Data• Metadata• Governance• DRM 2.0 Compliance (see next slide)• Information Architecture and Data

Architecture• DRM 3.0/Web 3.0• Discovery (see slide 53)

57

DRM 2.0 Compliance

The Three Requirements for Information Sharing Have Been Satisfied!

58

Discovery (Centrifuge)

This relational view represents a bundled graph of Maryland 2006 data showing Companies linked to Chemicals. This graph shows that two of the primary collections, PBT and TRI, have multiple companies between them. The chemicals have been bundled (grouped) by their chemical classifications.

59

Web 2.0 and Security• Social-networking technologies offer benefits

that support a homeland security agenda, Federal Computer Week, September 3, 3007:– Web 2.0 applications are resilient and well-suited to

collaboration because they need to connect the dots and respond to fast-changing situations.

– DHS employees can still access their information, even if their computers are inaccessible, as they might be during a national security emergency.

– While Web 2.0 might threaten command-and-control organizations and require improved mobile data security, the advantages to homeland and national security purposes far outweigh the risks.

David Stevenson Blog: http://stevenson-strategies.com

60

What are You Questions and My Answers?• Contact Information:

– Brand Niemann– [email protected]– 202-564-9491– http://semanticommunity.net

• Also see Online Book Part 14: The New Language of Business: SOA for Infrastructure Flexibility and Web 2.0 for Collaboration in A New Enterprise Information Architecture and Data Management Strategy for the U.S. Government.– June 25-26, 2008, Business Process Management Conference,

Service Oriented Architecture Conference and/or Business Architecture Conference, Brainstorm Group, Washington, DC. Invited Presentation.

– September 9-10, 2008: Business Transformation Though Enterprise Mashups of Enterprise, Segment, and Solutions Architecture Implemented in Web 2.0 Wikis. Presentation Submitted for the 2008 Enterprise Architecture Conference & Exhibition, Ronald Reagan Building and International Trade Center, Washington, DC.