BigMachine

8/10/2019 BigMachine

1/34


2/34

Copyright 2009 Deloitte Development LLC. All rights reserved. 2

Overview


3/34


Big Machines Overview

Big Machines (BMI) can be implemented to integrate within a CRM and/or ERP

environment BMI consists of three distinct areas: Configuration, Commerce, and Document

Engine

Configurationis a process by which complex and customized selections of productsand services can be assembled

Commerce is where the configured selections run through specific rules to determinepricing. This can include quote and line level discounting, margin calculations,customer specific pricing, and automation of workflow approvals

Document Engine completes the process with the creation of high quality proposaldocumentation that could include product features with pricing, technical datasheets,drawings, terms and conditions, and can even append external documents from ausers desktop.

A typical CRM/ERP landscape with BMI is shown on the following slide.


4/34


Customers

Typical BMI landscape with ERP and CRM

SFDC (CRM)

CustomerMaster

Item Master

ERP

OrderManagement

.

Opportunity

BMI

PricingMaster

Configure

Price

Quote Proposal

Direct push/pull of datawith standard integration

package (SFDC Only)

LocalItem andPricingCopy

Factory

OrderFulfillment

.

Data sync withstandard integration

package (SFDC Only)

Transaction flow (Custom) Transaction flow (standard) Data flow


5/34


Typical BMI landscape with ERP Only

ERP

CustomerMaster

Item Master

Factory

OrderFulfillment

.

OrderManagement

BMI

PricingMaster

Configure

Price

Quote Proposal

Data sync withCustom integration

package

Data sync withCustom integration

package

LocalItem and

PricingCopy

Customers



6/34


Capability Assessment


7/34Copyright 2009 Deloitte Development LLC. All rights reserved. 7

Capability Fit Assessment

BMI capabilities were evaluated across multiple competencies in order to determine theability of the tool to implement specific use case functionalities.

Additionally, BMI was compared to current Oracle Configurator capabilities against thesame set of use case functionalities.

A summary of these evaluation criteria and results can be found in the attachedspreadsheet.



Deployment Models



BMI Deployment Models

Typically BMI can be utilized in the following capacities

1. Solely for Configuration2. Full CPQ solution

There are 3 primary Masters Data aspects to consider in a BMI deployment: Customer,Parts, and Pricing. While they can be visualized with different names with different clients,the premise of these three variables is consistent.

Customer Master: Customer specific information including specific contacts, bill-to

and ship-to data, as well as other customized variables as needed. This data istypically maintained as master within the CRM or ERP.

Item Master: This is where all of the information relating to catalog items andservices are held. Parts information can include part ids, descriptions, and

associations to other parts. This data is typically maintained as master within the CRMor ERP and a local copy would be maintained in BMI.

Pricing: This variable is where all pricing data is held. This could include list prices,customer specific pricing information, discounting rules, and promotions. In a typicalBMI implementation, the pricing master is maintained within CRM/ERP and a local copywould be maintained in BMI.

