Thinus van Schoor

1
SABMiller and OMAC

• Presented by
• Thinus van Schoor
• Automation Manager
• thinus.vanschoor_at_sabreweries.com

OMAC Presentation 13 February 2003
2
Company Background

• On 9 July 2002, Miller Brewing Company became a
  wholly owned subsidiary of South African
  Breweries plc and SAB was renamed SABMiller plc
• SABMiller plc is the world's second largest
  brewer - volumes in excess of 120 million
  hectolitres
• SABMiller plc owns and operates 112 brewing
  operations and over 69,000 employees, in 24
  countries across Africa, Central and Eastern
  Europe, North and Central America and Asia.
• SABMiller is the world's largest bottler and
  distributor of Coca-Cola products outside the U.S.

3
Business Context
What is needed to compete in diverse FMCG
markets Product quality a non
negotiable Product consistency - sustained
growth Production efficiency - bottom
line Capacity utilization - return on
investment Plant availability - meeting demanded
schedule Production flexibility - responsiveness
to change New product deployment time to market
In short gt the optimum level of flexibility and
speed to fit the geographical market
FMCG Fast Moving Consumer Goods
4
Challenges we face

• A diverse spread of manufacturing operations and
  market demands
• Breweries are categorized as Emerging,
  Established, Developed and Advanced
• Varying existing degrees of automation
• Huge diversity of control system hardware
  platforms and software environments
• Packaging largely islands of automation
• High cost of reconfiguring OEM offerings
• OEM standards versus end user standards
• Difficult to integrate and maintain

5
Brewery Classification
6
Whats needed
Solutions need to supportoperational excellence
and market demands(Flexible Scalable)

• Key needs from future solutions
• Flexible - adaptable re-configurable
• Ease of maintenance
• -gt supporting lean manufacturing
• Reuse of engineering
• Scalable offer logical migration path
• Lower cost of ownership

7
fromLine Type 1No inter-machine communication
OMAC PackML Line Types
Queue Full Sensor
Queue Empty Sensor
Conveyor Running/Stopped
8
toLine Type 4 with connection to plant
business systems
OMAC PackML Line Types
Plant Business Systems
Line Network(s) - Field Bus, Cell Bus, Motion Bus
etc.
Unscramble
Unscramble
SCADA Server
Supervisory Controller
Label
Palletise
Carton
Fill
Cap
9
Line Types Scalability
Characteristics
Solution
Line Type
Strategy
Requirements
Stand alone
Motion control per machine
Machines not linked Own sensors and control May
have own operator interface
OEM alliance Software standards
A
Communicate via conventional I/O. Exchange of key
signals and information.
Interface standards Networks
B1
Hardwired
Linked Control
B2
Data exchange
Field bus
Communicate via network technology
Field bus Standards
HMI and Software Standards
Networked operator stations Common supervisory
system for line monitoring
Common Operator Interface
Line visibility
C
Integrated into plant information
system Reporting of line measures Quality
management
Naming standards Data structures Common
Architecture
Line optimization
Reporting And MES
D
Note Line classifications A,B1 ..directly
relates to OMAC type 1,2a..
10
Painting the As Is picture
11
OMAC Leverage for SABMiller
Solution
Line Type
Requirements
OMAC Workgroups
PackSoft
Stand alone
Motion control per machine
A
PackML
B1
Hardwired
Linked Control
PackConnect
B2
Data exchange
Field bus
PackML
Common Operator Interface
PackML
Line visibility
C
PackHMI??
PackML
Line optimization
Reporting And MES
D
PackAdv
12
Expectations of OMAC

• User driven with vendor alliance
• Common data models for discrete control arena
• Application of S88 principles in packaging
• Clear methodologies of scalable machine and line
  design
• Buy in of major vendors OEM and solution
  suppliers
• Lower cost of ownership of packaging lines
• AND more working examples!

13
Thank You!