Escolar Documentos
Profissional Documentos
Cultura Documentos
Chapter VII
ABSTRACT
The Singapore government enterprise architecture is a blueprint that will provide a holistic view of business functions, supporting data standards, and IT systems and services, regardless of the organisational structure and ownership of these functions and systems. The blueprint will also enable analysis of IT investments and their alignment to business functions, as well as facilitate collaboration among government agencies. When implemented, the Singapore government enterprise architecture will help bring about transformation in public sector by yielding optimised end-to-end business processes and system capabilities in alignment with government enterprise needs and missions.This chapter presents the considerations and approach taken to develop the Singapore government enterprise architecture. It examines the linkages of enterprise architecture with other initiatives such as the e-government action plans, policies, and processes related to IT governance, as well as summaries of lessons learned.
INTRODUCTION
The Singapore government enterprise architecture is a blueprint that will provide a holistic view of business functions, supporting data standards, and information technology (IT) systems and services, regardless of the organisational structure
and ownership of these functions and systems. It comprises four elements and reference models for the business, information, solution, and technical architectures. Of the four elements, the technical architecture has been developed in 2002 while the other three are currently being developed.
Copyright 2007, Idea Group Inc., distributing in print or electronic forms without written permission of IGI is prohibited.
The Singapore government enterprise architecture is to support e-government, and in particular, realise the outcomes of networked government where many agencies integrate across organisational boundaries to provide citizencentric services.
SINGAPORE E-GOVERNMENT
E-government is about enabling our government to harness info-communications technology (ICT) to better serve our citizens and businesses, and to deliver public services with greater convenience, effectiveness, and efficiency. For the Singapore public service, our e-government journey started in 1980 with the launch of the Civil Service Computerisation Programme.
the public sector in the delivery of public services by harnessing ICT technology. Launched in June 2000, the vision of the first eGAP was to be a leading e-government to better serve Singapore and Singaporeans in the new knowledge-based economy. The objective was to foster a shared vision of a leading e-government in the new millennium, develop a public sector that could contribute positively and work actively at propelling Singapore forward in the new economy, and provide a framework for informed, coordinated, and flexible ICT deployment. To move businesses, citizens, public officers, and the government toward the e-government vision, the first eGAP prescribed the broad directions of ICT deployment with five strategic thrusts and six programmes. The five strategic thrusts of the first eGAP were: 1. 2. Re-inventing government in the digital economy. Delivering integrated electronic service delivery. Being proactive and responsive. Using infocomm technologies to build new capabilities and capacities. Innovating with infocomm technologies.
3. 4. 5.
The six programmes identified to drive the strategic thrusts in the first eGAP include: 1. 2. 3. 4. 5. 6. Knowledge-based workplace. Electronic services delivery. Technology experimentation. Operational efficiency improvement. Adaptive and robust infocomm infrastructure. Infocomm education.
The key focus of the first eGAP was transforming the way the public sector interacts with its customers. Primarily, all public services deemed feasible for electronic delivery were designated for this transformation. The public sector would
130
need to better understand the impact of ICT, continually innovating and adapting business and operational processes to re-engineer, and totally transform the way things were done. In line with Singapores vision for service excellence, this plan would see an increase in the number of electronic services or e-service provisions to customers in three frontscitizens, businesses, and within the public service. The first eGAP covered the period 2000 to 2003. By the time it concluded in 2003, its achievements and accolades include the following: 1. One of the most advanced e-governments in the world as reflected in international benchmark studies by third parties. Singapore was ranked among the top leading e-governments by both accenture and the world economic forum, and also won several international e-government awards. Over 1,600 public e-services have been implemented. In a study of e-governments
3.
worldwide, Singapore was ranked second by Brown University at putting public services and information online. Our citizens are generally satisfied with e-government and with the quality of our e-services.
2.
While the first eGAP had provided the common vision for agencies in their ICT deployment, it was important to continue to engage all agencies in the conceptualisation and implementation of common systems, especially with gradual decentralisation of budgets as well as ICT deployment decisions to these agencies. Continual efforts would have to be put in to encourage and ensure that agencies pool their resources in the development of ICT applications with similar functionalities. Such engagement and customer-centric approach to delivering public services from the foundation laid by first eGAP would continue into the second eGAP.
Networked Government
Fostering Inter-Agency Collaboration
131
Our efforts in implementing e-services have been recognised internationally as well. Notably, we received the United Nations Public Service Award 2005 for the Online Business Licensing Service (www.business.gov.sg), an integrated e-service, which offers businesses a total of 69 licenses from 19 government agencies and allows 80% of all start-ups in Singapore to apply online for the licenses needed to start their businesses. The award was given to recognise the governments efforts to streamline, simplify, and integrate the application of licences from various agencies to save time and costs for enterprises. Overall, we have continued to do reasonably well for eGAP II and our achievements have ensured that Singapore continues to be ranked amongst the leading e-governments by international benchmarking studies conducted by the World Economic Forum, Accenture, and United Nations e-government survey.
132
platforms across agencies became paramount. Moreover, cost benefits could be realised through the use of common systems and platforms for the deployment of e-services, and demand aggregation for the procurement of compatible technology products. Hence, a practical approach by way of a public sector service-wide technology standard for agencies was necessary. This technology standard blueprint called the service-wide technical architecture (SWTA) was developed to provide a consistent framework for the effective management and protection of the public sectors IT assets that were implemented across the agencies. According to META Group (1999b), the development of such a technical architecture still offered the greatest opportunity for IT organisations to deliver prompt value to their business.
The SWTA, which was one of the key initiatives under the first eGAP, helped to create a better environment for interoperability and information sharing within the public service. The first five domain architectures in SWTA were published in October 2002. By April 2003, a total of nine domain architectures, as shown in Figure 2, were developed and published.
Application
Data Management
Middleware
Platfo (Clien t)
rm (S
erver)
Security
133
architectures was to explore the development of enterprise architecture. This programme, identified in eGAP II, would increase cross-agency collaboration and systems integration, enable more innovative and business-transforming projects to be initiated and completed, and improve the public services ability to anticipate and respond to rapid changes in the technology landscape when successfully executed. Reviews were conducted to glean insights into enterprise architecture practices, their implementation at a government-wide level, and the approaches taken by other e-governments. Some of the key findings are summarised next starting from enterprise architecture components and concepts, and expanding into their implementations in other countries. 1. Enterprise architecture would comprise four elements, namely the business, information or data, solution or application, and technical architectures according to META Group (1999a, 1999b), U.S. CIO Council (1999) and the Open Group (2002). An architectural framework provided a logical structure for classification and organisation of the four architecture elements, as well as guidance for developing architecture and systems implementation. TOGAF and Zachman were some of the frameworks reviewed. The open group architectural framework or TOGAF, originally used for developing technical architectures, was enhanced in the current version to develop other enterprise architectures elements as well. TOGAFs strength would be its architecture development method, a generic process consisting of eight phases for developing architecture (Open Group, 2002). The Zachman framework consisted of a two-dimensional matrix classification scheme in six columns (by what, how, where, who, when, and why) and five rows (by plan-
3.
4.
2.
ner, owner, designer, builder, and contractor perspectives) for describing an enterprise appears comprehensive (Zachman, 1997). However, the Zachman framework did not have a process for developing an enterprise architecture, and the completion of such a matrix, either partially or full, for the wholeof-government seemed daunting. In a government environment, enterprise architecture was deemed to be applicable at both government-wide and agency levels. Although both enterprise architecture implementations were conceptually similar, the construct was more complex in a government-wide context due to the scale and range of functions and diversity of the environment. Government-wide enterprise architecture provides a service-wide perspective of business functions and their IT initiatives. In this context, the Canadian and U.S. Federal Governments have published reference models. The enterprise architecture effort in Canada comprises the business transformation enablement program and the governments of Canada strategic reference models, which had evolved over the last 15 years from the municipal level governments reference model called the public service reference model to the provincial level government 10 years ago (Canada Treasury Board Secretariat, 2004). In the United States, the federal enterprise architecture reference model framework comprised the performance, business, service component, data, and technical reference models. These five reference models provided a classification scheme for government business operations and IT assets, and enabled the U.S. Federal Governments identification of collaboration opportunities and initiatives within five lines of business. In addition, it also facilitated the analysis of IT budgets and investments (U.S. Government Accountability Office, 2004;
134
5.
U.S. Office of Management and Budget, 2005). It was also noted that the deliverables, documentation, and approaches for enterprise architecture were varied. Carbone (2004) had described that existing enterprise architecture approaches were too complex and theoretical and had proposed a simpler and improvised approach, such as the use of the Gane/Sarson methodology for diagramming. Whittle and Myrick (2005) asserted that formal models and architectures were virtually nonexistent for business enterprises and highlighted several models to describe a business architecture enterprise. Lastly, Perks and Beveridge (2002) had
articulated the well-established processcentric TOGAF phases with clearer descriptions and details for practitioners use. These reviews from authors-practitioners showed that enterprise architecture deliverables and approaches needed to be fit for purpose intended and required customisation. Hence, the Singapore government would adopt a federated architecture approach similar to the United States government. Reference models would need to be developed to serve as the wholeof-government enterprise architecture framework, with a suitable methodology and/or process as part of the framework to provide the guidance for architectural development. These reference models would enable new initiatives and projects
135
on common business functions and IT assets to be identified. The architectural documentation requirements would require continual research and localisation.
4.
delivery in a systematic and well-disciplined manner. Technical architecture: This element details the organisations technology strategies, its extended technology linkages, and their impact on business initiatives.
Our Approach
Out of the four elements in SGEA, only the business, information, and solution architectures would need to be developed as the technical architecture element was already addressed by the SWTA. The development of these EA elements would require substantial time and resource, and the same for its maintenance as well. Some of the key considerations underpinning the formulation of the strategy for the SGEA programme are as follows: The implementation of a government-wide EA would enable the identification of common business processes to be streamlined, duplicative systems to be consolidated, and common systems to be implemented, leading to overall efficiency and effectiveness. The Singapore government had previously implemented several service-wide initiatives, which effectively constitute components of an EA. In developing the three remaining elements in SGEA, the strategy would be to leverage on these existing initiatives rather than start from scratch. There was a need for early results to demonstrate value and relevance of enterprise architecture to all stakeholders. Hence, the EA deliverables were intended to be purpose-driven, focusing on usefulness and relevance rather than comprehensiveness. Lastly, the implementation of SGEA would be a means to effect business transformation in the Singapore public sector.
2.
3.
136
government-wide lines of businesses and business functions. This would be sufficient to methodically identify agency collaboration opportunities or determine the need for common service-wide initiatives. A top-down whole-of-government and business-driven approach was preferred for the development of government BA. Executive sponsorship and strong participation of business personnel was key to the success of the government BA effort. The stakeholders included chief information officers and corporate planning and strategic planning directors who were engaged for their directions throughout the BA development process. Their inputs and information on the business functions and agency level priorities were analysed and integrated into the government BA. This enabled government leaders to focus on priority areas instead of being overwhelmed by the voluminous information available. The information for government BA was compiled into a structured format called the Singapore
Community Development
Economic Development
Family Development
Homeland Security
National Defense
Culture &Recreation
Energy Management
Environmental Mangement
Financial Assistance
Monetary Collection
Workforce Management
Asset Management
Administrative Services
Public Communications
Professional Services
Finance
Human Resource
Transportation
Education
Health
137
government business reference model, which defined the business operations of the government using terminologies that were common across all government agencies as shown in Figure 4 diagram and described next. 1. The business reference model in Figure 4 has two broad categories of lines of businesses. Under the services to public category are 24 lines of businesses, which are external facing services that the Singapore government provides to citizens, businesses, and external stakeholders. Examples of these include the family development, public transportation, and revenue collection lines of businesses. Under the corporate & supporting services category are nine lines of businesses representing all activities that support the delivery of services provided by the Singapore government to the public and all activities to operate the government effectively. Examples of these include project & logistics management, human resources, finance etc. Within each line of business are a set of related business functions and descriptions. For instance, continuing education & training and primary and secondary education are two business functions under the education line of business. In addition, the business reference model would also include a set of cross-functional matrix of business functions performed by government agencies.
streamlining opportunities, resulting in generic business processes for use across the government or within a sector. The generic business processes and related information will then be incorporated as part of the desired future state (i.e., target architectures).
2.
3.
The Singapore government business reference model will be used to identify business functions that: (a) are resource-intensive or (b) are potential candidates for inter-agency collaboration. Each common business function within could comprise business processes with the potential for streamlining. The identification of such common business processes would facilitate optimisation and
138
5. 6. 7.
At the point of writing, the focus for the DRM was on the data elements in the existing three data hubspeople hub, business hub, and land hub. At present, the three data hubs have mechanisms established to facilitate the sharing of commonly used people, land, and businesses-related data. The people hub is a centralized database on common non-sensitive people data (e.g., contains unique identification number (UIN) for all Singapore citizens and residents). The land hub is a one-stop resource centre for comprehensive and accurate digitised land data in map and textual forms. The fundamental land base information includes buildings, roads, and cadastral data, which are the basic land information that are required in the development of most map-based systems. The business hub is a centralized database containing a comprehensive range of information pertaining
to businesses in Singapore. The types of business data captured include company/business identification number and particulars, company/business profile, name history, capital, and shareholders share details. The initial DRM is planned for release in 2006. The envisioned seamless information exchange between data owners, government agencies, and the public resulting from the use of the DRM and implementation of government IA is depicted in Figure 5.
139
systems and services identified from collaboration opportunities and common business processes drawn from the government BA and existing ICT systems consolidated and implemented as shared components, which are reusable by agencies. Cost savings can then be better realised through such consolidation and standardization efforts. At the point of writing, the government SA was at the stage of development. The government SA is targeted for implementation from 2007-2010 and would cover several public facing services as well as corporate and supporting services.
provides a semantic framework for information sharing and interoperability of systems amongst all agencies. A review process is carried out every half-yearly with agencies to ensure the currency of SWTA and its relevance to enterprise architecture development. The SWTA architectural principles are highlevel statements that describe preferred practices followed in the design and deployment of ICT in the public sector. The principles covered the following: (a) infrastructure reuse, (b) modular architecture, (c) open standards, (d) robustness, scalability, adaptiveness, and performance. The SWTA framework consists of domain architectures, which are logical groups of related technologies. The content of each domain architecture includes: 1. 2. Technology components: Description of relevant technology components. Technology standards: International and industry standards that apply to the technology components selected and their status in terms of technology maturity. Products: These are specific products in this domain.
3.
140
4.
5.
6.
7.
Interoperability standards: The standards and requirements that are mandatory for inter-agency interoperability. Central services: Government-wide services that have been implemented and may be leveraged in this domain. Best practices: Guidelines or practical advice based on the experience and research of project teams for implementing specific domain technology components or products. Technology watch: Promising technologies that warrant further research and analysis for purpose of the domain.
(f) middleware, (g) platform, (h) network, and (i) security. A diagram showing the nine SWTA domain architectures within is given in Figure 6.
There are nine domain architectures and these include: (a) application, (b) collaboration and workflow, (c) data management, (d) distributed environment management, (e) internet/intranet,
MA SECU NA RIT GE Y ME NT
lu Va tal dy To Stu
UE AL L V TION TA TO LUA EVA
COBIT
AUDITING
S SYSTEM Y UIT CONTIN ENT ASSESSM
PROCUREMENT / BESTSOURCIN G MANAGEMENT
CT G OJE PR EWIN VI RE
M CH AN A A N GE GE M EN T
MA
ITIL
CMMI
APPLICATION MANAGEME NT
IM
141
be used to help them understand EA better and focus on showing the outcome. It is necessary to leave the technical blueprints in the boiler room. Work on some easier areas that will meet less resistance from business owners to demonstrate quick wins and successes. EA is developed iteratively and evolves over time. Look at common areas and pick out three priority areas to focus on. Good governance is critical to the EA programme. The governance structure of an EA programme typically involves many stakeholder and working level committees. Leverage on existing committees and structures, where possible. Integrate EA into established forums for IT Governance within the organisation, if possible.
ICT deployment, and describes the positioning of the governance pieces as shown in Figure 7. The framework adopts a lifecycle approach positioning IT governance needs and concerns around the agencys long term IT vision. The tools, policies, and methodologies are also positioned in the overview so that agencies can understand how these aids can help them. It is structured as a three concentric-layered onion with the IT vision of the agency in the centre: 1. 2. The first layer consists of the four-lifecycle stages of plan, invest, deploy, and control. The second layer breaks this down into processes that an agency should consider for each stage. The third layer identifies the policies, methodologies, and tools that best serve the agency in addressing the processes.
3.
This framework helps chief information officers and IT managers to first understand the considerations necessary to achieve IT effectiveness. It then directs their attention toward the tools and policies that address the individual considerations. The agency starts in the plan stage of the framework and examines and establishes the alignment of ICT and business goals through strategic planning and other processes including enterprise architecture. All of these processes require long-term mapping and need to be done at the beginning stage of the lifecycle. With the plan for the next few years in place, the agency then moves to the invest, deploy, and control stages for its IT investments where there are other tools like IT portfolio management and risk management methodology to provide guidance. The positioning of enterprise architecture within this framework, which according to SloanMIT Research, form part of the IT governance equation (Weill & Ross, 2004). This will help agencies to better align IT assets and to do more
142
with less by identifying and re-using components for shared systems and services, and will eventually articulate the real benefits of doing enterprise architecture.
Carbone, J. A. (2004). IT architecture toolkit. Upper Saddle River, NJ: Prentice Hall. Gartner Inc. (2005, February). Takes steps to improve government data sharing and reuse (ID Number: G00125749). Stamford, CT. META Group. (1999a). Enterprise architecture strategies process modelEvolution 1999. Stamford, CT. META Group (1999b). Holistic enterprise architecture: Beyond EWTA. Stamford, CT. Perks, C., & Beveridge, T. (2002). Guide to enterprise IT architecture. New York: Springer. The Open Group (2002). TOGAF, Version 8 Enterprise Edition. Retrieved from http://www. theopengroup.org/ U.S. CIO Council. (1999). Federal enterprise architecture framework version 1.1. Retrieved from http://www.cio.gov U.S. Government Accountability Office. (2004). The federal enterprise architecture and agencies enterprise architecture are still maturing. Retrieved from http://www.gao.gov U.S. Office of Management and Budget. (2005). Federal enterprise architecture. Retrieved from http://www.whitehouse.gov/omb/egov/a-1-fea. html Weill, P., & Ross, J. W. (2004). IT governance on one page (CISR WP No. 349 and Sloan WP No. 4516-04). Cambridge, MA: Massachusetts Institute of Technology. Whittle, R., & Myrick, C. B. (2005). Enterprise business architecture: The formal link between strategy and results. Boca Raton, FL: Auerbach Publications. Zachman J. (1997). Zachman framework for enterprise architecture. Retrieved from http://www. zifa.com
CONCLUSION
Over the years, the ICT goals and priorities of the Singapore government had evolved. Starting from one focussing on productivity and operational efficiency in the eighties, to one emphasising onestop, non-stop services in the nineties, and now on cross-agency, integrated public service online, we have come a long way. Architecting IT systems, whether at the agency or public service level, has always been seen as a means to the larger end of supporting the prevailing ICT goals and priorities. The establishment of data hubs to enable multilateral data sharing in 90s, and the implementation of the service-wide technical architecture in 2002 to facilitate systems interoperability were in practice early enterprise architecture efforts, though never labelled nor positioned as such. The formulation of the Singapore government business reference model, identification of common business functions and processes and their prioritisation to guide subsequent development of information exchange framework and data reference model, as well as the eventual deployment of solution architectures are all but examples of our pragmatic approach toward architecture development. The focus on meeting business needs and the principle of pragmatism will continue to guide us in the future work of developing and maintaining the Singapore government enterprise architecture.
REFERENCES
Canada Treasury Board Secretariat. (2004). Business transformation enablement program. Retrieved from http://www.tbs-sct.gc.ca/index_e.asp
143