Upgrade to Pro — share decks privately, control downloads, hide ads and more …

OML usage highlight: Machine Learning Recommendations for Maintenance and Repair

OML usage highlight: Machine Learning Recommendations for Maintenance and Repair

This week in our Office Hours for Oracle Machine Learning on Autonomous Database Lee Sacco, Senior Director Depot Repair Development presented the current integrations and usage of Machine Learning from OML in the EBS Depot Repair Application.

The Oracle Machine Learning product family supports data scientists, analysts, developers, and IT to achieve data science project goals faster while taking full advantage of the Oracle platform.

The Oracle Machine Learning Notebooks offers an easy-to-use, interactive, multi-user, collaborative interface based on Apache Zeppelin notebook technology, and support SQL, PL/SQL, Python and Markdown interpreters. It is available on all Autonomous Database versions and Tiers, including the always-free editions.

OML includes AutoML, which provides automated machine learning algorithm features for algorithm selection, feature selection and model tuning, in addition to a specialized AutoML UI exclusive to the Autonomous Database.

OML Services is also included in Autonomous Database, where you can deploy and manage native in-database OML models as well as ONNX ML models (for classification and regression) built using third-party engines, and can also invoke cognitive text analytics.

Marcos Arancibia

June 15, 2021

More Decks by Marcos Arancibia

Other Decks in Technology


  1. Oracle Machine Learning Office Hours Usage Highlight Machine Learning Recommendations

    for Maintenance and Repair with Lee Sacco supported by Marcos Arancibia, Sherry LaMonica & Mark Hornick Product Management, Oracle Machine Learning June 2021
  2. The following is intended to outline our general product direction.

    It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, timing, and pricing of any features or functionality described for Oracle’s products may change and remains at the sole discretion of Oracle Corporation. Safe harbor statement 2
  3. Depot Repair Business Models • The repair, maintenance, or recycling

    of products returned by customers to a processing facility. • Often conjoined or contrasted with “field service”, which involves repair, maintenance, or recovery at a customer or off-premise location. • Requires tracking each item from customer to repair center to final disposition (back to customer, to warehouse, to supplier, or recycler). • Manufacturers / OEMs • Contract Repairers • In-store • Authorized Service Providers What is it?
  4. User Schema Repair Technician • Wide spectrum of education and

    training – from cleaner to nuclear engineer. • Tactile, concrete, physical. Makers, builders, fixers. Good problem solvers. • Generally in a workshop or on a repair line. • Love fixing things but HATE data entry. • Don’t like being told what to do, especially by a computer. https://www.plexus.com/en-us/solutions#Aftermarket-Services • Track items from dock door to final disposition. • Diagnose problem and cause. • Determine best fix. • Track repair activities, parts, labor, analytic data, other documentation. Tasks • Very broad product sets. • Each item has a unique history. • Each item type has a different fault tree and diagnostic pathway. • “Best” fix is relative. Multi-level constraints. Problems Apply ML
  5. VERY Structured Data ERP: Canonical Tasks, Data, KPIs ERP Database

    Canonical Data Model Task 1 Task 2 Task 3 ERP Functions Canonical Use Cases (decisions and actions)
  6. VERY Structured Data “Structured” <> “Predictable” ERP Database Canonical Data

    Model • ~1000 different customers in many different industries • Shape of data: • Every business is different • Every item is different • Snapshots vs. Streams
  7. EBS Depot Repair Technician Portal • Clipboard-and-checkbox metaphor • Tabs

    for process steps: • Evaluation: diagnose and prescribe • Execution: tasks, parts, labor • Debrief: root cause, claims, activities • Decision Support: • Recommend Services • Frequency • Bulletins
  8. EBS Depot Repair Technician Portal: ML Recommendations • Released July

    2018: Patch #28263445 • Codeline 12.2.7+ RDBMS: • Demo: https://youtu.be/gWTXvvERfag • Targets: Service Code, Defect Code (RCC) • Predictors: • Item • Item Revision • Age • Diagnostic Codes • Technician Notes (TM) • Service Agent Notes (TM) • Problem Summary (TM) • Customer Problem Description (TM) • Specific, Actionable Recommendations • Confidence Thresholds • Insight as a Requirement • Automatic Data Update • Log Decision and Reasons
  9. Architecture Technician Portal: ML Recommendations • View Creation • Data

    Preparation • Encode categoricals • Scale numericals • Impute missing values • Manage sparse / imbalanced data* • Feature selection* • Manage outliers* • Generating Models (SVM, NB, DT) • Choosing the Best Model • Recommendation Thresholds • Oldest Transaction Date • Plumbing for Future Predictions
  10. Roadmap and Wishlist • Measure and report recommendation outcomes. •

    Provide clearer insights. • Feedback loop based on rejection log and reasons. • Additional predictors: • Quality / Inspection data • Meters • Installed Location • Number of failures • Time between failures • Component age • Supplier data • Next-up ML solutions: • Predict remaining useful life of parts • Predict next failure • Predict cost, time to repair • Recommend repair vs. replace • Recommend additional actions • Detect warranty fraud • More competing algorithms, hyper-parameters. • Log training time and memory usage for models.
  11. What we did Wrong 1. Confused data mining and app

    building. 2. Put too much faith in the initial data set. 3. Put too much faith in outside experts. 4. Chose a complex case first (multi-value targets). 5. Locked onto specific problems and solutions early.
  12. Take-aways 1. Start by knowing the business and the user.

    2. Structured data is still cool. 3. No perfect model or algorithm for all customers. 4. Test and iterate before locking onto a problem or solution. 5. Don’t put blind faith in experts.