FROM PROTOTYPE TO DEPLOYMENT

Your device prototype works. What should you check before deployment?

A successful demonstration proves that a particular scenario is possible. It does not yet show how the software behaves after a power interruption, a hardware revision or a failed update. The transition to deployment should be based on operating conditions and testable acceptance criteria, not the number of finished screens.

Renau Digital

1. Define what deployment means

A supervised pilot may have different requirements from a device handed over for independent operation. Record who operates the machine, in what environment, for how long and with what service access. Address safety requirements and any applicable product conformity assessment separately.

Known prototype limitations are inputs to the development plan, not something to hide. Identify manual steps, test data, shortcuts and tasks that still require a developer to be present.

2. Verify the software on target hardware

Results from a development board do not replace tests on the target device. Check the electronics revision, peripherals, interfaces and system configuration. A different sensor or communication interface may require software changes and repeat testing.

  • A list of supported hardware revisions and configurations.
  • A reproducible way to build, install and start the software.
  • Tests covering real inputs, outputs and operating conditions, not just a simulated screen.

3. Define startup, interruption and recovery

For each important process, decide what should happen after a restart, missing sensor input, lost communication or a cancelled operation. Automatic resumption is not always appropriate: conditions may need to be checked or an operator may need to intervene.

The HMI should display state confirmed by the device logic rather than treating a button press as proof that a command has been completed. Conditions for allowing operation must be established for the particular machine; the interface does not replace required safeguards.

4. Plan servicing and updates

Before handover, define how to identify the software version, access diagnostics and reproduce a reported issue. Logs should support investigation, with their scope, retention and access agreed for the project.

Test interrupted updates and configuration compatibility with new versions. Rollback or recovery needs to be designed and verified; do not assume the platform provides it automatically. Service access should be agreed and limited to the permissions actually needed.

5. Accept the result against tests

Prepare acceptance scenarios with expected outcomes, software versions and hardware configurations. After a change, repeat tests for functions that could be affected. Record which deviations are acceptable for a pilot and which block further deployment.

  • Can someone start the device from the documentation without help from the code's author?
  • Have the agreed power-loss and communication-loss scenarios been tested?
  • Is there a defined way to diagnose faults and restore operation?
  • Who is responsible for updates, servicing and future releases?

Have a demonstrator that needs further development? Tell us about its limitations and intended use. We can discuss the work needed before deployment.

Let's talk about your project

This website uses cookies and similar technologies to analyse traffic and protect the contact form from spam.

For more information, see our Privacy Policy.