Honda Europe NV. Honda Europe NV stands for : HE-IS

Transcription

1 1

2 Honda Europe NV Honda Europe NV was founded in Ghent in More than 20 years later Honda Europe NV has grown to be the logistic centre for Europe, Africa and the Middle-East. Currently Honda Europe NV realises a turnover of 647 million euro with more than 700 associates in Ghent and 200 more in the other European subsidiaries Honda Europe NV stands for : Logistics for cars, motorcycles and power equipment Purchasing, sales and logistics of original parts for all products Sales and logistics of industrial engines Development and management of information systems 2

3 LOGISTICS WITHOUT FRONTIERS 7 HONDA LOGISTIC CENTERS in Europe : Barcelona (HLC-Spain) Verona (HLC-Italy) Vienna (HLC-Austria) Offenbach (HLC-Germany) Swindon (HLC-UK) Malmö (HLC-Sweden) Ghent (HLC-Belgium) 3

4 INFORMATION SYSTEMS CENTER Customers and their locations Finland Honda European Head Quarters : 3 Honda regional Head Quarters : 4 Norway Sweden Ireland Denmark Baltic UK Netherlands Poland Belgium Germany France Tjech Austria Switzerland Hungary Portugal Spain Italy Turkey Russia Honda Genpos : 24 Honda Logistic Center : 7 Honda Dealers : 6300 Distributors : 200 Transporters : 140 Suppliers : 1700 Wholesales Independent repair centers: 404 (Italy) Africa End-customers 4

5 Process Modeling 5

6 Honda Europe Information s - Capability improvements More emphasis on Project management More focus on Analysis More Analysis and BA skill improvement Introduction Process Modelling Process Models as part of User requirements deliverables 6

7 Project management & BPM Analysis Design Build Test Review Kick- Off High-Level Requirement Detailed Requirements High-Level Design Detailed Design Technical Design Development Acceptance User Acceptance Cut-Over Post implementation Review E E E E E E E E Objectives Delivered result (system functions) better aligned with what the business needs (business requirements) J5; 46; 29% U1; 20; 13% n io 35 t a c 30 l lo a 25 e c 20 r u o 15 s e 10 R 5 0 Current (suystem delivery) U0 U1 J0/J1 J2 J3 J4 J5 P0 Development phases Future ( change) J3 J4; 40; 25% J1; 53; 33% n i o35 t a c 30 l lo a25 e c 20 r u o15 s e 10 R 5 0 U0 U1 J0/J1 J2 J3 J4 J5 P0 Development phases 7

8 The Detailed business requirements Process Analysis Design Build Test Review Kick- Off High-Level Requirement Detailed Requirements High-Level Design Detailed Design Technical Design Development Acceptance User Acceptance Cut- Over Post implementation Review E E E E E E E E Gather : * Interviews * Analyse information * Team discussions * Check on site Formalise Validate by team & experts Evaluate 8

9 From hierarchy puzzle to complete & common understanding Clear understanding how we will Deliver goods & services to our customer Process Logistics Parts Sales BA IS 9

10 2005 Start with BPM Supported by Visio 10

11 Visio & Process Modelling High level flow diagram to get a complete overview of the business flow 11

12 Visio & process Modelling detail example administration Detail level process flow for detailed information on the business process steps 12

13 Visio & process Modelling concerns : Visio flows is drawing tool only How can we add descriptions, screen & other layout output Limited standards on use and output to use How can we indicate integrations on organisation ( PARTS / MC & PE / CARS,.) How can we see business synergies among businesses How can we see bottlenecks / issues in processes How will we manage big models / complexity, How can we store and re-use work How can we present output easily to involved business key users, end users and IS people, to guarantee completeness & same understanding How can we maintain easily once live and Change Request comes up How can we manage and consolidate when different projects affects same flow How can we pass easily to system solution phase and maintain link with business process 13

14 2006 Process Modelling supported by stronger tool 14

15 Round 1 : Products? Nov Jan products 1st evaluation ( based on Gartner Magic Quadrant ) Products Not selected for the second round and requirement area : Popkins ( Ease in use, Drawing and process modelling ) IDS Scheer ( Ease in use ) IBM Process Modeler ( Ease in use / Drawing and process development ) Considered for 2nd round CASEWISE QPR Processguide Decision Analysis Must & want criteria 15

16 DA Criteria & evaluation method Multi-user / Ease in use / End user support 11 To have a central Repository ( metamodel ) with all business process model information stored with Import / Export via XML to other tools 12 To have different versions of specific model supporting the dev. live cycle of "In Dev." In test, In QA, and this for different projects, including Check In, Check out Q Q D&D D&D Snapshot of scoring list 13 To have model merge functionality Q D&D 14 To have automatic Change management functionality to Q D&D merge form D tot T to QA to Live ( In the tool or integrated with market standards products ) 15 To have security on user level and authorisation on Q D&D role/project level 16 HPMM ( Honda To have functionality to support the deliverables of Q D&D Methodology ) HPMM see sheet U0 U1 J1 ( see sheet U0 U1 J1 ) 17 Ease in use To be able to work as Analyst role after a 2 Q CR day training max. D 18 To be able to work as a inquiry end-user inquiry with a Q WIS simple written guideline 19 To have "online help" available within the tool Q D&D 20 End user Support To be able to have read access via Web interface Q D&D 21 To be able to Automatic publishing in different formats Website ( HTML ) / Reporting : WORD / XL / PDF / ( PPT ) Q D&D 22 s requirements To use a,supported HE IS relational DB,Oracle / UDB / Q D&D SQL 16

