1
00:00:12,600 --> 00:00:17,700
Welcome to our podcast. 
Inside sap as rehana, there is 

2
00:00:17,700 --> 00:00:21,600
no product success, without 
customer success, project, 

3
00:00:21,600 --> 00:00:27,400
success, and training, success, 
my name is Arnold kittelson and 

4
00:00:27,400 --> 00:00:29,900
I am a member of the services 
organization. 

5
00:00:30,200 --> 00:00:35,500
Americus I'm also a team member 
on the sap as for Hannah 

6
00:00:35,500 --> 00:00:39,500
Regional implementation group or
rig as we like to call it 

7
00:00:39,500 --> 00:00:43,200
internally. 
In today's session, we will be 

8
00:00:43,200 --> 00:00:46,700
joined by Lavon. 
Urbano from Intel Corporation, 

9
00:00:47,700 --> 00:00:50,900
you will talk about how Intel 
Corporation joined are five 

10
00:00:50,900 --> 00:00:55,000
steps to Fury training. 
How they liked it, whether they 

11
00:00:55,000 --> 00:00:58,800
felt that was benefits to 
joining such a training course 

12
00:00:59,500 --> 00:01:01,400
and what they can do to enhance 
it. 

13
00:01:02,200 --> 00:01:04,900
I understand that Intel 
Corporation has already 

14
00:01:04,900 --> 00:01:08,900
deployed, a few Theory 
applications, but we'll see how 

15
00:01:08,900 --> 00:01:12,400
the course could help them in 
their planning for the next few 

16
00:01:12,400 --> 00:01:16,900
re applications as well. 
Welcome Lavon, would you like to

17
00:01:16,900 --> 00:01:19,300
introduce yourself? 
Absolutely. 

18
00:01:19,900 --> 00:01:25,300
My name is Levon and I'm an 
Enterprise app development 

19
00:01:25,300 --> 00:01:26,700
engineer. 
At Intel. 

20
00:01:27,800 --> 00:01:31,500
Our main business is supplying 
microprocessors to computer 

21
00:01:31,500 --> 00:01:35,800
manufacturers. 
We employ over 100,000 employees

22
00:01:35,800 --> 00:01:40,400
and over 46 countries. 
So our Workforce and a support 

23
00:01:40,400 --> 00:01:43,400
for that Workforce is very 
geographically, dispersed. 

24
00:01:44,100 --> 00:01:47,500
We've used sap products 
extensively for a number of 

25
00:01:47,500 --> 00:01:51,800
years wide, variety of areas 
sales and distribution customer 

26
00:01:51,800 --> 00:01:54,200
relationship warehouse 
management. 

27
00:01:55,300 --> 00:01:58,400
Hop up on a cloud and a prize 
portal. 

28
00:01:59,300 --> 00:02:03,100
And I look at the products that 
are new to us and evaluate 

29
00:02:03,100 --> 00:02:06,800
whether they should be used and 
how best they should be used in 

30
00:02:06,800 --> 00:02:11,200
our environment. 
So most recently, we migrated 

31
00:02:11,200 --> 00:02:16,600
our content from the enterprise 
portal to the Fiore Launchpad we

32
00:02:16,600 --> 00:02:21,400
moved over 20 years worth of 
content over 100 business areas 

33
00:02:21,800 --> 00:02:24,900
to the Fiore launch pad. 
So participating in this boot 

34
00:02:24,900 --> 00:02:29,500
camp has really helped us to 
solidify our understanding of 

35
00:02:29,500 --> 00:02:35,300
the Fiore product. 
Thank you Lavon. 

36
00:02:35,300 --> 00:02:37,600
Yeah, it was exciting to. 
Have you guys seen the five 

37
00:02:37,600 --> 00:02:41,600
steps to Fiora program, given 
how large corporation you are 

38
00:02:41,600 --> 00:02:44,700
and how much work you have put 
into the portal before this 

