Dynamics 365 Asset Management - Simply Explained

1
00:00:00,000 --> 00:00:05,160
A conveyor stops midshift, a forklift won't start, a pump starts leaking, and suddenly everyone needs answers.

2
00:00:05,160 --> 00:00:06,840
Who Tim's going to fix it?

3
00:00:06,840 --> 00:00:09,640
When was the last service? Do we have the right part on hand?

4
00:00:09,640 --> 00:00:12,200
And where Oatm's the record from the previous repair?

5
00:00:12,200 --> 00:00:18,160
Instead, people start calling around, opening old spreadsheets, digging through folders O, while the equipment just sits there.

6
00:00:18,160 --> 00:00:21,600
That scramble costs real time and money before a wrench even touches the machine.

7
00:00:21,600 --> 00:00:28,480
I'm Mercopeaters from M365FM, and this knowledge nugget explains Dynamics 365 Acid Management in plain English.

8
00:00:28,480 --> 00:00:37,640
Etautm's part of Dynamics 365 Supply Chain Management, and it gives companies one place to track equipment, maintenance work, costs, and service history.

9
00:00:37,640 --> 00:00:42,680
Later, we would most see how a sensor warning can turn an emergency repair into planned work.

10
00:00:42,680 --> 00:00:47,400
But before we get there, we need to look at the physical assets of business relies on every single day.

11
00:00:47,400 --> 00:00:53,200
Now, while physical assets become a business problem, the tact must think about the equipment that keeps normal work running.

12
00:00:53,200 --> 00:00:56,480
A factory might have production machines, conveyor belts, motors and pumps.

13
00:00:56,480 --> 00:01:00,240
A warehouse depends on fork lifts, loading equipment and sorting systems.

14
00:01:00,240 --> 00:01:03,040
A transport company needs trucks that actually leave on time.

15
00:01:03,040 --> 00:01:07,240
And an office or facility team looks after heating, cooling, generators, and lifts.

16
00:01:07,240 --> 00:01:09,080
Every one of these items does a job.

17
00:01:09,080 --> 00:01:15,440
But every item also comes with a set of questions that Donau, TMT, disappear just because the equipment is working today.

18
00:01:15,440 --> 00:01:18,400
Where is it right now? Who looks after it? Is it still performing well?

19
00:01:18,400 --> 00:01:21,720
When was the last inspection or repair? Those questions sound simple-o.

20
00:01:21,720 --> 00:01:23,960
Until the answers live in five different places.

21
00:01:23,960 --> 00:01:27,640
One technician might know that a machine or terms of strange noise means trouble because they or

22
00:01:27,640 --> 00:01:29,440
them were worked beside it for years.

23
00:01:29,440 --> 00:01:33,960
Another person keeps a spreadsheet with service dates, purchasing files, part orders somewhere else.

24
00:01:33,960 --> 00:01:38,240
Finance sees invoices and costs, but not always the full repair story behind them.

25
00:01:38,240 --> 00:01:42,200
Then that technician takes a holiday, changes jobs, or simply is no-mit-on-shift.

26
00:01:42,200 --> 00:01:43,520
The knowledge leaves the room.

27
00:01:43,520 --> 00:01:47,520
This used to happen all the time with paper service sheets, folders in a workshop cabinet,

28
00:01:47,520 --> 00:01:49,720
and spreadsheets passed around by email.

29
00:01:49,720 --> 00:01:53,400
A team could still keep equipment running, but finding the full picture took time.

30
00:01:53,400 --> 00:01:55,720
People often worked from incomplete information.

31
00:01:55,720 --> 00:01:57,680
When equipment breaks, the problem spreads fast.

32
00:01:57,680 --> 00:02:00,240
Operations may lose production or slow down deliveries.

33
00:02:00,240 --> 00:02:04,720
The maintenance team has to find the fault purchasing might need to rush an order for a missing part.

34
00:02:04,720 --> 00:02:10,440
Finance later sees an expensive invoice, but can't always connect that cost back to the specific machine or repair.

35
00:02:10,440 --> 00:02:12,480
Nobody plans a breakdown.

36
00:02:12,480 --> 00:02:15,120
Emergency work also changes how people behave.

37
00:02:15,120 --> 00:02:18,840
A team orders the first part they can find pays extra for fast delivery,

38
00:02:18,840 --> 00:02:21,920
or skips the usual planning because the machine needs to run again.

39
00:02:21,920 --> 00:02:27,400
Sometimes that o-tems the right call, but when every repair feels like an emergency, costs climb,

40
00:02:27,400 --> 00:02:29,040
and the same fault keeps coming back.

41
00:02:29,040 --> 00:02:31,640
Different people need different parts of the same story.

42
00:02:31,640 --> 00:02:34,960
Maintenance workers need repair details and past notes.

43
00:02:34,960 --> 00:02:37,640
Operations needs to know whether equipment can run.

44
00:02:37,640 --> 00:02:40,080
Purchasing needs to know which parts are required.

45
00:02:40,080 --> 00:02:44,880
Finance needs a clear cost trail, and managers need to see where failures and spending keep showing up.

