Piece together metadata, enable configurations and go-live with the deployment. The deployment stage is where the project is implemented and the tasks defined in the project plan are put into action.
The steps in the deployment stage include the following:1. Gather metadata. 2. Procure hardware. 3. Allocate human resources. 4. Configure the service. 5. Build a support system. 5. Train users.
At this point, information related to the supply chain would have been gathered as a part of the study. However, detailed data per node in the supply chain will need to be gathered and this metadata can be broadly divided into the following types:
- Materials: Stock Keeping Unit (SKU) data such as name, type, nature of materials, etc. can be collected using the Material metadata collection template.
- Users: Contact data of users associated with an entity, including descriptions of their roles and reporting relationships, can be collected using the Entity and users metadata collection template, and contact data of supervisors can be collected using the Supervisors metadata collection template.
- Entities: Entity or facility data such as name, type, location, supply chain relationship with other entities, reporting hierarchies, materials managed, etc. can be collected using the Entity and users metadata collection template.
- Inventory: Inventory metadata such as min stock level, max stock level, and so on, can be collected using the Inventory metadata collection template.
- Assets: Asset or equipment data, such as type of asset, capacity, temperature range in which they are maintained, etc. can be collected using the Asset metadata collection template.
Based on the gaps identified during the infrastructure adequacy assessment, the required hardware will need to be procured. The procurement might be related to electronic hardware or SIM hardware, as listed in the Infrastructure requirements document.
A record of all the hardware that is deployed on the field should be documented along with adequate sign-offs from the responsible parties. The Hardware acknowledgement form can be used during handover of hardware.
Allocate human resources
Based on the scope, specific roles and responsibilities have to be defined before deployment. This might include a wide range of resources including entity managers, supervisory staff, training staff, support staff, deployment managers, and so on. The personnel for these functions may be available within the organization or additional workforce may be needed. The steps in the process include the following:The steps in the scoping stage include the following:
- The task and resource mapping in the project plan can be used to identify specific roles and responsibilities.
- Assessing internal human resource to understand adequacy of skills to perform these roles.
- Hiring the necessary staff, if the available resources are inadequate.
Configure LogistimoThe design and function of users in a supply chain will need to configured in the application. Different design decisions will need to be made broadly based on the following considerations:
- Supply Chain functions per echelon: The structure and functions of a domain depend on the scale and nature of operations, the modules adopted, and the type of data required at each level in the operating framework.
- Notifications: Notifications, which can be instantly enabled or disabled in real-time, allow periodic alerts, updates, or any ad-hoc communication to be sent to users.
Once the domains are created and configured, metadata collected during the planning stage will need to be updated onto Logistimo. The instructions to setup metadata on the Logistimo application can be found in Setup section of the Logistimo Knowledge Base.
The final piece before the deployment can go live is training users on using the product and following the processes.Setting up a training process includes the following steps:
- Defining a training framework which accounts for the number of trainings needed, the nature of training, curriculum, and exercises for each training.
- Setting up a training domain.
- Creating training documentation.
- Collecting training feedback.