PPG-ORACLE TRANSPORTATION MANAGEMENT Implementing Multiple Sites – Single Domain Vs Sub-Domains 1
About PPG • Founded in 1883 as Pittsburgh Plate Glass by Captain John B. Ford and John Pitcairn in Pittsburgh, Pennsylvania. • Today, PPG is a global supplier of paints, coatings, optical products, specialty materials, glass and fiber glass. • Through leadership in innovation, sustainability and color, PPG helps customers in industrial, transportation, consumer products, and construction markets and aftermarkets to enhance more surfaces in more ways than does any other company • Total Net Sales 2014: $15.4 Billion PPG is ranked 190 on the Fortune • Worldwide: 156 manufacturing facilities* United States: 45 sites (19 states) § Other Americas: 14 sites (10 countries) § EMEA: 64 sites (29 countries) § Asia Pacific: 33 sites (12 countries § • More than $5.53 million invested in PPG communities in 2014 through grant making 2
Current OTM Implementation • OTM – Transportation tool for US and Europe • All types of movements – LTL, FTL, Ocean • One Domain per Region § PPGNA & § PPGEU • Estimated number of EU sites 40 to be implemented over 2-3 years • Two ERP s - SAP and Oracle EBS • Site based ERP customisation being carried forward • Site based Shipping practices 3
PPG European Divisions – Org Chart PPG EU Architectural Marine Automotive Packaging Aerospace Refinishing Industrial Coatings Coatings Location 1 to Location 1 to Location 1 to Location 1 to Location 1 to Location 1 to Location 1 Location 2 Location n Location 1 Location 2 Location n n n n n n n 4
Site Level Requirements • Each site manage their own transport • This leads to site level requirements in § Planning § Notification to Involved Parties § Tender to Carriers § Transport Documentation in ERP § Hazardous Goods data being shared with carriers § Workflow logic split per site § Updates from ERP system § Updates from Internal and External Warehouse systems 5
PPG EU OTM Implementation – Story So Far • Live Sites § 10 sites • ERP (SAP) Interfaces § Orders Creation/Updates from SAP § Shipment Creation/Updates to SAP § Shipment Group Creation/Updates to SAP § Invoices to SAP • EDI Messaging to Carriers (All using EDIFACT via Seeburger) § Tender Messages § Tender response § Proof of Delivery § Invoicing • Carrier On-Boarding § 117 Carriers on-boarded § 14 Carriers on Self-billing with OTM issuing the credit notes 6
OTM Configuration Aspects – All in One • Planning § One site wants to honour ship date, other site delivery and some others no date at all § When user takes action, it is easy to use Planning parameter in preference § When integration action happens (update from ERP), domain default PPS is used § This leads to constant adjustment to tackle all scenarios • Notifications (Carriers & Involved Parties) § Some sites require certain type of shipments to be auto tendered and others not § Leads to endless IF/ELSE blocks in Agents 7
OTM Configuration Aspects – All in One – Contd … • Workflow § Finally, all these have to be handled in workflow with if/else § Agents have to be unnecessarily triggered even if they use saved condition at the trigger stage itself § Some others are so complex that reentrancy cannot be avoided 8
Sub Domain Proposal – 3 Tier PPG EU Architectural Marine Automotive Packaging Aerospace Refinishing Industrial Coatings Coatings Location 1 Location n Location 1 Location 2 Location 3 Location 1 Location 2 9
Sub Domain Proposal – 2 Tier PPG EU Architectural Marine Automotive Aerospace Refinishing Industrial Coatings Coatings 10
Sub-domain per Site/Division – Advantages • Planning parameter set up per site gives great flexibility to cater for site specific planning needs • Workflow parameters (heavily used in tendering set up) will also be set per site/sub-domain giving great flexibility in handling different tendering requirements • Reduces complexity/logical steps – Overall performance gain • Generic items such as users, screens and even agents can stay in PPGEU domain • User Roles to be created on the sub-domain • For movements across divisions, users can be assigned role at parent domain • Some logic can be set at middleware with help of lookup types and avoid workflow logic 11
Sub-domain per Site/Division – Disadvantages • Complex Setup • Concerns about cross domain consolidation (For panel to discuss) § There is a future need where orders from different sites/divisions may need to be combined to achieve cost saving § This may be done using a control tower concept § Having orders in different sub-domains may prevent this consolidation § Duplication of effort in workflow configuration for sites that do not have synergy in requirements • Impact § Re-arrange mapping changes in Middleware § Impact on SAP or carrier systems needs to be studied 12
PPG CCB - Concerns on Sub Domain Concept • Concerns about cross domain consolidation (For panel to discuss) § There is a future need where orders from different sites/divisions may need to be combined to achieve cost saving § This may be done using a control tower concept § Having orders in different sub-domains may prevent this consolidation (Challenging this thought process) § Duplication of effort in workflow configuration for sites that do not have synergy in requirements 13
Panel Recommendations • Panel Recommendations § Will Oracle recommend or endorse having 40 sub-domains in a setup? § Has anyone in the panel implemented the sub-domain concept and if so, what is your experience in terms of performance § One of the main objectives of a sub-domain is to gain control over planning set up. Alternatives to sub-domain w.r.t. planning parameter set? 14
Questions/Discussion 15
Recommend
More recommend
