Government Enterprise Architecture. GEA-NZ v3.0 Application and ICT Services Reference Model and Taxonomy November 2014

Transcription

1 Government Enterprise Architecture GEA-NZ v3.0 Application and ICT Services Reference Model and Taxonomy November 2014

2 Crown copyright. This copyright work is licensed under the Creative Commons Attribution 3.0 New Zealand licence. In essence, you are free to copy, distribute and adapt the work, as long as you attribute the work to the Department of Internal Affairs and abide by the other licence terms. To view a copy of this licence, visit Please note that neither the Department of Internal Affairs emblem nor the New Zealand Government logo may be used in any way which infringes any provision of the Flags, Emblems, and Names Protection Act 1981 or would infringe such provision if the relevant use occurred within New Zealand. Attribution to the Department of Internal Affairs should be in written form and not by reproduction of the Department of Internal Affairs emblem or New Zealand Government logo. Published by the Department of Internal Affairs Document Version 1.0 Page 2 of 80

3 Document Purpose The Government Enterprise Architecture for New Zealand (GEA-NZ) Reference Models outline the following artefacts for each dimension of the architecture: - Reference taxonomy - Structure and description - Context within the GEA-NZ v3.0 - Description of artefacts and relationships with other artefacts across all dimensions The objective of a Reference Model is to provide widely accepted core taxonomy, and an appropriate visual representation of that taxonomy. A Reference Taxonomy defines the terminology, and provides a useful, coherent, consistent, and structured description of the components of an Enterprise Architecture. The need for reference architectures and associated taxonomies as part of a Government Enterprise Architecture is described in the GEA-NZ v3.0 Context Document. There are eight architecturally significant dimensions within the Government Enterprise Architecture for New Zealand v3.0 framework (GEA-NZ v3.0). Each of these dimensions has a Reference Model which includes relevant reference artefacts and relationships. Where appropriate the Reference Model has an associated Reference Taxonomy. GEA-NZ v3.0 uses reference taxonomies to provide categorisation terms to describe the architecture of capabilities for use across All of Government (AoG), sectors, clusters, and agencies. Reference taxonomies reduce complexity by abstracting, organising and simplifying complex information sets. The overall consistency and cohesiveness of cross government services, shared services and common capabilities, can be improved when government entities apply common reference taxonomies to deliver consistent and aligned views of commonly required operational and technological services. The usage of the GEA-NZ reference taxonomy, at government, agency and sector level, will help drive ICT efficiencies and Transformation programmes through identification of opportunities for development or and reuse of common solutions. This will enable the implementation of the Government ICT Strategy and Action Plan to 2017 and Better Public Services: Results for New Zealanders. Use of the GEA-NZ v3.0 reference model will: - Provide common language to promote service, information, system and technology interoperability - Promote the identification and demand aggregation of sharable and common capabilities to improve the efficacy, utility and cost effectiveness of ICT across government - Foster traceability of features to meet requirements - Support the re-use of solutions and services - Support the development and delivery of coherent AoG Common Capabilities portfolio - Support the AoG Data Governance initiatives Document Version 1.0 Page 3 of 80

4 Scope This document provides a description of the GEA-NZ v3.0 Application and ICT Services Reference Model and Taxonomy. This will provide the basis for developing specific Application and ICT Services reference architectures and patterns. These reference architectures and patterns can be more readily used across government where the terms from the reference taxonomy are used consistently. This document does not include the description of the Application and ICT Services reference architecture or the use of software tools to construct and manage GEA-NZ v3.0 models. References to related documents are contained within the context of the document. Audience The intended audience of this document is (but not limited to): - Agencies Enterprise, Application and Solution Architects - Agencies and Business partners involved in development and delivery of business and technology solutions - ICT and Architect Managers - ICT Security Specialists for Certification & Accreditation activities (C&A) Authors Regine Deleu All-of-Government Enterprise Architect Jim Clendon Senior Enterprise Architecture Modeller Phil Cutforth All-of-Government Enterprise Architect Approval This document has been created following engagement with the Chief Architect Forum (CAF) and the Government Enterprise Architecture Group (GEAG). The content will be subject to yearly review and improvement. The Government Enterprise Architect team will manage revisions and will indicate priorities for this work. Approval for changes will be sought through the GEAG. Version Control Version Date Comment Modified by Approved by Next Review Date 1.0 November 2014 Initial version Regine Deleu GEAG End 2015 Acknowledgements This version of the GEA-NZ Application and ICT Services Reference Model and Taxonomy was developed by the Government Enterprise Architecture team, part of System Transformation Team, Department of Internal Affairs, New Zealand. It was peer-reviewed and approved by GEAG members. Additionally, feedback received from a number of experts from various agencies was greatly appreciated. Document Version 1.0 Page 4 of 80