39
00:02:44,700 --> 00:02:47,500
migration. 
So let's look at the program and

40
00:02:47,500 --> 00:02:53,000
see how you felt about it. 
So did the five steps to Fiore 

41
00:02:53,000 --> 00:02:55,400
boot camp helped form? 
An idea of? 

42
00:02:55,400 --> 00:02:58,400
How would you like to see if 
you're a being adopted and 

43
00:02:58,400 --> 00:03:01,700
Intel? 
Well, going into the boot camp, 

44
00:03:01,700 --> 00:03:05,100
some of our biggest areas of 
Interest were around the 

45
00:03:05,100 --> 00:03:09,000
complexity of Fury apps. 
Their versatility and the best 

46
00:03:09,000 --> 00:03:14,700
ways to enhance them. 
So the three-week, run time for 

47
00:03:14,700 --> 00:03:18,400
The Boot Camp was excellent 
because it gave us the time in 

48
00:03:18,400 --> 00:03:23,700
the environment Explorer, review
discuss and really strengthen. 

49
00:03:23,800 --> 00:03:30,000
Our understanding of the product
capabilities, one of the apps 

50
00:03:30,000 --> 00:03:36,100
that we use as the fiori, my 
inbox application, we used the 

51
00:03:36,100 --> 00:03:40,100
fury, my inbox application to 
replace the enterprise portal, 

52
00:03:40,200 --> 00:03:45,400
Universal word. 
Just the UWL but this product 

53
00:03:45,700 --> 00:03:48,200
the fury. 
My inbox wasn't intended as a 

54
00:03:48,200 --> 00:03:51,100
replacement. 
So some custom development was 

55
00:03:51,100 --> 00:03:55,200
required. 
So as we find more fiori 

56
00:03:55,200 --> 00:03:59,100
applications that and the key 
thing here is when we find 

57
00:03:59,100 --> 00:04:03,200
applications that fully meet our
business need, when those are 

58
00:04:03,200 --> 00:04:08,300
available, we could see how we 
can neatly integrate them into 

59
00:04:08,300 --> 00:04:12,100
our launch pad and also we can 
see how we can tweak them as 

60
00:04:12,100 --> 00:04:16,899
needed. 
So if you re my inbox, we 

61
00:04:17,500 --> 00:04:21,300
actively use that application, 
it generates over 200,000 

62
00:04:21,300 --> 00:04:25,200
approvals monthly. 
And so we really hope that we 

63
00:04:25,200 --> 00:04:28,600
will have more fiery 
applications that fully meet our

64
00:04:28,600 --> 00:04:33,200
business need. 
Wow, that is a lot of approvals 

65
00:04:33,400 --> 00:04:35,400
on a monthly basis in an app 
like that. 

66
00:04:35,400 --> 00:04:38,600
That's great. 
So as you know, we're trying to 

67
00:04:38,600 --> 00:04:42,100
find a lot of customers to, to 
join the boot camp because we 

68
00:04:42,100 --> 00:04:46,200
think it can help them. 
So how do you, how did you guys 

69
00:04:46,200 --> 00:04:49,800
learn about the five steps to 
Fiore boot camp and, and what 

70
00:04:49,800 --> 00:04:52,800
motivated, your team to join the
this training? 

71
00:04:53,900 --> 00:04:58,700
Our in-house sap tqm, that's the
technical quality manager. 

72
00:04:58,900 --> 00:05:03,200
Introduced us to the boot camp. 
So as a way of helping to 

73
00:05:03,200 --> 00:05:07,600
understand the product. 
So if you don't have a tqm it's 

74
00:05:07,600 --> 00:05:14,500
part of our program with sap, we
have an sap employee who is 

75
00:05:14,500 --> 00:05:20,000
available to us and when it's 
not covid is on site to help us 

76
00:05:20,000 --> 00:05:25,300
what issues and escalations. 
We know that Fury functionality 

