The Enterprise PIM (Product Information Management) Model
The Enterprise PIM Model
Enterprise PIM is not just a data repository. It is tools and processes that enable the management of product information spanning all portals and channels across the enterprise. It is an end-to-end process divided into 3 segments.
1. Data Acquisition
Supplier connectivity is important to ensure top quality data from the beginning. PIM reaches out to these partners and ensures collaborated efforts from both organization and supplier. All parties on both sides of the vendor channel will be motivated to participate as they enjoy the simplified and accelerated process of catalog exchange through tools and portals enabled by PIM.
2. Data Management
All data about products must be stored and maintained centrally and an enterprise team should be assigned to keep this repository in top shape. This repository will be flexible enough to support all types of data and meet the most complex data environments and rigorous requirements. All other downstream consumers of product information will benefit as a result including customers.
3. Data Re-purpose
Re-purpose is the appropriate term because regardless of the use it all originates from one location. Product data can be used internally for reporting, BI, customer care, or externally for e-commerce, print catalogs and flyers, e-catalogs, data pools, online malls, and more. Each use case requires specific data linked to products and it is up to PIM to maintain all elements in order to coordinate and accurately express this data while maintaining only one up-to-date instance of record.
Each stage is equally critical to achieve complete data maturity.
As more internal departments and external customers are linked through a PIM platform, value realized will increase exponentially. Ultimately, all customers, partners, and staff will benefit from the PIM solution.

There is a new whitepaper called "PIM 360". It tells more about the 360 degree view of product data. It seams the promised further chapters
Reply to this