openSAP SAP Business Suite powered by SAP HANA WEEK 2, UNIT 3

00:00:15 Welcome to the second week of the openSAP course for SAP Business Suite powered by SAP

HANA. You have chosen the unit about the impact and real-time value

00:00:25 of Suite on HANA for the line of business Enterprise Asset Management. My name is Martin

Janssen, I'm a solution manager in Enterprise Asset Management and I will be your instructor

for that unit.

00:00:37 After a short introduction, I will show you some examples for the real-time value of Asset

Management powered by HANA.

00:00:47 Asset Management is much more than just repairing assets or doing plant maintenance. Asset

Management covers the whole lifecycle of an asset

00:00:57 from the beginning to the end, from the decision to buy an asset, operation and maintenance

of the asset during the usage,

00:01:07 for example, for production until the end of the life of the asset where the decision is made to

exchange the asset with a new one.

00:01:17 With the tough economic conditions and uncertain markets, companies must maximize their

return on assets.

00:01:25 To be globally competitive, companies must achieve operational and maintenance excellence.

And while focusing on sustainable operations, they must also

00:01:35 manage risk, the performance of their assets, worker safety, and the environment – while

fulfilling of course the business objectives of their company.

00:01:46 SAP Business Suite powered by SAP HANA software leads to the way to new real-time

business practices in this key area of Asset Management.

00:01:59 Together with our customers we worked on the necessary end-to-end processes and solutions

we need to support the complete lifecycle of the assets

00:02:09 We identified the following end-to-end processes to cover a whole and holistic enterprise asset

management.

00:02:18 The first end-to-end process is asset portfolio and project management. This covers the

maintenance of the asset portfolio,

00:02:29 tracking the assets and tracking investment projects for the assets.

00:02:35 Asset information management is the second end-to-end process. This is to hand over or

create the asset master data in the system,

00:02:44 to maintain these data in the system and to keep the consistency of the data in the system on

a very high level.

00:02:53 Asset visibility and performance: This is the interface for the data from the shop floor into the

asset management area,

2

00:03:04 directly from the assets or via historians, to analyze the performance of the assets and to

visualize key performance indicators of the assets in the EIM area.

00:03:18 Maintenance operations: the core of that solution is to initiate maintenance activities for

corrective and preventive maintenance,

00:03:28 plan, schedule and track the activities of the maintenance staff and to collect the data after

execution of maintenance activities.

00:03:39 Maintenance parts and service provisioning to support the maintenance activities with the

necessary spare parts and with the necessary services to do the maintenance activities.

00:03:55 And last but not least, mobile asset management to support the technician with mobile devices

which then contains all necessary data he needs for his job.

00:04:08 Operational risk management to integrate risk information into their maintenance procedures

00:04:15 to integrate information about dangerous goods, about safety of their maintenance procedures.

00:04:23 And last but not least, real estate lifecycle management to manage the facilities and to support

maintenance for these facilities

00:04:36 In the early 2014, so some weeks ago, a new official standard of asset management was

published by the international organization of standardization,

00:04:46 the ISO organization. This standard will deeply influence the significance of asset maintenance

in our companies.

00:04:56 The new standard 55000 addresses asset management, its principle and terminology,

00:05:04 and the expected benefits for adopting asset management in organization and can be applied

to all kinds of assets and to all types and sizes of organizations.

00:05:17 This standard will also promote a better link between the board level decisions and asset

management activities.

00:05:25 The holistic idea of asset management will drive an integrative view on asset management,

environmental health and safety,

00:05:34 quality, and energy, and will drive a more comprehensive planning of capital expenditures and

operational expenditures.

00:05:47 With the availability of SAP HANA we analyzed our asset management solution where

capabilities of SAP HANA will help us to get better,

00:05:57 will help our customers to get better. And we not only checked our own solution but also

complementary solutions from our partner ecosystem

00:06:08 and encouraged our partners to use SAP HANA for their products and functions, too.

00:06:15 We identified different use cases where HANA can have a tremendous impact in maintenance

operations and in asset visibility and performance.

00:06:24 In many cases we optimized functionality to realize advantages out of SAP HANA, in other

cases we created real new functionality specific defined and designed for SAP HANA.

00:06:40 In some area even new processes were possible based on new capabilities in HANA, for

example, the prediction of asset failure is one of the new topics we were able to address by

SAP HANA.

3

