1. System Platform - building re-usable Standards Presenter: Dries van Schalkwyk Control Systems Integration

2. Agenda IntroductionIntroduction Definition of Standards Why Develop Standards? ConsiderationsConsiderations Lessons Learnt & Summary How do we do it?

3. Introduction ▪ Control Systems Integration ▪ Standards Development – Key in CSI ▪ Standards Developed Exxaro Sublime Technologies Mittal Kumba Iron Ore Others ▪ Standards Used SAB Miller Nestle Others

4. Agenda IntroductionIntroduction Definition of Standards Why Develop Standards? ConsiderationsConsiderations Lessons Learnt & Summary How do we do it?

5. Definition of “Standards” ▪ Pre-developed PLC, SCADA, A2 Code ▪ Bottoms Up Approach Schematics -> PLC Code -> A2 Obj Models -> SCADA Linked to Equipment Types (incl Brands) ▪ Documented ▪ Starter Pack Schematics, PLC Code, ArchestrA objects, SCADA graphics of various objects Documentation

6. Agenda IntroductionIntroduction Definition of Standards Why Develop Standards? ConsiderationsConsiderations Lessons Learnt & Summary How do we do it?

7. Why develop standards? ▪ Client – Reduced TCO! Save on Engineering Cost(New Projects & Expansions) e.g 41% saving Reduced Commissioning Time

8. Why develop standards? ▪ Client – Reduced TCO! Ease of Maintenance Lower Training Cost Centralised Enterprise SOP ▪ Reduced Risk

9. Why develop standards? ▪ The value to the SI Control over automation principles Competitive Advantage with customer Relationship with customer – Trusted Advisor Paid Services for SI Customer Commitment Save on Engineering – Time = Money e.g 41% saving Better planning and estimation = On-Time Delivery Automation of activities, e.g. Macros Risk Mitigation

10. Agenda IntroductionIntroduction Definition of Standards Why Develop Standards? ConsiderationsConsiderations Lessons Learnt & Summary How do we do it?

11. Approach to Develop Standards ▪ Project Approach Identify Scope (Equipment models) Schedule – Project Plan (1-3W/obj) Budget Strong Quality Control ▪ Strong PM ▪ Client involved – Joint Team ▪ Detailed documentation ▪ Wonderware SA involved Advice Best Practices Document

12. How do we do it? ▪ Get Corporate buy-in ▪ Think Wide ▪ Technical Skills ▪ Training ▪ Team approach SI/Customer ▪ Keep things Simple ▪ Simple to Complex derivations ▪ Group head offices & IT Antivirus Patch Management, service packs, Security, disaster recovery, group policies

13. Agenda IntroductionIntroduction Definition of Standards Why Develop Standards? ConsiderationsConsiderations Lessons Learnt & Summary How do we do it?

14. Other considerations ▪ Risk to the SI! ▪ Standards = Foundation of Projects ▪ Stds must be easy to Rollback Download PLC Code, A2 objects, SCADA Commission ▪ Standards ownership – not SI IP ▪ Size of Customer

15. Agenda IntroductionIntroduction Definition of Standards Why Develop Standards? ConsiderationsConsiderations Lessons Learnt & Summary How do we do it?

16. Lessons Learnt ▪ Right Resources (SI & Customer) ▪ Bench Test Thoroughly Comms Turnaround Time Scalability Cycle Times Test against H/W ▪ Highly Detailed FAT ▪ Take no shortcuts ▪ Enforcement Body at End user ▪ Change Control ▪ Hierarchical derivations ▪ Wonderware Audits

17. Conclusion ► You MUST Standardise ► It saves $$$$ for SI and Customer ► It helps in building relationships

18. Conclusion ► Questions???

19. Graphics Library