présentation mdm pim.pdf

Using IBM InfoSphere Master Data Management

forProduct Information Management

Module 1

Introduction to MDMPIM

1-1

1-2

Course Objectives

● Gain an understanding of Master Data Management (MDM) and Product Information Management (PIM)

● Become familiar with Master Data Management for Product Information Management’s (MDMPIM) Web-based tooling, navigation, security, workflow and scripting language

● Provide an overview of MDMPIM and exercises that explore the product features● Explore standard practices using MDMPIM

1-2 Using IBM InfoSphere MDMPIM

1-3

Course Requirements

● This is an introductory course for MDMPIM and assumes no prior knowledge of the solution. However, it is presumed that you have some basic knowledge / understanding of:

– Using a Personal Computer– Working with a Web browser (specifically IE)– Product / Item data in a business context

Introduction to MDMPIM 1-3

1-4

Introductions

● Name● Company● Where you live● Your role using IBM MDMPIM● Class expectations


1-5

Class Logistics

● Class starts at 9 a.m.● Class ends at 5 p.m.● Lab room availability● Topics not on agenda● Outside business● Restrooms / fire exits● Local amenities


1-6

Course Materials

● Student Workbook– Presentation slides– Labs

● References– Product documentation and more, available online at

http://publib.boulder.ibm.com/infocenter/pim/v6r0m0/index.jsp • Overview Installing • Migrating • Integrating with other products • Solution architecture • Solution development • Managing product information • Administering • Troubleshooting and support • Reference


1-7

Agenda – Day 1

1) MDMPIM Overview (1 day)a)Concepts of MDMb)MDMPIM Business Casec)PIM Modelsd)Methodologye)Architecturef) Data Objects and content modeling

2) Working with MDMPIMa)Initializing MDMPIM– Lab Exercises

b)Data Objects and Content Modeling– Lab Exercises


1-8

Agenda – Day 2

3) Working with MDMPIM (continued)c)Attribute Collections and Views– Lab Exercises

d) Specifications– Lab Exercises

e) Browsing, Searching and Selecting– Lab Exercises


1-9

Agenda – Day 3

4) Working with MDMPIM (continued)f) Security: Organizations, Access Control Groups, and Roles– Lab Exercises

g)Workflows and Collaboration Areas– Lab Exercises

a)Importing to and Exporting from Existing MDMPIM– Lab Exercises


1-10

Agenda – Day 4

5) MDMPIM Case Studya)Case Study Work Time and Presentationsb)Implementation Challengesc)Course Review and Evaluation


1-11

Course Evaluation

● On the final day of class, please complete and return course evaluation– It can be found in the appendix of your Student Notebook


1-12

What is Master Data

● The facts describing a company’s core business entities: customers, suppliers, partners, products, materials, chart of accounts, location and employees

– The high value information an organization uses repeatedly across many business processes

– Generally used across multiple LOB– The data is decisive (currency, quality) for these business processes, and often a

prerequisite for service-orientation ● Master Data is critical because it provides the business context by providing

concrete data models and processes for a particular domain● Master Data does not imply a particular usage pattern● Master Data is typically scattered within heterogeneous application silos across

the enterprise– Numerous applications / many subsidiaries / various LOBs– Inhibitor of a full scope enterprise transformation


1-13

Master Data Management

● Decouples master information from individual applications

● Becomes a central, application independent resource

● Simplifies ongoing integration tasks and new app development

● Ensures consistent master information across transactional and analytical systems

● Addresses key issues such as data quality and consistency proactively rather than after the fact in the data warehouse


1-14

IBM Point of View (1 of 2)

To achieve business optimization, market leaders require insight into….

● Customers and their behavior● Products and their performance● Partners and their effectiveness● Locations and their uniqueness● Assets and their utilization

…in order to tailor their business processes for competitive advantage


1-15

IBM Point of View (2 of 2)

Master Information and Master Data Management are critical enablers of business optimization by creating a single version of the truth and consistently interpreting information across all stakeholders.

● Customer Centricity● Product and Service Optimization● Risk and Compliance● Threat and Fraud Intelligence


1-16

Product Information Management – Current Processes


1-17

What is Master Data Management for Product Information Management

● Master Data Management for Product Information Management provides the solution for managing product information:

– Provides a centralized repository with processes to support the management and standardization of product information.

– Delivers product information to multiple channels in which products are sold, including e-Commerce applications, printed documents, marketing collateral, kiosks, and mobile devices

– Synchronizes internally with existing enterprise systems– Synchronizes externally with business systems and trading partners


1-18

Summary

● Now that you have completed the unit, you can:● Understand the primary objectives of this training course● Identify where MDMPIM fits into the overall MDM space




Module 2

Concepts of MDMPIM

2-1

2-2

Unit Objectives

● Brief Introduction to MDM Concepts● IBM’s Point of View on MDM● Components of MDM and their relevance by industry● Significance of Product Information within the MDM realm


2-3

What is Master Data

● The facts describing a company’s entities: customers, suppliers, partners, products, materials, chart of accounts, location and employees

– The high value information an organization uses repeatedly across many business processes

– Generally used across multiple LOB– The data is decisive (currency, quality) for these business processes, and often a

prerequisite for service-orientation ● Master Data is critical because it provides the business context by providing

concrete data models and processes for a particular domain● Master Data does not imply a particular usage pattern● Master Data is typically scattered within heterogeneous application silos across

the enterprise– Numerous applications / many subsidiaries / various LOBs– Inhibitor of a full scope enterprise transformation

Concepts of MDMPIM 2-3

2-4

Master Data Business Problem

● There is a lack of strategic control over data and business processes

● The full value of information is not being leveraged

● Trusted information is not available when and where it is needed

● Total IT costs are on the rise due to inefficient business processes

● There is a lack of focus on core competencies● Inflexibilities across the board make the

business slow to respond to changes


2-5

Imbalance of Data in the Enterprise


2-6

Master Data Is Distributed All Over

● How much of this data is Outdated? Incomplete? Inconsistent? Inaccurate?● When a data element changes, what are the ramifications across an enterprise?


2-7

Drivers of Deploying Master Data Management Solutions

● Gain control of core business entities:– Party: Customer consolidation, consumer privacy, marketing optimization, relationship

management– Product: Multi-channel commerce, new product introduction, global data

synchronization, RFID– Supplier: Vendor consolidation, spend management, procurement optimization

● Address compliance mandates, legislation and liability requirements– Fraud detection, homeland security and hazardous materials– Sarbanes Oxley, HIPAA, PIES, ACORD, Patriot Act, Tread Act, etc.

● Support dynamic business environments: Outsourcing, mergers and acquisitions, ERP deployments, application consolidation and data warehousing / business intelligence initiatives

Compelling business cases around cost reduction, revenue enhancement, customer satisfaction, compliance, time to market


2-8

Master Data Management Solutions

● Master Data Management Solutions help gain control over comprehensive Master Data and Business Processes

– Master Data Management (MDM) is the set of disciplines, technologies and solutions to create and maintain consistent, complete, contextual and accurate business data for all stakeholders across and beyond the enterprise

● Master Data Management plays many critical roles in a modern service oriented architecture

– A common source of accurate, consistent and comprehensive master information– Common business services supporting consistent information-centric procedures

across all applications– Business process support to integrate with or drive business processes across

heterogeneous applications


2-9

The Benefits of Master Data Management

● Decouples master information from individual applications

● Becomes a central, application independent resource

● Simplifies ongoing integration tasks and new app development

● Ensure consistent master information across transactional and analytical systems

● Addresses key issues such as data quality and consistency proactively rather than after the fact in the data warehouse


2-10

IBM Master Data Management

Multi – Domain

● Partner ● Product● Customer● Account● Location

Multi – Style

● Collaborative● Operational ● Analytical

Multiple Business Processes

● New Product Introduction ● Customer Centricity ● Householding


2-11

IBM MDM Manages a Complete Data Lifecycle

● Collaborative MDM publishes rich information into the data lifecycle

● Operational MDM ensures a consistent and synchronized set of processes via Web services

● Analytical MDM leverages an enterprise master view to gain insight into your business processes

● IBM MDM business services integrate with application business processes to provide accurate and complete master data


2-12

Enterprise Architecture – Placeholder for MDM


2-13

MDM Architecture Principles

The Master Data Management Architecture should …

• provide the ability to decouple information from enterprise applications and processes to make it available as a strategic asset for use by the enterprise.• provide the enterprise with an authoritative source for Master Data that manages information integrity and controls the distribution of Master Data across the enterprise in a standardized way that enables reuse. • provide the flexibility to accommodate changes to Master Data schema, business requirements and regulations, and support the addition of new Master Data. • be designed with the highest regard to preserve the ownership of data, integrity and security of the data from the time it is entered into the system until retention of the data is no longer required.• be based upon industry accepted open computing standards to support the use of multiple technologies and techniques for interoperability with external systems and systems within the enterprise.• be based upon a architectural framework and reusable services that can leverage existing technologies within the enterprise. • provide the ability to incrementally implement a Master Data Management Solution.


2-14

Components of MDM – Industry Dependence

● Product ● Customer● Other Master Data

– Location– Party / Trading Partner– Trade Terms / Contracts, etc.


2-15

Deploying Master Data Solutions

● What:– Master data information solutions look to provide a source to centralize and

standardize master data around different domains including, (but not limited to) party/customer, product, and supplier data.

– One of the primary objectives of consolidating master data is to ensure there is only one source of truth for a particular domain across an enterprise; this directly has an impact on decreasing costs and increasing revenue.

DATA DOMAIN EXAMPLES VALUE PROPOSITION

Party/ Customer Increased revenue through greater enterprise-wide insight into customers and their relationships.

Product Increased revenue and reduced costs through improved data quality and shorten time to market for new products.

Supplier Management of supplier relationships is more controlled, allowing for streamlined communication, improved procurement processes, and insight into buying patterns.


2-16

MDM Solutions: Focus on Product Information Management (PIM)


2-17

Synchronization Challenge – Retail Industry


2-18

How Big is the Product Information Problem?


2-19

MDMPIM Capabilities


2-20

Summary

● Now that you have completed the unit, you can:● Understand the concept of master data and the need for master data

management● Explain the typical data management challenges industries face ● Describe the key components of master data


