Erp integration
Download
1 / 34

ERP Integration - PowerPoint PPT Presentation


  • 278 Views
  • Uploaded on

ERP Integration. Bob Phare [email protected] (205) 879-3282 ext. 1130 Chris Strickland [email protected] (205) 879-3282 ext. 1241. Session Objective.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about ' ERP Integration' - isla


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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
Erp integration

ERP Integration

Bob Phare

[email protected]

(205) 879-3282 ext. 1130

Chris Strickland

[email protected]

(205) 879-3282 ext. 1241


Session objective
Session Objective

  • This session will describe how our core products are exploiting COMMANDedx capabilities to transform integration with third-party enterprise and financial systems.

ERP Integration


Agenda
Agenda

  • Overview of COMMANDedx

  • Definitions and Concepts

  • Specific ERP integration scenarios

    • ERP – COMMANDseries

    • ERP – COMMANDbatch

    • ERP – Apex

  • Some technical “nuts and bolts”

ERP Integration


Commandedx overview
COMMANDedx Overview

  • COMMANDedx – Enterprise Data Exchange

    • Is an integration platform that is standardizing the method of transporting data between Command Alkon and third-party products.

    • Allows systems with different platforms and data structures to exchange information in a uniform fashion

ERP Integration


Commandedx overview1
COMMANDedx Overview

  • COMMANDedx Technology

    • Integrates via standard XML entities (Business Objects)

    • Message bus is based on ISA-95 and OAGIS standards

    • Publisher–Subscriber model

    • Full Diagnostic Support Tools (Server / Web Based)

  • Product status:

    • Fully functional and shipping in two separate configurations.

ERP Integration


Definitions and background
Definitions and Background

  • ERP – “Enterprise Resource Planning” system

    • “A system used to manage and coordinate all the resources, information, and functions of a business.”

    • This may be a true ERP system like SAP or a simple accounting system.

  • OAG – Open Applications Group

    • A not-for-profit standards development organization focused on building data exchange standards for B2B and A2A integration.

  • OAGIS – “Open Applications Group Integration Specification”

    • A broad data exchange standard developed by OAG.

  • ISA-95 – Describes interfaces between enterprise and control systems.

ERP Integration


Definitions and background1
Definitions and Background

  • XML – “Extensible Markup Language”

    • A set of rules for encoding data in a format that is both human-readable and machine-readable.

    • XML format is simple, general-purpose, and can be used over the Web.

    • (Also known as “Excellent Marketing Language”)

  • BOD – “Business Object Document”

    • Describes/defines a type of transaction between systems

    • Consists of a “Verb” and a “Noun”

    • Example: Sync Credit

    • CAI has defined approximately 20 Business Objects based on OAGIS and ISA-95

  • Business Objects are the building blocks of system integration

ERP Integration


Business objects are the building blocks
“Business Objects are the Building Blocks”

OAGIS

“CustomerPartyMaster”

System A

System B

Customers

CUST

A

  • Data “Publishers” vs. Data “Subscribers”

ERP Integration


Commandedx plumbing
COMMANDedx “Plumbing”

  • Command Alkon – Traditional Integration Approach

ERP Integration


Commandedx overview2
COMMANDedx Overview

  • COMMANDedx Integration introduces the “Enterprise Data Bus”

ERP

A

A

A

ERP Integration


Commandedx plumbing1

Service Gateway

COMMANDedx “Plumbing”

  • External ERP systems normally access the Data Bus via the Service Gateway.

CMD series

CMD batch

A

Apex

ERP

CMD qc

COMMANDedx Data Bus

Integra

A

KP

Products

  • This allows the external system to view the various CAI products as a single system with a single interface point.

TMS

Products

ERP Integration


Three integration scenarios
Three Integration Scenarios

  • ERP to COMMANDseries

  • ERP to COMMANDbatch

  • ERP to Apex

ERP Integration


Three integration scenarios1
Three Integration Scenarios

Scenario 1: ERP to COMMANDseries

ERP Integration


Commandseries erp integration
COMMANDseries-ERP Integration

  • “Classic” implementation

    • Central Dispatch

    • With or without batch system interfaces

COMMANDbatch#1

ERP

- Invoicing

- Purchasing

- Financials…

COMMAND

concrete

- Order Entry

- Dispatch…

COMMANDbatch#2

COMMANDbatch#3

Traditionally implemented with Flat File interfaces

ERP Integration


Commandseries erp integration1
COMMANDseries-ERP Integration

ERP System

COMMANDseries

Materials

Materials

Products

Mixes

Customers

Customers

Projects

Projects

Drivers

Drivers

PO’s, Vendors

PO’s, Vendors

Tickets

Tickets/Loads

Inventory

Batch Weights

Invoices

Mat’l. Receipts

Financials

ERP Integration


Commandseries erp integration2
COMMANDseries-ERP Integration

  • Project Status: 50% complete on CS08 V3

    • Field testing tentatively arranged for Spring 2013

    • CS08 V2 work not yet scheduled

ERP Integration


Three integration scenarios2
Three Integration Scenarios

Scenario 2: ERP to COMMANDbatch

ERP Integration


Commandbatch erp integration
COMMANDbatch-ERP Integration

  • Differs from “Classic” implementation

COMMANDbatch#1

ERP

- Invoicing

- Purchasing

- Financials…

COMMAND

concrete

- Order Entry

- Dispatch…

COMMANDbatch#2