46
00:02:44,880 --> 00:02:50,120
Dynamics 365, asset management keeps that working record together for physical equipment,

47
00:02:50,120 --> 00:02:51,920
and the maintenance jobs tied to it.

48
00:02:51,920 --> 00:02:55,560
It does now come to replace the person who knows how to repair a motor.

49
00:02:55,560 --> 00:03:01,200
It gives that person and everyone around them a shared place to record what happened and find what they need.

50
00:03:01,200 --> 00:03:06,440
Before anyone can plan repair work, the system needs a clear picture of each individual asset.

51
00:03:06,440 --> 00:03:09,360
The asset record, a digital file for every machine.

52
00:03:09,360 --> 00:03:11,360
So here's how to think about asset management.

53
00:03:11,360 --> 00:03:15,800
Picture a filing cabinet in the maintenance room where every machine gets its own labeled folder.

54
00:03:15,800 --> 00:03:23,760
The difference is this folder lives inside Dynamics 365 Supply Chain Management, and the right people can find it without digging through a cabinet or asking around.

55
00:03:23,760 --> 00:03:26,480
Open the folder for a machine and you start with its identity.

56
00:03:26,480 --> 00:03:31,480
Record its name, product or model number, serial number, and a plain description of what it does.

57
00:03:31,480 --> 00:03:38,480
Throw in technical details and warranty information too, so the team can check whether a repair falls under vendor coverage before ordering parts.

58
00:03:38,480 --> 00:03:41,000
That sounds basic, but it stops a real headache.

59
00:03:41,000 --> 00:03:44,840
Two machines on the same floor can look almost identical while they're parts, warranty dates,

60
00:03:44,840 --> 00:03:46,640
or service needs are completely different.

61
00:03:46,640 --> 00:03:49,960
A clear asset record tells the team exactly which machine they're dealing with.

62
00:03:49,960 --> 00:03:54,240
The record also needs to answer a practical question, where does this equipment work?

63
00:03:54,240 --> 00:03:58,720
Dynamics 365 Asset Management uses something called Functional Locations for that.

64
00:03:58,720 --> 00:04:03,800
Think of a functional location as the place where an asset does its job, or not just a pin on a map,

65
00:04:03,800 --> 00:04:07,760
but something like a site, a building, a warehouse, a workshop, or a production line.

66
00:04:07,760 --> 00:04:08,560
Here's an example.

67
00:04:08,560 --> 00:04:10,280
Imagine a company with three plants.

68
00:04:10,280 --> 00:04:12,120
Inside one plant sits a packing area.

69
00:04:12,120 --> 00:04:13,920
Inside that area runs a conveyor line.

70
00:04:13,920 --> 00:04:16,760
That conveyor includes several motor, sensors, and rollers.

71
00:04:16,760 --> 00:04:23,080
You can describe that whole structure in the system from the larger location all the way down to the equipment that people actually inspect and repair.

72
00:04:23,080 --> 00:04:25,920
The plant sits at the top, below it, the production line.

73
00:04:25,920 --> 00:04:29,040
Under the line, the conveyor, under the conveyor, a motor.

74
00:04:29,040 --> 00:04:32,800
And below the motor, you might track a component that needs its own attention.

75
00:04:32,800 --> 00:04:36,880
This parent and child structure helps people understand where an asset belongs and what it connects to.

76
00:04:36,880 --> 00:04:39,920
So when a motor fails, the technician doesn't just see a serial number.

77
00:04:39,920 --> 00:04:44,000
They see that it belongs to conveyor line two in the packing area at plant north.

78
00:04:44,000 --> 00:04:48,000
That context helps the team estimate what work might stop while the motor is out of service.

79
00:04:48,000 --> 00:04:49,320
Equipment also moves.

80
00:04:49,320 --> 00:04:51,680
A forklift may shift from one warehouse to another.

81
00:04:51,680 --> 00:04:54,680
A pump may leave storage and get installed in a building.

82
00:04:54,680 --> 00:04:58,880
After a process change, a machine may move from one production line to a different one.

83
00:04:58,880 --> 00:05:02,200
Asset management can track those changes through the functional location.

84
00:05:02,200 --> 00:05:05,120
And that matters for costs to owe when an asset moves.

85
00:05:05,120 --> 00:05:09,400
The system connects its maintenance costs with the financial details of the new location.

86
00:05:09,400 --> 00:05:13,960
So if a machine now works in a different plant or department, the cost follows the machine to the place using it.

87
00:05:13,960 --> 00:05:17,080
You don't have to guess later which part of the business carried the repair bill.

88
00:05:17,080 --> 00:05:21,320
Now, a folder with only the original machine details wouldn't help much after the first year.

89
00:05:21,320 --> 00:05:24,200
The useful part is the history beside the asset record.

90
00:05:24,200 --> 00:05:25,920
Inspection sit next to repair work.

91
00:05:25,920 --> 00:05:27,640
Replaced parts sit next to labor time.