77
00:05:25,300 --> 00:05:31,700
will be integral in all future 
sap products and with our recent

78
00:05:31,700 --> 00:05:35,300
moved to the launch pad, there 
was a lot of interests within 

79
00:05:35,400 --> 00:05:39,100
the organization. 
So many of our geographically 

80
00:05:39,100 --> 00:05:43,000
dispersed groups were interested
in learning more so the boot 

81
00:05:43,000 --> 00:05:47,400
camp provided an excellent 
opportunity to expose the 

82
00:05:47,400 --> 00:05:50,900
developers, the analyst, the 
bases, the security groups to 

83
00:05:50,900 --> 00:05:55,400
that Fiore area, Perfect. 
Yeah, I think the tqm is part of

84
00:05:55,407 --> 00:06:00,900
the sap Max attention program is
what I believe so yeah. 

85
00:06:01,000 --> 00:06:04,800
So what was, what was the most 
valuable lesson? 

86
00:06:04,900 --> 00:06:08,900
You're obtained from the five 
steps to Fiora training, okay. 

87
00:06:08,900 --> 00:06:12,500
So we learned quite a lot from 
the session, so it's tough to 

88
00:06:12,500 --> 00:06:16,300
pick the most valuable but I'll 
share some of our highlights. 

89
00:06:17,400 --> 00:06:20,900
The format for us was very 
interesting, having the 

90
00:06:20,900 --> 00:06:25,000
sessions, and the environment 
spanning a few weeks, really 

91
00:06:25,000 --> 00:06:28,800
gave us the time to meet 
internally explored the system 

92
00:06:28,800 --> 00:06:33,200
extensively and it's the first 
time we've been exposed to this 

93
00:06:33,200 --> 00:06:37,000
type of a format and we hope to 
see more sessions like these in 

94
00:06:37,000 --> 00:06:40,300
other areas in the future. 
Now, that three-week run time 

95
00:06:40,300 --> 00:06:44,800
was great, but given the extent 
of the content 5 weeks would 

96
00:06:44,800 --> 00:06:49,300
have been even better. 
The sessions gave us a 

97
00:06:49,300 --> 00:06:53,100
comprehensive overview of what 
was required for each job role 

98
00:06:53,300 --> 00:06:56,700
in working with Fiore. 
So, what is our basis team do? 

99
00:06:56,700 --> 00:07:00,000
What is our security team do? 
What does the developers need to

100
00:07:00,008 --> 00:07:03,000
install to get started? 
And how do we tweak the 

101
00:07:03,000 --> 00:07:07,300
applications? 
And, you know, honestly, our 

102
00:07:07,300 --> 00:07:09,900
past experience was that 
spinning up? 

103
00:07:09,900 --> 00:07:13,200
A fury app was not 
straightforward, especially 

104
00:07:13,200 --> 00:07:16,200
ones, where the front end, and 
the back end components were 

105
00:07:16,200 --> 00:07:17,400
indifferent. 
Stunts. 

106
00:07:18,000 --> 00:07:22,900
When you look at the fury apps 
library, you get an idea about 

107
00:07:22,900 --> 00:07:24,900
that. 
There are so many different 

108
00:07:24,900 --> 00:07:29,700
facets to consider the 
activations of the odata 

109
00:07:29,700 --> 00:07:33,600
services, sift Services business
rules, technical roles catalogs 

110
00:07:33,600 --> 00:07:36,900
the group's. 
So one of the things in the 

111
00:07:36,900 --> 00:07:41,800
course, it was good to see the 
rapid app to vation 

112
00:07:41,800 --> 00:07:46,600
functionality in action, so it's
definitely a cleaner approach. 

113
00:07:46,800 --> 00:07:50,600
Watch to have that rapid 
activation and that automated 

114
00:07:50,600 --> 00:07:53,500
activation of the fury 
applications. 

115
00:07:54,800 --> 00:07:59,500
The other thing that was 
interesting for us is that in 

