<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="stratml.xsl"?>
<StrategicPlan><id/><Name>Information Technology Enterprise Architecture</Name><Description/><OtherInformation>Initially (2008), my articles tended to be in the question/answer format, and then I changed to a discussion format.  These discussion articles tended to focus on the relationship between the Enterprise Architect and the CIO.  Then I wrote a couple of articles about President Obama's investment areas:  Health, Education, and Energy.  (Whenever I am reminded of his investment areas, which now includes manufacturing (including research and development I believe), I think about how Enterprise Architecture could help formulate associated plans.)  Now (2010 and 2011), I am back to relationships again, and my articles are in the form of a discussion.  (I have created a CIO who is usually thoughtful and engaging.  I wish all of you could work for my imaginary CIO.)  Another thing I wanted to do is to explain to CIOs and Enterprise Architects what Enterprise Architecture is all about.  Maybe discussions can be more useful than PowerPoint slides and lectures.</OtherInformation><StrategicPlanCore><Organization><Name>George W. Brundage</Name><Acronym>GWB</Acronym><Identifier>_fa8d1fb4-702a-11e4-b1c9-146c2ea89478</Identifier><Description>I initially developed, along with a large number of federal employees, the Federal Enterprise Architecture Framework (FEAF) for the federal government...
Brief Background:  I received a B.A. from Wright State University and M.A. from the University of Cincinnati.  I retired in June 2004 from the federal government and am living in Ocean View, Delaware and Alexandria, Virginia.  I was an Enterprise Architect at the Department of the Treasury and the Department of Homeland Security.  I MC’ed the ArchitecturePlus Program for several years at the General Services Administration (GSA) and the Department of the Treasury.  </Description><Stakeholder><Name>Enterprise Architects</Name><Description>The Enterprise Architect should allocate activities and data to new systems. </Description></Stakeholder><Stakeholder><Name>Terry Hagle</Name><Description>When I first started working on Enterprise Architecture, I had a conversation with Terry Hagle of DoD about how difficult it was to find a contractor or academic institution that understood what we needed.  Admittedly, we did not know what we needed, but we knew what we did not need.  We wanted a way to sort things out at a higher level.  One thing for sure, we did not want to get specific, because we did not want to get drowned in details.  Also, I had trouble with the Acquisition orientation of GSA and with Capital Planning, which seemed shallow and had no way to get on top of things.</Description></Stakeholder><Stakeholder><Name>Michael Porter</Name><Description>Eventually, I found ideas from people like Michael Porter, John Zachman, Steven Spewak, Bernie Boar, and Mitre and SAIC folks, that were on the mark. </Description></Stakeholder><Stakeholder><Name>Bernie Boar</Name><Description/></Stakeholder><Stakeholder><Name>CIO Council</Name><Description>I got involved with the CIO Council's initial enterprise architecture effort, which described the grants and international trade federal activities.  Some DoD enterprise architecture products were used for this effort, which gave rise to ideas to reduce redundancy in federal systems and fragmentation of federal organizations.  There was also a better understanding and appreciation of the DoD enterprise architecture products.  </Description></Stakeholder><Stakeholder><Name>Mitre</Name><Description>I worked with many great people from Mitre.  They had the knowledge of the DoD products.  Also, these people understood the need to focus on at a  higher level.  Other support contractors were too specific.  </Description></Stakeholder><Stakeholder><Name>DHS</Name><Description>When I was at Homeland Security, I concentrated on the agency's enterprise architecture where I again worked with many great people, particularly an excellent Enterprise Architecture Support Contractor, SAIC.  </Description></Stakeholder><Stakeholder><Name>SAIC</Name><Description/></Stakeholder><Stakeholder><Name>DoD</Name><Description>Although I spent a lot of time on the DoD products, I never lost my preference for Enterprise Architecture Planning and the ideas of John Zachman and Steven Spewak.  It was planning.  How could it be wrong?  </Description></Stakeholder><Stakeholder><Name>John Zachman</Name><Description/></Stakeholder><Stakeholder><Name>Steven Spewak</Name><Description/></Stakeholder><Stakeholder><Name>OMB</Name><Description>If I were still involved, I would be looking over OMB's Lines of Business for opportunities that might be pursued, both in terms of integration of systems and reorganization of government organizations...
To kick start the forum, I have made several recommendations to OMB.</Description></Stakeholder></Organization><Vision><Description>Information Technology (IT), the substructure, supports the business, the superstructure.</Description><Identifier>_fa8d220c-702a-11e4-b1c9-146c2ea89478</Identifier></Vision><Mission><Description>To provide you with a "map" for Enterprise Architecture or how to proceed.</Description><Identifier>_fa8d24a0-702a-11e4-b1c9-146c2ea89478</Identifier></Mission><Value><Name>Analysis</Name><Description>The idea behind Enterprise Architecture Planning is that one should begin at the top with the analysis and not eliminate this or that activity or data; thus, preventing integration and standardization. </Description></Value><Value><Name>Integration</Name><Description/></Value><Value><Name>Standardization</Name><Description/></Value><Value><Name>Planning</Name><Description>I believe in IT planning.  I cannot imagine IT Planning and Investment Control without Enterprise Architecture Planning.  If you cannot see the business model (including activities, data, organizations and actors, business cycles, and locations, goals and objectives) in the current systems, then IT is not supporting the business.  One should not create new systems without a top-down understanding of the business.</Description></Value><Value><Name>Flexibility</Name><Description>Your "map" may differ in many ways from mine.  However, we have to remind ourselves that "there is more than one way to skin a cat."  It pays to be flexible.</Description></Value><Value><Name>Clarity</Name><Description>I keep asking myself whether there is a way to make the Enterprise Architecture Planning steps more clear?</Description></Value><Value><Name>Feedback</Name><Description>Absent feedback, the best I can do is to hope that others are listening and finding my thoughts to be of value...
Please send me emails or participate in the forum.  I like feedback.</Description></Value><Goal><Name>Data</Name><Description>Centrally manage data objects to encourage data sharing.</Description><Identifier>_fa8d25d6-702a-11e4-b1c9-146c2ea89478</Identifier><SequenceIndicator>1</SequenceIndicator><Stakeholder><Name>OMB</Name><Description/></Stakeholder><OtherInformation>OMB should centrally manage data objects to encourage data sharing. President Obama drew attention to the failure to coordinate intelligence gathering in his book, which I believe is a result of poor data management. Well, what has been done? However, intelligence data is only one federal activity that could use better data management. If OMB monitored data objects, they would be focusing or monitoring things that are important to the U.S. Government, for example, data objects related to health, education, welfare, research and development, security, and environment and energy. OMB should ensure that federal agencies provide the same answer consistently over time. Most significantly, OMB should decrease confusion over data definitions. Maybe OMB is satisfied with tracking and monitoring certain performance measures, but this is not good enough. OMB should set up a control system to manage data objects.</OtherInformation><Objective><Name/><Description/><Identifier>_fa8d26b2-702a-11e4-b1c9-146c2ea89478</Identifier><SequenceIndicator/><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective></Goal><Goal><Name>Administrative Systems</Name><Description>Consolidate federal administrative systems.</Description><Identifier>_fa8d27a2-702a-11e4-b1c9-146c2ea89478</Identifier><SequenceIndicator>2</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>OMB should consolidate federal administrative systems using Enterprise Architecture concepts as the foundation. OMB needs to focus on redundancy and overlapping activities. (GAO has a report, GAO 11 3188P, dated March 2011, which addresses opportunities to reduce potential duplication. (See: http://www.gao.gov/new.items/d11318sp.pdf) I would want to these opportunities to eminate from a Federal Enterprise Architecture. If so, the opportunities might be systematically identified using a top down aproach. Absent a Federal Enterprise Architecture that spawns opportunities for improvement, I suppose one would have to settle for a listing of GAO identified opportunities no matter how they were identified. Also, Sens. Lieberman and Warner introduced the Reforming and Consolidating Government Act of 2012.) You can see the administrative areas that I have in mind in my first article, but they include: personnel, finance, etc. (Of course, OMB should also create funded program offices to integrate cross.cutting administrative systems. See recommendation No. 3 below.) President Obama said in his book that nonessential programs should be consolidated. Well, what has been done? OMB should complete Enterprise Architecture Planning, which includes a business model, current analysis, target analysis, gap analysis, migration plan, and capital investment plan for each federal administrative area. I am more concerned about redundant and overlapping activities than nonessential programs. (President Obama, at least at the time he wrote his book, focused on nonessential programs, but I expect more. Maybe my orientation toward the elimination of redundant and overlapping activities is a result of being an Enterprise Architect?) 

In regard to the business side of the federal government (as opposed to the administrative side of the federal Government), OMB should request that DoD and the State Department provide a security and nation building enterprise architecuture(s). Then presidential candidate Obama in his book expressed concern about intelligence coordination. In the book, Don't Know Much about History by Kenneth C. Davis, the author says, "

"There is another issue, as Americans have learned since September 11, 2001, a new generation's day of infamy. Having intelligence and using it well are two very different things. The left hand does not always now what the right is doing, as the FBI and CIA demonstrated in revealing the pieces of the puzzle they had before the terrorist attacks of September 11."

Besides intelligence, other enterprise architectures would be useful like environment and energy, health, welfare, research and development (manufacturing), security in general, and education. In each of these Enterprise Architectures, I would like OMB to pay special attention to resources and capabilities that are required to make the activity a success. </OtherInformation><Objective><Name/><Description/><Identifier>_fa8d2888-702a-11e4-b1c9-146c2ea89478</Identifier><SequenceIndicator/><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective></Goal><Goal><Name>Applications &amp; Components</Name><Description>Develop common applications and components for each administrative area.</Description><Identifier>_fa8d2964-702a-11e4-b1c9-146c2ea89478</Identifier><SequenceIndicator>3</SequenceIndicator><Stakeholder><Name>OMB</Name><Description/></Stakeholder><OtherInformation>For each administrative area, OMB should develop common applications and components. (These are software units that support multiple activities, projects, and processes.) My experience has been that there are few bureaus in the government that can successfully develop software, which is the reason that I propose the establishment of program offices for the further development of activity Enterprise Architectures planning and implementation of Enterprise Architectures. Establishing program offices reduces the risk for OMB and the agencies and bureaus. Unfortunately, most government folks, particularly the Capital Planning Offices, are pretty much unaware of the import of common applications and components. (Common components and applications make up the core of integrated projects and may be used by a large number of users and other projects.)</OtherInformation><Objective><Name/><Description/><Identifier>_fa8d2a68-702a-11e4-b1c9-146c2ea89478</Identifier><SequenceIndicator/><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective></Goal><Goal><Name>Business Area Stewards</Name><Description>Appoint Business Area Stewards for each federal activity.</Description><Identifier>_fa8d2b58-702a-11e4-b1c9-146c2ea89478</Identifier><SequenceIndicator>4</SequenceIndicator><Stakeholder><Name>OMB</Name><Description/></Stakeholder><Stakeholder><Name>Business Area Stewards</Name><Description>These folks can help out with process improvement from a federal perspective. The Business Area Stewards should be aware of the overlapping activities being performed within the government, and have a sense of which agencies have experience with performing an activity. Business Area Stewards should question the assignment of activity to agencies that have little experience with that activity. It seems a bit risky to expect agencies to perform an activity for which they have little experience. </Description></Stakeholder><OtherInformation>OMB should appoint Business Area Stewards for each federal activity, who have sufficient power to prevent manipulation by OMB, and the agencies and bureaus.</OtherInformation><Objective><Name/><Description/><Identifier>_fa8d2c48-702a-11e4-b1c9-146c2ea89478</Identifier><SequenceIndicator/><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective></Goal><Goal><Name>Exhibit 300</Name><Description>Submit Exhibit 300s by federal activity.</Description><Identifier>_fa8d2d4c-702a-11e4-b1c9-146c2ea89478</Identifier><SequenceIndicator>5</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>OMB should request that 300s be submitted by federal activity. This will help OMB to see the overlap that is taking place at the federal level. </OtherInformation><Objective><Name/><Description/><Identifier>_fa8d2e32-702a-11e4-b1c9-146c2ea89478</Identifier><SequenceIndicator/><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective></Goal><Goal><Name>FEA Framework</Name><Description>Develop a Federal Enterprise Architecture Framework.</Description><Identifier>_fa8d2f22-702a-11e4-b1c9-146c2ea89478</Identifier><SequenceIndicator>6</SequenceIndicator><Stakeholder><Name>OMB</Name><Description/></Stakeholder><OtherInformation>OMB should develop a Federal Enterprise Architecture Framework.</OtherInformation><Objective><Name>Zachman Framework</Name><Description>Adopt the first row of the Zachman Framework.</Description><Identifier>_fa8d3026-702a-11e4-b1c9-146c2ea89478</Identifier><SequenceIndicator>6.1</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>At a minimum, federal agencies should adopt the first row of the Zachman Framework. </OtherInformation></Objective></Goal><Goal><Name>Systems Inventory</Name><Description>Inventory, identify, describe, and characterize existing system(s).</Description><Identifier>_fa8d312a-702a-11e4-b1c9-146c2ea89478</Identifier><SequenceIndicator>7</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>OMB should insist that a current analysis be completed that includes an inventory, and the identification, description, and characterization of existing system(s). </OtherInformation><Objective><Name>Value &amp; Fit</Name><Description>Assess the business value, technical value, and architecture fit of each system(s).</Description><Identifier>_fa8d3224-702a-11e4-b1c9-146c2ea89478</Identifier><SequenceIndicator>7.1</SequenceIndicator><Stakeholder><Name>Federal Agencies</Name><Description/></Stakeholder><OtherInformation>The agencies should assess the business value, technical value, and architecture fit of each system(s). (This recommendation goes along with recommendation No. 5 above.) </OtherInformation></Objective></Goal><Goal><Name>Planning, Standardization &amp; Integration</Name><Description>Encourage Enterprise Architecture Planning, and standardization and integration based on common activities and data.</Description><Identifier>_fa8d331e-702a-11e4-b1c9-146c2ea89478</Identifier><SequenceIndicator>8</SequenceIndicator><Stakeholder><Name>OMB</Name><Description/></Stakeholder><OtherInformation>OMB should encourage Enterprise Architecture Planning, and standardization and integration based on common activities and data.</OtherInformation><Objective><Name>Implementation</Name><Description>Implement plans.</Description><Identifier>_fa8d34ae-702a-11e4-b1c9-146c2ea89478</Identifier><SequenceIndicator>8.1</SequenceIndicator><Stakeholder><Name>OMB</Name><Description/></Stakeholder><Stakeholder><Name>Federal Agencies</Name><Description/></Stakeholder><OtherInformation>Of course, implementation is just as important as planning, and OMB should not think that they can walk away from implementation. Of course, the same applies federal agencies. OMB should demand to see agency business analysis, target analysis, current analysis, migration plan, and capital investment plan. OMB needs to see any products associated with the effort, in particular, opportunities for improvemment. I would like to see greater forcus on Enterprise Architecture planning and implementation. (The Federal Government has made Enterprise Architecture Planning its chosen methodology in everything but name.) (See: Steven Spewak, Enterprise Architecture Planning, 1992)</OtherInformation></Objective></Goal><Goal><Name>Activities, Databases &amp; Data Objects</Name><Description>Identify all participants in federal activities and databases/data objects, or who should be participating in federal activities and databases/data objects.</Description><Identifier>_fa8d35a8-702a-11e4-b1c9-146c2ea89478</Identifier><SequenceIndicator>9</SequenceIndicator><Stakeholder><Name>OMB</Name><Description/></Stakeholder><OtherInformation>OMB should identify all participants in federal activities and databases/data objects, or who should be participating in federal activities and databases/data objects.</OtherInformation><Objective><Name>Interface Memorandums</Name><Description>Create interface memorandums that include all participants.</Description><Identifier>_fa8d36d4-702a-11e4-b1c9-146c2ea89478</Identifier><SequenceIndicator>9.1</SequenceIndicator><Stakeholder><Name>OMB</Name><Description/></Stakeholder><OtherInformation>OMB should ensure that interface memorandums of understanding are created that includes all participants.</OtherInformation></Objective></Goal><Goal><Name>EA Budgets</Name><Description>Review Enterprise Architecture budgets and make appropriate recommendations.</Description><Identifier>_fa8d37c4-702a-11e4-b1c9-146c2ea89478</Identifier><SequenceIndicator>10</SequenceIndicator><Stakeholder><Name>OMB</Name><Description/></Stakeholder><OtherInformation>OMB should review Enterprise Architecture budgets and make appropriate recommendations for augmenting or decreasing the amount. If Enterprise Architecture is not in the budget then it is not really a meaningful performance measure. </OtherInformation><Objective><Name/><Description/><Identifier>_fa8d38be-702a-11e4-b1c9-146c2ea89478</Identifier><SequenceIndicator/><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective></Goal><Goal><Name>IT Commission</Name><Description>Create an Information Technology Commission similar to the previous DoD BRAC commission.</Description><Identifier>_fa8d3a1c-702a-11e4-b1c9-146c2ea89478</Identifier><SequenceIndicator>11</SequenceIndicator><Stakeholder><Name>OMB</Name><Description/></Stakeholder><OtherInformation>OMB should create an Information Technology Commission similar to the previous DoD BRAC commission.</OtherInformation><Objective><Name/><Description/><Identifier>_fa8d3b3e-702a-11e4-b1c9-146c2ea89478</Identifier><SequenceIndicator/><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective></Goal><Goal><Name>Outcomes</Name><Description>Use outcome related performance measures.</Description><Identifier>_fa8d3c42-702a-11e4-b1c9-146c2ea89478</Identifier><SequenceIndicator>12</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>OMB should prevent the manipulation of performance measures by agencies and force agencies to use outcome related measures. If a project will reduce costs, it should be a performance measure and be in the budget.</OtherInformation><Objective><Name/><Description/><Identifier>_fa8d3d78-702a-11e4-b1c9-146c2ea89478</Identifier><SequenceIndicator/><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective></Goal><Goal><Name>Business Value</Name><Description>[Institute] agency performance measures associated with the degree that IT supports the business.</Description><Identifier>_fa8d3e72-702a-11e4-b1c9-146c2ea89478</Identifier><SequenceIndicator>13</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>OMB should insist on agency performance measures associated with the degree that IT supports the business. Recognizing that the business is the substructure, and information technology is the superstructure, OMB needs to ensure that agencies make the connection. </OtherInformation><Objective><Name/><Description/><Identifier>_fa8d3f76-702a-11e4-b1c9-146c2ea89478</Identifier><SequenceIndicator/><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective></Goal><Goal><Name>Cooperation</Name><Description>Direct cooperation among CIO staff members.</Description><Identifier>_fa8d40b6-702a-11e4-b1c9-146c2ea89478</Identifier><SequenceIndicator>14</SequenceIndicator><Stakeholder><Name>CIOs</Name><Description/></Stakeholder><Stakeholder><Name>CIO Staff</Name><Description/></Stakeholder><OtherInformation>The direct reports to the CIOs should be required to cooperate with the Enterprise Architect, including, among others Directors of: 

- Security
- Capital Planning and Investment Control
- Standards
- Process Redesign,
- Applications,
- Data, 
- Communications, and 
- Infrastructure</OtherInformation><Objective><Name/><Description/><Identifier>_fa8d41e2-702a-11e4-b1c9-146c2ea89478</Identifier><SequenceIndicator/><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective></Goal><Goal><Name>Security</Name><Description>Incorporate security into the Enterprise Architecture.</Description><Identifier>_fa8d4318-702a-11e4-b1c9-146c2ea89478</Identifier><SequenceIndicator>15</SequenceIndicator><Stakeholder><Name>OMB</Name><Description/></Stakeholder><OtherInformation>OMB should make sure that security is incorporated into the Enterprise Architecture by insisting that security be identified in the lists and models.</OtherInformation><Objective><Name/><Description/><Identifier>_fa8d446c-702a-11e4-b1c9-146c2ea89478</Identifier><SequenceIndicator/><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective></Goal><Goal><Name>Application &amp; Data Directors</Name><Description>Appoint Application and Data Directors.</Description><Identifier>_fa8d45a2-702a-11e4-b1c9-146c2ea89478</Identifier><SequenceIndicator>16</SequenceIndicator><Stakeholder><Name>OMB</Name><Description/></Stakeholder><Stakeholder><Name>CIOs</Name><Description/></Stakeholder><Stakeholder><Name>Application Directors</Name><Description/></Stakeholder><Stakeholder><Name>Data Directors</Name><Description/></Stakeholder><OtherInformation>OMB should insist that the CIO's create Application and Data Directors reporting to them.</OtherInformation><Objective><Name/><Description/><Identifier>_fa8d46f6-702a-11e4-b1c9-146c2ea89478</Identifier><SequenceIndicator/><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective></Goal><Goal><Name>Chief Enterprise Architects</Name><Description>Make Agency Chief Enterprise Architects equivalent in rank to the CIO's. </Description><Identifier>_fa8d4872-702a-11e4-b1c9-146c2ea89478</Identifier><SequenceIndicator>17</SequenceIndicator><Stakeholder><Name>OMB</Name><Description/></Stakeholder><Stakeholder><Name>Chief Enterprise Architects</Name><Description/></Stakeholder><Stakeholder><Name>CIOs</Name><Description/></Stakeholder><OtherInformation>OMB should ensure that the Agency Chief Enterprise Architects are equivalent to the CIO's.</OtherInformation><Objective><Name/><Description/><Identifier>_fa8d4994-702a-11e4-b1c9-146c2ea89478</Identifier><SequenceIndicator/><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective></Goal><Goal><Name>Funding</Name><Description>Fund federal efforts.</Description><Identifier>_fa8d4ad4-702a-11e4-b1c9-146c2ea89478</Identifier><SequenceIndicator>18</SequenceIndicator><Stakeholder><Name>OMB</Name><Description/></Stakeholder><OtherInformation>OMB should ensure that federal efforts are funded. </OtherInformation><Objective><Name/><Description/><Identifier>_fa8d4c46-702a-11e4-b1c9-146c2ea89478</Identifier><SequenceIndicator/><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective></Goal><Goal><Name>Customer Service</Name><Description>Improve processes to provide effective and efficient customer service.</Description><Identifier>_fa8d4d86-702a-11e4-b1c9-146c2ea89478</Identifier><SequenceIndicator>19</SequenceIndicator><Stakeholder><Name>OMB</Name><Description/></Stakeholder><Stakeholder><Name>Citizens</Name><Description/></Stakeholder><OtherInformation>OMB should focus on improving processes to provide effective and efficient customer service. Processes are just as important as outcomes, because most citizens interact with specific agency and bureau processes.</OtherInformation><Objective><Name>Information Exchanges</Name><Description>Analyze the information exchanges between the government and its citizens.</Description><Identifier>_fa8d4ea8-702a-11e4-b1c9-146c2ea89478</Identifier><SequenceIndicator>19.1</SequenceIndicator><Stakeholder><Name>Government</Name><Description/></Stakeholder><Stakeholder><Name>Citizens</Name><Description/></Stakeholder><OtherInformation>The processes to improve can be determined from an analysis of the information exchanges between the government and its citizens. (OMB needs to remember that improving internal procedures may be necessary to improve external procedures. Internal and external procedures are often linked.)</OtherInformation></Objective><Objective><Name>Users</Name><Description>Identify user classes.</Description><Identifier>_fa8d5010-702a-11e4-b1c9-146c2ea89478</Identifier><SequenceIndicator>19.2</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>Another way to identify processes for improvement is through identifying user classes, for example, contractors, welfare recipients, etc., and then focusing on the information exchanged.</OtherInformation></Objective><Objective><Name>Business Rules</Name><Description>Create business rules to control and limit processes.</Description><Identifier>_fa8d5146-702a-11e4-b1c9-146c2ea89478</Identifier><SequenceIndicator>19.3</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>Finally, business rules should be created and should control and limit processes.</OtherInformation></Objective><Objective><Name>Testing</Name><Description>Develop processes to test federal activities.</Description><Identifier>_fa8d529a-702a-11e4-b1c9-146c2ea89478</Identifier><SequenceIndicator>19.4</SequenceIndicator><Stakeholder><Name>OMB</Name><Description/></Stakeholder><OtherInformation>OMB should develop processes to test the identified federal activities. </OtherInformation></Objective></Goal><Goal><Name>De-Funding</Name><Description>Identify systems for de-funding.</Description><Identifier>_fa8d53f8-702a-11e4-b1c9-146c2ea89478</Identifier><SequenceIndicator>20</SequenceIndicator><Stakeholder><Name>OMB</Name><Description/></Stakeholder><OtherInformation>OMB should state what agency systems will no longer be funded based on Agency or Federal Enterprise Architecture Migration Plans.</OtherInformation><Objective><Name>Accountability</Name><Description>Hold the CIOs acountable for the identification of systems that will no longer be supported.</Description><Identifier>_fa8d551a-702a-11e4-b1c9-146c2ea89478</Identifier><SequenceIndicator>20.1</SequenceIndicator><Stakeholder><Name>OMB</Name><Description/></Stakeholder><Stakeholder><Name>CIOs</Name><Description/></Stakeholder><OtherInformation>OMB should hold the CIOs acountable for the identification of systems that will no longer be supported rather than "passing the buck" to the project managers, etc.</OtherInformation></Objective></Goal><Goal><Name>Project Reviews</Name><Description>Reestablish the committee to review and help with failing projects.</Description><Identifier>_fa8d566e-702a-11e4-b1c9-146c2ea89478</Identifier><SequenceIndicator>21</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>OMB should ensure the reestablishment of the committee to review and help with failing projects.</OtherInformation><Objective><Name/><Description/><Identifier>_fa8d57fe-702a-11e4-b1c9-146c2ea89478</Identifier><SequenceIndicator/><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective></Goal><Goal><Name>Services</Name><Description>Identify suites of common services.</Description><Identifier>_fa8d5970-702a-11e4-b1c9-146c2ea89478</Identifier><SequenceIndicator>22</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>As part of the standards effort, suites of common services should be identified.</OtherInformation><Objective><Name/><Description/><Identifier>_fa8d5b46-702a-11e4-b1c9-146c2ea89478</Identifier><SequenceIndicator/><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective></Goal></StrategicPlanCore><AdministrativeInformation><StartDate/><EndDate/><PublicationDate>2014-11-19</PublicationDate><Source>http://www.enterprisearchitectureit.info/</Source><Submitter><FirstName>Owen</FirstName><LastName>Ambur</LastName><PhoneNumber/><EmailAddress>Owen.Ambur@verizon.net</EmailAddress></Submitter></AdministrativeInformation></StrategicPlan>