2-21

Group Assignment

● Pick an organization that you worked with and list out its different legacy and transactional systems (This includes ERP, CRM, SCP, Order Management and any relevant IT system or database used to capture business information.)

● Identify the master data that is common across these systems● Focus on data redundancies and illustrate the pain points in managing such an

inter-dependent IT division● Propose a strategy to address the above identified issues

– Be creative and feel free to come up with your own solution – Try to focus on the end result and not on terminology

● Present your findings to the rest of the group



2-22



Module 3

The Business Case for MDMPIM

3-1

3-2

Learning Objectives

● Identify the challenges facing modern product information management● Recognize the needs for efficient product information management● Position Master Data Management for Product Information Management in a

software solution● Understand a typical product information management data flow● Illustrate the business case for MDMPIM through a few sample scenarios


3-3

Information Explosion – A Common Issue

● Today’s industries face constant change – churning market demand, fleeting consumer preferences and continual technological advances. This is significantly impacting the way information is managed.

● Factors contributing to heterogeneity in IT systems:– Mergers and Acquisitions– Independent deployment of applications within different business units– Customization of software and data to suit individual needs

● Typically companies manage multiple versions of Product and Customer data across a number of their legacy and transactional systems.

The Business Case for MDMPIM 3-3

3-4

Industries’ Current New Item Introduction Process EDI, Paper, Spreadsheets, Phone, Fax, e-mail


3-5

Business Impact of Inefficient Systems

79% of retailers and 61% of consumer packaged goods (CPG) manufacturers rank “item management” as their top priority

● Errors in data – 30% of data in retailers systems is wrong● Lost productivity – 25 minutes manually cleansing an SKU each year● Slow time to market – 4 weeks to introduce new products● Invoice deductions – 43% of invoices result in deductions● Failed scans – up to 70,000 per week (1 large US retailer)● Lost sales – up to 3.5% per year

– Source: A.T. Kearney, GMA


3-6

Industry Catalysts are Creating Urgency

Multiple initiatives require companies to gain control of product information

● UCCNet and GS1 global registry● Global data synchronization● Global trade item numbers (GTIN) and Sunrise 2005● Radio frequency identification (RFID) and electronic product codes (ePC)● Web services and on demand services● AAIA Standards such as PIES and ACES are influencing the players within the

automotive aftermarket industry.


3-7

Key Issues in Managing Product Information


3-8

What is Master Data Management for Product Information Management?

● Master Data Management for Product Information Management provides the solution for managing product information:

– Provides a centralized repository with processes to support the management and standardization of product information.

– Delivers product information to multiple channels in which products are sold, including e-Commerce applications, printed documents, marketing collateral, kiosks, and mobile devices

– Synchronizes internally with existing enterprise systems– Synchronizes externally with business systems and trading partners


3-9

Master Data Management for Product Information Management – the Golden Source of Product Information


3-10

Complex Product Information Requires a PIM System


3-11

Solve the Multi-Dimensional Business Problem


3-12

MDMPIM Linkage, Context, and Semantics Turns Data into Information

... for all types of enterprise reference data


3-13

Who is Using PIM?

● Retailers, consumer products, and consumer electronics manufacturers are some of the leading industries that are broadly adopting product information management

– These companies depend on accurate, timely, and comprehensive product information to drive sales and reduce expenses

– They are also facing external mandates for initiatives, such as global data synchronization (GDS), and radio frequency identification (RFID)

– Upcoming e-commerce and business-to-business (B2B) initiatives also require companies to keep their product and service information consistent across all customer and trading partner touch points

● IBM offers numerous solutions that are based upon and leverage the capabilities of its comprehensive product information management offering, Master Data Management for Product Information Management and Global Data Synchronization


3-14

Business Integration of People, Processes, and Information

● Extend business processes to trading partners● Choreograph standalone applications to composite business processes● Broker and optimize high speed communications between applications● Provide a common view of diverse and distributed information


3-15

Publish Information on demand to employees, trading partners, and customers


3-16

Product information management has clear, demonstrated ROI


3-17

Product information management is foundational


3-18

Where else can Master Data Management for Product Information Management be used?


3-19

Leverage MDMPIM Business Integration seamlessly between internal and external touchpoints


3-20

Typical PIM Use Cases

Common use cases where MDMPIM has been positioned include:

USE CASE SHORT DESCRIPTION

New Product Introduction/Item Master

Solution to consolidate and provide a source or record/origin for all product information, including the setup of new products

PIM for eCommerce Product information management for Commerce Web sites

PIM for Publishing Product information management for print catalog solutions

Global Data Synchronization

Solution to manage item content between suppliers and retailers via Industry std messaging and industry hosted entities (called data pools)

Supplier Portal Retailer solution which enables suppliers to enter and maintain their item content

Master Data Repository Master for managing and linking multiple MDM entities (for example, Item, Vendor, Customer, Location)

Item Creation and Item Registry

Solution to support internal enterprise synchronization by the generation of an internal item number and global attributes

PIM for Part Re-use Solution for user to identify and leverage similar items across enterprise via guided navigation and item workflow


3-21

Typical product information management flow


3-22

MDMPIM: Business Integration Retail Scenario

MDMPIM


3-23

Implementation strategy for manufacturers


3-24

IBM trading partner collaboration visionis founded on product information management


3-25

Deploy trading partner portals


3-26

Sample Scenario – 1

● Customer Background– European leader in retail office supplies

operating in Europe, Asia and Canada– Sales (2004): 1561 M€ (90% in Europe)– 19 subsidiaries and 8700 employees– Catalog of 5000 products for each

subsidiary


3-27

Sample Scenario – 1 (Business Problem)

● Business Problem– Slow production time of paper catalogs and high cost of catalog preparation– Inability to publish customer-specific catalogs to multiple channels – Process inefficiencies with managing product information


3-28

Sample Scenario – 1 (Solution Details)

● Solution Overview:– Using MDMPIM, implemented 1 group catalog and 1 catalog in each subsidiary– Integrated MDMPIM with SAP for importing daily new product information.– Imported and input technical and marketing data (enrichment)– Integrated MDMPIM with MVS Print solution for paper catalog output– Automated generation of customer-specific electronic catalogs


3-29

Sample Scenario – 1 (Solution Architecture)


3-30

Sample Scenario – 1 (Solution Benefits)

● Major benefits of implementing an IBM MDMPIM solution:– Improved ability to meet customer needs increases customer satisfaction and drives

increased sales– Catalog creation process streamlined and expedited – Valuable Marketing and Sales resources are freed up from collecting data for

catalog production to focus on core competencies


3-31

Sample Scenario – 2

● Customer Background:– Leading North American specialty

retailer with over 7000 stores, more than 500 wireless and mall-based kiosks

– Average physical store contains 3,600 items

– $4.8 billion annual revenue (2004)


3-32

Sample Scenario – 2 (Business Problem)

● Business Problem – Inability to provide online customers with more buying choices. Company directive was

to grow SKU assortment from 4,800 to 20,000 SKUs– Inability to offer Web-only promotions to drive Web-specific business for both third

party and company brand products– Incomplete or total lack of compelling product information published on e-commerce

Web site, which has shown to have a direct impact on online sales– Lack of foundation for managing product information for other sales channels (stores,

kiosks, print catalogue and flyers) in future● Overall Desire: Increase Web profits and market share


3-33

Sample Scenario – 2 (Solution Details)

● Solution Overview– Provided an enterprise product content repository to consolidate and enrich product

information for feeding ecommerce and other sales channels such as print catalog and store kiosks

– Combined basic product information from Retek merchandising solution with additional information from CNET and drop ship providers (Ingram Micro and others) for over 5,000 Branded SKUs and 10,000 drop-ship SKUs

– Provided category based security to route new products to users who are responsible for a category

– Categorized new products to consumer (Web) hierarchy and populated 60+ attributes pertaining to the category (such as Cordless phones, Camcorders, Televisions, etc.)

– Managed retail and promotional pricing for ecommerce channel– Synchronize enriched product information as well as prices and promotions with the

ecommerce site (GSI Commerce)


3-34

Sample Scenario – 2 (Solution Architecture)

● MDMPIM Solution: PIM for eCommerce– Create a common repository for product content to feed their customer Web site– Provide workflow processes to increase time to market for new products and eliminate

process inefficiencies– Expand and ensure the quality of the product content

● Solution Architecture:

MDMPIM


3-35

Sample Scenario – 2 (Solution Benefits)

● Major benefits of implementing an IBM MDMPIM solution:– Improved customer’s online shopping experience resulting in increased sales – Processes to manage product information streamlined, and more effective– Consolidated product information supporting multiple sales channels


3-36

Summary

● Now that you have completed the unit, you can:● Understand the needs for efficient product information management● Explain what challenges industries face with current product information systems● Discuss the IBM vision for product information management● Discuss leveraging the golden source of product information● Describe a typical product information management flow● Walkthrough some typical use cases for Master Data Management for Product

Information Management


3-37

Exercise

● In teams of 2, write down the Top 3 business benefits of PIM● In 5 minutes, each pair will explain their top 3 benefits● A final review of the MDMPIM top 10 business benefits will then be revealed


3-38

The MDM for PIM Top 10 Business Benefits!

1) Reduces operational costs by streamlining processes around product information management

2) Provide faster time-to-market of product data enabling additional sales opportunities

3) Enables rich content authoring for different sales channels4) Provides security and control around product information5) Improves overall data quality and accuracy 6) Supports external data synchronization with trading partners7) Supports both internal and external data synchronization with up and downstream

systems8) Standardizes and consolidates product information eliminating disparate, one-off

systems and processes9) Reduces business dependency on IT10)Compliance with industry-specific mandates and regulations




Module 4

Typical PIM Models

4-1

4-2

Unit Objectives

● Provide a detailed overview of some of the most common PIM use cases:– PIM for New Product Introduction (NPI)– PIM for Commerce– PIM for Publishing– Global Data Synchronization (GDS)– Vendor Portal Solution

● Identify the pain points, solution components, and value proposition for each of the above use cases

● Understand how to leverage MDMPIM to address these scenarios


4-3

Introduction to PIM Solutions

● IBM has identified the following use cases to be common to many of our customers across different geographies and industries:

