Version 1.8 | 8-21-2014 Johnson Controls | EA & PM COE SAP Master Data Governance Hub (EIM) Emerging Standard Request 1 Application Technologies Single system for creating, storing as well as source of master data elements. Business Strategy Business Area Business Objective Vendor Scope Functionality • Have a single source for supplier, customer & product master data. • Provide a way by means of which downstream systems (consumers) requesting this master data can read & download master data • Integrate governance within business processes from the creation of master data • Deliver a single version of master data for supplier, product, customer, or user-defined objects Software Product Version SAP Business Unit Enterprise Corporate SAP Master Data Governance Hub V7.0 JCI Process Framework 14.04.07 Enterprise Information Management > 14.04.07.02 Manage & Maintain Master Data Management Hub Presenter David Start
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Version 1.8 | 8-21-2014
Johnson Controls | EA & PM COE
SAP Master Data Governance Hub (EIM)Emerging Standard Request
1
Application Technologies
Single system for creating, storing as well as source of master data elements.
Business Strategy
Business Area
Business Objective
Vendor
Scope
Functionality
• Have a single source for supplier, customer & product master data.• Provide a way by means of which downstream systems (consumers) requesting
this master data can read & download master data
• Integrate governance within business processes from the creation of master data• Deliver a single version of master data for supplier, product, customer, or user-
defined objects
Software Product Version
SAP
Business Unit
Enterprise
Corporate
SAP Master Data Governance Hub V7.0
JCI Process Framework 14.04.07 Enterprise Information Management > 14.04.07.02 Manage & Maintain Master Data Management Hub
Presenter David Start
Version 1.8 | 8-21-2014
Johnson Controls | EA & PM COE
Usage Guidelines This software product will become the system of record and thus a single source of truth for enterprise master data. Enterprise Master Data domains include but not limited to enterprise customer, product & supplier data
Upstream: SAP Information Steward & Data ServicesDownstream: Unity SAP ECC instance, any other applications that need customer, product, supplier master data
Application will be supported by Enterprise MDM team along with GI.
SAP Master Data Governance Hub (EIM)Emerging Standard Request
2
Support Framework
Initial Cost
Integration Requirementsand Capabilities
Alternative SolutionsConsidered Informatica MDM, IBM Infosphere
Potential Savings Per Year
Applications to be Retired?
Emerging Standard Justification
03/05/2016Date to Review Findings
Provide EAGC Meeting Date
None
New Application. No savings identified.
Deliverables Environment is successfully stood up and atleast one master data domain is successfully implemented in the solution
Enterprise wide Master Data Management as a discipline is new to JCI and so is this toolset. The reason for emerging standard is to ensure the product is a right fit for JCI before it is elevated to an enterprise standard
Annual Recurring Cost Annual Recurring Cost is 17% of 1x
Minimum 1x: $150,000 per 5000 objects, Maximum 1x: $15m for 500,000 object. The # of objects will not be known until after detailed design.
Licensing/Modeling Cost # of objects
Version 1.8 | 8-21-2014
Johnson Controls | EA & PM COE
Enterprise Architecture Governance Council Request Dashboard
3
Oth
er A
reas
Ente
rpris
e A
rchi
tect
ure
Pr
inci
ples
LegendRed – There is a significant risk identified.Yellow – Not enough data available to evaluate but there may be a potential risk.Green – There is no risk at all.
Insert dial rating image from
Appendix here.
Natural Boundaries
Insert dial rating image from
Appendix here.
Extensibility
Insert dial rating image from
Appendix here.
Application Language
Insert dial rating image from
Appendix here.
Business Alignment
Insert dial rating image from
Appendix here.
Strategic Platform/Vendor
Insert dial rating image from
Appendix here.
Commonality
Insert dial rating image from
Appendix here.
Security
Insert dial rating image from
Appendix here.
Global Infrastructure
Insert dial rating image from Appendix here, if applicable.If not applicable, place ‘Not
Applicable’ image here.
Unity
Insert dial rating image from Appendix here, if applicable.If not applicable, place ‘Not
Applicable’ image here.
SAP
Rating: Green Rating: Green Rating: Green
Rating: Green Rating: Green
Rating: Green Rating: Green
Rating: Green
Rating: Green Rating: Green
Version 1.8 | 8-21-2014
Johnson Controls | EA & PM COE
Gartner Quadrant Report
4
Product MDM Customer MDM
Version 1.8 | 8-21-2014
Johnson Controls | EA & PM COE
Application Checklist
5
Parameter Answers Contact Checklist Reference
Disaster Recovery
Review completed Risk ManagementDan Walker
• DR strategy should account for both Cloud Provider and JCI loss of service
• Backup Frequency, Retention Period clearly defined
Compliance Until a specific use case is identified, doing a PIA doesn’t make sense. The team is advised to have a PIA completed, once the technology is implemented and a use case has been identified
Risk ManagementPatti Suarez
Review/Approval• Follow PIA Process if Application stores Employee or Customer
information• Review Works Council Impact • Process may take 2-4 weeks, pending type of request. Make
sure to complete their required documentation to receive the required feedback. http://my.johnsoncontrols.com/portal/myportal/corp/jci/privacy
• Select: Privacy Deliverables for Projects
Data Management
ProcurementDoug MacFarland
• Clear Data Ownership by JCI• Identify any hidden/unreasonable charges for Data Volume transfer• Data has to be in agreed Usable format
Availability ProcurementDoug MacFarland
• Performance SLA should be defined based on Criticality• Penalties should be defined for not meeting SLA
Vendor Management
ProcurementDoug MacFarland
• Clear Exit Clause• Is the Vendor considered Strategic for JCI?• Does the Product align with Major JCI platforms (SAP, Oracle, GI
Strategy)? Preferred• Exit clause should be short preferably 1 year for convenience and
Performance
Application Architecture
Doug MacFarland Preferred• Multi-tenant, Subscription based, Configurable vs. customized
Integration All integrations are inner ring Enterprise IntegrationGriffith, Phil J
• Does the vendor use industry standard APIs?Preferred• Web Services Enabled• Existing connectivity using Cast Iron• Standard API across all customers , not specific to JCI
Financial Will depend on Request.
• TCO Analysis of On Premise vs. CloudCloud Cost should include:• Conversion Cost, Capital expenditure, Operational expenditure• Overhead costs
Insert the green, yellow, or red dial rating image
from Appendix here.
Assessed By: Gail R Delafose
Insert the green, yellow, or red dial rating image
from Appendix here.
Privacy: Once a use case is identified, PIA should be completedDisaster Recovery: DR checklist has been completedSecurity: Since application is in-house, no security assessment is required
Application uses SSO & uses GI approved design patterns
Insert dial rating image from Appendix here, if applicable.
If not applicable, place ‘Not Applicable’ image here.
The solution is a Unity requested solution
What SAP Modules are required for the Solution?
SAP
Assessed By: Abhinav Gautam
Insert dial rating image from Appendix here, if applicable.
If not applicable, place ‘Not Applicable’ image here.
This is a new SAP function added to the environment.
How will the Solution integrate with the SAP Modules?
The solution will integrate with legacy SAP ECC. Driven by Unity requirement and design. I would need to understand what integration if any is planned with existing SAP instances. If this is planned primarily for Unity with no integration back in to Legacy systems, I am OK , otherwise need to understand the nature of integration.
Does the solution align well with defined corporate direction and strategic needs of the business?
Question 1: Is the solution extensible and scalable in a cost effective manner?
Question 2: Is the data easily accessible for reporting downstream systems and integrations?
Business Alignment
Strategic business direction is to have a single source of record for customers, suppliers and product. This solution achieves that strategic business direction. Hence this solution is fully aligned.
Assessed By: David Start
Insert the green, yellow, or red dial rating image
from Appendix here.
Extensibility
Insert the green, yellow, or red dial rating image
from Appendix here.
Assessed By: Rohin Irani, Enterprise Architect
Data will be available to downstream systems to consume. Standard out of the box integrations will be used for the integration.
Solution can be scaled both horizontally as well as vertically.
Question 1: How well does the solution leverage common solutions and IT standards across Enterprise?
Question 2: Does the system integrate using JCI Enterprise Integration bus?
Question 3: Does the solution help simplify IT landscape and ease of use?
Commonality
No current standard exists in this space. This space is new to JCI. The proposed solution is requested to become a standard
Rohin Irani, Enterprise Architect
Insert the green, yellow, or red dial rating image
from Appendix here.
Inbound: This system will take a feed from various ERP master data sources in the environment. Whether those feeds will flow through ESB is yet to be determined.
Outbound: The system will directly integrate with SAP ECC. Since both SAP MDG & SAP ECC are considered inner ring, the integration will not go through ESB.
This is a new tool introduced in JCI and does not simplify IT application portfolio landscape. However, it does significantly clean up the data landscape by becoming the single source of truth for all master data (customer, product & suppliers)
Question 1: Is the solution designed to provide greater benefit to the enterprise versus a particular business unit?
Question 2: Is the data consumed by the solution provided by source applications?
Assessed By:
Natural Boundaries
The proposed solution will serve as the enterprise master data source. This solution provides benefit to the enterprise versus any specific BU
Rohin Irani, Enterprise Architect
Insert the green, yellow, or red dial rating image
from Appendix here.
There are various disparate master data sources that will provide the data to be consumed by this application. The exact source applications is yet to be determined.
1. Business Alignment 2. Extensibility IT solutions will align with the JCI business modelJohnson Controls will continuously ensure that, as an organization, it is cognizant of its changing business environment. In addition, it will ensure that its investment and capability are demonstrably aligned with its defined corporate direction and that they are driven by the strategic needs of the business.
Solutions will be extensible and scalableJohnson Controls must actively strive to design, build and invest in change that enhances the adaptiveness, flexibility and agility of its environment — in order to optimize its capability to be reconfigured and realigned to accommodate changes in business direction and objectives in a timely, cost-effective manner.
3. Commonality 4. Natural Boundaries Leverage common solutions & IT standards across JCI Johnson Controls will first strive to leverage common solutions that address multiple needs and that provide enterprise wide benefits over silo solutions.Note: This principle does not imply that individualized solutions are not acceptable. Rather, it is emphasizing the benefit of actively seeking to develop standardized solutions to business needs.
IT solutions designed using inner/outer ring Architecture management decisions are made to provide maximum benefit to the enterprise as a whole. Preserve the holistic groupings that define the business.
5. Strategic Platform/Vendor 6. Application LanguageLeverage strategic platform/vendor partners firstJohnson Controls balances solution costs against architectural flexibility. Understanding and managing platform & vendor partners is essential to optimizing Johnson Controls’ enterprise for current and future needs.
Global applications will support JCI defined end-user languagesLanguage diversity is controlled to minimize the non-trivial cost of acquiring or adapting solutions to support multiple languages.
Version 1.8 | 8-21-2014
Johnson Controls | EA & PM COE
Rating: Yellow Rating: Red
Appendix; Template Images
13
LegendRed – There is a significant risk identified.Yellow – Not enough data available to evaluate but there may be a potential risk.Green – There is no risk at all.