92
00:05:27,640 --> 00:05:32,080
Technician notes, fault details and recorded downtime all become part of the same equipment story.

93
00:05:32,080 --> 00:05:34,160
A new technician can check what happened last time.

94
00:05:34,160 --> 00:05:37,320
Maybe they find the same motor received two repairs in six months.

95
00:05:37,320 --> 00:05:39,120
Maybe a certain part keeps wearing out.

96
00:05:39,120 --> 00:05:43,800
Or an earlier note explains a setting that needs checking before anyone takes the machine apart.

97
00:05:43,800 --> 00:05:46,080
The system doesn't remember better than people do,

98
00:05:46,080 --> 00:05:50,640
but it gives people a place to leave useful information for the next person one point needs clearing up.

99
00:05:50,640 --> 00:05:56,200
Asset management focuses on physical equipment that needs regular care, repair, inspection or service over time.

100
00:05:56,200 --> 00:06:01,200
All think machines, production equipment, vehicles, building equipment and similar working assets.

101
00:06:01,200 --> 00:06:05,440
It isn't the tool for tracking office laptops, phones or software licenses.

102
00:06:05,440 --> 00:06:12,520
Those items may matter to a company, but a production machine with moving parts, service needs and downtime risk creates a different kind of record.

103
00:06:12,520 --> 00:06:15,080
Asset management focuses on that maintenance story.

104
00:06:15,080 --> 00:06:20,760
Once each asset has a clear identity, location, structure and history, the conversation changes.

105
00:06:20,760 --> 00:06:24,240
Instead of waiting for equipment to fail and then asking what happened before,

106
00:06:24,240 --> 00:06:27,800
a team can start planning the care that equipment actually needs.

107
00:06:27,800 --> 00:06:31,400
Preventive maintenance? Fix it before it fails.

108
00:06:31,400 --> 00:06:33,880
There are two ways maintenance usually begins.

109
00:06:33,880 --> 00:06:40,480
The first is reactive work O. Something fails, production stops, and people repair it because they have no other choice.

110
00:06:40,480 --> 00:06:44,840
The second is planned maintenance where a team looks after equipment before a fault turns into a stop.

111
00:06:44,840 --> 00:06:49,040
Using the manufacturer's guidance along with what the equipment actually needs in daily use.

112
00:06:49,040 --> 00:06:50,760
That difference changes the working day.

113
00:06:50,760 --> 00:06:54,760
A manufacturer might recommend checking a pump after a set number of running hours,

114
00:06:54,760 --> 00:07:00,080
but a pump working in a dusty, hot area may need attention sooner than the same model in a cleaner place.

115
00:07:00,080 --> 00:07:05,360
Asset management gives the maintenance team a way to plan around both the manual and the real conditions on site.

116
00:07:05,360 --> 00:07:08,520
Plan maintenance isn't about repairing equipment that works perfectly.

117
00:07:08,520 --> 00:07:11,680
It's about doing small, known jobs at sensible times,

118
00:07:11,680 --> 00:07:16,280
so a small issue doesn't grow into an unexpected failure during the busiest shift of the week.

119
00:07:16,280 --> 00:07:19,440
A maintenance plan can cover recurring work like visual inspections,

120
00:07:19,440 --> 00:07:22,960
cleaning, lubrication, safety checks, testing belts or filters,

121
00:07:22,960 --> 00:07:25,640
and replacing parts that wear out over time.

122
00:07:25,640 --> 00:07:26,720
Think about a forklift.

123
00:07:26,720 --> 00:07:31,000
It needs regular checks on breaks, tires, fluid levels, lights and battery condition.

124
00:07:31,000 --> 00:07:33,120
None of those checks feel dramatic on their own,

125
00:07:33,120 --> 00:07:37,160
but missing them repeatedly can lead to a forklift failing when a warehouse needs it most.

126
00:07:37,160 --> 00:07:39,120
The same idea applies to a production line.

127
00:07:39,120 --> 00:07:42,760
A technician may clean a sensor every week, check belt tension every month,

128
00:07:42,760 --> 00:07:45,280
and replace a part after a known period of use.

129
00:07:45,280 --> 00:07:50,120
Asset management helps the team record those routines and surface the next piece of work when it's due.

130
00:07:50,120 --> 00:07:51,840
Schedules are one piece of that picture.

131
00:07:51,840 --> 00:07:55,840
A job can come to every week, every month, or after a set number of days.

132
00:07:55,840 --> 00:08:00,640
But calendar dates aren't always enough because two machines of the same type may work very different hours.

133
00:08:00,640 --> 00:08:04,040
One machine might run one shift each day, another might run around the clock.

134
00:08:04,040 --> 00:08:07,640
Technical readings give the team another way to judge when maintenance should happen.

135
00:08:07,640 --> 00:08:10,840
Depending on the equipment that could include running hours, distance travel,

136
00:08:10,840 --> 00:08:14,840
temperature, pressure or another measurement that tells the team something about its condition.

137
00:08:14,840 --> 00:08:17,840
You don't replace a part just because a date appears on a calendar.