00:06:58 Asset availability is the key for a high performing company. Only when the production line is up

and running and there are no outages there,

00:07:08 goods can be manufactured, produced and the company can sell these goods and achieve

their revenue targets.

00:07:16 Maximizing the asset availability means maximizing their returns on asset. The companies

need to establish a maintenance strategy for their assets.

00:07:28 Sometimes the strategy is run an asset until a failure occurs and then repair the asset. In other

cases there is a maintenance plan

00:07:38 to maintain the asset to prevent failure and therefore minimize the downtime of this asset.

00:07:47 There are many other strategies for assets, we will hear later on during my presentation.

00:07:53 To realize preventive maintenance there is the need to define where, at which object, a

maintenance activity should happen,

00:08:03 when this maintenance activity should happen, so for example every ten operating hours,

every second month, and so on.

00:08:14 And last but not least, it need to define what - the step-by-step description what to perform

during the maintenance activities.

00:08:25 All this information is defined in a so called maintenance plan, which will be scheduled and, if

the maintenance plan is due

00:08:35 because the next ten operation hours are reached, needs ... the maintenance plan needs to be

performed.

00:08:45 and the scheduling routine then will create the necessary maintenance orders to perform these

maintenance activities.

00:08:57 To maximize the maintenance availability you need to make use of maintenance plan and

need to schedule frequently to perform maintenance in time,

00:09:06 so the more maintenance plans you use, the more... the better it is for the assets.

00:09:18 You need to check which maintenance plans are due and ensure the accuracy of the planning

by tracking the right ones.

00:09:28 So, track which maintenance plan is really due and which maintenance plan has not yet

reached the necessary values.

00:09:37 To get to accurate planning you need make use of preventive maintenance, you need to be

proactive in planning to mitigate failure of the asset and therefore downtime of the asset.

00:09:52 To enable all this, you really need up-to-date scheduling information and a close and short

feedback loop into your asset management system.

00:10:04 But having a high number of assets means having a huge amount of maintenance plans in the

system which need to be scheduled, and that makes the life of a maintenance planner more

complicated.

00:10:17 Without HANA there was the problem, that with a huge amount of maintenance plans the

necessary time for scheduling was very, very long

00:10:27 to perform the planning for all these maintenance plans in one run.

4

00:10:34 So, the customers therefore pre-selected in a first step which maintenance plans are really

relevant for the next scheduling run,

00:10:44 then they build packages out of these maintenance plan which need then to be scheduled in

one job

00:10:53 and at the end they defined so-called scheduling parameters for these packages to define

specific parameters,

00:10:54 for example, in which horizon I want to schedule my maintenance plans.

00:11:11 The scheduling of these different packages then was planned on different days of the week,

depending on the amount of time the scheduling needs.

00:11:22 This led to different problems with scheduling of these maintenance plans: It was very time-

consuming, for example.

00:11:36 It was very time-consuming, this process, and very error-prone because in some cases assets

were forgotten in these packages.

00:11:47 And therefore skipped, and necessary maintenance activities were not scheduled in time.

00:11:58 The time periods between maintenance activities in some cases were too long because of only

scheduling once a week.

00:12:08 This led to missing necessary maintenance activities or maintenance activities were performed

too late.

00:12:16 And this resulted in incomplete maintenance execution and sometimes even in safety issues,

for example, if you think of an aircraft

00:12:26 you need to do every one flight hour specific maintenance activities and you perform this

maintenance activities at flight hour 150 - that is really dangerous.

00:12:41 Now, with the usage of SAP HANA for the maintenance scheduling, it was possible to make

this process much faster than before.

00:12:52 Faster means, especially this process was faster more than a thousand times.

00:13:01 This speed enables the user to skip the complete pre-selection phase for their relevant

maintenance plans.

00:13:12 There was no longer the need to build packages because all plans could be scheduled at one

time.

00:13:21 Even the definition of the different scheduling parameters was no longer necessary because all

the plans could be scheduled at one time.

00:13:30 And it's a very small horizon into the future. Using SAP HANA...

00:13:38 Via using SAP HANA it was now possible to schedule all existing maintenance plans in one

package, in one run much faster.

00:13:48 This takes now minutes instead of hours or, in some cases, even days to schedule all the

maintenance plan.

00:13:57 The usage of SAP HANA enabled, in addition to that faster scheduling, the change of master

data more elegant and better

