GBS CMF and MDM – Business Requirements
GBS Cost Management Framework & Master Data Management
Business Requirements
Version 0.4
Author
Version / Date / Name / Comments0.1 / 20-Jun-2013 / Ramesh.S / Initial Draft
0.2 / 27-Jun-2013 / Ramesh.S / Changes based on review comments from Yvo
0.3 / 01-Jul-2013 / Ramesh.S / Changes based on review comments from Yvo
0.4 / 05-Jul-2013 / Ramesh.S / Changes to include URS ID reference
Approval (Sign Off)
Version / Date / Name / SignatureTable of Contents
1.0 INTRODUCTION 5
1.1. Purpose 5
1.2. Pre-requisites 5
2.0 Overview 5
2.1. Business Rationale 5
2.2. Application Landscape 6
3.0 Solution Scope 6
3.1. Scope Matrix 6
3.2. In Scope 7
3.2.1. Master Data Management Application 7
3.2.2. Cost Management Framework Datamart & Reporting 7
3.3. Out of Scope 8
4.0 Detailed Solution Requirements – MDM 8
4.1. Dimensions and Data Model 8
4.2. Business Rules in MDM 8
4.3. User Interface Mockup in MDM 12
5.0 Detailed Solution Requirements – CMF Datamart 13
5.1. Additional Master Data in CMF 13
5.1.1. Time Dimension 13
5.1.2. Version 14
5.1.3. ReportMeasures 14
5.2. Inbound Transaction Interface to CMF 15
5.2.1. Replicon Time Tracking Data 15
5.2.2. SAP IBI extracts to CMF 19
5.2.2.1. List of GBS Cost Centers 19
5.2.2.2. Actual Cost from SAP IBI 20
5.3. Outbound Interface from CMF 23
5.3.1. Replicon Data extract to SAP PCM 23
5.3.2. SAP IBI data extract to SAP PCM 25
5.4. CMF Inbound Interface - Results from PCM 27
5.4.1. Activity Driver Value - Actual & Plan Cost & Hours 27
5.4.2. Revenue Results - Actual & Plan Revenue 31
5.4.3. BoA Hours from PCM 32
5.5. Transformation & Aggregation in CMF Datamart for Reporting 32
5.5.1. Timesheet Reporting: Calculations 32
5.5.2. Calculations for Cost & Profitability Reporting 34
5.5.3. Add Reporting Elements and hierarchy 34
5.5.3.1. Timesheet Reporting Elements 35
5.5.3.2. Cost & Profitability Reporting Elements 35
5.5.4. Datamart and Report Refresh 36
5.5.5. Calculate results on Time dimension 36
5.5.6. Reporting Elements in Datamart / Reporting Cube 36
5.5.6.1. TimeSheet Reporting 36
5.5.6.2. Reporting on PCM Results 37
5.6. Reporting Solution 38
5.1. List of Reports from CMF 38
5.2. Report level Information requirement 38
5.2.1. Effort Analysis Report 38
5.2.2. Customer Profitability Report 40
5.2.3. Service Group Profitability Report 41
5.2.4. Service Costing Report 43
5.2.5. Time Sheet Actual Report 44
5.2.6. Time Sheet Submission Status Report 45
5.2.7. Time Sheet Compliance Status Report 46
5.3. Non-Functional Requirement Specification 47
1.0 INTRODUCTION
1.1. Purpose
This document describes the functional specification part of the solution required to fulfill the business requirements outlined in document ‘GBS_CMF and MDM_URS Document.docx’. The target audience is Novartis Global Business Services Management team (owners of GBS CMF), GBS IT and the vendor resources part of the Solve phase for GBS Cost Management Framework DW & MDM project.
1.2. Pre-requisites
The User Requirements Specification (URS), ‘GBS_CMF and MDM_URS Document.docx’ must be approved prior to the approval of this document and must act as input to the Functional Specification Document.
1.3. References
· GBS_CMF_BIZ BusinessRequirements 20121205 signed.pdf
· Onsite Requirement Gathering workshop Issue Log - GBS CFM Workshop 24May Final.pptx
· PBO Project Report Guide - CMF_BW Reports_User Guide_20110520_v1.0.pptx
· CMF & MDM User Requirement Document - GBS-CMF_URS_055-CMFMDM V 0.5.docx
2.0 Overview
2.1. Business Rationale
The establishment of Global Business Services (GBS) as integral part of the Novartis Pharma strategy has triggered a new Business Solution Center (BSC) governance model. The main objective of the new governance model is to capture synergies beyond labor arbitrage by adding new capabilities while reinforcing costumer focus through quality to cost key performance indicators (KPIs).
The GBS Cost Management Framework (CMF) is a key pillar of the BSC governance model, since it provides the foundation for moving from FTE to Service charging. The CMF targets to retain the simple charging model whilst enhancing the service cost transparency allowing service managers to drive productivity and quality.
The GBS is also envisioning standardization of its operating framework and consider creating a Master Data Management solution to provide a controlled environment for maintenance and modification of its organization, customer and service master element and hierarchies that is inherited by all applications across its system landscape.
2.2. Application Landscape
The GBS CMF system landscape diagram provided below explains the broad spectrum of applications part of GBS Cost Management Framework.
3.0 Solution Scope
3.1. Scope Matrix
Activities / MDM / CMFGUI to maintain Master Data Elements / Y / -
GUI to maintain Master Data Hierarchy / Y / -
GUI to maintain Master Data Relations / Y / -
Inbound Interface - Transaction Records
Replicon (TimeTracking) / - / Y
Clarity (TimeTracking) / - / N
SAP IBI (Consolidated ERP) / - / Y
SAP ECC (Individual ERP Instance) / - / N
OMF (Order Management Framework) / - / N
Volumetric Data (Spreadsheet) / - / N
Revenue Break-up (Spreadsheet) / - / N
Validate
Replicon - Transaction data elements with MDM / - / Y
Replicon - Transaction data element relations with MDM / - / N
SAP IBI -Transaction data element with MDM / - / N
SAP IBI - Transaction data element relations with MDM / - / N
Volumetric Data - Transaction data element with MDM / - / Y
Volumetric Data - Transaction data element relations with MDM / - / N
Revenue data - Transaction data elements with MDM / - / N
Revenue Data - Transaction data element relations with MDM / - / N
Aggregation & Transformation - Data
Transform and aggregate valid transaction records in datamart / - / Y
Outbound Interface
Push data directly to downstream application tables using database connect for OMF / N / -
Publish data in views from MDM that OMF can access / Y / -
Push data directly to CMF using database connect / Y / -
Publish Flat files with aggregated data to SAP PCM / - / Y
Inbound Interface - Results
SAP PCM Results extracted from published views to CMF / - / Y
Validate data elements in results with MDM / - / Y
Aggregation & Transformation - Results
Transform and aggregate valid results on reporting hierarchy and populate reporting cubes / - / Y
Reporting Hierarchy & reports
Create reporting hierarchy in CMF Datamart / - / N
Inherit reporting hierarchy from MDM to CMF / - / Y
Provide standard canned reports with slice & dice options in CMF / - / Y
Provide dashboard reporting in CMF / - / Y
3.2. In Scope
3.2.1. Master Data Management Application
The MDM solution consists of following
1) Multiple Graphical User Interfaces to create, update and delete master data elements part of organization, customer and service hierarchy.
2) Multiple Graphical User Interfaces to define, update and delete relations between master data elements part of the above mentioned hierarchies.
3) Technical interface to publish master definition for consumption by other applications within GBS. This does not refer to an automatic interface from MDM to CMF or other down stream applications.
3.2.2. Cost Management Framework Datamart & Reporting
CMF DM & Reporting application consists of
1) Data Integration solution to integrate
- Inputs from Replicon Time Attend Application on actual effort spent on GBS service delivery.
- Inputs from SAP IBI System on Actual Cost on GBS Service delivery
2) Validate Replicon input transaction data elements with the MDM definition for validity and time dependency.
3) Provide consolidated inputs to SAP PCM application after aggregation of valid transaction records to PCM required to run the PCM cost allocation engine.
4) Data Mart solution to
- Report on actual and plan CMF results.
- Analyze time tracking data to report on actual effort spent by BSC associates including their operational discipline like timesheet compliance & submission status.
5) Reporting solution to provide standard canned reports and Dashboard to help GBS stakeholders with operational performance review and decision making.
3.3. Out of Scope
This document does not cover
1) Actual Revenue breakup by cost objects, Volumetric driver data to allocate Bill of Materials will be directly uploaded into SAP PCM and not maintained in CMF
2) Solution for integrating Order Management Framework data into CMF Data Mart and reporting on Demand and Capacity management KPI. This may be a future requirement and will be dealt with in a separate document in subsequent phase.
3) Automatic interface from MDM to various downstream applications that consume the master data maintained in MDM.
4.0 Detailed Solution Requirements – MDM
4.1. Dimensions and Data Model
FRS ID / Detail / URS IDFRS-001 / Master Data Management Solution to cater to GBS master data maintenance requirements. / URS-MDM008
URS-MDM002
URS-MDM004
URS-MDM005
URS-MDM007
Attached logical data model and physical data model for the MDM solution
4.2. Business Rules in MDM
Table / Logic / Validations required / ExampleAPQC Process (8) / Must start with 2 letters plus 6 digit numeric code / None / PC030302
APQC Process Group (6) / Must consist of the first 6 digits of the APQC Process code / When creating a new APQC Process Code for which no higher level APQC Process Group exists system should determine new APQC Process Group Code and ask for description / PC0303
APQC Process Category (4) / Must consist of the first 4 digits of the APQC Process Code / When creating a new APQC Process Code for which no higher level APQC Process Category exists system should determine new APQC Process Category Code and ask for description / PC03
Service (8) / Must start with 2 letters plus 6 numeric digits / Mandatory to assign Service Group Code, Service Type, PCM Relevancy Flag and Service Chargeability Code / SE100008
Service Group (5) / Must consist of the first 5 digits of the Service Code / When creating a new Service Code for which no higher level Service Group Code exists system should determine new Service Group Code and ask for description / SE100
Service Type (2) / Free 2 digit alphanumeric code / None / 30
PCM Relevant (1) / 1 digit Y/N flag / Only 2 choices, namely Y= Yes and N = No / Y
Service Chargeability (2) / Free 2 digit alphanumeric code / None / 01
Product (6) / Free 5 digit alphanumeric code / None. Mandatory to assign Service, Product Group and Product Category Code / 100000
Product Group (3) / Free 3 digit alphanumeric code / None / 100
Product Category (2) / Free 2 digit alphanumeric code / None / 10
Customer (10) / A) If the division that the customer is linked to is equals '11' (Pharma Division customer) then the customer code must be determined programmatically as follows:
- First 4 letters must be set equals to the Company Code that the customer is linked to followed by a underscore sign '_', e.g. 'AT06_'
- add digits 6&7 equals to linked division code, i.e. '11', i.e. customer code becomes 'AT06_11' (normal case)
- For 8th digit propose nothing but allow user to add a 1 digit numeric code, such as '1' for regional office, i.e. 'AT06_111' (digits highlighted in blue cannot be determined by user, only 8th digit highlighted in red can be set by user in exceptional cases, however, only numeric values are allowed
B) If the division that the customer is linked to a division other than '11' (> Pharma Division customer) then the customer code must be determined programmatically as follows:
- First 4 letters must be set equals to the Company Code that the customer is linked to followed by an underscore sign '_', e.g. 'AT06_' (same logic as for A)
- add digits 6&7 equals to linked division code, e.g. '14' for Sandoz Division, i.e. customer code becomes 'AT06_14' (same logic as for A)
- MDM to default 8th digit as '_' but allow user to override defaulted underscore '_' sign with a numeric code (new logic), such as '1' for regional office, i.e. 'AT06_141', however, only numeric values are allowed (similar logic for A)
- Set digits 9-10 = '11', i.e. customer code becomes either 'AT06_14_11' (normal case) or 'AT06_14111' (exception) / Customer Code can be 7, 8 or 10 digits long.
Company Code, Division Code and Geographic Area Code are mandatory.
Users can only determine digit 8 on their own, i.e. all other codes are determined programmatically based on linked company and division code.
If the division code of the customer = '11' then the 8th digit can only be a number (0-9) and never an underscore '_', letter or a special character
If the division code of the customer > '11' then the 8th digit can only be an underscore '_' or a number (0-9) but never a letter or a special character /
AT06_11
AT06_111
AT06_14_11
AT06_14111
Company Code (4) / 4 digit alphanumeric code / Code cannot be shorter than 4 digits / AT06
Division Code (2) / 2 digit alphanumeric code / Code cannot be shorter than 2 digits / 14
Geographic Area (3) / 3 digit alphanumeric code / None, code can be shorter than 3 digits, in fact mostly it will be 2 digits / AT
Geographic Area Group (2) / 2 digit alphanumeric code / None, code can be shorter than 2 digits / 10
Franchise (8) / 8 digit alphanumeric code / Code must be 8 digits long, i.e. not allowed to be shorter / 1101SC01
Function (2) / 2 digit alphanumeric code / Code must be 2 digits long, i.e. not allowed to be shorter / 30
Func_Franchise / 12 digit alphanumeric field:
- first 2 digits to be set to 'FF'
- then ask user to select franchise and function code
- MDM to then add first 4 digits of franchise code to the prefix 'FF' (e.g. FF1101)
- MDM to then add function code to the above 6 digit code (e.g. FF110130)
- MDM to add digits 5-8 of franchise code to the above 8 digit code (end result e.g. FF110130SC01) / Code must be fully constructed by MDM based on Franchises and Functions created by user. As a result, no validations to be done / FF110130SC01