138
00:08:17,840 --> 00:08:21,840
You replace it when the plan, the equipment use and the readings show the work is due.

139
00:08:21,840 --> 00:08:24,840
Maintenance rounds help with this kind of regular care.

140
00:08:24,840 --> 00:08:29,440
A round gives a technician a planned route or set of inspections across several assets.

141
00:08:29,440 --> 00:08:34,440
Instead of treating every check as a separate surprise, the worker inspects related equipment during one routine visit

142
00:08:34,440 --> 00:08:36,240
and records the results as they go.

143
00:08:36,240 --> 00:08:39,240
Imagine a technician starting a morning round in a packing area.

144
00:08:39,240 --> 00:08:43,440
They check a row of conveyor motors, listen for unusual sounds, look for loose fittings,

145
00:08:43,440 --> 00:08:45,840
and record the readings the company cares about.

146
00:08:45,840 --> 00:08:50,040
The work becomes consistent even when different people take the round on different days.

147
00:08:50,040 --> 00:08:53,240
Now imagine one of those checks tracks vibration on a motor.

148
00:08:53,240 --> 00:08:55,640
For several weeks the reading sits in its normal range.

149
00:08:55,640 --> 00:08:58,040
Then it begins creeping upward, the conveyor still runs,

150
00:08:58,040 --> 00:09:00,440
so nobody outside maintenance may notice a problem yet,

151
00:09:00,440 --> 00:09:03,440
but the repeated reading tells the technician something has changed.

152
00:09:03,440 --> 00:09:08,240
That gives the team time to inspect the motor before it damages itself or stops the line.

153
00:09:08,240 --> 00:09:10,640
This is called condition-based maintenance.

154
00:09:10,640 --> 00:09:14,040
Rather than acting only on a fixed date, the team watches a technical value.

155
00:09:14,040 --> 00:09:17,040
When that reading crosses a limit the company has set,

156
00:09:17,040 --> 00:09:19,440
a maintenance need can appear for someone to review.

157
00:09:19,440 --> 00:09:23,240
A sensor can feed those readings into the process, but it doesn't repair anything.

158
00:09:23,240 --> 00:09:27,640
It can warn that a temperature is too high or vibration has moved beyond an accepted range.

159
00:09:27,640 --> 00:09:30,840
A person still needs to check the equipment, decide what the warning means,

160
00:09:30,840 --> 00:09:34,040
follow safety rules, and carry out the repair or inspection.

161
00:09:34,040 --> 00:09:35,440
That human step matters.

162
00:09:35,440 --> 00:09:37,240
A reading might point to a warn bearing,

163
00:09:37,240 --> 00:09:39,640
but it could also come from a loose fitting a sensor problem,

164
00:09:39,640 --> 00:09:41,640
or a change in how the equipment runs.

165
00:09:41,640 --> 00:09:44,240
The system brings attention to the condition.

166
00:09:44,240 --> 00:09:46,640
Train people decide what action belongs next,

167
00:09:46,640 --> 00:09:48,840
so the aim isn't to predict every failure perfectly.

168
00:09:48,840 --> 00:09:52,240
It's to give maintenance teams earlier notice, better routines,

169
00:09:52,240 --> 00:09:57,040
and fewer repairs that start with a rushed phone call after equipment has already stopped.

170
00:09:57,040 --> 00:09:59,040
Planned work still needs a clear job record,

171
00:09:59,040 --> 00:10:02,840
someone responsible for it, the right parts, and a way to track the cost.

172
00:10:02,840 --> 00:10:03,840
Work orders.

173
00:10:03,840 --> 00:10:06,240
The job ticket that holds the repair together.

174
00:10:06,240 --> 00:10:09,040
So when does a maintenance need become real work?

175
00:10:09,040 --> 00:10:10,240
It becomes a work order.

176
00:10:10,240 --> 00:10:12,640
Think of it as the job ticket that follows a repair

177
00:10:12,640 --> 00:10:15,040
from the first report all the way to the finished job,

178
00:10:15,040 --> 00:10:17,640
giving the team a single record of what went wrong,

179
00:10:17,640 --> 00:10:21,640
what needs to be done, who owns the work, and what it eventually costs.

180
00:10:21,640 --> 00:10:24,840
Without a work order, a technician might still fix the problem,

181
00:10:24,840 --> 00:10:28,240
but the details can vanish into a phone call, a shift hand over,

182
00:10:28,240 --> 00:10:32,040
or someone's memory, and later nobody can easily answer what work happened,

183
00:10:32,040 --> 00:10:35,440
how long it took, or whether the same fault has returned.

184
00:10:35,440 --> 00:10:37,840
And without that record, you're left with guesswork.

185
00:10:37,840 --> 00:10:40,040
Now, a work order can start in several ways.

186
00:10:40,040 --> 00:10:42,640
It might come from a planned maintenance job that's due

187
00:10:42,640 --> 00:10:44,440
from an inspection that finds a fault,

188
00:10:44,440 --> 00:10:46,440
from a breakdown when equipment stops,

