We pasted in the "Breakout Group Task Template" and then expanded it.    (25V)

Membership:    (25W)

==============================================================================    (2G9)

Charles "Chuck" Heazel Chief Technologist Lockheed Martin / OpenGIS Consortium    (25X)

Firefighter, get in get out quick. One finger in NCES, Other IC initiatives. I see a lack of understanding of how move forward. There is no one who owns everything.    (28Z)

EA is a business , not IT project. The "BASF" of IT.    (290)

No major project - no failures, no accomplishments.    (291)

==============================================================================    (2G2)

Charlie Martinez MITRE CEM FFRDC Senior Architectural Advisor    (25Y)

Currently starting a new EA framework for CIO council. Cross-Federal DODAF, Treasury EAF. Works with Ken Hoffman. Unifying Framework for Enterprise Modernization. A management discipline.    (27L)

Accomplishment: Father of DODAF C4ISR framework.    (27M)

Was with ACS Defense Systems --> Popkin SA C4ISR.    (288)

==============================================================================    (2G3)

Jana Crowder, Noblestar CSE    (25Z)

Got involved with the CIO council on the theme of re-use. Found during pilot project that information management for several ITIM functions was a topic of interest that was a natural extension of the latest s/w viewpoints on component management (eg, "software/systems development asset management".    (2QV)

Got involved with component registries that link large grained BUSINESS components (eg, legacy systems, SOAs, web services) with finer grained DISTRIBUTED components of those systems (eg, java, .net, or c++ code, UML diagrams, Rose models, etc.) in a way that can serve up real-time information to be used in several ways.    (2QW)

These uses include determining what systems exist for reuse (potential link to A300 database, FEAMS, actual linkages to internal agency systems at their locations), what larger or fine grained components of those systems exist for reuse, what real-time information to use in Metis or Popkin models for various activities (versus the current laborious process of collecting and tracking information about the systems), what real-time information to use for PART reports, etc.    (2QX)

Specifically for managing legacy systems, major packaged applications, and home-grown applications... metadata repository specifically for software development. Once linked to existing repositories, provides real-time data for management reporting and use, as well as for use by software developers and federal contractors. Can be aligned w/ multiple enterprise architectures within a single agency or across multiple agencies in a secure manner.    (2QY)

Understanding that government is managing EA from models that are out of date by the time the data is aggregated for large, complex, dynamic, agencies. Hysteresis. I.e. New technologies often are outside of existing agency EAs and agencies like DHS may find EA requires updates constantly.    (2QZ)

Differs from semantic search technologies and asset auto-discovery technologies in that provides engine for secure management of, and reporting about, asset use. Real-time use versus one-time use (ie, semantic search good for one-time info. aggregation but must do something with info that one time and asset-auto discovery produces results, but is not a run-time management system)    (2R0)

Modeling in Metis and Popkin, asset auto-discovery, semantic search are complementary solutions.    (28A)

The pilot is complete and information is available on www.web-services.gov under "Federated Registry Pilot Summary" presented on August 16, 2004. Two products that met all criteria include Logidex and Flashline. Noblestar prefers Logidex; Microsoft and IBM both actively use Logidex.{nid 26N}    (2R1)

Also enables management of software development methodologies and best practices alongside the very technologies they address.    (270)

==============================================================================    (2G4)

Elsa Rhoads<br> KM Architect<br> Pension Benefit Guaranty Corp.    (260)

Management Consultant - KM Architect since 2000. We deepen Business need driven CoPs. Deep into EA, in medium sized agencies. Rationalize applications, we are deep into training.    (289)

My task is to combine KM (content, change, - trust, transparency and education) and EA.    (28B)

Portal Technology drives KM. It used to be an enabler.    (28C)

Professional Accomplishment Ph.D. Dissertation from GWU on Knowledge Management and its Correlation to Successful eGov.    (28D)

==============================================================================    (2G5)

Mark A Frautschi, Ph.D. Independent Consultant    (261)

Physicist by training. Passionate about human-technical interface. Budding enterprise architect. thought leader on EA-OD (Organization Development or KM) interface.    (292)

Co-discoveror of the top quark.    (293)

http://mysite.verizon.net/frautsch/    (2ES)

==============================================================================    (2G6)

Collaborative Expedition #34 Breakout Groups Task Template    (24Q)

2. Best Practice content:    (24W)

a. What information (assets) does the user community need?    (24X)

How do you scope an enterprise? Given that the business components and IT assets of an enterprise can be shared across multiple enterprises (i.e. Federal health architecture, VA, DoD etc. share share components e.g. humans.)    (294)

How to view an enterprise:    (295)

How do we guarantee consistency and coherency of the four views?    (2GD)

This is why you start with the data reference model for the enterprise, not end with it.    (2A8)

The whole idea behind semantic interoperability is to provide a layer that bridges different data models.    (2A9)

How does an organization respond to rapid changes in its external environment and still keep our EA focus? Our EA techniques must respond in a timely manner to rapidly changing business environments.    (2BZ)

Boyd's OODA loop. http://www.belisarius.com/modern_business_strategy/sessions/planning.htm    (2D5)

Architecture should be vendor, technology neutral.    (2D1)

Open standards are good or necessary, depending on the enterprise and its scale and coupling. For a tightly coupled enterprise, open standards are not necessarily good, for a loosely coupled enterprise, they are essential.    (2CB)

Start with the human stakeholders and their data (data + human = knowledge).    (2B3)

Go only to the level of detail appropriate to answer the problem.    (2C9)

b. Define good, better, Best Practices.    (24Y)

Depends on the beholder - may be different for different stakeholders. Use the appropriate tool of the problem.    (2C8)

c. What is the criteria/certification for best?    (24Z)

The fact that it HAS been successfully used. What are the appropriate metrics?    (2CA)

3. Best Practice Repository:    (252)

a. How to generate the repository (brainstorming, case studies, audit...?    (253)

DoD XML Registry - exemplar of policies, procedures and governance.    (2D2)