Navigating the application of Modernisation Frameworks when using Commercial Of The Shelf products. This presentation will provide a walkthrough of the Business Process Information Model and how it will support automated, metadata driven business processes in the ABS.

Change Required Statistical processes and systems within the ABS were poorly documented and inconsistent across all Statistical Programs. systems siloed and inflexible to changing requirements, resulting in high maintenance and modification costs staff required to move in and out of various tools and interfaces throughout production cycle Metadata describe inconsistently between different collections, requiring constant transformation

Automated, Metadata Driven Business Processes The Statistical Workflow Management System (SWMS) will support the introduction of automated, standard, reusable metadata driven business processes within the ABS. This will support standardised business processes within the ABS, with the differences between Statistical Programs being addressed through the configuration of metadata (and data) as input to those business processes. Configuration of these standard business processes will be achieved via the use of Parameter Sets registered and stored within the ABS Metadata Registry & Repository (MRR).

SWMS Benefits SWMS will benefit the ABS by: Providing well documented, discoverable and accessible business processes, removing reliance on subject matter experts; Automating statistical business processes, removing menial manual tasks; Supporting the use of corporate infrastructure (MRR, SWMS, EDME), and reusable technical services, reducing (and eventfully eliminating) the need for bespoke, siloed local systems; Providing process metrics for standard business intelligence reporting and input into future business process improvements;

Use of Modernisation Frameworks The ABS developed its Enterprise Architecture to guide the Transformation Program which commenced in 2013. Key to the development of the Enterprise Architecture were the Modernisation Frameworks developed initially by the Statistical Network, and now owned and governed by the UNECE Statistics. These frameworks include: The Generic Statistical Business Process Model (GSBPM) The Generic Statistical Information Model (GSIM)

ABS variants to the Modernisation Frameworks - GSBPM & SPAM Generic Statistical Business Process Model (GSBPM) Version 5.0 - 2013 Statistical Production Activity Model (SPAM) Version 1.1 - 2017 The ABS has embarked on an ambitious transformation program, which aims to remove most to all unnecessary manual activities The GSBPM still reference activities which the ABS is seeking to make redundant The GSBPM needs to remain relevant to less advanced Statistical Organisations – so therefore cannot be matured to meet the ABS aspirations Accordingly – the ABS developed its own variant of the GSBPM The Statistical Production Activity Model (SPAM) SPAM has detailed mappings back to GSBPM to facilitate international collaboration efforts

Generic Statistical Information Model GSIM & AIM Generic Statistical Information Model (GSIM) ABS Information Model (AIM) The ABS Information Model (AIM) utilised GSIM as the starting point, and has expanded on this model to include all the Information relevant to the ABS statistical production cycle. The AIM is the underpinning model supporting our Metadata Registry & Repository (MRR). Currently – AIM is composed of: 12 Groups N Classes The AIM includes the ABS Business Process Information Model

ABS Enterprise Architecture & Business Processes SPAM 1 2 3 The Process Architecture supporting SWMS was developed from the ABS Enterprise Architecture, and leans heavily on the Business Architecture and artefacts supporting it, namely the Statistical Production Activity Model (SPAM). SPAM, like GSBPM is a categorisation framework to assist in realising the Business Architectures goal of identifying and describing non-overlapping statistical activities. The ABS used SPAM as the key framework to support building re-usable, configurable business processes. The ABS identified early on that standardising business processes from the top down would be extremely difficult and may not be fully achievable until the ABS business matured in terms of working with standardised and automated business processes. The Process Architecture therefore centred around standardising business processes at the lowest level of categorisation possible in SPAM (ie beyond level three) – and allowing for end to end workflows to be built up utilising these lower level “building blocks” in any order that was required. This approach would support standardisation whilst also providing flexibility for thestatistical business areas. 20/09/2018

Business Process Gartner defines business processes as: The coordination of the behaviour of people, systems and things* to produce specific business outcomes. A BPM platform minimally includes: a graphical business process and/or rule modelling capability, a process registry/repository to handle the modelling metadata, a process execution engine and a state management engine or rule engine (or both). Gartner definition of Business Process and BPM Platforms. The process registry/repository is typically supports open BPMN standards, such as BPMN 2.0, BPEL and WS-Human-Task. These standards have been designed to model business processes in great detail and are used widely within the Business Process modelling community. * "Things" in this context refers to devices that are part of the Internet of Things (IoT).

Business Process Standards BPMN 2.0 The Business Process Modelling Notation (BPMN) is a graphical notation that depicts the steps and the end to end flow of a business process. The notation has been specifically designed to coordinate the sequence of processes and the messages that flow between different process participants in a related set of activities. BPEL BPEL is an XML-based language for describing a business process in which most of the tasks represent interactions between the process and external Web services. The BPEL process itself is represented as a Web service, and is realised by a BPEL engine which executes the process description. WS-HumanTask WS-HumanTask enables the integration of tasks actioned by human beings in service-oriented applications. It provides a notation, state diagram and API for human tasks, as well as a coordination protocol that allows interaction with human tasks in a more service-oriented fashion and at the same time controls tasks autonomy.

