The challenges with PLM governance at Volvo ... - PDT Europe 2013
The challenges with PLM governance at Volvo ... - PDT Europe 2013
The challenges with PLM governance at Volvo ... - PDT Europe 2013
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<strong>The</strong> <strong>challenges</strong> <strong>with</strong> <strong>PLM</strong> <strong>governance</strong> <strong>at</strong> <strong>Volvo</strong><br />
Trucks and the transform<strong>at</strong>ion of business into a<br />
service-oriented and event-driven architecture<br />
<strong>PDT</strong> <strong>Europe</strong> 2012
Agenda<br />
1. Introduction<br />
2. Prerequisites<br />
3. Value analysis<br />
4. Change management approach<br />
5. Roadmap<br />
6. Some artifacts<br />
<strong>Volvo</strong> Group Trucks Technology<br />
Process Vehicle Architecture & DDTS, Trond Zimmerman<br />
3 2012-09-25
<strong>Volvo</strong> Group Organiz<strong>at</strong>ion<br />
Governance<br />
Group Trucks<br />
Sales &<br />
Marketing<br />
EMEA<br />
Group Trucks<br />
Sales &<br />
Group Trucks<br />
Sales & Group Trucks Group Trucks<br />
Marketing Marketing Oper<strong>at</strong>ions Technology<br />
Americas CLM APAC<br />
SCM <strong>PLM</strong><br />
70%<br />
Demand<br />
Truck Joint<br />
Ventures<br />
Construction<br />
Equipment<br />
15% 10%<br />
Business<br />
Areas<br />
Finance &<br />
Business<br />
Support<br />
Supply<br />
<strong>Volvo</strong> Group Trucks Technology<br />
Process Vehicle Architecture & DDTS, Trond Zimmerman<br />
4 2012-09-25
Implementing a Service-Oriented and<br />
Event-driven <strong>PLM</strong> Architecture<br />
Authority<br />
• Emphasized for roughly a year<br />
• Structured work through prestudy, project<br />
and hand-over to line organiz<strong>at</strong>ion<br />
(maintenance)<br />
• Setup of an oper<strong>at</strong>ional framework for<br />
project and applic<strong>at</strong>ion portfolio<br />
management<br />
• Implement<strong>at</strong>ion mainly <strong>with</strong>in new<br />
development<br />
• This far 12-15 FTEs invested<br />
<strong>Volvo</strong> Group Trucks Technology<br />
Process Vehicle Architecture & DDTS, Trond Zimmerman<br />
5 2012-09-25
Areas of implemen<strong>at</strong>ion<br />
Main work items<br />
<br />
Refine of IT and <strong>PLM</strong> str<strong>at</strong>egy<br />
<br />
Service directory description, service lifecycle model<br />
<br />
<strong>PLM</strong> Architecture descriptions<br />
<br />
Benefit argument<strong>at</strong>ions and way forward<br />
<br />
AS-IS & TO-BE showcases, and “mapped” details in<br />
user scenarios/ inform<strong>at</strong>ion mappings and service<br />
definitions (class diagrams, XML schemes)*<br />
<br />
Process and instructions for architecture and services<br />
<strong>governance</strong><br />
<br />
Applic<strong>at</strong>ion and adapt<strong>at</strong>ion of available<br />
infrastructure components<br />
<br />
Initi<strong>at</strong>ion of, and change of projects<br />
<br />
Plans and prepar<strong>at</strong>ions for hand-over to line org.<br />
<strong>Volvo</strong> Group Trucks Technology<br />
Process Vehicle Architecture & DDTS, Trond Zimmerman<br />
6 2012-09-25
Agenda<br />
1. Introduction<br />
2. Prerequisites<br />
3. Value analysis<br />
4. Change management approach<br />
5. Roadmap<br />
6. Some artifacts<br />
<strong>Volvo</strong> Group Trucks Technology<br />
Process Vehicle Architecture & DDTS, Trond Zimmerman<br />
7 2012-09-25
<strong>Volvo</strong> Group IT Targets<br />
IT Solutions Integr<strong>at</strong>ion<br />
• Secure controlled end-to-end process<br />
availability of IT<br />
• Reduce oper<strong>at</strong>ion and maintenance cost<br />
• Increased speed of change in IT solutions<br />
• Improved follow-up th<strong>at</strong> implement<strong>at</strong>ions<br />
are done according to decisions<br />
<strong>PLM</strong><br />
• Process efficiency<br />
• Connection (harmoniz<strong>at</strong>ion) of <strong>PLM</strong><br />
• Collabor<strong>at</strong>ion <strong>with</strong> external partners<br />
<strong>Volvo</strong> Group Trucks Technology<br />
Process Vehicle Architecture & DDTS, Trond Zimmerman<br />
8 2012-09-25
GUI for<br />
contexts<br />
…<br />
Positioning<br />
db<br />
…<br />
Geometry<br />
conversion<br />
Positioning<br />
…<br />
Take-off out of the VPDM Solutions Portfolio<br />
CAD X<br />
CAD db X<br />
PDM<br />
CAD Y<br />
CAD db Y<br />
Virt Prot<br />
VM X<br />
VM Z<br />
CAD X CAD Y<br />
CAD db<br />
PDM<br />
CAD db adapter PDM adapter<br />
<strong>PLM</strong> Service Bus<br />
…<br />
Prototypes<br />
LWG X<br />
Eng db<br />
<strong>The</strong> AS-IS IT solution was disharmonized <strong>with</strong><br />
overlapping solutions and stove pipe oriented<br />
<strong>The</strong> TO-BE architecture harmonizes system<br />
integr<strong>at</strong>ions into joint decoupled solution<br />
• Overlapping unsynchronized solutions<br />
• Competing virtual truths<br />
• Locked in d<strong>at</strong>a<br />
• Domino effects upon changes<br />
• Critical functions hard to realize<br />
• Today’s COTS highly customized<br />
• One overall shared solution<br />
• One consolid<strong>at</strong>ed view<br />
• Shared d<strong>at</strong>a<br />
• Decoupled applic<strong>at</strong>ions enables change<br />
• Shared improved solutions<br />
• Avoiding customiz<strong>at</strong>ion of <strong>Volvo</strong> business logic<br />
in COTS<br />
<strong>Volvo</strong> Group Trucks Technology<br />
Process Vehicle Architecture & DDTS, Trond Zimmerman<br />
9 2012-09-25
Enterprise Architecture enables best-in-class IT<br />
cooper<strong>at</strong>ion – across functions, domains, brands<br />
Inform<strong>at</strong>ion-centric <strong>PLM</strong> Architecture<br />
Business<br />
Solution<br />
General<br />
IT solution<br />
Mack<br />
<strong>Volvo</strong><br />
RT<br />
Business<br />
Processes<br />
Inform<strong>at</strong>ion<br />
Applic<strong>at</strong>ion<br />
Business<br />
Str<strong>at</strong>egy<br />
& Objectives<br />
Applic<strong>at</strong>ion Infrastructure<br />
UDT<br />
Core Infrastructure<br />
Illustr<strong>at</strong>ive<br />
Truck<br />
Critical<br />
Inform<strong>at</strong>ion centric architecture<br />
• Improve the inform<strong>at</strong>ion architecture – making<br />
inform<strong>at</strong>ion available through services via a<br />
service bus th<strong>at</strong> complies to industry standards<br />
• <strong>The</strong> inform<strong>at</strong>ion layer is the key enabler for<br />
benefits to be achieved jointly by business and<br />
IT<br />
• <strong>The</strong> inform<strong>at</strong>ion architecture and inform<strong>at</strong>ion<br />
access <strong>PLM</strong> Service architecture is an enabler<br />
for best-in-class cooper<strong>at</strong>ion in the overall<br />
<strong>Volvo</strong> Group IT community<br />
(e.g. across functions, domains, and brands)<br />
Inform<strong>at</strong>ion models<br />
<strong>PLM</strong> Arch<br />
<strong>Volvo</strong> Group Trucks Technology<br />
Process Vehicle Architecture & DDTS, Trond Zimmerman<br />
10 2012-09-25
Agenda<br />
1. Introduction<br />
2. Prerequisites<br />
3. Value analysis<br />
4. Change management approach<br />
5. Roadmap<br />
6. Some artifacts<br />
<strong>Volvo</strong> Group Trucks Technology<br />
Process Vehicle Architecture & DDTS, Trond Zimmerman<br />
11 2012-09-25
<strong>The</strong> service-oriented and event-driven <strong>PLM</strong><br />
Architecture supports corpor<strong>at</strong>e objectives<br />
Objectives<br />
Profitable growth<br />
1. Soft products and customer<br />
solutions<br />
2. Profitability and sales<br />
3. Brand value<br />
Product cycle management<br />
1. Product and service portfolio<br />
2. Innov<strong>at</strong>ion technology and<br />
concept management<br />
3. Global strength<br />
Oper<strong>at</strong>ional excellence<br />
1. Cost efficiency and Cash<br />
Flow<br />
2. People, leaders and<br />
organiz<strong>at</strong>ion<br />
3. Total quality through faultless<br />
execution<br />
Growth<br />
Expanding business means<br />
putting a strain on the existing<br />
IT architecture and infrastructure<br />
Global effective development<br />
Global co-oper<strong>at</strong>ion requires<br />
shared processes, based<br />
increasingly on shared<br />
technologies and a common<br />
architecture<br />
Efficiency, performance, and<br />
faultless execution<br />
Quick and reliable access to<br />
correct d<strong>at</strong>a on a global scale<br />
becomes a pre-requisite<br />
New <strong>PLM</strong><br />
Architecture<br />
supports <strong>with</strong><br />
Adaptive, flexible,<br />
scalable integr<strong>at</strong>ion<br />
A common integr<strong>at</strong>ion<br />
architecture <strong>with</strong> globally<br />
available standardized<br />
inform<strong>at</strong>ion services<br />
Service-based, event driven<br />
inform<strong>at</strong>ion exchange –<br />
quick and reliable inform<strong>at</strong>ion<br />
access<br />
<strong>Volvo</strong> Group Trucks Technology<br />
Process Vehicle Architecture & DDTS, Trond Zimmerman<br />
12 2012-09-25
Key business <strong>challenges</strong> th<strong>at</strong> are supported by the<br />
service-oriented and event-driven <strong>PLM</strong> Architecture<br />
Overview of key business situ<strong>at</strong>ions/ <strong>challenges</strong> supported by <strong>PLM</strong> Architecture<br />
1<br />
Replace/ upd<strong>at</strong>e<br />
existing applic<strong>at</strong>ions<br />
3<br />
Add new/ upd<strong>at</strong>ed<br />
applic<strong>at</strong>ions to<br />
IT landscape (e.g. COTS)<br />
5<br />
Implement clear<br />
master d<strong>at</strong>a, logic &<br />
info. architecture<br />
7<br />
Need to leverage<br />
(integr<strong>at</strong>ion)<br />
competences<br />
• Easier to replace or<br />
upd<strong>at</strong>e existing<br />
applic<strong>at</strong>ions due to<br />
standardized integr<strong>at</strong>ion<br />
architecture<br />
• Loose coupling via<br />
adapter makes it easier<br />
to add or replace new or<br />
COTS applic<strong>at</strong>ions<br />
• Changes and<br />
clarific<strong>at</strong>ion of the<br />
mastering of inform<strong>at</strong>ion<br />
and logic will be easier<br />
in the new architecture<br />
(e.g. service provider/<br />
consumer change)<br />
• Leverage integr<strong>at</strong>ion<br />
competences: experts<br />
for the <strong>PLM</strong> architecture<br />
can work across the<br />
whole <strong>PLM</strong> domain<br />
2<br />
Leverage existing<br />
applic<strong>at</strong>ions<br />
(prolong life)<br />
4<br />
Integr<strong>at</strong>e<br />
acquisitions/ JVs/<br />
suppliers<br />
6<br />
Maintain existing<br />
8 Change & integr<strong>at</strong>e<br />
integr<strong>at</strong>ions in<br />
changing environment business processes<br />
• Existing applic<strong>at</strong>ions<br />
can be leveraged by<br />
making logic and<br />
inform<strong>at</strong>ion available<br />
through event-driven<br />
services<br />
• Easier to integr<strong>at</strong>e<br />
partners <strong>with</strong> granular<br />
control of inform<strong>at</strong>ion<br />
access by connecting<br />
them to the <strong>PLM</strong> bus<br />
• Easier maintenance: A<br />
set of standardized<br />
services is provided to<br />
multiple consumers in<br />
the same way<br />
• Inform<strong>at</strong>ion availability<br />
more transparent and<br />
integr<strong>at</strong>ions more<br />
loosely coupled to<br />
processes – increased<br />
flexibility<br />
<strong>Volvo</strong> Group Trucks Technology<br />
Process Vehicle Architecture & DDTS, Trond Zimmerman<br />
13 2012-09-25
Agenda<br />
1. Introduction<br />
2. Prerequisites<br />
3. Value analysis<br />
4. Change management approach<br />
5. Roadmap<br />
6. Some artifacts<br />
<strong>Volvo</strong> Group Trucks Technology<br />
Process Vehicle Architecture & DDTS, Trond Zimmerman<br />
14 2012-09-25
Change management approach<br />
Way of realiz<strong>at</strong>ion<br />
• R<strong>at</strong>her large project initi<strong>at</strong>ing, <strong>with</strong> combin<strong>at</strong>ion of<br />
argument<strong>at</strong>ion and different kinds of technical<br />
competencies<br />
• Strong involvement of many other functions such as<br />
Corpor<strong>at</strong>e P&IT, IT suppliers, business functions,<br />
solution management, et cetera ...<br />
• Guidelines, rules and directives set onto ongoing<br />
project and applic<strong>at</strong>ion portfolio management<br />
• Emphasis on dependencies to company str<strong>at</strong>egies and<br />
important projects<br />
• Project support and establishment of best practices in<br />
service implement<strong>at</strong>ion<br />
• Showcases<br />
<strong>Volvo</strong> Group Trucks Technology<br />
Process Vehicle Architecture & DDTS, Trond Zimmerman<br />
15 2012-09-25
Showcases are used to investig<strong>at</strong>e a broad range of integr<strong>at</strong>ions in <strong>PLM</strong><br />
and to connecting domains, as well as a lever in articul<strong>at</strong>ing the to-be<br />
Showcases scope<br />
Product development (PD)<br />
CAD x CADdb x<br />
Program I CAD y<br />
Drawings<br />
CADdb y<br />
Electronics<br />
PCCT<br />
Project II<br />
Prototype<br />
3 4<br />
Project III Wareh. Prot. Mtrl.<br />
Purchase<br />
8<br />
Parts plan.<br />
1<br />
2<br />
6<br />
7<br />
Ext. (JV, Supp.)<br />
<br />
KOLA<br />
11<br />
12<br />
Service/ AM (DtR)<br />
Sol1<br />
Project V<br />
Sol2<br />
Sol3<br />
Sol4<br />
Sol5<br />
Sol6 Project VI<br />
Sol7<br />
Showcases<br />
•Release process<br />
•Item cre<strong>at</strong>ion/ bridging<br />
•Context cre<strong>at</strong>ion (incl. AM &<br />
virtual manufacturing)<br />
•Prototype parts ordering<br />
•Calcul<strong>at</strong>ion request<br />
(purchasing)<br />
•Manufacturing prepar<strong>at</strong>ion<br />
•Sales prepar<strong>at</strong>ion<br />
App1<br />
Project IV<br />
9 10<br />
App2<br />
Manufacturing (OtD)<br />
App3 App4 App5 App6 Sys1<br />
App7<br />
<strong>Volvo</strong> Group Trucks Technology<br />
Process Vehicle Architecture & DDTS, Trond Zimmerman<br />
16 2012-09-25<br />
Sales (StO)<br />
13<br />
Sys2<br />
Sys3<br />
•Service inform<strong>at</strong>ion & AM<br />
prepar<strong>at</strong>ion<br />
•Embedded software<br />
management<br />
•External collabor<strong>at</strong>ion
class Resolv eBOM<br />
Logical Services::<br />
1<br />
Verb<br />
Volv o<br />
Comput<strong>at</strong>ional<br />
Specific::<br />
Resolv eBOM<br />
Logical Serv ices::<br />
Serv ice<br />
Realizes<br />
<strong>Volvo</strong><br />
Comput<strong>at</strong>ional<br />
Core::Message<br />
1 Logical Services::<br />
Noun<br />
{subsets request}<br />
<strong>Volvo</strong><br />
+request<br />
Comput<strong>at</strong>ional<br />
1<br />
Core::Request<br />
Volv o Comput<strong>at</strong>ional<br />
Specific::<br />
Resolv eBOMRequest<br />
Logical<br />
Comput<strong>at</strong>ional<br />
+request<br />
{subsets response}<br />
<strong>Volvo</strong><br />
Comput<strong>at</strong>ional<br />
Core::Content<br />
- id :String<br />
<strong>Volvo</strong><br />
+response<br />
Comput<strong>at</strong>ional<br />
1<br />
Core::Response<br />
Volv o Comput<strong>at</strong>ional<br />
Specific::<br />
Resolv eBOMResponse<br />
<strong>Volvo</strong><br />
+headers<br />
Comput<strong>at</strong>ional<br />
Core::Header<br />
0..*<br />
+parameters<br />
<strong>Volvo</strong><br />
0..* Comput<strong>at</strong>ional<br />
Core::Parameter<br />
+payload<br />
0..1 <strong>Volvo</strong><br />
Comput<strong>at</strong>ional<br />
Core::Payload<br />
Volv o<br />
Comput<strong>at</strong>ional<br />
Core::<br />
Serv iceDirectiv e<br />
class Resolv eBOMRequest<br />
Logical Services:: 1 1 Logical Services::<br />
Verb<br />
Noun<br />
Volv o<br />
Comput<strong>at</strong>ional<br />
Specific::<br />
Resolv eBOM<br />
Logical Serv ices::<br />
Serv ice<br />
Realizes<br />
<strong>Volvo</strong><br />
Comput<strong>at</strong>ional<br />
Core::Message<br />
{subsets request}<br />
<strong>Volvo</strong><br />
+request<br />
Comput<strong>at</strong>ional<br />
1<br />
Core::Request<br />
Volv o Comput<strong>at</strong>ional<br />
Specific::<br />
Resolv eBOMRequest<br />
Logical<br />
Comput<strong>at</strong>ional<br />
<strong>Volvo</strong><br />
Comput<strong>at</strong>ional<br />
Core::Content<br />
- id :String<br />
+payload<br />
0..1<br />
<strong>Volvo</strong><br />
Comput<strong>at</strong>ional<br />
Core::Payload<br />
{subsets parameters}<br />
{subsets parameters}<br />
<strong>Volvo</strong><br />
+headers<br />
Comput<strong>at</strong>ional<br />
Core::Header<br />
0..*<br />
+parameters<br />
0..*<br />
<strong>Volvo</strong><br />
Comput<strong>at</strong>ional<br />
Core::Parameter<br />
Parameter::<br />
VariantSpecific<strong>at</strong>ion<br />
Parameter::<br />
ProductType<br />
Parameter::<br />
{subsets parameters}<br />
ProductClass<br />
{subsets parameters}<br />
Parameter::<br />
Factory<br />
Volv o<br />
Comput<strong>at</strong>ional<br />
Core::<br />
Serv iceDirectiv e<br />
BusinessObjectCharacteristics::<br />
{subsets headers} ProductClassCharacteriz<strong>at</strong>ion<br />
{subsets headers}<br />
{subsets headers}<br />
{subsets headers}<br />
BusinessObjectCharacteristics::<br />
ItemVersionCharacteriz<strong>at</strong>ion<br />
BusinessObjectCharacteristics::<br />
ItemCharacteriz<strong>at</strong>ion<br />
BusinessObjectCharacteristics::<br />
DesignDisicplineItemDefinitionCharacteriz<strong>at</strong>ion<br />
class Resolv eBOMResponse<br />
Logical Services:: 1<br />
Verb<br />
Volv o<br />
Comput<strong>at</strong>ional<br />
Specific::<br />
Resolv eBOM<br />
Logical Serv ices::<br />
Serv ice<br />
Realizes<br />
<strong>Volvo</strong><br />
Comput<strong>at</strong>ional<br />
Core::Message<br />
1 Logical Services::<br />
Noun<br />
<strong>Volvo</strong><br />
+response<br />
Comput<strong>at</strong>ional<br />
Core::Response<br />
1<br />
Volv o Comput<strong>at</strong>ional<br />
{subsets response} Specific::<br />
Resolv eBOMResponse<br />
Logical<br />
Comput<strong>at</strong>ional<br />
<strong>Volvo</strong><br />
Comput<strong>at</strong>ional<br />
Core::Content<br />
- id :String<br />
+payload<br />
{subsets payload}<br />
0..1 <strong>Volvo</strong><br />
Comput<strong>at</strong>ional<br />
Core::Payload<br />
Payload::<br />
<strong>PLM</strong>S2_1<br />
<strong>Volvo</strong><br />
+headers Comput<strong>at</strong>ional<br />
Core::Header<br />
0..*<br />
+parameters<br />
<strong>Volvo</strong><br />
0..*<br />
Comput<strong>at</strong>ional<br />
Core::Parameter<br />
content<br />
1<br />
Volv o<br />
Comput<strong>at</strong>ional<br />
Core::<br />
Serv iceDirectiv e<br />
<strong>PLM</strong>_core_container<br />
Inform<strong>at</strong>ionalModel::<br />
<strong>PLM</strong>_container<br />
{leaf}<br />
Workshop results shall consist of inform<strong>at</strong>ion flow, high-level TO-<br />
BE solution, inputs for details and the time plan<br />
1<br />
Showcase results overview<br />
KOLA<br />
1<br />
Protus<br />
2<br />
0<br />
2<br />
Inform<strong>at</strong>ion flow<br />
(AS-IS and<br />
required TO-BE<br />
inform<strong>at</strong>ion flow)<br />
BOM for TO<br />
XLS<br />
”BOM<br />
valid<strong>at</strong>ion”<br />
8<br />
JENA<br />
SAP<br />
Architectural overview<br />
Complete KOLA db*<br />
Daily** b<strong>at</strong>ch, fl<strong>at</strong>file, VCOM<br />
3<br />
Upd<strong>at</strong>e order/ st<strong>at</strong>us<br />
R/R synch. Webservice<br />
(WAS) periodic + on<br />
demand (some manual<br />
CSV TOB to JENA)<br />
M<strong>at</strong>ch invoice<br />
4<br />
TOB<br />
9<br />
10<br />
5'<br />
Acknowledge<br />
7 Part order info<br />
F/F VCOM, b<strong>at</strong>ch 1-3x /day<br />
5<br />
PPR<br />
VCOM over MQ bridge<br />
b<strong>at</strong>ch (~5x /hr)<br />
Part order<br />
GPS<br />
6<br />
Supplier<br />
Purpose/ process support<br />
0• Release part in KOLA, wait for transfer to PROTUS)<br />
1• Specify Test Object (TO) in Protus<br />
2• Engineering managers valid<strong>at</strong>e & approve Test Object (BOM)<br />
in Protus (digital review)<br />
3• Export specific BOM (list of parts for TO, containing build series<br />
of up to 50 trucks), some adjustments, cre<strong>at</strong>e Prototype Parts<br />
Aquisition (PPA) in TOB, import XLS into PPA in TOB<br />
4<br />
• Manipul<strong>at</strong>e BOM in TOB (e.g. replace cabling part numbers <strong>with</strong><br />
fictional cabling numbers) – Protus is not notified of changes<br />
(XLS sheet like manipul<strong>at</strong>ing functionality)<br />
5<br />
• Send Prototype Parts Requisition from TOB to GPS -4 modes-<br />
<strong>The</strong>n GPS acknowledges back to TOB 5' for exception handling<br />
6<br />
• Cre<strong>at</strong>e part orders to suppliers in GPS<br />
7• Transfer part order inform<strong>at</strong>ion to JENA (either <strong>at</strong> prototype<br />
order level or <strong>at</strong> order line level in add/upd/cancel mode)<br />
8• Carry out delivery control (e.g. receive goods, store goods,<br />
m<strong>at</strong>ch invoice)<br />
9• Transfer upd<strong>at</strong>ed order/ delivery st<strong>at</strong>us from JENA to TOB<br />
10 • Assign packages to assembly st<strong>at</strong>ions in prototype plant<br />
(e.g. Tuve prod. plant)<br />
Type of integr<strong>at</strong>ion<br />
• Manual XLS export/ import for Protus-TOB<br />
• VCOM #916, #926, #927, #915, #925 for GPS-JENA<br />
• VCOM #301 for TOB-GPS #302, #303 for GPS-TOB<br />
• JENA-TOB : Webservice synchronous Request/Response<br />
High level TO-BE<br />
Approach<br />
Variant<br />
string<br />
(KML)<br />
3<br />
Timeline/ roadmap<br />
4 Service descriptions<br />
Product<br />
Class<br />
Item to<br />
Variant<br />
structure<br />
link<br />
Part<br />
Part<br />
version<br />
5<br />
Service Details – Request part Details – Response part<br />
Inform<strong>at</strong>ion<br />
mapping<br />
<strong>Volvo</strong> Domain model (KOLA)<br />
Variant<br />
Function<br />
group<br />
Vehicle<br />
module<br />
Variant<br />
Specific<strong>at</strong>ion<br />
Test<br />
Object<br />
BOM link<br />
Roadmap<br />
<strong>PLM</strong> Services model (AP214)<br />
part<br />
Part_<br />
version<br />
assembly_<br />
definition<br />
(d_d_i_d)<br />
•----<br />
•----<br />
•----<br />
Item_<br />
instance<br />
next_higher<br />
_assembly<br />
• Inform<strong>at</strong>ion flow<br />
1<br />
Results<br />
• Agree on AS-IS or if possible required<br />
inform<strong>at</strong>ion flow as basis for servicebased<br />
solution<br />
• High level TO-BE solution<br />
2<br />
• Define needed services and agree on<br />
service oriented TO-BE solution<br />
• Input for detailing of services and<br />
inform<strong>at</strong>ion model/ mapping<br />
3<br />
4<br />
5<br />
• G<strong>at</strong>her details on exchanged<br />
inform<strong>at</strong>ion objects to be able to<br />
define the services in more detail and<br />
map the <strong>Volvo</strong> inform<strong>at</strong>ion objects<br />
against <strong>PLM</strong>S<br />
• Get time plans as input to roadmap<br />
• Collect project time plans (g<strong>at</strong>es) or<br />
anticip<strong>at</strong>ed time frames for future<br />
projects to consolid<strong>at</strong>e a roadmap for<br />
service implement<strong>at</strong>ion<br />
Example<br />
<strong>Volvo</strong> Group Trucks Technology<br />
Process Vehicle Architecture & DDTS, Trond Zimmerman<br />
17 2012-09-25
Agenda<br />
1. Introduction<br />
2. Prerequisites<br />
3. Value analysis<br />
4. Change management approach<br />
5. Roadmap<br />
6. Some artifacts<br />
<strong>Volvo</strong> Group Trucks Technology<br />
Process Vehicle Architecture & DDTS, Trond Zimmerman<br />
18 2012-09-25
Upgrade of integr<strong>at</strong>ion architecture & improvement of inform<strong>at</strong>ion<br />
architecture cre<strong>at</strong>es base for further improvement<br />
Steps required to reap benefits of service orient<strong>at</strong>ion<br />
Benefits for business<br />
Future business<br />
driven process<br />
improvements<br />
3<br />
Employ new<br />
architectural basis<br />
for driving process<br />
improvements<br />
• Business-driven process<br />
improvements and change can be<br />
handled more efficiently and <strong>with</strong><br />
higher flexibility<br />
Scope of <strong>PLM</strong><br />
Architecture<br />
project<br />
1<br />
2<br />
Use services to improve<br />
inform<strong>at</strong>ion architecture<br />
Upgrade integr<strong>at</strong>ion technology<br />
• Cre<strong>at</strong>e common inform<strong>at</strong>ion<br />
architecture<br />
• Simplify and reorder inform<strong>at</strong>ion<br />
exchange <strong>with</strong> a limited number of<br />
services<br />
• Ensure clear mastering of inform<strong>at</strong>ion<br />
and logic in the architecture<br />
• Cre<strong>at</strong>e basis to adapt efficiently to<br />
changing business needs<br />
• Upd<strong>at</strong>e technology to next level<br />
• Cre<strong>at</strong>e “critical mass” to reap<br />
economies of scale<br />
• Cre<strong>at</strong>e basis for improved inform<strong>at</strong>ion<br />
architecture<br />
<strong>Volvo</strong> Group Trucks Technology<br />
Process Vehicle Architecture & DDTS, Trond Zimmerman<br />
19 2012-09-25
Way forward: realize projects <strong>with</strong> strong case, e.g. supporting<br />
VPDM, and “piggyback” on existing projects<br />
General altern<strong>at</strong>ives for realizing the target architecture<br />
How to<br />
realize<br />
TO-BE<br />
Upd<strong>at</strong>e<br />
“all <strong>at</strong> once”<br />
Upd<strong>at</strong>e stepwise<br />
1<br />
2<br />
Upd<strong>at</strong>e all integr<strong>at</strong>ions<br />
ASAP<br />
Upd<strong>at</strong>e all integr<strong>at</strong>ions until<br />
a fixed d<strong>at</strong>e<br />
Where there is a perceived<br />
need and strong case<br />
Where there is an ongoing<br />
project th<strong>at</strong> needs to adapt<br />
integr<strong>at</strong>ions “anyway”<br />
<br />
<br />
•No – too expensive<br />
•No self carrying business case for all<br />
integr<strong>at</strong>ions<br />
•Yes – esp. for realizing “the main case”<br />
•Supports the business needs and<br />
realizes benefits directly<br />
•Yes – parallel stream of activities<br />
•To upd<strong>at</strong>e the technology<br />
•To gain “critical mass” for realizing scale<br />
dependent architectural benefits<br />
Where there is no project<br />
planned<br />
•No – only if there is a strong connection<br />
to a case <strong>with</strong> clear business benefits<br />
<strong>Volvo</strong> Group Trucks Technology<br />
Process Vehicle Architecture & DDTS, Trond Zimmerman<br />
20 2012-09-25
Three streams of implement<strong>at</strong>ion should be pursued in parallel to<br />
support business priorities and reap benefits<br />
High-level way forward for implement<strong>at</strong>ion<br />
benefit<br />
Prototype<br />
parts<br />
ordering<br />
Item Cre<strong>at</strong>ion/<br />
Item bridging<br />
Manufacturing<br />
prepar<strong>at</strong>ion<br />
…<br />
Release<br />
process<br />
Calcul<strong>at</strong>ion<br />
request<br />
…<br />
Embedded<br />
SW<br />
management<br />
Context<br />
cre<strong>at</strong>ion<br />
…<br />
…<br />
Total objective (requires 1,2,3):<br />
• Reap VPDM-rel<strong>at</strong>ed benefits<br />
• Realize the full potential in<br />
oper<strong>at</strong>ions & maintenance<br />
• Realize benefits from<br />
further process improvements<br />
… …<br />
…<br />
Stream 3: Continuous further development of infrastructure<br />
Service & AM<br />
prepar<strong>at</strong>ion<br />
Sales<br />
prepar<strong>at</strong>ion<br />
time<br />
Pilots,<br />
initial success<br />
”First<br />
orchestr<strong>at</strong>ed service”<br />
Main case<br />
context cre<strong>at</strong>ion<br />
Rollout<br />
... ... ...<br />
...<br />
Leverage new<br />
architecture<br />
<strong>Volvo</strong> Group Trucks Technology<br />
Process Vehicle Architecture & DDTS, Trond Zimmerman<br />
21 2012-09-25
Agenda<br />
1. Introduction<br />
2. Prerequisites<br />
3. Value analysis<br />
4. Change management approach<br />
5. Roadmap<br />
6. Isome Artifacts<br />
<strong>Volvo</strong> Group Trucks Technology<br />
Process Vehicle Architecture & DDTS, Trond Zimmerman<br />
22 2012-09-25
<strong>PLM</strong> Service Bus (Backend) Frontend<br />
ResolveBOM<br />
......<br />
Cre<strong>at</strong>eDCN<br />
......<br />
Get Part<br />
......<br />
......<br />
......<br />
GetPartID<br />
Revoke<br />
......<br />
Authentic<strong>at</strong>ion<br />
Performance<br />
Logging<br />
......<br />
<strong>The</strong> elements of the target architecture and their interactions<br />
are detailed in the <strong>PLM</strong> Architecture project<br />
Conceptual <strong>PLM</strong> target architecture – overview of elements<br />
Product development (PD)<br />
Sales<br />
(StO)<br />
Manufacturing<br />
(OtD)<br />
Service/<br />
AM (DtR)<br />
PDM CADdb y Prot.<br />
Mtrl.<br />
Service<br />
implement<strong>at</strong>ion<br />
Service<br />
implement<strong>at</strong>ion<br />
Service<br />
implement<strong>at</strong>ion<br />
Prototyp<br />
e<br />
Service<br />
implement<strong>at</strong>ion<br />
Parts<br />
plan<br />
Service<br />
implement<strong>at</strong>ion<br />
Adapter Adapter Adapter Adapter Adapter<br />
Sales<br />
config<br />
Service<br />
implement<strong>at</strong>ion<br />
Factory<br />
filtering<br />
Service<br />
implement<strong>at</strong>ion<br />
Spare<br />
parts<br />
Service<br />
implement<strong>at</strong>ion<br />
Adapter Adapter Adapter*<br />
…<br />
…<br />
Service<br />
implement<strong>at</strong>ion<br />
Adapter<br />
Service<br />
…<br />
enabled/<br />
N<strong>at</strong>ive<br />
appl.<br />
Integr<strong>at</strong>ion Pl<strong>at</strong>form<br />
Bridging adapter/ g<strong>at</strong>eway<br />
Partner/ JV systems<br />
Logical rel<strong>at</strong>ion to service directory – no runtime dependency<br />
Service directory (incl. inform<strong>at</strong>ion mapping repository)<br />
<strong>PLM</strong> services<br />
General services<br />
StructureMngt ChangeMngt PartMngt ...Mngt MasterD<strong>at</strong>aMngt Infrastructure<br />
General service<br />
implement<strong>at</strong>ion<br />
Inform<strong>at</strong>ion model<br />
(mapping repository)<br />
VOLVO <strong>PLM</strong><br />
Services<br />
* Adapter might be connected to both CLM and <strong>PLM</strong> service bus<br />
<strong>Volvo</strong> Group Trucks Technology<br />
Process Vehicle Architecture & DDTS, Trond Zimmerman<br />
23 2012-09-25
<strong>PLM</strong> Service Bus (Backend) Frontend<br />
ResolveBOM<br />
......<br />
Cre<strong>at</strong>eDCN<br />
......<br />
Get Part<br />
......<br />
......<br />
......<br />
GetPartID<br />
Revoke<br />
......<br />
Authetic<strong>at</strong>ion/<br />
Authoriz<strong>at</strong>ion<br />
Performance<br />
Logging<br />
......<br />
<strong>The</strong> example service ”ResolveBOM” shows how the<br />
target architecture elements work together<br />
Conceptual <strong>PLM</strong> target architecture – example of service provision<br />
Product development (PD)<br />
Sales<br />
(StO)<br />
Manufacturing<br />
(OtD)<br />
Service/<br />
AM (DtR)<br />
Steps in service provision<br />
PDM CADdb y Prot. Prototyp Parts 1 • PROTOT. Pro- adapter DIS/ (consumer) Ber- Glopps/ popul<strong>at</strong>es ResolveBOM<br />
… Service<br />
Request<br />
…<br />
Mtrl. e Plan<br />
message<br />
Builder<br />
(input<br />
edning<br />
parameters) according<br />
LISA<br />
to ...<br />
… enabled<br />
• ... the ResolveBOM message definition in the service directory*<br />
Service Service Service Service Service 2 Service Service Service Service appl.<br />
implemen- implemen- implemen- implemen- implemen- • PROTOT. implemen- adapter implemen- invokes the implemen- ResolveBOM implemen- Request using the<br />
t<strong>at</strong>ion t<strong>at</strong>ion t<strong>at</strong>ion t<strong>at</strong>ion t<strong>at</strong>ion integr<strong>at</strong>ion t<strong>at</strong>ion pl<strong>at</strong>form t<strong>at</strong>ion<br />
t<strong>at</strong>ion t<strong>at</strong>ion<br />
6 10<br />
3<br />
7 Adapter Adapter Adapter Adapter Adapter • the Adapter integr<strong>at</strong>ion pl<strong>at</strong>form Adapter routes Adapter* and transports Adapter the message to the<br />
5<br />
1<br />
Service endpoint<br />
8 4<br />
9 3 4 (different priciples to couple provider/ consumer possible)<br />
• PDM adapter (provider) receives the message<br />
Integr<strong>at</strong>ion Pl<strong>at</strong>form<br />
• PDM adapter (provider) parses message request and make<br />
5 n<strong>at</strong>ive calls to collect required d<strong>at</strong>a in n<strong>at</strong>ive form<strong>at</strong><br />
• PDM adapter (provider) transforms the n<strong>at</strong>ive General d<strong>at</strong>a to Service <strong>PLM</strong>S 2.1<br />
6 form<strong>at</strong> and popul<strong>at</strong>es the ResolveBOM Response Implement<strong>at</strong>ion message<br />
• the ResolveBOM Response message is transported to the<br />
Service directory (incl. inform<strong>at</strong>ion mapping repository) 7 integr<strong>at</strong>ion pl<strong>at</strong>fom<br />
• the ResolveBOM Response message is received by the<br />
<strong>PLM</strong> services<br />
General services<br />
Inform<strong>at</strong>ion model<br />
consumer<br />
StructureMngt ChangeMngt PartMngt ...Mngt 8 MasterD<strong>at</strong>aMngt Infrastructure (mapping repository)<br />
• consumer processes the ResolveBOM message, i.e. parses the<br />
VOLVO <strong>PLM</strong><br />
2<br />
message & the <strong>PLM</strong>S 2.1 content, and invokes n<strong>at</strong>ive calls to<br />
Services<br />
9 transform into GUI present<strong>at</strong>ion and/or upd<strong>at</strong>e n<strong>at</strong>ive local d<strong>at</strong>a<br />
• consumer processes the ResolveBOM message, i.e. parses the<br />
10<br />
message & the <strong>PLM</strong>S 2.1 content, and invokes n<strong>at</strong>ive calls to<br />
transform into GUI present<strong>at</strong>ion and/or upd<strong>at</strong>e n<strong>at</strong>ive local d<strong>at</strong>a<br />
* not lookup!<br />
<strong>Volvo</strong> Group Trucks Technology<br />
Process Vehicle Architecture & DDTS, Trond Zimmerman<br />
24 2012-09-25
<strong>The</strong> service lifecycle management process defined<br />
from IT str<strong>at</strong>egy to service termin<strong>at</strong>ion<br />
Service lifecycle management process – Overview<br />
1) Define str<strong>at</strong>egy,<br />
applic<strong>at</strong>ion<br />
& project portfolio<br />
2) Define <strong>PLM</strong><br />
architecture<br />
& migr<strong>at</strong>ion roadmap<br />
3) Implement in project<br />
according to IS-GDP &<br />
ISP<br />
4) Oper<strong>at</strong>e & maintain<br />
service<br />
5) Termin<strong>at</strong>e<br />
service<br />
Tasks<br />
1)...<br />
2)...<br />
3)...<br />
1)...<br />
2)...<br />
3)...<br />
1)…<br />
2)…<br />
3)…<br />
1)…<br />
2)…<br />
3)…<br />
1)…<br />
2)…<br />
3)…<br />
Artifacts<br />
•VG PPD P&IT str<strong>at</strong>egy<br />
•VG targ. arch. & gov.<br />
framework<br />
•VG SLA principles &<br />
templ<strong>at</strong>e<br />
•VG SLM principles &<br />
model<br />
•VG integr<strong>at</strong>ion pl<strong>at</strong>form<br />
principles<br />
•<strong>PLM</strong> applic<strong>at</strong>ion portfolio<br />
•<strong>PLM</strong> project portfolio<br />
Service st<strong>at</strong>us<br />
•<strong>PLM</strong> target arch. & arch.<br />
princip.<br />
•Info. model (MDM model<br />
for <strong>PLM</strong>)<br />
•Info. modeling &<br />
mapping guidelines &<br />
tool directive<br />
•<strong>PLM</strong> arch. migr<strong>at</strong>ion<br />
str<strong>at</strong>egy<br />
•Service portfolio &<br />
roadmap<br />
•Service description in<br />
tool<br />
•“Showcase descriptions”<br />
•Approved Integr<strong>at</strong>ion<br />
request – business part<br />
•Approved integr<strong>at</strong>ion<br />
request – solution part<br />
•Other artifacts<br />
describing services (see<br />
detailed description of<br />
phase)<br />
•Service usage &<br />
performance report<br />
•Input for <strong>PLM</strong> TO-BE<br />
service roadmap (e.g.<br />
progress, need for<br />
changes/ new<br />
development)<br />
•Changes/ upd<strong>at</strong>es to<br />
services documented in<br />
service directory<br />
•N/A •Emerging •Appointed •Preserving •Sunset •Removed<br />
•Service description<br />
artifacts in service<br />
directory (e.g. for sunset<br />
and replacement<br />
services)<br />
•Usage st<strong>at</strong>istics/ d<strong>at</strong>a<br />
•Service description<br />
st<strong>at</strong>us termin<strong>at</strong>ed in<br />
service directory<br />
<strong>Volvo</strong> Group Trucks Technology<br />
Process Vehicle Architecture & DDTS, Trond Zimmerman<br />
25 2012-09-25
Service lifecycle management stages and st<strong>at</strong>us have<br />
been defined<br />
Overview of service lifecycle stages<br />
Not in use any more and switched off.<br />
Event: Switched off<br />
Set by: zzz<br />
Not to be used anymore. D<strong>at</strong>e<br />
for decommission is set and<br />
communic<strong>at</strong>ed.<br />
Event: Decision<br />
Set by: xxx<br />
Sunset<br />
Removed<br />
Emerging<br />
Service is identified as part of the tobe<br />
solution but not decided<br />
Event: service entered in roadmap<br />
Set by: xxx<br />
CSG<br />
Decided<br />
In<br />
development<br />
Decision to start working on the<br />
specific<strong>at</strong>ion of a (emerging) service<br />
has been taken.<br />
Event: CSG<br />
Set by: yyy<br />
FDCG<br />
Decision to start<br />
development/<br />
implement<strong>at</strong>ion of a service<br />
has been taken.<br />
Event: FDCG<br />
Set by: yyy<br />
RG<br />
Preserving to secure<br />
existing investments. This<br />
service is maintained and<br />
supported.<br />
Event: Decision<br />
Set by: xxx<br />
Preserving<br />
Appointed<br />
Assured<br />
ULG<br />
Developed<br />
Development of service<br />
(incl. testing) has been<br />
concluded.<br />
Event: RG<br />
Set by: yyy<br />
Appointed and mand<strong>at</strong>ory to use for new investments.<br />
Full maintenance and support is available.<br />
Event: EG<br />
Set by: yyy (check <strong>with</strong> xxx)<br />
<strong>Volvo</strong> Group Trucks Technology<br />
Process Vehicle Architecture & DDTS, Trond Zimmerman<br />
26 2012-09-25<br />
EG<br />
Quality assurance & (user) test of<br />
integr<strong>at</strong>ion solution has been performed.<br />
Event: ULG<br />
Set by: yyy
General service definitions are stored in service directory –<br />
specific implement<strong>at</strong>ion is realized in applic<strong>at</strong>ions<br />
Governance of main architectural elements – overview<br />
General<br />
Applic<strong>at</strong>ion specific<br />
Own: xxx<br />
Message<br />
model<br />
Defines<br />
structure for<br />
1 *<br />
(General) service<br />
definition<br />
Own: xxx<br />
Specified by<br />
zzz<br />
Sets<br />
boundaries for<br />
1 *<br />
(Adapter) specific<br />
service definition<br />
Own: See<br />
applic<strong>at</strong>ion<br />
Specified by<br />
zzz<br />
Realized<br />
(partly) in<br />
1 1<br />
Service<br />
implement<strong>at</strong>ion<br />
Own: See<br />
applic<strong>at</strong>ion<br />
Specified by<br />
zzz<br />
1<br />
Is needed for<br />
Contains<br />
Contains 1<br />
1<br />
Service<br />
directory<br />
Own: xxx<br />
Impl. by yyy, zzz,<br />
et cetera ...<br />
1<br />
*<br />
Contains<br />
references to<br />
1 *<br />
Is referenced in<br />
(baseline)<br />
Info. (model) &<br />
mappings<br />
Own: ddd<br />
1<br />
1<br />
Specified by lead<br />
architect in projects<br />
Is implemented<br />
in<br />
1 1<br />
Realized<br />
(partly) in<br />
Adapter<br />
See applic<strong>at</strong>ion<br />
*<br />
1<br />
Is part of<br />
1 1<br />
1<br />
1<br />
Realized<br />
as part of<br />
Applic<strong>at</strong>ion<br />
Own: ccc<br />
Dev. bbb<br />
MA by aaa<br />
Provides/<br />
consumes<br />
1 1<br />
1<br />
Service<br />
in oper<strong>at</strong>ion<br />
See applic<strong>at</strong>ion<br />
1<br />
Provides & specifies<br />
connectivity<br />
*<br />
1<br />
VG Integr<strong>at</strong>ion<br />
pl<strong>at</strong>form (VGIP)<br />
*<br />
1<br />
Own: kkk<br />
Impl. & MA fff<br />
Connects to<br />
Is needed for<br />
*<br />
<strong>Volvo</strong> Group Trucks Technology<br />
Process Vehicle Architecture & DDTS, Trond Zimmerman<br />
27 2012-09-25
Thank you!<br />
Trond Zimmerman, M.Sc., Ph.D.<br />
PDM Manager<br />
<strong>Volvo</strong> Group Trucks Technology<br />
Process Vehicle Architecture & DDTS<br />
Dept. BF15330, GC3<br />
SE-405 08 Göteborg, Sweden<br />
(: +46 (0)31 322 6342<br />
(: +46 (0)73 902 6342<br />
(: +46 (0)31 327 8359<br />
* : trond.zimmerman@volvo.com<br />
<strong>Volvo</strong> Group Trucks Technology<br />
Process Vehicle Architecture & DDTS, Trond Zimmerman<br />
28 2012-09-25
Change language