116
00:07:59,500 --> 00:08:03,400
the long term, there's always 
cost to any alterations, we make

117
00:08:03,400 --> 00:08:07,100
to a vendor delivered product. 
So we try to always stay as 

118
00:08:07,100 --> 00:08:12,100
native as possible. 
And inevitably we have to make 

119
00:08:12,100 --> 00:08:17,800
changes So we're always on the 
lookout for low code, no code 

120
00:08:17,800 --> 00:08:21,700
opportunities for enhancements. 
And we did see that there are 

121
00:08:21,700 --> 00:08:25,000
several changes that can be made
without development effort. 

122
00:08:25,800 --> 00:08:27,700
And there are a number of 
changes that can be made 

123
00:08:27,700 --> 00:08:32,100
directly to the front end that 
don't impact the back end 

124
00:08:32,100 --> 00:08:35,600
component. 
So it was, it was enlightening 

125
00:08:36,000 --> 00:08:40,500
to have that visibility. 
Yeah, that's great. 

126
00:08:40,500 --> 00:08:43,200
And that's one of our things 
that we're trying to focus on a 

127
00:08:43,200 --> 00:08:48,500
little bit in the course, it's 
also making a holistic overview 

128
00:08:48,500 --> 00:08:52,700
of the Fiore environments, not 
just like the development 

129
00:08:52,700 --> 00:08:55,700
jumping right into start coding,
when there are potentially 

130
00:08:55,700 --> 00:09:01,200
options for low code or no code.
So, so with that said, how do 

131
00:09:01,200 --> 00:09:05,700
you feel as far as well prepared
to start additional applications

132
00:09:05,900 --> 00:09:09,500
at the Intel corporations? 
So the boot camp is giving I 

133
00:09:09,500 --> 00:09:12,200
said, clear understanding of 
Fiore. 

134
00:09:14,900 --> 00:09:19,800
So when we find Theory 
applications that meet our 

135
00:09:19,800 --> 00:09:24,300
business need, we could easily 
now identify, you know, what's 

136
00:09:24,300 --> 00:09:26,900
the extent? 
And the complexity of the work 

137
00:09:27,500 --> 00:09:33,700
involved in changing it. 
If we need to, we could also see

138
00:09:34,000 --> 00:09:38,800
that they're big benefits to 
spinning up an environment. 

139
00:09:38,900 --> 00:09:42,600
So, So that we could. 
You know, half business, 

140
00:09:42,600 --> 00:09:48,800
evaluation of functionality. 
And with the boot camp, we were 

141
00:09:48,800 --> 00:09:51,900
able to also expose a wide 
cross-section of our 

142
00:09:51,900 --> 00:09:57,100
organization to the product, 
which really gives everyone a 

143
00:09:57,100 --> 00:10:00,200
good sense of what a Furia looks
like. 

144
00:10:00,200 --> 00:10:02,500
What it feels like to navigate 
within it. 

145
00:10:02,800 --> 00:10:06,500
What's involved in activating? 
It tweaking it securing, it, 

146
00:10:06,500 --> 00:10:11,100
enhancing it, so I'm good 
overall sense of what Fury 

147
00:10:11,100 --> 00:10:18,300
application, entails. 
So changing a little bit of 

148
00:10:19,500 --> 00:10:22,600
direction here. 
So so what do you think of the 

149
00:10:22,600 --> 00:10:26,400
sap for implementation 
methodology that we showed cased

150
00:10:26,400 --> 00:10:28,300
in the five steps to Fiora 
training? 

151
00:10:29,000 --> 00:10:34,000
The methodology was presented 
using a team concept so the 

152
00:10:34,000 --> 00:10:38,000
materials were segmented into 
sections for functional expert 

153
00:10:38,000 --> 00:10:43,200
developer basis security But the
materials were covered as a 

154
00:10:43,200 --> 00:10:46,700
team, and I think the team 
approach was brilliant, because 

