WEBVTT Kind: captions; Language: en

1
00:00:00.000 --> 00:00:04.080
Well so is the subject of the booths method

2
00:00:04.250 --> 00:00:09.770
once again an acronym that really is a chronic mind console in sectivispoinphons

3
00:00:09.770 --> 00:00:13.190
starving rootsilize groupsiis booths is therefore

4
00:00:13.190 --> 00:00:17.750
method of ite management ite management

5
00:00:17.750 --> 00:00:22.820
consists of a frame of reference that structures this most

6
00:00:22.820 --> 00:00:27.800
to deal with the process descriptions of the organizational entity

7
00:00:27.800 --> 00:00:32.210
with which the sprout according to the kopit is managed and controlled in this way

8
00:00:32.210 --> 00:00:37.250
the control perspectives mentioned in the name which are in practice

9
00:00:37.250 --> 00:00:42.350
requirements for process control as to how processes are monitored

10
00:00:42.350 --> 00:00:46.970
I bind management practices, that is, what kind

11
00:00:46.970 --> 00:00:51.320
the ways in which this entity is managed are managed

12
00:00:51.320 --> 00:00:56.250
and I tie maturity levels to maturity somalis

13
00:00:56.250 --> 00:01:01.290
the management of the organization’s crystal and its functionality and effectiveness

14
00:01:01.290 --> 00:01:05.250
can be evaluated and further developed

15
00:01:05.250 --> 00:01:12.750
the current version of the vitonen kitilintapo practice is this kind of book series

16
00:01:12.750 --> 00:01:18.510
you would have written bisnes footin naren mänisnentofintepäisaitii

17
00:01:18.510 --> 00:01:23.280
which is the rapporteur's overall frame sit is thicker

18
00:01:23.280 --> 00:01:28.800
with his work Rousi thus where there are processes with which

19
00:01:28.800 --> 00:01:33.900
with which the operation is rotated on the implementation of the seven eight pages

20
00:01:33.900 --> 00:01:39.150
book and then a thick thick book again associated with toho

21
00:01:39.150 --> 00:01:44.520
information security management and management booths

22
00:01:44.520 --> 00:01:49.750
words like itille are complementary as a frame of reference

23
00:01:49.750 --> 00:01:54.850
This addresses the same themes as, for example, ITE risk management and both offerings

24
00:01:54.850 --> 00:01:59.740
a reference related to or guiding the implementation of these activities

25
00:01:59.740 --> 00:02:04.690
process models, i.e. these recommended best practices where

26
00:02:04.690 --> 00:02:09.880
focus only on ite functions and especially on the provision of ite services

27
00:02:09.880 --> 00:02:15.430
very looks at things from a slightly broader formula from an organization--wide perspective

28
00:02:15.430 --> 00:02:20.320
by sector from there to stakeholder and business goals

29
00:02:20.320 --> 00:02:25.300
and in addition to booth support for sperm audit evaluation

30
00:02:25.300 --> 00:02:29.750
where itil itself for example supply tools

31
00:02:29.750 --> 00:02:36.230
both the booths and the itel have frames of reference which means that their use will be agreed upon

32
00:02:36.230 --> 00:02:41.720
the organization’s needs for operating models, i.e., they were not oo intended for use as such

33
00:02:41.720 --> 00:02:47.250
nor do they in themselves provide tools or models of business that

34
00:02:47.250 --> 00:02:53.100
it would even be possible to put it into practice without adapting those practices

35
00:02:53.100 --> 00:02:58.020
The main difference if you compare your booths is that of booths

36
00:02:58.020 --> 00:03:03.360
describes what to do and then rather that how these things work

37
00:03:03.360 --> 00:03:08.850
should be done if overall architecture overall architecture management is desired

38
00:03:08.850 --> 00:03:14.100
puts out the overall architecture of a series of such question words

39
00:03:14.100 --> 00:03:19.200
could describe where this is done and how it is done

40
00:03:19.200 --> 00:03:24.750
kopit coverage seen during this period

41
00:03:24.750 --> 00:03:30.240
relative to some other known standards i.e. there are more

42
00:03:30.240 --> 00:03:36.480
the big standard was the longing for infonical security and tone of mind

43
00:03:36.480 --> 00:03:41.250
sit there is it and mummies the maturity of the collection

44
00:03:41.250 --> 00:03:46.710
prince machine and beatbox or project management best practices

45
00:03:46.710 --> 00:03:52.000
and then toka to manage the overall architecture

46
00:03:52.000 --> 00:03:56.620
more well reflects the fact that the booths are so wide quite

47
00:03:56.620 --> 00:04:01.060
an all--encompassing frame of reference that can then be put into practice

48
00:04:01.060 --> 00:04:05.500
based on several other standards

