using root cause analysis to promote your information supply chain

EXTERNAL USE

SETH PARKDN ISC MANAGER

10 OCT 2016

TC DOJO PRESENTATION

USING ROOT CAUSE ANALYSIS TO PROMOTE INFORMATION SUPPLY CHAIN

EXTERNAL USE2

Motivation: cultural change around documentation quality

• Documentation errors are seen as documentation problems

• Organizations fail to see documentation as part of the quality process

Old perception

Organizations are missing out on their greatest insight into operational excellence

EXTERNAL USE3

Motivation: cultural change around documentation quality

• Documentation errors are seen as documentation problems

• Organizations fail to see documentation as part of the quality process

Old perception

• Documentation errors result from mishandled information

• Documentation quality is a reflection of internal product development process quality

New perception

Organizations are missing out on their greatest insight into operational excellence

Organizations focus on the internal transfer of information for the good of all

EXTERNAL USE4

Durable template for documentation error “5 Why” analysisIncorrect information in documentation

Why?

EXTERNAL USE5


Missed information hand-offWhy

?Why

?

EXTERNAL USE6


Missed information hand-off

Human error (missed email, copy/paste error, etc.)

Why?

Why?

Why?

EXTERNAL USE7




No formal method for handling information

Why?

Why?

Why?

Why?

EXTERNAL USE8





Fundamental gap in information flowWhy

?Why

?Why

?Why

?Why

?

EXTERNAL USE9

Durable template for documentation error “5 Why” analysis

Ineffective get-well plans:• “Better/more reviews in the future”• “Create/update checklist”

Incorrect information in documentation




Fundamental gap in information flowWhy

?Why

?Why

?Why

?Why

?

Need systemic solutions:• Formalize transfers with data standards• Institutionalize transfers within PMO

CONFIDENTIAL AND PROPRIETARY10

WHY YOU NEED AN INFORMATION SUPPLY CHAIN

EXTERNAL USE11

Management doesn’t value untraceable systems

Without clear traceabilty

If you cant trace errors back to the root cause, it’s a documentation error.

Fix plan strategy

• Seen as production capacity problem• Prefer resource quantity over quality• Disconnected from business strategy

? ?Copy/paste,“save as”

What is traceabilty?

Traceability is having a system where you can predict the outcome, and if something goes wrong, you can systematically diagnosis it.

Business people loath uncertainty and open-ended systems.

Documentation often falls in this bucket and rarely gets a seat at the adult table.

EXTERNAL USE12

Make documentation traceable

With clear traceabilty

Documentation errors expose product development quality issues.

Role of ID resources

• Seen as process quality function • Prefer knowledgeable ID staff• Encourages continuous improvement• Valuable partner in business strategy

Become the quality device

Tie into mission critical product development systems.

Leverage same quality standards and development phase gates as mission critical functions.

Become a solution partner for enabling automation of human-readable content where possible.

EXTERNAL USE13

As a critical business strategy partner…

Documentation quality provides critical leading insight into the quality of product development processes that could result in lagging costs (incidents, schedules)

(Program Management)

Documentation errors are actually indications product development deficiencies, which are serviceable using normal process improvement techniques

(Quality Organization)

Investments in unifying product development and documentation workflow increase internal efficiency and customer success

(Operational Excellence)

EXTERNAL USE14

CULTURAL REVOLUTION

(THROUGH RESULTS)

EXTERNAL USE15

How to turn a battleship#1: Emphasize the importance of information transactions

(paint a picture that resonates within your organization)

#2: Quality Assurance is your best friend, not the enemy(sometimes they actually have budget)

#3: Be proactive about quality risk in the system(where is copy/paste/reformat or “save-as” used?)

#4: Roll out “information supply chain” initiative(propose how to optimize hand-offs and single source)

#5: Go to the gemba and make an offer they cant refuse(integrate, don’t recreate)

EXTERNAL USE16

#1: EMPHASIZE THE IMPORTANCE OF INFORMATION TRANSACTIONS

(PAINT A PICTURE THAT RESONATES WITHIN YOUR ORGANIZATION)


Engineering is information work.

Product development is information workflow.

Information supply chain is a product development strategy for

the information age.

EXTERNAL USE19

#2: QUALITY ASSURANCE IS YOUR BEST FRIEND, NOT THE ENEMY

(SOMETIMES THEY ACTUALLY HAVE BUDGET)

EXTERNAL USE20

Speak their language

A root cause is …

an initiating cause of either a condition or a causal chain that leads to an outcome or effect of interest. Commonly, root cause is used to describe the depth in the causal chain where an intervention could reasonably be implemented to improve performance or prevent an undesirable outcome.

-wikipedia

An information supply chain is …

the traceable series of information transactions that occur during the product development lifecycle, which allows traditional root cause analysis techniques to be used to identify and address sources of errors that would otherwise appear in product endpoints including, but not limited to, technical documentation.

-seth

https://en.wikipedia.org/wiki/Root_cause

EXTERNAL USE21

