►
From YouTube: SAP ACE 2016- HMEL
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hi
everyone
welcome
to
this
session.
We
have
hmel
talking
about
their
project,
for
which
they
nominated
themselves
for
the
ace
awards,
so
we
have
sumanth
from
hmal
who's.
Gonna.
Take
us
through
the
presentation
so
notice
we
can,
if
you
could
just
introduce
yourself
and
then
take
it
up
from
there
on.
Please.
B
B
Okay,
so,
first
of
all,
I
would
like
to
tell
you
about
hmel,
so
htcl,
michael
energy,
hml
hmel
is
a
joint
venture
between
hpcl
method,
sorry
hindustan,
petroleum
corporation
limited
that
is
hpcl
and
missile
energy
investment,
pt
limited
singapore,
which
is
a
lakshmi
and
methyl
group
company.
B
B
B
B
B
So
this
was
about
a
brief
about
hmel,
so
in
2009-10,
when
hms
was
about,
this
company
was
about
to
come
be
commissioned,
come
was
not
having.
It
was
a
greenfield
refinery.
It
was
not
having
any
business
process
any
softwares.
Anything
so
hml
took
a
strategic
program
to
design,
implement
and
sustain
world-class
business
processes
and
cutting-edge
business
applications
which
we
in
hmi
call
it
as
project
prism.
B
So
prism
stands
for
process
integration
through
sap
and
mes.
So
the
idea
was
to
have
plant
food
plant
floor
that
is
field
instrumentation
to
top
floor,
that
is,
management,
dashboards
integration,
including
the
intermediate
control
systems.
That's
it
that
is
this
dcs
data
and
all
transaction
systems
like
sap
and
mes
this
program
aimed
at
creating
an
instrumented,
interconnected
and
intelligent
enterprise,
where
hml
business
teams
to
collaborate
seamlessly
by
leveraging
the
best-in-class,
sap
and
mes
applications
supported
by
state
of
the
art
enterprise
performance
management
system,
that
is,
management
dashboards.
B
B
Html
has
deployed
14
sap
modules
and
14
and
14
mnes
application,
which
are
integrated
via
sap
mii
html
application
architecture
is
divided
into
five
major
layers,
with
mi
integrating
l2
to
l5
layers.
So
l
one
is
physical
assets,
l2
control
systems,
l3
is
mem
that
is
manufacturing
execution
system.
L4
is
sap
and
l5
is
management
reporting
and
through
sfpmi
integration
we
have
integrated
all
our
force
of
all
our
sap
and
mes
applications.
B
B
B
B
B
I
will
review
about
what
were
the
project
objectives
and
how
we
have
achieved
that
okay,
so
the
project
goal
was
basically
to
undertake
next
level
of
integration
of
mes
sap
and
control
systems
and
leverage.
The
second
point
was
leverage
intelligence
of
mi
tool
for
future
hml.
Ig
roadmap
use
the
semantic
mapping
capability
of
sap,
mi
plant
information,
catalog
use,
plant
connectors
for
opc
systems
and
existing
connectors
for
homogeneous
technologies
like
web
services,
etc
and
reduction
of
product
maintenance
cost
some
of
the
project
benefits
which
we
have
realized
after
the
implementation
of
sap.
B
Etc,
now
about
the
key
value
creation,
what
value
sap,
mi
implementation
and
hr
that
is
html
integration
framework
is,
is
creating
for
hmes.
Some
of
the
specifics
are
in
the
area
of
financial
operations
and
execution.
B
We
have
automated
permit
details
from
sap
pm
to
our
operations,
log
book,
updating
of
mes
operations,
data
for
from
source
application
to
our
cpm
dashboards,
updating
of
monthly
production
and
realization
plan
numbers
to
epm
dashboards.
All
this
has
reduced
manual
work,
which
has
given
a
benefit
of
rupees
5
lakhs
on
the
process,
efficiency
and
compliance
part.
We
have
integrated
integrated,
honeywell
movement,
monitoring
data
and
sap
for
our
daily
stock
accounting.
B
This
has
this
is
a
seamless
integration
of
the
physical
asset.
That
is
the
right
from
the
sensor
up
to
the
data
in
the
sap
and
is
very
essential
as
we
required
it
without
any
manual
intervention,
because
physical
stocks,
which
are
there
in
the
tanks,
they
are
directly
reflected
in
our
sap
books,
the
other
being
automatic
updating
of
tank
level
inventory
and
data
into
data
historian
automation
of
lab
data
with
process
historian.
B
B
On
the
innovations
part,
what
innovations
during
the
project
we
have
brought
in
and
hmiel
has
done
for
during
the
sap
mi
implementation
in
the
process.
In
for
the
process,
innovation,
we
have
single
mi
installed
in
corporate
network.
B
B
B
So
by
this
installation
in
plant
network,
the
data
gets
updated
from
different
data
and
dcs
in
future.
If
mi
has
to
integrate
directly
with
process
control,
layer,
dcf
and
instance
of
speaker
has
to
be
installed
in
plant
network
on
the
other
part
of
innovation
in
the
design
and
business
model
we
have.
We
have
mdo
data
exchangement
mechanism.
Mdo
is
manufacturing
data
object,
so
we
have
implemented
asset
to
transfer
mdo
related
data
between
mri
systems.
B
A
B
On
the
design
and
business
model,
innovation
is
measur
a
message
process
mechanism
so
message.
Process
functionality
is
also
used
in
hmi
to
process.
The
interface
related
messages
that
gets
saved
data
user
can
easily
select
the
interface
and
data
range
as
required
to
process
the
message.
It
could
be
easily
processed
number
of
message
by
user.
Also
in
attached
screenshot,
we
mentioned
the
message:
processing
functionality
on
the
building,
competitive
innovations
we
have
mrf.
That
is
the
message
routing
framework.
B
B
Other
innovation
areas
which
we
have
implemented
to
fsp
mii,
are
plant
information.
Catalog
this
has
been
implemented,
project
backup
utility.
This
has
been
implemented
as
helping
sap
with
mi
version
15.1
issue,
so
we
were
on
the
ramp
up
as
a
ramped
up
customer
of
sap
mri
and
during
the
project
implementation.
B
B
Am
I
when
we
we
were
we
identified
sapmi
as
the
tool
for
our
hiv?
That
is
html
integration
framework?
We
have.
We
had
two
things
in
mind
that
we
have
to
leverage
the
intelligence
part
of
sapmi
in
the
future
and
how
sap
mi
can
fit.
In
my
vision
for
2020
and
beyond
so
mi
implemented,
implementation
done
in
html
is
aligned
to
industrial
4.1.
B
Oh,
that
is
collecting
visualization
visualizing
and
analyzing
data
using
sap.
Mri
offers
a
whole
new
world
of
opportunities
for
hmer,
with
increased
transparency.
My
by
making
data
visible
integration
and
intelligence
trend,
identification,
early
warning
system
and
flexible
deployment.
So
in
2016
we
we
want
to
enhance
the
plan
to
enterprise
integration
to
sapmi.
B
We
want
to
capitalize
on
the
deeper
erp
connectivity
and
broader
standards
based
on
integration
scenarios
and
rich
manufacturing
services
and
2017
and
beyond.
We
use
we
want
to
use
leverage,
sap,
mi
for
our
internet
of
things
and
machine
to
machine
technology,
to
create
business
value
for
mes
for
hmu
and
gain
enterprise,
wise
insights
from
real-time
event,
processing
and
big
data,
manufacturing,
analytics
and
visualization
optimize
asset
utilization
gain
insights
into
poorly
performing
assets
and
real-time
manufacturing
user
interfaces.
C
Thanks
a
lot
sir,
for
presenting
your
project,
so
one
question
that
I
have
from
about
this
project
from
my
side
is:
if
you
were
to
do
a
few
of
the
things
differently,
you
were
given
a
chance
to
redo
or
be
a
part
of
this
project
again.
So
what
are
the
things
that
you're
going
to
do
differently.
B
So
what
difference
do
we
have?
We
would
have
done?
Is
we
right
now
we
have
gone
for
phase
twice
implementation.
First,
we
have
done
the
integration
and
then
we
are
going
for
the
intelligence
part.
So,
given
the
choice,
we
would
have
done
it
both
so
family.
B
A
B
B
So
that
was,
I
have
been
learning
other
things
which
we
have
learned
is
we
have
removed
lot
of
redundant
integration
points
through
sap,
mi
integration.
So
earlier
we
were
having
sap
pi
in
between
the
integration
layer
so
that
that
learning
we
have
that
you
should
have
minimum
integration
touch
points
so
that
the
failures
are
less.
A
Thank
you,
okay,
thank
you.
If
you
don't
have
any
further
question,
then
I
would
like
to
thank
both
both
of
you
guys
who
actually
helped
do
this
session
and
I'm
looking
forward
to
meeting
you
in
mumbai
at
the
ace
awards.