Prototype scale

PoCs sometimes need to improvise or cut corners to fit within the prescribed time frame existing infrastructure, and cost constraints. Some features, processes, or data may need to be improvised or simulated. The solution definition should specify which corners can, or will be, cut, and which features and characteristics of the PoC must be demonstrated and proven.

The PoC may require infrastructure to be deployed. It would be cost-prohibitive to include all potential data sources for a PoC when the eventual IIoT system will collect data from hundreds of locations and thousands of devices. A few representative locations and devices, or simulated data, can be enough to demonstrate the business value. A representative demonstration of technologies under consideration and integrations must be selected. All viewpoints need to be addressed in the prototype, including their corresponding security concerns.

For some PoCs, a small-scale working model or prototype of the IIoT system can be developed. This enables the project team to simulate and evaluate the IIoT system and allows users and stakeholders to experience the capabilities at first hand. For example, in a system that will collect and process data from an aircraft engine, a physical prototype of the engine, sensors, and data collection can be modeled.