• Like
Demantra Case Study Doug
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

Demantra Case Study Doug

  • 10,220 views
Published

Case Study presentation on Demantra Implementation

Case Study presentation on Demantra Implementation

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
10,220
On SlideShare
0
From Embeds
0
Number of Embeds
1

Actions

Shares
Downloads
240
Comments
0
Likes
3

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • This case study describes the implementation of Demantra Demand Management solution as a replacement to a highly customized, end-of-life legacy forecasting tool. This project enabled an integrated Supply Chain Planning environment, reduce manual processes & increase forecast accuracy I am going to share the implementation details and lessons learned from this project The key takeaway is that you can draw on our real-world experience during this project to help support similar needs.
  • Sunday Ichie: Currently leading the Oracle Applications DBA Team in Education Technology (Ed Tech) at Texas Instruments. 15 years experience in the Information Technology industry including 12+years as an Oracle Applications DBA. I has served as technical lead and project manager on several recent implementations including: Oracle's Real Application Clusters (RAC), Oracle Demantra, Oracle GRC and Oracle 11i Upgrade.
  • Texas Instruments (NYSE: TXN) is an American company known best for its semiconductors and graphing calculators.
  • Education Technology division (Ed Tech) Manufacture products focused on bridging the gap between education and technology. Texas Instruments handheld calculators are segmented into Graphic, Scientific and Business calculators
  • Industry Segment = Education / Consumer Electronics
  • Three primary suppliers (Far East) Manufacturers –out sourced to china Distribution Centers in US, Singapore, Australia, Netherlands, Fort Worth, TX Customers base includes Major Retail chains and Educational Distributors Primary Supplier Schedule for 300 Item/Supplier Finished Goods combinations
  • We have a very seasonal business (back-to-school) with relatively long lead times on manufactured items which are out sourced from China. Forecast are provided at calculator level which may be BOM component level due to customers ordering special pack displays (containing many different types of calculators) Data is collected daily from applications in data collection process and fed into ASCP. Output is pushed back to MRP and supplier schedules (part customizations) are generated for suppliers every two weeks. 6 Weeks lock on Suppliers Schedules 5 Weeks standard transit time (Supplier to warehouse)
  • Manufacturing (Discrete) Financials Unconstraint ASCP Plan
  • 3 base tool; 25 web based access Supply Chain Planning & Optimization (SCPO) Application. (not used) Demand Planning Extended Edition (DPEE) Application Manugistics Collaborative Forecast engine run time is 8hrs
  • Client Server Technology (Year 2000 Version 6.1.4) Application specific modules –Demand, Fulfillment, Collaborate Legacy tool had evolved to mixed use Supply Planning product forecast (> Lead time) Finance/Sales Revenue reporting (< lead time) Primarily used sales input modified via consensus S&OP process
  • E2E= End to End
  • Client/Server Architecture The Manugistics application is split into client and server. The application server executes all of the data management, aggregations, calculations (number crunching), database interfacing and other related functions. The application client and server is connected via Manugistics (OSF compliant) custom RPCs. The application server and database connection is implemented via Oracle’s SQL*Net using a custom vendor provided odbc. Supply Chain Planning and Optimization (SCPO) Demand Planning/Extended Edition (DP/EE) Collaborative Services DCE (Distributed Computing Environment) Transarc DCE V2.0 Client (Base Services) V2.0 Microsoft Data Access Components (MDAC)Version 2.1
  • Lack of visibility across channels. Customer, geography plans Custom integration using 30+ Concurrent Requests (DW Loads / Oracle extracts in monthly process) Manual work around for sales and channel plans to operations execution taking too long Little belief in capacity to drive improvement using the existing tools and processes
  • Business Needs Eclipsed Legacy Forecasting Solution Conclusion: “Serious business problem in need of an enterprise solution!” Importance of Sales & Production Forecast is Paramount Accuracy of forecast directly impacts inventory & labor resource operating budget customer service & satisfaction
  • The executive team could not accept the increasing risk of a forecast process breakdown, so a decision was made to take action.”
  • Conducted research and analysis to determine appropriate vendors. Involved Gartner analysis, whitepaper research, and Internet research. Use of the magic quadrant to select vendors based on criteria and objectives of the company. 3 vendors chosen which met the most criteria points.
  • RFP=Requests for Proposals Finalized complete list, combining both recommended vendors as well as “best of breed” vendors based on independent research
  • With thorough evaluation criteria defined up front, the project team was able to objectively evaluate and score 3 vendors of relevant application packages. Demantra right away was the front runner
  • Demantra had matured processes and was deemed most likely to allow incremental improvement.
  • Distributed RFP with guidelines (Request for Proposal)
  • The project was crucial and time-sensitive. With the planning organization, we had to carefully assess the impact of the change and manage user expectations. There was great attachment to the existing software and a brute-force replacement would doom our chances of successful user adoption
  • Break Implementation into 5 simple steps Evaluation of your situation and reasons for project Planning out your implementation – scope and approach, timeline and timeframe Prepare – change management, team structure, project plan Execute - easy because you’ve done all the hard work up front Maintain – document and train
  • Evaluation of your situation and reasons for Project
  • ASCP – minor changes associated with install of current (patch level) release provides few changes to ASCP users and little risk with regard to their use. Were Oracle to fail to deliver on their scheduled delivery of ASCP 11.5.10 with Demantra 7.2, then additional coding would be required for the Demantra Phase 1 project.
  • What is Demantra?
  • Demantra Application Platform consists of the following elements:
  • Planning out your upgrade – scope and approach, timeline and timeframe
  • Combine ASCP Upgrade and Demantra implementation (Project execution) Demantra will not be installed in any Dev, Test or PreProd instance until the successful completion of ASCP testing in that instance. Key Questions: How customized is the environment How much have the organization structure changed What fundamental changes to the configuration is needed How clean is the data Performed assessment to determine right approach.
  • What does the license cover? Demantra Analytical engine (windows server)     Review other Configuration variations possible (Citrix cluster, Distributed Deployment) Timing your Sizing activity and getting it right is key. Demantra sizing tool was used to gather requirements for estimating hardware resources to run Oracle Demantra and ASCP Hardware sizing was based on the "rough cut" recommendation provided by Oracle. Leveraged implementation partner in sizing. Start upfront in the sales cycle to help in making investment decisions using a ballpark estimate
  • Current selection of ASCP 11.5.10 on new environment is based upon Demantra Phase 1 Charter assumptions that Demantra 7.2 functionality will be available to 11.5.10 by May 2008. Collections. Provides ability to collect data from the Source (Oracle EBS or other Transaction Systems) .
  • No MSC table structure changes were identified in the review of patch set, the implementation of the latest patch set of 11.5.10 should have no impact to DataWarehouse integration.
  • Oracle integration for 11.5.10 was evolving during project start. As of Kick off in April 2008, Oracle integration for S&OP lagged and was not delivered on time Also, the standard collection process that is used to collect the Sales Order history had limitations. To address these gaps, we built interfaces between Oracle EBS, ASCP, Data Warehouse.
  • Prepare – change management, team structure, project plan
  • Oracle has nicely gathered all the user guides and implementation guides related to ASCP Demantra at one place. Look in the Product Specific Documentation Library . Another important document, which can be a good starting platform for learning is "Oracle Demantra 7.1 Foundation Implementation Guide", which can be found under header of 7.1 release Demantra SIG: Demantra SIG is a part of Oracle's OAUG and has been delivering various knowledge sharing sessions and conferences on regular basis. You can find interesting documents, case studies, and some advanced Demantra documentation at Demantra's SIG group website. http://demantrasig.oaug.org/knowledgebase.php?page=knowledgebase The Library contains all the versions starting from latest Demantra 7.2.1 to older ones like Demantra 5.2. Few of the old basic Demantra documentations are available under 7.0.1 release header:
  • KED BRD=Business Requirement Document FRD=Functional Requirement Document
  • Execute - easy because you’ve done all the hard work up front
  • Provide a pictorial view of the architecture of this application, including interfaces to other systems. Include details such as type of machine, model, #CPUs, Memory size, disk size, DNS Name, etc. Include details of interfaces to other systems The above style of diagram is one that tends to work well in ITR reviews. Work with your Server Capacity/Performance Core Team member to calculate the Operations Support and hardware charges for this project. Include slide in ITR 1, 2, 3 presentations
  • 4. Relink MSC,MRP module from adadmin on Target (ASCP) DB node. 5. Execute this request “Gather Schema Statistics” on Source (ERP) and Target (ASCP) node. 6. Set “MSC:Source Setup Required” to “Y” in Target (ASCP) System, set “N” in Source (ERP) System. 7. Run “Refresh Collection Snapshots” from Source (ERP) instance.
  • Download Demantra Installation patch 5985614. We created a folder D:Demantra72. Associate EBS.APS User to Demantra Responsibilities
  • Decentralized Architecture.
  • MSD_DEM: Two-Level Planning #This profile enables demand forecasts at the Product Family level on the basis of sales histories of member items. Exclude family members with forecast control 'None'. MSD_DEM: Currency Code #This profile designates the Demand Management base currency. MSD_DEM: Data Profile for Price Lists Set this profile to import integration data profile for price lists. MSD_DEM: Debug Mode #When set to 'Yes', this profile is used to print debug information to the output file of the concurrent request. MSD_DEM: Host URL Set this profile to the Oracle Demantra #Application Server Host Name, Port Number and Application Name. This profile is used to invoke Oracle Demantra URLs from the E-Business Suite applications. MSD_DEM: Schema Set this profile value to the database schema name where the Oracle Demantra schema has been installed.
  • Standard collection for Calendars, (Price Lists, New Products) When an E-Business Suite user is granted any responsibility containing the Demand Management Workbench an Oracle Demantra user of the same username is created in the Oracle Demantra Demand Management component. Users assigned E-Business Suite Demand Management System Administrator or Demand Analyst responsibilities are automatically assigned mirrored responsibilities in Oracle Demantra. When a user is created in the E-Business Suite and mirrored in Oracle Demantra, the default password in Oracle Demantra is 'Oracle Demantra'. The Web Server must be restarted for a new user to be available in Oracle Demantra."
  • • Plan on doing 2-3 test-runs before upgrading the production environment • Backup the environment at different stages to ensure all the work is not lost if there are some issues in a specific step/phase • The first test-run takes the maximum amount of time because various issues with the database, applications customizations, etc. will surface. The focus of the first test run should be to complete the upgrade successfully and document all the issues and fixes. • Start timing the different upgrade phases in the second test-run to identify the most time consuming tasks
  • Maintain – document and train
  • Develop a strategy to partition these tables, Consult the worksheet design team as this can impact their user experience as well. Have Auto extend turned on for them. Turn off the Redo logs for these tables
  • Started with a legacy forecasting Manugistics tool which was old, obsolete, and running on an unsupported hardware & software. Also, An APS (ASCP) environment that was near end of life. ended up with a fully integrated Supply Chain Planning environment that provide both Supply Chain and Demand Management functions
  • Improved ASCP Plan run time.
  • Also, we delivered the following benefits New supported hardware and software Updated APS technology We were able to complete platform change with little impact and then drive continued improvement
  • Reduce manual processes Increased forecast accuracy Enable a Phase 2 project to implement Demantra Real Time Sales & Operations Planning
  • Significant improvement in forecast accuracy (80% )
  • reduce out-of-stock occurrences to 3% or less.
  • Nspire product lunch
  • Integrated ASCP, e-biz and Demantra. Reduced customization
  • eTRM=Electronic Technical Reference Manual
  • Recap
  • Demantra takes a fair amount of support. This should be considered when calculating the on-going costs of the tool. Long-term success depends a good plan for post implementation support.

