Aligning Business and System Functionality

1. Aligning Business and System Functionality Colette Rolland Université Paris1 Panthéon Sorbonne http://crinfo.univ-paris1.fr

2. Outline • The Conceptual Mismatch • The MAP representation system • The matching Process • Conclusion

3. Organisation Purpose System Product Functionality The Mismatch The Conceptual Mismatch Avoiding the « conceptual mistmatch »  (Arsajanasi01)

4. Business model ERP Requirements High level expression High level expression Goal - strategy driven Goal - strategy driven The Match Global Global Abstracting ERP Functionality Descriptions The Mismatch Low level description Function driven Local Mitigating the Mismatch

5. Abstraction Step Iteration ERP System ERP Reqts Matching Reqts Matching Step Iteration Organisation Reqts A Requirements Driven matching ERP customisation process ERP Map (Might-Be Map) The Matched Map (To-Be Map) As-Is & As-Wished Maps

6. Modelling with Map sij2 Ii sij1 Ij si sji sjk ski Start Stop sk Ik ss Map as a set of interconnected sections <Ii, Ij, Sij> with a multithread and multipath topology A map is a process model in which is featured a non-deterministic ordering of intentions and strategies Intention a goal to be achieved Strategy a mean or a manner to achieve an intention Section a triplet <Intention Ii, Intention Ij, Strategy Sij> that constitutes the basic block of a map

7. Modelling with Map The SAP Material Management map Inventory balance strategy Start Quality inspection strategy By planning Reservation strategy Monitor Stock By Reminder Manually Purchase Material Valuation strategy Out-In strategy Bill for expenses strategy In-In strategy Financial control strategy Stop

8. By reorder point planning Start By bill for expenses strategy Periodic Reference Sampling C2 Continuous By forecast based planning Manually Component Name By inventory balance strategy Purchase Material based on reorder points By reservation strategy Component Interface Purchase material By valuation strategy Manage course registration <(Start, Purchase material, by reorder point planning)> Monitor stock By reminder Component Body By ‘out-in’ strategy By quality inspection By ‘in-in’ strategy • Automatically generate purchase requisition order when the stock of a given material attains the reorder point • Transform purchase requisition into purchase order By financial control Stop SAP-MM map: Business view / System view C6 C2 C1 C3 C7 C11 C8 C4 C5 C9 C10 C12

9. By reorder point planning Start By bill for expenses strategy C6 Periodic Sampling Reference C1 Continuous By forecast based planning Manually By inventory balance strategy Component Name Purchase Material manually By reservation strategy C7 Purchase material By valuation strategy Manage course registration Monitor stock C8 By reminder By ‘out-in’ strategy C9 • Collect information about material, vendor, price… • Manually define a purchase requisition order • Check information correctness • Create a purchase order By quality inspection C10 By ‘in-in’ strategy Component Body By financial control C12 Stop SAP-MM map: Business view / System view C2 C1 C3 C11 Component Interface <(Start, Purchase material, manually)> C4 C5

10. Map Meta Model and Formal Definition OR XOR sequence Map Path Refined by source Section Link target Strategy Target Intention Source Intention Start Intention Stop

11. Start Rejection strategy Recon- ciliation of unit difference Reconciliation of under/over delivery Okay strategy Stop C5.3 C5.4 Reconciliation by PO recovery C5.2 C5.0 C5.7 Completeness strategy C5.1 Accept delivery C5.5 Out-in direct consumption strategy Enter goods In stock C5.6 Out-in storage based strategy Modelling with Map Map refinement Purchase material C5 Monitor stock By ‘out-in’ strategy

12. Reference C5.3 Component Name Accepting delivery Component Interface <(Start, Accept delivery, by okay strategy)> Component Body • Automatically check the compliance of the delivered goods with the purchase order • Generate goods receipts Modelling with Map Refined map: Business / System views Start Rejection strategy Recon- ciliation of unit difference Reconciliation of under/over delivery C5.4 Okay strategy Stop C5.1 C5.0 C5.7 C5.3 Completeness strategy Reconciliation by PO recovery Accept delivery C5.2 C5.5 Out-in direct consumption strategy Enter goods In stock C5.6 Out-in storage based strategy

13. The Matching Process The Matchmaking Process Modeled as a Map Start Abstraction ERP driven Construct Matched Map As-Wished driven Construct As-Is, As-Wished ERP maps As-Is driven As-Wished driven verification Feed-back Stop

14. Supply Chain Manufacturing Economic performance Distribution Customer Satisfaction Business Process eCenter Aligning SNCF needs Finances Resources Optimization Financials Workforce Analytics eProcurement HRMS eStore CRM EPM Applying the Matching Process ERP customisation process Aligning business requirements with ERP functionality at SNCF

15. The Matching Process Introducing similarity measures As-Wished Map Map Map To-Be Similarities Analysis As-Is Matching Process Map Map Matched Map Map Map Map Might-Be Map Map Map

16. Intention Strategy Similarity Section Map Intrinsic Structural Synonymy Hyperonymy/ Hyponymy Relational Compositional Dice / Jaccard / Cosine Modified Coefficients • Sim(A,B)= 1 if A and B are identical or synonyms • 1- if A is hyponym of B •  if A is hyperonym of B • 0 else •  ]0,1[ The Matching Process Similarity Typology: different types of similarities between 2 maps

17. As-Wished BERCI Matches As-Is Covers SIRCI Might-Be Reuses LOGEsp Applying the Matching Process Global deployment of IS • Uniform installation of an information system to support financial activities at DIAC FUSE

18. The Matching Process Introducing Gaps As-Wished Map To-Be Gaps Analysis As-Is Gaps Matching Process Map Matched Map Might-Be Map

19. The Matching Process Gap Typology Gap Category Gap types Rename strategy Naming Rename intention( verb, target, parameter) Give/ Remove intention (parameter) Modify intention( verb, target, parameter) On Element Give/Remove/Modify section (pre, post condition, business rule) Retype intention into strategy Add/remove intention, strategy, section Structural Change section (source, target) Merge/Split, intention, strategy, section

20. The Matching Process Introducing Gaps • Top down approach : from business gaps to software gaps Intentional view LOGESP Intentional view FUSE Gaps  Maps Intentional Operational Gaps  Operational view LOGESP Operational view FUSE Conceptual OO specs

21. Conclusion • Map provides a representation of the functionality in an easy to understand language • Map provides a basis for expressing two combined view points about SF and BM • Map helps in customising the ERP offer in high level terms • Multiply experiences & validate approach • Develop a methodological support tool