Applying GSIM Business Process model with CotS Product The ABS acquired a Commercial of the Shelf Product for implementing and managing our automated business processes. ActiveVOS is a BPM product acquired in 2015 by which; is a service orientated business process automation platform. executes BPMN models directly on a high-performance BPEL engine that runs on any standards-based Java Enterprise Edition server. supports open standards such as BPMN 2.0, BPEL and WS-Human-Task.

Applying GSIM Business Process model with CotS Product The GSIM Business group models Business Processes down to a level which duplicates the open standards supported by ActiveVOS and other COTS BPM products. ABS did not want to replicate modelling in our ABS Information Model (AIM) that was natively supported by ActiveVOS. Key requirements for the modelling Business Processes in AIM were: Registration of re-usable Business Processes (SPAM building blocks) Registration of Workflows for Statistical Programs Registration of executed Workflows for Statistical Programs Registration & Storage of all Workflow configurations for Statistical Programs Registration & Record of all Process Outputs from Workflows

GSIM Business group for Business Processes Replaced with: Parameter Set Definition Parameter Set Not Required This meant a number of GSIM objects were not required Process Method, Process Design, Process Control, Process Control Design are all objects which are natively modelled and controlled within a CotS BPM product, including ActiveVOS Additionally, the ABS did not require the Business Service and Business Function objects modelled. These are catalogued elsewhere and was not deemed necessary to incorporate within AIM The Process Inputs and Outputs Specification are replaced with a Parameter Set Definition The Process Inputs and Outputs are replaced with Parameter Sets The Input and Output are specified by relationships.

Parameter Set Definitions Parameter Set Definition replaces the Process Input Specification and Process Output Specification in GSIM. The Parameter Set Definition specifies the types of Process Inputs and Process Outputs that the Business Process will either consume or produce (the configuration). The Relationship between the Parameter Set Definition and Business Process specifies its use for Process Input Specification or Process Output Specification.

Parameter Sets Parameter Sets replaces the Process Input and Process Output in GSIM. The Parameter Set is used to capture and store both the design time and run time Process Inputs for a Statistical Program’s re-use of the Business Process. A Parameter Set is described by the Parameter Set Definition related to the Business Process that is being re-used. The Relationship between the Parameter Set and Workflow/Workflow Instance specifies its use for Process Input (design or run time)or Process Output.

Business Process Information Model The ABS Business Process Information Model was developed to capture only the set of information required by the ABS . As mentioned previously, this model supports the key requirements: Registration of re-usable Business Processes (SPAM building blocks) Registration of Workflows for Statistical Programs Registration of executed Workflows for Statistical Programs Storage of all Workflow configurations for Statistical Programs Recording all Process Outputs from Workflow We will now take a walkthrough of the ABS Business Process Information Model describing each of the objects and their purpose.

Business Process Information Model

Business Process Information Model The Business Process is the registration of a standard, re-usable and configurable process supporting a defined business activity. The Parameter Set Definition specifies the types of Process Inputs and Process Outputs that the Business Process will either consume or produce (the configuration). The Process Input Specification and Process Output Specification are specified by the relationship name to the Parameter Set Definition. The Business Process is the registration of a standard, re-usable and configurable process supporting a defined business activity. The Parameter Set Definition specifies the types of Process Inputs and Process Outputs that the Business Process will either consume or produce (the configuration).

Business Process Information Model One of the 6

Business Process Information Model A Workflow is the process for a Statistical Program which undertakes a higher level business function. Typically, Workflows will orchestrate together many reusable Business Processes.

Business Process Information Model The Process Step represents the re-use of a Business Process within a Statistical Program’s Workflow. The Process Step binds the Parameter Set for the re-use of the Business Process.

Business Process Information Model The Parameter Set is used to capture and store the design time Process Inputs for a Statistical Program’s intended re-use of the Business Process. This Parameter Set takes its content and typing from the Parameter Set Definition Which is related to the Business Process that the Process Step is calling.

Business Process Information Model One of the 6

Business Process Information Model The Workflow Instance is the registration in the MRR of the execution of a Workflow for a Statistical Program. One of the 6

Business Process Information Model The Process Step Instance is the registration in the MRR of the execution of a Process Step for a Statistical Program. The Process Step Instance binds the Parameter Set for the actual re-use of the related Business Process. One of the 6

Business Process Information Model The Parameter Set is used to capture and store the Actual Process Inputs and the Actual Process Outputs for a Statistical Program’s executed re-use of the related Business Process. One of the 6

Business Process Information Model One of the 6

Build and register our library of re-usable Business Processes supporting lower level activities as described by SPAM. These become our SPAM building blocks. Each Business Process will have an associated Parameter Set Definition – which will describe the type of inputs that the Business Process requires. Each building block will call Technical Services from our service layer. The ABS has adopted Service Orientated Architecture (SOA) – which enables disaggregated services to be aggregated together to undertake business functions Statistical Programs will build their End to End Workflows – identifying which re-usable Business Processes they will call & when. Process Steps within the End to End Workflows are linked to re-usable Business Processes. The Process Steps then have Parameter Sets associated with them, describing the actual Process Inputs will be used at execution time. The Parameter Sets are described by the Parameter Set Definitions associated with the Business Process being re-used.

The End. Questions?