Proposed roadmap for completing GSIM V1.0

1. Introduction

This document presents the work required to progress from GSIM V0.4, as delivered by GSIM Sprint   2, to GSIM V1.0.

The term GSIM   V1.0 refers to the first version of GSIM which could be applied in practice for all of the agreed purposes for GSIM listed in Section 2.

The Sprint process, which led to Sprint 1 and Sprint 2, was commissioned by HLG-BAS in order to accelerate development of GSIM.  This acceleration was prompted in November 2011 by the first Workshop on Strategic Developments in Business Architecture in Statistics which identified that a number of other practical collaboration activities are already waiting to use GSIM as a reference model.

Assuming the same level of priority continues to be placed on completing development of GSIM, and now that the Sprints have established a clear, shared, sense of the remaining work required, it is anticipated an initial “complete” version (1.0) of GSIM can be delivered by December 2012.

Section 2 of this document summarises what has been delivered so far.

Section 3 summarises the roadmap proposed for progressing to release of GSIM V1.0.

Section 4 of the document highlights the need for overall project planning, management and governance arrangements. These must be determined and set in place urgently if the necessary further development work is to be progressed as promptly as required to release GSIM V1.0 in December   2012.  Once the project management role, and project governance arrangements, have been established critical first steps will be

1.       confirming the project plan

2.       estimating in more detail the resources required

3.       ensuring sufficient resources will be available to progress each activity within the work program

The Sprint 2 team seeks feedback – and ideally endorsement – from HLG-BAS regarding the program of work set out in this roadmap document.  It also seeks advice and assistance from HLG-BAS in addressing the planning, management and governance arrangements required to initiate the proposed streams of work.

In regard to these streams of work, Annex 1 and Annex 2 provide details of the activity (completing the GSIM Specification Layer) that will take the longest elapsed time and require the most resources.

Annex 3 provides details of all of the main components in the work program and Annex 4 provides a high level Gantt Chart highlighting interdependencies.

2. What has been delivered so far

GSIM Sprint 1 achieved international consensus on the scope and purpose of GSIM.

While Sprint 2 had developed alternative wording which expresses the purposes more clearly, the following purposes remain fundamentally the same as those proposed to HLG-BAS in the report from Sprint 1.

1.       Improve communication between users, producers and providers of official statistics.

2.       Improve communication between different disciplines involved in statistics production.

3.       Generate economies of scale by enabling intra-   and inter-agency collaboration, especially through the reuse of information, methods or technology.

4.       Enable configurable, rule-based and modular ways of making statistics, thus minimising human intervention in the production process.

5.       Provide a basis for flexibility and innovation, including support for the easy deployment of new statistical products and the adoption of new types of statistical data sources

 

Sprint 2 has determined that GSIM should be documented in the following manner

  1. Overview Layer

       A reference that explains broadly GSIM for Senior Managers.

The Overview Layer also helps other readers (eg target audiences beyond statistical agencies) understand whether GSIM is relevant for them and whether they should explore the other layers.
 

  1. Communication Layer

       Supports use of GSIM by subject matter statisticians, process designers and methodologists
 

  1. Specification Layer

       Supports consistent implementation of GSIM by metadata specialists and by application developers, including making it easy for them to use implementation standards such as SDMX and DDI on a shared basis

In producing GSIM V0.4, Sprint 2 has delivered completed drafts of the Overview Layer and the Communication Layer.  These layers are sufficient for meeting Purpose 1 and 2 for GSIM.

3. Roadmap summary

Completing the Specification Layer for inclusion in GSIM V1.0 will require additional modeling.  While this is not the only activity required to progress from GSIM V0.4 to GSIM V1.0, it is the work which will take the longest elapsed time and require the most resources.

Annex 1 provides a brief explanation of what is required to complete the Specification Layer.  Annex   2 outlines a suggestion developed by Sprint 2 for how this work could be progressed.

Current planning suggests initial drafting of the Specification Layer can be completed by 31 August   2012.

It is proposed the initial draft of the Specification Layer then be reviewed at a one week workshop by a GSIM Integration Team which includes a number of participants from Sprint 1 and Sprint 2.  The same workshop would review the input received from external reviewers of the Overview Layer and Communication Layer as documented within GSIM V0.4.

The workshop would ensure documentation of the Specification Layer is

       internally consistent, and appropriate, from both business and technical perspectives

       consistent with the Overview and Communication Layers

