- Value [1] Communities of Services
- Communities of Services (COS) creating suites of shared services.
- Value [2] Life Cycle Events
- Rationalized government response to the breadth of issues related to Life Cycle Events. A Life Cycle Event is a common incident
in a citizen’s life requiring interaction with multiple Communities of Service. A Life Cycle Event can trigger responses within
a wide spectrum of government and non-government entities. The diagram, Figure 3, illustrates some of these interactions.
An example of a Life Cycle Event is a health emergency. The event may trigger service needs from several agencies at the federal,
state and local levels and may be tracked or supported by other government and non-government entities. A health event can
cascade through multiple Communities of Service requiring data notification. For instance the Public Safety COS would have
to be notified if the event is a viral outbreak of pandemic proportions. Education could be involved in terms of school closings.
Such a health emergency could also identify environmental issues that require tracking. At present, these COSs, though possibly
connected to each other, are typically not integrated. Unsurprisingly, citizens experience frustration when they must interface
separately with many government agencies at multiple levels, wasting time for both the citizen and the government and resulting
in errors, inefficiencies and increased costs. Erroneous and/or conflicting data in various systems lead to poor services
or no service at all. The logical solution is the familiar “enter once/multiple use” single point of data entry cascading
across the network of COSs that relate to various Life Cycle Events. Multiple use also presents opportunities to seek process
streamlining and consolidation. Given the breadth of agencies, non-governmental organizations, private sector and academic
institutions that may be involved in supporting these Life Cycle Events, opportunities will materialize for major business
process transformation and consequent cost savings. The advent of Web 2.0 and its social networking capabilities will have
an impact on COSs in multiple areas. Citizen Enabled Open Government must have the agility to respond effectively to new requirements
based on changing demographics, legislation, technologies or community needs. To do so it must be able to reorganize, when
necessary, the COSs around which the Life Cycle Event is organized--or create new ones. This requires a process for integrating
new stakeholders into the New Life Cycle Event, for redesigning process flows and adapting government processes to ensure
effective oversight of the new enterprise.
- Value [3] Service Integration Model
- A Service Integration Model that allows these services to be provided virtually, agilely and adaptively. Service Integration
Models aim to achieve agile and adaptive operation among stakeholders who must coalesce around emergent issues quickly and
flawlessly. The Services Integration Model, depicted in Figure 4, consists of four main components: * Mission Mediation focused
on managing strategic themes of the enterprise. Resources Management focused on allocating resources needed to execute the
themes. * Quality Assurance to ensure appropriate results are achieved. * Collaboration Tools to ensure that stakeholders
work in a transparent and effective environment. Those components will be accessible via Cloud Computing and supported by
Metadata, Service Capabilities such as management routines, and Process Collaboration.
- Value [4] Service Oriented Government
- Service Oriented Government (SOG) establishing value chains of services across agencies and levels of government (described
in greater detail in Chapter 4).
- Value [5] Stewardship/Accountability
- To address the issues of stewardship and accountability, citizens need feedback mechanisms, such as Wikis and other channels
that would allow them to correct inaccurate data (if they have authority). CEOG will provide citizen access to shared data,
spreading the risk and accountability for its maintenance, accuracy, integrity and privacy among participating agencies. Administrators
will have to evaluate trade offs between ease of access and privacy of data. Public confidence will quickly erode if suspect,
inaccurate or erroneous data leads to bad decisions or outcomes.
- Value [6] Adaptability and Agility
- For the Life Cycle Event model to work properly, it should rapidly adapt to new circumstances, such as laws mandating new
service requirements. As circumstances change, the underlying architectures will use “plug and play” and “hot-swap” features
to add or subtract COS capabilities, thereby avoiding down time, unnecessary delays or service gaps.
- Value [7] Organizational Transformation
- Organization of Life Cycle Events will result in identification of service overlaps among the agencies and relevant COSs,
presenting opportunities for service consolidations and streamlining of operations across government.
- Value [8] Technological Innovation
- (e.g., Cloud Computing) Appropriately exchanging and managing data around Life Cycle Events requires, Cloud Computing capability,
which enables multiple agencies and their customers to share common, networked computer resources.
- Value [9] Acquisition and Allocation of Resources
- The ability to acquire the IT assets, including Cloud infrastructure, needed to support enterprise-wide solutions, will require
resolving issues of ownership and allocation of resources across the enterprise.
- Value [10] Governance
- As organizational transformation occurs, new governance structures must be adopted. A more in-depth discussion of this issue
can be found in Chapter 7.
|
