Integration technology to solve business problems in manufacturing

© Copyright John Cachat

Integration Technology to

Solve Business Problems

in Manufacturing

John M. [email protected] Better Technology. Lower cost.


Housekeeping

Phones are muted

Use the question

block for questions Copy of presentation

available upon request


About John M. Cachat

• Driving Business Performance

– Helping companies align their business and technology

– Focus on people, process, and then the technology

– Subject matter expert on business process management

– On-going research into next generation of technology for enterprise

systems

• 28 years experience in enterprise systems

– USAF Research Project (1985)

– Founder of enterprise quality software company (1988)

– Chair of ASQ technical committee on computerizing quality (1992)

• Trusted advisor to global organizations, government agencies,

and professional groups

http://www.linkedin.com/in/johncachat


Agenda

• The Manufacturing Software Map

• Engineering Change Process Example

• Software Demonstration

• The Business Case

• Introduction to Silico

4

Get the software you want and make it work the way you want it to work.


Evolution of Manufacturing Software

Started with Accounting

(AR, AP, GL)

Labor Intensive

Slow and Error Prone

Executives wanted faster

and more flexible reports

Reports showed too much

inventory

5



(AR, AP, GL)

Labor Intensive

Slow And Error Prone



Reports showed too

much inventory


(AR, AP, GL)

Then Came Inventory

Related Transactions

Labor Intensive Purchase Better

Slow and Error Prone Schedule Better



Ship Better


inventory

That covers it; Right?


6



(AR, AP, GL)

Labor Intensive

Slow And Error Prone



Reports showed too

much inventory

Started with Accounting (AR, AP, GL)

Then came Inventoryrelated transactions

Labor Intensive Purchase Better

Slow And Error Prone Schedule Better



Ship Better

Reports showed too

much inventory

That covers it, Right?


(AR, AP, GL)

Then Came Inventory

Related Transactions

Engineering & Shop Floor

Labor Intensive Purchase Better Moved from drafting board

to computer (CAD)

Slow And Error Prone Schedule Better Can’t find documents –

added vaulting (PDM)



Ship Better Added workflow (PLM)


inventory

Shop Floor MES


7


Manufacturing Software Map

ERP - Planning Systems

PLM

–

En

gin

ee

rin

g S

yst

em

s

MES – Execution Systems

Document

DrivenData

Driven

CRM / SRM

Legacy

Other

8


What About the Other?

• Imagine if you had a technology that allowed you to focus on the business process

• Let’s look an the Engineering Change Process

9

What business processes are the

ERP, PLM, MES technology not

supporting in your company?

What areas do you use XLS to

help do your job?


Engineering Change Management:

A Four Step Process

1.

ECR

Change Request

2.

ECN

Change Notice

3.

ECO

Change Order

4.

ECV

Change Verification

10


Change Request• Source

– Customers

– Internal

– Suppliers

• Deviation/Waiver/Permanent

• Should you or shouldn’t you do it?

– Review impact & related costs

– Determine risk

– Other parts, processes, etc.

• Who get’s to vote? – Create some rules.

11



A Four Step Process

1.

ECR

Change Request

2.

ECN

Change Notice

3.

ECO

Change Order

4.

ECV

Change Verification

12


Change Notice

• Who needs to know about the change and what do they have to do in order to prepare for the change?– Engineering

– Manufacturing

– Quality

– Purchasing

– Marketing (Packaging)

– Customers

– Suppliers

• What needs to be updated?

13



A Four Step Process

1.

ECR

Change Request

2.

ECN

Change Notice

3.

ECO

Change Order

4.

ECV

Change Verification

14


Change Order

• Everything is ready to go

• When do we start?

– Immediately

– By Date

– By Inventory/production schedule

• Existing parts (rework, scrap, use as is)

• New parts

15


Engineering Change Management

A Four Step Process

1.

ECR

Change Request

2.

ECN

Change Notice

3.

ECO

Change Order

4.

ECV

Change Verification

16


Change Verification

• Percent of changes that were correct

• Did we get what we expected?

– Cost reduction

– Quality improvement

• If yes, great and review other parts that we can apply

the same change

• If no, start over

17


Manufacturing Engineering Change Process

ERP

PL

M

MES

CRM / SRM

LegacyOther

1.

ECR

Change Request

2.

ECN

Change Notice

3.

ECO

Change Order

4.

ECV

Change Verification

18


Integration Ideas

• Look at the product lifecycle and look for gaps

• Process view, not department view, not a

document view

• Start with a process flowchart

19

© Copyright John Cachat20

Engineering Change Process

What it actually is:

What you think it is:

What it should be:


Lesson Learned

• Traditional software development that focuses on

databases, menus, and screens is obsolete

• Listen to the people, understand their process,

and help them do it better

• Technology must not be a roadblock that

– Requires extensive training

– Requires expensive customization to fit your needs

– Forces people to adapt to the software

• Help them do their job!!!

21


Next Generation Software

“If you want the Next Generation of the workforce to

use the software, it needs to look like something

they will want to use…..”

22


Next Generation SoftwareWORKFLOW BUILT IN REPORTING

SUPPORT

MOBILE

DEVICES

23


Instant Application Platform

Instant Application

Platform

Workflow

User Interface

Templates

SecurityReports

Business Logic

API Tool Set

24


The Process (or Workflow)

2525


People, Process, Technology

Process(workflow)

Technology

People


Your Form, Your

Process, Not Their

Screen

27


Your Form, Your

Process, Not Their

Screen

28

• Little-to-no training

required

• No need to change

existing documentation

• Make their job easier

• Integration to ERP, PLM,

MES should be invisible

to User


THE DEMO

29


ECR, ECN, ECO, ECV

30


The Silico Model

3.

Technology

2.

Process

1.

People

31


Next Generation

Technology Requirements

• Requires little internal IT support

• Rapid web form development & maintenance

• Minimum to no programming required

• Intuitive and graphical workflow definition

• Integration with other applications (web services)

• Rapid updates/improvements

• Support mobile devices/tablets

• Option – Buy or Software as a Service (SaaS)

32


What is the Goal?

No Bad MaterialDo Things FasterLess Labor Increase Revenue

33


Value Proposition

� Streamline operations - faster cycle time

� Improve responsiveness – simplify work

� Increase visibility – via notifications

� Minimize risk - less variation

� Make better decisions – access to data

� Reduce IT costs - less development time

� Enforce governance – compliance & audit trail

Bottom Line – Reduce Risk & Save Money!!!

34


About Us

John Cachat

[email protected]

Contact

Proven expertise in business

information systems

Rapid Solution

Development™ process

ServicesAssess Current Status

Develop Short and Long

Term Plans

Develop Specific Solutions

to Your Problems

Assist in ROI Analysis


FREE Proof of Concept

WeWe


Integration Technology To Solve Business Problems in Manufacturing

&

Contact:

John Cachat

[email protected]

Copy of Presentation

&

Request a Demo

Visit:

http://peproso.com/webinars

Future Webinars

Date post:	20-Jan-2015
Category:	Business
Upload:	john-cachat
View:	92 times
Download:	10 times