Ddz project new-approach-091124
-
Upload
saco-heijboer -
Category
Design
-
view
15 -
download
0
Transcript of Ddz project new-approach-091124
![Page 1: Ddz project new-approach-091124](https://reader031.fdocuments.in/reader031/viewer/2022022203/5873d3ea1a28ab9d168b6c21/html5/thumbnails/1.jpg)
A new approach for refurbishment projects Saco Heijboer - project manager NedTrain
24 November 2009
![Page 2: Ddz project new-approach-091124](https://reader031.fdocuments.in/reader031/viewer/2022022203/5873d3ea1a28ab9d168b6c21/html5/thumbnails/2.jpg)
2
Overview
• About NedTrain • A projects as it should be • Questions • The reality that isn’t any help either • The alternative approach • Goals and stake holders • Baselines and control loops • The benefits
![Page 3: Ddz project new-approach-091124](https://reader031.fdocuments.in/reader031/viewer/2022022203/5873d3ea1a28ab9d168b6c21/html5/thumbnails/3.jpg)
3
NedTrain: Who are we? • Part of Dutch Railways • Maintenance of rolling stock • € 400 million turnover • 3.000 employees • 3.000 units (coaches and locomotives) • Established all over the Netherlands:
• 35 Service locations • 5 Maintenance locations • 2 Overhaul locations (1 also refurbishment)
• 7x24 at your service!
![Page 4: Ddz project new-approach-091124](https://reader031.fdocuments.in/reader031/viewer/2022022203/5873d3ea1a28ab9d168b6c21/html5/thumbnails/4.jpg)
4
NedTrain goals
• For service and maintenance: • Development towards ‘Maintenance Integrator’
• For refurbishment & overhaul: • Development towards • ‘System Integrator’
• Key aspects: • Connect disciplines • Connect information • Connect supply chain
• Ambition to become “Best in class”
![Page 5: Ddz project new-approach-091124](https://reader031.fdocuments.in/reader031/viewer/2022022203/5873d3ea1a28ab9d168b6c21/html5/thumbnails/5.jpg)
5
a project as it should be
• Define Scope and requirements • Define constraints (planning, cost, means, etc.) • Design the train conform requirements • Verify whether the requirements are met • Deliver trains • During the project: manage scope changes and make
sure the customer is paying for them.
![Page 6: Ddz project new-approach-091124](https://reader031.fdocuments.in/reader031/viewer/2022022203/5873d3ea1a28ab9d168b6c21/html5/thumbnails/6.jpg)
1
solution finding principle designing is a process of generating possible solutions and selecting the best one with respect to all applicable requirements
divergence convergence requirements
brainstorms creative process
looking for solutions
filtering evaluation
making choices
solution
![Page 7: Ddz project new-approach-091124](https://reader031.fdocuments.in/reader031/viewer/2022022203/5873d3ea1a28ab9d168b6c21/html5/thumbnails/7.jpg)
7
Scope change control
• Define the requirements as detailed as you can • Include requirements about maintainability, weight, energy
consumption, environment friendly solutions, etc. • Control deviations of requirements • Make a decision loop with your customer to deal with those
deviations and to manage additional cost
![Page 8: Ddz project new-approach-091124](https://reader031.fdocuments.in/reader031/viewer/2022022203/5873d3ea1a28ab9d168b6c21/html5/thumbnails/8.jpg)
8
And now....
![Page 9: Ddz project new-approach-091124](https://reader031.fdocuments.in/reader031/viewer/2022022203/5873d3ea1a28ab9d168b6c21/html5/thumbnails/9.jpg)
9
Questions
• Is an extensive scope and requirement description a warranty for getting what you want?
• Is a fixed and massive contract a warranty for getting what you want?
• Can you describe in advance exactly what you want? • Is the cheapest supplier always the preferred one? • What is smarter: helping your supplier to solve his
problem or pointing out to him which penalty is applicable if he doesn’t solve it?
• The questions above are relevant for all supply chain parties.
![Page 10: Ddz project new-approach-091124](https://reader031.fdocuments.in/reader031/viewer/2022022203/5873d3ea1a28ab9d168b6c21/html5/thumbnails/10.jpg)
10
The reality in real life projects
• During a project the scope is always evolving. • Several requirements will remain contradictory. • The demands of all stake holders can never be met. • Design decisions always come to soon • It’s not always clear how to meet requirements
![Page 11: Ddz project new-approach-091124](https://reader031.fdocuments.in/reader031/viewer/2022022203/5873d3ea1a28ab9d168b6c21/html5/thumbnails/11.jpg)
1
solution finding principle again • designing is an iterative process of generating
possible solutions and selecting the best one with respect to all applicable requirements
divergence convergence requirements
brainstorms creative process
looking for solutions
filtering evaluation
making choices
solution
![Page 12: Ddz project new-approach-091124](https://reader031.fdocuments.in/reader031/viewer/2022022203/5873d3ea1a28ab9d168b6c21/html5/thumbnails/12.jpg)
12
Alternative approach
• Define the requirements not too detailed and as functional as possible.
• Define the goals of the requirements. • Determine which performance shall be optimised. • Allocate targets for the performance to be optimised. • Train your design teams. • Give the design teams decision rules and tools. • Take the whole chain into account. • Make a decision loop with your stake holders to deal with
those optimisations (budget change control)
![Page 13: Ddz project new-approach-091124](https://reader031.fdocuments.in/reader031/viewer/2022022203/5873d3ea1a28ab9d168b6c21/html5/thumbnails/13.jpg)
13
Goals and stake holders
• Design for reliability • Design for maintenance • Design for assembly • Design for logistics • Design for environment • Design for weight • Design to cost • Design for cleaning • Design for ...
![Page 14: Ddz project new-approach-091124](https://reader031.fdocuments.in/reader031/viewer/2022022203/5873d3ea1a28ab9d168b6c21/html5/thumbnails/14.jpg)
14
Communicating vessels
• Balancing by levelling project goals • E.G.: adding cost and weight might reduce LCC and Reliability
Ene
rgy
Wei
ght Rel
iabi
lity
Life
Cyc
le C
ost
Pro
ject
Cos
t
![Page 15: Ddz project new-approach-091124](https://reader031.fdocuments.in/reader031/viewer/2022022203/5873d3ea1a28ab9d168b6c21/html5/thumbnails/15.jpg)
15
Optimisation iteration
• Start with top down targets in the first baseline • Let the design teams create a bottom up baseline based on
their conceptual designs • Update your baselines regularly,
at least with each design review • Formulate business cases for difficult or important design
decisions.
![Page 16: Ddz project new-approach-091124](https://reader031.fdocuments.in/reader031/viewer/2022022203/5873d3ea1a28ab9d168b6c21/html5/thumbnails/16.jpg)
16
iterative baseline principle
Configuratie info
New baseline budgets
generate solutions
analyse solutions
select solution
define problem
Realisation
Keep in control And give room for control to the team
“Closed loop” Iteration process
Baseline budgets
![Page 17: Ddz project new-approach-091124](https://reader031.fdocuments.in/reader031/viewer/2022022203/5873d3ea1a28ab9d168b6c21/html5/thumbnails/17.jpg)
17
Customer intimacy
• For all involved parties: • Open communication is essential • Close co-operation is essential • Looking for the benefit of all parties is essential • Sharing available information is essential
![Page 18: Ddz project new-approach-091124](https://reader031.fdocuments.in/reader031/viewer/2022022203/5873d3ea1a28ab9d168b6c21/html5/thumbnails/18.jpg)
18
The benefit of it all
• Better designs: not just performing well, but optimised for all relevant aspects!
• An involved and satisfied customer • Involved and satisfied stake holders in general • And therefore: less surprises when the train is delivered.
![Page 19: Ddz project new-approach-091124](https://reader031.fdocuments.in/reader031/viewer/2022022203/5873d3ea1a28ab9d168b6c21/html5/thumbnails/19.jpg)
19
Thank you for your attention