Hide If | |||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||
|
Show If | ||
---|---|---|
| ||
Product Lifecycle Management STATE MODELProduct Lifecycle Management (PLM) is responsible for managing the entire lifecycle of the catalog element and its underlying components. This include all of the processes required to design, build, deploy, maintain and ultimately retire the catalog element. |
...
Product Lifecycle Management (PLM) is responsible for managing the entire lifecycle of the catalog element and its underlying components. This include all of the processes required to design, build, deploy, maintain and ultimately retire the catalog element.
When the macro conception of a catalog element is started the first status of the later is "In Study".
When the conception of the catalog element is accepted its status is changed to "In Design".
If the design is approved its status is changed to "In Test".
Then either the test is OK and then its status is changed to "Active" or the test is KO and its status is changed to "Rejected". The Rejected status is a final status.
When a catalog element is in an "Active" status it means it has been validated and tested, but it is still not available for customers.
When the beginning of marketing is reached, its status is changed to "Launched". At this moment customers can buy it.
If the catalog element is not launched, its status is changed to "Retired".
The same status is achieved when a catalog element reaches the end of marketing.
The "Retired" status means it can not be sold to any new customers, but previous customers can still have it.
When no
more customer holds the catalog element, its status is changed to "Obsolete" meaning it can be removed from the catalog. |
...
Catalog RESOURCEThe root |
...
The root
entity for catalog management.
|
Field Descriptions :
|
...
Category RESOURCEThe category resource is used to group product offerings, service and resource candidates in logical containers. Categories can contain other categories and/or product offerings, resource or service candidates.
|
...
...
Product Offering RESOURCEThe Product Offering resource represents entities that are orderable from the provider of the catalog, this resource includes pricing information.
|
...
|
...
_Toc362514682 Anchor
|
...
...
Product Specification RESOURCEThe ProductSpecification Resource is a detailed description of a tangible or intangible object made available externally in the form of a ProductOffering to customers or other parties playing a party role.
|
Field | Description |
configurable | If true, the Boolean indicates that the productSpecCharacteristic is configurable |
description | A narrative that explains in detail what the productSpecCharacteristic is |
name | Name of the productSpecCharacteristic |
valueType | A kind of value that the characteristic can take on, such as numeric, text and so forth |
validFor | The period for which the productSpecCharacteristic is valid |
...
Field | Description |
default | Indicates if the value is the default value for a characteristic |
unitOfMeasure | Could be minutes, GB… |
validFor | The period of time for which a value is applicable |
value | A discrete value that the characteristic can take on |
valueFrom | The low range value that a characteristic can take on |
valueTo | The upper range value that a characteristic can take on |
valueType | A kind of value that the characteristic can take on, such as numeric, text, and so forth |
...
Field | Description |
href | Reference of the productSpecification |
validFor | The period for which the productSpecificationRelationship is valid |
type | Type of relationship such as migration, substitution, dependency, exclusivity |
id | Unique identifier of the productSpecification |
...
Field | Description |
id | Unique identifier of related party |
href | Reference of the relatedParty, could be a party reference or a partyRole reference |
name | Name of the related party |
role | Role of the related party |
validFor | The period for which the related party is linked to the entity |
...
Field | Description |
href | Reference of the resource specification |
id | Unique identifier of the resource specification |
name | Name of the requiredResourceSpecification |
version | Resource specification version |
...
Field | Description |
href | Reference of the serviceSpecification |
id | Unique identifier of the service specification |
name | Name of the requiredServiceSpecification |
version | Service specification version |
...
An ExportJob resource represents a TASK used to export resources to a File
The ExportJob resource supports the following properties:
...
Attribute name
...
Description
...
query
...
Used to scope the exported data (identical to GET filter construct using target ID as base)
"query": "type=productOffering&version=2.0"
...
path
...
URL of the root resource acting as the source for streaming content to the file specified by the ExportJob
../partyManagement/individual
...
content-type
...
The format of the exported data .By default "application/json"
...
status
...
notstarted, running, succeeded, failed
...
url
URL of the File containing the data to be exported
a file URL, which is of the form
...
completionDate
...
Date at which the Job was completed.
...
creationDate
...
Date at which the Job was created.
...
errorLog
...
Reason for Failure
...
{ |
UML Model:
...
An ImportJob resource represent a TASK used to import resources from a File
The ImportJob resource supports the following properties:
...
Attribute name
...
Description
...
content-type
...
The format of the imported data. By default "application/json"
...
path
...
URL of the root resource where the content of the file specified by the ImportJob must be applied
../partyManagement/individual
...
status
...
notstarted, running, succeeded, failed
...
url
URL of the File containing the data to be imported
a file URL, which is of the form
...
completionDate
...
Date at which the Job was completed.
...
creationDate
...
Date at which the Job was created.
...
errorLog
...
Reason for Failure if status is failed
...
{ |
UML Model:
...
Two notification event types are defined:
- CatalogChangeNotification
- CatalogChangeBatchNotification
Catalog Notification UML Diagram:
Catalog change notification: notifies that a catalog has been updated.
{ |
Catalog change batch notification: notifies in detail all catalog updates.
{ "version": "2.0", "name": "Colour", |
Export and Import Job Notifications
- Export Job Completion Notification
- Import Job Completion Notification
...
{ |
Event: ImportJobCompletionNotification
...
time *3). Certain characteristics, such as color, may be configured during the ordering or some other process.
Export Job ResourceAn ExportJob resource represents a TASK used to export resources to a File
UML Model: Import Job ResourceAn ImportJob resource represent a TASK used to import resources from a File
|
|
...
|
...
...
...
|
...
UML Model: |
© TM Forum 2015. All Rights Reserved
.