189
00:10:46,440 --> 00:10:50,040
or from a technician who finishes one repair, spots another issue,

190
00:10:50,040 --> 00:10:52,640
and creates follow-up work before leaving the site.

191
00:10:52,640 --> 00:10:54,640
Different reasons, but the same structure.

192
00:10:54,640 --> 00:10:57,240
The work order turns a maintenance need into something

193
00:10:57,240 --> 00:10:59,840
the team can schedule a sign, track, and close.

194
00:10:59,840 --> 00:11:01,640
So whether it's planned or unplanned,

195
00:11:01,640 --> 00:11:04,040
the work order captures the reason and the response.

196
00:11:04,040 --> 00:11:06,440
First, the work order describes the job.

197
00:11:06,440 --> 00:11:10,640
A short title might read, "Inspect unusual vibration on conveyor motor 4".

198
00:11:10,640 --> 00:11:13,440
Below that, the maintenance team can add the tasks needed

199
00:11:13,440 --> 00:11:15,640
to complete the work, like isolate the equipment,

200
00:11:15,640 --> 00:11:18,440
inspect the motor mount, check bearings, test the repair,

201
00:11:18,440 --> 00:11:19,840
and return the machine to service.

202
00:11:19,840 --> 00:11:22,440
That level of detail helps when the job changes hands.

203
00:11:22,440 --> 00:11:24,440
A checklist can guide the technician through work

204
00:11:24,440 --> 00:11:26,040
that must happen in a certain order,

205
00:11:26,040 --> 00:11:28,040
which is useful for regular inspections

206
00:11:28,040 --> 00:11:31,240
and helps with repairs where a missed step could create safety risks

207
00:11:31,240 --> 00:11:33,440
or leave the equipment running poorly.

208
00:11:33,440 --> 00:11:35,640
Safety instructions belong with the work too.

209
00:11:35,640 --> 00:11:38,440
The worker may need to lock out power before opening a panel

210
00:11:38,440 --> 00:11:41,440
where protective equipment or confirm a line has stopped

211
00:11:41,440 --> 00:11:43,040
before touching moving parts.

212
00:11:43,040 --> 00:11:45,040
The work order gives the team a place to include

213
00:11:45,040 --> 00:11:47,840
those instructions where people will see them during the job.

214
00:11:47,840 --> 00:11:48,840
Then comes the planning.

215
00:11:48,840 --> 00:11:50,840
The maintenance team can assign the workers, estimate

216
00:11:50,840 --> 00:11:53,040
how long it should take and schedule a date and time.

217
00:11:53,040 --> 00:11:55,240
That doesn't mean every repair runs exactly to plan

218
00:11:55,240 --> 00:11:57,640
because equipment failures rarely read the calendar,

219
00:11:57,640 --> 00:11:59,840
but it gives the team a clear starting point.

220
00:11:59,840 --> 00:12:02,840
You can also add the parts and supplies the job needs.

221
00:12:02,840 --> 00:12:05,440
For our conveyor motor, that could include a replacement bearing,

222
00:12:05,440 --> 00:12:08,240
bolts, grease, or maybe an entire motor.

223
00:12:08,240 --> 00:12:10,840
The work order links the repair with the items required,

224
00:12:10,840 --> 00:12:12,840
so the technician doesn't arrive ready to work

225
00:12:12,840 --> 00:12:14,840
and then discover the part is missing.

226
00:12:14,840 --> 00:12:17,040
That means the technician isn't stuck waiting for a part

227
00:12:17,040 --> 00:12:18,240
that never arrives.

228
00:12:18,240 --> 00:12:21,640
If stock already holds the item, the team can plan around that supply.

229
00:12:21,640 --> 00:12:25,640
If stock can't cover it, the need moves into the purchasing process

230
00:12:25,640 --> 00:12:27,640
and someone can order the required part

231
00:12:27,640 --> 00:12:29,640
without relying on a rushed message

232
00:12:29,640 --> 00:12:32,640
or a handwritten note that gets lost on a desk.

233
00:12:32,640 --> 00:12:36,040
The work order still keeps the repair story connected to that purchase.

234
00:12:36,040 --> 00:12:39,240
This is where the job ticket starts doing more than describing a fault.

235
00:12:39,240 --> 00:12:40,840
It's like a central command post

236
00:12:40,840 --> 00:12:43,640
that everyone can look at before they start their part of the job.

237
00:12:43,640 --> 00:12:46,040
It helps people prepare before the work begins.

238
00:12:46,040 --> 00:12:47,440
The technician knows what to inspect,

239
00:12:47,440 --> 00:12:49,240
the planner knows who should take the job,

240
00:12:49,240 --> 00:12:51,040
the store team can see which parts are needed,

241
00:12:51,040 --> 00:12:53,440
and purchasing can act when a part isn't available.

242
00:12:53,440 --> 00:12:56,240
As work moves forward, the order records its status.

243
00:12:56,240 --> 00:12:58,240
It begins as created, then someone schedules it.

244
00:12:58,240 --> 00:13:01,040
When the technician starts work, the team records that change.

