These models are used to contain business processes and for organizational design

12
Each Capability Area is further defined by Major Service Functions accessed by drilling down - # 4 is active for this demonstration This is the top level of Proact’s Retail Service Function Model showing the five Capability Areas. Service Functions represent the Essential Operational Capabilities of the Enterprise

description

This is the top level of Proact’s Retail Service Function Model showing the five Capability Areas. Service Functions represent the Essential Operational Capabilities of the Enterprise. - PowerPoint PPT Presentation

Transcript of These models are used to contain business processes and for organizational design

Each Capability Area is further defined by Major Service

Functions accessed by drilling down - # 4 is active for this

demonstration

This is the top level of Proact’s Retail Service Function Model

showing the five Capability Areas. Service Functions represent the

Essential Operational Capabilities of the Enterprise

This Service Function Model shows the five Major Service Functions in Capability

Area 4 with Service Flows defining the Relationships between SFs and External

Entities (Customers)

Each Major Service Function is further defined by Service Functions accessed by

drilling down - # 4.2 is active for this demonstration

Each Service Function is then further defined by another level of

decomposition or as a Basic Service Function. Click Here!

This is the next level of decomposition of the

Service Function Model showing the five Service Functions comprising 4.2

Sales Creation and Solution Support and their Service Flows

Proact builds a Matrix of all Create/Use Relationships from which System Families

are identified. Click Here for sample!

This is a Basic Service Function Model showing all Service Relationships AND all the Information Subjects both Used and

Created by this BSF! There are 170 BSFs and over 650 Information Subjects

in this Retail Reference Model!

These models are used to contain business processes and for

organizational design

3.9

.5

V

en

do

r R

ela

tion

ship

Ma

na

gem

en

t

3.9

.6

M

an

ufa

ctu

rin

g V

end

or

Ca

pab

ility

Ass

mt

4.1

.1

S

ale

s &

Se

rvic

e O

pe

ratio

ns

Ma

na

ge

me

nt

4.1

.2

C

ha

nn

el P

ers

on

nel

Sch

ed

ulin

g

4.1

.3

M

erc

ha

nd

ise

& P

arts

Pla

cem

en

t

4.1

.4

I

n-C

ha

nne

l Pre

sen

tatio

n M

ain

ten

an

ce

4.1

.5

C

ha

nn

el O

pe

ratio

ns

Au

diti

ng

4.1

.6

C

ha

nn

el O

ps

Pe

rfo

rma

nce

Me

asu

rem

en

t

4.2

.1

N

ee

ds

Qu

alif

ica

tion

& S

olu

tion

Pro

po

sal

4.2

.2

C

on

figu

ratio

n G

en

era

tion

4.2

.3

P

rod

uct

& S

olu

tion

Su

pp

ort

4.2

.4

S

olu

tion

Ava

ilab

ility

Ass

ess

me

nt

4.2

.5

C

ust

om

er

Re

turn

s A

uth

ori

zatio

n

4.3

.1

C

ust

om

er

Ord

er

Pro

cess

ing

4.3

.2

T

en

de

r, R

eb

ate

& A

cco

un

t P

roce

ssin

g

4.3

.3

F

rau

d Id

en

tific

atio

n

4.4

.1

S

erv

ice

Ord

er

Man

ag

em

en

t

4.4

.2

P

rod

uct

Act

iva

tion

4.4

.3

P

rod

uct

In

sta

llatio

n

4.4

.4

S

erv

ice

Eq

uip

me

nt

& W

ork

Are

a M

gm

t

4.4

.5

P

rod

uct

Re

pa

ir &

Pre

ven

tive

Ma

int

4.5

.1

L

oya

lty M

an

ag

em

en

t

4.5

.2

C

ust

om

er

Issu

e M

an

ag

em

ent

402.07 Product Sales Analysis C402.08 Product Sales Analysis by Market C402.15 Customer Gift Registry C M402.03 Customer Requirements & Expectations C U402.06 Customer Solution Environment C U U U302.06.02 Inventory Allocation Requests C U404.03 Transport Allocation Request C U402.11 Proposed Pricing C402.1 Proposed Solutions C403.01 Rainchecks U U U C U404.02 Service Allocation Request C U U402.09 Customer Product Configurations U C400.02 Customer Solutions Support Log C U402.14 Vendor/ Provider Product Support Issues U C402.01 Product & Solution Availability U C401.03 Customer Return Authorization C U401.04 Customer Return Rejection C U U

Sales Support Systems Family

This is a small cross-section of the Create/Use Matrix. It is generated automatically by the Proact Toolkit from the contents of the Basic Service Function (BSF) Models. The Matrix shows the relationship (Creates, Modifies, Used By) between BSF’s and Information Subjects. The Create/Use Matrix is the link from the Operational View into the Systems View as Systems Families are defined here using affinity analysis. The full Matrix identifies 29 Systems Families. This sample show the “Sales Support Systems Family”. To view Reference Models for this Systems Family Click Here.

Each System Family is used to create Reference System Models.

Click Here!

These are the five System Families in the Customer Experience –

Sales and Service Capability Area.

Each System Family is further modeled to show the Information Exchanges between Families.

Click Here for sample!

This is Reference System Model for the Sales Support System Family. It shows eight different types of Applications within the Family plus the related group of Information Subjects for which they are responsible. This is used to classify

existing inventory of systems and to begin Target Systems Development

Continue

At this point we switch to Target

System Architecture Development for the System Family. Click Here!

This is an additional type of System Reference Model called a System Family Spider Diagram. It

shows all required information exchanges between the Sales Support System Families and other Systems Families in the model. It is derived from the

Create/Use Matrix which reflects the operational requirements

Continue

Each Reference System Family is also used to create a Target Information

Exchange Model. Click Here!

These are the ten Target Systems in the Sales Solution System Family and their associated Data Stores. They represent opportunities for consolidating existing solutions

while addressing need for diversification and distribution of applications.

Once External Flows are resolved, we address exchanges within the

System Family. Click Here!

This is a Systems Family Information Exchange model for Sales Solution System Family. It shows how we plan to use Integration Systems (Hubs, Data Ware Houses, Portals, and ETL Systems) to connect System Families

This is the Systems Information Exchange Model for the Target

Systems within the Sales Support System Family. It shows which

System is responsible for receiving or requesting information exchanges through the Integration Systems

These Target System Architecture Models are then used to design each Target

System, each Data Store and each Information Exchange for

each step in the planned Migration.

Proact also supports the development of Target IT

Infrastructure Models to support these Target Systems based

again on Reference Models (Not shown).

Conclusion

This Concludes the Demo

We would like to remind you that this demonstration only covered models in the Operational and Systems Views of the Proact Framework.

It also illustrated a small sampling of the Proact Retail Industry Reference Model.

For more information on the capabilities of Proact and our extensive Industry Reference Models please contact us

Double Click to restart the Demo

Close this window to return to the Proact Website