Meeting notes - November 19th, 2024

[Chris-ECE]

Of the 6 Overarching Processes (OPs) in GSBPM, 3 do not have detailed descriptions.
The last discussion discussed whether to rename or elaborate them. – If we elaborate them, the text should clarify the distinction between each OP and GAMSO activities.
There wasn’t strong support expressed in the meeting for removing any of the OPs, though some have expressed support/acceptance for this by email (incl. InKyung, Flavio, Carlo, Dan Gillman).
Claudia said that the difference of OPs with GAMSO is not always clear. She suggested improving the description to distinguish them. We looked at the proposed text for the 3 lesser-described OPs.
Juan said if OPs are closely related to production, we should think about describing them in GSBPM, and we can’t just delete them if they are part of the statistical production process. Activities that apply to managing all statistical projects can be in GAMSO, but specific details related to a statistical process should be in GSBPM. The description that must be clarified to avoid confusion, and make the right connection between GSBPM and GAMSO.
Cory questioned how many phases Provider Management would apply to. For the other 2, he said elaboration is needed to see whether they belong in GSBPM and GAMSO.
It was agreed to revert back to the previous version of the names of these OPs:

1. Process Data Management
2. Knowledge Management
3. Provider Management
   Gabriel said that OPs are part of GAMSO, in that they have analogues in some of the GAMSO activities (Manage Quality, Manage Data Suppliers, etc). He suggested within the OPs making a link to the corresponding activity of GAMSO, elaborating the OPs in the context of GSBPM and avoiding contradiction with GAMSO. GSBPM and GAMSO are inter-connected. There was a discussion about whether or not each OP is a subset of a GAMSO activity within the Corporate Support Grouping, or whether those GAMSO activities bleed into the OPs in some way. It was agreed that the important aspect is the interoperability/alignment and/or contact-points between the OPs and certain GAMSO activities.

Istat pointed out that the separation between GAMSO and GSBPM OPs is in that GAMSO activities are at the organizational level, while GSBPM refers to a single process/workflow, so they consider a different viewpoint. Nadia suggested that some GSBPM OPs are more related to GAMSO while others belong more firmly within GSBPM.
Looking at the body of the GAMSO document, in many cases it specifies that GAMSO handles activities at an organizational level, while GSBPM handles activities more directly related to statistical production. So there seems to be a boundary defined there (although there may be similarities and touchpoints between them). Of the 3 OPs that already have detailed explanatory text, most contain an explicit reference to what aspects are covered by GAMSO.

Provider Management
Looking at the proposed text for Provider Management, Gabriel cautioned against using the phrase “in contrast”.
Action: Chris to re-write the Provider Management (and others) to be more in the style of the other OPs.

Process Data Management
The proposed text was reviewed. There were no comments.

Knowledge Management
Juan presented the text proposal.
Action: Chris offered to tweek the text to make it clear that keeping things (methodologies, practices) up to date is the outcome of this process, but the OP itself is concerned with documenting knowledge as a means of achieving this.