To implement means to prototype with new and unknown technologies until they are functionally useful according to a design specification where they can then be incrementally introduced into the real-world.
With a signed off master plan to build the next great thing, the fun really begins. Blueprints become real creations that can ‘wow’ end users.
Implementation of new and complex IoT concepts should be viewed as an R&D effort in the first attempts, until it becomes a scientific process and perhaps someday an art .Concepts may vary from simple new interactive UI, automated controller, remote monitoring or fully integrated digital twins, the implementation can may concern entirely bespoke or off the shelf solutions.
Regardless of how the technology is built the challenge comes from the digital and cultural changes of implementing concepts into new environments with users who may begin to work and live in entirely different ways.
THE RESULT: Implementation is the realisation of a concept and architecture design that can be tested and measured to ensure proper functionality and usability creating value for it’s users.
Who to involve?
At this phase in a project it’s a blend of engineer meetings, internal testing and progress reports to clients and stakeholders. As with any agile iterative approach, the best way is open communications getting feedback as soon as possible.
The development process must be clear up front, bugs and blemishes are natural and any early beta testing must be taken with a grain of salt.
- Project Manager
- Senior Developers
- Software Architects
- Client leads
- Important stakeholders who understand the development process
The tools for development and implementation are endless. Whether it’s the software development life cycles, electronic production processes or general business project life cycles, there’s a lot out there.
We will be sharing case studies in the future, with some of the typical software and project management tools we have found great in our projects.
Why implement and prototype?
By creating a prototype of the solution, a team can easily determine the aspects and features worth keeping and which should need more attention. The lean attitude uncovers bugs and unwanted user desire early on that aren’t easily noticed on paper. A prototype allows a design team to evaluate and test the product before its full production, thus lowering the production costs.