USE CASE SHORT DESCRIPTION

New Product Introduction/Item Master

Solution to consolidate and provide a source or record/origin for all product information, including the setup of new products.

PIM for eCommerce Product information management for Commerce Web sites

PIM for Publishing Product information management for print catalog solutions

Global Data Synchronization

Solution to manage item content between suppliers and retailers via Industry std messaging and industry hosted entities (called data pools)

Vendor Portal Solution Retailer solution which enables suppliers to enter and maintain their item content

Master Data Repository Master for managing and linking multiple MDM entities (e.g. Item, Vendor, Customer, Location)

Item Creation & Item Registry

Solution to support internal enterprise synchronization by the generation of an internal item number and global attributes

PIM for Part Re-use Solution for user to identify and leverage similar items across enterprise via guided navigation and item workflow

Typical PIM Models 4-3

4-4

Why Focus on New Product Introduction (NPI)?

● The focal point of any company are the products they bring to market.● In order for companies to remain competitive in the marketplace, they need to

deliver new products to market quickly and efficiently while providing end consumers with complete, accurate information about these products.

● The volume and complexity of information required to bring new products to market has skyrocketed

– As systems environments are becoming outdatedand unable to accommodate such a demand, most companies are struggling to keep their competitive edge.


4-5

Inefficient NPI Key Pain Point Driving PIM Adoption


4-6

NPI Pain Points

● Slow time to market for new products (4-6 weeks)● Data inaccuracies and inconsistencies in internal systems● Inaccurate and inconsistent data presented to customers● Manual, paper-based process inefficient and error prone● Validation rules inconsistent and undocumented● Inconsistent compliance checks create legal exposure● Large volumes of new product data are hard to keep up with

– Multiple data source/item repositories to manage product information• Silo solutions are created to support different departmental needs• Manual data entry in each solution takes time• Identification of known silos (many not known)


4-7

An example of the impact of inefficient NPI processes in Retail


4-8

Another example of the impact of inefficient NPI processes in Retail


4-9

An example of the impact of inefficient NPI processes in CPG


4-10

Proposed New Product Introduction Process Flow


4-11

MDMPIM Solution Approach – Functionality to Leverage for NPI solutions

● MDMPIM Import functionality – Import new product data from multiple sources including GDS, Vendor Portals, etc.– Consolidate existing product information from multiple legacy item and supplier

masters, identify and eliminate duplicates and standardize product and supplier information

● MDMPIM Data Modeling:– Support for all product referential attributes to support the creation of a new product.

● MDMPIM Search and Review functionality – Compare incoming product data against existing product data to avoid duplicate

product creation.● MDMPIM Workflow functionality

– Streamline business processes and eliminate process inefficiencies. Route product information to content owners/approvers in various departments (category management, finance, pricing, store operations, merchandising, etc.)

● MDMPIM Export functionality– Support for sending new and updated product information to dependent systems

which require it on a near real time basis.


4-12

New Product Introduction Value Proposition and ROI Measures

● Reduce Cost– Time spent processing new products from identification to fulfillment at the stores has

proven to be costly for retailers. – Inefficient processes require more people and take longer to execute. Efficient

processes typically require less people, therefore reducing labor costs. – Reducing the need for maintenance on multiple systems will reduce capital costs.

● Increase Revenue– Coordinating a product release for a specific season or promotion is critical to keep a

competitive edge and to get full price for products. • If the product arrives too late in the season, it may have to be sold at a reduced price which could result in a financial loss, as well as a loss of a customer.

– Coordination of ads and product availability also impacts revenue. If a product is not available when an ad says it will be, the customer may take their business elsewhere.


4-13

What PIM for eCommerce Customers want?


4-14

eCommerce Content – Product Information


4-15

Business Problem: Managing increasingVolumes and Velocity of Product Information

● Multiple back-end sources of product information ● Increasing velocity of change to site content compounds information complexity

– Apparel retailer: 10,000 products, significant time pressures of daily and weekly product content changes, multiple seasons, frequent promotions.

– Industrial distributor: 500,000 products, challenges of maintaining information from multiple manufacturers.

– Hard Goods retailer: 5 million+ products and services, 2,000stores, kiosks, a Web site and a partner network. Managingmulti-channel is a major issue.

– Electronics manufacturer: 5,000 products, 90 countries, 20 languages, complex product relationships, unstructured content (images, operation manuals) – challenges in managing processes such as translation.


4-16

PIM for eCommerce -- Solution Architecture


4-17

MDMPIM Solution Approach – Functionality to Leverage PIM for eCommerce Solutions

● MDMPIM Import functionality – Import of product data from multiple upstream sources (Merchandising systems,

vendor portals, etc.)● MDMPIM Data Modeling

– Support for attributes supporting eCommerce specific attributes(rich content) along with image relationships providing detailed, descriptive information to convert an online browser into a buyer

● MDMPIM Workflow functionality – Processes to support item enrichment and approval for Web site-specific product data

● MDMPIM Preview Capabilities– Review of product data in Web site format before publication, preventing potential data

errors from being published● MDMPIM Export Functionality

– Export data in multiple formats to support the requirements of best-of-breed commerce solutions


4-18

PIM for eCommerce Value Proposition

● Streamlined and efficient business processes around the introduction, enrichment and management of product informationfor data publication to an eCommerce solution

● Aggregation and enrichment of product information coming from multiple sources● Increased business user involvement in managing product data, reducing

dependencies on IT personnel● Maintain product versions to allow for repurposing of product content to support

seasonal publications


4-19

What Print Customers Want?


4-20

PIM for Publishing – Problem Statement

● Dispersed product data makes it difficult to produce printed catalogs and flyers in an efficient manner

● Typical print catalog processes are manual, time consuming, and error prone● Inability to reuse data across different catalog and flyer publications● Support for different print formats is difficult to achieve


4-21

PIM for Publishing - Solution Architecture


4-22

MDMPIM Solution Approach – Functionality to Leverage for PIM for Publishing

● MDMPIM Import functionality– To import and consolidate product data from multiple sources

● MDMPIM Preview capabilities– Review product data in specified format prior to export

● MDMPIM Workflow functionality – To support the gathering and enrichment of catalog-specific data

● MDMPIM Integration capabilities– Integration capabilities with tools such as MVS to support template layouts for print

solutions● MDMPIM Export functionality

– Export data in multiple formats to support the requirements of best-of-breed publishing tools


4-23

PIM for Publishing Value Proposition

● Aggregate and enrich product information coming from multiple sources in a centralized repository, eliminating the need to spend time and money re-creating or searching for data for a catalog or flyer.

● Create page layouts for various product categories specific to a variety of desktop-publishing tools such as Adobe InDesign or other third-party publishing systems, avoiding the need to manually reformat product data to meet a tool’s specifications.

● Automate and expedite the export of product information to publishing systems used to generate sales documents.

● Quickly and easily repurpose existing product content to support seasonal catalog publications, as well as collateral pieces like data sheets, print catalogs, and technical-specification documents


4-24

Global Data Synchronization (GDS)

What is it?

● The continuous matching of data attributes and values between two or more different systems

● Provides a standard, electronic framework for trading partners to exchange information

● Must be implemented both internally and externally

● External synchronization processes must utilize EAN.UCC standards


4-25

Global Standards for Product Information 153 Core Attributes per Item

● Standards call for 153 core attributes for each item

● EAN.UCC Business Message Standards Version 1.3, published in July 2003

● Implemented by UCCnet (2.2+), Transora and WWRE (Q2 2004)

● Roughly 50 of the 153 attributes are mandatory● 8 attributes per item go into the global registry● Core attributes do not vary across different

categories of items● Not all core attributes are relevant to each

category of items● Minimal normalization of attribute values

TRADE ITEM

Identification & Classification (GTIN, description, classification, alternate item etc.)

Hierarchy (each, case, pallet, quantity per etc.)

Physical & Logistics (measurements, handling, hazardous/safety info (incomplete), packaging, temperature for storage & shipping, etc.)

Ordering (country of origin, tax rate & amount, lead time, min/max/multiple quantity, start/end availability date etc.)

Misc.(start/end availability date, consumer avail-ability date, canceled date, discontinued date etc.)


4-26

Basic Item Synchronization

● Base item data flows largely from manufacturer to retailer● On average 10 attributes are available in ERP system● On average 15 attributes are available in other enterprise systems● On average fewer than 30 attributes are initially populated● Data completeness and quality is a major challenge for manufacturers


4-27

Retailer GDS and MDMPIM Standard Practice Architecture


4-28

GDS and MDMPIM Solution Suite Supplier Perspective


4-29

MDMPIM Solution Approach –Functionality to Leverage for GDS

● MDMPIM has a separate GDS application that provides the following:– Support for modeling and managing complex relationships and classification schemas

for trading partners, attributes, automated processes, and messaging – Data model that manages and supports interoperability between industry-leading data

pools and registries as well as new attributes, data pools, and trading partners, as they are required

– Configurable workflows that allow modification of the out-of-the-box processes to meet specific customer needs and business environments

– Reporting capabilities for summary and detailed information to keep records of global data synchronization activities

● Contact IBM Services Team


4-30

Value Proposition for GDS

● Facilitates timely synchronization of item data between source and recipient trading partners

– Strengthens partner communication and collaboration capabilities– Reduces flow of inaccurate information to trading partners– Improves the speed and accuracy of decision making– Reduces costs by achieving operational efficiencies

● Lays the foundation for future supply chain collaboration initiatives which require that trading partners are in sync on the basic product, price, party and relationship-specific information.

● Enables faster new product introductions through the efficient and accurate transfer of information


4-31

Vendor Portal Solution – What Customers Want?

● Devise an effective way to exchange key trading partner information such as product information, POS, inventory, category performance and invoice reconciliation information

● Facilitate a single interface to provide partner-specific product information● Establish and maintain customer and trading partner loyalty

by providing personalized content● Acquire more extensive relation-specific information from suppliers


4-32

Vendor Portal Solution


4-33

MDMPIM Solution Approach – Functionality to Leverage for a Vendor Portal Solution

● Pre-built portlets– Create/Modify an item– Proposal, terms, and conditions data– Modify synchronized items– Advanced Search– Mass uploads– User-specific selections

