Login required to access the wiki. Please register to create your login credentials We apologize for any inconvenience this may cause, but please note that this step is necessary to protect your privacy and ensure a safer browsing experience. Thank you for your cooperation. Documents available for download: GAMSO , GSBPM , GSIM |
1. The Generic Statistical Business Process Model (GSBPM) describes and defines the set of business processes needed to produce official statistics. It provides a standard framework and harmonised terminology to help statistical organisations to modernise their statistical production processes, as well as to share methods and components. The GSBPM can also be used for integrating data and metadata standards, as a template for process documentation, for harmonising statistical computing infrastructures, and to provide a framework for process quality assessment and improvement.
2. Since its release in 2008 (v1.0), GSBPM has gained wide adoption within official statistical community and become a de-facto standard for process model. The GSBPM comprises of eight phases of the process and sub-processes within each phase, which are the building blocks that can be used to design statistical business process. The activities and their descriptions in GSBPM remain at a high-level to keep the model generic, hence applicable for as many organizations as possible. While this generic nature of the model is attributed to its success, several organisations have added activities more detailed than GSBPM sub-processes (called “Task” henceforth) when they adopt GSBPM for local setting. A list of common tasks will provide better clarity on the activities to be conducted in different phases and sub-processes, thereby facilitating the implementation of GSBPM.
3. The purpose of this document is to compile examples from countries that have added lower-level activities to their national version of GSBPM, and to develop a list of common tasks for all GSBPM sub-processes without losing the generic nature of the model under a set of principles (e.g., coding, granularity, minimality, description format) with reference to the current version of the GSBPM (version 5.1).
4. The Task team has collected examples of finer-level activities from 9 countries: Australia, Azerbaijan, Costa Rica, France, Norway, Romania, Saudi Arabia, Serbia, and Spain (see here for the summary) and developed a proposal for the task level for all GSBPM sub-processes (see section II, highlighted in blue). The Task team has further prepared some suggestions to the GSBPM revision team (see section III).
5. The list of tasks was developed based mainly on the description of each sub-process in the GSBPM, by adding country examples as well as feedback received from the community. Each task uses the format of “Action verb + an object” as well as with hierarchical coding (e.g., 1.1.1, 1.1.2, etc.).
6. It should be noted that the GSBPM is not a rigid framework in which all sub-processes must be followed in a strict order, some sub-processes can be skipped and re-visited. Likewise, tasks in this document are meant to provide a set of building blocks that can be put together to construct a logical sequence for the production process, hence do not need to be followed linearly in the order they are presented, some tasks can be omitted and repeated.
7. During the discussion, many connections have been explored not only with the GSBPM revision team, but also with GSBPM Overarching processes (OPs) that are applied throughout the entire production process. The examples of OPs include management of quality, management of metadata and data management. Given that these activities take place in many moments in the production, the GSBPM does not make direct references to OPs in every sub-process where relevant, but instead, make explicit mention only where they are considered particularly important to highlight. Following the same approach in the GSBPM, this document does not include task-level activities related to OPs everywhere they could take place, but only in a few sub-processes where they are considered to be particularly relevant to highlight (i.e., essential to the given sub-process from the statistical perspective that exclusion of such tasks would cause more confusion).
8. In the following months, a task team is expected to be formed to analyse the OPs in detail and decide the best way to connect OPs and sub-processes and tasks of the GSBPM.