The workshop would produce the first draft of GSIM which included all three layers in a fully documented and integrated form.  This draft would be termed GSIM V0.8.

GSIM V0.8 would be a candidate for being released as GSIM V1.0 if external review identified no significant issues with any of the layers.  As this will be the first time the Specification Layer has been made available for external review, however, it is expected some matters will need to addressed to update GSIM V0.8 and produce GSIM V1.0.

GSIM V0.8 should be released for external review on 24 September 2012.

GSIM V0.8 should be sufficiently close to GSIM V1.0 to allow a Communication Plan for GSIM V1.0 to be prepared and a User Guide.

From 29 October, the GSIM Integration Team would analyse and address the external review feedback on all three layers of GSIM V0.8.  It would draft the proposed specification of GSIM V1.0.  It would ensure the Communication Plan and User Guide were fully consistent with the proposed GSIM V1.0 specification and appropriate to support its release.

The final proposed specification for GSIM V1.0 would be introduced to HLG-BAS, and the expert groups associated with HLG-BAS, at the 2 nd annual workshop on Business Architecture for Statistics to be held on 7-8 November.

The specification would then be submitted to the high level approval process (yet to be determined) for having GSIM V1.0 recognised internationally.  Depending on the process required for final approval, GSIM V1.0 might be released officially on 17 December 2012.

4. Initiating implementation of the road map

The previous section provides a narrative overview of the Roadmap.  Annex 3 provides more information about each of the main components within the roadmap.  An indicative very high level Work Breakdown Structure (WBS) is provided in Annex 4.

Annex 4, in particular, highlights the interdependencies between various elements of the work.  Several different streams of activities are proposed to be progressed in parallel.

In order to be confident that the roadmap will be followed and produce GSIM V1.0 by December   2012, appropriate project planning, management and governance arrangements need to be established.  These arrangements need to be established quickly, otherwise commencement of work on further developing the Specification Layer may be delayed or may be initiated on a less certain, committed and vigorous basis than envisaged in the Roadmap. As completing initial design of the full details of the Specification Layer is on the “critical path” for completing development of GSIM V1.0, failing to apply and maintain the anticipated momentum in regard to this work will delay delivery of GSIM overall.

It is proposed that project management responsibilities for implementing the Roadmap are assigned urgently.  The project manager can then

       review, add detail to, change timings and otherwise adjust the high level plan set out in the Roadmap

       add resource estimates for the various tasks

       work with HLG-BAS Secretariat or others to define the governance arrangements for the project overall and the activities within the project

       work within the governance arrangements to confirm how resources will be made available to progress work with the necessary momentum

       establish specifically who is responsible for leading, and who will participate in, the progressing of each activity

Once the project management role has been established, and the governance arrangements clarified for the project overall and the individual activities within it, the project manager would be responsibly forgoing monitoring, co-ordination, management and reporting of progress on the project overall.


Annex 1: Description of what is required to complete the Specification Layer

Sprint 2 has identified the set of 100+ “information objects” which should be defined in the Specification Layer.  The definition for each of these objects should include a set of “standardised” attributes for that object. [1]

When an example of that GSIM object is used in a business process, designers (including of IT applications to support the business process) can count on the meaning of those attributes being defined on a standard basis.

The standardised attributes of each GSIM information object may either

       correspond directly with implementation modelling in SDMX and/or DDI (in cases where the implementation modelling in SDMX and/or DDI is fit for purpose for conceptual modelling in GSIM), or
 

       “mapped” to implementation in SDMX, DDI or other standards

GSIM Sprint 2 defined the standardised attributes for a number of objects.  There was not time to standardise the attributes of the majority of information objects in the Specification Layer.


Annex 2: Suggested approach to completing an initial draft of the Specification Layer

As mentioned in Annex 1, Sprint 1 has identified 100+ information objects that should have their standardised attributes defined in the Specification Level.

Different experts have the knowledge about different sets of information objects which is required to complete modelling of them as quickly and effectively as possible.  For example, the business experts in regard to the information required to describe and drive statistical business processes in practice (associated with the Production Group in GSIM) tend to be different to the experts in modelling Conceptual metadata such as concepts and classifications.

It would not be efficient to define a single (large) task team to progress all of the work.

One possible means of dividing the work appropriately among focused task team would be the following.

