1 / 22

Beyond Planning – Moving to full closed loop execution

Beyond Planning – Moving to full closed loop execution. Kris Reid, director, professional services Paul Rachniowski, director , research and development. Agenda. Why consider closing the loop? What type of things do people close the loop on? What are the technology options? Demo

hamish
Download Presentation

Beyond Planning – Moving to full closed loop execution

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Beyond Planning – Moving to full closed loop execution Kris Reid, director, professional services Paul Rachniowski, director, research and development

  2. Agenda • Why consider closing the loop? • What type of things do people close the loop on? • What are the technology options? • Demo • Q&A (time permitting)

  3. Why Close the Loop? • RapidResponse provides a rich interface for simulation and decision making • Reduce time to execute on “plan” • Use features and advanced analytics that don’t exist in ERP • Interface information with other enterprise systems • Collaborate with your Customers/Suppliers – B2B • Before you get started…..Really understand what changes users have to frequently make in RapidResponse and then in the ERP system – these are good candidates for closing the loop.

  4. What Do People Often Close the Loop on? • Master Data • Safety Stock • Min/Max/Multiple • Planner and Buyer information • Demand Changes • Order Promise / Available dates • Forecast / Consensus Demand Plan for S&OP • Supply Changes • Master Schedule • WO / PO creation, date and quantity changes • Firming Planned Orders • Inventory Transfers • Advanced Analytic results • Substitution • Constraint • Order Priority

  5. What Are My Options? • Inbound and outbound options utilized depend on: • Frequency at which data will be updated • Volume of data which will be presented • Type of data interface – full or change

  6. What Are My Options? • Other Considerations: • If using Net Change Data Update….Transactional data needs to be updated together (Demand/Inventory/Supply) • What can your source or destination system handle / provide – full data or change data • Scenario structure – change approval, automatic updating • Post processing needs – Scheduled Tasks, Alerts, Scripting • Map out the use case including points of data edit and timing

  7. What Are My Options? Example 1 – Requirement = Update full data daily into RapidResponse and send all planned orders from RapidResponse to ERP once a day • Low frequency, high volume • INBOUND: • Most commonly used interface - Full Data, extracts via ERP Adaptor / SFTP / Data Update • OUTBOUND: • Export files to a drive location using an Alert • Utilize SFTP to transmit back to customer network • Custom App or Middleware to write the data into ERP 1 2

  8. Example 1 Customer Network Kinaxis Data Center Secure FTP (DTC) 2d 2e 2c Secure FTP (DTC) Custom App / Middleware 2b Alerts Scheduled Tasks Scripting 1b 1c Internet 2f ExecuteScript WebServices ERP Adaptor Data Update UploadExtract GetDataUpdateStatus ERP 1d TriggerDataUpdate CaptureDataChanges 1a GetCapturedChanges GetWorksheetChangedData CDC Instance / Workbook ClearCaptureChanges GetWorkbookData 2a 1e GetWorksheetData ExportWorkbookData Workbook ImportWorkbookData RapidResponse DB Web Services Application

  9. What Are My Options? Example 2 – Requirement = Update full Master Data in RapidResponse daily, Transactional Data every 30 mins, Send PO Changes between RapidResponse and ERP every 30 mins • Master data inbound = Low frequency, high volume • Transactional data inbound = High frequency, low volume • INBOUND OPTION : • ERP Adaptor / SFTP / Data Update • Master Data – Full data update daily • Transactional Data - Net change data update • INBOUND OPTION : • Web Services / Data Update • File size limit = 50MB compressed • UploadExtract – Command uploads the data to be included in the data update (returns key) • GetDataUpdateStatus – Use key to determine status of data update (returns code = completion status) • GetWorkbookData – Can be used to retrieve record level logging of success/failure from a workbook 1 2

  10. Example 2 - Inbound Diagram Customer Network Kinaxis Data Center Secure FTP (DTC) Secure FTP (DTC) Custom App / Middleware Alerts Scheduled Tasks Scripting 1c 1b Internet ExecuteScript 1d Web Services ERP Adaptor Data Update UploadExtract GetDataUpdateStatus ERP TriggerDataUpdate 2d 2c CaptureDataChanges 1a GetCapturedChanges GetWorksheetChangedData CDC Instance / Workbook ClearCaptureChanges GetWorkbookData 2e 1e GetWorksheetData 2a ExportWorkbookData Workbook ImportWorkbookData 2b RapidResponse DB Web Services Application

  11. What Are My Options? • When using Net Change inbound: • Can leverages existing Data Source Mappings • When providing Net Change data, file names must include “partial” or “delete” attribute • Full Data data file name = Onhand.tab • Net Change data file name (Inserts & Modifies) = Onhand.partial.tab • Net Change data file name (Deletes) = Onhand.delete.tab • Extract folders(full and net change) must have timestamp suffix (for sequenced processing) • Old File Structure • New File Structure

  12. What Are My Options? • When using Net Change inbound: • Can only be used for tables with key uniqueness • Can only be used for text files, Excel files not supported • Transactional data updated together • Recommended that on some frequency (daily or weekly) a Full Data Update performed – resolve any Net Change failures

  13. What Are My Options? Example 2 - Requirement = Update full Master Data in RapidResponse daily, Transactional Data every 30 mins, Send PO Changes between RapidResponse and ERP every 30 mins • Change data outbound = High frequency, low volume • OUTBOUND OPTION : • Use Change Data Capture (CDC) through Web Services • Use if desire is to capturing user initiated changes • OUTBOUND OPTION : • Use ExportWorksheetData / GetWorkbookData / GetWorksheetData commands through Web Services • Since we want change data you would have to create a workbook that compares 2 scenarios to calculate changes • For this reason, OPTION 2 is probably not the most efficient choice for this particular use case as CDC handles the capturing of changes with less effort to configure 1 2

  14. Configuring CDC a) Create Web Services User b) Create CDC Instance c) Create / Test a CDC Workbook and share Workbook, Scenario, Filter with Web Service User d) Develop and Test a Web Services Application to access CDC Workbook via CDC Instance….

  15. Example 2 - Outbound Diagram Customer Network Kinaxis Data Center Secure FTP (DTC) Secure FTP (DTC) Custom App / Middleware Alerts Scheduled Tasks Scripting Internet ExecuteScript Web Services ERP Adaptor Data Update UploadExtract GetDataUpdateStatus ERP TriggerDataUpdate CaptureDataChanges GetCapturedChanges 2e 1d 1c 1b CDC Instance \ Workbook ClearCaptureChanges 1d 1a GetWorksheetChangedData GetWorkbookData 1d 1d GetWorksheetData ExportWorkbookData Workbook 2a 2e ImportWorkbookData 2b 2c RapidResponse DB Web Services Application 2d 2e

  16. Optional Considerations • If you need to do “post processing”: • Data Update can trigger Alerts to output reports/data and ScheduledTasks to run Scripts or modify data • Updating or Committing to Scenario can also trigger Alerts/ScheduledTasks • Scripts can be run from Web Services Interface – ExecuteScript command • Scripts are useful where there are a series of dependent activities in sequence. i.e. create scenario, modify data, publish scenario, send message to users message center 1 2

  17. Scripting, Scheduled Tasks and Alerts Diagram Customer Network Kinaxis Data Center Secure FTP (DTC) Secure FTP (DTC) Custom App / Middleware Alerts Scheduled Tasks Scripting 2d 1d Internet 1b 1c ExecuteScript Web Services ERP Adaptor Data Update UploadExtract 2c GetDataUpdateStatus ERP 1a TriggerDataUpdate CaptureDataChanges GetCapturedChanges GetWorksheetChangedData CDC Instance / Workbook ClearCaptureChanges 1e GetWorkbookData 2e GetWorksheetData ExportWorkbookData Workbook 2a ImportWorkbookData 2b RapidResponse DB Web Services Application

  18. Demo • Use Case : • User firms RapidResponse Planned Orders into ScheduledReceipts (POs) • CDC captures changes • Web Services Application gets changed data and processes into ERP • Net Change Data Update via Web Services – New ERP POs imported into RapidResponse with proper ERP Order IDs • Scheduled Task or Command identifies duplicate records (ones with RapidResponse Order ID and ERP Order ID and deletes RapidResponse record) 1 2 3 4 5

  19. Closed Loop Example Diagram Customer Network Kinaxis Data Center 5 Secure FTP (DTC) Secure FTP (DTC) Custom App / Middleware Alerts Scheduled Tasks Scripting Internet ExecuteScript Web Services ERP Adaptor Data Update UploadExtract GetDataUpdateStatus ERP TriggerDataUpdate 4d 4e CaptureDataChanges GetCapturedChanges 3d 4b GetWorksheetChangedData 2 CDC Instance / Workbook ClearCaptureChanges 3c GetWorkbookData 3a 3b GetWorksheetData 1 4a ExportWorkbookData Workbook 4c ImportWorkbookData 4c RapidResponse DB Web Services Application

  20. Thank You!

More Related