155
00:10:46,700 --> 00:10:51,200
it mirrors the way that work is 
typically performed. 

156
00:10:51,900 --> 00:10:55,500
So, initial Focus was on basis, 
to build the environment 

157
00:10:55,500 --> 00:10:58,500
security, to build the roles 
developers could work on the 

158
00:10:58,508 --> 00:11:03,300
installs and the analysts start 
becoming familiar with the 

159
00:11:03,300 --> 00:11:07,500
product. 
So that team concept gave all 

160
00:11:07,500 --> 00:11:13,600
groups that is ability to 
various facets of the And there 

161
00:11:13,600 --> 00:11:17,200
are definite benefits that, for 
example, the security team could

162
00:11:17,200 --> 00:11:22,400
clearly see what the developers 
trying to accomplish and with 

163
00:11:22,400 --> 00:11:25,900
that knowledge, can build an 
Optimum security rule. 

164
00:11:27,000 --> 00:11:27,600
Yeah. 
Awesome. 

165
00:11:27,600 --> 00:11:30,500
Because that was one of our 
ideas from the started putting 

166
00:11:30,500 --> 00:11:34,600
this training together was to 
actually try to mimic a little 

167
00:11:34,600 --> 00:11:39,500
bit about how you're working 
within your corporation and 

168
00:11:39,500 --> 00:11:42,900
there are so many Aziz. 
If the bases team have it 

169
00:11:42,900 --> 00:11:45,700
installed everything correctly, 
the developers can develop and 

170
00:11:45,700 --> 00:11:47,500
so forth. 
So that was one of our goals and

171
00:11:47,900 --> 00:11:52,900
glad it worked out. 
So what would you tell other 

172
00:11:52,900 --> 00:11:55,500
customers that are planning to 
join the five steps to fewer 

173
00:11:55,500 --> 00:11:58,800
training? 
We weren't really sure what to 

174
00:11:58,808 --> 00:12:01,300
expect. 
We didn't have a good 

175
00:12:01,300 --> 00:12:06,200
understanding of the format of 
The Bootcamp, and how it would 

176
00:12:06,200 --> 00:12:10,800
work for us. 
So they prescribed an intact. 

177
00:12:11,000 --> 00:12:15,100
Of a developer, a functional 
expert basis, and a security 

178
00:12:15,100 --> 00:12:19,500
rep. 
But those exact rules don't map 

179
00:12:19,500 --> 00:12:22,800
for our organization. 
And we also had a 

180
00:12:22,800 --> 00:12:26,800
disproportionately large number 
of developers and analysts 

181
00:12:27,100 --> 00:12:30,400
compared with bases or security 
reps. 

182
00:12:31,400 --> 00:12:34,500
So here are some of the things 
we did want to have Heights. 

183
00:12:34,500 --> 00:12:38,100
I pearly some of the things we 
wish we had done to get the most

184
00:12:38,100 --> 00:12:43,300
out of the boot camp. 
So, one of the first things was,

185
00:12:43,400 --> 00:12:47,300
we use the sap Cal instance, for
hosting, and not really 

186
00:12:47,300 --> 00:12:50,200
simplified the environment 
setup. 

187
00:12:51,600 --> 00:12:54,600
It gave us. 
It also gave us a chance to 

188
00:12:54,600 --> 00:12:58,600
explore the latest version as 
opposed to, you know what, we 

189
00:12:58,600 --> 00:13:01,100
may have had in house and it was
a lot less. 

190
00:13:01,300 --> 00:13:05,400
Effort to spin up our own 
environment down to spin up our 

191
00:13:05,400 --> 00:13:09,700
own environment in house. 
However, I will say that it 

192
00:13:09,700 --> 00:13:14,200
would have been better if sap 
could also host the environment 

193
00:13:15,600 --> 00:13:19,400
because that was just an extra 
stress step for us to get 