00:14:09 in terms of usage because you now can establish mass transactions where you can select a

5

huge number of objects or maintenance plans

00:14:20 and change these maintenance plans in one change routine, so the mass transactions for this

area was enabled by HANA, too.

00:14:33 This leads to many benefits for the customers.

00:14:40 And the customers can now maximize asset availability and safety by using this accelerated

scheduling execution.

00:14:53 The customer has less effort for scheduling because they can select all maintenance plan at

once and do not need to slice and dice the different objects into different packages.

00:15:05 You have up-to-date scheduling information in your system for the maintenance operations

and do not need to think about complex parameter restrictions.

00:15:20 Planning now takes not weeks or days, now scheduling can be run in minutes, so you even

can now run your scheduling routine several times a day.

00:15:33 This faster response time leads to more accurate maintenance scheduling and in addition, as

already mentioned,

00:15:42 you have the possibility to use mass transactions to read very fast a huge amount of data and

change these data

00:15:52 and you do not need all the long-time reading data from the database.

00:16:03 In the area of asset visibility and performance we identified additional use cases.

00:16:10 So, the tracking and visualization of asset-related data is key in that area of asset visibility and

performance.

00:16:20 The user needs the relevant information on the performance of his assets and he needs an

easy understanding,

00:16:29 and an easy judgment of what happens in the shop floor with his assets.

00:16:37 With respect to the assets there are some cross-industry so-called key performance indicators,

for example Meantime Between Failure,

00:16:47 Meantime to Repair, Meantime between Repairs. Such KPI's are totally cross-industry and

relevant for all companies doing asset management.

00:17:00 And during the definition phase of the functionality for Asset Analytics we discussed with many

different customers

00:17:10 from different industries which KPI's are really relevant for them and identified the most

relevant KPI's for such an asset analytics tool.

00:17:22 And we came then to a specific number of more than thirty KPI's and we implemented them

into Asset Analytics.

00:17:31 So, these KPI's in asset analytics can now be clustered in different dimensions.

00:17:39 So, we track in the system, in Asset Analytics, the KPI's for reliability, for availability of the

assets,

00:17:49 for the maintainability, for supplies and for sustainability.

00:17:56 So, in reliability and availability the monitoring of the performance of the assets is possible.

6

00:18:06 To do an impact or root cause analysis on these assets and on the performance of the assets

and to make decisions for improvement programs

00:18:16 you need the KPI's for maintainability and for the supplies. In addition to that, we implemented

the more and more important set of information

00:18:26 with respect to sustainability to track the carbon footprint, to track the necessary KPI's in

sustainability.

00:18:36 Having the set of as I already said more than 30 pre-defined KPI's in Asset Analytics it's now

even possible to benchmark with peers in the industry.

00:18:48 So, to compare your company with peer companies in the industry and to see where is

potential for improvement.

00:18:59 In the area of reporting, without having HANA and HANA Live it was a very cumbersome

process for the end users

00:19:09 to get reports adjusted or even new reports established in the system.

00:19:16 Traditionally, such reports, they're not done in the online transaction system that a user works

from day to day but in an analytical system like Business Information Warehouse.

00:19:34 The user had to contact his IT department and ask for such a new report or to change an

existing report.

00:19:42 And then it took between days and sometimes even a month to come from the definition what

needs to be there in addition to a report or what needs to be there in that new report.

00:19:54 So, from the definition of the requirements until such a report was really available in the

productive system, as said, it took days or even months.

00:20:04 Sometimes the necessary data the user requested was even not there, was not part of the

existing info cubes in Business Information Warehouse,

00:20:14 therefore there was an adjustment or even a new creation of info cubes in Business

Information Warehouse necessary.

00:20:22 The new report then could be built based on the new info cubes, tested and after test it was

transported into the productive landscape

00:20:32 and the users was then finally able to find it and to use it in his productive environment.

00:20:39 The effort for this process was very, very high, as you see on the screen in different steps,

00:20:48 and the need for people with very specific skills was even high, too, because you need people

which are skilled in changing or creating new info cubes,

00:20:59 building extractors from the transactional system into the analytical system

00:21:09 and so, you had a high demand on very high-skilled people.

00:21:15 Now, with having SAP HANA and HANA Live as part of the online transaction system and with

the help of SAP BusinessObjects tools, the life is much easier for the users.

00:21:30 So, as you can see on the slide, many steps I already mentioned on the slides before are now

