The phases of CCU that are not covered in this article are concealed by a transparent grey rectangle.
The meta-process model (left side of the process-data diagram) is divided into several parts which are presented along with the corresponding paragraphs throughout the article to make it easier to understand.
Because the method is quite innovative a lot of the activity's are designed especially for this model and therefore the explanations do not have a source.
The manual is the document that will provide the customer with guidance in deploying and using the product.
In this situation the license agreement is a contract or a certificate which is the customers prove of its using permits.
CCU is designed to fit both situations but as bandwidth is growing it is making more sense to distribute especially updates and new versions to existing customers online.
In the process-data model it is assumed that the software vendor conducts both distribution channels.
As a practical example: HISComp, a provider of medical information systems distributes its software straightforward via CDs.
After a new package is assembled, the customer needs to be made aware of the new release.
In the process-data model this is being depicted as a loop which states advertising the update until the customers are being properly informed.
Besides this, the package ready for delivery, needs to be stored in a repository for the online distribution.
In most cases this means that a link to the product on the website of the vendor is created.
In case of offline distribution, the vendor needs to create physical transfer channels.
This can be done automatically when the current product of the customer searches for an update at the online repository.
Besides this the Customer Relationship Management (CRM) system of the vendor is updated.
By storing this in a system the vendor will be able to give the customer particular service when it needs a new product.
Another advantage of storing this information in a system is that it will ease the process of online delivery.
In this article we will discuss the function of this customer data in the CCU delivery process.
Information about the license agreement between the customer and the software vendor is stored in the CRM system.
In the meta-data model this repository and online distribution is linked to the CRM system this can again be done automatically.
The system will check if the license of a customer is sufficient to obtain a certain product or update.
In order to keep all the described systems up-to-date at the vendor site it is important that the vendor receives a lot of An example of a successful application of the CCU method can be found at Exact Software (ES).
ES is a manufacturer of accounting and enterprise resource planning software based in the Netherlands.
In the delivery phase this means that the customers are able to obtain all the products through an online connection.
So ES sells contracts (licenses) and stores them into their CRM system, the delivery of the actual products can be done by the customers themselves completely automated requiring little effort.