Downloaded 15 times
Why Integrate using an API? | MuleSoft
- 1. Kiet Bui Implementing Mulesoft aspart of corporate and IT transformation
- 2. Agenda Batory Foods Introduction IT Evolution MuleProject Moving Forwards Strategic Direction
- 3. Batory Foods Introduction AnOverview • Batory Foods is a family owned national ingredient distributor founded in 1979 and based out of Chicago. • Our business is providing a broad range of high-quality ingredients to food and beverage manufacturers across the United States. • 50+ account managers in the field servicing our customers. • 450+ vendor-relationships, access to thousands of ingredients. • 200+ support staff across the country. • Over 10,000 customers in various markets. • Bakery • Beverage • Candy and Confectionary • Dairy • Health and Nutrition
- 4.
- 5. Batory Foods Introduction AChanging Business 5 • Entrepreneurial Agile Business Model • Very focused on customer service • Acquisitions • Continuing to grow by acquisition • Value Added Services • Liquid and Dry Ingredient Blending • Sugar Powdering and Browning • Custom Packaging and Labelling • Adding New Services • Warehouse and Storage • Manufacturers Representative and Distributer • Tailored Ingredient Distribution • Custom and Hybrid Models
- 6. Strategic Direction Corporate StrategicReview Four Pillars Responsiveness Communication Standardization Training Supporting Automation Accountability Vision 2020 Recommendations Increase Visibility Implement New ERP Restructure Inventory Planning Customer Portal Segmentation
- 7. Batory Strategic Direction SelectedInformation Technology Initiatives Implementation of Transportation Management System Implementation of Supply Chain Planning Applications Implementation of Billing Management Application Upgrade of ECM New ERP Development and Implementation of New Customer Portal
- 8. Information Technology Evolution CurrentState of Application Portfolio ERP Enterprise Resource Planning Enterprise Content Management Warehouse Management System Customer Portal
- 9. Information Technology Evolution ApplicationPortfolio Future State Warehouse Management System ECM Transportation Management System Cloud Based Document Sharing Customer Portal Hosted ERP ERP Signature Capture Billing Management Inventory Planning System C(X)RM
- 10. Information Technology Evolution PartnerCollaboration Warehouse Management System Enterprise Content Management Transportation Management System Cloud Based Document SharingCustomer Portal Hosted Enterprise Resource Planning ERP Signature Capture Billing Management Inventory Planning System Warehousing Customers Suppliers Carriers 3PL Warehouse Operators Distribution Customers
- 11. Batory’s First MuleProject – TMS Integration Requirements Requirements Solution to support cloud and on premise Support internal application and partner integration Do not want to add developer skills to IT Department Have no time to develop skills Agile Model – Grow and shrink skills as needed Need 24 hour support Solution Selected Mulesoft Selected Cognizant as Mulesoft partner Managed Service for ongoing support of environment Resources for capital projects Mulesoft Agreement – 24 hour support Mulesoft provided advisory and audit role throughout the project
- 12. Batory’s First MuleProject Project Deliverables Transportation Management System Warehouse Management System ERP Enterprise Resource Planning Purchase Orders Warehouse Sales Orders Warehouse Transfers Direct Sales Orders WMS Qty Updates Order Plan Settlement Details Payment Connectors Used SFTP Database Connector REST Web Services SOAP Web Services
- 13. Batory’s First MuleProject Timeline 5/1 8/15 Design Mule Review Proof of Concept Development Second Mule Checkpoint LiveUser Testing Go Live
- 14. Batory’s First MuleProject Project Outcome Project Outcome TMS Application Implemented GP and WMS Integrated with the TMS Mule Environment easily met the performance requirements Business Outcome More Efficient and Reliable Transportation Processes More Efficient and Reliable Accounts Payable Processes Mule Environment easily met the performance requirements Improved visibility for customer service and sales Gathering accurate transport data
- 15. Batory’s First MuleProject Lessons Learned Lessons Learned Complexity of Flows – Increase the number of flows Complexity of Flows – Remove business logic introduce a Business Rules Engine Error Reporting and Recoverability – User oriented e-mails
- 16. Moving Forwards The next12 Months • Upgrade to 3.7 • Business Rules Engine Refactor
- 17. • Upgrade to 3.7 •Business Rules Engine Refactor • All WMS Integrations WMS Moving Forwards The next 12 Months
- 18. • Upgrade to 3.7 •Business Rules Engine Refactor • All WMS Integrations WMS • Upgrade • Replace Point to Point ECM Moving Forwards The next 12 Months
- 19. • Upgrade to 3.7 •Business Rules Engine Refactor • All WMS Integrations WMS • Upgrade • Replace PtoP ECM • Integration to Customers ERP • B2B Whse Cust Moving Forwards The next 12 Months
- 20. • Upgrade to 3.7 •Business Rules Engine Refactor • All WMS Integrations WMS • Upgrade • Replace PtoP ECM • Integration to Customers ERP • B2B Whse Cust • Implement SC Planning Applications Supply Chain Moving Forwards The next 12 Months
- 21. • Upgrade to 3.7 •Business Rules Engine Refactor • All WMS Integrations WMS • Upgrade • Replace PtoP ECM • Integration to Customers ERP • B2B Whse Cust • Implement SC Planning Ap Supply Chain • New ERP • All integrations ERP Moving Forwards The next 12 Months
- 22. • Upgrade to 3.7 •Business Rules Engine Refactor • All WMS Integrations WMS • Upgrade • Replace PtoP ECM • Integration to Customers ERP • B2B Whse Cust • Implement SC Planning App Supply Chain • New ERP • All integrations ERP • New customer portal Portal Moving Forwards The next 12 Months
- 23. Moving Forwards Options Beyond2016 • Partner Portal • Increased use of different cloud based solutions • Increased automation between Batory and Supply Chain Partners • Demand Planning • Inventory Visibility • Add real value to sales process and customer relationship by the use of technology • Leading with the • Vendor Managed Inventory • Even closer integration, use of Internet of Things technology • Changing models requiring different types of integration 23
- 24. Create Change Order CreateChange Order Create Change OrderCreate / Change Order BR API BR API PROCESS Get SO Get SO Get SO Send SO Get Payable Send Pay Great Plains ERP Get SO Get SO Get SO Get SO Inv Upd Ship Manhattan Scale WMS Partner APIs Partner Applications Get SO Get SO Get SO Get SO Send Sch Send Payable Lean Logistics TMS Scale WMS ERP TMS EDI API EDI API Batory Applications SERVICEAPPLICATION Cloud Applications WMS Business Processes Data Business Rules Carrier Payment Ship Order Ship Order EDI TPM B2B Connect API API ECM ERP
- 25.