245
00:13:01,040 --> 00:13:03,040
After the repair, it moves to complete it.

246
00:13:03,040 --> 00:13:05,240
And a manager or another responsible person

247
00:13:05,240 --> 00:13:06,840
can review it before the record closes.

248
00:13:06,840 --> 00:13:08,440
Those steps may sound like admin work,

249
00:13:08,440 --> 00:13:09,840
but they answer practical questions.

250
00:13:09,840 --> 00:13:12,240
Does anyone dealing with this has the job started?

251
00:13:12,240 --> 00:13:14,440
Is the machine ready to return to normal use?

252
00:13:14,440 --> 00:13:17,040
Did someone check that the work meets the required standard?

253
00:13:17,040 --> 00:13:20,040
And those questions are exactly what a maintenance team needs answered

254
00:13:20,040 --> 00:13:21,040
during a busy shift.

255
00:13:21,040 --> 00:13:23,640
The completed work order also records what the repair used,

256
00:13:23,640 --> 00:13:26,440
the old labor time, parts, and other expenses,

257
00:13:26,440 --> 00:13:29,640
and the system connects those costs with the asset involved.

258
00:13:29,640 --> 00:13:32,040
Over time, that gives the company a clearer picture

259
00:13:32,040 --> 00:13:33,240
than a pile of invoices.

260
00:13:33,240 --> 00:13:36,040
A manager can see that one motor needed repeated repairs

261
00:13:36,040 --> 00:13:38,840
and the maintenance team can compare the cost of ongoing repairs

262
00:13:38,840 --> 00:13:41,440
with the cost of replacing equipment without searching through

263
00:13:41,440 --> 00:13:44,840
separate systems and guessing which bill belonged to, which fault.

264
00:13:44,840 --> 00:13:47,840
The final part is often the most useful for the next technician.

265
00:13:47,840 --> 00:13:51,240
When the work ends, the technician can add notes about the fault,

266
00:13:51,240 --> 00:13:54,640
the checks completed, the part replaced, and anything worth watching.

267
00:13:54,640 --> 00:13:57,040
Maybe the bearing failed because the mount had loosened.

268
00:13:57,040 --> 00:13:58,640
Maybe the repair fixed the noise,

269
00:13:58,640 --> 00:14:01,240
but the motor should get another inspection in two weeks.

270
00:14:01,240 --> 00:14:03,240
That note stays with the completed work,

271
00:14:03,240 --> 00:14:07,040
so months later, someone facing the same issue doesn't start from zero.

272
00:14:07,040 --> 00:14:09,840
Oh, they can see what happened before, what worked,

273
00:14:09,840 --> 00:14:12,040
and what the earlier technician noticed.

274
00:14:12,040 --> 00:14:14,240
That continuity can save a lot of time down the road.

275
00:14:14,240 --> 00:14:17,040
A work order explains one maintenance job from start to finish,

276
00:14:17,040 --> 00:14:19,040
but its wider role appears when that job

277
00:14:19,040 --> 00:14:21,240
connects with the stock records, purchasing activity,

278
00:14:21,240 --> 00:14:22,640
and cost records around it.

279
00:14:22,640 --> 00:14:24,840
And that's the real value of a work order out.

280
00:14:24,840 --> 00:14:26,640
It's not just a document, it's a tool

281
00:14:26,640 --> 00:14:29,840
that keeps the maintenance operation running smoothly.

282
00:14:29,840 --> 00:14:33,240
Connected to supply chain, finance, and fieldwork.

283
00:14:33,240 --> 00:14:34,840
Think of a business like an office building.

284
00:14:34,840 --> 00:14:36,840
Asset management is the maintenance room.

285
00:14:36,840 --> 00:14:38,640
It focuses on keeping equipment working,

286
00:14:38,640 --> 00:14:40,640
but it isn't cut off from the rest of the building

287
00:14:40,640 --> 00:14:43,040
because the part store purchasing office, finance team,

288
00:14:43,040 --> 00:14:46,040
and service workers all need pieces of the same information.

289
00:14:46,040 --> 00:14:48,240
Asset management isn't isolated out,

290
00:14:48,240 --> 00:14:51,040
it's connected to every other department through the work order.

291
00:14:51,040 --> 00:14:54,840
That connection saves people from copying the same details into separate places.

292
00:14:54,840 --> 00:14:58,040
That means less chance for errors and a lot less wasted time.

293
00:14:58,040 --> 00:15:01,440
Inside Dynamics 365 Supply Chain Management,

294
00:15:01,440 --> 00:15:05,240
maintenance work can connect with the stock records for spare parts and supplies.

295
00:15:05,240 --> 00:15:08,640
If a repair needs a bearing, a filter, or a replacement motor,

296
00:15:08,640 --> 00:15:11,240
the team can check whether that item is already available

297
00:15:11,240 --> 00:15:13,240
before anyone starts chasing vendors.

298
00:15:13,240 --> 00:15:15,040
Stock tells you what sits on the shelf.

299
00:15:15,040 --> 00:15:16,640
When the needed part isn't there,