194
00:13:19,400 --> 00:13:25,700
funding to work outside of our 
cloud provider to arrangements, 

195
00:13:25,700 --> 00:13:29,600
to get that hosting environment.
But definitely the Cal instance,

196
00:13:29,800 --> 00:13:34,300
made things easier The other 
thing is that if you have a 

197
00:13:34,300 --> 00:13:40,900
large group, a team lead role is
crucial, and it really should be

198
00:13:40,900 --> 00:13:44,200
a technical person who could 
review the materials for each of

199
00:13:44,200 --> 00:13:48,400
the different prescribed rules 
and then assisted team with 

200
00:13:48,400 --> 00:13:51,800
issues and initiate a 
Communications with sap. 

201
00:13:53,600 --> 00:13:56,700
We ran our sessions as a 
project. 

202
00:13:56,900 --> 00:14:01,100
So we had group Recaps and 
working sessions to make sure 

203
00:14:01,100 --> 00:14:06,600
that everyone was engaged and so
that we could facilitate sharing

204
00:14:06,700 --> 00:14:10,700
and document findings. 
So that's something that would 

205
00:14:10,700 --> 00:14:16,700
be valuable to do. 
And also ensure that people have

206
00:14:16,700 --> 00:14:21,700
enough time allocated at least 
30 hours, I would say for 

207
00:14:21,700 --> 00:14:25,700
developers the The other thing 
is that the workload in The 

208
00:14:25,708 --> 00:14:30,000
Bootcamp, is heavily weighted in
the last two sessions. 

209
00:14:30,000 --> 00:14:34,300
So make sure that people have 
enough time allocated for those 

210
00:14:34,300 --> 00:14:39,600
last couple weeks. 
The other thing that really 

211
00:14:39,600 --> 00:14:41,700
helped us is to do some 
scouting. 

212
00:14:41,700 --> 00:14:44,500
So you have one or two people in
each area. 

213
00:14:44,500 --> 00:14:48,800
Forge ahead and work on the 
exercises on the installs, then 

214
00:14:48,800 --> 00:14:53,100
they could share with the team, 
the issues the work around. 

215
00:14:53,200 --> 00:14:58,000
Rounds. 
And also another problem if you 

216
00:14:58,000 --> 00:15:01,400
have a scenario where your 
screenshots don't match your 

217
00:15:01,600 --> 00:15:05,500
environment, screenshots in the 
materials, don't match your 

218
00:15:05,500 --> 00:15:08,300
environment, it gives you a 
chance to update them. 

219
00:15:09,800 --> 00:15:13,700
The other thing, the other 
reason for doing that scouting 

220
00:15:13,700 --> 00:15:18,900
ahead is if the division of 
labor in your organization 

221
00:15:18,900 --> 00:15:22,900
doesn't map to the materials. 
And what I mean by that is let's

222
00:15:22,900 --> 00:15:27,500
see your security person 
typically doesn't do 

223
00:15:27,500 --> 00:15:31,100
configuration and there's some 
configuration called out in the 

224
00:15:31,100 --> 00:15:35,400
security section. 
You have a chance then to look 

225
00:15:35,400 --> 00:15:40,900
at the materials and move that 
section. the configuration 

226
00:15:41,400 --> 00:15:48,900
section for your developer, a 
few other things, encourage your

227
00:15:48,900 --> 00:15:53,600
basis, and security reps to do 
their work. 

228
00:15:54,900 --> 00:15:59,900
In a sharing session, it really 
gives everyone visibility to the

229
00:15:59,900 --> 00:16:05,800
setup and so they understand 
later on potential issues and 

230
00:16:06,400 --> 00:16:09,500
can help it can really help 
simplify troubleshooting. 

231
00:16:11,600 --> 00:16:17,900
And the last couple things I'll 
mention security roles, some of 

232
00:16:17,900 --> 00:16:20,200
the security rules are 
auto-generated. 

233
00:16:20,300 --> 00:16:25,300
So if internally in your 
organization, you limit Auto 

