1. 1 Collaborative Organizing Workshop: Opening Up Networked Improvement Activities Around Service Oriented Architecture in 2007 Collaborative Expedition Workshop #57, Tuesday, January 23, 2007, at NSF DRAFT

2. 2 Why We Are Here SOA is the Number 2 Priority in the “CIO Top 10 Challenges Report” from the AFFIRM 2006 Survey. There is Lots of Activity on Service-Oriented Architecture. –AIC Subcommittees: Governance & Services –Best Practice Committee CoPs: KM WG, SOA, SICoP –Non-governmental Organizations: See growing list: http://colab.cim3.net/cgi- bin/wiki.pl?PracticalGuidetoSOAImplementation

3. 3 Why We Are Here Town Hall for SOA Management Strategies: –Purposes and Outcomes: Bob Haycock, Former Chief Architect –Panel Discussion: Business Case: Kshemendra Paul, Chief Enterprise Architect, Department of Justice Services: George Thomas, Chief Architect, GSA Data: Bryan Aucoin, Chief Architect, Director of National Intelligence (DNI) Governance: Roy Mabry, Senior Enterprise Architect, DOD- CIO –Related EA/SOA Events: Brand Niemann, US EPA, and SOA CoP Co-Chair Proceedings at http://colab.cim3.net/cgi-bin/wiki.pl?ArchitecturePlusSeminar_2006_12_19

4. 4 Why We Are Here Governance - Go for recognition and status like the DRM 2.0: An announcement from Karen Evans of a new process with lead agency (DHS) and person (Mike Daconta), and management team, open process, and schedule of deliverables. –Lead: Mike Tiemann to discuss with new AIC Leadership, Dick Burk, and Karen Evans and report on at our next meeting. Writing Team - Compile list of volunteers and recommend co-chairs (government and non-government) for each of about 5 teams to work on major sections of the proposed outline. –Lead: Dave Mayo to work with others to provide this for our next meeting. AIC Emerging Technology Subcommittee and Best Practice Committee/SOA CoP Support for Items 1 and 2 - Continue outreach, expand the demo, and provide Wiki training to report at our next meeting and the January 23rd Workshop. –Leads: Brand Niemann and Susan Turnbull Suggestions by Brand Niemann at the January 5 th SOA Joint Task Force Meeting.

5. 5 Why We Are Here White Papers: –BPC (Steve Else-SOA CoP) –GSA OIS (Marc Wine-Shared Services) –ACT/IAC (Dave Mayo-Practical Guide) Workshops and Conferences: –This monthly series (February 20 th, etc.) –3 rd SOA for E-Government (May-June) Pilots: –SOA CoP Phase 3 (in planning)

6. 6 Phase II SOA CoP Demo Business Intelligence (Reports/Dashboard) NEF Program (Manages Projects) Employee (Reports Time) Finance LoB (Calculates Costs) HR/Payroll - LoB (Allocates Time to Projects) Contractor (Produces Invoices) MetaMatrix Data Services Sun MicroSystems DynAccSys Web Service Web Service Web Service Web Service Web Service Web Form Data Access Executable Model Data Access Executable Model Dashboard Client Implementation

7. 7 Why We Are Here Source: FEA Practice Guidance, “Value to the Mission”, December 2006, Federal Enterprise Architecture Program, Management Office, OMB, 45 pp.

8. 8 Why We Are Here Make the relationships between: –1. enterprise architecture A management practice for transitioning from the current state to the desired future state. –2. segment architecture, and Detailed results-oriented architecture (baseline and target) and transition strategy for common, shared, or enterprise services. –3. solution architecture An architecture for an individual IT system that is part of a segment. real using SOA in White Papers, Workshops/Conferences, and Pilots.

9. 9 Why We Are Here Understand Our Different “Maps” of SOA/EA: –David Mayo – Seven Topics and Detailed Outline –Chris Harding – Ontology –Haiping Luo – Conceptual Model –Duane Nickull – Concept Map –Eric Sweden – Governance Model –Bob Marcus – SOA Technologies Roadmap –Dave Chesebrough, and Hart Rossman, and Steve Orrin – SOA Implementation Roadmap