Depending of the location of Master Data, the typical integration flows for either mode(Configurator` Only or full CPQ) of deployment are shown in the following slides.



BMI

BMI as CPQTransaction flow

Configure

Price

Quote

EBS

WIP /Shipping

OrderManagement(Pass thru)

VCP

ASCP

Order creation

Order details

Configuration attributesProduct dimensions/drawings

Routing information

ATP(availability)

Orderupdates/cancellation

EDI



11/34



BMI as CPQDesign Considerations

Additional attributes needed in BMI to support EBS multi-org architecture

Operating Units Inventory organization (Shipping warehouse)

Leverage approval capability in BMI to baseline quote before releasing it to EBS

BMI to control order changes based on order progression in EBS and will honor standardEBS constraints

BMI to EBS integration will support both Configured and SKU based products

BMI will offer both products and services, but the contract management and installed base

will be managed completely in Order management. BMI will provide enough information toOM to trigger service related transactions

Only master controlled item attributes will be interfaced to BMI



BMI as Configure onlyTransaction flow

EBS

OrderManagement

(Pass thru)

WIP/Shipping

Quoting(Quote & Price)

VCP

ASCP

BMI

Configure Configurations



14/34



BMI as Configure Only - Design Considerations

BMI to EBS integration will support both Configured and SKU based products

Leverage approval capability in Oracle quoting to baseline quote before releasing it to OM Configuration changes from BMI will be interfaced as a new version of quote in EBS

Only master controlled item attributes will be interfaced to BMI


16/34


Option Comparison


17/34


Option comparison

Processconsiderations

Sales organization will align to BMI as primarytool with limited visibility/ownership in EBS

Engineering organization will support bothBMI and EBS for product configuration/NPI

Change orders will always be initiated in BMIand interfaced to EBS via orderupdates/cancelation

Product availability and commitment tocustomers can be managed via lead timescaptured in BMI or by getting real time

feedback from supply chain

The upstream quoting process will initiate inEBS Quoting with only configurationcompleted in BMI. Both Sales andEngineering organizations will function inEBS and BMI.

Lack of end to end visibility of quote andconfiguration within a single system.

Additional complexities in the process sinceusers are operating in 2 systems tocomplete quotes

Product availability only in EBS

Integrationconsiderations

Additional integrations compared toConfigurator only option

High complexity in order integration due todependencies on EBS OM and downstreamfactory operations

Pricing can either be duplicated in BMI(preferred) or using EBS pricing engine

Easy to manage change orders due tointegration with Oracle Quoting and itsversion control capability

Industry/Sectoralignment

Consumer Products

Retail & Distribution Insurance products Technology & High Tech manufacturing

Industrial Products & Services

Aerospace & Defense Telecommunications & Services

Implementationcost

$$$$ $$$

Summary

The architecture option is suitable for a simpleconfigure to order business with simple tomedium complexity products with shorter leadtimes

The architecture option is suitable for highlycomplex products and services specifically inan engineer to order business with long leadtimes

BMI as CPQ BMI as Configure only


18/34


Additional Deployment

Considerations


19/34


Additional Deployment Considerations

Need capability in BMI to offer products thru web portal

EBS will be the source of truth for pricing. A hybrid approach can be deployed to duplicatelist price in BMI and call Oracle pricing engine to derive selling price using web service

Adaptors will be designed with plug and play to support all product and pricingcomplexities and quote/order integrations


20/34


Deployment Accelerators

BMI as CPQ


21/34


High Level DesignProcess Flow

Big MachinesFusionMiddleware

OracleeBusinessSuite

Configure Quote CompleteQuote Transform Order

Customer Products

PriceCustom

Data Table

BMI QuoteXML

AIA Format

EBS OrderXML

Order Booked

Shipped

Invoiced


22/34


23/34


Technical ArchitectureFMW AIA Components

BMI

FMWEBS

RequesterABCS

Configuration

attributes

Order details

EBS

Configuration

attributes

Order details

ProviderAdapter

Configuration

attributes

Order details

Requester ABCSService

EBS Service Provider ABCSService

Provider AdapterService

Service Type Synchronous Synchronous Synchronous Synchronous

Input Payload BMI Quote AIA AIA Oracle

Transformation BMI to AIA NA AIA to Oracle NA

ProviderABCS

Configuration

attributes

Order details


24/34


Demo


25/34


BMI Home Page


26/34


BMI Configuration Page


27/34


BMI Quote Page - Draft


28/34


BMI Quote PagePricing Finalized


29/34


Fusion Middleware (AIA)Data Flow

Flow Trace for FMW Create Sales Order Flow

Complete Data flow


30/34


EBSOrder Screen


31/34


EBSOrder Screen


32/34


EBSLines and Configurator


33/34




34/34


BigMachine

Documents

Transcript of BigMachine