3. ASTICONArla Foods 2003 – 2018: Learnings
A history of MES-implementation at the front EDGE:
- Early adopter, always 2 years ahead of technology
- Great cooperation with Wonderware /sharing visions
- Too much focus on collecting data
- Too little focus on the last 40 cm to the user
- Little understanding of perspective at Senior Mgmt
- Strong relation management with site
- Total lack of tools for multi-site deployment
- “Don’t come and upgrade, what works ..”
2003
Master Brains:
2018:
50 sites
4. ASTICONCurrent status: Learnings & Challenges
MES/MOM Implementations – IN GENERAL - characterized by:
- There is often “politics” in defining border line between MES and ERP.
- Lack of resources by customer to engage in project
- MES is the “abstraction layer” between ERP and the real world.
Makes it hard to avoid “custom code”.
- Often: too large an initial scope. Start with a narrow, “vertical”
solution.
- Limited Senior Management understanding of MES opportunities /
challenges
6. ASTICONNEW Technology: Industry 4.0 overview
The 1st (Steam)
The 2nd (Ford T)
The 3rd (www, PC)
The 4th Industrial Revolution
Internet of Things (IoT)
IT: ”Digital”
New
Business
Models
INDUSTRIE 4.0
The good old www: Internet
(of People)
Supply Chain: Manufacturing Customer-oriented
INDUSTRIAL
IoT
MES/MOM & Automation
7. ASTICONNEW Technology: EDGE
With the Cloud-providers
Viewpoint:
EDGE
Device
EDGE
Device
EDGE
Device
EDGE
Device
EDGE
Device
EDGE
Device
EDGE
Device
ERP
MES/MOM
Automation
PLC PLC
EDGE device
EDGE device
EDGE device
EDGE device
EDGE device
EDGE device
S
S
S
8. ASTICONNEW Technology: Learning from the “office-IT”
In the OT world, we have focus on
Operations, Productivity, Efficiency
WITH EDGE TECHNOLOGY COMES:
Scalable
Software
High-level
Languages
Artificial
Intelligence
Open Source,
Eco-systems
Object oriented
Programming
Software life cycle
Management
Auto-testing
IT OT
Life Cycle Management !
9. ASTICONNEW Technology: Using Cloud(s) in Manufacturing
1. Cloud for Business
Transactions
2. Cloud for external
Services
EDGE device
EDGE device
EDGE device
Azure IOT
AI
3. Cloud for EDGE
Device/App Mgmt
Corporate Data Center
DWH
ONE truth of
Manufacturing
Information
4. Cloud for Manu-
facturing big-data
10. ASTICON
The Supply Chain
Product Research/
Innovation
Digital Twin
Plant
Control
QA, Life Cycle Mgmt
Plant
Maintenance Resource Management
Warehousing & Logistics
Customer
Opportunities: Industry 4.0 in Supply Chain
Multi-level Planning
IIoT: Connect to “everything” –
enable extensive use of data
11. ASTICONOpportunities: Typical business cases
• Collect even more data from production:
• Collect “all data” - to be able to tell the story of the product
• Fast detailed traceability through all production steps (4h)
• Collect data without affecting validated systems
• Collect data to deliver “story around Product”
• Optimisation with Machine Learning algorithms
• Tools for the operator, handheld devices, remove double entry of data
• Maintenance:
• Smart remote service (e.g. HoloLens)
• Monitor equipment – repair just in time
• OEE and equipment utilisation
12. ASTICONChallenges:
- 70% says Industry 4.0 is top priority. Progress remains unexpected SLOW. PILOT PURGATORY !
- 3 steps to succeed:
- Executive sponsorship + clear roles/resp for the digital team
- Chooses use cases carefully. Tangible value, easy-to-implement, right people on site.
- Ensure IT/OT cooperation.
- On most factory floors, the links between IT and OT tend to be immature in unique ways.
- Five issues, blocking roll out of solutions:
- Heterogenous environment at plant floor
- Old, unconnected machines
- Security concerns ( stay on-prem )
- Limited site local OT capabilities
- Poor collaboration between IT and OT.
Source: McKinsey & Nestlé
13. ASTICONAgenda
1. Introduction
2. MES/MOM – current status
3. New technologies, opportunities & challenges
4. How to succeed
- PEOPLE – PROCESSES – TECHNOLOGY (WHO-WHAT-HOW)
5. Q&A
14. ASTICONPeople, Processes and (then) Technology
When starting a digital journey, do your planning in this order:
1) Define the Vision/Guiding star for the journey
2) People, stake holders (WHO)
3) Processes (WHAT)
4) Technology (HOW)
5) Iterative Process (who – what – how)
People
&Culture
&Org
Proces-
ses
Tech-
nology
15. ASTICON
Joint IT + MES/Prod-IT
team ??
People: IT/OT explained
IT OT
ERP Team
Architecture team
Infra Structure
Service desk,
2. level support
“Digital” team
Information Technology - Operations Technology
Corporate functions: HR, Legal,
Procurement, Sales, Marketing,
High levels Planning
Information/IT
Security
Corp Engineering
Corp Project office Corp LEAN office
Corp Quality
MES/Prod-IT team Automation team
Automation team
Site Mgmt
Production Mgmt
Maintenance Dep.
Lean/PTD
Process mgmt
..Other local teams
Local Project office
Quality MgmtMES/Prod-IT team
16. ASTICONPeople: Analytics translator - the new must-have role
• Recognizing that success with IIoT requires cross-functional, agile teams.
Teams that include data engineers, visualization experts, and— perhaps most important—
translators.
• A “Translator” is bridging the (IT) technical expertise with operations’ domain knowledge.
• What “Translators” do:
• Use domain knowledge to find best business cases
• Use their analytics understanding to convey business goal to data scientists
• Communicates the benefits/insights back to business to drive adoption.
• Can (almost) only be found internally, due to domain knowledge is critical
Source: McKinsey
17. ASTICONProcesses: Where to start
Find the first gross list of opportunities:
- Get your colleagues to think: “If only I could have ….!”
- Remove manual work (e.g. double entries)
- Transparency: collect, integrate & publish data
- Traceability (production and quality data)
- Data on you hand-held
- Optimise work flows (e.g. Maintenance)
- Optimise production- and packaging-processes
- Equipment efficiency / OEE
- Get Suppliers and other end-users’ inspiration
Choose the Opportunity where:
1) Chance of getting very VISIBLE
results.
2) Possible to implement prototype
within 2..3 months
3) If the Site director is not interested,
move on !
18. ASTICON
Technology: Focus on Architecture,
rather than “choosing a software package”
Think “big” - (try to) think “long-term architecture”:
• Connectivity - Clear interfaces
• Open platform / open source ?
• Whatever software, you choose – in 3 years time …
• Decent System Development and Management tools
• Bear in mind: Regulatory requirements come to all
industries
19. ASTICONWrapping up
• Vision: Vision & Senior Mgmt ownership.
• Strategy: Define strategy (and keep updated)
• Relations: Engage IT/OT key stake holders
• Team: Set team & roles (business, scientist, translator ! )
• Tools: Select an agile method (scrum team level, not too big)
• Case: Start with a narrow use case, with expected clear results
• Tech: Don’t wait for the “right” technology. Fail-fast = learn fast !
• Architecture: Define and keep updating
• Connectivity: Integration layers, data governance and models.
• Iterations: 3 weeks/12 weeks (inner/outer loop)
20. ASTICONAgenda
1. Introduction
2. MES/MOM – current status
3. New technologies, opportunities & challenges
4. How to succeed
- PEOPLE – PROCESSES – TECHNOLOGY (WHO-WHAT-HOW)
5. Q&A
21. ASTICONThank you for listening ..
Arne.Svendsen@asticon.dk
MES-architect &
Business Translator
Ready for:
new jobs
in new industry verticals
in 2020 ..
Thank you for support to:
Carsten Nøkleby, SESAM-world.com
22. ASTICONASTICON – Partner network
Informal Partners (extract):
• NiceLabel – Enterprise Printing Solutions
• Eltronic - MES/MOM/Automation integrator. DIAP EDGE/Cloud solutions.
• CGI – IT Services + MES/MOM/Automation.
• Integra2r. MES/MOM integrator.
• Au2mate – MES & Automation experts.
• Optimatic – EDGE Solutions, OEM-software to Machine Builders
• AVEVA Wonderware – MES/MOM Solutions, EDGE/Cloud.
• Mitsubishi MES/MOM/Automation + Advanced EDGE solutions
• I2R, MES/MOM/Automation consultancy and solutions.
• Head House Consulting – Change Management Experts
Knowledge sharing with other end-users:
• SESAM-World.com
• SESAM has 4-6 day-conferences per year, focused on todays’ topics.
We have ongoing work groups, e.g. “Production data in Cloud”, PackML, GAPP Project Model
Strongly recommended, not least due to interaction with other end-users.
Editor's Notes
This presentation is based on 30 YEARS WITH MES/MOM.
I will try and mix my own experiences from past and from current MES projects, I am involved in.
.. With the newest findings from McKinsey and other sources that I follow.
I was an automation engineer in the 80’ies, MES consultant in the 90’ies.
Currently working as MES-architect in 3 different businesses: Chr Hansen, which a.o. is probiotic culture production, McNeil which is part of J&J and last, in chicken slaugthery business, which is again quite different.
Looking for new ventures in 2020 …
CONTENT
- current status – what are the main challenges, we face implementing MES
Quick overview of new tech’s and opportunities, has been covered a lot already today
What to do (different) to succeed MES/MOM projects.
How to do thing in small slices and agile ?
I have some 25 minutes, so I wont get into detail on technology as I usually prefer, but insteat focus more on what to with people and not least company cultures on how to succeed. Again based on experiences from past and present.
Let us get STARTED
50 SITES IMPLEMENTED, FULL SAP-INTEGRATION
INTEGRATION PROJECTS: INTEGRATING PEOPLE, PROCESSES AND TECHNOLOGY
2 or more different CONTEXTs and Name Spaces
I work as independent consultant today – but still with a little preference for Wonderware and its products. Not gotten used to say AVEVa .. Currently working with ERP-integration and MES with WW involved on 2 of 3 projects.
Bullet1: You can work on the politics side bringing parts of the organization closer together
Bullet2: Given fact that there is fewer resources on most sites
Bullet3: Given fact MES will also in future be needed to bind 2 worlds
Bullet4: You can work on the scope
Bullet5: Senior mgmt IS are much more motivated to understand - due to all the fuzz about I4.0
This was 2 slides, which is a Maggi cube or boil down of 25 years with MES, primarily Wonderware but also homegrown and other standard MES solutions.
Let us have a LOOK FORWARD on INDUSTRY 4.0, Cloud and EDGE.
I expect most of you to have a good idea of this already, so here is my short overview.
How does it all fit together MES – CLOUD – EDGE and other new terms
What are the leading businesses trying to achieve
My simplified ”try” to put the buzzwords into the same CONTEXT
IOT as of 2007 – the iPhone
Industry 4.0 as of 2011, Merckel decided to MOVE Germany forward
”Digital” – appeared in the Corporate IT organisations, as of 2013’ish
Industrial IoT – a cousin to I4.0
MES/MOM AUTOMATION – STILL AT THE CORE OF THE FACTORY !
We are MISSING EDGE and CLOUD. (FOG computing does not exist in my mind)
US, UK, China, Japan has other acronyms for Industrie 4.0 – of course
You will hear some people say that ISA88,95 is going outdated, and the same with MES systems. It is mostly the new field players trying to make room, as well as universities, which tends to say this. I disagree, as you can hear. This said, it is definitely a challenge to the MES/MOM suppliers to improve – AND OPEN UP –their suites.
A VERY QUICK EXPLANATION to EDGE
Seen from the CLOUD, seen from IT – the edge of the world out there
Seen from OUR side, in the factory, things are a BIT MORE COMPLEX
What to do about new devices, sensors – WHEN to connect with MES/MOM and when to go to CLOUD directly
I am involved in several projects, where we discuss these thing, but today I will actually NOT DISCUSS this in detail, as Peter has asked me to try NEW LAND and talk more about the PEOPLE and CULTURE side.
So let us talk more technology tonight.
I can strongly recommend to join Danish SESAM community, if you want to get hands on. There is a EDGE hands-on conference in early December in Copenhagen, that I am part of arranging.
EDGE comes with all the good development standards and tools, known from PROFESSIONAL SOFTWARE DEVELOPMENT. In PARTICULAR if you are in regulated businesses, this is useful. I just pulled in a figure from the GAMP5 practice model we use in Pharma.
But ALL industries will benefit from better LIFE CYCLE MANAGEMENT of increasingly large software applications on the shop floor.
With EDGE comes a spreading of intelligence into to a large number of devices, only possible with strict system management. I HAVE MISSED MES TOOLS FOR SYSTEM MANAGEMENT AND MULTI-SITE DEPLOYMENT for 2 decades. It is coming to the factory now.
EDGE benefit: Not so much what you can do with it, but HOW you can lift your development methodologies and life cycle management. If you want to work with AI/Machine Learning, which you DO WANT TO, then this is the way forward.
This slide is IRRELEVANT in today context, but I can let it go.
Lots of people are slightly confused about CLOUD in relation to the factory floor. Here is my take on it:
The purpose: The clarify that CLOUD has at least 4 different purposes.
Your business applications are going to cloud. This is an example of NiceLabel printing solution via Cloud
New business model, e.g. Tetra Pak: You give them your machine data, they bundle with other data, and you can pay to get some intelligence back.
Cloud for managing your devices, as of previous slide
Cloud for collecting the one truth of the factory. ( In real Cloud on cloud-on-prem, melting together)
Current examples: Middleware and MES development based on Microsoft Azure DevOps and .net CORE suites. If is fast, it just works, it support working with Agile teams, baselines, realeases and branching of your software. AND there is thousands of young people wanting to work with these tools, as opposed to e.g. ladder programming.
Let us talk opportunities based on a classic Supply Chain figure, like this.
In some industries such as Automotive, there is a lot of focus on Digital Twins
Across many industries, there is focus – still today – on UPTIME, and ensuring Plant Maintenance, incl. OEESENSORs on e.g. rotating equipment measuring vibration and sound.
It can be simple, using HoloLens and setting up a Skype session with you man in the field, simple, working ..
In areas as AGV’s, robots, cobots - the software has matured a lot, making it much easier to get up running.
And then of course we have the over-arching theme of CONNECTING AND COLLECTING - IIoT
Bring RASPBERRY PI 4.0 UNIT:
Finding the first gross list of opportunities:
- Get your colleagues to think: “If only I could have ….!”
- Remove manual work (e.g. double entries)
- Transparency: collect, integrate & publish data
- Traceability (production and quality data)
- Data on you hand-held (?)
- Optimise work flows (e.g. Maintenance)
- Optimise production- and packaging-processes
- Equipment efficiency / OEE
- Get Suppliers and other end-users’ inspiration
Limited last-mile OT capabilities at scale: Fundamentally, delivering Industry 4.0 at scale requires the ability to extract, interpret, and harmonize data from disparate systems that were not designed to work together. When building towards an IIoT platform, make sure you can find capable OT service providers
Poor collaboration between IT and OT.Often the problem is due to the historic lack of connection between IT activities and OT activities, typically by onsite manufacturing process engineers. Getting the IT and OT staffs working together from the start is a must.
Today, in 2019, supply chain organisations are working hard to take the benefits of the new promised land, called Industry 4.0. Leaders are starting to have success, laggers have not at all started to consider it.
A large segment in the middle are struggling with their first prototypes, and taking some expensive learnings. This presentation is giving a view on current status, and suggesting a checklist on how to succeed, with a strong focus on the people and culture side of implementations.
With RIGHT PEOPLE, you can do anything
AND With a CLEAR GOAL-of-WHAT, you can succeed any technology
Define the Vision/Guiding star for the journey
Culture, people, stake holders (WHO)
a) Who is invited, who to invite to the journey ?
Processes (WHAT)
a) Take an overview of the Factory -> gross list of buss.cases
Technology (HOW)
a) Look at your install base, and find candidate areas.
Iterative Process (who – what – how)
a) Come up with gross list and rough shot estimates
b) Suggest the team, that can succeed
c) Suggest a lean-agile way of working
In ONE picture, this is WHY MES PROJECTS ARE SO COMPLEX.
Remember: MES is the abstraction layer between Central business applications and the REAL COMPLEXITY out there.
Referring to the McKinsey statement in the start: IT – OT as terms I think, originate from the US, and there are different perceptions on it. Here is my version.
In the past, WE in the production has had the perception of IT as far away, rigid to work with, show stoppers, lets try to go without IT involvement etc etc The SAP consultants cost a fortune, and at the end of the project, we need to fix the last details anyway to get it to work.
In the past, WE in IT has had the perception, that MES, Automation, printers, scanners and all the stuff on the shop floor has been a big black box, and there is no structure out there. And why don’t they just keep Windows upgraded, as a minimum etc ..
(Sub) cultures and ways of working are almost always different, some times VERY different.
Funding models may be different, approval and project processes, causing priorities out of sync.
The challenge and answers – according to McKinsey 2019:
Get to understand Analytics opportunities in general + own opportunities
Process: Decide where the most promising sources of value exist
Data Science is the easy part. The hard part is getting the data (and valid)
When data not ready/valid, decide on effective data governance
It is as much about CHANGE management. Work will be different. Have a “translator”
Make dash boards, deliver results early and continued to internal customers.
Central function to own best practices (CoE)Many organization models work. Fast decision-making is key.
Having/breeding talents: Data Scientists can be found. Business translators are needed, to be groomed.
Allow failure. Build sandbox environments and build a fail-fast culture.
Make a gross list of opportunities
Use the Business translator “role” we just learned about - to connect with customer to find what is REALLY importantKEEP IT SMALL
Make thin slice solutions, where data from e.g. one work cell get collected AND brought to the customer.
Think AGILE.
By Agile I mean, find an experienced scrum master to run an agile team.
DON’T implement any big AGILE framework – that will take all you focus.
If you want to implement Agile ways of working, implement it piece by piece – use the agile mindset even on implementing you AGILE ways of working !!! ( a bit “meta” )
Of course you should still look carefully at the FUNCTIONALITY of the technology and software you are about to go with.
But in the past, I have seen that there has been just TOO MUCH focus on choosing software it self.
It is the eco-system around – that matters. If there is clever integrators /solution houses for a certain MES package, then you can succeed – in time – otherwise – the best software solution can fail the goal, if you miss the people and organization to do it right.
So if we just do af few thing right on the people side, MES projects will succeed and there is still a huge need out there.
Just think of it – I Denmark, 3-4 of the real large players are looking to choose an MES system. The likes of Grundfos.
The is in fact opportunities for Wonderware and its like: It seems, some of the really large end-users are “growing out of their home-grown solutions”. I think some of these companies started out on MES-functions back in the 90’ies where MES was not on the market yet. Arla started when MES systems came about for real in around 2000, and now some of the big earlymovers are giving standard MES packages a new chance. My interpretation at least ..
Today, in 2019, supply chain organisations are working hard to take the benefits of the new promised land, called Industry 4.0. Leaders are starting to have success, laggers have not at all started to consider it.
A large segment in the middle are struggling with their first prototypes, and taking some expensive learnings. This presentation is giving a view on current status, and suggesting a checklist on how to succeed, with a strong focus on the people and culture side of implementations.
Even if I am a one-man company, I can always find a partner, that can answer your questions.