forked from amgadabdelhafez/IT4IT-RA-in-Archi
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathIT4IT_Reference_Architecture-V0.1.archimate.bak
More file actions
4254 lines (4178 loc) · 330 KB
/
IT4IT_Reference_Architecture-V0.1.archimate.bak
File metadata and controls
4254 lines (4178 loc) · 330 KB
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
<?xml version="1.0" encoding="UTF-8"?>
<archimate:model xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:archimate="http://www.archimatetool.com/archimate" xmlns:canvas="http://www.archimatetool.com/archimate/canvas" name="SMAG V7" id="6a18db2b" version="3.1.1">
<folder name="Business" id="7b608ab1" type="business">
<element xsi:type="archimate:BusinessActor" id="75d26025" name="Service Provider">
<documentation>Party 2 in Contract
</documentation>
</element>
<element xsi:type="archimate:BusinessActor" id="7430b38a" name="Service Consumer">
<documentation>Party 1 in Contract
</documentation>
</element>
<element xsi:type="archimate:BusinessRole" id="c633df8a" name="Requester"/>
<element xsi:type="archimate:BusinessRole" id="96d14f95" name="Fulfiller"/>
<element xsi:type="archimate:Contract" id="d9b126b8" name="Service Agreement"/>
<element xsi:type="archimate:BusinessInterface" id="1dca85ea" name="Service Desk"/>
<element xsi:type="archimate:BusinessService" id="cb617a48" name="IMaaS">
<documentation>Incident Management as a Service</documentation>
</element>
<element xsi:type="archimate:BusinessEvent" id="7e1dcbf0" name="Submit Request"/>
<element xsi:type="archimate:BusinessProcess" id="bc02e1bf" name="Requested "/>
<element xsi:type="archimate:BusinessProcess" id="60262786" name="Facknowledged "/>
<element xsi:type="archimate:BusinessProcess" id="0ecbcd32" name="Opened "/>
<element xsi:type="archimate:BusinessProcess" id="7e548be9" name="Assigned "/>
<element xsi:type="archimate:BusinessProcess" id="5b059180" name="GAcknowledged "/>
<element xsi:type="archimate:BusinessProcess" id="71b44618" name="Pending "/>
<element xsi:type="archimate:BusinessProcess" id="c4f17f85" name="Resolved "/>
<element xsi:type="archimate:BusinessProcess" id="531870e0" name="Worked "/>
<element xsi:type="archimate:BusinessProcess" id="ca629ab4" name="Canceled "/>
<element xsi:type="archimate:BusinessProcess" id="1fb660b3" name="Closed "/>
<element xsi:type="archimate:BusinessActor" id="6db30003" name="Requester"/>
<element xsi:type="archimate:BusinessObject" id="408c9cc2" name="Smart Agreement Template">
<documentation>The Logical Model for the Smart Agreement between two parties
This will be the base (class) for the SmAg between the contracting parties
</documentation>
</element>
<element xsi:type="archimate:BusinessProcess" id="d9f878bd" name="Implement Agreement"/>
<element xsi:type="archimate:BusinessProcess" id="9f8e9022" name="Operate Agreement"/>
<element xsi:type="archimate:BusinessProcess" id="c6434aa4" name="Update Agreement"/>
<element xsi:type="archimate:BusinessProcess" id="25e71bf9" name="Terminate Agreement"/>
<element xsi:type="archimate:BusinessProcess" id="e9e88d47" name="Retire Agreement"/>
<element xsi:type="archimate:BusinessActor" id="1dae7697" name="3rd Party">
<documentation>Implementer</documentation>
</element>
<element xsi:type="archimate:BusinessEvent" id="ae20d337" name="Demand for new SmartAgreement"/>
<element xsi:type="archimate:BusinessProcess" id="e99414cd" name="Define SmartAgreement Draft">
<documentation>Requirements Documentation</documentation>
</element>
<element xsi:type="archimate:BusinessService" id="d70dd147" name="SmartAgreement Templates"/>
<element xsi:type="archimate:BusinessEvent" id="8ab7086b" name="Issue RFP"/>
<element xsi:type="archimate:BusinessProcess" id="8ebdc79a" name="Evaluate Proposals"/>
<element xsi:type="archimate:BusinessEvent" id="fbbacaec" name="Award Proposal"/>
<element xsi:type="archimate:BusinessObject" id="bfeb7a68" name="Request for Proposal"/>
<element xsi:type="archimate:BusinessFunction" id="e09b940b" name="Design SmartAgreement Offering"/>
<element xsi:type="archimate:BusinessObject" id="c4c07ae3" name="Proposal"/>
<element xsi:type="archimate:BusinessCollaboration" id="e75d2fbb" name="Negotiate terms and conditions"/>
<element xsi:type="archimate:BusinessFunction" id="713fcea4" name="Procurement"/>
<element xsi:type="archimate:BusinessInteraction" id="8788c92a" name="Solicitation"/>
<element xsi:type="archimate:BusinessEvent" id="ff0d153e" name="Selection"/>
<element xsi:type="archimate:BusinessProcess" id="caf068a1" name="Budgetting">
<documentation>Budgeting enables an organization to plan future IT expenditures, reducing the risk of over-spending and ensuring the revenues are available to cover the predicted spend. Additionally, budgeting allows an organization to compare actual costs with previously predicted costs in order to improve the reliability of budgeting predictions.
Cost types, codes
capital/revenue
fixed & variable
</documentation>
</element>
<element xsi:type="archimate:BusinessProcess" id="8ae95a75" name="Charging">
<documentation>Charging provides the ability to assign costs of an IT Service proportionally and fairly to the users of that service. It may be used as a first step towards an IT organization operating as an autonomous business. It may also be used to encourage users to move in a strategically important direction - for example by subsidizing newer systems and imposing additional charges for the use of legacy systems. Transparency of charging will encourage users to avoid expensive activities where slightly more inconvenient but far cheaper alternatives are available. For example, a user might browse a dump on screen rather than printing it off.
Charging is arguably the most complex of the three sub-processes, requiring a large investment of resources and a high degree of care to avoid anomalies, where an individual department may benefit from behavior which is detrimental to the company as a whole. Charging policy needs to be simultaneously simple, fair and realistic.
Charging need not necessarily mean money changing hands (full charging). It may take the form of information passed to management on the cost of provision of IT services (no charging), or may detail what would be charged if full charging were in place without transactions actually being applied to the financial ledgers (notional charging). Notional charging may also be used as a way of piloting full charging.
Cost, Cost plus, market rate, notional
</documentation>
</element>
<element xsi:type="archimate:BusinessProcess" id="89239ca6" name="Accounting">
<documentation>IT accounting is concerned with the amount of money spent in providing IT services. It allows an organization to perform various financial analyses to gauge the efficiency of the IT service provision and determine areas where cost savings can be made. It will also provide financial transparency to aid management in the decision making process.
direct/indirect
unabsorable overheads
TCO ROI
</documentation>
</element>
<element xsi:type="archimate:BusinessObject" id="a329fc5a" name="Service"/>
<element xsi:type="archimate:BusinessObject" id="2006ac2a" name="Supplier"/>
<element xsi:type="archimate:BusinessObject" id="2fbfd0a8" name="Clearance"/>
<element xsi:type="archimate:BusinessObject" id="cb999f8f" name="Duration"/>
<element xsi:type="archimate:BusinessObject" id="8ef3ae4e" name="Interfaces"/>
<element xsi:type="archimate:BusinessObject" id="6c1f245d" name="Communication"/>
<element xsi:type="archimate:BusinessObject" id="140eefd6" name="Service Times"/>
<element xsi:type="archimate:BusinessObject" id="5b3b6eeb" name="Support Types"/>
<element xsi:type="archimate:BusinessObject" id="2eab7f76" name="Support Levels"/>
<element xsi:type="archimate:BusinessActor" id="872666bd" name="CFO"/>
<element xsi:type="archimate:BusinessActor" id="98b01666" name="Fulfiller"/>
<element xsi:type="archimate:BusinessObject" id="9d410e42" name="Bill of IT"/>
<element xsi:type="archimate:BusinessObject" id="61df495a" name="General Ledger"/>
<element xsi:type="archimate:BusinessObject" id="33378635" name="IT Service Invoice"/>
<element xsi:type="archimate:BusinessObject" id="6e424f1c" name="Cost Data for Service Provisioning ">
<documentation>The cost for providing a service, calculated by Financial Management as a basis for calculating the price a customer is expected to pay for a service.
</documentation>
</element>
<element xsi:type="archimate:BusinessProcess" id="19e1fdfd" name="Service Portfolio Review ">
<documentation>Process Objective: To assess the Service Portfolio at regular intervals in order to ensure the service provider offers economically viable services which are aligned with the Service Strategy. This process also keeps the Service Portfolio up to date.
</documentation>
</element>
<element xsi:type="archimate:BusinessObject" id="9404db4b" name="Invoice ">
<documentation>The invoice for the delivery of a service or product.
</documentation>
</element>
<element xsi:type="archimate:BusinessProcess" id="836ff324" name="Financial Management Support">
<documentation>Process Objective: To define the necessary structures for the management of financial planning data and costs, as well as for the allocation of costs to services.
</documentation>
</element>
<element xsi:type="archimate:BusinessObject" id="fcbad65f" name="IT Budget ">
<documentation>The IT Budget is an annual financial plan that provides a forecast of expected expenditures and allocates financial resources to the various service management processes and organizational units within the IT organization.
</documentation>
</element>
<element xsi:type="archimate:BusinessProcess" id="2df4d800" name="Financial Planning ">
<documentation>Process Objective: To determine the required financial resources over the next planning period ("IT Budget"), and to allocate those resources for optimum benefits.
</documentation>
</element>
<element xsi:type="archimate:BusinessObject" id="27669129" name="Service Model ">
<documentation>A Service Model is a high-level description of a service and the components required to deliver that service. The main purpose of Service Models is to facilitate an understanding of what service components, assets and other resources are necessary to create the service, including their interactions. Service Models are a valuable tool for understanding the impact of proposed new or changed services on other services at an early stage. (Note: New output in ITIL 2011.)
</documentation>
</element>
<element xsi:type="archimate:BusinessActor" id="1b2201ac" name="IT Steering Group (ISG) ">
<documentation>The IT Steering Group (ISG) sets the direction and strategy for IT Services. It includes members of senior management from business and IT. The IT Steering Group reviews the business and IT strategies in order to make sure that they are aligned. It also sets priorities of service development programs/ projects.
</documentation>
</element>
<element xsi:type="archimate:BusinessObject" id="844d3c5c" name="Financial Data Categories ">
<documentation>Various categories are used to structure financial data, as a means to gain insight into the underlying costs of service provisioning and service profitability.
</documentation>
</element>
<element xsi:type="archimate:BusinessActor" id="2411066d" name="Service Owner"/>
<element xsi:type="archimate:BusinessObject" id="5fa46d99" name="Financial Analysis ">
<documentation>The Financial Analysis is an important input to the Portfolio Management process. It contains information on the costs for providing services and provides insight into the profitability of services and customers (see also: ITIL Checklist Financial Analysis).
</documentation>
</element>
<element xsi:type="archimate:BusinessObject" id="43327432" name="Service Portfolio Review Report ">
<documentation>A document containing the results and findings from a Service Portfolio Review. This report is an important input to the strategic service assessment.
</documentation>
</element>
<element xsi:type="archimate:BusinessProcess" id="7ef131c5" name="Charging">
<documentation>is the activity whereby payment is required for services delivered. Charging requires that accounting procedures and systems exist and are set up. It makes a difference whether the organization is an internal service provider, or if it serves external customer as its main business. In the case where an IT organization is an internal service provider (according to ITIL, these are Type I and Type II organizations), it is not necessary to bill for services. Sometimes such IT organizations only allocate costs. If an IT organization sells its services to external customers (Type III organization) they will, certainly, issue bills for their services and generate income which funds that organization.
Charging for services by an organization with external customers is the only way to get funding for the organization, cover costs and generate revenue. But, in the case of an internal service provider it can be seen as bureaucratic procedure, which is true. On the other side, I found that internal charging has several advantages:
It justifies IT resources needed (increased transparency),
users throughout organization use only resources they really need (optimization of usage),
business can plan their cost of operation (which is, further on, included in price charged to their customers), and
IT has better control of its business.</documentation>
</element>
<element xsi:type="archimate:BusinessProcess" id="826eb4ba" name="Design Agreement"/>
<element xsi:type="archimate:BusinessFunction" id="cb7c283c" name="Budget Allocation ">
<documentation>A budget allocated by the Financial Manager to implement a Change. Budget Allocations are issued in response to Budget Requests originating from any Service Management process in conjunction with Requests for Change.
</documentation>
</element>
<element xsi:type="archimate:BusinessService" id="cd9c5819" name="Bilateral netting">
<documentation>an arrangement whereby two parties net their bilateral obligations
</documentation>
</element>
<element xsi:type="archimate:BusinessProcess" id="68b5fe19" name="Service Invoicing ">
<documentation>Process Objective: To issue invoices for the provision of services and transmission of the invoice to the customer.
</documentation>
</element>
<element xsi:type="archimate:BusinessObject" id="597461b6" name="Budget Request ">
<documentation>A request for a budget, typically issued from any of the Service Management processes at the same time when compiling a Request for Change. An approved Budget Request means that the required financial resources for implementing a Change are approved by Financial Management.
</documentation>
</element>
<element xsi:type="archimate:BusinessProcess" id="f0ed961f" name="Financial Analysis and Reporting ">
<documentation>Process Objective: To analyze the structure of service provisioning cost and the profitability of services. The resulting financial analysis allows Service Portfolio Management to make informed decisions when deciding about changes to the Service Portfolio.
</documentation>
</element>
<element xsi:type="archimate:BusinessProcess" id="662f83b8" name="Approve new or changed Services ">
<documentation>Process Objective: To submit a formal Change Proposal to Change Management, and to initiate the design stage for the new or changed service if the Change Proposal is authorized.
</documentation>
</element>
<element xsi:type="archimate:BusinessActor" id="4685baaa" name="Service Portfolio Manager">
<documentation>The Service Portfolio Manager decides on a strategy to serve customers in cooperation with the IT Steering Group, and develops the service provider's offerings and capabilities.
</documentation>
</element>
<element xsi:type="archimate:BusinessObject" id="f6856e7c" name="Service Portfolio ">
<documentation>The Service Portfolio represents a complete list of the services managed by a service provider; some of these services are visible to the customers, while others are not. It contains present contractual commitments, new service development, and ongoing service improvement plans initiated by Continual Service Improvement. It also includes third-party services which are an integral part of service offerings to customers. The Service Portfolio is divided into three phases: Service Pipeline, Service Catalogue, and Retired Services (see also: ITIL Checklist Service Portfolio).
</documentation>
</element>
<element xsi:type="archimate:BusinessProcess" id="e05d2a7f" name="Define and Analyze new or changed Services ">
<documentation>Process Objective: To define the desired outcomes of a proposed new or changed service, analyze the impacts on existing services in the Service Portfolio, and determine the assets required to offer the service.
</documentation>
</element>
<element xsi:type="archimate:BusinessFunction" id="486578b3" name="Clearing"/>
<element xsi:type="archimate:BusinessObject" id="bbd4d740" name="Service Charter ">
<documentation>The Service Charter is a high-level description of a new or substantially changed service and the approach to build that service. In particular, the Service Charter outlines the deliverables to be created during the service implementation project, the required resources, and an initial project schedule. Service Charters are passed to Service Design to initiate the detailed design of the new or changed service. (Note: New output in ITIL 2011.)
</documentation>
</element>
<element xsi:type="archimate:BusinessProcess" id="9578befa" name="Clearing">
<documentation>transmitting, reconciling and, in some cases, confirming transfer orders prior to settlement, potentially including the netting of orders and the establishment of final positions for settlement. Sometimes this term is also used (imprecisely) to cover settlement. For the clearing of futures and options, this term also refers to the daily balancing of profits and losses and the daily calculation of collateral requirements. </documentation>
</element>
<element xsi:type="archimate:BusinessObject" id="c5f889f7" name="Change Proposal ">
<documentation>A Change Proposal describes a proposed major Change, like the introduction of a new service or a substantial change to an existing service. The purpose of Change Proposals is to communicate a proposed major Change and assess its risk, impact and feasibility before design activities begin. Change Proposals are typically created in Service Portfolio Management.
</documentation>
</element>
<element xsi:type="archimate:BusinessActor" id="b4d08a7e" name="Access Manager">
<documentation>The Access Manager grants authorized users the right to use a service, while preventing access to non-authorized users., The Access Manager essentially executes policies defined in Information Security Management.</documentation>
</element>
<element xsi:type="archimate:BusinessActor" id="a15894e7" name="Risk Manager">
<documentation>The Risk Manager is responsible for identifying, assessing and controlling risks., This includes analyzing the value of assets to the business, identifying threats to those assets, and evaluating how vulnerable each asset is to those threats.</documentation>
</element>
<element xsi:type="archimate:BusinessActor" id="d9eee3a2" name="Service Catalogue Manager">
<documentation>The Service Catalogue Manager is responsible for maintaining the Service Catalogue, ensuring that all information within the Service Catalogue is accurate and up-to-date.</documentation>
</element>
<element xsi:type="archimate:BusinessActor" id="5dc3aa4c" name="1st Level Support">
<documentation>The responsibility of 1st Level Support is to register and classify received Incidents and to undertake an immediate effort in order to restore a failed IT service as quickly as possible., If no ad-hoc solution can be achieved, 1st Level Support will transfer the Incident to expert technical support groups (2nd Level Support)., 1st Level Support also processes Service Requests and keeps users informed about their Incidents' status at agreed intervals.</documentation>
</element>
<element xsi:type="archimate:BusinessActor" id="530c65f7" name="Incident Manager">
<documentation>The Incident Manager is responsible for the effective implementation of the Incident Management process and carries out the corresponding reporting., He represents the first stage of escalation for Incidents, should these not be resolvable within the agreed Service Levels.</documentation>
</element>
<element xsi:type="archimate:BusinessActor" id="8ec4fb68" name="Knowledge Manager">
<documentation>The Knowledge Manager ensures that the IT organization is able to gather, analyze, store and share knowledge and information., His primary goal is to improve efficiency by reducing the need to rediscover knowledge.</documentation>
</element>
<element xsi:type="archimate:BusinessActor" id="e153c2fc" name="3rd Level Support">
<documentation>3rd Level Support is typically located at hardware or software manufacturers (third-party suppliers)., Its services are requested by 2nd Level Support if required for solving an Incident., The aim is to restore a failed IT Service as quickly as possible.</documentation>
</element>
<element xsi:type="archimate:BusinessActor" id="6017bf04" name="IT Steering Group (ISG)">
<documentation>The IT Steering Group (ISG) sets the direction and strategy for IT Services. It includes members of senior management from business and IT., The ISG reviews the business and IT strategies in order to make sure that they are aligned., It also sets priorities of service development programs/ projects.</documentation>
</element>
<element xsi:type="archimate:BusinessActor" id="cb0388d4" name="Capacity Manager">
<documentation>The Capacity Manager is responsible for ensuring that services and infrastructure are able to deliver the agreed capacity and performance targets in a cost effective and timely manner., He considers all resources required to deliver the service, and plans for short, medium and long term business requirements.</documentation>
</element>
<element xsi:type="archimate:BusinessActor" id="1ed4c65d" name="Configuration Manager">
<documentation>The Configuration Manager is responsible for maintaining information about Configuration Items required to deliver IT services., To this end he maintains a logical model, containing the components of the IT infrastructure (CIs) and their associations., Emergency Change Advisory Board (ECAB), A sub-set of the Change Advisory Board who makes decisions about high impact Emergency Changes., Membership of the ECAB may be decided at the time a meeting is called, and depends on the nature of the Emergency Change.</documentation>
</element>
<element xsi:type="archimate:BusinessActor" id="b61c86b2" name="Release Manager">
<documentation>The Release Manager is responsible for planning and controlling the movement of Releases to test and live environments.</documentation>
</element>
<element xsi:type="archimate:BusinessActor" id="766c86a5" name="Major Incident Team">
<documentation>A dynamically established team of IT managers and technical experts, usually under the leadership of the Incident Manager, formulated to concentrate on the resolution of a Major Incident.</documentation>
</element>
<element xsi:type="archimate:BusinessActor" id="cc8556e2" name="Information Security Manager">
<documentation>The Information Security Manager is responsible for ensuring the confidentiality, integrity and availability of an organization’s assets, information, data and IT services., He is usually involved in an organizational approach to Security Management which has a wider scope than the IT service provider, and includes handling of paper, building access, phone calls etc., for the entire organization.</documentation>
</element>
<element xsi:type="archimate:BusinessActor" id="fac3ea99" name="Service Owner">
<documentation>The Service Owner is responsible for delivering a particular service within the agreed service levels., Typically, he acts as the counterpart of the Service Level Manager when negotiating Operational Level Agreements (OLAs)., Often, the Service Owner will lead a team of technical specialists or an internal support unit.</documentation>
</element>
<element xsi:type="archimate:BusinessActor" id="da1f1230" name="Problem Manager">
<documentation>The Problem Manager is responsible for managing the lifecycle of all Problems., His primary objectives are to prevent Incidents from happening, and to minimize the impact of Incidents that cannot be prevented., To this purpose he maintains information about Known Errors and Workarounds.</documentation>
</element>
<element xsi:type="archimate:BusinessActor" id="673573d0" name="IT Operations Manager">
<documentation>An IT Operations Manager will be needed to take overall responsibility for a number of Service Operation activities., For instance, this role will ensure that all day-to-day operational activities are carried out in a timely and reliable way.</documentation>
</element>
<element xsi:type="archimate:BusinessActor" id="7437c0c2" name="Service User">
<documentation>A person who uses one or several IT services on a day-to-day basis. Service Users are distinct from Customers, as some Customers do not use IT services directly., </documentation>
</element>
<element xsi:type="archimate:BusinessActor" id="b948138c" name="Project Manager">
<documentation>The Project Manager is responsible for planning and coordinating the resources to deploy a major Release within the predicted cost, time and quality estimates., The Release Manager is responsible for planning and controlling the movement of Releases to test and live environments.</documentation>
</element>
<element xsi:type="archimate:BusinessActor" id="3b3ddeb2" name="Process Architect">
<documentation>The Process Architect is responsible for maintaining the Process Architecture (part of the Enterprise Architecture), coordinating all changes to processes and making sure that all processes cooperate in a seamless way., This role often also supports all parties involved in managing and improving processes, in particular the Process Owners. Some organizations combine this role with the Enterprise Architect role.</documentation>
</element>
<element xsi:type="archimate:BusinessActor" id="0f635945" name="Application Developer">
<documentation>The Application Developer is responsible for making available applications and systems which provide the required functionality for IT services., This includes the development and maintenance of custom applications as well as the customization of products from software vendors.</documentation>
</element>
<element xsi:type="archimate:BusinessActor" id="d0f75ceb" name="Supplier Manager">
<documentation>The Supplier Manager is responsible for ensuring that value for money is obtained from all suppliers., He makes sure that contracts with suppliers support the needs of the business, and that all suppliers meet their contractual commitments.</documentation>
</element>
<element xsi:type="archimate:BusinessActor" id="6f74ed73" name="Technical Analyst">
<documentation>The Technical Analyst is a Technical Management role which provides technical expertise and support for the management of the IT infrastructure., There is typically one Technical Analyst or team of analysts for every key technology area., This role plays an important part in the technical aspects of designing, testing, operating and improving IT services., It is also responsible for developing the skills required to operate the IT infrastructure., ITIL roles and boards - Service Transition</documentation>
</element>
<element xsi:type="archimate:BusinessActor" id="13224895" name="Compliance Manager">
<documentation>The Compliance Manager's responsibility is to ensure that standards and guidelines is followed, or that proper, consistent accounting or other practices are being employed., This includes to make sure that external legal requirements are fulfilled.</documentation>
</element>
<element xsi:type="archimate:BusinessActor" id="65ff89e4" name="IT Service Continuity Manager">
<documentation>The IT Service Continuity Manager is responsible for managing risks that could seriously impact IT services., He ensures that the IT service provider can provide minimum agreed service levels in cases of disaster, by reducing the risk to an acceptable level and planning for the recovery of IT services.</documentation>
</element>
<element xsi:type="archimate:BusinessActor" id="05aa2d99" name="Customer">
<documentation>Someone who buys IT services., The Customer of an IT service provider is the person or group who defines and agrees the service level targets.</documentation>
</element>
<element xsi:type="archimate:BusinessActor" id="c7706792" name="Service Strategy Manager">
<documentation>The Service Strategy Manager supports the IT Steering Group in producing and maintaining the service provider's strategy., This role is also responsible for communicating and implementing the service strategy., The Service Strategy Manager has been introduced as a new role in ITIL 2011.</documentation>
</element>
<element xsi:type="archimate:BusinessActor" id="650606f9" name="CSI Manager">
<documentation>The Continual Service Improvement (CSI) Manager is responsible for managing improvements to IT Service Management processes and IT services., He will continually measure the performance of the service provider and design improvements to processes, services and infrastructure in order to increase efficiency, effectiveness, and cost effectiveness.</documentation>
<property key="SN_Role" value="[csi_manager]"/>
</element>
<element xsi:type="archimate:BusinessActor" id="0d52ee63" name="Demand Manager">
<documentation>The role Demand Manager has been introduced in ITIL 2011 to perform the activities in the Demand Management process., The Demand Manager is responsible for understanding, anticipating and influencing customer demand for services., The Demand Manager works with capacity management to ensure that the service provider has sufficient capacity to meet the required demand.</documentation>
</element>
<element xsi:type="archimate:BusinessActor" id="50b4f1fc" name="Process Owner">
<documentation>A role responsible for ensuring that a process is fit for purpose., The Process Owner’s responsibilities include sponsorship, design, and continual improvement of the process and its metrics., In larger organizations there might be separate Process Owner and Process Manager roles, where the Process Manager has responsibility for the operational management of a process., ITIL roles outside the IT organization</documentation>
</element>
<element xsi:type="archimate:BusinessActor" id="fceed450" name="Service Portfolio Manager">
<documentation>The Service Portfolio Manager decides on a strategy to serve customers in cooperation with the IT Steering Group, and develops the service provider's offerings and capabilities.</documentation>
</element>
<element xsi:type="archimate:BusinessActor" id="3792f150" name="Service Level Manager">
<documentation>The Service Level Manager is responsible for negotiating Service Level Agreements and ensuring that these are met., He makes sure that all IT Service Management processes, Operational Level Agreements and Underpinning Contracts are appropriate for the agreed service level targets., The Service Level Manager also monitors and reports on service levels.</documentation>
</element>
<element xsi:type="archimate:BusinessActor" id="1f269918" name="IT Operator">
<documentation>IT Operators are the staff who perform the day-to-day operational activities., Typical responsibilities include: Performing backups, ensuring that scheduled jobs are performed, installing standard equipment in the data center.</documentation>
</element>
<element xsi:type="archimate:BusinessActor" id="e01f1539" name="Change Advisory Board (CAB)">
<documentation>A group of people that advises the Change Manager in the assessment, prioritization and scheduling of Changes., This board is usually made up of representatives from all areas within the IT organization, the business, and third parties such as suppliers.</documentation>
</element>
<element xsi:type="archimate:BusinessActor" id="44d5066e" name="Change Manager">
<documentation>The Change Manager controls the lifecycle of all Changes., His primary objective is to enable beneficial Changes to be made, with minimum disruption to IT services., For important Changes, the Change Manager will refer the authorization of Changes to the Change Advisory Board (CAB).</documentation>
</element>
<element xsi:type="archimate:BusinessActor" id="b2ba5d2a" name="Test Manager">
<documentation>The Test Manager ensures that deployed Releases and the resulting services meet customer expectations, and verifies that IT operations is able to support the new service., ITIL roles and boards - Service Operation</documentation>
</element>
<element xsi:type="archimate:BusinessActor" id="75fef400" name="Applications Analyst">
<documentation>The Applications Analyst is an Application Management role which manages applications throughout their lifecycle., There is typically one Applications Analyst or team of analysts for every key application., This role plays an important part in the application-related aspects of designing, testing, operating and improving IT services., It is also responsible for developing the skills required to operate the applications required to deliver IT services.</documentation>
</element>
<element xsi:type="archimate:BusinessActor" id="ad584f18" name="Service Design Manager">
<documentation>The Service Design Manager is responsible for producing quality, secure and resilient designs for new or improved services., This includes producing and maintaining all design documentation.</documentation>
</element>
<element xsi:type="archimate:BusinessActor" id="9d7597c5" name="Availability Manager">
<documentation>The Availability Manager is responsible for defining, analyzing, planning, measuring and improving all aspects of the availability of IT services., He is responsible for ensuring that all IT infrastructure, processes, tools, roles etc. are appropriate for the agreed service level targets for availability.</documentation>
</element>
<element xsi:type="archimate:BusinessActor" id="1fd9a8fa" name="Service Request Fulfilment Group">
<documentation>Service Request Fulfilment Groups specialize on the fulfillment of certain types of Service Requests., Typically, 1st Level Support will process simpler requests, while others are forwarded to the specialized Fulfilment Groups., ITIL roles - Continual Service Improvement</documentation>
</element>
<element xsi:type="archimate:BusinessActor" id="85b9094d" name="Enterprise Architect">
<documentation>The Enterprise Architect is responsible for maintaining the Enterprise Architecture (EA), a description of the essential components of a business, including their interrelationships., Bigger organizations may opt to introduce specialist EA roles like Business Architect, Application Architect, Information Architect, or Infrastructure Architect.</documentation>
</element>
<element xsi:type="archimate:BusinessActor" id="841d9971" name="Business Relationship Manager">
<documentation>The Business Relationship Manager is responsible for maintaining a positive relationship with customers, identifying customer needs and ensuring that the service provider is able to meet these needs with an appropriate catalogue of services., The Business Relationship Manager works closely with the Service Level Manager., The Business Relationship Manager has been introduced as a new role in ITIL 2011.</documentation>
</element>
<element xsi:type="archimate:BusinessActor" id="e1f46804" name="2nd Level Support">
<documentation>2nd Level Support takes over Incidents which cannot be solved immediately with the means of 1st Level Support., If necessary, it will request external support, e.g. from software or hardware manufacturers., The aim is to restore a failed IT Service as quickly as possible.</documentation>
</element>
<element xsi:type="archimate:BusinessActor" id="0e827a0e" name="Facilities Manager">
<documentation>The Facilities Manager is responsible for managing the physical environment where the IT infrastructure is located., This includes all aspects of managing the physical environment, for example power and cooling, building access management, and environmental monitoring.</documentation>
</element>
<element xsi:type="archimate:BusinessActor" id="74d2ddcd" name="Financial Manager">
<documentation>The Financial Manager is responsible for managing an IT service provider's budgeting, accounting and charging requirements.</documentation>
</element>
<element xsi:type="archimate:BusinessProcess" id="3f2ebf53" name="Showback"/>
<element xsi:type="archimate:BusinessProcess" id="1879ba42" name="Chargeback"/>
<element xsi:type="archimate:BusinessProcess" id="7209ac7f" name="Activity based costing"/>
<element xsi:type="archimate:BusinessProcess" id="b2675f32" name="Performnce Based Charging"/>
<element xsi:type="archimate:BusinessProcess" id="64675337" name="Cost Analysis">
<documentation>Cost reports (standard, custom, ad hoc) are generated and the results are analyzed
Operational and business partner analytics performed on costing results
Compare actual output values with budgeted values</documentation>
</element>
<element xsi:type="archimate:BusinessProcess" id="caddabc9" name="Cost Assignment">
<documentation>Costing relationships are developed and required calculations performed Costing relationships are developed and required calculations performed
Design and development of IT cost models
Production of cost for products, services, applications and business partners.</documentation>
</element>
<element xsi:type="archimate:BusinessObject" id="cf29a9c2" name="Costing Model"/>
<element xsi:type="archimate:BusinessObject" id="17b6b911" name="Allocation Model"/>
<element xsi:type="archimate:BusinessProcess" id="6d929cd9" name="Data Collection ">
<documentation>Financial and operational data is collected, loaded and data owners identified
Review and analysis of the data collection and maintenance process
Design and implementation of data integration
Identification and selection of operational data used for cost drivers. </documentation>
</element>
<element xsi:type="archimate:BusinessProcess" id="966b73d4" name="Manage Business">
<documentation>Manage Business
Analytics are translated into business decisions
Integration of actual cost results into the budgeting and forecasting processes
Review results with operations and business partners identifying improvement opportunities. </documentation>
</element>
<element xsi:type="archimate:BusinessFunction" id="f1d5788e" name="Planning"/>
<element xsi:type="archimate:BusinessFunction" id="5aa5a6d6" name="Allocate IT Costs"/>
<element xsi:type="archimate:BusinessFunction" id="2a8704f6" name="Calculate usage cost (invoice)"/>
<element xsi:type="archimate:BusinessFunction" id="78435270" name="Variance Analysis"/>
<element xsi:type="archimate:BusinessFunction" id="645a9cba" name="Forecacsting"/>
<element xsi:type="archimate:BusinessProcess" id="ffb42cb0" name="IT Financial Management">
<documentation>Financial Management
2.4.1 Process Overview
The Financial Management process provides the business and IT with the quantification (in financial terms) of the value of IT services, the value of the assets underlying the provisioning of those services, and the qualification of operational forecasting. It includes all function and processes responsible for managing an IT service provider's budgeting, accounting and charging policies and activities.
Key objectives of Financial Management are:
• Establishing and enforcing IT financial controls
• Ensuring compliance with legal, industry, and corporate standards and procedures
Assisting IT portfolio investment decisions by providing detailed business cases as well as financial input for decision support
• Effectively predicting and controlling IT budgets
• Providing the enterprise with operational visibility, insight, and superior decision-making.
The overriding goal of Financial Management is to provide cost effective stewardship of the IT assets and the financial resources used in providing IT services. Primarily this is to enable an organization to account fully for the financial resources consumed by the IT service provider and to attribute these costs to the services delivered to the organization’s customers.
This is accomplished by the categorization, collection and analysis of accounting, contract and pricing data including the following typical cost elements:
• Hardware and software license costs
• Annual maintenance fees for hardware and software
• Personnel resources used in the support or maintenance of a service
• Utilities, data centre or other facilities charges
• Taxes, capital or interest charges
• Compliance costs
• Transfer costs and internal charging by other business units/processes.
</documentation>
</element>
<element xsi:type="archimate:BusinessProcess" id="b8c6dd55" name="Business Impact Analysis "/>
<element xsi:type="archimate:BusinessProcess" id="59228ca8" name="Financial Demand Modelling "/>
<element xsi:type="archimate:BusinessProcess" id="518b9f2e" name="Funding Models Evaluation "/>
<element xsi:type="archimate:BusinessProcess" id="56c32011" name="Service Provisioning Analysis and Optimization "/>
<element xsi:type="archimate:BusinessProcess" id="f0d308e6" name="Service Valuation "/>
<element xsi:type="archimate:BusinessProcess" id="e88711ae" name="Variable Cost Dynamics Analysis "/>
<element xsi:type="archimate:BusinessProcess" id="3456f2e0" name="Business Process"/>
<element xsi:type="archimate:BusinessProcess" id="95d9a583" name="Auditing"/>
<element xsi:type="archimate:BusinessProcess" id="8892ccd3" name="Plan & Control Budgets ">
<documentation>Establish budgeting framework based on DoD standards. Align budgetary plants to DoD standards and the PPBE process.
</documentation>
</element>
<element xsi:type="archimate:BusinessProcess" id="92ac7abd" name="Communicate to Stakeholders ">
<documentation>Publish budget allocations to customer Business Financial Managers (BFMs) to initiate financial management budgeting process.
</documentation>
</element>
<element xsi:type="archimate:BusinessProcess" id="cdf00315" name="Service Investment Authorized? ">
<documentation>Determine whether requests for new Service Investments are approved or rejected. The Financial Management Approval Committee (a Government role which is TBD), will allocate financial and workforce resources to approved requests and communicate the authorization to stakeholders. Rejected requests are re-submitted for Service Valuation (Step 2.0).
</documentation>
</element>
<element xsi:type="archimate:BusinessProcess" id="a8167554" name="Portfolio Investment Analysis ">
<documentation>Analyze the cost and benefits of the new service(s) under consideration based on impact to the NGEN program, infrastructure, and existing services. Develop business case to support the Service Portfolio Management process.
</documentation>
</element>
<element xsi:type="archimate:BusinessProcess" id="1e1c35c2" name="Service Valuation ">
<documentation>Quantify (in financial terms), the value of IT Services and the value of the assets underlying the provisioning of those services.
</documentation>
</element>
<element xsi:type="archimate:BusinessProcess" id="f469f143" name="Initiation of Financial Analysis ">
<documentation>Assist financial management with managing IT resources using inputs from Change, Demand, Service Portfolio and Supplier Management processes.
</documentation>
</element>
<element xsi:type="archimate:BusinessProcess" id="da3b1de2" name="Business Process"/>
<element xsi:type="archimate:BusinessProcess" id="a0305641" name="Auditing">
<documentation>Examine financial data and the Financial Management process to determine level of conformance to NGEN standards and practices. This activity also identifies irregularities and improvement opportunities.</documentation>
</element>
<element xsi:type="archimate:BusinessProcess" id="be0c8a04" name="Administer Charging ">
<documentation>Recover cost of IT services by charging customers for services rendered. Deliver bills to customers for payment based on an established pricing model as defined in NGEN’s chargeback framework.
</documentation>
</element>
<element xsi:type="archimate:BusinessProcess" id="4dd3f651" name="Service Accounting ">
<documentation>Track and record all costs incurred in the NGEN program and attribute those costs to NGEN customers. Perform this activity continuously
</documentation>
</element>
<element xsi:type="archimate:BusinessProcess" id="7b56b4d5" name="Service Ordering/ Invoices ">
<documentation>Initiate procurement by selecting the appropriate supplier(s) and placing the order. Attribute actual usage data to customers and apply the NGEN pricing model to support invoicing.
</documentation>
</element>
<element xsi:type="archimate:BusinessProcess" id="765eb22d" name="Budget Execution"/>
<element xsi:type="archimate:BusinessActor" id="69de26fb" name="Financial Analyst"/>
<element xsi:type="archimate:BusinessActor" id="81e07203" name="Billing Admin"/>
<element xsi:type="archimate:BusinessActor" id="9c876846" name="Asset Manager"/>
<element xsi:type="archimate:BusinessProcess" id="09b84769" name="Cost Planning"/>
<element xsi:type="archimate:BusinessProcess" id="df1e6561" name="Determine / Revise mode of costing"/>
<element xsi:type="archimate:BusinessProcess" id="480c5c90" name="Determine / Revise budget"/>
<element xsi:type="archimate:BusinessProcess" id="36749963" name="Define / Revise Standard cost units and chargable items"/>
<element xsi:type="archimate:BusinessProcess" id="e2abe3c0" name="Determine / Revise sources for resource usage"/>
<element xsi:type="archimate:BusinessProcess" id="5550a40d" name="Determine / Revise charging policies, charging calculations, and pricing methodologies"/>
<element xsi:type="archimate:BusinessProcess" id="81c15228" name="Analyze usage and cost reporting"/>
<element xsi:type="archimate:BusinessProcess" id="b0ecd627" name="Calculate Total Cost of Ownership"/>
<element xsi:type="archimate:BusinessProcess" id="935691a0" name="Calculate invoice and bill customer"/>
<element xsi:type="archimate:BusinessProcess" id="92290fe3" name="Recieve Payment"/>
<element xsi:type="archimate:BusinessProcess" id="f155ce14" name="Track financial assets"/>
<element xsi:type="archimate:BusinessActor" id="aff33767" name="Business Unit"/>
<element xsi:type="archimate:BusinessActor" id="8c9c5e6a" name="Employee"/>
<element xsi:type="archimate:BusinessActor" id="7678e9cf" name="Manager"/>
<element xsi:type="archimate:BusinessActor" id="8f74c7b3" name="Supervisor"/>
<element xsi:type="archimate:BusinessActor" id="29d98cfa" name="User"/>
<element xsi:type="archimate:BusinessActor" id="11ec4976" name="financial management administrator">
<documentation>[financial_mgmt_admin]
Sets up and administers the entire cost model, which includes the general ledger and the items used in the allocation process, like rules, methods, metrics, and so on. Creates, modifies, and deletes allocation lines, fiscal periods, and reports.
</documentation>
</element>
<element xsi:type="archimate:BusinessActor" id="11fcbaff" name="financial management user ">
<documentation>[financial_mgmt_user]
Views general ledger records and allocation records for reporting purposes.</documentation>
</element>
<element xsi:type="archimate:BusinessActor" id="5b4b7e02" name="financial analyst ">
<documentation>[financial_analyst]
Uses the workbench to allocate expenses. Modifies the cost model. Creates, edits, and deletes financial reports.</documentation>
</element>
<element xsi:type="archimate:BusinessActor" id="db5be646" name="data mart administrator ">
<documentation>[data_mart_admin]
Creates, modifies, and deletes records in the data mart. Creates dimension tables that can be used as a segment, so that financial management administrators and analysts can add the segments to the IT chart of accounts.</documentation>
</element>
<element xsi:type="archimate:BusinessActor" id="5fd49dc4" name="Budget Owner">
<documentation>Budget owners can view all items that budget keys are associated with, such as budget plans and forecasts.
Budget owners are users in the instance that you can associate with a budget plan. Create a budget owner record to give a user the budget_owner role, which grants access to budget plans and forecasts.</documentation>
</element>
<element xsi:type="archimate:BusinessActor" id="b6774223" name="Budget Key Owner">
<documentation>Budget key owners are also users in the instance that you can associated with a budget key, and thereby budget plans as well. Budget key ownership can be full or limited:
Full access allows the owner to access everything associated with the budget key, including budget plans and forecasts, targets, and budget key expenses.
Limited access allows the owner to see only the budget plans they own and the items in those plans.
Budget key owners also have the same level of access to the items associated with child budget keys.</documentation>
</element>
<element xsi:type="archimate:BusinessActor" id="2579f205" name="Budget Analyst"/>
<element xsi:type="archimate:BusinessActor" id="f1cea098" name="budget Admin"/>
<element xsi:type="archimate:BusinessActor" id="64186310" name="End User"/>
</folder>
<folder name="Application" id="cbb6025b" type="application">
<element xsi:type="archimate:DataObject" id="5054a846" name="Stages">
<documentation>{in_progress, canceled, paused, completed, breached}</documentation>
</element>
<element xsi:type="archimate:DataObject" id="f43a5a75" name="States">
<documentation>{open, assigned, in_progress, resolved, closed}</documentation>
</element>
<element xsi:type="archimate:ApplicationComponent" id="cff50ff1" name="SMAG Contract"/>
<element xsi:type="archimate:ApplicationComponent" id="124cd2f7" name="SMAG Snow App"/>
<element xsi:type="archimate:ApplicationComponent" id="395f4fae" name="Web Frontend"/>
<element xsi:type="archimate:ApplicationComponent" id="541a9e2b" name="API Frontend"/>
<element xsi:type="archimate:ApplicationFunction" id="f4d2edfb" name="Budgeting"/>
<element xsi:type="archimate:DataObject" id="b2d9e5d5" name="Usage Record"/>
<element xsi:type="archimate:ApplicationFunction" id="94d77be2" name="Accounting"/>
<element xsi:type="archimate:ApplicationFunction" id="ec94f979" name="Chargeback/Showback FC">
<documentation>7.4.8 Chargeback/Showback Functional Component
Purpose
• Provide chargeback or showback for internal and external services taking into account service Subscription and Usage information.
• Break down chargeback or showback based on charge types such as CapEx/OpEx, direct/indirect, fixed/variable, and labor/non-labor, as well as by consumer or consumer groups.
• Charge for IT services rendered based on the pricing model associated with the catalog item, this may also be implemented via showback (no actual billing or cross-charging), which helps the consumer become more IT cost-aware.
• Trace chargeback or showback line items to individual cost drivers based on the cost model.
• Consolidate IT service Subscription (right to use) and actual Usage as the usage may differ from the right to use.
The Chargeback/Showback functional component:
• Shall provide the price of consuming/subscribing to a service.
• Can take actual usage into consideration when calculating the price of consuming a service.
If an IT Financial Management component exists, the Chargeback/Showback functional component:
• Can provide the necessary information in order for the IT Financial Management supporting function to produce invoices or bills for services rendered.</documentation>
<property key="Purpose" value="Provide chargeback or showback for internal and external services taking into account service Subscription and Usage information. • Break down chargeback or showback based on charge types such as CapEx/OpEx, direct/indirect, fixed/variable, and labor/non-labor, as well as by consumer or consumer groups. • Charge for IT services rendered based on the pricing model associated with the catalog item, this may also be implemented via showback (no actual billing or cross-charging), which helps the consumer become more IT cost-aware. • Trace chargeback or showback line items to individual cost drivers based on the cost model. • Consolidate IT service Subscription (right to use) and actual Usage as the usage may differ from the right to use."/>
</element>
<element xsi:type="archimate:ApplicationComponent" id="824f83e3" name="ServiceNow"/>
<element xsi:type="archimate:ApplicationComponent" id="cefcbf8e" name="Users Controler"/>
<element xsi:type="archimate:ApplicationComponent" id="78ec8045" name="User Wallt"/>
<element xsi:type="archimate:ApplicationComponent" id="d6ba30ec" name="Groups Controler"/>
<element xsi:type="archimate:ApplicationComponent" id="cacbe3bd" name="Service Catalog"/>
<element xsi:type="archimate:ApplicationInterface" id="131ac6bb" name="Website"/>
<element xsi:type="archimate:ApplicationInterface" id="4c522f1a" name="API"/>
<element xsi:type="archimate:ApplicationService" id="617e2a37" name="Webservice"/>
<element xsi:type="archimate:ApplicationService" id="44a69c05" name="Web Frontend"/>
<element xsi:type="archimate:DataObject" id="09c78617" name="Task Record">
<property key="Purpose" value="foo"/>
</element>
<element xsi:type="archimate:DataObject" id="d7f9fe52" name="Wallet"/>
<element xsi:type="archimate:DataObject" id="1729b388" name="Budget"/>
<element xsi:type="archimate:DataObject" id="de1ffa53" name="Offer Record"/>
<element xsi:type="archimate:DataObject" id="1c11a754" name="Fulfillment Request"/>
<element xsi:type="archimate:DataObject" id="b735f926" name="Subscription"/>
<element xsi:type="archimate:DataObject" id="edee5551" name="Data Object"/>
<element xsi:type="archimate:ApplicationComponent" id="a3560c3b" name="Mist"/>
<element xsi:type="archimate:ApplicationInterface" id="6ad71be9" name="Web3 API"/>
<element xsi:type="archimate:ApplicationInterface" id="58889dce" name="RPC"/>
<element xsi:type="archimate:DataObject" id="215d2e14" name="Invoice"/>
<element xsi:type="archimate:DataObject" id="e715674f" name="Bill"/>
<element xsi:type="archimate:DataObject" id="8e91bfb7" name="Chargeback Contract">
<documentation>Details the financial obligations between the service consumer and provider(s). The Chargeback Contract typically defines the unit of measure (price) for a given service and is often tightly linked to Usage.
Key Attributes
The Chargeback Contract data object shall have the following key data attributes:
• ChargebackContractID: Unique identifier for the Service Contract.
• SubscriptionID: Link to the Subscription for which this Service Contract is instantiated (from Subscription).
Key Data Object Relationships
The Chargeback Contract data object shall maintain the following relationships:
• Chargeback Contract to Subscription (n:1): This relationship provides the traceability between the service rendered (represented by the Subscription) and the expected charges for those services (described in the Chargeback Contract).</documentation>
</element>
<element xsi:type="archimate:ApplicationComponent" id="ae8414d6" name="Pricing">
<documentation>•Shall provide the price of consuming/subscribing to a service</documentation>
</element>
<element xsi:type="archimate:ApplicationComponent" id="fa1d2739" name="Usage">
<documentation>Can take actual usage into consideration when calculating the price of consuming a service.</documentation>
</element>
<element xsi:type="archimate:ApplicationComponent" id="301749f7" name="Produce invoices"/>
<element xsi:type="archimate:ApplicationComponent" id="cc03ada9" name="Produce bills"/>
<element xsi:type="archimate:ApplicationFunction" id="fb5c1198" name="Check Balance"/>
<element xsi:type="archimate:ApplicationFunction" id="5ddd05ce" name="Fund Wallet"/>
<element xsi:type="archimate:ApplicationFunction" id="2e9b00db" name="Update Balance"/>
<element xsi:type="archimate:ApplicationFunction" id="01cf09cd" name="Calculate Task Deposit"/>
<element xsi:type="archimate:ApplicationFunction" id="62831510" name="Calculate Task Invoice"/>
<element xsi:type="archimate:ApplicationFunction" id="738b4602" name="Settle Task"/>
<element xsi:type="archimate:ApplicationFunction" id="9e25ae3e" name="Calculate Invoice"/>
<element xsi:type="archimate:ApplicationFunction" id="6dd1482b" name="Calculate Bill"/>
<element xsi:type="archimate:DataObject" id="d46341d1" name="Terms and Conditions"/>
<element xsi:type="archimate:ApplicationComponent" id="9d4a7175" name="RTGS system">
<documentation>A system where ensuing monetary obligations are settled</documentation>
</element>
<element xsi:type="archimate:DataObject" id="582f21cc" name="Accounting Rules"/>
<element xsi:type="archimate:DataObject" id="9f685f15" name="Service Definition"/>
<element xsi:type="archimate:ApplicationComponent" id="88abd8d8" name="Clearing system">
<documentation> a set of rules and procedures whereby financial institutions present and exchange data and/or documents relating to transfers of funds or securities to other fi nancial institutions at a single location (e.g. a clearing house). These procedures often include a mechanism for calculating participants’ mutual positions, potentially on a net basis, with a view to facilitating the settlement of their obligations in a settlement system.</documentation>
</element>
<element xsi:type="archimate:ApplicationComponent" id="135c224c" name="Deferred net settlement system">
<documentation>a system which settles on a net basis at the end of a predefi ned
settlement cycle (typically at the end of – but sometimes during – the business day).</documentation>
</element>
<element xsi:type="archimate:DataObject" id="ed1108ee" name="Users"/>
<element xsi:type="archimate:DataObject" id="019a1ec5" name="Service Level Definition"/>
<element xsi:type="archimate:DataObject" id="4035a755" name="Conflict Resolution Rules"/>
<element xsi:type="archimate:ApplicationComponent" id="05b27ce8" name="Ancillary system">
<documentation>a system in which payments or securities are exchanged and/or cleared. Meanwhile,
the ensuing monetary obligations are settled in another system, typically an RTGS system</documentation>
</element>
<element xsi:type="archimate:ApplicationComponent" id="49af0e79" name="Bilateral net settlement system">
<documentation>a settlement system in which every individual bilateral
combination of participants settles its net settlement position on a bilateral basis.</documentation>
</element>
<element xsi:type="archimate:DataObject" id="bdeccf8c" name="Indirect Cost Allocation Table ">
<documentation>A table used to allocate indirect costs that are shared among multiple services, defining the rules how those costs are spread among the services.
</documentation>
</element>
<element xsi:type="archimate:ApplicationFunction" id="07ae79b9" name="Get Price"/>
<element xsi:type="archimate:ApplicationFunction" id="f11ff7da" name="Calculate Estimate"/>
<element xsi:type="archimate:ApplicationComponent" id="35d517ed" name="Budeting"/>
<element xsi:type="archimate:ApplicationComponent" id="31f8173d" name="Accounting"/>
<element xsi:type="archimate:ApplicationComponent" id="5c4130f0" name="Charging"/>
<element xsi:type="archimate:ApplicationInteraction" id="6457f10b" name="Submit service request"/>
<element xsi:type="archimate:DataObject" id="6b214708" name="Offer"/>
<element xsi:type="archimate:DataObject" id="00434e51" name="Service Objectivs"/>
<element xsi:type="archimate:DataObject" id="2b40a4a3" name="IT Service Continuity Plan">
<documentation>is input for</documentation>
</element>
<element xsi:type="archimate:DataObject" id="eb57e440" name="Cost of Non-Availability">
<documentation>is input for</documentation>
</element>
<element xsi:type="archimate:DataObject" id="a4954124" name="Charging Models">
<documentation>is input for</documentation>
</element>
<element xsi:type="archimate:DataObject" id="bd4fa161" name="Strategic requirements for new services">
<documentation>is input for</documentation>
</element>
<element xsi:type="archimate:DataObject" id="009b5453" name="Availability Plan">
<documentation>is input for</documentation>
</element>
<element xsi:type="archimate:DataObject" id="dbceed9d" name="Business impact analysis">
<documentation>has as output</documentation>
</element>
<element xsi:type="archimate:DataObject" id="2b6ae0cf" name="Capacity Plan">
<documentation>is input for</documentation>
</element>
<element xsi:type="archimate:DataObject" id="4c5b6aef" name="Configuration Item">
<documentation>is input for</documentation>
</element>
<element xsi:type="archimate:DataObject" id="bfc71618" name="Value proposition">
<documentation>has as output</documentation>
</element>
<element xsi:type="archimate:DataObject" id="29ce3ad0" name="Service Provisioning Cost Assessment">
<documentation>has as output</documentation>
</element>
<element xsi:type="archimate:DataObject" id="9fd3311e" name="Charging Models">
<documentation>has as output</documentation>
</element>
<element xsi:type="archimate:DataObject" id="289a41b1" name="Policies">
<documentation>is input for</documentation>
</element>
<element xsi:type="archimate:DataObject" id="c48f720e" name="Cost Data">
<documentation>has as output</documentation>
</element>
<element xsi:type="archimate:DataObject" id="4cfe47bc" name="Reports on investment">
<documentation>is input for</documentation>
</element>
<element xsi:type="archimate:DataObject" id="73113041" name="CMDB">
<documentation>is input for</documentation>
</element>
<element xsi:type="archimate:DataObject" id="c9256c8f" name="Supplier Contract">
<documentation>is input for</documentation>
</element>
<element xsi:type="archimate:DataObject" id="1f50c6ca" name="Actual Patterns">
<documentation>is input for</documentation>
</element>
<element xsi:type="archimate:DataObject" id="ec2ac6e2" name="Core Service">
<documentation>is input for</documentation>
</element>
<element xsi:type="archimate:DataObject" id="b8c4974b" name="Service investment analysis">
<documentation>has as output</documentation>
</element>
<element xsi:type="archimate:DataObject" id="3c9960d2" name="Provisioning Value">
<documentation>has as output</documentation>
</element>
<element xsi:type="archimate:DataObject" id="ca83c9d7" name="SLA">
<documentation>is input for</documentation>
</element>
<element xsi:type="archimate:DataObject" id="aedf8973" name="Financial information">
<documentation>has as output</documentation>
</element>
<element xsi:type="archimate:DataObject" id="8e7a7dfd" name="IT Budget">
<documentation>has as output</documentation>
</element>
<element xsi:type="archimate:DataObject" id="a22c9d73" name="State Enum">
<documentation>{open, assigned, in_progress, resolved, closed}</documentation>
</element>
<element xsi:type="archimate:DataObject" id="5520fb6f" name="Stages (copy)">
<documentation>{in_progress, canceled, paused, completed, breached}</documentation>
</element>
<element xsi:type="archimate:ApplicationComponent" id="48f5ef2e" name="Enterprise Architecture Component"/>
<element xsi:type="archimate:DataObject" id="774b264f" name="Service Architecture"/>
<element xsi:type="archimate:ApplicationComponent" id="69d8ac53" name="Policy Component"/>
<element xsi:type="archimate:DataObject" id="d7389082" name="Policy"/>
<element xsi:type="archimate:ApplicationComponent" id="3de0d198" name="Portfolio Demand Component"/>
<element xsi:type="archimate:DataObject" id="b62c4a15" name="Portfolio Backlog Item"/>
<element xsi:type="archimate:ApplicationComponent" id="67073bff" name="Service Portfolio Component"/>
<element xsi:type="archimate:DataObject" id="d5cebb36" name="Conceptual Service"/>
<element xsi:type="archimate:DataObject" id="8ec6c4fe" name="Conceptual Service Blueprint"/>
<element xsi:type="archimate:ApplicationComponent" id="ef45dc57" name="Proposal Component"/>
<element xsi:type="archimate:DataObject" id="8d0b110d" name="Scope Agreement"/>
<element xsi:type="archimate:ApplicationComponent" id="536e1f4c" name="Requirement Component"/>
<element xsi:type="archimate:DataObject" id="3b6e16bd" name="Requirement"/>
<element xsi:type="archimate:ApplicationComponent" id="b628317f" name="Project Component"/>
<element xsi:type="archimate:DataObject" id="a1a68f70" name="IT Initiative"/>
<element xsi:type="archimate:ApplicationComponent" id="094764ca" name="Service Design Component"/>
<element xsi:type="archimate:DataObject" id="f0ade417" name="Logical Service Blueprint"/>
<element xsi:type="archimate:DataObject" id="3df53fec" name="Conceptual Service Blueprint (copy)"/>
<element xsi:type="archimate:ApplicationComponent" id="db2a76f8" name="Source Control Component"/>
<element xsi:type="archimate:DataObject" id="04325b5e" name="Source"/>
<element xsi:type="archimate:ApplicationComponent" id="fecea935" name="Defect Component"/>
<element xsi:type="archimate:DataObject" id="584b481e" name="Defect"/>
<element xsi:type="archimate:ApplicationComponent" id="29cbfa7d" name="Test Component"/>
<element xsi:type="archimate:DataObject" id="f0a1ff47" name="Test Case"/>
<element xsi:type="archimate:ApplicationComponent" id="e47a834f" name="Build Package Component"/>
<element xsi:type="archimate:DataObject" id="36ba6435" name="Build Package"/>
<element xsi:type="archimate:ApplicationComponent" id="8486c686" name="Release Composition Component"/>
<element xsi:type="archimate:DataObject" id="7a5d912f" name="Service Release"/>
<element xsi:type="archimate:DataObject" id="00ad60f6" name="Service Release Blueprint"/>
<element xsi:type="archimate:ApplicationComponent" id="6bee1d97" name="Build Component"/>
<element xsi:type="archimate:DataObject" id="b48ff17c" name="Build"/>
<element xsi:type="archimate:ApplicationComponent" id="805af5a7" name="Catalog Component"/>
<element xsi:type="archimate:DataObject" id="50e7b1b3" name="Service Catalog Entry"/>
<element xsi:type="archimate:DataObject" id="268a8d02" name="Conceptual Service (copy) (copy)"/>
<element xsi:type="archimate:DataObject" id="66692bd5" name="Conceptual Service Blueprint (copy) (copy)"/>
<element xsi:type="archimate:ApplicationComponent" id="abecccdc" name="Offer Management Component"/>
<element xsi:type="archimate:DataObject" id="9dc6687a" name="Offer"/>
<element xsi:type="archimate:ApplicationComponent" id="c22960df" name="Offer Consumption Component"/>
<element xsi:type="archimate:DataObject" id="6ea49a80" name="Shopping Cart"/>
<element xsi:type="archimate:ApplicationComponent" id="841a3f9a" name="Fulfillment Execution Component"/>
<element xsi:type="archimate:DataObject" id="6f3744ec" name="Conceptual Service (copy) (copy)"/>
<element xsi:type="archimate:DataObject" id="4cc09c58" name="Demand Service Model"/>
<element xsi:type="archimate:ApplicationComponent" id="cf7f98aa" name="Proposal Component (copy) (copy)"/>
<element xsi:type="archimate:DataObject" id="d8b2e420" name="Request"/>
<element xsi:type="archimate:ApplicationComponent" id="1673d18b" name="Usage Component"/>
<element xsi:type="archimate:DataObject" id="66060a84" name="Usage Record"/>
<element xsi:type="archimate:DataObject" id="0ae1946f" name="Conceptual Service (copy) (copy) (copy)"/>
<element xsi:type="archimate:DataObject" id="a1b84356" name="Conceptual Service Blueprint (copy) (copy) (copy)"/>
<element xsi:type="archimate:ApplicationComponent" id="2415d3e9" name="Chargeback/Showback Component"/>
<element xsi:type="archimate:DataObject" id="866ccd80" name="Chargeback Contract"/>
<element xsi:type="archimate:ApplicationComponent" id="76f3865c" name="Problem Component"/>
<element xsi:type="archimate:DataObject" id="ce789cdc" name="Problem / Known Error"/>
<element xsi:type="archimate:ApplicationComponent" id="d059a127" name="Diagnostics & Remediation Component"/>
<element xsi:type="archimate:DataObject" id="85cf0376" name="Run Book"/>
<element xsi:type="archimate:ApplicationComponent" id="dc8d2819" name="Change Control Component"/>
<element xsi:type="archimate:DataObject" id="0a6a0b90" name="Conceptual Service (copy) (copy)"/>
<element xsi:type="archimate:DataObject" id="d3821e5e" name="Conceptual Service Blueprint (copy) (copy)"/>
<element xsi:type="archimate:ApplicationComponent" id="ad22e314" name="Service Level Component"/>
<element xsi:type="archimate:DataObject" id="336d6aeb" name="Service Contract"/>
<element xsi:type="archimate:ApplicationComponent" id="8346990c" name="Enterprise Architecture Component (copy) (copy)"/>
<element xsi:type="archimate:DataObject" id="3c9b4b57" name="Service Architecture (copy) (copy)"/>
<element xsi:type="archimate:ApplicationComponent" id="8ee07bd0" name="Incident Component"/>
<element xsi:type="archimate:DataObject" id="713fd26d" name="Incident"/>
<element xsi:type="archimate:ApplicationComponent" id="e65b3302" name="Service Monitoring Component"/>
<element xsi:type="archimate:DataObject" id="1eb426ff" name="Service Monitor"/>
<element xsi:type="archimate:ApplicationComponent" id="296fe9d8" name="Configuration Management Component"/>
<element xsi:type="archimate:DataObject" id="f4ef71df" name="Actual Service CIs"/>
<element xsi:type="archimate:DataObject" id="6dc280a9" name="Conceptual Service Blueprint (copy) (copy)"/>
<element xsi:type="archimate:ApplicationComponent" id="036937f2" name="Event Component"/>
<element xsi:type="archimate:DataObject" id="6620abeb" name="Event"/>
<element xsi:type="archimate:DataObject" id="afec3d5b" name="Fulfillment Request"/>
<element xsi:type="archimate:DataObject" id="ff08f776" name="RFC"/>
<element xsi:type="archimate:DataObject" id="13c942ac" name="Subscription"/>
<element xsi:type="archimate:DataObject" id="94b3d383" name="User"/>
<element xsi:type="archimate:DataObject" id="f3f6afdc" name="Group"/>
<element xsi:type="archimate:DataObject" id="e3ffda44" name="User (copy)"/>
<element xsi:type="archimate:ApplicationComponent" id="18a3770b" name="Roles module"/>
<element xsi:type="archimate:DataObject" id="94980924" name="Roles"/>
<element xsi:type="archimate:ApplicationInterface" id="16225a24" name="Users View"/>
<element xsi:type="archimate:ApplicationInterface" id="fa3a957c" name="Groups View"/>
<element xsi:type="archimate:ApplicationComponent" id="d8347408" name="Departments Controler"/>
<element xsi:type="archimate:DataObject" id="69e7077c" name="Department"/>
<element xsi:type="archimate:ApplicationInterface" id="39e734f7" name="Departments View"/>
<element xsi:type="archimate:ApplicationComponent" id="844f859d" name="Wallet view"/>
<element xsi:type="archimate:ApplicationComponent" id="13c433b9" name="SMAG SN App"/>
<element xsi:type="archimate:DataObject" id="0565c1b3" name="Wallet"/>
<element xsi:type="archimate:ApplicationInterface" id="1faa96f6" name="View Wallet Balance"/>
<element xsi:type="archimate:ApplicationService" id="3a4c19d5" name="Fund Wallet Balance"/>
<element xsi:type="archimate:ApplicationInteraction" id="1a956123" name="Fund User Wallet"/>
<element xsi:type="archimate:ApplicationFunction" id="112e6f81" name="Mange User Wallet"/>
<element xsi:type="archimate:ApplicationFunction" id="7c0f0879" name="Pay Deposit for request"/>
<element xsi:type="archimate:ApplicationFunction" id="6a32a270" name="Pay for Request"/>
<element xsi:type="archimate:ApplicationService" id="5fd67cef" name="Calculate Depoist"/>
<element xsi:type="archimate:ApplicationService" id="20223a7d" name="Pay Invoice"/>
<element xsi:type="archimate:ApplicationService" id="02b8e817" name="Pay Deposit"/>
<element xsi:type="archimate:ApplicationService" id="3a15c1ff" name="Calculate Invoice"/>
<element xsi:type="archimate:ApplicationComponent" id="16591c95" name="IT Finance ">
<documentation>http://wiki.servicenow.com/index.php?title=IT_Finance#gsc.tab=0
ServiceNow Financial Management applications</documentation>
</element>
<element xsi:type="archimate:ApplicationComponent" id="69e3c2aa" name="General ledger">
<documentation>List of IT organization's expenses
</documentation>
</element>
<element xsi:type="archimate:ApplicationComponent" id="7b4ed766" name="Fiscal period">
<documentation>Timeframe during which expenses were incurred. You can work with only one fiscal period at a time.</documentation>
</element>
<element xsi:type="archimate:ApplicationComponent" id="063ebff5" name="Cost model">
<documentation>Rules, methods, and metrics that tell the application how to allocate expenses to the accounts in the IT chart of accounts.
The allocation engine: the core of the application that uses your cost model to calculate expenses and determine how to allocate expenses.
Financial reports and dashboards: graphical representations of the expense allocations that show you where your expenses are coming from.
With the workbench, you can manage your general ledger, choose the fiscal period, build your cost model, and run the allocation engin</documentation>
</element>
<element xsi:type="archimate:ApplicationComponent" id="e5af84de" name="Allocation engine">
<documentation>Core of the application that uses your cost model to calculate expenses and determine how to allocate expenses.
Financial reports and dashboards: graphical representations of the expense allocations that show you where your expenses are coming from.
With the workbench, you can manage your general ledger, choose the fiscal period, build your cost model, and run the allocation engin</documentation>
</element>
<element xsi:type="archimate:ApplicationComponent" id="67f9c412" name="Workbench">
<documentation>With the workbench, you can manage your general ledger, choose the fiscal period, build your cost model, and run the allocation engin</documentation>
</element>
<element xsi:type="archimate:ApplicationComponent" id="4cf9f901" name="Financial reports and dashboards">
<documentation>Graphical representations of the expense allocations that show you where your expenses are coming from.
</documentation>
</element>
<element xsi:type="archimate:ApplicationComponent" id="cf2caad0" name="SNITFM_Allocation Groups">
<documentation>Access the groups you can use to classify allocations.</documentation>
</element>
<element xsi:type="archimate:ApplicationComponent" id="cce766e3" name="SNITFM_Segment Hierarchy">
<documentation>Access the records that control the hierarchy of segments in the IT chart of accounts.</documentation>
</element>
<element xsi:type="archimate:ApplicationComponent" id="b6488368" name="SNITFM_CIO Dashboard">
<documentation>View a report that gives CIOs a quick summary of finances operations, and projects.</documentation>
</element>
<element xsi:type="archimate:ApplicationComponent" id="3a7d15a3" name="SNITFM_Financial Overview">
<documentation>View reports that show costs per fiscal period for each segment in the IT chart of accounts.</documentation>
</element>
<element xsi:type="archimate:ApplicationComponent" id="e168ff94" name="SNITFM_General Ledger">
<documentation>General Ledger</documentation>
</element>
<element xsi:type="archimate:ApplicationComponent" id="9c383c2e" name="SNITFM_Dashboards">
<documentation>Dashboards</documentation>
</element>
<element xsi:type="archimate:ApplicationComponent" id="424175f5" name="SNITFM_Account Overview">
<documentation>View reports that show allocations for the accounts in all segments.</documentation>
</element>
<element xsi:type="archimate:ApplicationComponent" id="09551af0" name="SNITFM_Allocation Methods">
<documentation>Access the methods that cost allocation rules use to allocate expenses.</documentation>
</element>
<element xsi:type="archimate:ApplicationComponent" id="4ce031f2" name="SNITFM_Create Weighted Metric">
<documentation>Create a new weighted metric.</documentation>
</element>
<element xsi:type="archimate:ApplicationComponent" id="b27f573e" name="SNITFM_Allocation Rules">
<documentation>Access all cost allocation rules used to allocate expenses.</documentation>
</element>
<element xsi:type="archimate:ApplicationComponent" id="15e4788f" name="SNITFM_Staged Expenses">
<documentation>Access the list of the expenses that you imported into the application.</documentation>
</element>
<element xsi:type="archimate:ApplicationComponent" id="52dc7820" name="SNITFM_Groomed Expenses">
<documentation>Access the expenses that are already groomed, assigned to buckets, and ready for allocation.</documentation>
</element>
<element xsi:type="archimate:ApplicationComponent" id="5e63ca6d" name="SNITFM_Allocation Lines">
<documentation>Access the expense lines that have been allocated from expenses in the general ledger.</documentation>
</element>
<element xsi:type="archimate:ApplicationComponent" id="ade43f6d" name="SNITFM_Business Service Overview">
<documentation>View reports that show allocations for business services.</documentation>
</element>
<element xsi:type="archimate:ApplicationComponent" id="cf6d7043" name="SNITFM_Cost Model">
<documentation>Cost Model</documentation>
</element>
<element xsi:type="archimate:ApplicationComponent" id="803d0eb7" name="SNITFM_IT Chart of Accounts">
<documentation>Access the definitions that specify the segments used by your cost allocation method.</documentation>
</element>
<element xsi:type="archimate:ApplicationComponent" id="35447e38" name="SNITFM_Dimensions">
<documentation>Opens a list of dimension table definitions.</documentation>
</element>
<element xsi:type="archimate:ApplicationComponent" id="a8dbf897" name="SNITFM_Business Units">
<documentation>Access the business units that are associated with companies. By default, the business unit is the first segment in the IT chart of accounts.</documentation>
</element>
<element xsi:type="archimate:ApplicationComponent" id="710b2f6f" name="SNITFM_Account Buckets">
<documentation>Access the buckets that you can use in the workbench to group expenses.</documentation>
</element>
<element xsi:type="archimate:ApplicationComponent" id="f0af6413" name="SNITFM_Facts">
<documentation>Opens a list of fact definitions.</documentation>
</element>
<element xsi:type="archimate:ApplicationComponent" id="9dd6db62" name="SNITFM_Last Run">
<documentation>Opens the records showing the most recent time that the application created dimension tables.</documentation>
</element>
<element xsi:type="archimate:ApplicationComponent" id="d6e0400c" name="SNITFM_Business Unit Overview">
<documentation>View reports that show allocations for business units.</documentation>
</element>
<element xsi:type="archimate:ApplicationComponent" id="f173eacf" name="SNITFM_IT Shared Services">
<documentation>Access the services that are shared across your IT infrastructure.</documentation>
</element>
<element xsi:type="archimate:ApplicationComponent" id="92114cc2" name="SNITFM_Trending Dashboard">
<documentation>View reports that shows allocation data for each segment over time.</documentation>
</element>
<element xsi:type="archimate:ApplicationComponent" id="286cc505" name="SNITFM_Grooming Conditions">
<documentation>Access advanced query conditions that the workbench uses during the Bucketing stage.</documentation>
</element>
<element xsi:type="archimate:ApplicationComponent" id="c87f1654" name="SNITFM_Chart of Accounts">
<documentation>Chart of Accounts</documentation>
</element>
<element xsi:type="archimate:ApplicationComponent" id="c2102767" name="SNITFM_Overviews">
<documentation>Overviews</documentation>
</element>
<element xsi:type="archimate:ApplicationComponent" id="a46b9359" name="SNITFM_IT Data Mart">
<documentation>IT Data Mart</documentation>
</element>
<element xsi:type="archimate:ApplicationComponent" id="1f515b0c" name="SNITFM_Cleansed Expenses">
<documentation>Access the expenses that you already cleansed in the workbench.</documentation>
</element>
<element xsi:type="archimate:ApplicationComponent" id="12fea0c9" name="SNITFM_Allocation Metrics">
<documentation>Access the metrics that rules and methods use to allocate expenses.</documentation>
</element>
<element xsi:type="archimate:ApplicationComponent" id="c636be02" name="SNITFM_Filter Conditions">
<documentation>Access records that allocations rules use to filter the expenses that can match allocation rules.</documentation>
</element>
<element xsi:type="archimate:ApplicationComponent" id="b7876f5a" name="SNITFM_Financial Dashboard">
<documentation>View the main financial management dashboard that shows allocations for selected segments.</documentation>
</element>
<element xsi:type="archimate:ApplicationComponent" id="19d5477f" name="SNITFM_Workbench">
<documentation>Open the workbench, which is a user-friendly interface that you can use to manage expense data in the general ledger, set up the cost model, and perform allocations.</documentation>
</element>
<element xsi:type="archimate:ApplicationComponent" id="4912b0bb" name="SNITFM_Getting Started">
<documentation>Access the documentation to help you get started with the application.</documentation>
</element>
<element xsi:type="archimate:ApplicationComponent" id="f88e04bc" name="SNITFM_Cost"/>
<element xsi:type="archimate:DataObject" id="7a8a1218" name="SNITFM_Budget Segment Map [itfm_budget_segment_map]">
<documentation>A relationship between segments that budgets use and a budget key.</documentation>
</element>
<element xsi:type="archimate:DataObject" id="9d550ef9" name="SNITFM_Cost Allocation Aggregate [itfm_allocation_aggregate]">
<documentation>A more brief set of allocation line data than is saved in the Cost Allocation [itfm_allocation] table.</documentation>
</element>
<element xsi:type="archimate:DataObject" id="968c8f2a" name="SNITFM_Bucket [itfm_bucket]">
<documentation>Buckets used in the allocation workbench to group similar expenses.</documentation>
</element>
<element xsi:type="archimate:DataObject" id="ab8a2401" name="SNITFM_Budget Asset Depreciation [itfm_bi_asset]">
<documentation>Budget items of type Asset Depreciation.</documentation>
</element>
<element xsi:type="archimate:DataObject" id="d46547d7" name="SNITFM_Budget Forecast [itfm_budget_forecast]">
<documentation>All budget forecasts.</documentation>
</element>
<element xsi:type="archimate:DataObject" id="765b434b" name="SNITFM_ITFM Session [itfm_session]">
<documentation>Saves session information for the workbench.</documentation>
</element>
<element xsi:type="archimate:DataObject" id="cc7f4f71" name="SNITFM_Budget Hardware [itfm_bi_hardware]">
<documentation>Budget items of type Hardware.</documentation>
</element>
<element xsi:type="archimate:DataObject" id="036e3783" name="SNITFM_Cost Allocation Rollup [itfm_rollup]">
<documentation>Rollups that the application creates when you use the workbench.</documentation>
</element>
<element xsi:type="archimate:DataObject" id="6b2d30ee" name="SNITFM_Cleansing Condition [itfm_cleansing_condition]">
<documentation>Conditions that the application automatically generates when you clean data in the workbench.</documentation>
</element>
<element xsi:type="archimate:DataObject" id="15e1af1c" name="SNITFM_Segment Relationship [itfm_itcoa_hierarchy]">
<documentation>Relationships between segments in the segment hierarchy as defined in the Data Definition stage of the workbench. Also captures the segment hierarchy for budget models.</documentation>
</element>
<element xsi:type="archimate:DataObject" id="743c0507" name="SNITFM_FM Report [itfm_report]">
<documentation>Finance reports.</documentation>
</element>
<element xsi:type="archimate:DataObject" id="75809356" name="SNITFM_Segment Definition [itfmCasegment_map]"/>
<element xsi:type="archimate:DataObject" id="790b653c" name="SNITFM_Budget Owner [itfm_budget_owner]">
<documentation>Owners of budgets.</documentation>
</element>
<element xsi:type="archimate:DataObject" id="8676a43a" name="SNITFM_Financial Data Source [itfm_data_source]">
<documentation>The source of the financial data: the staged general ledger or the cost plan breakdown.</documentation>
</element>
<element xsi:type="archimate:DataObject" id="ff0b92fc" name="SNITFM_General Ledger Log [itfm_gl_log]">
<documentation>Log records that are created when expenses are added to the general ledger for a fiscal period.</documentation>
</element>
<element xsi:type="archimate:DataObject" id="aea03ca7" name="SNITFM_Budget Item Breakdown [itfm_bi_breakdown]">
<documentation>Breakdowns of budget costs for a given budget item.</documentation>
</element>
<element xsi:type="archimate:DataObject" id="d465181d" name="SNITFM_Cost Allocation [itfm_allocation]">
<documentation>All allocation lines that are processed from allocations. This table holds a more detailed level of allocation lines as compared to the Cost Allocation Aggregate table.</documentation>
</element>
<element xsi:type="archimate:DataObject" id="cf500950" name="SNITFM_Budget Forecast Items [itfm_bf_item]">
<documentation>All items on the budget forecast.</documentation>
</element>
<element xsi:type="archimate:DataObject" id="90aab051" name="SNITFM_Budget Item [itfm_budget_item]">
<documentation>All budget items.</documentation>
</element>
<element xsi:type="archimate:DataObject" id="e8ddcb09" name="SNITFM_Budget Contract [itfm_bi_contract]">
<documentation>Budget items of type Contract.</documentation>
</element>
<element xsi:type="archimate:DataObject" id="f0c65aca" name="SNITFM_Bucket Allocation Rule [itfm_bucket_allocation_rule]">
<documentation>Allocates expenses to buckets.</documentation>
</element>
<element xsi:type="archimate:DataObject" id="e6254461" name="SNITFM_Budget Plan [itfm_budget_plan]">
<documentation>Budget plans specify expenses for assets, contracts, labor, and certain configuration items (CIs) for a fiscal period, particularly one in the future. Use budget plans as the basis to compare your actual versus planned expenses.
Budget plans are associated with a budget key and a fiscal period. If you have financial data over several financial periods, make a separate plan for each period.
There are several types of items you can add to the budget plan. The costs of these items are broken down over the fiscal period that you specify for the plan. See Budget items and Budget item breakdowns for more information.
Budget plan expense amount types
Budget plans show these types of expense amounts:
Target amounts: An amount that you set as a goal to reach or a limit not to exceed. A target amount is created for a specific fiscal period and account code combination. When you select the account code and fiscal period for the budget plan, the target amount is automatically populated in the read-only target fields. There are targets for both operating and capital expenses.
Budgeted amounts: A rollup of all the budget plan items, which appear as related lists on the Budget Plan form. Only items marked as capital expenses do not roll up to the amount fields. There are budgeted amounts for both operating and capital expenses.
Budget plan ownership
Budget plans have a single owner, who must have the budget_owner role. Whoever you chose as the budget owner must also be associated with the budget plan's budget key as an owner.
Budget plan parent-child relationships
Budget plans can have one or more sub-plans, which roll up their actual budget amounts to the parent budget plan. You cannot promote child plans individually. Only the top-level plan in a hierarchy can be promoted.