-
Notifications
You must be signed in to change notification settings - Fork 3
/
GSIMv2.html
6362 lines (6356 loc) · 293 KB
/
GSIMv2.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!DOCTYPE html>
<html>
<head>
<title>GSIM version 2.0</title>
<meta http-equiv='Content-Type' content='text/html;charset=utf-8' />
<script src='https://www.w3.org/Tools/respec/respec-w3c' class='remove' defer></script>
<script class='remove'>
var respecConfig = {
// specStatus: "unofficial",
noRecTrack: true,
shortName: "GSIMv2",
subtitle: "Generic Statistical Information Model (Version 2.0)",
// latestVersion: "https://unece.github.io/GSIM-2.0/GSIMv2.html",
// publishDate: "2022-xx-xx",
wg: "High-Level Group for the Modernisation of Official Statistics",
wgURI: "https://statswiki.unece.org/display/hlgbas/Modernisation+Groups",
wgPatentURI: "https://creativecommons.org/licenses/by/3.0/igo/",
github: {
repoURL: "https://github.com/UNECE/GSIM-2.0",
branch: " ", // avoids default 'gh-pages'
},
};
</script>
</head>
<body>
<section id="abstract">
<!-- <img src="https://upload.wikimedia.org/wikipedia/commons/e/e1/CC_BY_icon.svg"> -->
<p class="copyright" style="font-size:15px;" > This work is licensed under <a href="http://creativecommons.org/licenses/by/4.0/">the Creative Commons Attribution 4.0 International License</a>. If you re-use all or part of this work, please attribute it to the United Nations Economic Commission for Europe (UNECE), on behalf of the international statistical community. </p>
<p>This is the GitHub repository for version 2.0 of the Generic Statistical Information Model (GSIM). You can use the sidebar to navigate different sections of this page. </p>
<p>
<strong>Need an Executive Summary of GSIM?</strong> - Please refer to our <a href="https://github.com/UNECE/GSIM-2.0/blob/main/Reference%20Documents/GSIM%20Communication%202_0%20(2024).pdf">GSIM Communication Paper</a> (aimed at senior managers).
</p>
<p>
<strong>For a summary of changes to GSIM since version 1.2, please refer to this page <a href="https://github.com/UNECE/GSIM-2.0/blob/42b3f8ea173fd31a451e25b110ba7979a6064e40/Changes%20since%20GSIM%20v1.2/Introduction.md">refer to this page</a>
</strong>
</p>
<p>For information about <em>previous versions</em> of GSIM, you may consult the <a href="https://statswiki.unece.org/display/gsim/GSIM+v1.2">UNECE Statistics Wiki site</a>
</p>
<p>
<strong>Quick Links</strong>
</p>
<p>
<a href="#id1_base_group">1. Base Group</a>
</p>
<p>
<a href="#id2_business_group">2. Business Group</a>
</p>
<p>
<a href="#id3_concept_group">3. Concept Group</a>
</p>
<p>
<a href="#id4_exchange_group">4. Exchange Group</a>
</p>
<p>
<a href="#id5_structure_group">5. Structure Group</a>
</p>
</section>
<section id="id1_base_group">
<h1>Base Group</h1>
<section id="id11_base_group_group_diagram">
<h2>Group Diagram</h2>
<p>
<strong>Click the diagram below and then select a class for an interactive step-through of the Base Group classes</strong>
</p>
<figure>
<a href="https://app.diagrams.net/?lightbox=1&p=ex&#Uhttps%3A%2F%2Fraw.githubusercontent.com%2FUNECE%2FGSIM-2.0%2Fmain%2FUML%20Model%20Files%2FGSIM_2_0_Base_Group.drawio#%7B%22pageId%22%3A%222KFCqOQoIdhveJmsqo8c%22%7D">
<img src="./img/GSIM_2_0_Base_Group.png" alt="Alt text here">
</a>
</figure>
</section>
<section id="id12_base_group_descriptive_information">
<h2>Descriptive Information</h2>
<p>
<strong>Base Group</strong> provides features that are reusable by other classes to support functionality such as identity and versioning.
</p>
<p>The information classes defined within this group as as follows:</p>
<h3 id="administrative-details">Administrative Details</h3>
<strong>Definition</strong>
<table class="simple">
<thead>
<tr>
<th>
<strong>Class</strong>
</th>
<th>
<strong>Group</strong>
</th>
<th>
<strong>Definition</strong>
</th>
<th>
<strong>Explanatory Text</strong>
</th>
<th>
<strong>Synonyms</strong>
</th>
</tr>
</thead>
<tbody>
<tr>
<td>Administrative Details</td>
<td>Base</td>
<td>extensions to the model based on an organisations administrative needs</td>
<td>The <em>Administrative Details</em> is designed to act as a placeholder to allow for future extensions to the existing model. It allows for further information to be added about the <em>Administrative Details</em> required to maintain the other information classes outlined by GSIM. </td>
<td> </td>
</tr>
</tbody>
</table>
<strong>Attributes</strong>
<table class="simple">
<thead>
<tr>
<th>
<strong>Name</strong>
</th>
<th>
<strong>Description</strong>
</th>
<th>
<strong>Cardinality</strong>
</th>
<th>
<strong>Value Type</strong>
</th>
</tr>
</thead>
<tbody>
<tr>
<td>Administrative Status</td>
<td>Indicator for access to an item: under review, open for use, or removed.</td>
<td>0..1</td>
<td>ControlledVocabulary</td>
</tr>
<tr>
<td>Alias</td>
<td>The alias or alia associated with the information class.</td>
<td>0..*</td>
<td>String</td>
</tr>
<tr>
<td>Annotation</td>
<td>A comment or instruction which provides additional explanations about the information class and how to use it.</td>
<td>0..*</td>
<td>String</td>
</tr>
<tr>
<td>Created Date</td>
<td>The date on which the information class was created.</td>
<td>0..1</td>
<td>Date</td>
</tr>
<tr>
<td>Documentation</td>
<td>An official document or paper that has been published by an organisation.</td>
<td>0..*</td>
<td>String</td>
</tr>
<tr>
<td>Last Updated Date</td>
<td>The date on which the information class was last changed.</td>
<td>0..1</td>
<td>Date</td>
</tr>
<tr>
<td>Life Cycle Status</td>
<td>Indicator for the quality of an item: incomplete, valid, superseded, or retired.</td>
<td>0..1</td>
<td>ControlledVocabulary</td>
</tr>
<tr>
<td>Url</td>
<td>Allows location of the information class. Distinct from the identification of the class as handled by the identifier attribute in <em>Identifiable Artefact</em>. </td>
<td>0..*</td>
<td>String</td>
</tr>
<tr>
<td>Valid From</td>
<td>The start date included in the period during which the class is effective or valid. It is effective or valid from that date.</td>
<td>0..1</td>
<td>Date</td>
</tr>
<tr>
<td>Valid To</td>
<td>The end date included in the period during which the information class is effective or valid. It is no longer effective or valid after that date.</td>
<td>0..1</td>
<td>Date</td>
</tr>
</tbody>
</table>
<h3 id="agent"> Agent </h3>
<strong>Definition</strong>
<table class="simple">
<thead>
<tr>
<th>
<strong>Class</strong>
</th>
<th>
<strong>Group</strong>
</th>
<th>
<strong>Definition</strong>
</th>
<th>
<strong>Explanatory Text</strong>
</th>
<th>
<strong>Synonyms</strong>
</th>
</tr>
</thead>
<tbody>
<tr>
<td>Agent</td>
<td>Base</td>
<td>someone or something that plays an active role in the lifecycle of an <em>Identifiable Artefact</em>
</td>
<td>An <em>Agent</em> may be an <em>Individual</em>, an <em>Organisation</em> (or part of it) or a <em>Software Agent</em> that affects in some way an instance of a GSIM class. For example, an <em>Agent</em> can play a role in the execution of a <em>Business Processes</em> or in the way a <em>Statistical Classification</em> (or a <em>Concept</em>) changes over time. </td>
<td> </td>
</tr>
</tbody>
</table>
<strong>Attributes</strong>
<p>* Attributes inherited from super-type(s) are not included here</p>
<h3 id="agent-in-role"> Agent In Role </h3>
<strong>Definition</strong>
<table class="simple">
<thead>
<tr>
<th>
<strong>Class</strong>
</th>
<th>
<strong>Group</strong>
</th>
<th>
<strong>Definition</strong>
</th>
<th>
<strong>Explanatory Text</strong>
</th>
<th>
<strong>Synonyms</strong>
</th>
</tr>
</thead>
<tbody>
<tr>
<td>Agent In Role</td>
<td>Base</td>
<td>an <em>Agent</em> acting in a specific <em>Role</em> </td>
<td>In the Organization Ontology from W3C <em>Agent In Role</em> is called a Post. </td>
<td> </td>
</tr>
</tbody>
</table>
<strong>Attributes</strong>
<table class="simple">
<thead>
<tr>
<th>
<strong>Name</strong>
</th>
<th>
<strong>Description</strong>
</th>
<th>
<strong>Cardinality</strong>
</th>
<th>
<strong>Value Type</strong>
</th>
</tr>
</thead>
<tbody>
<tr>
<td>Description</td>
<td>The description of the information class.</td>
<td>0..1</td>
<td>MultilingualText</td>
</tr>
<tr>
<td>Name</td>
<td>A term which designates a concept, in this case an information class. The identifying name will be the preferred designation. There will be many terms to designate the same information class, such as synonyms and terms in other languages.</td>
<td>1..1</td>
<td>MultilingualText</td>
</tr>
</tbody>
</table>
<h3 id="change-event"> Change Event </h3>
<strong>Definition</strong>
<table class="simple">
<thead>
<tr>
<th>
<strong>Class</strong>
</th>
<th>
<strong>Group</strong>
</th>
<th>
<strong>Definition</strong>
</th>
<th>
<strong>Explanatory Text</strong>
</th>
<th>
<strong>Synonyms</strong>
</th>
</tr>
</thead>
<tbody>
<tr>
<td>Change Event</td>
<td>Base</td>
<td>indication of the occurrence of a change to an <em>Identifiable Artefact</em>
</td>
<td>A <em>Change Event</em> relates to the information class(es) that has(have) been affected. It can be applied to only one <em>Identifiable Artefact</em> and result in one or more <em>Identifiable Artefact(s)</em>. On the other hand, a <em>Change Event</em> can be applied to more than one <em>Identifiable Artefact</em> and result in only one <em>Identifiable Artefact</em>. </td>
<td> </td>
</tr>
</tbody>
</table>
<strong>Attributes</strong>
<table class="simple">
<thead>
<tr>
<th>
<strong>Name</strong>
</th>
<th>
<strong>Description</strong>
</th>
<th>
<strong>Cardinality</strong>
</th>
<th>
<strong>Value Type</strong>
</th>
</tr>
</thead>
<tbody>
<tr>
<td>Change Date</td>
<td>The date on which the <em>Change Event</em> occurred. </td>
<td>1..1</td>
<td>Date</td>
</tr>
<tr>
<td>Change Type</td>
<td>The type of change that occurred during the <em>Change Event</em>. </td>
<td>1..1</td>
<td>String</td>
</tr>
<tr>
<td>Identifier</td>
<td>The unique identifier of the <em>Change Event</em> that is applied to an information class; assigned by the owner agency. </td>
<td>1..1</td>
<td>String</td>
</tr>
</tbody>
</table>
<h3 id="contact"> Contact </h3>
<strong>Definition</strong>
<table class="simple">
<thead>
<tr>
<th>
<strong>Class</strong>
</th>
<th>
<strong>Group</strong>
</th>
<th>
<strong>Definition</strong>
</th>
<th>
<strong>Explanatory Text</strong>
</th>
<th>
<strong>Synonyms</strong>
</th>
</tr>
</thead>
<tbody>
<tr>
<td>Contact</td>
<td>Base</td>
<td>
<em>Role</em> in which Individual(s) is(are) responsible for providing additional information about an information class and/or its metadata, either directly or indirectly by linking to its source
</td>
<td> </td>
<td> </td>
</tr>
</tbody>
</table>
<strong>Attributes</strong>
<p>* Attributes inherited from super-type(s) are not included here</p>
<h3 id="identifiable-artefact"> Identifiable Artefact </h3>
<strong>Definition</strong>
<table class="simple">
<thead>
<tr>
<th>
<strong>Class</strong>
</th>
<th>
<strong>Group</strong>
</th>
<th>
<strong>Definition</strong>
</th>
<th>
<strong>Explanatory Text</strong>
</th>
<th>
<strong>Synonyms</strong>
</th>
</tr>
</thead>
<tbody>
<tr>
<td>Identifiable Artefact</td>
<td>Base</td>
<td>abstract class that comprises the basic attributes and associations needed for identification, naming and other documentation</td>
<td>All GSIM classes except <em>Administrative Details, Agent In Role, Change Event, Datum, Process Input</em> (and its sub-types) and <em>Process Output</em> (and its sub-types) are a sub-type of <em>Identifiable Artefact</em>. In SDMX, Identifiable Artefact is defined as construct that contains structures capable of providing identity to an object. </td>
<td> </td>
</tr>
</tbody>
</table>
<strong>Attributes</strong>
<table class="simple">
<thead>
<tr>
<th>
<strong>Name</strong>
</th>
<th>
<strong>Description</strong>
</th>
<th>
<strong>Cardinality</strong>
</th>
<th>
<strong>Value Type</strong>
</th>
</tr>
</thead>
<tbody>
<tr>
<td>Description</td>
<td>The description of the information class.</td>
<td>0..1</td>
<td>MultilingualText</td>
</tr>
<tr>
<td>Id</td>
<td>The unique identifier of the information class; assigned by the owner agency.</td>
<td>1..1</td>
<td>String</td>
</tr>
<tr>
<td>Local ID</td>
<td>This is an identifier in a given local context that uniquely references an information class. For example, Local ID could be a variable name in a dataset.</td>
<td>0..1</td>
<td>String</td>
</tr>
<tr>
<td>Name</td>
<td>A term which designates a concept, in this case an information class. The identifying name will be the preferred designation. There will be many terms to designate the same information class, such as synonyms and terms in other languages.</td>
<td>1..1</td>
<td>MultilingualText</td>
</tr>
<tr>
<td>Version</td>
<td>The version designator of the information class assigned by the owner agency.</td>
<td>0..1</td>
<td>String</td>
</tr>
<tr>
<td>Version Date</td>
<td>The date on which the version was created.</td>
<td>0..1</td>
<td>Date</td>
</tr>
<tr>
<td>Version Rationale</td>
<td>The reason for making this version of the information class.</td>
<td>0..1</td>
<td>String</td>
</tr>
</tbody>
</table>
<h3 id="individual">Individual</h3>
<strong>Definition</strong>
<table class="simple">
<thead>
<tr>
<th>
<strong>Class</strong>
</th>
<th>
<strong>Group</strong>
</th>
<th>
<strong>Definition</strong>
</th>
<th>
<strong>Explanatory Text</strong>
</th>
<th>
<strong>Synonyms</strong>
</th>
</tr>
</thead>
<tbody>
<tr>
<td>Individual</td>
<td>Base</td>
<td>person who acts, or is designated to act towards a specific purpose</td>
<td> </td>
<td> </td>
</tr>
</tbody>
</table>
<strong>Attributes</strong>
<p>* Attributes inherited from super-type(s) are not included here</p>
<h3 id="maintainer"> Maintainer </h3>
<strong>Definition</strong>
<table class="simple">
<thead>
<tr>
<th>
<strong>Class</strong>
</th>
<th>
<strong>Group</strong>
</th>
<th>
<strong>Definition</strong>
</th>
<th>
<strong>Explanatory Text</strong>
</th>
<th>
<strong>Synonyms</strong>
</th>
</tr>
</thead>
<tbody>
<tr>
<td>Maintainer</td>
<td>Base</td>
<td>
<em>Role</em> in which a <em>unit</em> or group of persons within the <em>Organisation</em> is responsible for managing an information class and its metadata
</td>
<td>A unit or group of persons with the role of <em>Maintainer</em> is responsible for all administrative and operational issues relating to one or a set of information classes and its metadata (e.g. adding, modifying or deleting metadata about an information class). It is answerable to all stakeholders for all issues related to the information classes under its responsibility. A <em>Maintainer</em> is not a decision-making body. Decisions are made collaboratively among the owners of the artefact. </td>
<td> </td>
</tr>
</tbody>
</table>
<strong>Attributes</strong>
<p>* Attributes inherited from super-type(s) are not included here</p>
<h3 id="organisation"> Organisation </h3>
<strong>Definition</strong>
<table class="simple">
<thead>
<tr>
<th>
<strong>Class</strong>
</th>
<th>
<strong>Group</strong>
</th>
<th>
<strong>Definition</strong>
</th>
<th>
<strong>Explanatory Text</strong>
</th>
<th>
<strong>Synonyms</strong>
</th>
</tr>
</thead>
<tbody>
<tr>
<td>Organisation</td>
<td>Base</td>
<td>unique framework of authority within which a person or persons act, or are designated to act, towards some purpose</td>
<td>
<em>Organisation</em> represents a collection of people organised together, often with hierarchical structures. Examples of <em>Organisation</em>: national statistics office, international agency
</td>
<td> </td>
</tr>
</tbody>
</table>
<strong>Attributes</strong>
<p>* Attributes inherited from super-type(s) are not included here</p>
<h3 id="owner"> Owner </h3>
<strong>Definition</strong>
<table class="simple">
<thead>
<tr>
<th>
<strong>Class</strong>
</th>
<th>
<strong>Group</strong>
</th>
<th>
<strong>Definition</strong>
</th>
<th>
<strong>Explanatory Text</strong>
</th>
<th>
<strong>Synonyms</strong>
</th>
</tr>
</thead>
<tbody>
<tr>
<td>Owner</td>
<td>Base</td>
<td>
<em>Role</em> in which a statistical office, authority or other organisation is responsible for defining, specifying, creating and making decisions about the maintenance of a class and/or its metadata
</td>
<td>Some information classes may have several <em>Owners</em>. </td>
<td> </td>
</tr>
</tbody>
</table>
<strong>Attributes</strong>
<p>* Attributes inherited from super-type(s) are not included here</p>
<h3 id="role"> Role </h3>
<strong>Definition</strong>
<table class="simple">
<thead>
<tr>
<th>
<strong>Class</strong>
</th>
<th>
<strong>Group</strong>
</th>
<th>
<strong>Definition</strong>
</th>
<th>
<strong>Explanatory Text</strong>
</th>
<th>
<strong>Synonyms</strong>
</th>
</tr>
</thead>
<tbody>
<tr>
<td>Role</td>
<td>Base</td>
<td>function assumed by an <em>Agent</em>
</td>
<td>Part played by an <em>Individual</em>, an <em>Organisation</em> (or part of it) or a <em>Software Agent</em> in a particular situation. Examples: <em>Contact</em>, data steward, scheduler. <em>Role</em> can be maintained by a controlled vocabulary (e.g. RASCI). </td>
<td> </td>
</tr>
</tbody>
</table>
<strong>Attributes</strong>
<p>* Attributes inherited from super-type(s) are not included here</p>
<h3 id="software-agent"> Software Agent</h3>
<strong>Definition</strong>
<table class="simple">
<thead>
<tr>
<th>
<strong>Class</strong>
</th>
<th>
<strong>Group</strong>
</th>
<th>
<strong>Definition</strong>
</th>
<th>
<strong>Explanatory Text</strong>
</th>
<th>
<strong>Synonyms</strong>
</th>
</tr>
</thead>
<tbody>
<tr>
<td>Software Agent</td>
<td>Base</td>
<td>software that carries out <em>Process Step</em> based on <em>Process Control</em>
</td>
<td>Examples: google bot</td>
<td>PROV Software Agent, DDI Machine</td>
</tr>
</tbody>
</table>
<strong>Attributes</strong>
<p>* Attributes inherited from super-type(s) are not included here</p>
</section>
</section>
<section>
<h1 id="id2_business_group"> Business Group</h1>
<h2 id="id21_business_group_group_diagram"> Group Diagram</h2>
<p>
<strong>Click the diagram below and then select a class for an interactive step-through of the Business Group classes</strong>
</p>
<figure>
<a href="https://app.diagrams.net/?lightbox=1&p=ex&#Uhttps%3A%2F%2Fraw.githubusercontent.com%2FUNECE%2FGSIM-2.0%2Fmain%2FUML%20Model%20Files%2FGSIM_2_0_Business_Group.drawio#%7B%22pageId%22%3A%222KFCqOQoIdhveJmsqo8c%22%7D">
<img src="./img/GSIM_2_0_Business_Group.png" alt="Alt text here">
</a>
</figure>
<h2 id="id22_business_group_descriptive_information"> Descriptive Information</h2>
<p>
<strong>Business Group</strong> is used to capture the designs and plans of statistical programmes, and the processes undertaken to deliver those programmes.
</p>
<p>The information classes defined within this group as as follows:</p>
<h3 id="assessment"> Assessment </h3>
<strong>Definition</strong>
<table class="simple">
<thead>
<tr>
<th>
<strong>Class</strong>
</th>
<th>
<strong>Group</strong>
</th>
<th>
<strong>Definition</strong>
</th>
<th>
<strong>Explanatory Text</strong>
</th>
<th>
<strong>Synonyms</strong>
</th>
</tr>
</thead>
<tbody>
<tr>
<td>Assessment</td>
<td>Business</td>
<td>result of the analysis of the quality and effectiveness of any activity undertaken by a statistical organisation and recommendations on how these can be improved</td>
<td>An <em>Assessment</em> can be of a variety of types. One example may include a gap analysis, where a current state is determined along with what is needed to reach its target state. Alternatively, an <em>Assessment</em> may compare current processes against a set of requirements, for example a new <em>Statistical Need</em> or change in the operating environment. An <em>Assessment</em> can use various classes as inputs, whether they are the main classes that the <em>Assessment</em> is about or auxiliary classes that help accomplish the <em>Assessment</em>. </td>
<td> </td>
</tr>
</tbody>
</table>
<strong>Attributes</strong>
<table class="simple">
<thead>
<tr>
<th>
<strong>Name</strong>
</th>
<th>
<strong>Description</strong>
</th>
<th>
<strong>Cardinality</strong>
</th>
<th>
<strong>Value Type</strong>
</th>
</tr>
</thead>
<tbody>
<tr>
<td>Date Assessed</td>
<td>Date when the Assessment took place</td>
<td>1..*</td>
<td>Date</td>
</tr>
<tr>
<td>Issues</td>
<td>Issues identified through the <em>Assessment</em>
</td>
<td>0..*</td>
<td>String</td>
</tr>
<tr>
<td>Recommendations</td>
<td>Recommendations from the <em>Assessment</em>
</td>
<td>0..*</td>
<td>String</td>
</tr>
<tr>
<td>Results</td>
<td>Results from the <em>Assessment</em>
</td>
<td>0..*</td>
<td>String</td>
</tr>
</tbody>
</table>
<p>* Attributes inherited from super-type(s) are not included here</p>
<h3 id="business-case">Business Case</h3>
<strong>Definition</strong>
<table class="simple">
<thead>
<tr>
<th>
<strong>Class</strong>
</th>
<th>
<strong>Group</strong>
</th>
<th>
<strong>Definition</strong>
</th>
<th>
<strong>Explanatory Text</strong>
</th>
<th>
<strong>Synonyms</strong>
</th>
</tr>
</thead>
<tbody>
<tr>
<td>Business Case</td>
<td>Business</td>
<td>proposal for a body of work that will deliver outputs designed to achieve outcomes</td>
<td>A <em>Business Case</em> is produced as a result of a detailed consideration of a <em>Change Definition</em>. It sets out a plan for how the change described by the <em>Change Definition</em> can be achieved. A <em>Business Case</em> usually comprises various evaluations. The <em>Business Case</em> will specify the stakeholders that are impacted by the <em>Statistical Need</em> or by the different solutions that are required to implement it. A <em>Business Case</em> will provide the reasoning for undertaking a <em>Statistical Support Activity</em> to initiate a new <em>Statistical Programme Design</em> for an existing <em>Statistical Programme,</em> or an entirely new <em>Statistical Programme</em>, as well as the details of the change proposed. </td>
<td> </td>
</tr>
</tbody>
</table>
<strong>Attributes</strong>
<table class="simple">
<thead>
<tr>
<th>
<strong>Name</strong>
</th>
<th>
<strong>Description</strong>
</th>
<th>
<strong>Cardinality</strong>
</th>
<th>
<strong>Value Type</strong>
</th>
</tr>
</thead>
<tbody>
<tr>
<td>Date Approved</td>
<td>Date when the <em>Business Case</em> was approved </td>
<td>0..1</td>
<td>Date</td>
</tr>
<tr>
<td>Date Initiated</td>
<td>Date when the <em>Business Case</em> was initiated </td>
<td>0..1</td>
<td>Date</td>
</tr>
<tr>
<td>Outcomes (objectives)</td>
<td>Outcomes (objectives) that the proposed work in the <em>Business Case</em> would achieve </td>
<td>1..*</td>
<td>String</td>
</tr>
<tr>
<td>Outputs (deliverables)</td>
<td>Outputs (deliverables) that the proposed work in the <em>Business Case</em> would deliver </td>
<td>1..*</td>
<td>String</td>
</tr>
<tr>
<td>Type</td>
<td>E.g. new programme, permanent (indefinite) change to existing programme, temporary change to existing programme, cease programme.</td>
<td>1..*</td>
<td>ControlledVocabulary</td>
</tr>
</tbody>
</table>
<p>* Attributes inherited from super-type(s) are not included here</p>
<h3 id="business-function"> Business Function </h3>
<strong>Definition</strong>
<table class="simple">
<thead>
<tr>
<th>
<strong>Class</strong>
</th>
<th>
<strong>Group</strong>
</th>
<th>
<strong>Definition</strong>
</th>
<th>
<strong>Explanatory Text</strong>
</th>
<th>
<strong>Synonyms</strong>
</th>
</tr>
</thead>
<tbody>
<tr>
<td>Business Function</td>
<td>Business</td>
<td>activities undertaken by a statistical organisation to achieve its objectives</td>
<td>A <em>Business</em>
<em>Function</em> delivers added value from a business point of view. It is delivered by bringing together people, processes and technology (resources), for a specific business purpose. <em>Business Functions</em> answer in a generic sense What business purpose does this <em>Business Service _or</em> Process Step_ serve? (c.f. Business Process answers the question of How?). Through identifying the <em>Business Function</em> associated with each <em>Business Service</em> or <em>Process Step</em>, it increases the documentation of the use of the associated <em>Business Services</em> and <em>Process Steps</em>, to enable future reuse. A <em>Business Function</em> may be defined directly with descriptive text and/or through reference to an existing catalogue of <em>Business Functions</em>. The phases and sub-processes defined within GSBPM can be used as an internationally agreed basis for cataloguing high-level <em>Business Functions</em>. A catalogue might also include <em>Business Functions</em> defined at a lower level than sub-process. For example, Identify and address outliers might be catalogued as a lower level <em>Business Function</em> with the Review and validate function (5.3) defined within GSBPM.
</td>
<td> </td>
</tr>
</tbody>
</table>
<strong>Attributes</strong>
<p>* Attributes inherited from super-type(s) are not included here</p>
<h3 id="business-process"> Business Process </h3>
<strong>Definition</strong>
<table class="simple">
<thead>
<tr>
<th>
<strong>Class</strong>
</th>
<th>
<strong>Group</strong>
</th>
<th>
<strong>Definition</strong>
</th>
<th>
<strong>Explanatory Text</strong>
</th>
<th>
<strong>Synonyms</strong>
</th>
</tr>
</thead>
<tbody>
<tr>
<td>Business Process</td>
<td>Business</td>
<td>structured and repeatable activity that performs one or more <em>Business Functions</em>
</td>
<td>For example, a particular <em>Statistical Programme Cycle</em> might include several data acquisition activities, the corresponding editing activities for each acquisition and the production and dissemination of final outputs. Each of these may be considered separate <em>Business Processes</em> for the <em>Statistical Programme Cycle</em>. </td>
<td> </td>
</tr>
</tbody>
</table>
<strong>Attributes</strong>
<p>* Attributes inherited from super-type(s) are not included here</p>
<h3 id="business-service"> Business Service </h3>
<strong>Definition</strong>
<table class="simple">
<thead>
<tr>
<th>
<strong>Class</strong>
</th>
<th>
<strong>Group</strong>
</th>
<th>
<strong>Definition</strong>
</th>
<th>
<strong>Explanatory Text</strong>
</th>
<th>
<strong>Synonyms</strong>
</th>
</tr>
</thead>
<tbody>
<tr>
<td>Business Service</td>
<td>Business</td>
<td>means of performing a <em>Business Function</em>
</td>
<td>A <em>Business</em>
<em>Service</em> may provide one means of accessing a particular <em>Business Function</em>. The operation of a <em>Business Service</em> will perform one or more <em>Business Processes</em>. The explicitly defined interface of a <em>Business Service</em> can be seen as representing a service contract. If particular inputs are provided then the service will deliver particular outputs in compliance within specific parameters (for example, within a particular period of time). Note: The interface of a <em>Business Service</em> is not necessarily IT based. For example, a typical postal service will have a number of service interfaces: <br>- Public letter box for posting letters <br>- Counter at post office for interacting with postal workers
</td>
<td> </td>
</tr>
</tbody>
</table>
<strong>Attributes</strong>
<table class="simple">
<thead>
<tr>
<th>
<strong>Name</strong>