Industry Advisory Council’s Enterprise Architecture Shared Interest Group (IAC EA SIG)

1. Industry Advisory Council’s Enterprise Architecture Shared Interest Group(IAC EA SIG) Collaborative Approach to Addressing Common Government- Industry Needs May 17, 2005

2. Context Setting: IAC and Collaboration • Provide a Vendor-Neutral Enterprise Architecture View of Government- Industry Issues • Leverage collective experience from Industry and Government that “maybe” applicable” to government • “Put away” Vendor Push and support “Government Transformation” • Provide initial “thoughts” and offer other review and collaboration….create Strategic Plan • Treat with mini-planning form- identify key customers • Be Guided by Advisory Board • Don’t do work that can be contracted • Avoid Conflicts of Interest • Short summary information and more detailed information • Information can be put in Technical Notes document or White Paper, if desired…

3. The Role of the EA SIG • Purpose: a forum for government and industry to identify and candidly discuss and evolve the application of Enterprise Architecture methods and practices in Government. • Mission: Provide a practical implementation approach for EA and the utilization of the Reference Models, Profiles, Standards and other EA Guidance in alignment with the President’s Management Agenda and individual Agency’s Mission Goals. Objective: Identify opportunities for IAC to support federal partners in articulating and advancing the importance and utilization of EA across government and in further definition of the FEA.

4. The Role of the Advisory Panel • The Advisory Panel is comprised of senior government executives engaged in the leadership of transformational EA practices within their respective agencies. • The Advisory Panel’s purpose is to offer guidance to the SIG membership resulting in the formulation of projects of shared interest that address current issues and promote the implementation of exemplary EA programs.

5. Strategic Planning Steps • Understand the Range of Opportunities- 21 initially • Solicit interest and feedback from IAC- December 3rd. • Prioritize and Group Activities- December 13 • Thought Leadership • Review • Participate and Collaborate • Outreach and Communication • Review with Advisory Panel- January 12- May 20…. • Map to FEA PMO Strategic Plan- Dick Burk • Fit with the Tasks and Needs of Architecture and Infrastructure and each Subcomittee: Governance, Components, ET and work with Lines of Business • Leadership team will seek Broad Participation and Oversee the activities • Good mix of industry SME and knowledgeable government practitioners • Track and Use Request Form for Project Initiation and Tracking • Process and Style – Honest communication as critical as Products Produced Strive to be a “Trusted Partner” with the Government and Bridge to Industry and Other Partners

6. Focus versus Breadth- Increased Involvement • Objectives: • More members want to be involved • More support seems to be needed • Approach for 2005 • Leader- Mentoring by IAC EA Experienced members, bring in knowledgeable new participants • Mature process with Request Form - Plans – Schedules - Review • Manage expectations, schedule and deliverables • Grow culture of openness thru sharing and honest information exchange • Use Collaborative Portal • Schedule of activities that support both government and industry with knowledge and act as outreach for CIO Council-AIC-FEA PMO-Departments and Agencies • Build on Foundation with strong focus on new Partnering Activities • New partners within government at additional levels • New relationships with Industry Standards and Professional Societies and Universities • Participate in Conferences: Management of Change, Executive Leadership Conference, others…..

7. Thought Leadership • Evolution of FEA Reference Models • Including Enterprise Transformation/Modernization • Effective Governance Techniques • Identification of Emerging Technology Process and connect to Business Innovation • Population of ET.gov • Security and Privacy Profile- Volume 3 • Design Guidelines for the Architecture-Designer • Collaboration with the Security and Privacy Professional and Service Component Providers • GAO Awareness and Support • Data Interoperability • Modeling, Methodology, Innovative Approaches and Gap Analysis and Standards needs • Bridge to OMG, OASIS, ISO or WS-I • Federal Health Architecture Data Interoperability Technology Thoughts • EAIG Awareness, Involvement and Support

8. Review • Component White Paper Update • Security and Privacy Profile- Volume 3 • Design Guidelines for the Architecture-Designer and Collaboration with the Security and Privacy Professional and Service Component Providers- work with the Security and Privacy SIG • EA Focus on Process and Integration with EA and SP SIG and recommend a set of Services similar to eAuthentication • Semantic Interoperability: Readiness today and Future Options Paper • USAF ISC Support: Support Standards Group

9. Participate and Collaborate • EA Maturity White Paper Completion- completed • Modifications to Components Repository – Core.gov • Recommend extensions with team • EA Tools Interoperability and Government Use Cases and needs definition of ontologies and glosssaries. • FEAF to GEAF Process and Guidelines and Alternatives • Vertical government integration • Chief Architects’ Forum Support • Support definition process and workshops • A130 Review/Changes Support

10. Outreach/Communication • IAC Conferences- Management of Change and Executive Leadership Council- Spring and Fall • NSF Workshops • Chief Architects’ Forum Support • EAIG Awareness, Involvement and Support • A130 Review/Changes Support • Identify other contract Opportunities • Receive out to new companies and explain EA to all the companies • Work with Universities- NDU, others…