49
00:04:05.500 --> 00:04:10.810
here the lecture is now to see how hard and itili work together i.e.

50
00:04:10.810 --> 00:04:16.210
Booths thus provide an overall model of the operation of an organization

51
00:04:16.210 --> 00:04:21.000
information and the technologies that support it are managed

52
00:04:21.000 --> 00:04:26.220
it introduces a large number of processes and practices and all

53
00:04:26.220 --> 00:04:31.560
processes with practices as well as feed what went into the processes and the outputs

54
00:04:31.560 --> 00:04:37.080
What they come out of is the unique identifiers and interfaces of different processes

55
00:04:37.080 --> 00:04:42.060
between is clearly defined one copit core

56
00:04:42.060 --> 00:04:47.250
The guiding idea is what English is called a schoolmaster

57
00:04:47.250 --> 00:04:48.780
is this

58
00:04:49.000 --> 00:04:54.040
business needs of the company's stakeholders needs them first

59
00:04:54.040 --> 00:04:59.560
are linked to the goals of the organization's activities, which continue to be the goals of Hiite

60
00:04:59.560 --> 00:05:04,000
and then finally as enabling goals

61
00:05:044.000 --> 00:05:08.500
that is, in practice, the kopit uses hiite goals

62
00:05:08.500 --> 00:05:12.500
linked to the organization’s core business objectives

63
00:05:12.500 --> 00:05:17.990
here is the general level of this cobit frame of reference

64
00:05:17.990 --> 00:05:22.220
and key areas of governance and management, i.e.

65
00:05:22.220 --> 00:05:27.860
there is a top management function that directs and monitors the use of the line

66
00:05:27.860 --> 00:05:32.000
it becomes a feeder of business need

67
00:05:32.000 --> 00:05:39.500
sit is the level of manure that produces, develops and maintains ideas and its services

68
00:05:39.500 --> 00:05:44.690
at the level of samism, the course of development is quite familiar

69
00:05:44.690 --> 00:05:49.700
planned to be built, driven or implemented

70
00:05:49.700 --> 00:05:54.530
and that activity is monitored by monitoring the monitoring brings

71
00:05:54.530 --> 00:05:59.540
while cheering up tons of cavannas to level thus monitoring data

72
00:05:59.540 --> 00:06:04.750
which is assessed and on the basis of these assessments

73
00:06:04.750 --> 00:06:10.000
the price is re--developed and controlled from which we then return again

74
00:06:10.000 --> 00:06:14.980
tons of production development and maintenance design

75
00:06:14.980 --> 00:06:20.020
to construction and so away, that is, to rotate I rotate in such a perimeter

76
00:06:20.020 --> 00:06:25.270
where it activities iten management management

77
00:06:25.270 --> 00:06:29.920
development and thus practical implementation revolved around

78
00:06:29.920 --> 00:06:35,000
produce evaluation data that can be used to develop it

79
00:06:35.000 --> 00:06:38.570
here are the booths of vitosen

80
00:06:38.750 --> 00:06:44.000
processes divided into those previous slides shown in the part area

81
00:06:44.000 --> 00:06:49.730
last night's top assessment guidance and monitoring

82
00:06:49.730 --> 00:06:54.530
the five related processes sit on this auxiliary layer of Alain

83
00:06:54.530 --> 00:06:59.360
head ongenais design action then

84
00:06:59.360 --> 00:07:04.580
bilty sinks implementeli construction acquisition putting into production

85
00:07:04.580 --> 00:07:09.770
and if the level of brochure is that service production service support

86
00:07:09.770 --> 00:07:15.560
Bill's culprit supooot and then there's monitoring on the side

87
00:07:15.560 --> 00:07:19.880
evaluation of the functions of the related processes; and

88
00:07:19.880 --> 00:07:25.610
indeed, that little one shows that in each of its processes the tags are acidified

89
00:07:25.610 --> 00:07:30.410
two beaa iii zero one weahainolla two

90
00:07:30.410 --> 00:07:35.510
in the case of zero one and so on then disappear by way of example that

91
00:07:35.510 --> 00:07:40.970
process zero two, that is, service requests

92
00:07:40.970 --> 00:07:45.980
incident disturbance management process which also

93
00:07:45.980 --> 00:07:50.900
then that itille video deals with this process

94
00:07:50.900 --> 00:07:55.790
seven sets of tasks for example

95
00:07:55.790 --> 00:08:01.000
incident registration classification prioritization

96
00:08:01.000 --> 00:08:05.590
disorder investigation diagnosis location

97
00:08:05.750 --> 00:08:10.910
incident solution incident closure and thus

98
00:08:10.910 --> 00:08:16.250
whole sight monitoring monitoring

99
00:08:16.250 --> 00:08:23.750
whether these tasks could be properly structured as process costs

