Proof of Concept
What does the POC consist of?
The POC (Proof of Concept) serves to better understand the benefits that TRAMA can bring and to give the client a better understanding of how it works. It consists of four phases:- Phase 1 – Information gathering.
- Phase 2 – Generation of training content.
- Phase 3 – Use period: training, broadcasting, skill management, etc.
- Phase 4 – Conclusions and evaluation of the proof of concept.
These phases, although they may undergo some modifications if deemed necessary, are usually executed as follows:
TRAMA POC work plan
| POC Stages | ||||
|---|---|---|---|---|
Phase 1 – Gathering information and designing the data structure |
||||
| Visit to the workstation (or similar) chosen to carry out the POC. Collecting documents, defining the data organization structure, taking 360º photos (if applicable) for data contextualization and defining the protocol to access the platform and to manage broadcasts. | ||||
Phase 2 – Content validation |
||||
| Validation of the training contents and the data organization structure during a face-to-face session (whenever possible) with the person(s) in charge assigned by the client. | ||||
Phase 3 – Training |
||||
| Training day(s) with the operators who have been selected to be part of the POC. Test use of the courses created with these operators. Test use of the broadcasting system and the methodology defined for its use with a control instruction. Survey to evaluate the platform for the participants of the day. | ||||
Phase 4 – Conclusions |
||||
| Presentation of conclusions and evaluation of the proof of concept. In case of success, definition of next steps for the rollout. | ||||
Start up
Rollout – Implementation process after the proof of concept.
After a successful proof of concept, proceed to the rollout phase, which consists of the following phases:Phase 1 – Deployment
A client-specific instance of TRAMA is deployed, either in the cloud or On-Premise (client’s own servers), as preferred. The deployment in the cloud is free of charge and takes less than 48 hours. On-Premise deployment will be carried out in collaboration with the client’s IT department and will involve a cost, depending on the dedication required in each specific case. It is usually ready in less than a week.Phase 2 – Connections
If there are other IT systems that manage useful information for the operation of the platform, they can be connected to TRAMA. If you want to connect TRAMA to document management systems (Microsoft Sharepoint, Google Drive, etc.) instead of using your own document repository, this will be done free of charge. If TRAMA is connected to other systems with different uses (for example, reading KPIs from these systems to automate actions or allowing these systems to access information contained in TRAMA) a connection module and its specific functionalities will be developed on demand. These connections can also be made at a later stage if you are not sure how to proceed. The full setup does not need to be done on day one.Phase 3- Content creation
The training content in TRAMA is based on the existing instructions that the client already has, so there is no need to create the material that the courses consist of. However, there are two tasks that must be carried out before starting to use the platform. First, we must define how to structure and order the information and how to connect it to the existing workstation and assets. The TRAMA team will advise the client in this process, as each client requires a different solution and making the right decision is very important to be able to use the platform comfortably in the future. Secondly, in order to evaluate the knowledge of users, questions are required about each instruction used in the courses. This process can be carried out by the client or can be outsourced to TRAMA. At least, for the first examples, we recommend outsourcing the process, in order to generate a few use cases to serve as a reference for the rest of the content.Calculadora de ahorro Savings calculator