● LDAP authentication– Ensures authorized users can access only the data they are responsible for

in MDMPIM.● MDMPIM Search and Review functionality

– Compare incoming product data against existing product data to avoid duplicate product creation.

● MDMPIM Workflow functionality – Streamline business processes and eliminate process inefficiencies. Route product information to

content owners/approvers in various departments (category management, finance, pricing, store operations, merchandising, etc.)


4-34

Vendor Portal Solution Value Proposition

● Build more effective way to exchange key trading partner information such as product, promotion, POS, inventory, category performance, and invoice reconciliation information

● Establish electronic method to exchange product information with trading partners of all sizes, removing manual, paper processes.

● Establish method of getting information from suppliers not supplied by data pools


4-35

Summary

● Now that you have completed the unit, you can:● Understand the typical use cases of PIM● Describe the pain points and process workflows of each of these use cases● Understand the role of MDMPIM in addressing the following solution use cases:

– NPI– Commerce– Print– GDS– Vendor Portal Solution



4-36



Module 5

Implementation Methodology

5-1

5-2

Learning Objectives

● Identify the key roles on MDMPIM planning● Recognize the importance of a phased approach● Understand the MDMPIM Implementation Methodology ● Recognize the importance of the MDMPIM Prescriptive Methodology● Realize the value of the MDMPIM Quality Assurance Process


5-3

MDMPIM Implementation Methodology – Benefits

● Delivery of an on-time, stable, and complete solution● Leveraging of implementation best practices● Change management● Value focused● Overall satisfaction

– Matches the expectations of the users● Phased implementation approach scope minimizing solution and delivery risks● Proven approach, world-wide

Implementation Methodology 5-3

5-4

Three Primary MDMPIM Implementation Team Roles on an Engagement

LEAD AND SENIOR TECHNICAL SPECIALISTS

(SOLUTION ARCHITECT)

PRINCIPAL AND

SOLUTION IMPLEMENTATION MANAGERS

FUNCTIONAL AND PRODUCT TEAM

Experienced MDMPIM implementer Leverages MDMPIM and industry practices to design and implement user solutions.Provides application domain expertise throughout MDMPIM solution implementations.Performs Quality Assurance reviews on solution designs and implementations to ensure alignment of business value objectives.

Ensures executive sponsorship alignment is in place with regards to scope, schedule, cost, as well as risk mitigation. Identifies and tracks project issues and risks throughout implementation to ensure delivery success.Maintains compliance with MDMPIM project methodology throughout implementation.Builds strong team relationships to achieve referenceable results.

Gathers and documents user requirements/expectations and translates into application design.Skill set includes industry specific knowledge to be leveraged during an implementation. Responsible for development of the MDMPIM solution.Supports system and user testing efforts.Supports MDMPIM deployment activities.


5-5

Phased Approach

● “Why a phased approach?”– Quick wins avoid over-engineering – Promotes gradual assimilation – Reduces risk – Dramatically faster overall implementations – Increased business benefits


5-6

Phased implementation approach scope


5-7

Overall implementation methodology approach


5-8

Plan Phase

● OBJECTIVES– Validate and re-affirm your expectations on delivery goals– Gather high level requirements and lock down scope for Phase

1– Develop a program roadmap outlining high-level scope for

future phases– Identify and mobilize Phase 1 project team– Develop and obtain a signed Phase 1 statement of work

agreement

PLANPLAN


5-9

Discovery phase

● OBJECTIVES– Provide MDMPIM demo to prospective end users to ensure

understanding of product and capabilities– Document and detail MDMPIM technical requirements– Identification and preparation of systems environment– Finalize detailed Phase 1 project plan

DISCOVERYDISCOVERY


5-10

Development phase

● OBJECTIVES– Incrementally design, build, and unit test functional

and technical requirements– Configure test and production environments– Provide user functionality reviews of unit tested

functionality to users– Establish a production migration plan to address

legacy data– Develop strategies for communication, test, and

training

DESIGNDESIGN

BUILDBUILD

DESIGNDESIGN

BUILDBUILD


5-11

Test phase

● OBJECTIVES– Migrate development environment to test environment– Execute end-to-end system testing on MDMPIM

implementation. (flow through, end-to-end testing including integration touch points)

– Provide high-level, informal training to user acceptance testers– Obtain user acceptance of MDMPIM application through user

acceptance testing– Define production cutover requirements and prepare for

deployment

TESTTEST


5-12

Deploy phase

● OBJECTIVES– Conduct end-user training– Provide seamless migration from test to production

environment– Conduct due diligence on migrated production environment

prior to go-live– You are live on MDMPIM

DEPLOYDEPLOY


5-13

Project management on-going activities

● OBJECTIVES– Provide overall project status – Track issues and action items– Maintain project timelines and

budget– Manage change– Promote MDMPIM solution and program quality assurance checks– Maintain project deliverables such as contact lists and project organization structure

DEPLOYDEPLOYTESTTEST

DESIGNDESIGN

DISCOVERYDISCOVERYPLANPLAN

BUILDBUILD

DEPLOYDEPLOYTESTTEST

DESIGNDESIGN

DISCOVERYDISCOVERYPLANPLAN

BUILDBUILD


5-14

Prescriptive Methodology

● A prescriptive methodology provides guidelines in the form of Solution Definitions and How-to Guides for implementing specific functionality for a solution.

– A Solution Definition is a functional document outlining a clear outline of a solution which addresses a specific business problem, and includes a set of specific solution components to make up that solution.

– A How-to Guide is a technical document which provides best practices, guidance, and step-by-step instructions for how to design and implement the specific solution components of a Solution Definition.

● These tools and guidelines have been put in place to minimize solution variability, and increase the predictability of solution outcomes.

● The Prescriptive methodology and the tools which support it should be leveraged throughout an engagement as guidelines for How to implement a particular solution.


5-15

Quality Assurance

● As part of the IBM MDMPIM Implementation Methodology, generally 1 - 2 Solution Quality Assurance Reviews should be executed during the implementation.

● The IBM MDMPIM methodology has 2 QA review activities which are estimated at 3-5 days pending project complexity.

– Program Quality Assurance (PQA): Experienced Principal to evaluatethe overall execution and health of the program to identify, contain, and mitigate any possible risks which could jeopardize the success of the project.

– Solution Quality Assurance (SQA): Experienced Senior Technical Specialist to evaluate the solution being developed to identify risks and opportunities for improvement in solution design and implementation approach.

● Both the PQA and SQA reviews are independent review activities that should be conducted at least once during a MDMPIM implementation. They are used to ensure high quality and value focused MDMPIM solutions are implemented fulfilling end user requirements.


5-16

Summary

● Now that you have completed the unit, you can:– Define the key roles on a MDMPIM implementation project– Understand the importance of a phased approach– Explain the MDMPIM Implementation methodology– Describe the MDMPIM Quality Assurance Processes– Discuss the importance and tools available to support the MDMPIM Prescriptive

Methodology




Module 6

Architectural Fundamentals of MDMPIM

6-1

6-2

Learning Objectives

● Identify core components of the MDMPIM architecture● Identify the core services of the MDMPIM architecture● Navigate the MDMPIM tool● Configure the settings of the MDMPIM tool● Personalize the MDMPIM tool using settings and configuring table spaces


6-3

Component Breakout

Architectural Fundamentals of MDMPIM 6-3

6-4

Layered and modularized organization


6-5

Data model differentiators

● Product information managed by MDMPIM is metadata driven– Defines data structure and models business logic and behavior

● Organizational modeling in conjunction with security model● Linkages between product information

– Category to category, category to item, item to item, restrictions to catalogs● Support for unstructured content● Attribute level granularity● Location data supports enterprise solidarity and regional uniqueness● Integrate with Web Services or native Java code

– Eclipse-based development environment supports ease of use● Regionalized and translated product information

– Strong support for multiple languages or targeted for particular markets• Supported with versioning, access control, inheritance, and workflow


6-6

Architecture and differentiators


6-7

Complementary functional architecture


6-8

MDMPIM process architecture


6-9

J2EE and MDMPIM roles and responsibilities

J2EE responsibility

Load balancing: Distribute load over multiple Web and application servers.

Failover: Avoid connection start and stop costs by one Web server or application server goes down, reroute to remaining servers, as well as maintain connection through session replication.

Connecting pooling: Reusing database connections.

Multi-threading: Provide concurrency through multi-threading.

Session management: Allow information about user to be maintained to provide authenticated and authorized access and caching of frequently accessed information.

MDMPIM responsibility

Load balancing: Distribute load over multiple Web and application servers.

Failover: Maintain very lean sessions so that if session replication, if used, does not cause large IP traffic load on the network, as well as small footprint in server memory.

Connecting pooling: Use pool at all times. Solve long running transaction problem.

Multi-threading: Additional services should be multi-threaded. J2EE services should use cached and static data safely.

Session management: Lean session memory footprint while effectively utilizing the benefits of the session cache.


6-10

Service-oriented architecture and integration

● Service-oriented architecture– Atomic services such as item update and query– Workflow integration with enterprise wide workflow– New services can be defined and published with Java APIs, Web Services, or scripting

● Ease of integration capability – Strongest across all vendors– Protocols: HTTP, HTTPS, FTP, SMTP, MQ– Formats: XML, CSV, EDI– Implementation track record

● Advanced feature set for imports and exports● New service creation a feature of Jav APIs


6-11

MDMPIM Process Architecture

● MDMPIM uses a lean RMI protocol and registry to manage the registration and administration of these services across multiple machines

● All services are multi-threaded and any combination of one or more services can be deployed on a number of machines

● Persistence is done in a relational database – State (of workflows, of product information, of scheduled jobs, and so forth) is

preserved in this database● Key design guidelines in MDMPIM for scalability:

– Services are multi-threaded and more than one instance of a service can be started on same or multiple machines

– Each task for each thread (a page hit for an application server, a scheduled job for the scheduler) is optimized for indexed database access


6-12

Scripting and the Java scripting API

● Scripting is MDMPIM’s built-in programming language

– Object oriented language, but some structured aspects

– Java-like in nature, but not Java– Context-sensitive: applies to particular

objects or functions– May include custom built functions, reports

or headers● Java scripting API

– Provides context for calling Java code– Results of Java execution returned to

MDMPIM


