• We suggest adding a point between the point 34 and 35 (Intro paragraphs for Specify Needs) mentioning to assess the cost of production, reliability and the risk of privacy breaks, particularly acknowledging the increased demand for a higher level of geographical detail in official statistics and the need of providing geospatial enabled statistics with the right spatial resolution for policy-making. (Statistics Portugal)
Addressing respondent needs
• In the specify needs phase – can we also add something in here to explore respondent needs not just data user needs? This should be done early on once the user needs are understood to then help shape and size the later phases of work (ONS)
Difference between 1.1 and 1.2
• We suggested the aggregation of the sub-processes 1.1 “Identify needs” and 1.2 “Consult & confirm needs”, because the related tasks are performed simultaneously. The borders are very thin. (Statistics Portugal)
• Further emphasize the difference between 1.1 and 1.2. It is unclear if 1.2 is only about validating by users the need defined. A need could be largely modified due to consultation. Then rewriting the need would be an activity in the sense of 1.1 or 1.2 ? Then, maybe change the wording in 1.3 from « the user needs identified in sub-process 1.2 » to « the user needs validated in sub-process 1.2 » (INSEE)
1.1
• In this process, it is necessary to mention that the identification of needs is supported by recurrent and permanent processes. (Statistics Ecuador)
• Clarify the meaning of "statistics" identified in 1.1 and the difference with "concepts" identified in 1.4. (INSEE, repeated under 1.4)
1.2
• Consult and confirm needs: it should also refer to the fact that not all user needs must be fulfilled and the selection between the ones NSOs would or would not fulfil, should be included in the description. Also, we suggest adding an activity on organizing and confirming collected user needs (that will feed into the next iteration of the statistical business process). (Statistics Hungary)
1.3
• Establish output objectives: maybe rename to “Set output objectives”. The description mentions legal frameworks as constraints even though they reflect statistical considerations. These are not only present in legal instruments but also in quality-related or methodological normative documents. Instead of constraints these are more like requirements, quality components for the product. (Statistics Hungary)
• We are talking more about "accessing data" instead of "transmitting data". This change of perspective should be reflected in the text of the GSBPM (maybe also generate additional tasks somewhere?) (GSBPM “Task” task team, 2022) (Relevant to 1.3??)
1.4
• Clarify the meaning of "statistics" identified in 1.1 and the difference with "concepts" identified in 1.4. (INSEE, repeated under 1.1)
1.5
• In parallel with this, the process step “check data availability and other pre-requisites” will contain a detailed description of evaluation of possible new data sources. (Statistics Sweden)
• The current version describes a process that is made for statistics based on administrative registers; nonetheless, it is unclear the process to follow for surveys and censuses which are not combined surveys, or if what was described in the 5.0 version will be maintained for this kind of sources. For these reasons, it is still not clear how to implement this sub-process. (Statistics Ecuador)
1.6
• How to handle decision points in the statistical business process model, such as approval of business cases of action plans (1.6 & 8.3 and possibly even more in the process)? (GSBPM “Task” task team, 2022)
Specify Needs phase Introduction text
• We suggest adding a point between the point 34 and 35 (Intro paragraphs for Specify Needs) mentioning to assess the cost of production, reliability and the risk of privacy breaks, particularly acknowledging the increased demand for a higher level of geographical detail in official statistics and the need of providing geospatial enabled statistics with the right spatial resolution for policy-making. (Statistics Portugal)
Addressing respondent needs
• In the specify needs phase – can we also add something in here to explore respondent needs not just data user needs? This should be done early on once the user needs are understood to then help shape and size the later phases of work (ONS)
Difference between 1.1 and 1.2
• We suggested the aggregation of the sub-processes 1.1 “Identify needs” and 1.2 “Consult & confirm needs”, because the related tasks are performed simultaneously. The borders are very thin. (Statistics Portugal) • Further emphasize the difference between 1.1 and 1.2. It is unclear if 1.2 is only about validating by users the need defined. A need could be largely modified due to consultation. Then rewriting the need would be an activity in the sense of 1.1 or 1.2 ? Then, maybe change the wording in 1.3 from « the user needs identified in sub-process 1.2 » to « the user needs validated in sub-process 1.2 » (INSEE)
1.1
• In this process, it is necessary to mention that the identification of needs is supported by recurrent and permanent processes. (Statistics Ecuador) • Clarify the meaning of "statistics" identified in 1.1 and the difference with "concepts" identified in 1.4. (INSEE, repeated under 1.4)
1.2
• Consult and confirm needs: it should also refer to the fact that not all user needs must be fulfilled and the selection between the ones NSOs would or would not fulfil, should be included in the description. Also, we suggest adding an activity on organizing and confirming collected user needs (that will feed into the next iteration of the statistical business process). (Statistics Hungary)
1.3
• Establish output objectives: maybe rename to “Set output objectives”. The description mentions legal frameworks as constraints even though they reflect statistical considerations. These are not only present in legal instruments but also in quality-related or methodological normative documents. Instead of constraints these are more like requirements, quality components for the product. (Statistics Hungary) • We are talking more about "accessing data" instead of "transmitting data". This change of perspective should be reflected in the text of the GSBPM (maybe also generate additional tasks somewhere?) (GSBPM “Task” task team, 2022) (Relevant to 1.3??)
1.4
• Clarify the meaning of "statistics" identified in 1.1 and the difference with "concepts" identified in 1.4. (INSEE, repeated under 1.1)
1.5
• In parallel with this, the process step “check data availability and other pre-requisites” will contain a detailed description of evaluation of possible new data sources. (Statistics Sweden) • The current version describes a process that is made for statistics based on administrative registers; nonetheless, it is unclear the process to follow for surveys and censuses which are not combined surveys, or if what was described in the 5.0 version will be maintained for this kind of sources. For these reasons, it is still not clear how to implement this sub-process. (Statistics Ecuador)
1.6
• How to handle decision points in the statistical business process model, such as approval of business cases of action plans (1.6 & 8.3 and possibly even more in the process)? (GSBPM “Task” task team, 2022)