8/8/2019 Gestion y Optimizaciuon de Procesos Poldat

http://slidepdf.com/reader/full/gestion-y-optimizaciuon-de-procesos-poldat 1/1

www.iitgroup.comESPAÑA PORTUGAL

Centro Empresarial EuronovaRonda de Poniente, 2 Ofic. 16 B-F

28760 Tres Cantos – MADRIDTlf. +34 91 5902951 Fax.: +34 91 8042196

Rua da Misericórdia, 761200-273 LISBOA

Tlf.: +351 21 3210175 Fax: +351 21 3210299

So luc iones para l a Gest ión y Autom at izac ión de P rocesos

Gestión y Optimización de ProcesosGestión y Optimización de Procesos

- Success Stories -

Title : Clarks Shoes

“Casewise helped us to understand our supply 

chain. It showed us how different parts of thecompany work in different ways, and which of our   systems are mission critical……The result was a3-D model of Clarks’ processes, systems & data.This has helped us to plan improvements, resolvecertain data issues, and will ultimately help usintegrate our IT systems” 

- Bernard Faughey, Clarks Shoes

Background

Casewise was originally employed at Clarks to understand anddocument internal business processes. It was then decided to

build on these models to include the data, location andtechnology dimensions. The main objectives were to: 1)

resolve data conflicts & duplications, 2) provide process maps

to key business areas, and 3) provide data models to ITdepartments.

The Modelling Requirement

Clarks wanted to create a model of the retail supply chains,

which would enable:

•  Understanding of the differences in supply chains

across the company

•  Identification of the most important systems

•  Identification of business ownership of processes and

data•  Data consistency checking at every level

The Approach Taken

Clarks created a ‘top-down’ enterprise model, which includedall the POLDAT dimensions (Process, Organization, Location,

Data, Application and Technology). Due to the objectives of the

project, the model was also divided into two ‘subject areas’:

logical - showing the organizational, process and businessrequirements, and physical - representing the real-lifeapplications, IT infrastructure and data entities & attributes.

•  1. High-level ‘end-to-end’ view of processes(logical side) and high-level view of 

applications (physical side) The first step was tocreate a high-level ‘end-to-end’ view of the supply

chain (in effect, a value chain diagram), and a high-

level hierarchy of Clarks’s major computerapplications. Due to the size and complexity of 

operations, this was felt to be a good starting pointto ‘overview’ operations.

•  2. Connection of high-level processes and high-

level IT systems Each of the processes (‘process’ 

objects) on the high-level value chain were then

linked to the IT system on which they depends(‘application’ objects in the physical side). This wasdone using Corporate Modeler’s ‘Association’ dynamic

object linking.

•  3. Decomposition of high-level processes intoprocess flow diagrams A further level of detail wasthen added beneath each of the major processes in

the high-level value chain. In a consultation with

process owners and operatives, Process Dynamicsdiagrams were created, and added as ‘drill-downs’ 

underneath process steps. Each showed thechronology and control of a procedure, and provided

four major benefits:

•  Identification of variations on the same

processes

•  Visualization of ‘cross-functional’ customer

facing processes

•  Location of organizational hand-off issues•  Visual identification of ‘best practice’ 

procedures

•  4. Mapping of data onto processes (Logical

Side) The next step was to map the data which eachprocess step uses to perform its function. This was

done by firstly importing an existing database of Clarks’ data entities & attributes into Corporate

Modeler using AutoModeler. CRUD matrices werethen used to associate these data entities and

attributes with the relevant processes.

•  5. Detailing applications & IT infrastructure

(Physical Side) ‘Drill-downs’ and associations werethen created to detail the high-level major

applications, and link them to the IT hardware they

run on (‘Technology’ objects).

•  6. Linking to Physical Data Model The final step inthe model construction was to link both sides of themodel to a Physical Data Model imported from Oracle

Designer. This was done map mapping ‘PhysicalEntity’ & ‘Physical Data’ type objects to the Logical

entities & attributes within Corporate Modeler (usingthe ‘Issue’ classification). This completed the ‘three-

dimensional’ model, which then covered the complete ‘end-to-end’ supply chain from high-level business

right down physical data.

Remote Working & Publishing Much of the workwas done remotely, where users would downloadsections of the model to their laptops (sub-models),

work on them, and then re-combine the sub models

with the master model in the shared objectrepository.

The project has been seen as a success, and to communicatethe model to a wider audience the next planned stage is to webpublish the models on the company intranet using Corporate

Publisher HTML.

Key Benefits

Clarks site some of the main advantages of using Corporate

Modeler as:

•  Full POLDAT support represented all aspects of the

supply chain in one consistent model.

•  The diagramming techniques provided clear notationthat could be understood by non-technical process

owners, and hence aided consultation, knowledgegathering and presentation of plans.

•  Its flexibility enabled the model to be focused on

process-system-data relationships