6-13

Supported Platforms (1 of 2)

● Open systems approach– J2EE compliant– ANSI SQL

● Client Access:– Browser: Microsoft Internet Explorer Version 6.0 SP 1 – MS Windows 2000 Professional or XP Professional

● Operating systems:– AIX 5.2 (SP O6) or AIX 5.3 (SP O2)– Solaris 9 – Red Hat Enterprise Linux AS 3.0 (update 5)– HP-UX 11i

● Application Server:● BEA WebLogic 8.1 SP2● IBM WebSphere 6.0.2● RDBMS:

– Oracle 9i EE (9.2.0.8)– IBM WebSphere Information Integrator 8.2.2


6-14

Supported Platforms (2 of 2)

Operating Systems

Databases

Application Servers

OPERATING SYSTEM VERSION # SERVICE PACK/PATCH/MAINTENANCE LEVEL

AIX 5.3 O2Solaris 9 Latest recommended patch clusterRed Hat Enterprise Linux, Advanced Server AS 3.0 Update 5HP-UX 11i Latest recommended cluster

SOFTWARE AIX VERSION LINUX VERSION SOLARIS HP-UX VERSION

IBM WebSphere Information Integrator Advanced Edition

8.2.2 8.2.2 N/A N/A

Oracle 9i Enterprise Edition 9.2.0.8 9.2.0.8 9.2.0.8 9.2.0.8

SOFTWARE AIX VERSION LINUX VERSION SOLARIS HP-UX VERSION

IBM WebSphere Application Server 6.0.2 6.0.2 N/A 6.0.2BEA WebLogic N/A 8.1 SP2 8.1 SP2 8.1 SP2


6-15

Summary

● MDMPIM is architected to execute on the IBM Vision– Best of breed platform– Most feature-rich and complete product - validated in deployments– Development environment for the delivery of applications

● Stable and scalable technology ● Unique capabilities in platform

– 18 month lead on competitors; repeated validation in sales cycles


6-16

Instructor-led Walkthrough

● MDMPIM Startup Procedure and Login● MDMPIM Navigation

– The Home Page• Left Navigation Area• Working Area• Personalizing table spaces

– Menu Toolbar• Home• Product Manager• Collaboration Manager• Data Model Manager• System Administrator• Help


6-17

Walkthrough: MDMPIM Startup Procedure and Login

● In this walkthrough, you will start up the MDMPIM Server from a standalone VMware

● The following tasks will be completed:– Start VMware Workstation– Start the virtual machine– Launch the MDMPIM image– Connect to the image from a browser:

• Open a browser and type the Web address to log in to MDMPIMhttp://www.mymdmpim.com:7507/utils/enterLogin.jsp

• Log in as an Administrator– Username: Admin– Password: trinitron– Company: Acme

● A detailed step-by-step guide can be found in the Exercise material


6-18

Walkthrough: MDMPIM Navigation

● The home page– Launched upon MDMPIM login– Home pages may be different for every customer– Use Home > My Home to return– Home page contains left pane navigation and a working area– Navigation frame may be toggled on or off

● Menu Toolbar– Drop-down menus navigate to major functional areas – Menus are secure

• Access to menus and menu items are based on security roles– Menus are modular

• Access to menus and menu items are relevant to assigned tasks


6-19

Walkthrough: Left pane and workspace areas

● Left pane navigation area:– View organizational structure– Add, cut, copy, remove, delete item from a selected catalog– Add, cut, copy, remove, delete category from a selected hierarchy– Reserve, release, and work with items in a selected collaboration area

● Working area– Creating, modifying, or authorizing:

• Entries (items or categories)• Containers (catalogs or hierarchies)• Workflows and processes• Selections• Searches• And more

– Workspace provides context for your work– Workspaces can be customized– Every workspace table can be customized, sorted– Unique, customized tools can be added


6-20

Walkthrough: The menus (1 of 2)

● Home menu– Works with personal settings, tasks, and profile. Sign out and exit.

● Product manager menu– Designed for business users– Reduces the complexity in managing content from multiple sources– Allows users the ability to provide customer-focused content

● Collaboration manager menu– Designed for business process analyst users– Process modeling, alerts, escalations, workflows and supplier enablement– Item state, approvals, collaboration areas, task lists– Imports and exports– Web Services


6-21

Walkthrough: The menus (2 of 2)

● Data model manager menu– Designed for business analyst users– Manage structure of data and models, translations, workflows– Manage security– Script functions– Schedule and automate processes

● System Administrator menu– Application support is provided using MDMPIM's system administration tools that help

monitor and measure application performance– Users can analyze system bottlenecks; monitor running processes, view audit logs,

and much more● Help Menu



6-22



Module 7

Data Objects and Content Modeling

7-1

7-2

Learning Objectives

● Understand the core objects in MDMPIM● Learn about the use of a location hierarchy● Identify the capabilities of localization in MDMPIM● Create a catalog ● Create a primary specification with attributes● Create a hierarchy● Apply hierarchies to a catalog● Add items to a catalog● Add categories to a hierarchy● Configure a catalog’s and a hierarchy’s attributes● Map hierarchies


7-3

Core Data Objects in Master Data Management for Product Information Management

The primary data elementRepresents individual products, i.e. a carton of milkItems must possess a unique primary key attribute

Field types: string, number, flag, currency, image, etc.Contain parameters, such as min and max length, mandatoryAttributes are fields that describe an object, i.e. name

Core attributes which all items in a container shareMust have a unique key fieldFunctions as a template for all entries in the container

Hierarchies are containers for categories Categories further sub-divide items Categories create hierarchy levels

Catalogs are defined by three required components:Name, primary spec, primary hierarchyAn unlimited item repository, a container for all items

Data Objects and Content Modeling 7-3

7-4

Items

● Item is the most basic object in Master Data Management for Product Information Management

– Defined by an unlimited set of attributes – An item’s core attributes are defined by the catalog’s primary spec– Items are a type of entry, catalog is its container

• Item is a subclass of the Entry class• An item can belong to any number of categories

– Secondary specs (item category specifications) can further define the list of attributes applicable to an item

● An item must possess a primary key attribute – Primary keys must be unique in the catalog


7-5

Item Attributes


7-6

Primary Spec

● Attributes are used to describe an entry – either an item or a category● Attributes provide characteristics for a particular item or category● Primary spec defines core attributes of an entry● One field must serve as the primary key in a primary spec. Each node in a

container will have a unique value as the primary key


7-7

Catalogs

● Catalogs are a type of container: catalogs contain items● Required components:

– A unique name– A primary spec– A default hierarchy– An access control group (ACG), used for catalog security

● Optional components– Secondary hierarchies– Linked catalogs

• Attributes of a single item are managed across multiple catalogs– Support for location data– Processing scripts

• Entry build, pre-processing, post-processing, post-save


7-8

Catalogs in the catalog console


7-9

Catalog details


7-10

Hierarchy

● A type of container which contains categories– Also known as a taxonomy, category tree or schema– Examples: UN/SPSC, UDEX, eCl@ss, GPC, internal, and so on– Used to organize and classify items within catalogs

● Required attributes:– A unique name – A primary specification– Type of hierarchy

● Security in the form of an access control group (ACG)● Optional attributes:

– Items on leaves only option– Processing scripts

• Entry build, pre-processing, post-processing, post-save● Hierarchies are independent objects from a catalog. One hierarchy can be

mapped from 0 to N catalogs


7-11

Hierarchy as an organization of items

● A hierarchy contains categories● Categories organize items into groups

– By an arbitrary internal classification (such as merchandising)

– By external classification schemas (UDEX, AC Nielsen, EAN.UCC, GPC bricks)

● Hierarchies are built and stored separately from items and catalogs

● Hierarchies are re-usable in multiple catalogs● Items in a single catalog can be viewed in

context of multiple hierarchies, butonly one at a time


7-12

Hierarchy Details


7-13

Category

● Categories are entries in a hierarchy● Categories organize or filter items in a catalog● Categories are nested in a tree-like structure● A category’s attributes are defined by the hierarchy’s spec

– All categories contain attributes from the hierarchy’s primary spec– Categories may contain additional attributes from a standalone spec

● Two types of secondary specs may be associated to a category– Standalone: attributes of the spec apply to the category– Item category: attributes of the spec apply to items in the category


7-14

Hierarchy mappings

● You have the ability to map categories between hierarchies. Automatically map an in-house category to a standardized category

– For example: any item added to the Merchandising internal hierarchy can be automatically mapped to a corresponding category in the UNSPSC hierarchy

● Mapping is recursive and radiates between trees– That is, an item added to a category is automatically mapped to its partner category in

another hierarchy, and so forth for all mapped hierarchies– Mappings are always uni-directional


7-15

Other data objects

● Defines attributes applicable to all items in a category

● For example: Lactose free is a relevant attribute for items in a dairy category, but not in a soda category

● Selection is a subset of categories within a catalog

● For example: all red wines sold to vendor X● Saved searches are selections

● A miniature catalog containing static data● Contains a spec, but no hierarchies● Attributes are somewhat limited in nature


7-16

Lookup tables

● Lookup tables contain static data similar to a mini, static catalog– Contain a primary spec but not secondary specs– Do not use hierarchies of any kind– Use a special type of spec: lookup table spec, which is related to

the primary spec– Are somewhat limited in the type and parameters of their attributes– Cannot be versioned manually– Do not have an attached security ACG– May be searched, edited or bulk add, like catalogs

● Lookup tables can be used as references for: – Units of measure (UOM)– Currency exchange– Countries, provinces, states, tax rates and related information– Custom replacements, such as BK for black and BL for blue

● Create and manage lookup tables similarly to standard items


7-17

Lookup table specifications

● Lookup tables and catalogs use specifications– Catalogs require a primary spec and optional secondary specs– Lookup tables use a lookup table spec only

● Lookup table specs are a type of primary spec used only for lookup tables– Primary specs can be used for catalogs or hierarchies

● Other similarities:– One attribute must be named as the key attribute– Each attribute must be of a particular type

• String, number, integer, date, image, and so on– Each attribute has optional parameters

• Default value, delimiter, minimum length, validation rule● Some differences:

– Only primary keys may be set to unique– Attributes cannot be hidden, linked or non-persistent– No multi-occurring attribute values– Relationship type is unavailable


