Closed FranckCo closed 5 years ago
Decision during May 7 VC: affect to Juan.
The diagram has been updated to add: Task, and the specialized StatisticalProductionTask Add StatisticalProductionProcess as a specilized StatisticalProcess
Classification of Activities, Statistical Activities, Tasks and Statistical Tasks from GAMSO 1.2 Activity-StatisticalActivity.docx Activity-StatisticalActivity.pdf
The more I think about this, the less certain I become whether it is even possible to classify GAMSO activity into either "statistical activity" and "non-statistical activity" because GAMSO activity is so high-level and generic. For example, (@FlavioRizzolo, correct me if I am wrong), the Statistics Canada's Enterprise Anchor Model (see below) has vertical layers of IT services that are, together, both statistical (e.g. generic system for E&I) and non-statistical (e.g. email, IT security). Is it right then to classify GAMSO Manage IT activity which reads like
- These activities cover coordination and management of information and technology resources and solutions. They include the management of the physical security of data and shared infrastructures. These include: Manage IT assets and services; Manage IT security; Manage technological change
as an "activity" (hence, without statistical element in it)?
Statistics Canada's Enterprise Anchor Model
![]()
- An Infrastructure Layer—core infrastructure services related to storage, informatics, and infrastructure security. In the Government of Canada, a government organization responsible for government-wide infrastructure (Shared Services Canada) provides these services. Email is included in this layer in the model, as a mail service hosted by Shared Services Canada.
- A Core Technology Platforms layer—the various platforms that are part of the Technology Architecture
- A Core Information Services layer—the statistical and corporate information services used across the organization (e.g., registers, metadata and data management, information management, classifications management)
- A Core Statistical Services layer—common, shared statistical functions such as those found in Statistics Canada's Generalized Systems (e.g., Banff E&I, G-SAM, G-Export, etc.). Creating reusable services can be a strong contributor to organization success.
- A Core Production Segments layer—platforms for the different solution segments supporting statistical production, including the collection platform, dissemination, business statistics processing, social statistics processing (common tools), and census. It also includes corporate services platforms used in running the business.
I tend to agree with @InKyungChoi. I think that rather than classifying activity into "statistical" and "non-statistical" we should probably classify them into "purely statistical", i.e. those that are only about statistical production, and "corporate", i.e. those that are about the functioning of the organization in general, including, but not limited to, statistical production.
I'd say that everything in Production is "purely statistical" whereas pretty much everything else would be "corporate", in the sense given above. The only ones that seem out of place to me w.r.t. to that classification is Manage Statistical Methodology and Manage Data Suppliers: they are "purely statistical" based on their definitions, but for some reason they are not in Production.
I agree with @InkyungChoi too, maybe this will make the classification easier to understand. I will make the correction, accordingly to this.
Decision during August 29 VC: only Manage Statistical Methodology (http://id.unece.org/activity/activity/3.2) and Manage Data Suppliers (http://id.unece.org/activity/activity/3.6) are instances of coos:StatisticalActivity. The other GAMSO activities are just instances of the higher-level coos:Activity.
Decision during 16 April VC: instances of activities would be spread between those with statistical nature (e.g. methodology), which would be instances of StatisticalActivity, and those without statistical nature (e.g. logistic), which would be instances of Activity.