#3: BE PROACTIVE ABOUT QUALITY RISK IN THE SYSTEM

(WHERE IS COPY/PASTE/REFORMAT OR “SAVE-AS” USED?)

EXTERNAL USE22

Quality incident reviews… what happens when you’re not there

Settings summary table

incorrect

Change done in only one place

Summary table manually

maintained

Summary table not auto compiled

No automated system

Why?

Why?

Why?

Why?

EXTERNAL USE23



incorrect



maintained


No automated system

Why?

Why?

Why?

Why?

…therefore, we need to:

• Conduct more reviews• Add this to the checklist

EXTERNAL USE24



incorrect



maintained


No automated system

Why?

Why?

Why?

Why?


• Conduct more reviews• Add this to the checklist Wrong!

You need an automated system!

EXTERNAL USE25



incorrect



maintained


No automated system

Why?

Why?

Why?

Why?


• Conduct more reviews• Add this to the checklist Wrong!

You need an automated system!

This happens because of the old perceptions:

“Documentation errors are seen as documentation problems”

EXTERNAL USE26

#4: ROLL OUT “INFORMATION SUPPLY CHAIN” INITIATIVE

(PROPOSE HOW TO OPTIMIZE HAND-OFFS AND SINGLE SOURCE)

EXTERNAL USE27

Information architecture

Structured content that flows through the supply chain

Product data demand

Network of information dependencies

Data flow automation

Rules-based electronic workflow engine

Define your information supply chain domains

EXTERNAL USE28

Define your ISC basic formula

EXTERNAL USE29

Define your innovation vs. standards strategy

Backend process

DITA generation collapses complexity

Innovation discovers best solutions

DITA from various flows integrated in the CCMS by maps

DITA CCMS

Differentiation where it adds value

Standards and Off-the-Shelfwhere it doesn’t

Engineering repo

DITA Generator Export/import

Product development Publication management

Services…Simple DITA

EXTERNAL USE30

Define content assembly strategy DITA CMS

Registers(IP-XACT)

Git(SW .h)

Pin Data(XML)

Parametrics(XML)

regs.dita

chapter.dita

TGI

Doxygen

Origen

Origen

api.dita

pinlist.dita

bga.svg

specs.dita

Marketplace of innovation allowing unconstrained domain experts to develop automation.

The only requirement is that the output must be valid DITA

regs.dita

chapter.dita

api.dita

pinlist.dita

bga.svg

specs.dita

Sync

.dita

.dita

.dita

.dita

.dita

Web

PDF

EXTERNAL USE31

#5: GO TO THE GEMBA AND MAKE AN OFFER THEY CANT REFUSE

(INTEGRATE, DON’T RECREATE)

EXTERNAL USE32

Gemba: the “real place”

Gemba is a Japanese term meaning "the real place."

In business, gemba refers to the place where value is created; in manufacturing the gemba is the factory floor.

In lean manufacturing, the idea of gemba is that the problems are visible, and the best improvement ideas will come from going to the gemba.

In quality management, gemba means the manufacturing floor and the idea is that if a problem occurs, the engineers must go there to understand the full impact of the problem…

https://en.wikipedia.org/wiki/Gemba

EXTERNAL USE33

Example: semiconductor pin data flow

Before

Investing in more document reviews is like investing in the cover-up.

EXTERNAL USE34


Customer

BSDL

IBIS

OrCAD

Docs

Tools

Pin Ruby(Origen)Assignments

Pin list

AfterBefore

EXTERNAL USE35


Customer

BSDL

IBIS

OrCAD

Docs

Tools

Pin Ruby(Origen)Assignments

Pin list

AfterBefore

“Solving the root problem increases overall system qualitywhile preventing future similar documentation escapes.”

EXTERNAL USE36

And then there’s the simple value of automation92 pages of tables and 5 pages of full color images are generated from data-driven flow using same data source as Test Engineering. Option A: fix the data flow

problem and update docs to reflect design changes within minutes

Option B: hire an army of low-cost labor to create and maintain docs per design changes

TM

Confidential and Proprietary | 37

hand created

PinXML

SpecML

SpecML

hand created

copy/paste

hand created

Hand cre-ated15%

Pin XML30%

SpecML53%

Percent by page count

ISC status: 83% automated, single-sourced with test engineering

TM

External Use | 38

Packaging

Apps/SoC

SoC/Chassis arch

Data SheetPin list

Mem map def

RCW

HW design / DFTBallmap

DFT scan chain

ISC Pins

Pin list

BGA

SoC specs

IP specs

ISC Specs

IP design

IP specs

SoC specs & IP overrides

Features

Ordering info

Case outline

case outlines

Features

Overview info

ISC model integrationISC Regs

Reg defs

SoC paramsRef manArch def

IP blocks

Overview info

Overview info

Signals

Modes

Registers

Functional

Mem map

Params

ISC information architecture (typical semiconductor)

EXTERNAL USE39

QUESTIONS?

https://www.linkedin.com/in/sethpark