234
00:16:25,300 --> 00:16:28,500
generation, pay attention to 
basis areas. 

235
00:16:29,600 --> 00:16:32,700
And then the last thing I'll 
mention is give people more 

236
00:16:32,700 --> 00:16:37,400
authorization than the 
prescribed, because especially 

237
00:16:37,400 --> 00:16:44,200
if your rules your basis 
security developers rules, don't

238
00:16:45,400 --> 00:16:52,600
fit naturally with the 
prescribed roles, Give extra 

239
00:16:52,600 --> 00:16:58,400
authorization that way people 
can explore and really 

240
00:16:58,400 --> 00:17:03,800
understand when then the, the 
last thing is that we really set

241
00:17:03,800 --> 00:17:08,400
up fee or user and a student ID 
for every participant. 

242
00:17:08,800 --> 00:17:11,700
And that way we prevented any 
kind of conflicts in the 

243
00:17:11,700 --> 00:17:16,900
environment, so hopefully those 
will help you make the most out 

244
00:17:16,900 --> 00:17:24,000
of your sessions. 
I bet they will, and it's very 

245
00:17:24,000 --> 00:17:26,500
interesting to see how 
intertwined it is between all of

246
00:17:26,500 --> 00:17:28,800
the different groups when you 
lay it out like this Lavon. 

247
00:17:29,500 --> 00:17:32,000
So finally, here, is there 
something else you would like to

248
00:17:32,000 --> 00:17:33,800
share with the audience at the 
end here? 

249
00:17:34,100 --> 00:17:39,700
Well, we were pleasantly 
surprised by how well the format

250
00:17:39,700 --> 00:17:43,300
work for us. 
You know, as I mentioned, we did

251
00:17:43,300 --> 00:17:45,400
go into it with some 
uncertainty. 

252
00:17:45,400 --> 00:17:52,400
We like that integrated approach
the training, we liked the Stan 

253
00:17:52,400 --> 00:17:57,900
of time for the training and the
sessions themselves. 

254
00:17:57,900 --> 00:18:03,500
The presenters were obviously 
expert and had intimate. 

255
00:18:04,200 --> 00:18:06,100
Variance with the null with the 
product. 

256
00:18:07,700 --> 00:18:10,700
Anytime we needed support. 
It was excellent. 

257
00:18:10,700 --> 00:18:13,900
And prompt to whether it was a 
one-on-one or specifically for 

258
00:18:13,900 --> 00:18:18,200
our group. 
So we would really appreciate 

259
00:18:18,900 --> 00:18:24,100
seeing future training sessions 
modeled after this format and a 

260
00:18:24,100 --> 00:18:28,700
big thanks to Jose and Shriram 
and team for their hard work and

261
00:18:28,700 --> 00:18:32,200
support. 
Thank you so much for sharing so

262
00:18:32,200 --> 00:18:34,500
many insights, and Lessons 
Learned Lavon. 

263
00:18:34,800 --> 00:18:39,300
I'm glad that the five steps to 
Fiore boot camp. 

264
00:18:39,300 --> 00:18:41,800
Had a positive impact at Intel 
Corporation. 

265
00:18:42,900 --> 00:18:46,100
If you are interested in joining
this training, feel free to send

266
00:18:46,100 --> 00:18:51,100
an email, requesting enrollment 
to Isfahan as 4-H underscore 

267
00:18:51,100 --> 00:18:56,500
customer underscore care at 
sap.com/learnbi this episode. 

268
00:18:56,600 --> 00:18:59,800
And if you have any feedback or 
would like to propose any other,

269
00:19:00,100 --> 00:19:05,600
Big engaged with us via inside 
as for that is the digit 4. 

270
00:19:05,600 --> 00:19:12,000
So inside, as for at sap.com 
bust, a tuned and be inside as a

271
00:19:12,000 --> 00:19:13,200
PS4, Hannah
