Happy almost New Year! I hope you’re ready to take on 2018 and all it has to offer – including Oracle’s new EDMCS offering for master data management.

You can look forward to a series of posts comparing and contrasting different tools available for managing your master data / metadata and documenting new features and functionality as they come out. Today’s post is going to be on just the basics of EDMCS: What is it? What does it cost? And, what are its integration options?

EDMCS Basics / Initial Functionality

EDMCS is Oracle’s Master Data Management solution in the Oracle Cloud. It’s a Software-as-a-Service (SaaS) product, like many of their other EPM cloud offerings (FCCS, PBCS, EPBCS, ARCS, etc.). The basis of master data management is to manage any reporting structures, hierarchies, reference data, mappings, metadata, attributes, etc. that could have many usage-points in your organizational systems; and keep things in sync and manageable for administrators of those systems.

From an overall functionality standpoint, EDMCS has a very different data model than DRM (which will be covered in another post) but the gist is that there are numerous “viewpoints” to which the data stewards can view only the nodes/hierarchies that will be sent to an application. Think of each viewpoint as a customized hierarchy view based on the the downstream application; DRM does this differently, as we usually create custom membership properties to filter out nodes by specific criteria from the total hierarchy view. EDMCS allows administrators to visualize their hierarchy view EXACTLY as it will appear in their application.

EDMCS also does auditing/tracking of changes, has the rails for a future governance feature (it does not have initial DRG workflow type functionality at initial release), and a robust security model that can easily limit users to specific data sets and activities. More information on the governance component will be covered in a later post.

Also important to note, is that all “property definitions” and validations that are typically created to support node attributes are going to be very simple in EDMCS at its release. All values will be “defined” values by a data steward, and validations will be limited to a few OOTB to support downstream EPM applications.

DRM has robust capabilities to allow property definitions and validations to be inherited, derived, calculated, defined as lists, defaults, etc. which make it a very powerful tool to ensure quality master data and easier maintenance for users. It will likely take years for EDMCS to catch up to this functionality.

EDMCS Licensing Considerations – What We Know Now

Although EDMCS is available for purchase through your Oracle rep (although as of today 12.28.17 it still has a “coming soon” sticker on its Oracle Cloud product page), we know that EDMCS licensing will be slightly different from Oracle’s other cloud offerings. Typically, with other EPM Cloud offerings, you’d buy a number of user licenses at a determined fee-per-user. EDMCS, however, is similar to DRM in its licensing considerations – by record.

A “record” in both DRM and EDMCS is defined as a unique node; which may have multiple usages in multiple viewpoints or hierarchies.  For licensing, a standard cost-per-record is used, and users can be added to the application, as needed (no limit). I think the current rate for each record, at this moment, can be estimated around $1.50/record.

EDMCS Integration Options – Initial Release

In the future, EDMCS will have OOTB adapters that are available to integrate seamlessly to other Oracle EPM products. PBCS will have an adapter with the initial release, and adapters are being developed for both EPBCS and FCCS, and several other EPM applications.

Other than the adapters, EDMCS also has integration capabilities via a flat-file export; and I expect this will be the main mode of integration for the foreseeable future. I would not be surprised if direct interface table-integration would also eventually become available (like DRM).

It is important to note that EDMCS will leverage Oracle’s EPM Automate utility that is used for other Oracle EPM Cloud applications; which means that EDMCS will be able to leverage the REST API, and will likely allow for custom integration options to other cloud applications.

Until then, importing and exporting data from an EDMCS pod will be managed from EPM Automate; and will require a “jumpbox” to manage these scripts for integration. Check out the available EPM Automate commands for EDMCS (and the other Cloud EPM apps) in my post here.

View after logging in to EDMCS for a “Service Administrator” role:
Screen Shot 2017-12-28 at 1.54.38 PM.png