L I C E N S I N G
Project Management in CodeMeter License Portal
Anyone who has ever built a house knows that a construction site involves many different roles , and the success of the project depends on the seamless interaction between them . The architect designs the project , the workers on-site implement it , and the logistics coordinator ensures that the necessary materials are available .
Software projects delivered to plants and factories have a comparable level of complexity . A project planner creates an overview of which licenses are needed and how they should be distributed within the facility . The purchaser procures the licenses , and the on-site employee activates them . The more precisely the project planner specifies the distribution of the licenses , the more efficiently the activation is carried out on-site .
This is where the project management function in CodeMeter License Portal comes into play . The project planner organizes the project and assigns the licenses to the devices . An on-site employee then simply imports the preconfigured license packages . This saves time , prevents errors in the field , and reduces the need for employee training .
Different Roles In this use case , we consider three roles : the purchaser who procures the licenses , the project planner who assigns the licenses , and the on-site employee who activates the licenses . In the terminology of CodeMeter License Portal , the purchaser and the project planner are group administrators , while the on-site employee is a group user . Administrators can assign licenses to groups and projects . Users can activate and deactivate licenses . Groups can represent either real or virtual entities in which licenses are organized , such as departments , teams , or virtual license pools like a purchasing pool .
Procurement of Licenses The workflow typically begins with the procurement of licenses . In most cases , the system integrator purchases a larger quantity of licenses through a volume contract . These licenses are generated by the software manufacturer upon order and delivered to CodeMeter License Portal . The delivery is made to a group , such as the purchasing pool . Typically , purchasers and project planners are administrators of the purchasing pool . They can withdraw licenses from this virtual inventory and distribute them to other groups or projects .
Project Preparation A project planner from the system integrator selects a group and then creates a project in the next step . Within this project , the project planner defines the individual devices . From
CodeMeter ’ s perspective , each device receives exactly one CmContainer , where the licenses will later be activated and securely stored . When a device is defined , a virtual CmContainer is automatically created .
An exception to this single-container approach applies when licenses from different software vendors need to be activated on the same device and involve machine-bound CmActLicenses . This use case is not covered here .
After defining the devices , additional users can be assigned to the project . These users can be given either the role of Project User or Project Administrator . Users who are already administrators of the group in which the project was created automatically inherit the administrator role for the project . However , group users must be explicitly assigned to the project . This allows for granular control over project access .
Once the project is created , it is automatically set to the status “ In Progress ”.
Assignment of Licenses To assign licenses to a project , the logged-in
8