100
00:08:23.750 --> 00:08:29.300
or alternatively itil equivalent may be applied

101
00:08:29.300 --> 00:08:34.750
process to itilin thus an insidenmänizment session

102
00:08:34.750 --> 00:08:38.320
or internal sign this was gone through

103
00:08:38.500 --> 00:08:44.290
let’s now take those into this incident management

104
00:08:44.290 --> 00:08:50,000
practices which would be one in seven

105
00:08:50.000 --> 00:08:55.880
practical second which is hence the incident recording classification

106
00:08:55.880 --> 00:09:01.400
and prioritization booths defines all tasks for all processes

107
00:09:01.400 --> 00:09:06.500
racial roles or risponsipolo

108
00:09:06.500 --> 00:09:11.420
the housing fire left me in the foo i.e. who is

109
00:09:11.420 --> 00:09:16.280
the executor of the task is none of its responsible owners

110
00:09:16.280 --> 00:09:21.110
in connection with the task must be consulted and who in connection with the task

111
00:09:21.110 --> 00:09:25.500
must inform this is defined that

112
00:09:25.500 --> 00:09:29.910
this is the responsibility of the self--service director and the task owner

113
00:09:29.910 --> 00:09:34.000
is then ite operations manager

114
00:09:34.000 --> 00:09:39.220
incident tickets go into this process as feeds

115
00:09:39.220 --> 00:09:43.390
disruption notifications service level agreements that it

116
00:09:43.390 --> 00:09:48.130
associated with and then such an emergency escalation policy

117
00:09:48.130 --> 00:09:52.500
escalon is talked about in it on video

118
00:09:52.500 --> 00:09:59.220
from process deessäs zero yx I so it is the management of family benefits services comes

119
00:09:59.220 --> 00:10:04,000
input this disorder ticket

120
00:10:04.000 --> 00:10:10.060
another area from the process of pine--eating grim, i.e., service contracts

121
00:10:10.060 --> 00:10:15.500
the management process becomes the necessary service level agreements

122
00:10:15.500 --> 00:10:19.760
and then availability and capacity management

123
00:10:19.760 --> 00:10:24.740
the process, with its inputs, becomes an emergency if necessary

124
00:10:24.740 --> 00:10:28.500
escalation goes here

125
00:10:28.500 --> 00:10:34.020
the second task, ie recording incidents, prioritizing classifications

126
00:10:34.020 --> 00:10:37.980
involves six more specific sub--levels

127
00:10:37.980 --> 00:10:43.590
task logging of game service requests and and fault notifications

128
00:10:43.590 --> 00:10:47.500
maintenance of these records

129
00:10:47.500 --> 00:10:52.600
doing analytics for trend analyzes created from them

130
00:10:52.600 --> 00:10:57.430
and thus prioritizing interference in relation to what is promised

131
00:10:57.430 --> 00:11:02.410
service level and then their estimated business impact

132
00:11:02.410 --> 00:11:06.700
that is, if using a itil copier

133
00:11:06.700 --> 00:11:11.750
alongside so there can be found for example too

134
00:11:11.750 --> 00:11:17.500
former prioritization practices and guidelines

135
00:11:17.500 --> 00:11:23.080
the incident management process then results in an internal one

136
00:11:23.080 --> 00:11:27.730
their use of log information about the incident which can thus still be used again

137
00:11:27.730 --> 00:11:32.950
services to assess resourcing needs

138
00:11:32.950 --> 00:11:38.110
evaluation of its such and classified as prioritized

139
00:11:38.110 --> 00:11:43.250
a list of reported incidents and service requests

140
00:11:43.250 --> 00:11:50,000
the input goes to the copy processes then to the relationship management process

141
00:11:50.000 --> 00:11:54.590
back to the service contract management process

142
00:11:54.750 --> 00:11:56.280
perhaps

143
00:11:56.500 --> 00:11:59.560
the process of managing the right

144
00:11:59.750 --> 00:12:07.250
that is, in this way these processes interact with Niilo as defined by said interfaces

145
00:12:07.250 --> 00:12:12.350
certain processes become inputs to other processes these processes

146
00:12:12.350 --> 00:12:17.510
then returns its results forward to other processes

147
00:12:17.510 --> 00:12:21.440
the processes form such a functional whole; and

148
00:12:21.440 --> 00:12:26.150
as you in the example of the flash can then, for example, itili practices

149
00:12:26.150 --> 00:12:31.070
implement a failure in the practical implementation of the resolution process

150
00:12:31.070 --> 00:12:35.810
in the prioritization of disturbances and in this, i.e. booths

151
00:12:35.810 --> 00:12:40.250
provides such a larger frame of reference by functional areas

152
00:12:40.250 --> 00:12:44.630
can be covered by other information management standards I use for you