Conceptual Architecture Document Template

QT Consulting Asia Pacific Conceptual Architecture Version 1 (Example Only) 18 February 2005 Conceptual Architecture Table of Contents Introducing Conceptual Architecture Principles........................................................... 3 Overview....................................................................................................................................3 Definition and Purpose.............................................................................................................4 Principles Identification Model ................................................................................................5 Conceptual Architecture Principles Vision.................................................................... 7 Conceptual Architecture Principles (CAPs) .................................................................. 8 CAP 1: Business alignment......................................................................................................8 CAP 2: Business consistency..................................................................................................9 CAP 3: Optimise for organisational benefit ..........................................................................10 CAP 4: Technology as an investment....................................................................................11 CAP 5: Whole of life-cycle ......................................................................................................12 CAP 6: Architecturally manage technology ..........................................................................13 CAP 7: Extended enterprise ...................................................................................................14 CAP 8: Equity of access .........................................................................................................15 CAP 9: Ease of access – Pervasive connectivity..................................................................16 CAP 10: Human productivity..................................................................................................17 CAP 11: Technology dependence..........................................................................................18 CAP 12: Corporate compliance..............................................................................................19 CAP 13: Information accuracy ...............................................................................................20 CAP 14: Information and knowledge management ..............................................................21 CAP 15: Information security.................................................................................................22 CAP 16: Continuous improvement ........................................................................................23 CAP 17: Adaptiveness, flexibility and agility ........................................................................24 CAP 18: Standardise, rationalise, centralise, componentise and Encapsulate..................25 CAP 19: Buy before build .......................................................................................................26 Conceptual Architecture Example (V1.0) Page 2 of 26 18 February 2005 Conceptual Architecture Introducing Conceptual Architecture Principles Overview QT’s Enterprise Architecture approach to the management and operation of technology is a holistic approach that focuses on improving the alignment between technology and the business’ information needs (i.e., the information and data that the organisation and its decision-makers require to attain the stated strategic objectives of the organisation). Further, the strengthening of this alignment enhances the organisation’s ability to trace technical investment decisions back to the organisation’s strategic objectives to enable management to weigh-up trade-offs and assess the contribution or impact of these tradeoffs. Additionally, the approach or framework allows the managers responsible for technology to assess how changes in the organisation’s strategic direction and objectives may impact the management and operation of the technology function. A fundamental benefit of this demonstrable alignment is enhanced and agreed understanding on the organisation’s overall approach to managing and operating the organisation’s technology. QT recommends this enhanced understanding be formally documented and broadly disseminated through a set of Conceptual Architecture Principles (CAPs). The series of CAPs presented in this document are illustrative only to provide the reader with greater insight into Conceptual Architecture. This set of CAPs was written by QT Consultants and have not been verified or endorsed as appropriate for adoption or use within Queensland Police Service (QPS). Conceptual Architecture Example (V1.0) Page 3 of 26 18 February 2005 Conceptual Architecture Definition and Purpose QT defines Conceptual Architecture Principles (CAPs) as “the agreed set of guiding principles that define the organisation’s approach to managing its technological assets”. Essentially, Conceptual Architecture Principles provide an essential communication link between the business and technology to help bridge the organisational gap and strengthen the alignment. The purpose of CAPs is to document the agreement between the business and technology managers regarding their shared fundamental beliefs relating to the management of the organisation’s technology. Hence it is fundamental that the CAPs are expressed in the language of the business and are free of technical terms and jargon. CAPs can be thought of as more detailed value statements or interpretations of the organisation’s general value statements to make them more applicable to technology. CAPs should represent the few points of stability upon which the organisation can construct and maintain its Technical Architecture (i.e., its Enterprise-Wide Technical Architecture within respect to QT’s Enterprise Architecture Framework. Consequently, these principles should have a ''timeless'' quality about them because they are defining the value system. Conceptual Architecture Principles may have somewhat of a ''motherhood'' characteristic. However, it's still important to define a ''value system'' that states the important shared values for the architecture. Conceptual Architecture Principles are a pivotal component of the Enterprise Architecture. They reflect consensus between the business and technology managers, and therefore the importance of these principles cannot be emphasised strongly enough, nor can the importance of their dissemination (e.g., via the organisation’s Intranet) as part of a socialisation or communications strategy or plan. The recommended structure and format is presented in Table 1 overleaf. Conceptual Architecture Example (V1.0) Page 4 of 26 18 February 2005 Conceptual Architecture Table 1 Information and Technology Management Principle Structure Component Principle Title Principle Definition Principle Justification Definition A punchy name for the principle. A paragraph that elaborates on the “Statement” to provide clarity as to the intention of the principle. The business and technical rationale for the adoption of the principle. In effect, this component discusses why this principle is included in the Conceptual Architecture. The currently cognised consequences of adopting this principle (e.g., a principle to introduce a new technology implies that people must trained in the technology). Principle Implications Principles Identification Model To ensure the set of Conceptual Architecture Principles are comprehensive QT recommends that a structured model be used to help identify principles. In determining the set of principles that apply to the XZY Group the dimensions described in Table 2, overleaf, were considered. Once a draft set of principles is identified it is paramount that time be taken to ensure the definitions, justifications and implications are consistent across each of the individual principles. It is suggested that before consensus is achieved, the set of principles will undergo several iterations. Whilst the effort expended to achieve consensus may appear excessive it should be noted that once consensus is reached it will serve the organisation well into the future and the resulting principles will endure as a reference base that will, over time, justify the expended effort. Conceptual Architecture Example (V1.0) Page 5 of 26 18 February 2005 Conceptual Architecture Table 2 Principle Identification Model Dimension Business Considerations Where technology “fits” within the organisational structure and its relationship with the Lines of Business and other business functions (e.g., Human resource management, financial management, risk management etc.) The emphasis the organisation places on technology and how the organisation approaches the financial management of its technological assets. How technology may be used to support and automate the organisation’s core business processes and the processes relating to the management and operation of technology How technology, its application, its management and operation may impact the human resources of the organisation. How can investment in, and application of, technology support the organisation’s people and enhance their work experience What are the qualities the organisation is striving across its information repositories (e.g., reach, richness, accuracy, timeliness, and completeness) What are the key over arching best practices that the organisation believes will assist it to achieve its desired financial return on technical investment Investment Processes People Information qualities Technology Conceptual Architecture Example (V1.0) Page 6 of 26 18 February 2005 Conceptual Architecture Conceptual Architecture Principles Vision Please note. The following vision statement is a QT draft only and should be critically reviewed by the management of XZY before this document is formally released. XZY’s Conceptual Architecture Principles will provide the Group with an enduring and stable foundation that supports and facilitates consistent information and technology decision-making and deployment Conceptual Architecture Example (V1.0) Page 7 of 26 18 February 2005 Conceptual Architecture Conceptual Architecture Principles (CAPs) CAP 1: Business alignment Definition Source: QT XZY will continuously ensure firstly, that as an organisation is cognisant of its changing business environment and secondly, that its IT investment and capability is demonstrably aligned with its defined corporate direction and is driven by the informational needs of the business Justification · IT must be viewed as a business enabler that effectively and efficiently provides access to the information needed to realise the corporate and business goals · The ability to re-organise itself in response to changing business and technical requirements is critical for XZY to remain competitive · The Technology Division must be able to realign XZY’s infrastructure and systems (i.e., Applications and infrastructure) in response to changing business, technology and informational requirements in a timely manner Implications · XZY should consider establishing a formalised process for external environmental scanning that includes a technology watch function · XZY must have an effective and efficient corporate and business planning process · XZY must be able to identify the need for change and the resulting opportunities and threats and therefore will require a business intelligence watch function and capability · XZY must have a formalised and effective change management process that incorporates a Return on Investment (ROI) evaluation · XZY must evaluate the effectiveness of implemented change in delivering the planned outcomes · XZY’s technical environment (i.e., its technical infrastructure and applications) must be designed and built to be adaptive and agile to accommodate changes in business needs Related Requirements of Technical Architecture (RTAs) Start here Conceptual Architecture Example (V1.0) Page 8 of 26 18 February 2005 Conceptual Architecture CAP 2: Business consistency Definition Source: QT XZY will continuously strive to enhance its understanding of its purpose and the most effective manner to deliver against its defined purpose. It will seek and exploit opportunities to rationalise and standardise its business activities, business information systems, defined authoritative sources for data and the human and technological interfaces to its systems. It will actively seek opportunities to disaggregate its business functions, programs, activities and processes to identify common elements that represent “best-of-breed” and promote adherence to these common elements and the reuse of these common elements. Justification · Business consistency drives economies of scale, resource use optimisation, adaptability and therefore cost effectiveness · Business process consistency is fundamental to achieving and delivering services online in a cost effective manner · Business consistency is critical to human productivity, flexibility and satisfaction Implications · XZY must intimately understand its organisational constitution, strategic direction, legal and social obligations, organisational boundaries and constraints · XZY must invest in defining, documenting and communicating its business processes and actively seek to rationalisation these processes and any automation of these processes · XZY must pro-actively foster a business culture that strives for business consistency and interaction across programs · XZY must implement a governance structure and compliance processes that fosters and promotes business consistency and adherence to common practises and standards Related Requirements of Technical Architecture (RTAs) Start here Conceptual Architecture Example (V1.0) Page 9 of 26 18 February 2005 Conceptual Architecture CAP 3: Optimise for organisational benefit Definition Source: QT XZY technology investment, management, operation and resource allocation will be optimised to deliver the greatest benefit to the Group. This implies that in some circumstances individual projects, subsidiary or cluster initiatives may be compromised in order to deliver greater Group-wide benefits or to align with the boarder organisational direction. Note, this principle does not imply that individualised solutions are not acceptable, it is emphasising the need and benefit of actively seeking to develop standardised solutions to business needs. Justification · Within XZY, there will always be conflicting and competing projects and subsidiary initiatives for the limited resources available. Taking a group-wide perspective to this matter and to the allocation of limited resources is the most fair and equitable mechanism for resolving such conflicts · Managing from the group-wide perspective (i.e., across all clusters and subsidiaries) provides the best opportunity to identify duplications of effort and opportunities for rationalisation to and to reuse solutions · The current autonomous subsidiary management within XZY has lead to duplications of efforts and technology investments · It is more cost effective to have specialised skills (e.g., business analysts, project management analyst/programmers) within a central pool that is shared across the Group, rather than for the individual subsidiaries to carry the costs of such resources within their budgets · World-wide there is a recognised IT skills shortage making the cost of available IT resources relatively high. It is therefore imperative that IT resources within XZY are highly productivity and available to address the needs of all subsidiaries Implications · XZY should review and assess its IT resources review how these resources are structured to optimise their productivity and availability to all XZY subsidiaries · XZY should invest in an IT Governance Structure and Compliance Processes to enhance its IT investment evaluation, approval and resource allocation processes · XZY should consider, as part of its Governance Structure and Compliance Processes, establishing a centralised Program Management Office (PMO) that is responsible for evaluating all change initiatives against its Enterprise Architecture to ensure compliance with the all architectural components and to identify project overlaps and opportunities for reuse · The XZY Enterprise Architecture and Governance and Compliance Processes must cater for tailored solutions to address unique requirements and ensure strict management of all such exceptions to avoid incremental divergence from the XZY Enterprise Architecture over time Related Requirements of Technical Architecture (RTAs) Start here Conceptual Architecture Example (V1.0) Page 10 of 26 18 February 2005 Conceptual Architecture CAP 4: Technology as an investment Definition Source: QT XZY will recognise its growing dependency upon technology and invest in, mange and promote technology as an enabler of effective product and service delivery using an IT portfolio management approach Justification · A significant percentage of XZY’s products and services delivery is dependent upon the effective deployment of technology · XZY is becoming more and more dependent upon technology for the development, delivery and monitoring of its business activities and performance · Technology investment decisions and budget allocation represent an increasing percentage of the XZY operational budget · The autonomous subsidiary management responsibility to technology investment has resulted in inefficient expenditure on technology Implications · XZY must acknowledge and account for its total investment in technology and seek to manage that investment as prudently as it manages any other capital investment (e.g., return on assets) and consider adopting an IT Portfolio Management approach · All investments in technology must be demonstrable aligned to a recognised business imperative and supported by a compelling, commercially oriented business case · XZY’s budget and financial reporting system must clearly identify IT capital and operational expenditure Related Requirements of Technical Architecture (RTAs) Start here Conceptual Architecture Example (V1.0) Page 11 of 26 18 February 2005 Conceptual Architecture CAP 5: Whole of life-cycle Definition Source: QT XZY will recognise that technology assets have a life cycle and manage its technology assets accordingly. It will also ensure that the total cost of all technology acquisitions over the entire life cycle of the asset are factored into the business case supporting the acquisition. A simple version of the technology life cycle is: Procure è Install è Commission è Operate è Maintain è Divest è Replace Justification · Technology operation and maintenance costs often represent a significant percentage of the total cost of ownership over the total life cycle · Technology assets are expensive and should be properly managed though out the life cycle to ensure that the maximum return of the investment is achieved · Technology assets are expensive and understanding their life cycle expectancy will assist XZY to prepare, schedule, budget and plan for their eventual replacement Implications · XZY should review its technology procurement policy, including its business case template, to ensure that it adequately reflects the organisation’s adopted technology asset life cycle and ensures the total cost of ownership is considered in all IT related acquisitions · XZY should centralise its IT asset procurement processes Related Requirements of Technical Architecture (RTAs) Start here Conceptual Architecture Example (V1.0) Page 12 of 26 18 February 2005 Conceptual Architecture CAP 6: Architecturally manage technology Definition Source: QT XZY will manage and operate its technology assets using a recognised holistic framework and associated processes to ensure that technology is responsive to and aligned with the needs of the business Justification · XZY is a dynamic business that is continuously changing. Change is often imposed upon it by external agencies and initiatives. Recognising its increasing dependence upon technology XZY must ensure that it manages its technology to be adaptive and agile to accommodate change in a timely manner. Developing and maintaining an Enterprise Architecture approach to technology management will assist XZY better accommodate changing business requirements. · Managing and operating technology assets using a recognised framework and process (i.e., QT’s Enterprise Architecture framework and processes) is recognised world-wide as “best practice” and ensures that technology it driven by the needs of the Group and is responsive to the change · Enterprise and Technical architecture frameworks and processes are now more mature and have been proven in large complex multi-national organisations and government departments and therefore represent a lower risk to XZY · Non-architectural approaches to managing and operating technology have failed to deliver against business expectations · Technology life cycles are continuously reducing making technology more dynamic which is increasing technology management and operational complexity · The proliferation of internet/intranet technologies simplifies distribution and maintenance of enterprise and technical architectures content · Adopting an architectural “best practice” technology management and operational framework will provide XZY with added confidence in accounting for its technology expenditure Implications · XZY must identify candidate technology management and operational frameworks; choose the most appropriate for its needs and adequately resource an implementation initiative · XZY must recognise that architecture is a process, not a once-off effort, and allocate adequate resources to maintain and evolve the architecture in perpetuity · XZY must implement an effective change initiative governance structure and compliance process and instil a governance and compliance mindset amongst its people including technology management and staff Related Requirements of Technical Architecture (RTAs) Start here Conceptual Architecture Example (V1.0) Page 13 of 26 18 February 2005 Conceptual Architecture CAP 7: Extended enterprise Definition Source: QT XZY will design and enable its business processes and systems to support inter-connection and interoperability with its extended business environment including its partners, suppliers, government agencies and customers wherever in they may be geographically located Justification · E-commence is forcing organisations to review all aspects of their operations, including how they interact with suppliers, customers and partners · Organisational partnering and networking is increasing and XZY is likely to enter into more joint ventures and strategic alliances · Organisations are becoming more specialised and therefore more dependent on other organisations to deliver holistic solutions and meet market expectations Implications · XZY’s business processes and systems must be designed to mitigate the greater risk that exposure to a broader enterprise implies · XZY must meet and support a common format for information exchange across the extended enterprise in accordance with its Enterprise Architecture especially its security requirements Related Requirements of Technical Architecture (RTAs) Start here Conceptual Architecture Example (V1.0) Page 14 of 26 18 February 2005 Conceptual Architecture CAP 8: Equity of access Definition Source: QT XZY will ensure that all customers will be able to access and use the XZY information and services in a fair and equitable manner irrespective of geographical location, time or access method Justification · Customers are becoming more informed and are demanding enhanced product and service flexibility and access · Customers are increasingly mobile and require flexible access to services via consistent interfaces · Equity of access may provide XZY with enhanced business opportunities (e.g., cross-selling of products and services) Implications · XZY information should be available in a consistent manner anytime, anywhere · XZY must ensure that information provided is consistent across all delivery methods and channels · XZY must ensure that its Security policy does not impede equity of access while at the same time information is only available to authorised persons · XZY must define process and system standards and conduct audits to ensure compliance to its standard processes and systems Related Requirements of Technical Architecture (RTAs) Start here Conceptual Architecture Example (V1.0) Page 15 of 26 18 February 2005 Conceptual Architecture CAP 9: Ease of access – Pervasive connectivity Definition Source: QT XZY will ensure that all its customers and stakeholders are able to gain access to the services and information that they are authorised to access easily and consistently irrespective of the access device. In a nutshell this is the age old principle of “Keep It Simple” Justification · XZY serves a wide variety of user groups. It cannot make assumptions regarding the technology that individuals have access to or regarding the technical competencies of those individuals and therefore must ensure that all users can access the information and services that they need or are interested in intuitively · Ease of access to information and services is essential to XZY’s internal productivity Implications · XZY activities have to enable consistent anytime, anywhere supplier, partner and customer interaction · XZY must ensure that information provided is consistent across all delivery methods and channels · XZY must ensure that its Security policy does not impede equity of access · XZY must define process and system standards and conduct audits to ensure compliance · XZY must extend its network service provision beyond its traditional organisational boundaries to enable it suppliers and customers ease of access to facilitate end-to-end integration of business processes · XZY must extend its network capabilities to move from fixed points for connectivity to pervasive “anywhere” connectivity Related Requirements of Technical Architecture (RTAs) Start here Conceptual Architecture Example (V1.0) Page 16 of 26 18 February 2005 Conceptual Architecture CAP 10: Human productivity Definition Source: QT XZY will invest in technology that enhances the productivity of its human resources both directly and indirectly. XZY will invest in technology that automates menial, repetitious tasks and allows its people to focus on activities requiring high order thinking Justification · The cost of human labour is increasing while the cost of technology is reducing · Human productivity falls when people perform menial, repetitious tasks and there is also an increased risk of injury · In general, people respond positively to increased responsibility and this leads to higher levels of employment satisfaction · When staff satisfaction is high productivity is also high Implications · XZY will measure and report on its human productivity and satisfaction · XZY should review its technology procurement policy to ensure that it considers and assesses the impact that the acquisition may have on its staff and their morale and productivity · XZY will ensure that its people are appropriately trained and can demonstrate a required level of competency in the deployed technology. Consider adopting a Human Capital Management approach. · XZY will assess the impact of changes in strategic direction on the required skills competencies and develop training programs to keep it staff skills current and aligned to the business direction · XZY should review its job/position descriptions, recruitment and contractor engagement processes to ensure that they adequately specify and account for the increasing use and dependence upon technology Related Requirements of Technical Architecture (RTAs) Start here Conceptual Architecture Example (V1.0) Page 17 of 26 18 February 2005 Conceptual Architecture CAP 11: Technology dependence Definition Source: QT XZY is becoming increasingly dependent upon technology to effectively and efficiently deliver its products and services and to meet Government and its own internal managerial, operational and reporting requirements. The “e-everything” boom is also contributing to XZY’s increasing technical dependence Justification · XZY’s ability to deliver products and services is increasing dependent upon its technology capability · XZY’s product and service delivery mechanisms are being enhanced by using emerging technologies (e.g., “the Internet”) · Malay Government reporting requirements are increasingly · Business managers requirements for timely, accurate and appropriate information is increasing · Technology costs are decreasing while human labour costs are increasing · XZY must embrace and invest in technology if it is to remain competitive with both nation and international organisations Implications · XZY needs to make appropriate investments in technology research, acquisition / development and implementation to enhance service delivery and to have a framework to evaluation and guide technical investments · Business managers must become more technically savvy to better understand how technology can enhance their lines of business · XZY must develop and maintain an internal capabilities (for consistency, development of tactical knowledge, richness of understanding, business analyst effectiveness) to understand the business requirements and identify where technology may add value · All staff must be trained to a minimum level of competency in the use of the XZY standard desktop and applications critical to their employment positions · All staff must be trained to a minimum level of competency in the use of the XZY specific business applications · XZY may need to review its recruitment policy to ensure new employs are technically literate Related Requirements of Technical Architecture (RTAs) Start here Conceptual Architecture Example (V1.0) Page 18 of 26 18 February 2005 Conceptual Architecture CAP 12: Corporate compliance Definition Source: QT XZY will acknowledge its corporate obligations and invest in technology that is compliant with the corporate requirements imposed upon it Justification · Corporate breaches have significant political, social, legal and cost implications · XZY must be able to demonstrate how it is socially and economically acquiescent to the process of government and must lead by example in its adherence to legislative requirements · Being a “good” corporate citizen can enhance market place credibility Implications · XZY must be cognisant of all its corporate requirements including: · Occupational Health and safety · Equal Employment Opportunity · Privacy Act · Freedom of information · Religious and cultural expectations · XZY must review its current performance against corporate requirements and identify any breaches and address these immediately Related Requirements of Technical Architecture (RTAs) Start here Conceptual Architecture Example (V1.0) Page 19 of 26 18 February 2005 Conceptual Architecture CAP 13: Information accuracy Definition Source: QT XZY will design its business processes and systems to ensure information collected, stored and disseminated can be relied upon Justification · Information accuracy is required for: · Legislative obligations · Corporate requirements · Financial management and accountability (FMA) · Business opportunity analysis and development · General decision making · To reduce the current plethora of data inconsistencies · To mitigate the potential to disseminate misinformation Implications · XZY must identify and define its data and information requirements and develop a comprehensive Information Architecture to document and communicate these requirements · XZY must develop and maintain a consistent meta data set · XZY must identify a single authoritative source for all data items Related Requirements for Technical Architecture (RTAs) Start here Conceptual Architecture Example (V1.0) Page 20 of 26 18 February 2005 Conceptual Architecture CAP 14: Information and knowledge management Definition Source: QT XZY will value, manage, protect and leverage its information and knowledge as a strategic assets to improve decision making and enhance its outcomes Justification · Knowledge and information sharing can contribute to XZY’s bottom line · Leveraging knowledge proactively will enhance organisational learning · Managing information and knowledge will contribute to improving decision making effectiveness · Mismanagement of information and knowledge adversely impacts the quality of decisions · To comply with corporate requirements for records and document management · Well structured information and knowledge repositories support changes in business requirements (e.g., Changing organisational structure reporting and meeting joint venture partners information requirements) Implications · XZY must acknowledge that information and data are assets and therefore manage these assets accordingly using a recognised asset management life-cycle model · XZY must continue to invest in the development and maintenance of comprehensive information and knowledge bases · XZY must continue to invest in the refinement of a comprehensive set of information policies and practices · XZY must invest in an electronic document and records management system incorporating electronic mail · XZY must have a well defined and simple document classification scheme to facilitate archival and security policy requirements Related Requirements for Technical Architecture (RTAs) Start here Conceptual Architecture Example (V1.0) Page 21 of 26 18 February 2005 Conceptual Architecture CAP 15: Information security Definition Source: QT XZY will develop and maintain best practice for the protection of its people, information and assets Justification · XZY has an obligation to protect its information and IT assets from “misuse” and unauthorised access, either accidentally or deliberately, in accordance with Privacy and other legislative and corporate obligations · Misuse of XZY information may dissipate XZY’s intellectual property · Information can be a source of competitive advantage Implications · XZY must authenticate all persons that access any XZY information · XZY must implement and maintain information access audit trails in accordance with the XZY security policy · Failure to adopt this approach may cause XZY to be in breach of Malay corporate law · XZY must have a well defined and simple document and meta data classification scheme to facilitate security policy implementation · XZY must have a secure, electronic data, information, document and records transmission capability to disseminate information to stakeholders within and beyond its organisational boundaries Related Requirements for Technical Architecture (RTAs) Start here Conceptual Architecture Example (V1.0) Page 22 of 26 18 February 2005 Conceptual Architecture CAP 16: Continuous improvement Definition Source: QT XZY will fully assess all change proposals for alignment with the Group’s vision, strategic direction and the components of its Enterprise Architecture for compliance and to ensure each proposed change represents an acceptable level of risk to the Group Justification · To ensure all proposed changes and projects are business driven and align with strategic goals and the principles, best practices and standards as defined and documented in the XZY Enterprise Architecture · To maximise return on technology investments and minimise the likelihood of incompatibility · To ensure that individual subsidiary change proposals are optimised from the XZY Group perspective rather than from a project perspective. Implications · XZY must implement and to continue to enforce adherence to its change initiative assessment framework and processes · XZY must monitor all change initiative progress and measure change implementation effectiveness and the on-going benefits derived from the change · XZY must establish, resource and maintain a centralised Program Management Office and develop procedure and processes to support its use Related Requirements for Technical Architecture (RTAs) Start here Conceptual Architecture Example (V1.0) Page 23 of 26 18 February 2005 Conceptual Architecture CAP 17: Adaptiveness, flexibility and agility Definition Source: QT XZY actively strive to design, build and invest in technology that enhances the adaptiveness, flexibility and agility of its technological environment to optimise its capability to be reconfigured and realigned to accommodate changes in business direction and objectives in a timely, cost effective manner Justification · XZY operates in a highly dynamic environment and is constantly required to react to commercial imposed changes as well as internally motivated changes · Increasing the adaptiveness, flexibility and agility of technology can extend the productive life-cycle of technological assets and therefore increase the derived return on investment Implications · XZY should review its technology procurement policy and identify any clauses that may impact the adaptiveness, flexibility and agility of acquired assets (e.g., always accept the lowest tendered price) · XZY should review how technology assets are specified and introduce criteria that ensure the specified technology will meet expected short to mid – term demand increases · XZY should adopt the notion that its technology must be “highly granular” and “loosely coupled” and actively, over time, replace technology installations that are inflexible Related Requirements for Technical Architecture (RTAs) Start here Conceptual Architecture Example (V1.0) Page 24 of 26 18 February 2005 Conceptual Architecture CAP 18: Standardise, rationalise, centralise, componentise and Encapsulate Definition Source: QT XZY will continuously seek opportunities to: · Rationalise: optimise the physical number of technology assets in each asset class · Standardise: reduce or eliminate variation between assets in each asset class · Centralise: physically house technology assets in common locations · Componentise: develop highly granular modules and processes that can be reused many times · Encapsulate: Limiting the interconnections between things by reducing the way different classes of components interact. In general, infrastructure should be exposed and consumed as a service that encapsulates as much of the underlying technology components as possible. Justification · Standardising, rationalising, centralising and componentising technology increases adaptiveness, flexibility and agility · Standardising, rationalising, centralising and componentising technology assets is recognised as world’s best practice · Standardising, rationalising, centralising and componentising technology enables organisations to increase the effectiveness and productivity of scarce human expertise · Standardising, rationalising, centralising and componentising technology enables organisations to leverage economies of scale to introduce more sophisticated automated management practices that otherwise would not be cost effective or justifiable · Componentising technology assets recognises that capacity and performance requirements do not increasing uniformly across of asset classes (e.g., server power and storage volumes) Implications · XZY must evolve and maintain its Enterprise Architecture and ensure that it has well defined and up-to-date technical standards for every technical category. Further, this information must be broadly distributed and available across the XZY group. QT recommends that XZY publish its Enterprise Architecture on its intranet · XZY must identify technology assets that are non-standard and develop strategies to replace these assets with standardised components over time · XZY must establish geographically centralised locations to house its IT assets Related Requirements for Technical Architecture (RTAs) Start here Conceptual Architecture Example (V1.0) Page 25 of 26 18 February 2005 Conceptual Architecture CAP 19: Buy before build Definition Source: QT XZY will adopt buy before build mindset toward technology. Therefore XZY will actively seek to acquire proven, commercially available technology first and to the extent possible only build technology that provides competitive advantage Justification · There is an increasing plethora of commercially available technology and solutions available · More mature commercially available solutions provide industry based templates that are aligned with best practices · By “buying” technical solutions enables XZY to leverage the vendors economies of scale · Building solutions is historically a costly and risky activity (e.g., more that 75% of IT projects fail to deliver all of their espoused benefits) · Building customised solutions only serves to promoted non-standardisation of both business processes and technology solutions Implications · XZY must ensure that its IT procurement processes are well defined, efficient and effective · XZY must maintain an internal capability to specific is technical requirements and evaluate candidate products and solutions · XZY must introduce centralised processes to critically assess the need and justification to “build” a customised solution for any aspect of its business or for subsidiary Related Requirements for Technical Architecture (RTAs) Start here Conceptual Architecture Example (V1.0) Page 26 of 26