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.
10.
11.
12. Agenda Introduction Business Environment Legacy System Background Business Case Implementation Experience Case Study Conclusions
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.
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
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
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
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.
69.
70.
71.
72.
73.
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….
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 &quot;rough cut&quot; 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 &quot;Oracle Demantra 7.1 Foundation Implementation Guide&quot;, 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:
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.&quot;
• 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.