7-18

Linking catalogs

● Allows shared attribute values to be maintained in a master catalog● Items in destination catalog are supplemented with attributes from the respective

linked item in the source● An attribute in the source primary spec has to be set as Link● Linked attribute associated to destination catalog’s key attribute ● Association made in catalog console


7-19

Location data

● Location data is used to distinguish organizational or regional information in the form of a location hierarchy

● Critical solution for companies that maintain product information specific to a location

– Examples: pricing, terms and conditions, promotions and so on● Items may be sold in different regions (or countries) but information may be

different depending upon location● Location data supports hundreds of separate locations and associated product

info● Shared information is written into a secondary spec supporting inheritance needs


7-20

Granularity

CONTAINER LEVEL

(CATALOGS AND HIERARCHIES)

ENTRY LEVEL (ITEMS AND

CATEGORIES)

ATTRIBUTE LEVEL

Versioning, rollback, comparisons between versions

Reusability of data across items or categories

Access control and views into data Control, routing, and access in workflow steps

Localization: translation and regional targeting of content

Business logic – validations, computations


7-21

User interface globalization and localization

● Master Data Management for Product Information Management offers a globalized user interface with resource bundles for translation

● There are two aspects to localization: – Localization to the tools and user interface– Localization of the attributes and their values

● The following Group 1 languages are supported:– Chinese simplified– Chinese traditional– Japanese– Korean– French– German – Italian– Spanish – Portuguese Brazilian


7-22

Summary

● Now we have examined the Master Data Management for Product Information Management data objects, including:

– Item– Attribute – Primary spec – Hierarchy– Catalog– Selections– Secondary spec– Lookup table– Location data– Localization


7-23

Exercise: Instructor-led Walkthrough

● Create a new catalog using an existing primary spec and product type hierarchy● Create a new category for the primary hierarchy● Populate the catalog with a sample item● Create a new manufacturer primary specification● Create a new manufacturer hierarchy● Create new categories in hierarchy● Associate the second hierarchy to the catalog● Appendix: Create New Catalog Elements

– Create a new primary specification– Create a new primary hierarchy



7-24



Module 8

Specifications

8-1

8-2

Learning Objectives

● Understand the differences between a primary and secondary specification, and their different usages

● Learn about category mapping capabilities● Build a secondary specification● Set the parameters for attributes in a specification● Add additional parameters to attributes in a specification● Architect the successful application of item category or standalone specifications● Apply a secondary specification to a category


8-3

Specification

● What is a Specification?● A model for how data is stored, calculated, and managed in Master Data

Management for Product Information Management● A model for data as it resides outside of Master Data Management for Product

Information Management● Flexible data templates that are used for data validation

– Can be changed on-the-fly● Can be updated and maintained by a selected group of users● Different types:

– Primary, used for containers– Secondary, used for categories and location data– Lookup, used for lookup tables– File and destination, used for imports and exports respectively– Script, used for macros and script functions

Specifications 8-3

8-4

Spec node parameters


8-5

Spec nodes sample

Specifications 8-5

8-6

Secondary specifications

● Used to describe underlying items in a category or the category itself● They may be used as item category, standalone or location data specs● How to distinguish the different types of specs:

– If it captures region-specific data, it is a location secondary spec– If it applies to items in a category, it is an item category spec– If it applies to a category, but not the items, it is a standalone spec


8-7

Item category and standalone secondary specs

● Both are types of secondary specs● Both are created in the same way, with any number of attributes● Secondary specs never use a primary key● Item category specs consist of attributes that are assigned to categories and

define the items in that category● Standalone specs consist of attributes that are assigned to the category and

define the category, but not the items within● To create a secondary spec:

– Assign a unique name to it– Add attributes to the spec and set the attribute parameters– Save the spec– Remember: new specs and attributes need to be added to attribute collections

Specifications 8-7

8-8

Facts about specifications

● Every Container class object (catalogs, hierarchies and lookup tables) requires only one primary-type spec (either primary spec or lookup)

● Secondary specs are optional, many secondary specs may be applied● Secondary specs are only attached to categories and may:

– Apply their template to all the items in the category – Apply their template just to the category itself

● Attributes used for location data are modeled as secondary specs● File and destination specs are used to model data for imports and exports


8-9

Category mapping

● Category mapping entails associating two categories together● Categories may be in a different or the same hierarchy● From the Product Manager menu, navigate as follows:

– Product Manager > Hierarchies > Hierarchy Maps > Map Hierarchies– Select From and To Hierarchies (Source and Destination)– Browse the From hierarchy and select the category (source) that needs to be mapped– A pop-up window appears with the To hierarchy– Select the destination category to which you want to map the source category– Click the Select link

● Wherever a mapping exists, a green checkmark will be displayed

Specifications 8-9

8-10

Map categories screen


8-11

Summary

● A specification is blueprint for how data is stored ● Secondary specs are used to provide additional underlying information about a

particular items ● There are two types of specifications: mapped item category specs and

standalone specs● Hierarchies and their categories are used to structure and organize items in a

catalog

Specifications 8-11

8-12


● Create a new secondary specification● Add the secondary spec to the attribute collection● Assign the secondary spec to a category● Add specs to attribute collections● Build a tabbed view● Appendix

– Creating secondary specs for use as standalone




Module 9

Attribute Collections and Views

9-1

9-2

Learning Objectives

● Understand what Attribute Collections are, their use and benefits● Apply an attribute collection to other objects● Understand what Views are, and how they are used● Switch between views in catalogs or hierarchies ● Create a dynamic or static attribute collection● Build an editable, viewable, or tabbed view


9-3

Attribute Collections – A Definition

● An attribute collection is an arbitrary group of attributes that will be associated or behave the same way in a given context

● Type of Attribute Collections:– Static Attribute Collections:

• A static collection are built up from individually selected attributes from specs• If attributes are added to a spec, a static collection does not get automatically updated

– Dynamic Attribute collections:● A dynamic collection comprise entire attribute specs

• Any object using a dynamic collection gets automatically updated if attributes are added to a spec

Attribute Collections and Views 9-3

9-4

Specs and Attribute Collections

● Specs and attribute collections are both groups of specs, but:– There are different types of specs (primary, secondary, and so on) but only one type of

attribute collection– Attribute collections can contain several specs– Specs form the template of a container and behave the same way under all

circumstances– Attribute collections are arbitrary and perform under specified contexts– Attribute collections may be static or dynamic, specs are not


9-5

Why do we use Attribute Collections?

● Once an attribute collection is created, it can be used in:– Access privileges

• Assign attribute-level security access– Views

• Determine the read and write access for attributes in a view– Tabs

• Establish tabs in views– Workflow steps

• Enable or disable attributes in a workflow– Location data

• Determine which attributes will be made available for location data


9-6

Benefits of Attribute Collections

● Efficient Data Management– With the use of attribute collections, data is modeled in a more efficient and organized

manner. – Instead of managing a large amount of attributes for an item, managing them in

subsets creates a more manageable dataset.● Easier security specification

– Specify access privileges for a group of attributes on the item and assign access to the appropriate functional role (for example: marketing Attribute Collection can be edited by users with marketing role while other users can only view marketing attributes)

● Faster mapping of business process within Master Data Management for Product Information Management

– Set up Attribute Collections as part of views, tabs and workflow steps to be worked on as a group


9-7

Views

● Views apply to a container (catalogs or hierarchies)● Catalog and hierarchy views highlight different MDMPIM objects● Views are created through container consoles● Different types of views:

– Catalogs:• Editing an item• Bulk editing items• Generating item lists• Popping up an item• Location data for items

– Hierarchies:• Editing a category• Bulk editing categories


9-8

Security and Views

● Contrary to popular belief, views are not a form of security● All views are available to all users: views cannot be restricted● Views allow users the flexibility to display their data in the most suitable and

productive way– Read, write, hidden, tabbed, or any combination

● Views apply only after security has been applied● Views display only available attributes


9-9

Catalog Views

● Catalog views allow users to personalize which item attributes are editable, read only or hidden:

– Used as a way to create a more efficient or task-specific view of items when working in a catalog

– Often used to create groups of attributes related to a specific data entry or data maintenance process

• Example: promotion-related attributes– Multiple views can be created and used with each catalog– Views are shared by all users– Catalog privileges determine which attributes a user can choose from to create a view


9-10

Hierarchy Views

● Hierarchy views are used to display categories in a hierarchy● There are two features that can be built at the time of creating a hierarchy view:

– Category edit– Bulk category edit


9-11

Tabbed Views

● Tabbed views may be created within a view● An advantage of tabbed views is that it decreases the need to scroll through a

catalog’s long list of attributes thus enhancing page rendering time and usability● Catalog or hierarchy views display all attributes and their values in one panel – a

tabbed view displays attributes in a tabular manner


9-12

Summary

At the completion of this module you should be able to:

● Discuss attribute collections – why they are created and what they are used for● Discuss views, the different types, and the function of each


9-13


● Create a new attribute collection● Create a new catalog view● Create a new hierarchy view● Update and Populate Catalog with Items

– Using Catalog to Catalog Export● Create a read-only view



9-14



Module 10

Browsing, Searching, and Selecting

10-1

10-2

Learning Objectives

● Learn about searching for data in MDMPIM● Learn about data selections● Configure parameters to perform a rich search● Create a reusable search template for use with rich searches● Layer search templates to create complex searches● Save searches as selections● Create static and dynamic selections


10-3

Methods to Browse for Items

● Tree view– Navigating items in the various levels of a classification associated to a catalog

• Any level of a classification can contain items• Each classification level graphically relates to its parent and child categories

● List view● Browsing through other hierarchies

– In the left navigation pane, choose a catalog name from the drop-down list and select ADD (the plus sign ‘+’)

• The catalog box displays with Show On-Demand Filter and Show On-Demand Search links

– Select Show On-Demand Filter and choose the category hierarchy to display• The category hierarchy will be displayed in the left navigation pane

– Expand the category hierarchy to view items• Items will be displayed on the right side of the page

Browsing, Searching, and Selecting 10-3

10-4

Browsing items in tree view


10-5

Browsing items in list view


10-6

Searching catalogs

