OMS has designed an architectural model to assist in organizing the processes related to a digital product's lifecycle from initial release to subsequent updates. OMS also uses the Digital Product Lifecycle Management (DPLM) model to help us match processes with the workflow within our solution’s applications. This allows effort and teams to be narrowly focussed within specific deployment projects.
While DPLM is simply a model it does provide a starting framework which can be used to relate infrastructure and existing processes thereby allowing teams to streamline practices or identify process gaps and interfaces.
| Workflow |
Description |
OMS Product |
| Build
|
This is earliest that the product details can be finalized. During this activity product meta-data and product structures are created. Component part numbers are assigned and content can be added. These are generally built into manufacturing bills of materials (BOMs) and utilize elements developed and delivered in the engineering builds or BOMs.
|
RESCUE
|
| Configure
|
The configuration process is focused on planning inheritance and entitlement. This activity allows the full extent of the product meta-data to be populated including the relationship to other existing versions or releases of this product. Also during the activity the business rules and conditions surrounding its release are documented and configured.
|
RESCUE
|
| Entitle
|
The entitlement process includes all the steps used to create and validate the list of customers that are “entitled” to a product. These are the targets of the product delivery and usually have a set of business rules associated with qualification. The rules may be as simple as all those who purchased the previous version of the product in the past, or may need to be qualified further as those who also have a valid active maintenance contract.
By its very nature, the entitlement can only occur during the release process when product transitions to publicly available. |
RESCUE/ACROSS
|
| Deliver
|
The delivery process includes steps like notification and making the components available to the entitled parties. It also includes the customer taking receipt (i.e. downloading) or ordering physical copies and having them delivered.
|
ACROSS
|
| Install
|
The installation process may exist entirely outside the ESD system but allows us to see the validation points and any data that must be collected as part of the installation process.
|
ACROSS
|
| Control
|
The control process includes any installation or post install control mechanisms including issuing of license keys, configuration files or such. In can also be steps involved in renewing or changing licensing models, hence it can involve sales processes and ecommerce elements.
|
ACROSS/ACCESS
|
| Present1
|
The presentation process is related to displaying new product or services available for purchase. It can involve both the traditional marketing and sales models as well as ecommerce elements.
|
ACCESS
|
| Transact1
|
The transact process is actual sales and collection processes.
|
ACCESS
|