17 Conclusion of DA Both alternatives meet all Must-requirements On the Wants Score QPR Processguide 998 points Casewise 733 points Reasons why QPR Processguide score is higher More easy in use Lower cost Local Belgium support ( Ackinas ) Easier in application maintenance for analysts 17

18 Image of a QPR tool to support BPM 1. user 4. QPR tool Administrator QPR Repository Base Model Model Project Model Level-1 Level-2 Level-3, 3 Level-4, 4 QPR portal 2. Leads 5. Administrator Client server 3. analyst 18

19 BPM : Implementation in QPR High-Level requirements Detailed requirements High-Level system design Detailed system design User Acceptance Product Flow 2 Use Cases Test scenarios Flow Diagram 3 Navigation Flow 5 Product Motorcycles Car Power Equipment Engines Marine 1 L1 L2 L2 L3 L3 Model Domain Entity Process Flow s and Interfaces Image Functional Model FDD functions 4 Parts L4 L4 Activity Flow Accessories QPR Model-1 QPR Model-2 19

20 process Level-1 : the domains SEIHAN draft Marketing R& D Pre-Sales Trade Sales Production Logistics Transport Finance Service Warranty Accounting Tax & Customs Human resources Budgeting 20

21 Level 2 the entities : example MC & PE Logistics Steering Core Supporting HE Management INBOUND STORAGE OUTBOUND Shipping Movements Delivery Instruction Re-invoicing Container Allocation Arrival Locations Picking Inspection Packing Un-& Re-pack Loading Stock Taking Dispatch Discrepancy Delivery Inbooking Confirmation Mastering Quality control draft Logistics customer care Logistics budgeting Logistics invoicing Transport arrangements Transport arrangements 21

22 Level 3 the business process flow example MC & PE Logistics draft 22

23 BPM Use in projects 23

24 Positioning option mounting within Motorcycle Logistics Motorcycles Level 1 & 2 to position the process in the Motorcycle business SEIHAN Motorcycles Logistics Marketing HE Management R&D Production Pre-sales Trade Sales Logistics Inbound Factory Binning Shipping Re-invoicing Container planning Arrival Inspection Unpack Repack Discrepancy Handling Binning Storage Location Change Movement Plant move Outbound Delivery Instruction Allocation Picking Packing Loading Dispatch Delivery confirmation Export Invoices Transport Finance Service Mastering Quality Control Logistics Customer Care Warranty Logistics Budgetting Accounting Logistics Invoicing Stock Taking Tax&Customs Transport Arrangements Transport Arrangements Human resources Budgetting ICT services 24

25 Flow diagram Atessa - production MC - destination domestic MAPICS Factory PLS Warehouse (Cerratina) PLS Send Produced MC to PLS / MAPS (every 10 ) Automatic inbooking in warehouse IT-HI QLRG RF-Truck load to Cerratina Open gate Fill trailer & dest. (AT) Scan Frames (factory label) Close gate Loadlist location change U8207 flow flow diagram diagram for for summarised summarised view view on on business business operation operation QLSD RF-Inbooking factory stock Input packaging type Scan Frames (factory label) + print PLS-framelabel Atessa Cerratina 25

26 Process Flow Motorcycles - Logistics - Facto ry binning Level-3 Level-3 for for detailed detailed operation operation HIA factory dat a trans missio n domestic production domestic production production info export product ion automatic inbooking EX wareho use A llocation picking slip picking s lip c hild part picking s lip print sche dule picking s lip picking slip RF truck load export c lose trailer picking s Arrival info HLC-IT automatic inbooking H I warehouse PLS delivery instruction dispatch t railer p icking slip Fac tory Framelabel RF truck load export PLS delivery confirmation Fac tory Framelabel Rf inbooking factory stoc k Arrival info HIR S ales O rder process ing (S ales) (Sales ) 26

27 Project management & BPM result Analysis Design Build Test Review Kick- Off High-Level Requirement Detailed Requirements High-Level Design Detailed Design Technical Design Development Acceptance User Acceptance Cut-Over Post implementation Review E E E E E E Objectives Delivered result (system functions) better aligned with what the business needs (business requirements) E E Current (suystem delivery) 45 J5; 20; 22% 40 n io 35 t a c 30 l lo a 25 e c 20 r u o 15 s e 10 R 5 0 U0 U1 J0/J1 J2 J3 J4 J5 P0 U1; 30; 34% Development phases Future ( change) 45 J3 J4; 20; 22% J1; 20; 22% 40 n i o35 t a c 30 l lo a25 e c 20 r u o15 s e 10 R 5 0 U0 U1 J0/J1 J2 J3 J4 J5 P0 Development phases 27

28 END 28