COMMANDbatch#3

ERP Integration


Commandbatch erp integration1
COMMANDbatch-ERP Integration

  • Direct COMMANDbatch-ERP implementation

    • Suited for plant-level dispatch vs. central dispatch

    • Large number of plants justifies integration investment

    • Ideal for operations with intermittent plant connectivity

COMMANDbatch

ERP

- Invoicing

- Purchasing

- Financials…

COMMANDbatch

COMMANDbatch

ERP Integration


Commandbatch erp integration2
COMMANDbatch-ERP Integration

COMMANDbatch

ERP System

Materials

Materials

Products/Mixes

Mixes

Customers

Customers

Projects

Projects

Drivers/Trucks

Drivers/Trucks

Orders

Tickets

Tickets/Loads

Inventory

Batch Weights

Invoices

Mat’l. Receipts

Financials

ERP Integration


Commandbatch erp integration3
COMMANDbatch-ERP Integration

  • Project Status: 90% complete

ERP Integration


Three integration scenarios3
Three Integration Scenarios

Scenario 3: ERP to Apex

ERP Integration


Apex erp integration
Apex-ERP Integration

  • Typical Apex configurations are

    • Distributed; or

    • Centralized/Distributed

Apex #1

- Order Entry

- Scaling/Ticketing

ERP

- Invoicing

- Purchasing

- Financials…

Apex

(Data Consolidation)

Apex #2

Apex #3

ERP Integration


Apex erp integration1
Apex-ERP Integration

  • The data and process flows are similar regardless of configuration

    • In a centralized configuration, Apex manages data replication to the plant systems

    • In a distributed configuration, COMMANDedx manages routing of data.

ERP

- Invoicing

- Purchasing

- Financials…

Apex

ERP Integration


Apex erp integration2
Apex-ERP Integration

Apex

ERP System

Items/Materials

Items

Customers

Customers

Haulers

Haulers

Projects

Sales Orders

Trucks

Trucks

Orders

Tickets

Tickets/Loads

In/Out/Produced Inventory

Inventory

Invoices

Financials

ERP Integration


Apex erp process flow
Apex-ERP Process Flow

  • Project Status: 10% complete.

    • Requirements review and high-level design underway

  • Currently out of scope:

    • Tickets dispatched on ERP, sent to Apex

    • Cartage calculated on Apex, sent to ERP

ERP Integration


Justifying commandedx
Justifying COMMANDedx

…or, “Why would I want to do this?”

  • “Business real-time” data synchronization

    • Improves operational efficiency

    • Reduces workarounds currently required to deal with slow or missing data

  • Higher reliability and reduced support cost

    • “Guaranteed delivery” of data, and internal delivery confirmation

    • Transactional control over data objects such as Projects and Mix Designs

    • Real-time error checking allows timely correction of data problems if/when they occur.

ERP Integration


Justifying commandedx1
Justifying COMMANDedx

…or, “Why would I want to do this?”

  • Greater functionality, i.e. more data shared between systems.

  • Higher data security

    • No intermediate flat files to be misplaced or corrupted

    • More difficult to hack the system

  • Equal or lower implementation cost on new systems

  • Configuration flexibility makes future system changes easier.

ERP Integration


Business objects are the building blocks1
“Business Objects are the Building Blocks”

OAGIS

“CustomerPartyMaster”

System A

System B

Customers

CUST

A

ERP Integration


Anatomy of a business object xml
Anatomy of a Business Object (XML)

Customer Code

<CustomerPartyMaster xmlns="http://www.openapplications.org/oagis/9">

<PartyIDs>

<ID>1003636</ID>

<TaxID />

</PartyIDs>

<AccountID>1003636</AccountID>

<Name sequence="1">Ronald Reagan</Name>

<Name sequence="2">REAGAN</Name>

<Location type="Primary">

<Address>

<AttentionOfName>White House</AttentionOfName>

<AddressLine sequence="1">1600 Pennsylvania Ave</AddressLine>

<AddressLine sequence="2" />

<AddressLine sequence="3" />

<CityName>Washington</CityName>

<CountrySubDivisionCode>DC</CountrySubDivisionCode>

<CountryCode>USA</CountryCode>

<PostalCode>20502</PostalCode>

</Address>

</Location>

<Location type="Invoice">

<Address>

<AttentionOfName>White House</AttentionOfName>

<AddressLine sequence="1">1600 Pennsylvania Ave</AddressLine>

<AddressLine sequence="2" />

<AddressLine sequence="3" />

<CityName>Washington</CityName>

<CountrySubDivisionCode>DC</CountrySubDivisionCode>

<CountryCode>USA</CountryCode>

<PostalCode>20502</PostalCode>

</Address>

</Location>

Description

Short Description

Primary Address Element

Invoice Address Element

A

ERP Integration


Connecting to the gateway

Service Gateway

Connecting to the Gateway

CMD series

A

COMMANDedx Data Bus

SOAP Services

File Services

A

ERP Integration


Related sessions
Related Sessions

ERP Integration


Questions answers
Questions (& Answers?)

ERP Integration


Please complete your evaluation
Please Complete Your Evaluation

  • Be sure to circle the session you are evaluating on the back of your card

    • Management (Track Name)

    • MGT-003 (Session Code)

    • ERP Integration (Session Title)

  • All breakout session materials can be accessed at: www.commandalkon.com/cc2012/update/index.htm

  • Thank You!

ERP Integration


ad