300
00:15:16,640 --> 00:15:18,640
purchasing can work from the same maintenance need

301
00:15:18,640 --> 00:15:21,040
and a purchase order connects to the repair work,

302
00:15:21,040 --> 00:15:23,440
giving everyone a clearer view of why the item was ordered

303
00:15:23,440 --> 00:15:25,240
and where it will go when it arrives.

304
00:15:25,240 --> 00:15:27,640
Production also sits close to this process.

305
00:15:27,640 --> 00:15:29,440
If a machine needs planned downtime,

306
00:15:29,440 --> 00:15:32,240
operations can see that maintenance work may affect a line

307
00:15:32,240 --> 00:15:33,240
or a warehouse process.

308
00:15:33,240 --> 00:15:36,040
That doesn't remove the need for people to talk to each other,

309
00:15:36,040 --> 00:15:39,640
but it gives those conversations a shared record instead of a chain of guesses.

310
00:15:39,640 --> 00:15:41,840
So when maintenance and production share the same system,

311
00:15:41,840 --> 00:15:42,840
there's less friction.

312
00:15:42,840 --> 00:15:44,040
Finance needs a different view.

313
00:15:44,040 --> 00:15:46,240
A maintenance team thinks about the fault and the repair,

314
00:15:46,240 --> 00:15:48,240
but finance needs to know where the spending belongs.

315
00:15:48,240 --> 00:15:51,040
Asset management can link asset costs to the functional location

316
00:15:51,040 --> 00:15:52,240
where the equipment works,

317
00:15:52,240 --> 00:15:56,440
so repair spending follows the machine to the right plant department or business area.

318
00:15:56,440 --> 00:15:59,040
Imagine the same type of machine running at two different sites.

319
00:15:59,040 --> 00:16:02,640
Both need repairs, but one side uses it far more heavily.

320
00:16:02,640 --> 00:16:04,640
When costs connect to the correct location,

321
00:16:04,640 --> 00:16:08,640
managers can see which site carries the spending instead of seeing one large repair total

322
00:16:08,640 --> 00:16:10,040
with no useful context.

323
00:16:10,040 --> 00:16:12,040
That makes cost conversations less confusing

324
00:16:12,040 --> 00:16:13,640
and helps accompany spot patterns.

325
00:16:13,640 --> 00:16:16,640
If one location keeps spending heavily on the same type of equipment,

326
00:16:16,640 --> 00:16:18,440
the team can ask better questions.

327
00:16:18,440 --> 00:16:20,040
Does that site run longer shifts?

328
00:16:20,040 --> 00:16:21,640
Does it need a different maintenance plan?

329
00:16:21,640 --> 00:16:24,040
Or does the equipment itself need replacing?

330
00:16:24,040 --> 00:16:27,240
It's these patterns that drive better maintenance decisions over time.

331
00:16:27,240 --> 00:16:30,840
Asset management can also connect with Dynamics 365 field service.

332
00:16:30,840 --> 00:16:35,040
Asset management commonly tracks equipment that company owns and uses inside its own operation,

333
00:16:35,040 --> 00:16:37,840
while field service focuses on work performed for customers,

334
00:16:37,840 --> 00:16:39,440
often at customer locations.

335
00:16:39,440 --> 00:16:42,040
When those areas share related service information,

336
00:16:42,040 --> 00:16:45,840
a business can keep a clearer view of equipment, service activity,

337
00:16:45,840 --> 00:16:47,040
and the people doing the work.

338
00:16:47,040 --> 00:16:49,640
One company might maintain machines in its own factory,

339
00:16:49,640 --> 00:16:53,040
while also sending technicians to repair equipment it sold to customers.

340
00:16:53,040 --> 00:16:55,440
Those are different jobs, but the service history,

341
00:16:55,440 --> 00:16:59,040
equipment details and repair habits can connect where the business needs them to,

342
00:16:59,040 --> 00:17:01,440
instead of living in unrelated records.

343
00:17:01,440 --> 00:17:03,440
Sensors add another source of information.

344
00:17:03,440 --> 00:17:06,440
Azure IoT Central can receive readings from connected equipment

345
00:17:06,440 --> 00:17:08,440
such as temperature, pressure, or vibration.

346
00:17:08,440 --> 00:17:11,640
When a reading moves outside a limit, the company has chosen,

347
00:17:11,640 --> 00:17:14,640
it can trigger a maintenance response for someone to review.

348
00:17:14,640 --> 00:17:16,240
The sensor provides the signal,

349
00:17:16,240 --> 00:17:18,640
but the technician still decides what that signal means,

350
00:17:18,640 --> 00:17:22,440
and whether the equipment needs inspection, repair, or a closer look.

351
00:17:22,440 --> 00:17:24,440
The warning can reach the maintenance process,

352
00:17:24,440 --> 00:17:27,640
while the equipment still runs, rather than after a fault stops it.

353
00:17:27,640 --> 00:17:29,840
This kind of early warning can prevent a minor issue

354
00:17:29,840 --> 00:17:31,240
from becoming a major breakdown.

