1 / 11

bt 2 – Design Options for Masco Cabinetry March 9 , 2010

bt 2 – Design Options for Masco Cabinetry March 9 , 2010. Agenda. Why did we need string table? String table issues Masco Cabinetry new requirements Proposed high level approach Non-dimensional configuration Dimensional configuration Product Information Management.

myrrh
Download Presentation

bt 2 – Design Options for Masco Cabinetry March 9 , 2010

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. bt2 – Design Options for Masco CabinetryMarch 9, 2010

  2. Agenda • Why did we need string table? • String table issues • Masco Cabinetry new requirements • Proposed high level approach • Non-dimensional configuration • Dimensional configuration • Product Information Management

  3. Why did we need string table? • To provide one stop solution with all sellable products across all brands to facilitate price book generation and various customer catalog creation. • To enable quick order entry using SKU + Global Options instead of Oracle Item Numbers (Lot Management, Dealer Order Entry, proCab) • To provide customers all sellable product data with an identifying number (legacy part number), so the customers can load this data into their systems and send part number based orders via EDI,FTP to BCG • To map legacy part number to Oracle item number in order to facilitate importing of legacy orders into Oracle (EZ Cab, JDE) • To allow creation of order-ready quotes for entire sub-division in various door-styles, species, colors, etc (IntelliQuote) • To cross reference product strings based on back-fill rules to minimize customers/BCG to change global options while creating orders using SKU + Global options • This also minimizes ‘gaps’ in product offering while preparing quotes for builder business. • To move away from completely pre-configured environment to selective pre-configure environment • To configure product on-demand if the ordered product is not pre-configured already

  4. String Table Issues • String table contains invalid global option combinations • Allows customers to order products that BCG cannot manufacture or ship wrong products • String Table maintenance is a nightmare • Data volume is huge. It requires more time to validate to ensure that all the product strings are cross referenced appropriately and pricing records are linked appropriately • Some times we don’t even know where to start with validation when we run a back-fill rule • Mass load and string maintenance form has limited validations allowing users and Frontier Interface to create duplicate strings • String Table is a drag on the system performance as this table keeps growing due to NPDs, new cross reference rules etc • String table design will not work in a 100% dimension based configure to order environment

  5. Masco Cabinetry New Requirements • System to support both dimensional and non-dimensional based configuration • System to support attribute based pricing • A centralized product information system to create and maintain product data and engineering changes and to publish to all the systems that require this information (Product Data Hub) • Need to eliminate string table dependency for order entry, quoting and catalog generation • Unified customer facing solution for Merillat, Quality and Kraftmaid products supporting manufacturing functions in both Oracle and legacy systems • Simplified catalog for 20/20 providing models, applicable options and pricing

  6. Proposed High Level Approach – Non-Dimensional Configuration Configurator (CZ Gold) String Generator • CZ Reference Model • (Merillat) • Models & options (mfg) • Backfill rules • CZ Reference Model • (Quality) • Models & options (mfg) • Backfill rules • CZ Reference Model • (Kraftmaid) • Models & options (mfg) • Backfill rules • String Table (CZ) • Configured item strings • Backfill Strings • BOM Models • Part pulling rules • BOM Models • Part pulling rules • BOM Models • Part pulling rules String Pricing Table (CZ) Attribute based pricing Publish Models Discrete String Generator EBS Prod Inventory/PIM Pricing Catalog Generator Backfill Program • String Table (INV) • Discrete item strings • Discrete item backfill strings • 20/20 • Distributor Master

  7. Proposed High Level Approach – Non-Dimensional Configuration • Establish Oracle Configurator as the single source of truth for all configured products of Masco Cabinetry. • Oracle Configurator to contain models, applicable options and backfill rules for all configured products of Masco Cabinetry to support customer order entry. i.e. Oracle configurator would support all sales side configurations for all brand products but may or may not support generating star item BOM, Routing etc. • Enhance string generator extension to create original product strings as well as backfill strings for all configured (non-dimension based) products. String generator to call pricing engine to derive list price based on attribute values. This extension is required until we convert all of our customers to attribute based ordering from part number based ordering. • Reduce the scope of backfill program to backfill only discrete item strings. • Develop a new program to generate catalogs based on the models and applicable options definitions in Oracle Configurator in combination with pricing definition in Advanced Pricing.

  8. Proposed High Level Approach – Dimensional Configuration Configurator (CZ Gold) Guided Selling UI • CZ Reference Model • (Merillat) • Models & options (mfg) • Backfill rules • CZ Reference Model • (Quality) • Models & options (mfg) • Backfill rules • CZ Reference Model • (Kraftmaid) • Models & options (mfg) • Backfill rules • Order Entry Applications • proCab • Order Management • Quoting • BOM Models • Part pulling rules • BOM Models • Part pulling rules • BOM Models • Part pulling rules Attribute based pricing Publish Models EBS Prod Inventory/PIM Pricing Catalog Generator • 20/20 • Distributor Master

  9. Proposed High Level Approach – Dimensional Configuration • Establish Oracle Configurator as the single source of truth for all configured products of Masco Cabinetry. • Oracle Configurator to contain models, applicable options and backfill rules for all configured products of Masco Cabinetry to support customer order entry. i.e. Oracle configurator would support all sales side configurations for all brand products but may or may not support generating star item BOM, Routing etc. • Develop guided selling user interfaces in Configurator for each model and link to all customer facing solutions in order to configure and price products at the time of real-time order entry. • Develop a program (API) that accepts model, attribute values along with dimensional information to validate the configuration, for orders requiring batch validation (e.g. EDI, XML orders) • Develop a new program to generate catalogs with models, applicable options and min-max dimensions based on the product definition in Oracle Configurator and pricing definition in Advanced Pricing.

  10. iFocus Kraftmaid Quality iFocus EBS - PROD iFocus iFocus iFocus Merillat Stellent APC2 CZ Gold iFocus iFocus Oracle 11i Oracle 11i Oracle 11i Oracle 11i Oracle 11i Oracle 11i Oracle 11i JDE Legacy R12 R12 Friedman Proposed High Level Approach – Product Information Management Kraftmaid Items Top Level Items Brands live in Oracle Quality Brand Items Merillat Brand Items Subscribe to new product definitions and changes Fusion Middleware Publish new product definitions and changes Sub-assembly data Product Data Hub • New Product Introductions • Engineering Change Management • Data Quality Management • Duplicate prevention and mergers • Data Security Document Management

  11. Proposed High Level Approach – Product Information Management • Build a separate instance that acts as a product data hub • Product data hub will contain all products of Masco Cabinetry (Oracle and non-Oracle) • Product definitions include Item, BOM, Catalogs and Attribute information • We need to perform one time conversion of product data from all the existing production systems (EBS Prod, Kraftmaid and Countertops) • Design common data structures for Items, BOMs, Catalogs and Attributes ensuring all the necessary data elements required by various target systems are included. • Maintain source system references for product data in PDH in order to publish product data from PDH to target systems. • PDH will publish data to target systems using Fusion Middleware architecture about new product definition and changes to existing products. • Target systems will subscribe data from PDH if designated for their systems. • Target systems to perform insert or update based upon mode of operation suggested by PDH. • PDH will also interface with APC2 to receive sub-assembly data

More Related