5 Table of Contents Document... 3 Purpose... 3 Scope... 4 Audience... 4 Authors... 4 Approval... 4 Version Control... 4 Acknowledgements... 4 Table of Contents... 5 Executive Summary... 7 Application and ICT Services Reference Model and Taxonomy... 8 Introduction... 8 Principles... 9 Context within GEA-NZ Benefits Development Background Approach Tools Application and ICT Services Reference Model Structure Application Domains Corporate Applications Common Line of Business Applications End User Computing Data and Information Services Identity and Access Services Security Services ICT Components, Services and Tools Interfaces and Integration Specialist Line of Business Applications Appendix GEA-NZ v3.0 Application and ICT Services Reference Taxonomy in Context with Other Artefacts Strategy and Policy Performance Business Customer Channel Product and Service People and Organisations Document Version 1.0 Page 5 of 80

6 Process Data and Information Application and ICT Services Infrastructure Security and Privacy Standards Document Version 1.0 Page 6 of 80

7 Executive Summary The Government Enterprise Architecture for New Zealand (GEA-NZ) Reference Models outline the following artefacts for each dimension of the architecture framework: - Reference taxonomy - Structure and description - Context within the GEA-NZ v3.0 - Description of artefacts and relationships with other artefacts across all dimensions The objective of a Reference Model is to provide widely accepted core taxonomy, and an appropriate visual representation of that taxonomy. A Reference Taxonomy defines the terminology, and provides a useful, coherent, consistent, and structured description of the components of an Enterprise Architecture. The GEA-NZ Application and ICT Services Reference Taxonomy consistently categorise and describe the government wide Application and ICT that support business capabilities. It is used for identifying opportunities for cost reduction, collaboration, shared services, common capabilities and solution reuse in ICT portfolios within and across agencies to effectively and efficiently support citizen centric service transformation. The usage of the GEA-NZ reference taxonomy, at government, agency and sector level, will help drive ICT efficiencies through identification of opportunities for development or and reuse of common solutions. This will ultimately support the implementation of the Government ICT Strategy and Action Plan to 2017 and Better Public Services: Results for New Zealanders. Use of the GEA-NZ v3.0 reference model will: - Provide common language to promote service, information, system and technology interoperability - Promote the identification and demand aggregation of sharable and common capabilities to improve the efficacy, utility and cost effectiveness of ICT across government - Foster traceability of features to meet requirements - Support the re-use of solutions and services - Support the development and delivery of coherent AoG Common Capabilities portfolio - Support the AoG Data Governance initiatives Document Version 1.0 Page 7 of 80

8 Application and ICT Services Reference Model and Taxonomy Introduction The GEA-NZ Application and ICT Services describes business applications, including X as a Service, that support the business processes. It includes core business, corporate and specialist line of business applications, end user computing, data and information management, identity and access management and security services. It also includes ICT components, services and tools, interfaces and integration. At an All-of-Government level, the model facilitates a common understanding of application assets and ICT services, identifying opportunities for sharing, reuse, and consolidation or renegotiation of licenses. It also assists the GCIO assurance function by identifying application assets that will require maintenance or renewal within the business planning horizon. At an agency level, the model describes the application assets and ICT services of the agency, and helps application portfolio management. Mapping their current and planned Information Systems to the Application and ICT Services Reference Taxonomy categories should help agencies and sectors identify opportunities for sharing, reuse, and consolidation or renegotiation of licenses. The GEA-NZ Application and ICT Services Reference Taxonomy provide the basis for categorising applications and their components. It categorises software that supports business. It does not include operating systems that are used to operate hardware, as these are contained in the Infrastructure Reference Model. Document Version 1.0 Page 8 of 80

9 The GEA-NZ Infrastructure Reference Taxonomy is an integral part of the Government Enterprise Architecture for New Zealand v3.0 (GEA-NZ v3.0). Principles The value of reference models comes from applying them as part of business as usual practices and capability acquisition across agencies in a consistent manner. They are used to provide a consistent view across a complex system of business services and supporting ICT so that the delivery of government services can become customer centric, and that investments can be made that benefits the system as a whole, not just specific agencies in accordance with the guiding principles of the Government ICT Strategy and Action Plan to 2017: - Centrally led, collaboratively delivered The Strategy and Action Plan will be led by the GCIO and delivered in collaboration with agency chief executives. - Customer centricity Customer insights must inform service design and delivery. Customers should be shielded from the internal complexities of Government. - Trust and Confidence Build public trust and confidence in government s ability to maintain the privacy and security of information. This underpins our ability to use digital channels. - Simplify by design Remove complexity, fragmentation and duplication, and reengineer business processes end toend. - Share by default Capabilities must be shared by default rather than by exception. Document Version 1.0 Page 9 of 80