355
00:17:31,240 --> 00:17:34,240
Some jobs also need more than a written checklist.

356
00:17:34,240 --> 00:17:37,040
Dynamics 365 guides, used with HoloLens,

357
00:17:37,040 --> 00:17:39,040
can give technicians step-by-step guidance

358
00:17:39,040 --> 00:17:40,840
while they work on complicated equipment.

359
00:17:40,840 --> 00:17:42,840
A worker can follow instructions in front of them,

360
00:17:42,840 --> 00:17:45,240
which helps when a task has many steps,

361
00:17:45,240 --> 00:17:48,840
or when an experienced technicians method needs to be shared with newer staff.

362
00:17:48,840 --> 00:17:51,440
That doesn't turn a beginner into an expert overnight,

363
00:17:51,440 --> 00:17:53,440
but it gives the technician practical guidance

364
00:17:53,440 --> 00:17:55,240
at the point where the work happens.

365
00:17:55,240 --> 00:17:58,240
While the maintenance records keep track of the job around it.

366
00:17:58,240 --> 00:18:01,240
Many people expect one business app to handle every job by itself,

367
00:18:01,240 --> 00:18:02,840
but it doesn't work that way.

368
00:18:02,840 --> 00:18:04,840
Asset management handles the maintenance side,

369
00:18:04,840 --> 00:18:07,240
while connected parts of Dynamics 365,

370
00:18:07,240 --> 00:18:09,440
handles stock, purchasing, finance,

371
00:18:09,440 --> 00:18:11,240
customer service, and other work.

372
00:18:11,240 --> 00:18:14,040
The benefit comes from records passing between those areas

373
00:18:14,040 --> 00:18:16,040
without people retyping the same details

374
00:18:16,040 --> 00:18:17,840
or losing the reason behind them.

375
00:18:17,840 --> 00:18:20,840
It's the connections between these systems that make the platform powerful,

376
00:18:20,840 --> 00:18:22,640
so let's bring those connected rooms together

377
00:18:22,640 --> 00:18:24,440
through one simple maintenance story.

378
00:18:24,440 --> 00:18:29,440
Now you have a clear picture of how asset management fits into the larger Dynamics 365 ecosystem.

379
00:18:29,440 --> 00:18:34,840
A day in the life, from warning to completed repair.

380
00:18:34,840 --> 00:18:38,240
Imagine a warehouse conveyor motor sending unusual vibration readings.

381
00:18:38,240 --> 00:18:40,040
That's the warning before failure.

382
00:18:40,040 --> 00:18:41,040
Here's the process.

383
00:18:41,040 --> 00:18:44,440
You open the asset record, see the motor's location, history,

384
00:18:44,440 --> 00:18:46,240
warranty, and scheduled work.

385
00:18:46,240 --> 00:18:48,440
Then you create a work order, assign a technician,

386
00:18:48,440 --> 00:18:51,240
list inspection steps, and check stock for the bearing.

387
00:18:51,240 --> 00:18:54,840
If the bearing isn't available, the system orders it while tracking time and cost.

388
00:18:54,840 --> 00:18:58,240
After repair, the technician logs the result and leaves notes.

389
00:18:58,240 --> 00:19:01,240
The manager sees cost, repeat faults, down time,

390
00:19:01,240 --> 00:19:03,240
and all maintenance around that motor.

391
00:19:03,240 --> 00:19:04,840
The warning didn't fix the motor.

392
00:19:04,840 --> 00:19:08,240
It gave people time to plan instead of starting with an emergency scramble.

393
00:19:08,240 --> 00:19:10,840
So most, who it fits and what it does not replace.

394
00:19:10,840 --> 00:19:12,440
So who needs asset management?

395
00:19:12,440 --> 00:19:15,840
Any company that depends on machines, vehicles, production equipment,

396
00:19:15,840 --> 00:19:17,240
or building equipment.

397
00:19:17,240 --> 00:19:21,040
That includes manufacturers, warehouses, transport teams, utilities,

398
00:19:21,040 --> 00:19:22,840
and service-heavy operations.

399
00:19:22,840 --> 00:19:23,840
But here's the thing.

400
00:19:23,840 --> 00:19:26,440
It doesn't replace technicians, safety rules, or judgment.

401
00:19:26,440 --> 00:19:28,640
It gives those people one shared record, oh,

402
00:19:28,640 --> 00:19:30,840
like a medical chart for your equipment,

403
00:19:30,840 --> 00:19:33,840
and a planned way to keep everything running.

404
00:19:33,840 --> 00:19:34,840
Conclusion.

405
00:19:34,840 --> 00:19:37,440
Keep the equipment's story in one place.

406
00:19:37,440 --> 00:19:40,640
With asset management, you keep the asset, maintenance job,

407
00:19:40,640 --> 00:19:43,440
parts, costs, and service history in one place.

408
00:19:43,440 --> 00:19:46,840
Subscribe to m365.fm for more plain English knowledge nuggets

409
00:19:46,840 --> 00:19:48,840
and continue with the next building block.