● On-Demand Search– Expand the On-Demand Search tool in the left pane navigation– Search on a key or display attribute or both– Search for items in a catalog or categories in a hierarchy– Results are displayed in left pane navigation as hyperlinks

● Rich search– Right-click in left pane navigation and click Item Rich Search– Click Rich Search from the catalog console– Can be performed on any primary or secondary spec attribute– Can be performed on any category of any hierarchy in catalog– Can be scheduled to run in the background


10-7

Rich search options, restrictions and criteria


10-8

Search templates

● A re-usable group of attributes for performing searches● May contain attributes from primary or secondary specs● Intelligently chooses predicates based on attribute data type

– Begins with, ends with, contains for strings– Greater than, less than, equal to for numbers types– For dates, before, after, or on

● Search templates automatically added to bookmarks– Click bookmark to automatically initiate a new search with

template criteria


10-9

Building a search template

Name and describe the template

Search for specs and attributes to add to template

Specs and attributes currently in template


10-10

Creating complex, layered searches

● Search results may be displayed in single edit screen, bulk edit or automatically chosen based upon results

● Return to the rich search tab to search within search results to narrow results or to layer searches. For example:

– 10,000 items are in a catalog– Search on prices greater than $50 produces 1,000 out of 10,000– Search again on prices less than $100 produces 50 out of 1,000

● Add hierarchy and category restrictions for complex searches● Search results can be saved:

– Name the search results– Searches are saved as static or dynamic selections


10-11

Basic selections

● Selections are subsets of a catalog● Selections may be static or dynamic

– Static selections do not update when master set changes– Static selections are editable – Dynamic results updated when master set updated– Dynamic selections are not editable

● Selections are instantly accessible from the selections component in the left pane navigation

● Append an item list to a static or dynamic selection


10-12

Uses for selections

● Selections may be:– Used for export to another catalog or system– Pushed through a portlet for information sharing– Used as the feed for a workflow process– Source feed for performing a mass update– Expedite mapping to new hierarchies or categories


10-13

Dynamic selections

● To create a dynamic selection:– Save search results as a dynamic selection– Manually create a basic dynamic selection

● Manual creation of a basic dynamic selection– Product Manager > Selections > New Basic Selection– Select the catalog– Select a catalog’s hierarchy– Select the categories within the hierarchy– Categories may be recursed from parent to child– Selection may be previewed to ensure results


10-14

Summary

Now that this module is completed, you are prepared to:

● Discuss item browsing through hierarchies● Explore On-Demand Search tool● Understand the purpose and function of search predicates● Discover how to create search templates● Discover how to create complex searches by layering search results and

templates● Create static and dynamic selections● Append search results to an item selection


10-15


● Search your item catalog● Use rich search to search your catalog● Create a search template● Use a search template from the bookmarks● Create a static selection● Appendix

– Create a Dynamic selection– Bulk Edits



10-16



Module 11

Security: Organizations, Roles and Access Control Groups

11-1

11-2

Learning Objectives

● Understand organizational hierarchies● Learn about users and roles configuration● Define roles which abstract user rights and privileges● Assign security privileges to users via roles● Enable and disable users● Extend roles to access control groups● Grant permissions by mapping access control groups to objects● Tune security access to an attribute level via catalog and hierarchy access

privileges


11-3

Organization hierarchies and organizations

● An organization is a collection of users● Organizations are contained in an organization hierarchy● Organizations are modeled as categories

– The steps required to set up organizational hierarchies are very similar to how category hierarchies are created

● Organizations are supported under the same framework as hierarchies in which they are created using specs and can be viewed in the left pane

● Organization hierarchies contain organizations and category hierarchies contain categories

Example: The European region can be set up as an organization hierarchy. Countries within the European region can be set up as organizations within the European organization hierarchy. Users can be added at the country level.

Security: Organizations, Roles and Access Control Groups 11-3

11-4

Creating an organization hierarchy

● Organizational hierarchies are created in the hierarchy console● Use the same wizard to create an organization hierarchy as a category hierarchy● Multiple organization hierarchies can be created● Organizational hierarchies can have many levels of organizations● Secondary specs can be applied to organizational hierarchies


11-5

Organization and category hierarchies

ORGANIZATION HIERARCHIES

CATEGORY HIERARCHIES

A container for organizations

A container for categories

Contain and organize users Contain and organize itemsCore attributes are defined by the primary spec

Core attributes are defined by the primary spec

Secondary specs are optional

Secondary specs are optional

Are nested to many levels, completely customizable

Are nested to many levels, completely customizable

Independent of catalogs independent of catalogsMultiple organizations are supported

Multiple categories are supported


11-6

Organization hierarchies and users

● Organizations consist of groups of users● First, an organization is created followed by the

creation of a user● In order to add a user, the left navigation pane is

used ● Organizations are added to the left pane just as

hierarchies● Organization hierarchies are arbitrary and

completely customizable


11-7

Users

● Users are individuals that use and interact with MDMPIM

● Users are defined with a unique user name and password

● Users are assigned one or more roles● Users are part of an organization● Users may be enabled or disabled, but not deleted


11-8

Editing user information

● Maintain users from left pane:– Add the organization hierarchy to the

left pane– Locate user in organization– Click user to edit information

● Maintain users from user console:– Data Model Manager > Security > User

Console– Click Username to edit user– Use tools to enable or disable one or

many users


11-9

Roles

● Role is an abstract representation of a set of permissions which is shared amongst one or more users

● Privileges and permissions are assigned to roles, not users.● Permissions are never assigned to an individual, always to a role.● Two native roles are MDMPIM standard: administrator and basic● All roles are customized (such as: content reviewer, approver, catalog manager,

…)● Administrator is the only role which cannot be modified or deleted


11-10

Roles – types of access

● For each role, there are three areas of security that can be implemented:– Group access: Restrict access to the role for each associated Access Control Group– System-wide access: Restrict access to various features– Locale access: Restrict access to one or more available locales


11-11

Access control groups

● Access control groups (ACGs) combine roles to a single source in order to serve as a liaison between role permissions and MDMPIM objects.

● Roles determine the permissions, but not the objects. ACGs provide a single point of contact for roles to objects.

● Change security restrictions to an object by either:– Associating a new ACG to the object– Change the roles associated to the ACG


11-12

Security model


11-13

Roles and access control groups

● Many-to-many relationship between roles and ACGs

● Roles may have many ACGs, so each role could have many levels of permissions depending upon the ACG

– Multiple ACGs can be grouped to define a role

– Roles also define the user access to specific part of MDMPIM (such as modules, screens, operations)

– The access to different locales is also defined at role level


11-14

Access privileges

● Access privileges determine role-based access to attributes– Roles determine permissibility for functions– Access control groups map roles to MDMPIM objects– Access privileges limit security down to the attribute level

● Access privileges are granted on catalogs and hierarchies● Using attribute collections, role-based access can be granted:

– Read only– Read and write– Combinations of the above on a per attribute collection basis

● To grant access privileges:– Data Model Manager > Security > Access Privileges > New Catalog Access Privileges– Data Model Manager > Security > Access Privileges > New Hierarchy Access

Privileges


11-15

Roles and access control groups

● Create an ACG– Assign a name and description– Choose roles to include in ACG

● Map the ACG to the MDMPIM objects– Map ACG to catalogs, hierarchies, selections, workflows, collaboration areas or

docstore files.– Perform mapping when creating object– After objects have been created, change mapping by clicking Data Model Manager >

Security > Access Control Groups > Object to Access Control Group Map


11-16

Questions

1) What should be done when an employee leaves the company?2) How many roles can be assigned to a single user?3) How would you grant a manager access to view, list, and delete catalogs, but not a

developer?4) How would you prohibit guests to my catalog from seeing any data related to

price?5) Given two users with identical permissions, how would you restrict user A from

working with a workflow, but permit user B?6) A local store manager has the ability to view, list, create, modify, or delete

information from their store catalog, but not from home office’s master catalog. How can this be accomplished using a single role?


11-17

Summary

● Organizations consist of groups of users ● Roles are created to abstract user permissions● Users are assigned one or many roles● Access control groups determine which objects roles are applied to● Access privileges manage security down to an attribute level


11-18


● Create a new role● Create a new access control group● Map an object to an access control group● Set access privileges for a catalog and for hierarchies● Build a new user and assign it to the new role● Test security by accessing MDMPIM as the new user you just created and

attempt to perform various functions




Module 12

MDMPIM Workflows

12-1

12-2

Learning Objectives

● Plan a workflow as a means of capturing a business process● Create a workflow containing steps and transitions● Apply a security model to individual steps● Apply attribute-level access to individual steps● Use pre-defined steps to build a new workflow● Connect the steps of a workflow● Model a visual representation of a workflow using the workflow GUI editor● Link a workflow to an object through a collaboration area● Check items into a workflow● Process items in a workflow


12-3

Workflows

● Workflows are used to model a business process● Workflows may be nested one in another● Workflows are based upon the UML design of a finite state machine

– Every workflow has one starting point (the initial state)– Every workflow has one ending point (a final state)– There can be any number of states – or steps – between initial and final– Transitions navigate from one step to another– Steps perform pre-defined actions, or custom-built actions– Any number of items may be checked out into a workflow at one time

MDMPIM Workflows 12-3

12-4

Examples of workflow processes

● Introducing new items– Manager delegates completion of item details to users– Users individually complete details– Final details are consolidated– If approved, the new item is introduced

● Global data synchronization– Data is published to an external data pool– The data pool publishes the information on a global registry– The data pool and registry notify that the data has been accepted

● Item review and approval– An item is checked out for edit– Users perform edits and release item back into the catalog– Managers review edits, and either approve or reject them


12-5

Workflow components

● Workflow components offer a set of screens to setup task lists, status screens, and reporting functionality

● Workflows use pre-defined steps types for modification, approval and so forth● Based on the type of workflow step, it is possible to setup additional parameters

for the step, these parameters include– Roles or users who are authorized to perform the step– Set of attributes available in the step– Exit values for the step (including escalation)– E-mail notifications at the step– Timeout values for the step– Additional business logic to execute during the step (scripts)


12-6

Creating a new workflow

● Two steps to workflow creation:– Create the steps– Create the flow by linking the steps

● Creating the steps logic– New workflow wizard will automatically include an initial state and two final states