10 Context within GEA-NZ 3.0 The GEA-NZ Application and ICT Services Reference Taxonomy is a core part of the GEA-NZ Application and ICT Services Reference Model within the GEA-NZ v3.0 framework. The GEA-NZ Application and ICT Services Reference Model provides the basis for categorising Application and ICT Services assets at a department or agency level as well as Sector and AoG levels. The following table shows the GEA-NZ Application and ICT Services Reference Model in context with the other GEA-NZ reference models. Application and ICT Services represents a key mechanism for realising strategic goals, through adoption of agile core business applications and industry standard corporate support functions provides the ICT services that enables performance measurement and control, and offers opportunities to improve business efficiency through sharing and reuse provides the application and ICT services that support business services, processes, capabilities, information sharing, and reuse sets requirements and provides the tools to manage, model, structure, share, and exchange data and information provides the application and ICT service requirements for technology and infrastructure services, and supporting applications for infrastructure management (e.g. CMDB) provides the application and ICT service controls needed to support security and privacy requirements Strategy and Policy Performance Business Data and Information Infrastructure Security and Privacy sets the application and ICT service requirements that drive development and scope of corresponding standards Standards In the Appendix you can find tables showing the GEA-NZ Application and ICT Services Reference Taxonomy in context with other artefacts. Benefits The GEA-NZ Application and ICT Services Reference Model will provide the following benefits to agencies, sectors and their business partners involved in the delivery of public services and joint capabilities: - Drives standardisation at the technology layer, improving the overall manageability, ensuring technologies are directly referenced to business outcomes, and making understanding the impact of changes more unambiguous. - Provides a government wide common language for applications and ICT services. - Identification of opportunities for sharing, re-use and consolidation of services to improve efficiencies and effectiveness of current capabilities. To guide change towards shared common services. - It will enable both horizontal assessments of where multiple products are delivering the same business service (consolidation and sharing opportunities), and vertical assessments of where different technology products have been implemented for the same or similar services (standardisation and re-use opportunities. - Provides a basis for the objective review of ICT investment by the government. Document Version 1.0 Page 10 of 80

11 - For agencies Four Year Plan to help show what they will achieve and how it will be achieved aligning to Better Public Services and all-of-government shared services. - Enables more cost-effective and timely delivery of ICT services through a repository of standards, principles and templates that support repeatable and consistent design and delivery of ICT capability, as well as business and operational support services. - Identification of opportunities for the consolidation and standardisation of applications and ICT services. - Baseline for agencies Services and API Catalogue and their Application portfolio and Catalogue; - An engagement framework that translates a high-level logical view for capability definition and delivery. From a practical perspective, to provide a tool kit for Enterprise Architects to use in their daily work. This will ultimately result in increased collaboration between agencies, reduced risks, reduced number of incompatible systems across and within agencies, and it contributes to government-wide interoperability commitments in an affordable manner. In real terms, this will allow the Government to realise savings in two key areas: Financial Aligning the GEA-NZ Application and ICT Services Reference Model within the broader architectural framework enables explicit links to be established from the performance layer through to the data and application and infrastructure layers. This will facilitate continuous, robust analysis of the relationship between ICT investments and the associated impact on performance against required business outcomes. Once established, these linkages will support evidence-based decision making around which technologies and standards are most essential to ensure the continued provision of priority, fit-for-purpose and value for money systems, services and applications. User Productivity Standardisation and rationalisation of diverse set of technical standards will improve productivity for not only the user community and those responsible for the management and delivery of ICT services, but also those involved with capability definition, development, acquisition, and delivery and integration (introduction into service, and integrated logistics support management). Improved standardisation will reduce existing barriers to workforce interoperability, service availability and sharing, and data access and sharing capabilities, and deliver improved consistency across communication and collaboration platforms. ICT will realise increases in productivity driven by the reduced complexity which flows from having a standardised, agreed set of application and ICT services. Additionally, as a more standardised suite of approved technologies and platforms develops over time, the number of applications which are supported by bespoke or specialised technologies will fall, reducing the requirement to maintain highly specialised skills to support legacy applications. Document Version 1.0 Page 11 of 80

12 Development The GEA-NZ Application and ICT Services Reference Taxonomy has been adapted for New Zealand based on the United States Federal Enterprise Architecture version 2 (US FEAF v2) 1 Application and ICT Services Reference Model combined with content developed for the NZ Defence Technology Reference Model. NZ Defence based the development of their Technology Reference Model on the following sources: - GEA-NZ v2.0 AoG Common Operating Environment (COE) and NZDF COE - NATO C32 Taxonomy - Australian Department of Defence (DoD) Integrated Defence Architecture3 (IDA) - US Information Exchange Architecture (IEA). - UK Government ICT Strategy, End User Device Programme Conceptual Framework dated Apr 12. The GEA-NZ v3.0 framework separates Application and ICT Services from Applications and ICT Services, so only content from the NZ Defence Technical Reference Model that relates to Application and ICT Services have been included. We have deliberately used the term ICT services to remove any confusion between the services delivered by government to customers / New Zealand, and what are ICT services which support the delivery of services by government to customers / New Zealand. Background The GEA-NZ v3.0 Application and ICT Services Reference Taxonomy replaces the GEA-NZ v2.0 Service Reference Taxonomy which re-used the NZ FEAF Service Reference Model. The Service Reference Model abstracted ICT services from the underlying applications. While this approach has merit in a Service Oriented Architecture for the most part applications are delivering the services directly. This Service Reference Taxonomy was originally approved as part of the NZ FEAF, back in 2008, and was essentially the same as the taxonomy in the US FEAF Service Reference Model developed in years ago. There has been some adoption of this within agencies. However 8 years is a long time in the fast moving world of ICT and technology so it is missing some concepts. As a result agencies have in turn adapted and expanded the taxonomy to the extent that it no longer provides a common set of terms. For example the GEA-NZ v2.0 COE Reference Architecture was defined using a new set of terms, with very few terms from the older reference taxonomies being reused. Approach Our approach is to reuse and adapt reference taxonomies from other jurisdictions. Three major sources for GEA-NZ v3.0 are the Australian Government Architecture v3.0 (AGA v3.0), the UK Reference Architecture (UK-RA 2012), and the US FEAF v2.0. Representatives from the Chief Architects Forum (CAF) and the Government Enterprise Architecture Group (GEAG), and other agencies review and contribute to the taxonomies NATO C3 = North Atlantic Treaty Organisation Command, Control and Co-ordination Agency 3 Note: The ADF IDA closely follows the US FEAF model. Document Version 1.0 Page 12 of 80

13 Tools The master GEA-NZ v3.0 Application and ICT Services Reference Model has been developed using the OpenText ProVision 4 modelling tool using hierarchical models. The diagrams are published using.png files, and the taxonomy data is published using Microsoft Excel. Government Enterprise Architecture will migrate the master Application and ICT Services Reference Taxonomy to the Sparx Systems Enterprise Architect 5 modelling tool in the last quarter of The Application and ICT Services Reference Taxonomy will subsequently be published in Sparx EA compatible file formats. 4 OpenText ProVision was the tool selected by the State Services Commission for Enterprise Architecture modelling by agencies in Sparx Systems Enterprise Architect, Ultimate Edition, has been selected by Government Enterprise Architecture in August 2014 as the go forward tool for developing and maintaining GEA-NZ v3.0. Document Version 1.0 Page 13 of 80

14 Application and ICT Services Reference Model Structure GEA-NZ v3.0 Application Reference Taxonomy Structure Application Services Application GEA-NZ Application v3.0 Application Area Domain Taxonomy Reference and ICT 1 1 Categorisation 1Reference Taxonomy Structure* Agency Implementation (Using ArchiMate elements)application Category ArchiMate (Information Data Asset) Object ArchiMate Application «generalisation» «access» Function «assignment» The GEA-NZ Application and ICT Services Reference Taxonomy model is a simple hierarchical structure made up of application domains, which are divided into application areas, which have categories. Application categories may have multiple levels where more detail is required. The diagram below shows the structure of the taxonomy and an approach for implementation using the Open Group ArchiMate 6 elements and relationships. ArchiMate Component Application 6 ArchiMate is an emerging standard for enterprise architecture modelling in the GEA-NZ Standards. Document Version 1.0 Page 14 of 80

15 Application Domains The GEA-NZ Application and ICT Services Reference Model include nine domains that can be used as a common language to classify Application and ICT Services. These are the: - Corporate Applications - Common Line of Business Applications - End User Computing - Data and Information Services - Identity and Access Services - Security Services - ICT Components, Services and Tools - Interfaces and Integration - Specialist Line of Business Applications Document Version 1.0 Page 15 of 80

16 Application The domains and their related areas are shown in the following diagram: and ICT Services Reference TaxonomyA1 A1.05 Strategy A1.01 (ERP) Corporate Applications A1.09 Corporate Enterprise Governance Resource Planning and A1.02 A1.06 Financial Corporate and Administration Asset A1.03 A1.07 Human Procurement Resource A1.04 A1.08 A1.12 Workforce System Business (BPMS) Intelligence Process Capability and A1.13 Analytics Improvement Continuity A1.10 Collaboration Unified Communications and A1.11 (ECM) Enterprise Content A2.05 A2.01 Business Transformation and Customer Product and Accounting Service A2.06 A2.02 Customer Marketing Service A2 Common Line of Business A2.03 Customer Applications Relationship A3.05 A3.01 Graphics End User and Device Multimedia A3.02 End User Tools A3 End User Computing A3.03 A2.07 Mobile Emergency Applications A2.04 A3.04 A2.08 Partner Productivity Grants Relationship Suite A4.01 Architecture A4.05 A4 Data and Information Services A4.09 Data and Protection Information A4.06 A4.02 Interoperability Database and Information A4.07 Services A4.03 Additional Data and Records Data and Governance Information A4.08 A4.04 Geospatial Data Quality Information A5.01 Accountability Content System A5 Identity Access A6.03 A5.03 Authentication Services Security Service A5.04 A6.04 Authorisation Security Service and Controls Access A6.01 A5.05 Identity Encryption Directory Governance Service and A5.06 Components A5.02 Operations Identity Functional Administration Core and Services A6.06 A6.02 Enterprise Network Security Security Service A5.99 Other Identity Service A8.01 Integration A8.02 A7.02 Data ICT Components Interoperability A7 ICT Services A5.07 Public Identity Key Interoperability Infrastructure (PKI) A7.01 Tools A6.05 A7.05 Business Digital Forensics Cloud Services Process A7.06 Core ICT Operation A8 Services Components, Services Interfaces and A7.03 and A8.03 xa7.07 Tools ICT Integration Interface Host and Development Layering Tools Environment A7.04 ICT Tools A9 Specialist Line of Business Applications A8.04 Gateways A1.09 Business Continuity A1.06 Corporate Administration A1.11 Enterprise Content A1.12 Business Process A3.05 Graphics and Multimedia A3.04 Productivity Suite A5.05 Directory Service A5.03 Authentication Service A8.01 A7.05 Integration Cloud Services A8.02 Data Interoperability A8.03 xa7.07 Interface Host Layering A8.04 Gateways Document Version 1.0 Page 16 of 80

17 Corporate Applications A1.05 Strategy A1.01 (ERP) Corporate Enterprise Governance Resource Planning and A1.02 Financial and Asset A1 Corporate Applications A1.03 A1.07 Human Procurement Resource A1.04 A1.08 Analytics A1.12 System Workforce Business (BPMS) Intelligence Capability A1.09 Continuity A1.06 A1.10 Collaboration Corporate Unified Communications Administration and A1.11 (ECM) Enterprise Content Process and A1.13 Improvement Business Transformation and A1.09 Business Continuity A1.06 Corporate Administration A1.11 Enterprise Content A1.12 Business Process Note: Detailed diagrams are available as.png files, and this table is available as an Excel file. Name A1 Corporate Applications A1.01 Enterprise Resource Planning (ERP) Description These are standard corporate applications within government to support the internal facing functions for managing staff, money and the way government agencies run their business. Note: The applications found in this domain can also be used as ICT services or application components. Many commercial applications may contain elements of applications listed here and specific software solutions may offer a mix of these in one suite. Enterprise resource planning (ERP) is business management software; usually a suite of integrated applications, that an organisation can use to collect, store, manage and interpret data from many business activities. In the past ERP solutions focused on back office functions but modern solutions often include some key front office functions as well. Note: Application Categories for ERP can be found under the Corporate Applications and Core Business Applications areas. Example ERP Modules are: - Financial Accounting: General ledger, fixed asset, payables including vouchering, matching and payment, receivables cash application and collections, cash management, financial consolidation. - Accounting: Budgeting cost management; activity based costing - Human Resources: Recruiting, training, rostering, payroll, benefits, diversity management, retirement, and separation. - Manufacturing: Engineering, bill of materials, work orders, scheduling, capacity, workflow management, quality control, manufacturing process, manufacturing projects, manufacturing flow, product life cycle management. - Order Processing: Order to cash, order entry, credit checking, pricing, available to promise, inventory, shipping, sales analysis and reporting, sales commissioning. - Supply Chain : Supply chain planning, supplier scheduling, product configurator, order to cash, purchasing, inventory, claim processing, and warehousing (receiving, put away, picking and packing). - Project : Project planning, resource planning, project costing, work breakdown structure, billing, time and expense, performance units, activity management. - Customer Relationship : Sales and marketing, commissions, service, customer contact, call center support - CRM systems are not always considered part of ERP systems but rather Business Support systems (BSS). - Self Service: Various "self service" interfaces for customers, suppliers and/or employees. Document Version 1.0 Page 17 of 80

18 A1.02 Financial and Asset A Budget Planning and Execution A General Ledger A Accounts Payable A Accounts Receivable A Asset Applications, software or services that support financial and asset management. Financial management refers to the efficient and effective management of money (funds) in such a manner as to accomplish the objectives of the organisation. It is the specialised function directly associated with the top management. It includes how to raise the capital, how to allocate it i.e. capital budgeting. Not only about long term budgeting but also how to allocate the short term resources like current assets. It also deals with the dividend policies of the shareholders. Software that supports all activities undertaken to determine priorities for future spending and to develop an itemised forecast of future funding and expenditures during a specified period of time. This includes the collection and use of performance information to assess the effectiveness of programs and develop budget priorities and the legal (apportionment) and managerial (allotment and sub-allotment) distribution of budget authority to achieve results consistent with the formulated budget. Software that supports accounting for assets, liabilities, fund balances, revenues and expenses associated with the maintenance of government funds and expenditure of government appropriations (salaries and expenses, operations and maintenance, procurement, working capital, trust funds, etc.), in accordance with applicable standards. Software that manages and pays the funds owed. Software that supports collections and receivables, including deposits, fund transfers, and receipts for sales or service. Software that supports the tracking of information related to deploying, operating, maintaining, upgrading, and disposing of assets cost-effectively. Includes an inventory of assets. A Expense Support the management and reimbursement of costs paid by employees or an organisation. A Financial Audit Software used to track and manage financial audit and support the examination and verification of records for accuracy. A Portfolio Software or services that provide the set of capabilities to support the administration of a group of investments held by an organisation. A1.03 Human Resource A Recruitment Applications, software or services that support human resource management. Human resource management (HRM or simply HR) is a function in organisations designed to maximize employee performance in service of their employer s strategic objectives. HR is primarily concerned with how people are managed within organisations, focusing on policies and systems. HR departments and units in organisations are typically responsible for a number of activities, including employee recruitment, training and development, performance appraisal, and rewarding (e.g., managing pay and benefit systems). HR is also concerned with industrial relations, that is, the balancing of organisational practices with regulations arising from collective bargaining and governmental laws. Software that supports the procedures for attracting and selecting high-quality, productive employees with the right skills and competencies, in accordance with merit system principles. This includes developing a staffing strategy and plan, and establishing an applicant evaluation. Document Version 1.0 Page 18 of 80

19 A Education / Training A Personnel Administration A Employee Records A Time and Attendance A Career Development and Retention A Staff Directory A Payroll A Salary A Benefits A Awards A Team and Organisation A Skills A Emergency Notification A1.04 Workforce Capability Software that supports the design, development, and implementation of a comprehensive employee development and training approach to ensure that agency employees have the right competencies. Support the matching between an organisation s employees and potential opportunities as well as the modification, addition and general upkeep of an organisation s employee-specific information. Software that manages employee personnel records and files. Software that supports the set of capabilities to support the submission, approval and adjustment of employee hours. Support the monitoring of performance as well as the professional growth, advancement and retention of an organisation's employees. Software that supports the listing of employees and their whereabouts. Software that supports the administration, calculation and payment of employee wages, bonuses, and deductions including tax. Software and or services that support the calculation and payment of salaries and payroll taxes. Software that supports the design, development, and implementation of benefits programs for agency employees. This includes establishing and communicating benefits programs, processing benefits actions, and interacting as necessary with third party benefits providers. Software that supports the administration of employee bonus and monetary awards programs. Also includes software used to design, develop, and implement pay for performance compensation programs to recognize and reward high performance, with both base pay increases and performance bonus payments. Software that supports the hierarchy structure and identification of employees within the various sub-groups of an organisation. Software that supports the proficiency of employees in the delivery of an organisation's products or services. Software that enables designated individuals to communicate critical information to many individuals across multiple devices. Applications, software or services supports workforce management. Workforce capability management encompasses all the activities needed to maintain a productive workforce. It can be part of or overlap with HR management and ERP systems. Document Version 1.0 Page 19 of 80

20 A Resource Planning and Allocation A Field Service A Demand A Workforce Scheduler A Workforce Dispatcher A Contingent Workforce A1.05 Corporate Governance and Strategy Software that supports the processes for identifying the workforce competencies required to meet the agency s strategic goals and for developing the strategies to meet these requirements. The software also supports procedures for attracting and selecting high-quality, productive employees with the right skills and competencies, in accordance with merit system principles. This includes developing a staffing strategy and plan; establishing an applicant evaluation approach; announcing the vacancy, sourcing and evaluating candidates against the competency requirements for the position; initiating pre-employment activities; and hiring employees. Software to optimally plan and dispatch field service technicians and their properly stocked vehicles to a customer's location in a timely manner in order to deliver against their service commitments. Software to help forecast work orders to plan the number and expertise of staff that will be needed. Software to predefined rules to automatically optimise the schedule and use of resources (people, parts, vehicles). Software to automatically assigning work orders within predefined zones to particular technicians. Software that supports the continuity of operations for an organisation's business through the identification of surge or temporary personnel in addition to agency staff. Applications, software or services that support corporate governance functions. Corporate governance broadly refers to the mechanisms, processes and relations by which corporations are controlled and directed. Governance structures identify the distribution of rights and responsibilities among different participants in the corporation (such as the board of directors, managers, shareholders, creditors, auditors, regulators, and other stakeholders) and include the rules and procedures for making decisions in corporate affairs. Corporate governance includes the processes through which corporations' objectives are set and pursued in the context of the social, regulatory and market environment. Governance mechanisms include monitoring the actions, policies and decisions of corporations and their agents. Corporate governance practices are affected by attempts to align the interests of stakeholders. A Strategy and Planning Software that allows setting up the activities of determining strategic direction, identifying and establishing programs, services and processes, and allocating resources (capital and labour) among those programs and processes. A Governance A Compliance Software that supports decisions, actions, business rules and other matters that govern an organisation. Compliance software and or services provide a common framework and an integrated approach to manage all compliance requirements faced by an agency. It enables companies to manage cross-industry mandates and regulations such as SOX, OSHA, EH&S, and FCPA as well as industry focused regulatory guidelines from FDA, FERC, FAA, HACCP, AML, Basel II, and Data Retention laws. Document Version 1.0 Page 20 of 80

21 A Internal Control A Corporate Policy A Risk A Corporate Performance A1.06 Corporate Administration A Legal Advice Support the methods and procedures used by the organisation to safeguard its assets, produce accurate accounting data and reports, contribute to efficient operations, and encourage staff to adhere to management policies and mission requirements. Software that supports development and enforcement of corporate policy within an organisation. Software that allows planners to explicitly address uncertainty by identifying and generating metrics, setting parameters, prioritizing, and developing mitigations, and tracking risk. Software that allows setting up performance metrics, planners to explicitly address uncertainty by identifying and generating metrics, setting parameters, prioritizing, and developing mitigations, and tracking risk. Applications, software or services that support the day-to-day management and maintenance of the internal administrative operations. Software that supports giving legal advice. A Facilities Software that supports facilities management including the maintenance, administration, certification, and operation of office buildings that are possessions of the government / agency. A Accommodation A Media and Facilities Reservations A Travel A Issue Tracking Software that supports managing the accommodation needs of the workforce. Software that supports arrangements to track and secure the use of media and facilities. Software that supports activities associated with planning, preparing, and monitoring of business-related travel expenses. This may include employees and others supporting the work of the government. Software that supports the management of a service center to respond to government and contract employees' technical and administrative questions. A1.07 Procurement Applications, software or services that supports procurement; the acquisition of goods, services or works from an outside external source. A Supplier Software used to manage the relationship and lifecycle of existing suppliers. The purpose of Supplier is to obtain value for money from suppliers and contracts. It ensures that underpinning contracts and agreements align with business needs, Service Level Agreements and Service Level Requirements. Supplier oversees process of identification of business needs, evaluation of suppliers, establishing contracts, their categorisation, management and termination. Note: This has a close link to "Partner Relationship " in the "Common Line of Business Application" area. A Sourcing A Supplier Contract Support the supply of goods or services as well as the tracking and analysis of costs for these goods. Supplier Contract (SPM) is about defining what a supplier is to deliver in a contract. Document Version 1.0 Page 21 of 80

22 A Supplier Performance A Supplier Balanced Scorecard Supplier Performance (SPM) is about ensuring the supplier delivers what has been promised in the contract. A balanced scorecard includes a mixture of quantitative and qualitative measures, including how key participants perceive the quality of the relationship. These KPIs are shared between customer and supplier and reviewed jointly, reflecting the fact that the relationship is two-way and collaborative, and that strong performance on both sides is required for it to be successful. Advanced organisations conduct 360 degree scorecards, where strategic suppliers are also surveyed for feedback on their performance, the results of which are built into the scorecard. A Ordering / Purchasing Allow the placement of request for a product A Supplier Catalogue A Invoice Tracking and Approval A Logistics and Transportation A1.08 Business Intelligence and Analytics A Data Warehouse A Data Mart A Data Mining A Decision Support Support the listing of available products or services that an organisation offers and shopping cart / ordering functionality. Software that manages inflow and outflows of "products", as well as data about the level of "products" on hand and support the identification of where a shipment or delivery is within the business cycle. Provide for efficient freight and traffic management to receive purchased goods and services. Software or services to support Business intelligence (BI). It includes techniques and tools for the transformation of data and information into meaningful and useful information and knowledge for business analysis purposes. Common functions of business intelligence technologies are reporting, online analytical processing, analytics, data mining, process mining, complex event processing, business performance management, benchmarking, text mining, predictive analytics and prescriptive analytics. A data warehouse (DW, DWH), or an enterprise data warehouse (EDW), is a system used for reporting and data analysis. Integrating data from one or more disparate sources creates a central repository of data, a data warehouse (DW). Data warehouses store current and historical data and are used for creating trending reports for senior management reporting such as annual and quarterly comparisons. The data stored in the warehouse is uploaded from the operational systems (such as marketing, sales, etc.). The data may pass through an operational data store for additional operations before it is used in the DW for reporting. A data mart is the access layer of the data warehouse environment that is used to get data out to the users. The data mart is a subset of the data warehouse that is usually oriented to a specific business line or team. Data marts are small slices of the data warehouse. Whereas data warehouses have an enterprisewide depth, the information in data marts may pertain to a single department. Software that provides for the efficient discovery of non-obvious, valuable patterns and relationships within a large collection of data. Software or services that support business or organisational decision-making activities. Supports the management, operations, and planning levels of an organisation and helps to make decisions, which may be rapidly changing and not easily specified in advance. Document Version 1.0 Page 22 of 80

23 A Online Analytical Processing (OLAP ) A Online Transaction Processing (OLTP ) A Predictive Analysis A Knowledge and Discovery A Data and Information Analysis A Information Retrieval A Knowledge Capture A Knowledge Distribution and Delivery A Simulation A Survey Data Collection A Business Intelligence Reporting A Ad hoc Reporting A Balanced Scorecard Software or services that support a process to swiftly answer multi-dimensional analytical (MDA) queries and enable users to interactively analyse multidimensional data from multiple perspectives. An OLAP consists of three basic analytical operations: consolidation, drill-down, and slicing and dicing. Online transaction processing (OLTP) is a class of information systems that facilitate and manage transaction-oriented applications, typically for data entry and retrieval transaction processing. Software and or services to provide predictive analysis. Predictive analysis is about finding and quantifying hidden patterns in the data using complex mathematical models that can be used to predict future outcomes. Predictive analysis is different from OLAP in that OLAP focuses on historical data analysis and is reactive in nature, while predictive analysis focuses on the future. These systems are also used to support Customer Relationship (CRM). Software that supports knowledge and discovery management. Software and or services to support the analysis and inspection of data and information. This feeds into: - Data and Information Modelling - Data Categorisation - Data Cleaning - Data Transformation Software that provides access to data and information for use by an organisation and its stakeholders. Software that facilitates collection of data and information. Software that supports the transfer of knowledge to the end customer. Software or services that help manipulate information to identify patterns and create possible changes. Software or services that support methods to collect information from a sample of individuals in a systematic way for empirical research in social sciences, marketing and official statistics. Software and or services that supports analysis, reporting and statistics for Business Intelligence. Software tools or services that support the creation and display of individually designed and structured reports with self-service access to meaningful data. A semi-standard structured report supported by proven design methods and automation tools that can be used by managers to keep track of the execution of activities by the staff within their control and to monitor the consequences arising from these actions. Document Version 1.0 Page 23 of 80

24 A BI Dashboard A On Demand Reporting A Standardised / Canned A Operational Data Store (ODS) A Statistical Analytics A Data Profiling A dashboard is "an easy to read, often single page, real-time user interface, showing a graphical presentation of the current status (snapshot) and historical trends of an organisation s key performance indicators to enable instantaneous and informed decisions to be made at a glance. In real-world terms, "dashboard" is another name for "progress report" or "report." Often, the "dashboard" is displayed on a web page that is linked to a database which allows the report to be constantly updated. A dashboard can be created as a 'mashup' of data from different sources. Note: This is not to be confused with a balanced scorecard. Software tools or services that support on-demand reporting. An on-demand report is a formatted version of a report run with the currently available data and viewed immediately. When you run an on-demand report, you can specify the parameter values to use; the report is then formatted using the current data and displayed in the report viewer. Software or services that support the creation and display of standard reports with self-service access to meaningful data. An operational data store (ODS) is a database designed to integrate data from multiple sources for additional operations on the data. Unlike a master data store the data is not passed back to operational systems. It may be passed for further operations and to the data warehouse for reporting. Because the data originates from multiple sources, the integration often involves cleaning, resolving redundancy and checking against business rules for integrity. An ODS is usually designed to contain low-level or atomic (indivisible) data (such as transactions and prices) with limited history that is captured "real time" or "near real time" as opposed to the much greater volumes of data stored in the data warehouse generally on a less-frequent basis. Software or services that support the study of a collection, organisation, analysis, and interpretation of data. Software that supports all forms of data analysis of extremely large, complex data sets (big data) that are manipulated for business consumption. Data profiling is the process of examining the data available in an existing data source (e.g. a database or a file) and collecting statistics and information about that data. The purpose of these statistics may be to: - Find out whether existing data can easily be used for other purposes. - Improve the ability to search the data by tagging it with keywords, descriptions, or assigning it to a category. - Give metrics on data quality including whether the data conforms to particular standards or patterns. - Assess the risk involved in integrating data for new applications, including the challenges of joins. - Assess whether metadata accurately describes the actual values in the source database. - Understanding data challenges early in any data intensive project, so that late project surprises are avoided. Finding data problems late in the project can lead to delays and cost overruns. - Have an enterprise view of all data, for uses such as master data management where key data is needed, or data governance for improving data quality. A1.09 Business Continuity Software or services to support the business continuity. This includes Health and Safety, Disaster. Document Version 1.0 Page 24 of 80