Date: 08/17/2004 ExpeditionWorkshop/BestPracticesRepository_Group_7    (2B6)

3. Best Practice Repository:    (2B7)

a. What do we mean by repository?    (2B8)

i. A place where you store things or data, and then retrieve it when you have a need. It should be organized. ii. What is important, the storing or retrieving? We should start backward by asking what I might need and design the repository based on it. Some times people design repository based a law. This is not a good approach iii. It should serve stakeholders!!! Always start with this question!! Example from the health care, how much does it cost and how much does it serve our patients? When there is a question about a disease or certain case, then you click and retrieve the info quickly. Another stakeholder is the physician and the policy maker… in short the repository should serve all stakeholders at any time and low cost. Health policy makers are considering the cost of effectiveness of the health electronic record. This is also a way to build a best practice iv. Available repository needs to be proven based on knowledge, serve multiple stakeholders base on multiple users needs, system enterable base on accepted standers v. Effective open repository to find a specific solution-- for a specific problem is a challenge – how to utilize the open sources to serve a specific problems. vi. Benchmarking as a tool to enhance the repository richness vii. There is value and components that make it valuable. The transaction cost must be low so people can benefits from viii. How can we build a repository work? The people who are part of it!!! The incentives and obligations understood…. Communicate the missions and visions    (2B9)

b. How to generate the repository (brainstorming, case studies, audit...?    (2BA)

i. Incentives, enterprise architecture, market the success, leadership, identified the champion ii. Keep it simple, easy to use and retrieve iii. Grass root driven iv. Cover the needs v. Start small and be customer driven vi. There should be an interface standards – user side vii. It should be strategy driven viii. Series of links interface standards that they are linked to each other ix. There should be a trust model embedded in the process—cultural driven through the process    (2BB)

c. How should this information be classified, formatted, organized, maintained?    (2BC)

i. Standardization, domain specific standers, be facilitated for awareness process, consensus ii. What kind of categorizing!!! What is the key access factor? Health IT imitative iii. Customer oriented classification system, identify roles of leadership iv. The content should be valid—the content and updating the content    (2BD)

d. General comments:    (2BE)

e. Political issues and its impact on PB in the government.    (2HQ)

f. Enterprise architecture is there and we need to make it as good as possible to serve the organization    (2HR)

g. The Internet is an example of fast growing movement that people reacted to incorporated into their enterprise architecture. IT should be integrated in the enterprise architecture    (2HS)

h. Executive sandbox – enterprise architecture content where people as each others what is going on    (2HT)

i. To generate BP, you have to have the architecture keys with the employees. Benchmarking is again is a good tool    (2HU)

j. Different users have different understanding and definitions for the same things--- this is a challenge in the EA and PB arena… this means we need a standards. This is why we need a manager or moderator who may understand what in there and that does the users request mean ?    (2HV)

k. NOAA – what are the business questions that needed to build an architectures – then what are these components needed, then populate it and pilot it    (2HW)