There are several schools of thought on methodologies to implementing a proper product MDM solution with Oracle PIM Data Hub.
I divide them into two different schools. Although both should have the same outcome, they don’t currently.
Technical waterfall style implementation projects fail or appear to be successful but are truly failures.
Business driven iterative implementation projects take longer typically but are far higher chances of success and long term benefit for organizations.
PIM initiatives are the business’s way to taking technology and making it work for them. Not the other way around. If your PIM Data Hub project starts with technical resources versus pushed from the top down as a required initiative then you are certain for failure.
How can a term defined by wikipedia as stated in a previous article show predominately managed by IT?
“processes and technologies focused on centrally managing information about products, with a focus on the data required to market and sell the products through one or more distribution channels. A central set of product data can be used to feed consistent, accurate and up-to-date information to multiple output media such as web sites, print catalogs, ERP systems, and electronic data feeds to trading partners.”
Who in your organization sets policy for your product data?
You need to answer that question honestly.
Oracle PIM Data Hub is not a development project primarily. It is a tool to satisfy a very serious business initiative.
I’ve been on some projects where business pushed it off to the IT people to implement. Bad business people!! shame on you!
I know it is overwhelming and intimidating to take on such a big project but in your own personal lives you have done more complex tasks.
You have to start controlling and governing your product data. You are somehow doing this today even if it is with multiple systems. Somewhere in the past you have given business policy to IT and told them to build a program to do that work.
You need to start the process of establishing true uniform product data. The best place to start is at the beginning of the PIM project, not at the end. If you need help, ask for it. Acting like you know what you are doing or overplanning a fairly less complicated implementation can get you into trouble or your boss into trouble.
Functional processes on an implementation are business driven, not technology driven. You should be able to identify the work that you need done technically. Any gaps in the Oracle PIM Data Hub functionality that you as a business have identified through the thorough process of knowing the functionality meets your business requirements in detail will be much more accurate than gaps that are “guessed” in advance of this effort.
Don’t leave it up to your IT staff nor contractors to decide your product data policies and processes. You need to understand them and how they will exist in the new Product Hub environment in detail yourselves. That doesn’t mean that you are learning how to write code or other technology skills.
You need to learn as a business how to configure off the shelf systems like you know how to build spreadsheets and documents. Configuration of “off the shelf” systems are not that complicated anymore. They are uniform skills and are not different across other organizations. Oracle PIM Data Hub is the same peice of software for everyone with the same set of configuration steps available to use. There are exceptions with some of the verticals but the methods are all identical and practically important to all.
A functional specification for a solution to resolving a gap in Oracle PIM Data Hub functionality written by the client with strong support for the PIM Data Hub functional experts will produce faster development and better unit testing than one written without deep basic configuration knowledge from the client themselves.
It takes at least three to four months on average for an organization to gain PIM Data Hub design knowledge in relation to their own product data for a high quality functional specification to be written by business.
Exception: If you know you are going to build interfaces, then it is possible to start solutioning a technical architecture early in the project. But the data mapping comes from the business gradually so you must plan to evolve these types of specifications.
Thanks for the reading of the article!
功能上的实现过程是业务驱动的，而不是技术驱动。你应该能够识别你需要做技术上的工作。 Oracle PIM数据平台的功能，你作为一个企业通过深入的过程中知道的功能已经确定的任何空白，满足您的业务需求的详细比的差距，“猜”在这方面的努力将更加准确。
您需要了解作为一个企业如何配置现成的系统，如你知道如何建立电子表格和文档。 “现成的”系统配置不那么复杂了。他们是一致的技能和其他组织之间是不一样的。 Oracle PIM数据平台的是一样的peice，软件的每个人都可以使用一组相同的配置步骤。有一些的垂直，但有例外，均相同，并实际上重要的所有的方法。