The task teams would include business experts related to each work package, together with at least one modeller.  Not all business experts would need to have participated in the GSIM Sprint process, but at least one in each team should have.  The task teams would progress their work mainly via wiki and tele/web conferences.  Each task team would also include an expert in the implementation standards that were relevant for that work package (eg SDMX and DDI for all work packages, BPMN for the Production work package, ISO 11179 for the Conceptual work packages)

The modeller for each task team would be an outposted member of Modelling Team and would compare modelling with their modelling colleagues on an ongoing basis.

The more broadly based Expert Reference Group would review the modelling from time to time (eg every two weeks) to ensure the modelling done by the task teams is coherent and appropriate from a business perspective.


Annex 3: Main components in the roadmap

1. Develop Specification Layer

This activity, which will take the longest elapsed time and require the most resources, is described in Section 3 and Annex 1 and 2.

2. Confirm management plan and resource plan for progressing from V0.4 to V1.0

This activity is described in Section 4.

3. Establish and confirm an appropriate set of “use cases” for validation purposes

Practical, well documented and readily applied “use cases” (detailed examples of business processes that GSIM needs to support) have been essential to support and validate development of GSIM to date and will remain so when progressing from V0.4 to V1.0.  Overall requirements for use cases, ensuring adequate representation of different types of production processes and different phases of the GSBPM, need to be established.  The set of use cases defined to date can be assessed against these requirements and, if necessary, new use cases added and/or additional detail added to existing use cases.

 

Practical business process use cases will, for example, be essential material for reference and validation purposes for the task teams that develop the Specification Layer.  They will also be used more generally to validate V0.8 of GSIM and the proposed V1.0.

4. Manage external review process for GSIM V0.4

GSIM V0.4 is expected to be released for general review in mid May, with comments closing by the end of June 2012.  The comments will then be reviewed and decisions made on whether, and how, each comment should be reflected in the design of GSIM V0.8.

5. Organise and conduct GSIM Layer Integration Workshop

It is proposed a one week workshop be held in September.  The Workshop would bring together GSIM experts to

       review the initial consolidated design proposal for the Specification Layer

       review proposed updates to the Overview Layer and Communication Layer based on reviewer feedback on GSIM V0.4

6. Manage external review process for GSIM V0.8

GSIM V0.8, the first draft of GSIM to include all three layers, would be released following the Layer Integration Workshop.  Reviewer feedback on V0.8 would be due by the end of October 2012.

7. Confirm governance processes for GSIM V1.0

The two main requirements in this regard are interrelated.

       Identify the process which needs to be followed in order to have GSIM V1.0 “confirmed”/”endorsed” so that it becomes internationally recognised as the first complete version of GSIM
 

       Identify what arrangements will be put in place to maintain and support GSIM after it is released as V1.0.

8. Develop communication plan for GSIM V1.0

A long list has already been compiled of stakeholders who should be informed in regard to GSIM V1.0, and encouraged to harness it in practice.  A communication plan will ensure that

       appropriate supporting material is available when GSIM V1.0 is released, and

       stakeholders are informed, engaged and encouraged appropriately once GSIM V1.0 is released

9. Prepare GSIM User Guide

It is proposed to provide a User Guide to assist users in applying GSIM V1.0 for communication and specification purposes in a consistent and effective manner.

10. Finalise GSIM V1.0 Specifications

From 29 October, the GSIM Integration Team would analyse and address the external review feedback on all three layers of GSIM V0.8.  It would draft the proposed specification of GSIM V1.0.  It would ensure the Communication Plan and User Guide were fully consistent with the proposed GSIM V1.0 specification and appropriate to support its release.

The final proposed specification for GSIM V1.0 would be introduced to HLG-BAS, and the expert groups associated with HLG-BAS, at the 2 nd annual workshop on Business Architecture for Statistics to be held on 7-8 November.

The specification would then be submitted to the high level approval process (yet to be determined) for having GSIM V1.0 recognised internationally.  Depending on the process required for final approval, GSIM V1.0 might be released officially on 17 December 2012.

 


Annex 4: Indicative high level Gantt Chart

 


[1] The aim is to standardise the minimum set of attributes for each object which are required to ensure information, methods or technology can be designed to be shared.  Different implementations (eg different existing IT systems) may define additional attributes to be used for local purposes.  Such attributes are not generic and do not belong within GSIM.