no longer valid, no longer necessary.

00:21:41 The user can now directly report in real time in the online transaction system.

7

00:21:48 The users do not need to go into Business Information Warehouse or a separate analytics

system, they can work directly in the online transaction system.

00:22:00 And HANA Live delivers all relevant data directly and the user can use existing reports or even

create new reports on-the-fly using SAP BusinessObjects tools.

00:22:13 Now, with HANA and HANA Live an easy-to-use ad-hoc reporting system, reporting tool is

available for the end user,

00:22:24 and no need furthermore for this descripted cumbersome process to get a new report

developed by the IT department, transported in the productive environment.

00:22:38 The business impact is very high. You are much more agile, you have a quick time to decision,

00:22:47 you know you need a specific information and you can get it directly ad-hoc out of the system.

00:22:55 You have a better control over data and reports. As the user you decide which data you need

and which report you run now.

00:23:03 And now, the decisions the users need to make are based on real-time information.

00:23:09 SAP Lumira is the next step in our self-service business intelligence vision, in SAP's business

intelligence vision.

00:23:19 Formerly known as SAP Visual Intelligence software, SAP Lumira now extends even beyond

the desktop into the cloud.

00:23:30 So you can use cloud information in to your Lumira reports, too.

00:23:39 Coming to the area of maintenance planning, of preventive maintenance. We already heard

about maintenance plans

00:23:49 with the information where to perform the maintenance activity, what to perform in that

maintenance activity and when to perform that maintenance activity.

00:24:04 Transforming from this preventive strategy to a condition-based strategy is the next step in

Asset Management.

00:24:17 One of the objectives of course of asset management and of maintenance is to minimize the

downtime of an equipment.

00:24:25 Preventive maintenance strategies for assets are mainly based on volume, on counter

information, on time periods,

00:24:33 so every ten operating hours, every five hundred liters or every one hundred operating hours.

00:24:46 More and more relevance in this area now comes to the condition of an asset.

00:24:53 More and more, the maintenance strategies change to a condition-based maintenance, means

to track the actual condition of such an asset

00:25:05 to judge whether a maintenance activity is necessary or not. You do not need to change the

tires of your car if not really necessary.

00:25:16 To do this condition-based maintenance, to be able to do that, you need to consolidate a large

amount of equipment data

00:25:27 of sensor data from the equipment into your asset management system.

00:25:34 Data like heat, vibration, noise, fluid levels but also quality of products indicates whether a

8

maintenance activity needs to be performed or not.

00:25:45 With SAP HANA it is possible to handle a huge amount of asset data and analyze this huge

amount of asset data in real time

00:25:55 and therefore judge the condition of an asset and, if a specific value is reached, if a specific

condition is reached,

00:26:05 initiate maintenance activities on an asset to change something in the asset, to do a repair, to

exchange sealings or things like that.

00:26:20 There is a predefined so-called rapid deployment solution for Condition-Based Maintenance,

00:26:28 this SAP solution establishes now this necessary link for Condition-Based Maintenance into

the shop floor.

00:26:36 It collects and consolidates the asset data into the asset management area and

00:26:46 provide an easy-to-consume, in an easy-to-consume way the look into these data.

00:26:53 It visualizes trends, asset data in dashboards. It gives you a real-life health monitoring of your

asset.

00:27:08 So, the system not only visualizes what's going on in the shop floor.

00:27:14 The system tracks the conditions of the different assets, visualize them and, if necessary,

initialize automatically maintenance activities for these assets.

00:27:29 This condition-based maintenance is a further step in maintenance strategy, in addressing

maintenance topics via the system.

00:27:39 The next step then from condition-based maintenance is predictive maintenance.

00:27:44 For every asset that contributes to reach the goals of a company, there is the need to ensure

that this asset works efficiently and safety.

00:27:57 To implement now a predictive maintenance strategy, and predictive means to predict failure

which will occur in a future,

00:28:07 to implement such a predictive maintenance strategy there are some prerequisites.

00:28:15 To prepare and to implement such a strategy we need to have a very good understanding of

the capabilities of the assets, the different machines.

00:28:24 What are really the capabilities of them and what are the operational parameters for that

machine.

00:28:32 Apart from their designed parameters it’s even more important to review usage experience

00:28:41 as how were the machines used in the history and historical failure behavior. So, what

happens in history.