10. 10 Why We Are Here Practical Guide to Federal SOA: –The topic areas for which we seek team leads are (this is draft and subject to change): SOA Drivers & Rationale Executive Support and SOA Governance SOA Adoption & Management SOA and EA SOA Infrastructure Service Delivery and Composition SOA and Other Management Processes See http://colab.cim3.net/file/work/caf/meetings/2006-12-19/SOAPracticalGuideOutline12182006.doc

11. 11 Why We Are Here

12. 12 Why We Are Here Drafted in Nov, 2006 by Haiping Luo. 2006-12-1: updated.

13. 13 Why We Are Here OASIS Reference Model for Service Oriented Architecture V 1.0 - Official Committee Specification approved Aug 2, 2006.

14. 14 Why We Are Here There is no normative convention for interpreting the concept maps used and other than described in the RM document, no detailed information can be derived from the concept maps herein.

15. 15 Concept Map of DRM 2.0 See next slide for explanation. Is_a

16. 16 Concept Map of DRM 2.0 Essentially a Data Model of a Data Model! –PDF Version for Use in a Document, SVG Version for Use on the Web, XML Version for Structure, OWL Version for Semantic Relationships, and Simple Text Version. Source: Brand Niemann, Jr., Informal Communication, October 28, 2006, as part of the October 11, 2006, Birds of a Feather Meeting on National Information Sharing Standards at the Fifth Semantic Interoperability for E- Government Conference, October 10-11, 2006. –http://colab.cim3.net/file/work/SICoP/2006-10- 10/NatilStandards_10_11_2006.doc –See Concept Maps Home Page at http://cmap.ihmc.us/

17. 17 Why We Are Here Source: NASCIO's Service Oriented Architecture: an Enabler of the Agile Enterprise (June 1, 2006).

18. 18 Why We Are Here

19. 19 Why We Are Here The SafeSOA Taskforce Kickoff Meeting Presentations, December, 13th 2006, at http://www.safesoa.org/

20. 20 Agenda 8:30 am - Check-in and Coffee 8:35 am - Welcome and Introduction 9:00 am - Introductions: What are your interests in light of the workshop purpose? 9:30 am - Invitation to Collaborative Authoring of A Practical Guide to Federal SOA Outline and Collaborative Process –David Mayo, President, Everware-CBDI and IAC EA SIG Services Subcommittee Chair

21. 21 Agenda 10:00 am - Invitation to Collaborative Authoring of The Open Group SOA Ontology –Chris Harding, The Open Group Forum Director for SOA and Semantic Interoperability (remote from England) 10:30 am - BREAK 10:45 am - Invitation to Collaborative Authoring of The Enterprise Architecture Management Guide –Haiping Luo, Data Management Coordinator, Government Printing Office and Chair of the a|EA Standards Committee

22. 22 Agenda 11:15 am - 11:45 pm - Invitation to Collaborative Action Around OASIS Reference Model for SOA –Duane Nickull, Senior Technical Evangelist at Adobe Systems, chairs the OASIS Service Oriented Architecture Reference Model (SOA- RM) Technical Committee, which recently delivered its first Committee Specification. 11:45 - 1:15 pm - Networking Lunch (on your own)

23. 23 Agenda 1:15 pm - Opening Up SOA Networking: Initiatives and Perspectives from State and Local Government –Eric Sweden, Enterprise Architect, NASCIO 1:45 pm - Invitation to Collaborative Prototyping Around Emerging SOA Standards –Bob Marcus, SRI International 2:15 pm - BREAK

24. 24 Agenda 2:30 pm - Invitation to Collaborative Prototyping Around the Association for Enterprise Integration's (AFEI) SafeSOA Initiative –Dave Chesebrough, President, Association for Enterprise Integration (AFEI) and Hart Rossman, SAIC, and Steve Orrin, Intel

25. 25 Agenda 3:00 pm - Break-Out Sessions - Organizing for Collaborative Authoring, Credible Agreements, and Joint Action –Group 1 - SOA Guide –Group 2 - Open Group SOA Ontology –Group 3 - Enterprise Architecture Management Guide –Group 4 - Organizing February 27 Collaborative Expedition Workshop: Potentials and Realities of SOA-based Identities Management –Group 5 - Cross-Domain Semantic Interoperability –Group 6 - Organizing Around Collaborative Prototyping Opportunities

26. 26 Agenda 4:00 pm - Report out from Break-Out Sessions and Discussion 4:30 - 5 pm - ADJOURN AND NETWORKING