JDE Maintenance Scheduling

Maintenance
Scheduling
in
JDE

Denise
Hill

Powerco

The most comprehensive Oracle applications & technology content under one roof

Powerco

•  Powerco
is
New
Zealand's
second
largest

electricity
and
gas
distribu8on
company.

•  We
service
approximately
420,000
consumers

represen8ng
46%
of
gas
connec8ons
and
16%

of
electricity
connec8ons
in
New
Zealand.


Powerco

•  Asset
management
company

•  Maintenance
ﬁeld
services
contracted
out
to


Historically

•  Work
issued
to
Service
Provider
and
results
came

back
on
paper

•  Very
hard
to
track
what
had
been
done
/not

done

•  Individual
MS
Access
databases
/
spreadsheets

with
result
data
and
defects

•  $15
million
–
suﬃcient
yield
?

•  Regulated
company
so
maintenance
spend
is

regulated


Gaps

•  No
company
wide
view
of
asset
condi8on

•  Inconsistent
applica8on
of
maintenance

standards

•  Defects
managed
inconsistently
across
regions

•  Squeaky
wheel
got
the
oil


Solu8on

•  Use
JDE
maintenance
scheduling
applica8on

•  Use
Service
Request
applica8on
to
manage

defects


Assets

•  Asset
master
for
network
assets
is
GIS
(ESRI
+

ArcFM
version
9.3)

•  Interface
between
GIS
&
JDE
using
BizTalk.

Adds,
updates
and
deletes
processed

•  Only
assets
that
have
a
capital
value
and/or

are
scheduled
for
maintenance
are
sent
to
JDE

•  Asset
count
in
JDE
is
over
2.5
million


Asset
Hierarchy

•  Assets
arranged
in
JDE
in
a
hierarchy

•  Hierarchy
based
on
spa8al
loca8on
and

connec8vity


Electricity
Hierarchy


Gas
Hierarchy


Where
to
Schedule
?

•  Compromise
between
keeping
number
of

work
orders
to
a
minimum
and
keeping

numbers
of
assets
per
work
order
to
a

sensible
number


Asset
PM
Schedule

•  5
year
cycle
of
maintenance

•  Frequency
and
tasks
required
based
on

maintenance
standards

•  12,000
schedules
so
far
(
in
year
3
now)

•  Generally
set
up
against
a
high
level
“asset”

•  Setup
consistently
across
all
regions
even
if
there

are
no
assets
of
that
type.
WOs
with
no
assets

are
later
cancelled.

•  Actual
assets
to
be
maintained
setup
in
the

Equipment
Routes


PM
Schedule


Equipment
Routes


How
to
Maintain
Equipment
Routes
?

•  Hundreds
of
updates
to
GIS
each
day

•  Thousands
of
schedules
to
maintain

•  Impossible
to
do
manually


Solu8on

•  Create
custom
Model
PM
applica8on
to

deﬁne
what
asset
types
are
to
be
maintained

under
each
Service
Type.
Uses
asset
category

codes,
asset
status
and
age

•  Custom
UBE
to
troll
through
the
asset

hierarchy
star8ng
at
the
scheduled
parent

asset
to
ﬁnd
all
the
assets
that
match
the

Model
PM
and
add
them
to
Equipment
Routes


Model
PM


Equipment
Routes
UBE

•  Custom
UBE
creates
Equipment
Route
records

and
a
log
of
what
schedules
have
been

updated
and
when


Genera8on
of
Schedule

•  Standard
JDE
–
no
mods

•  PM
Backlog
records
and
WO
generated

•  WOs
with
no
assets
cancelled
in
PM
Backlog


PM
Backlog


WO
to
PO
Processing

•  WO/PO
budget
=
#
assets
x
unit
rate

•  Unit
rates
deﬁned
using
Address
Book

Supplemental
data


Custom
UBE

•  Custom
UBE
to
create
WO
parts
list

•  PO
generated
from
WO
parts
list


Field
Results

•  Each
service
type
has
its
own
set
of
tests

•  Custom
app
developed
to
map
service
type
to

tests

•  Test
results
can
be

–  Numeric

–  Pick
list
op8on

–  Calcula8on


Service
Type
vs
Test
App


Pick
List
Setup


Service
Provider
Applica8on
(SPA)

•  Once
PO
has
been
approved
all
the
relevant

data
is
automa8cally
sent
to
SPA
using
BizTalk

•  SPA
consists
of
a

–  Web
app
(ASP.NET
Web
Forms)

–  Mobile
app
(C#
and
.NET
Compact
Framework

Windows
Mobile
6.5)


SPA

•  Web
app
used
to

–  assign
a
Service
Provider
Reference#

–  enter
results
and
defects

–  release
results
back
to
JDE

•  Mobile
app
used
to

–  enter
results
and
defects

•  Conﬁgura8on
in
SPA
comes
from
views
over

data
in
JDE


Orphans

•  Network
changing
so
asset
lis8ngs
will
not
be

perfect

•  Needed
the
ability
to
create
orphan
asset

result
sets

•  User
provides
asset
loca8on/label
details
as

well
as
test
results


Release
Scheduled
Results
to
JDE

•  BizTalk
transfers
the
released
results
from
SPA

back
to
JDE

–  Test
results
entered
into
the
asset
Supplemental

data

–  PM
Backlog
updated
to

•  99
-‐
Complete
if
all
test
results
are
completed

•  96
-‐
Par8ally
complete
if
par8al
result
set
returned

•  97
-‐
Not
Found
if
asset
has
not
been
found
in
the
ﬁeld


Orphan
Results


Defects

•  Defects
are
added
to
Service
requests


Views
in
GIS


Where
to
next
?

•  Precedence
processing

Month
1
Month
2
Month
3
Month
4
Month
5
Month
6

Check
oil
level
√
√
√
√
√
X

Change
oil

√

•  Expand
test
data
types
to
include
text
and

dates

•  Eﬀec8ve
dated
test
sets

•  GPS
coordinates

•  Maps


Ques8ons


Contacts
at
Powerco

Denise.Hill@powerco.co.nz

Enterprise
Team
Leader

Denise.Cadman@powerco.co.nz

Informa8on
Services
Manager


JDE Maintenance Scheduling

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Was ist angesagt?

Was ist angesagt? (20)

Andere mochten auch

Andere mochten auch (6)

Ähnlich wie JDE Maintenance Scheduling

Ähnlich wie JDE Maintenance Scheduling (20)

Mehr von InSync2011

Mehr von InSync2011 (20)

JDE Maintenance Scheduling