00:28:52 Which error occurred, what failures were there in the history. And this knowledge,

00:29:02 the parameters of the machine, the history of the machine, the behavior of the machine, the

usage experience

00:29:11 all this provide the intelligence to judge situations under which these machines stopped

working, producing downtime.

00:29:24 Leading organization, leading companies use these details, these information to identify

9

potential preventive measures and ensure

00:29:34 that such operational environment does not occur once again to avoid such failures of the

machine.

00:29:43 We need the capability to slice and dice this information with statistical analysis to identify

potential relations

00:29:52 between data which seems to be totally unrelated, that could be potential reasons for failure or

downtimes.

00:30:03 So you put together different information and try to find pattern, try to find relationship between

information

00:30:13 which seems to be unrelated. We need to...

00:30:18 We need visibility into deviations of asset performance from the expected results and the

system then need to provide alerts and notifications to the business users

00:30:30 so that they can plan activities, they can proactively initiate maintenance activities.

00:30:40 Asset management powered by HANA already contains a generic analytic tool that can be

used to find such mentioned patterns

00:30:49 of seemingly unrelated information and build models out of the asset data.

00:30:55 So the virtual data model in Suite on HANA already contains all relevant asset information

00:31:05 which need to be there to do such an analysis and algorithms are available from the Predictive

Analysis Library

00:31:15 and from the programming language "R“ to do such analytical activities in the system to find

such patterns.

00:31:27 Results then can be to trigger follow-on activities in other applications like to initiate

maintenance activities

00:31:36 like to inform a service provider to initiate service activities,

00:31:44 trigger information to suppliers with respect to warranties, trigger the provisioning of spare

parts

00:31:54 to help the technician to be more efficient and faster in maintenance activities, and so on.

00:32:01 These follow-on activities of course can be implemented on a customer-specific basis as well.

00:32:10 That is what today is available in Suite on HANA and HANA Live to support such predictive

maintenance projects.

00:32:22 And for the future, SAP plans to build a specific component for predictive maintenance and

service

00:32:32 which should analyze the usage data on the one-hand side and the other already mentioned

information in the system

00:32:42 and should deliver proposals on the one-hand side for engineering improvements of the

assets, on the other hand side, of course the proposal for maintenance activities to mitigate

failure of the asset.

00:32:55 The prediction of potential failure in the future should be part of this component to improve

10

production quality, so keep the production line up and running,

00:33:07 to support service planning and therefore to avoid unplanned downtime of the assets

00:33:16 because the user is with predictive maintenance in a position that he can address issues

before they occur.

00:33:24 This leads to a much better maintenance and service planning and gives the asset manager

the ability to prioritize the real important maintenance activities.

00:33:37 So he exactly knows what will happen, he has a model what happened and he can address

the high priority topics first.

00:33:47 and can judge which is not so high in the priority.

00:33:53 This means he can change from a reactive mode to a proactive maintenance in asset

management.

00:34:03 At the end of this session, some points to keep in mind. So, SAP HANA enables faster and

smarter processes

00:34:13 but makes not only the existing processes faster and smarter. It even enables to address new

processes with the usage of SAP Suite on HANA

00:34:28 HANA Live, the virtual data model, delivers predefined data models that provide real-time

insight into your asset management

00:34:39 and, in addition to that, we do have the right tools, the BusinessObjects tools to visualize that

information for the user to transfer data into information for the user.

00:34:53 SAP delivers several different rapid deployment solutions that run on HANA or Business

Information Warehouse on HANA:

00:35:04 predefined, clear, specified solutions; very fast implemented on customer side

00:35:15 And there is already the possibility to use prediction based on HANA. It is available today and

you can use it today.

00:35:25 And in addition to what is already there, SAP plans to deliver a specific solution for predictive

maintenance and service in the future.

00:35:37 Now we are at the end of the session. Thank you for your participation in the unit of impact and

real-time value of Suite on HANA for the Line of Business of Asset Management.

00:35:50 Now you can do the corresponding assessment. After this you are free to choose one or more

optional units covering other Lines of Business

00:36:02 which are offered in the course of this week. Once again, thank you very much.

© 2014 SAP AG or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG or an SAP affiliate company.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG (or an SAP affiliate company) in Germany and other countries. Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

National product specifications may vary.

These materials are provided by SAP AG or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP AG or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP AG or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. In particular, SAP AG or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP AG’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP AG or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

www.sap.com