(Success and Failure)– New steps can be added using the Add step button– Update the appropriate step actions (type, users, attributes, security, business logic,

etc.,)● Creating workflow logic flow

– Link the created steps by adding the appropriate next step to the exit value– Save the workflow!– Use the workflow GUI editor to build a graphic representation

• Drop steps onto the editor and build the transitions• Workflow GUI is used to show the overall flow and another method for a user to access a step


12-7

Creating a workflow step-by-step

We will create the following New Product Introduction Process

● Department A defines the descriptions● Department B sets pricing ● The pricing must be approved:

– Manager approval required for products costing under $100– VP approval required for products costing over $100


12-8

Step 1: Launch the workflow wizard

● Data Model Menu > Workflows > Workflow Console● Select the New workflow button


12-9

Step 2: Define the workflow

● Provide a name and description for the new workflow

● Access control groups control security to a workflow

● Define the container type:

– Catalog to process items

– Hierarchy to process categories


12-10

Step details

● Types of steps– General: Modify an entry without locking it– Modify: Modify an entry by locking it first– And_Approval: Approval is required from all performers– Or_Approval: Approval is required from one of the performers– Automated: Defined by custom built script– Wait: Pause a specified time frame– etc.

● Performers are users or roles who complete the step– Select specific users, roles, or both

● Attribute collections are used to work on specific attributes– Select attribute collections for single edit, bulk edit, or item pop-up– Attribute collections can be viewable, editable, or required

● Exit values are different for each step– Some exit values can be customized


12-11

Step 3: Add steps to workflow

● Build the workflow steps as follows:

STEP NAME TYPE PERFORMERS ATTRIBUTES EXIT VALUES

Edit description General Dept A Key Marketing collection

DONE

Set price Modify Dept B Pricing collection

DONE

Route by cost Automated n/a Pricing collection

LESS_100MORE_100

Manager approval Or_Approval Manager Pricing and Key Marketing collections

APPROVEDREJECTED

VP approval Or_Approval VP Pricing and Key Marketing collections

APPROVEDREJECTED


12-12

Step 4: Sequence the steps

● Use the Add button in each row (plus symbol) to specify the next step● Save the workflow to avoid loss of work


12-13

Step 5: Adding a script to a step

● Any step may have an attached script

● Scripts attached to workflows will execute functions when:

● The step is entered● The step is exited● The step times out● The script is something which

must be customized● Scripts may be built in script

editor or script workbench


12-14

Step 6: Using the workflow GUI


12-15

Compare model and workflow GUI


12-16

Step 7: Create a collaboration area

● Workflows are re-usable for different containers● Collaboration areas link a workflow to a specific container● Collaboration areas are mini-catalogs that support regular catalog and hierarchy

functionality ● A collaboration can be temporary and deleted when empty or permanent for

common business processes● Collaboration Manager > Collaboration Areas > New Collaboration Area


12-17

Create a collaboration area


12-18

Using collaboration areas (1 of 2)

● Entries are checked out into a collaboration area● Collaboration area places the entry in its workflow’s initial state● Entries are copied into the collaboration and the source entry is locked● When an entry reaches the final state, either:

– The copy overwrites the source if it is a success state– The copy is dropped if it is a failure state

● Data may be checked out into a collaboration area by:– Clicking the Checkout button and selecting a collaboration area from an edit screen– Right-clicking the entry in the left pane navigation area, clicking Checkout and

selecting a collaboration area● Work with items in a collaboration area by:

– Opening the collaboration area console– Adding the collaboration area to the left pane navigation area– Selecting items from the workflow GUI


12-19

Using collaboration areas (2 of 2)


12-20

Editing checked out items


12-21

Summary

● Workflows are used to implement a multi-step process ● Workflows model business processes● Many pre-defined steps are available, but can be customized● Workflows require a collaboration area to be run● Entries are checked out into collaboration areas


12-22


● Complete the Workflow exercise




Module 13

Imports and Exports

13-1

13-2

Learning Objectives

● Discuss the purpose and function of imports and exports● Understand what a data source is● Learn how to perform basic imports and exports● Examine the files which an export creates● Learn how to troubleshoot import and export issues● Understand scheduling capability for imports and exports


13-3

Import overview (1 of 2)

● An import is a feed that inputs data from an external source into MDMPIM● An import is first configured manually and can then be run on a scheduled or on-

demand basis● MDMPIM allows you to import multiple types of data (items, binary files, category

trees, categorization mappings)– From multiple sources– To accomplish multiple purposes (update, replace, delete)

● Additional features:– GUI-based data mapping– Broad character set support (UTF-8)– Supports a variety of file formats

Imports and Exports 13-3

13-4

Import overview (2 of 2)


13-5

Import specifics

● There are four different data feed types: – Binary feed (such as images, .pdf, .doc, and so on)– Category tree feed– Item feed– Item to category map feed

● Three data feed semantics:– Update– Replace– Delete


13-6

Data sources

● A data source is source that is used for the import feed● Defines where and how the content will be coming in● It is a pointer to a location where the file is stored● Data source types include:

– Have MDMPIM retrieve via FTP – a server address and username and password are needed

– From the document store (including FTP) – a path needs to be specified for the document store

– Upload via Web browser● To create a data source:

– Three options• Create a new data source• Modify an existing data source• Select an existing data source


13-7

File specifications

● A file specification is used as a blueprint or schema to represent the structure of the incoming data model

● Consists of attributes and details of each attribute


13-8

File mapping

● Useful to be able to map the attributes of the incoming file to the destination attributes

● Selected attributes of the file spec are matched to existing spec attributes


13-9

Import console

● Central location for viewing all created imports ● Console from which imports are executed● Also used to check status of the feed● Provides links to open the following:

– File specification– View details for data source– Import map – Import script


13-10

Import result

● When the import has completed:– The progress bar will disappear– A summary is offered that includes details such as the number of

• Lines that were processed in the file• Items added, modified and deleted• Item to category mappings added and modified• Errors and warnings that occurred during the import


13-11

Export overview

● An export is an event that syndicates data from MDMPIM to an external destination

● An export is first configured manually and can then be run on a scheduled or on-demand basis

● Similar to imports, the MDMPIM allows for the export of multiple types of data to a variety of destination types:

– Data types: items, hierarchies– File formats: XML, CSV, tab-delimited, character-delimited, fixed width– Destinations: FTP server, e-mail attachment, HTTP post

● Use the export console to review existing exports and to create a new export


13-12

Types of mapping

● There are different types of export mappings:● Catalog specification to destination specification mapping:

– Can be shared by all the feeds that use any catalog that uses the catalog specification specified in the feed

– Many catalogs can share the same catalog specification. Therefore, it is possible to re-use this mapping with all the catalogs that use that specification

● Catalog to destination specification mapping:– This mapping is catalog-specific, that is, only one specific catalog will be able to use

this mapping– Use this type of mapping only if there is no reason to expect that the mapping can be

re-used for other exports


13-13

Running the export feed

● From the export console:● Select the export rules

– Check the box at the start of the row● Click the Go button to execute


13-14

Export result

● When the export is completed– The progress bar will disappear– A summary is offered that includes details such as

• A hyperlink to all the files that were created during the export• Errors and warnings that occurred during the import


13-15

Viewing the file (1 of 2)

● You can also view the file from MDMPIM● Select the Job Info button for the grocery export feed● Verify that the export feed completed successfully● Click catalog.out in the right most column


13-16

Viewing the file (2 of 2)

● Standard exports will produce one file entitled ‘catalog.out’● To review the file, click the ‘catalog.out’ hyperlink● The file will open up in a new browser window● You can then review the results and optionally save the file on your computer or

network● All export files are kept in the document store

– schedule_logs directory– Arranged by generated export name– Each export file is time and date stamped


13-17

Troubleshooting a job

● If an import or an export runs into problems:– Hyperlinks to errors or warnings are displayed on the job summary– Errors are critical problems that prevented the successful processing of an item– Warnings are non-critical problems that should not have prevented the successful

processing of an item● Sometimes, a job will fail to complete:

– Instead of a summary, an error will be displayed– Record the circumstances of the problem – Note the error message– Contact an import administrator or manager


13-18

Jobs console

● All imports and exports are called jobs● Every job is run on the scheduler service

– Jobs run now are, in fact, scheduled to run at current date and time– Jobs may be scheduled for other dates or times

● Click Scheduler > Jobs console to trace scheduled jobs– Search schedule status– View the status of running jobs– Add another job to the schedule– Delete a job from the schedule– Compare scheduled jobs– Follow each job to a calendar GUI to visualize scheduled jobs

● Schedules can be:– Immediate runs– One-time runs– Yearly, monthly, weekly, daily, and hourly runs


13-19

Scheduler considerations

● Several scheduler services can be running concurrently– Consider the type of job: long running, batch or quick report– Consider CPU: memory intensive or database intensive– Consider logic: complex validation rules are more intensive– Number of concurrent jobs

● Number of concurrent jobs can be customized:– Depends on number and types of jobs– Default value of 8 concurrent jobs per scheduler is fine for lightweight jobs– Best practice: Two concurrent jobs per processor on a heavily utilized system

● As with the appsvr component, the JVM’s 2 GB memory limitation will need to be considered


13-20

Document store: filesystem or database

● The document store is a repository for every incoming and outgoing file, plus more

– Import scripts, reports, and specification files– Every import file is copied and stored into the document store– Can be utilized as a backup engine or log record

● Document store structure resembles Windows Explorer● Each file in document store is a hyperlink to files on the database● Manage user files in the following manner:

– View a file’s content and details– Control access to a file– View a document’s audit log– Delete files


13-21

Summary

● Document store (docstore) is the area in MDMPIM where files that are being imported or exported are stored

● There are two types of mapping – one is specific to a particular catalog and the other is not catalog specific and multiple feeds can leverage the mapping

● Scheduler is a useful feature for scheduling jobs to run on a repetitive basis


13-22


● Create a new import job● Import from a source file into MDMPIM● Create a new export job● Export from MDMPIM to the document store ● Import a hierarchy into MDMPIM


présentation mdm pim.pdf

Documents

overview of mdmpim

mdmpim continuedrity

ete data

master data management

existing mdmpim exercises1

magenda day

business context1

business processes