Transcript

  • 1. Presented by Sunday Ichie Implementing Demantra as a replacement to a legacy forecasting tool: A TI Success Story
  • 2. Agenda Introduction Business Environment Legacy System Background Business Case Implementation Experience Case Study Conclusions
  • 3. Agenda Introduction Business Environment Legacy System Background Business Case Implementation Experience Case Study Conclusions
  • 4.  
  • 5. Introducing Education Technology (Ed Tech division)
    • Revenue $500+M
    • Product lines:
        • Calculators (graphic, scientific and business)
        • Classroom learning systems,
        • Data collection devices & computer software
    • World leader in products focused on bridging the gap between education and technology
    • Works with educators throughout the world in designing and developing technology for classrooms
    • A well-managed company and great place to work
  • 6. GraphLink 84+ 84+ SE 92 92+ V200 GraphLink 89T 89 83+ SE 83+ 83 86 85 80 82 81 CBL CBL 2 CBR 73 GraphLink 2 TI InterActive! TI Connect TI Connect TI-Navigator Viewscreen Viewscreen Viewscreen Viewscreen Product Lines TI-Presenter GraphLink 2 GraphLink GraphLink GraphLink GraphLink GraphLink GraphLink GraphLink GraphLink GraphLink GraphLink GraphLink GraphLink
  • 7. Agenda Introduction Business Environment Legacy System Background Business Case Implementation Experience Case Study Conclusions
  • 8. Supply Chain Operations Suppliers Three primary suppliers (Far East) Sourced from China 4 global distribution Centers Major Retail chains and Distributors Students, teachers, end users Manufacturers I N V E N T O R Y Distribution I N V E N T O R Y End Customers Channel I N V E N T O R Y I N V E N T O R Y
  • 9. Supply Chain Overview
    • Seasonal business (back-to-school)
    • Forecast at calculator level
    • Data collection fed into ASCP.
    • Output is pushed back to MRP (PO, WIP)
    • Supplier schedules generated for suppliers every two weeks.
    • Schedules are in 13 weekly buckets and 9 monthly buckets.
    • Suppliers commit to schedules and are manually input into Apps
    • Primary Supplier Schedule for 300 Item/Supplier Finished Goods combinations
    • Forecast at detail level (Item/Customer/Country) for 1300 Items, 1000 Customers and 23K combinations
  • 10. Planning Systems Summary
    • Where we were in 2008…
    • Full Oracle E-Business suite - Live since 1999 -Currently on 11.5.10.2
      • Modules = Financials, OM, MWA, many CRM modules
      • Oracle Planning (MRP) – 1999
    • Integration with ASCP 2003
    • Yantra WMS
    • Data Warehouse
    • Legacy Demand Planning: Manugistics -1999
  • 11. ERP Systems
    • Oracle ERP Applications (Oracle 11.5.10) Environment
      • Order Management
      • Oracle iStore
      • iPayment
      • Payables
      • Financials
      • Purchasing
      • Warehouse Management System
        • WMS (Europe)
      • Manufacturing
      • Oracle Mobile Web App (MWA)
      • Shipping and Logistics
        • Chainware
        • Loftware
        • Vendor Connect
    • Demand Planning: Manugistics
    • Oracle Planning: Oracle
    • Discoverer View and Plus (Reporting)
    • Data Warehouse (Reporting)
    • Oracle Single Sign-On (SSO)
  • 12. Agenda Introduction Business Environment Legacy System Background Business Case Implementation Experience Case Study Conclusions
  • 13. Legacy System
    • Manugistics NetWORKS Demand and Collaborate
    • (Scheduling and Demand loading)
    • Statistical forecast engine
    • Graphical and data table interface
    • One forecast in and one forecast out
    • Provides the ability to add an override at a higher level and allocate that override to the lower levels
    • 3 separate modules – equated to long batch processing and forecast load times
  • 14. Manugistics Functionality Operational Decisions (Daily/Hourly or shorter) Tactical Decisions (Monthly/Weekly) Order Commitment TM Strategic Decisions (Annually/Quarterly) Sales Planning Master Planning Supplier Planning Transportation Management Strategic Planning Detailed Scheduling Order Commitment
  • 15. Forecasting Process Flow
    • Manugistics
    • Data Warehouse
    • Oracle ASCP
    Sales & Marketing Inputs Reporting: Finance (Revenue, Margins, Costs…) SCP (Quantity, Dates) … ASCP: E2E Planning Reporting: Reviews & Consensus
  • 16. Manugistics Infrastructure –Hardware & Software Database Server Client RPCs Application Server Databases SQL*Net Sun Solaris 2.6 SCPO Server V6.02 Oracle RDBMS 8.0.6.0 Transarc DCE V2.0 NT Server 4.0 NetWORKS Collaborate v6.0.1 BEA WebLogic Server v4.0.3 Manugistics ODBC driver for Oracle 8 MS Windows DP/EE Client MDAC Version 2.1
  • 17. Manugistics System Support Lifecycle End of Support Life Near End of Support Life Business Application Application End of Life Operating System (OS) OS End of Life Hardware Hardware End of Life Manugistics Core De-Supported Solaris 2.6 De-Supported Sun Ultra-450 De-Supported Oracle RDBMS 8.0.6 De-Supported SCPO Server V6.02 De-Supported NetWORKS Collaborate v6.0.1 N/A Windows NT 4.0 De-Supported HP Server De-Supported Manugistics ODBC driver for Oracle 8 N/A Windows NT 4.0 De-Supported
  • 18. Challenges/ Opportunities Forecast accuracy and visibility Collaboration Lots of manual work Operational Support Vendor Support Integration Limitations Business Need No DR – poor business continuity provision Legacy system out-dated and not sustainable End-of-Life Manugistics software End-of-Life Sun Hardware End-of-Life Solaris OS No integration to APS No integration to ERP No support for sales and operations planning
  • 19. Agenda Introduction Business Environment Legacy System Background Business Case Implementation Experience Case Study Conclusions
  • 20. Business Case
    • Forecast Tools in Need of an Overhaul
      • Integrated Supply Chain Planning environment,
      • Forecast accuracy and out of stock occurrences
    • Key applications were in various states of disrepair, and the risk of affecting business had become very real.
    • Business faces a risk of the loss of Demand Planning capabilities due to multiple de-support scenarios.
    • Did not want to rely on EOL Legacy System to forecast $500 million of revenue?
    • The executive team could not accept the increasing risk of a forecast process breakdown, so a decision was made to take action.”
  • 21. Action Plan Run maintain readiness Manugistics Infrastructure Upgrade Demand Planning Discovery Demantra & ASCP Projects Proactive activities to ensure system availability: keeping the lights on Vendor Selection Planning Organization 2008 strategic Projects Infrastructure upgrade project POC Improve current operations Freeze development Minimize changes Explore feasibility of upgrading existing infrastructure: OS and database versions Define Selection Process
  • 22. Vendor Selection Process
    • Conducted vendor research
      • Internet
      • Whitepaper
      • Gartner (Best of Breed, Magic Quadrant)
      • Past relationships
      • Solicited peers
    Vendor Research Vendor List Engagement Evaluation Select Vendor
  • 23. Vendor Selection Process
    • Met with stakeholders
    • Engaged selected vendors
    • Requested RFP
    Vendor Research Vendor List Engagement Evaluation Select Vendor
  • 24. Vendor Selection Process Vendor Research Product Features Engagement Evaluation Select Vendor
  • 25. Vendor Selection Process
    • Executed vendor evaluations, based on the defined approach evaluation criteria, and scoring. Determined point totals and published final scores internally
    Vendor Research Vendor List Engagement Evaluation Select Vendor
  • 26. Vendor Selection Process
    • Selected vendor . Notified all other vendors of status. Made plans for the execution of the contract, pending reviews of terms and conditions
    Vendor Research Vendor List Engagement Evaluation Select Vendor
  • 27. Next Steps
    • Charter a Business Systems Project
    • Identify Business Sponsor
    • Set Measurable Objectives
    • Identify Implementation Partner
  • 28. CHALLENGES
    • Years of customizations had resulted in a complex platform, but one that was familiar and comfortable for its resident users. Manugistics ,while out of date and in danger of imminent failure, was getting the job done for the Planners
    • The biggest challenges associated with this project were user-focused. Convincing the Planners that replacement software was vital to the success of the company was the first hurdle, and introducing the selected solutions would require user preparation
    TI Confidential
  • 29. Project – Wish List
    • Provide the ability to load and archive a Salesman, Consensus, and Statistical forecast
    • Automated Copy History – update actual sales to particular SKU’s
    • Ability to allocate (dis-aggregation) the statistical forecast at a high level to a lower level using historical data, proportions, and other appropriate methods
    • Ability to generate and override multiple forecasts
    • Provides extensive report writing and graphing capabilities.
    • Reduction in batch processes and total run times
  • 30. Agenda Introduction Business Environment Legacy System Background Business Case Implementation Experience Case Study Conclusions
  • 31. Project Steps
  • 32. Upgrade Steps
  • 33. Evaluate Identify and Prioritize Project Drivers and Objectives
  • 34. Project Scope (ASCP)
    • Upgrade ASCP hardware environment to enable stable support for a combined ASCP and Demantra environment. The upgrade activity will bring the environment to the current (Solaris) Operating System and (Oracle ASCP) patch level
    • The Project end-state will be a combined Oracle ASCP/Oracle Demantra server configuration, enabling more native integration across modules and sharing Data Collection processes between the ASCP/Demantra and Oracle EBS environments
  • 35. Project Scope (Demantra): Phase I and II
    • Phase I: Replace Manugistics with Demantra as the global forecasting tool for ET Sales forecasting
    • Enable a more integrated Supply Chain Planning environment, reduce manual processes, increase forecast accuracy
    • Enable a Phase 2 project to implement Demantra Real Time Sales & Operations Planning (RTS&OP)
    • Phase II: Development processes, reports and the enabling of the Demantra RTS&OP module to create a robust real time Sales & Operations Planning process (RTS&OP):
      • Units and Dollars in one place – real time and interactive
      • Support multiple Forecasts, Forecast Revisions & historical Forecast Deltas
      • In short, the ability to see how we have done in the past (accuracy by units and dollars) and to factor current forecasts by historical patterns – in real time
  • 36. Evaluate
    • Demantra is a completely independent product from Oracle ERP
    • Oracle Demantra Platform of 6 Solutions
      • Demand Management
      • Advanced Forecasting and Demand Modeling
      • Real Time Sales and Operational Planning
      • Predictive Trade Planning
      • Trade Promotion Optimization
      • Deductions and Settlement Management
  • 37. Elements of a Demantra Solution
    • Clients
    • A Demantra solution includes multiple client machines, each running a browser to access Demantra
    • Application Server
    • Web server and a J2EE application server, which can be on the same or different machines; for supported software, see the Oracle Demantra Installation Guide
    • Database Server
    • Every Demantra solution includes a database server
    • Analytical Engine
    • Oracle provides two different modes for the Analytical Engine:
      • In PE mode, the engine is suitable for use with Promotion
      • Effectiveness.
      • In DP mode, the engine is suitable for use in demand planning applications.
  • 38. Upgrade Steps
  • 39. Plan
    • ASCP
      • Upgrade OS for existing hardware
      • Deploy new ASCP hardware. (Change to multi-node configuration)
      • ASCP Upgrade vs. Re-Implementation
      • Source Side Requirements
      • Replace customizations
    • Demantra
      • Retool processes
      • Take advantage of simplification opportunities in advance of Implementation
      • Phasing
  • 40. Evaluate
    • Software Requirements
    • Application Servers
    • Client Requirements
    • Licensed Modules
    • Hardware configuration
    • Hardware Architecture
      • DB and AS Server
      • Demantra Analytical engine (windows server)  
    • Integration Options
    • Connectivity Requirements (Performance Requirement)
    • Hardware Sizing
    • Use Oracle Demantra and ASCP Sizer
    Total Locations [50] Total SKU [200] Average SKUs per Location [40] Effective Avg. theoretical SKU/Location Combination [20000] History Periods [36] Future Periods [18] Total Periods [54] Number of Users [30]
  • 41.
    • EBS 11i10 sources instances + combined 11i10 APS/Demantra destination instance
    • EBS 11i10 sources instances + separate 11i10 APS + separate Demantra destination instance
    • Data collectors can be used to export the data from Oracle ERP to Demantra but it still needs to be transformed to fit the needs of Demantra.
    EBS-Demantra Configurations Options
  • 42. Data Model
  • 43. Process & Functional Flow
    • Demantra
    • Data Warehouse
    • Oracle ASCP
    Sales & Marketing Inputs Reporting: Finance (Revenue, Margins, Costs…) SCP (Quantity, Dates) … ASCP: E2E Planning Reporting: Reviews & Consensus Current Project Phase is focused on replacing Manugistics with Demantra while maintaining as much consistency with current processes as feasible.
  • 44. Demantra Integration with Oracle E-business Suite and ASCP 11.5.10 (Decentralized Architecture)
  • 45. Upgrade Steps
  • 46. Prepare
    • Took Advantage of Available ASCP and Demantra Content ( https://metalink.oracle.com/ )
    • ASCP
      • Oracle Advanced Planning and Scheduling Suite (118086.1)
      • 11.5.10 - Oracle Advanced Planning Implementation and Users Guide (B-10144-08)
      • List of High Priority Patches for the APS Suite – (223026.1)
    • DEMANTRA
      • Oracle Demantra Documentation Library" Metalink. (Doc Id: 443969.1) EBS-Demantra Integration Installation Overview and Diagram (434991.1)
      • Demantra SIG group website: (http://demantrasig.oaug.org/knowledgebase.php?page=knowledgebase)
  • 47.  
  • 48. Upgrade Steps
  • 49. Analytical Engine HP Server (380G5) Brower (Client) ASCP Forms/Web OAS 10g R3 (SOA) OC4J_Demantra Sun v880 Existing Hardware New Hardware Key HTTP / HTTPS Oracle NET 8 ASCP DB/CCM & Demantra DB / Services Sun V890 Architecture Oracle 11.5.10 Sun Solaris DB/CCM – 8x32 SFe4900 Forms/Web – 3-4x16 SFv440 Login via SSO WMS Yantra YCS/DCS Sun Solaris 2x8 SFv880 Data Warehouse Sun Solaris Sun v890 dblink dblink dblink dblink Oracle NET 8
  • 50. Execute ASCP
    • Install APS - 11.5.10 CU2
    • Apply APS patches
      • ATP Patch for J -Rollup
      • Data Collections patches (RUP#24 Patch – 6625126)
      • ASCP Engine/UI Rollup patch #27 - 6444221
    • Create DB link between transaction source (ERP) server and APS(Advanced Planning & Scheduling) server
    • Setup/configure/verify EBS/APS Profiles
    • Setup Collection Instance
    • Setup collection program
    • Run collection to copy supply chain model from source instance to APS server
    • Define an ASCP plan and setup plan options (with no constraints)
    • Launch the plan
  • 51. Execute Demantra
    • EBS-Demantra Installation
    • Install OracleAS 10.1.3 Application Server Middle Tier
    • On the Windows Server
      • Install Oracle 10g Client
      • Install Oracle Demantra 7.2
      • Create and Deploy demantra.war file to Oracle AS 10.1.3 Middle -Run Create_war.bat (%DEMANTRA_HOME%Collaboratordemantra)
      • Run Tamcat WebServer -%DEMANTRA_HOME%CollaboratorTomcatinstartup.bat
    • Upgrade EBS/APS 11i (11.5.10.2) applications to J2SE 1.5.0.12
    • Upgrade EBS/APS 11i (11.5.10.2) applications Dev6i to Patch 18 or newer
    • Install Latest ASCP Collections and Engine Patches on EBS/APS
    • Install EBS Demantra Integration Patch
  • 52. EBS Demantra Integration Patch
    • Install on both EBS and APS Applications Instances.
    • Source ------
      • 6625126 Data Collections Patch (Rup#24)
      • 5997112 EBS-Demantra Integration Patch
    • Destination -----------
      • 5985614 Oracle Demantra Release 7.1.1
      • 6444221 Engine/UI Rollup Patch (Rup#27)
      • 6625126 Data Collections Patch (Rup#24)
      • 5997112 EBS-Demantra Integration Patch
    • The Integration Patch installs Demantra (MSD_DEM_XXXXXX) objects into the APS Database / Demand Planning MSD Schema.
  • 53. Setup Demantra Profiles
    • Source Side Profiles
      • Profile Name Value
      • -------------------------------------------------- ---------------
      • MSD: Enabled Organization for Item Collections MSD_ALL_ORG
      • MSD: Two-Level Planning 2
    • Destination Side Profiles
      • Profile Name Value
      • -------------------------------------------------- ---------------
      • MSD_DEM: Currency Code USD
      • MSD_DEM: Data Profile for Price Lists EBS Price List
      • MSD_DEM: Debug Mode N
      • MSD_DEM: Host URL http://dlek40.itg.ti.com:8888/demantra
      • MSD_DEM: Schema DEMANTRA
  • 54. Execute Demantra
    • Run Download Calendars concurrent program)
      • The Download Calendars concurrent program downloads collected manufacturing and fiscal calendars, in Advanced Supply Chain Planning collections, to Oracle Demantra.
    • Register APS with OID/single sign-on server to enable single sign-on (Follow note Register Demantra applications with OID/single sign-on)
      • -Run ssoreg
      • Enable mod_osso (in httpd.conf file)
      • Protect the required Demantra URLs in mod_osso.conf file
      • Update mod_osso.conf in [ORACLE_HOME]ApacheApacheconf
    • Restart Demantra Web Server
  • 55. Execute
    • Notes on Testing
      • Test key business processes, flows and scenarios
      • Execute multiple testing rounds and budget enough time for issue resolution
        • Performed 3 successful test cycles before production cutover
      • Perform load and volume testing
      • Time the upgrade process to gauge duration required for cutover
  • 56. Upgrade Steps
  • 57. Maintain
    • Ensure that the Schema stats are up to date
    • Gather Schema stats after every forecast run and essentially before the forecast is run
    • Forecast versioning : Keep it to the number that is absolutely necessary
    • Ensure that Sales_data, mdp_matrix are in their own tablespaces. Monitor for growth as they are prone to performance issues
    • The Web Server must be restarted for most changes to be available in Oracle Demantra.
  • 58. Agenda Introduction Business Environment Legacy System Background Business Case Implementation Experience Case Study Conclusions
  • 59. So we did Historical data Forecast Causal factors Combined model Superior Bayesian-Markov Analytics Causal Analysis Outlier Detection Promotion Events Seasonality Cyclical Patterns Trend
  • 60. What is the result? Finalize Consensus Demand Plan
  • 61. Summary – a great success, a proven project model A major hardware platform upgrade and software rollout in a live operational environment
  • 62. So is that all the benefit?
  • 63. So what are these other benefits? Improved forecasting and planning accuracy
  • 64. So what are these other benefits? Reduced out-of-stock occurrences Improved forecasting and planning accuracy
  • 65. So what are these other benefits? Forecast new items and/or customers that have no sales history Reduced out-of-stock occurrences Improved forecasting and planning accuracy
  • 66. So what are these other benefits? Integrated Supply Chain Planning environment Forecast new items and/or customers that have no sales history Reduced out-of-stock occurrences Improved forecasting and planning accuracy
  • 67. So what are these other benefits? Integrated Supply Chain Planning environment Forecast new items and/or customers that have no sales history Reduced out-of-stock occurrences Improved forecasting and planning accuracy Reduced cycle times
  • 68. CHALLENGES
    • Primarily relied on self education and limited functional training
    • Little documentation on Windows components (no sizing, tuning or best practice for the engine)
    • One of the first PMO managed projects meant new processes
    • Functional
    • Manugistics expertise was no longer present in Demand Planning
    • Demand Planning staff home grown
    • Business Analyst new to Demand Planning
    • Consulting budget very limited
      • Used for business requirements development
      • Process modification deeply extended
    • Training budget non-existent after economic downturn
    TI Confidential
  • 69. CHALLENGES (Technical)
    • 1 Developer attended functional training and was out of country for significant portion of development cycle
    • Data Warehouse deemed as key role
    • Client introduced java incompatibility challenges (Softgrid had to be deployed)
    • No eTRM
    • Outcomes
    • Native integration not used (Mods & DW emphasis)
    • Interface seen as intuitive
    • No training issues with Sales
    • No lost/reduced cycle
    • Transition was perceived as a great success
    TI Confidential
  • 70. What worked well…
    • The new system!
    • User group
    • In general all users accepted the system
    • 1 big team approach
    • Steering board very supportive
    • ‘ Expertise’ involved
    • Weekly project meetings
    • Roll-out weekends
    • Project management
    • Post-implementation support
    • Restricting project scope
  • 71. Pending Phase 1 issues
    • DW Load
    • Windows Launch of forecast engine
    • Concurrent Request launch of Workflow
    • Large list of unexplored features
  • 72. Bullets Dodged
    • Tuning
      • Forecast at customer, not customer site therefore tuning not as challenging
    • Limited Phase 1
      • Limited use of manugistics allowed scaled back phase 1 feature set
  • 73. Texas Instruments - Education Technology Division (Ed. Tech.)
    • Revenue $500+M
    • Product lines: calculators (graphing, financial & scientific), classroom learning system, data collection devices & computer software
    • Three primary suppliers (Far East)
    • Distribution Centers in Singapore, Australia, Netherlands, Fort Worth, TX
    • Demand Planning
    • Primary Supplier Schedule for 300 Item/Supplier Finished Goods combinations
    • 12+ month forecasting horizon
    • Forecast at detail level (Item/Customer/Country) for 23K combinations
    • Supply Chain Planning
    • 8 orgs
    • 1300 items
    • Legacy forecast tool -Manugistics version 2.6
    • 3 separate modules – equated to long batch processing and forecast load times
    • end-of-life system and de-support (HW & SW)
    • Forecast accuracy < 70%
    • Forecast engine run time is 8hrs
    • No system supported sales and operations planning process
    WITH ORACLE
    • Runs worldwide manufacturing and sales operations using ASCP and Demantra
    • Single, global plan for 8 orgs, including worldwide distribution centers and manufacturing plants
    • Reduce manual forecasting processes
    • Using real-time material constrained, multi-org, multi-level ATO order promising process
    Benefits
    • Integrated Supply Chain Planning environment
    • Strongly reduced planning cycle time
    • Strongly increased forecast accuracy
    • Enabled sales and operations planning process
    COMPANY PROFILE BEFORE DEMANTRA AFTER DEMANTRA PLANNING BENCHMARK
  • 74. In Summary… Make Sure You’re Prepared and Test, Test, Test! Integrated Supply Chain Planning environment Increased accuracy with advanced forecast tuning Excellent performance reduces cycle times Richer functionality in Sales & Demand management Demantra is the right direction….
  • 75. Thank You
  • 76. Questions?