A visual diagram to express the intent of the Prototype using symbols and a short story to indicate the

• functionality
• communication strategy
• security
• technology
• data storage strategy
• user interfaces
• device interfaces

The diagram has the advantage of simplifying the message to the different type of readers, novices thru experts, operators thru CEO’s.

My symbol set and examples are modest, i wish to improve my abilities so suggestions are welcome, link

A good team will have a number of distinct roles, if there is only one person, they will need to be good at talking to themselves.

• coder, a key role with the most hours per week and the most stress. The person needs to be able to read code as well a write code. Reading code is important to understand the examples that will be provided, writing code is required to implement the changes for the teams objectives. Intermediate experience with Java or C# language is preferred, it will be enough to follow along, undertake homework and ask good questions.
• value hunter, a key role required to identify where is the value that this prototype is trying to capture. The person will have some Lean Engineering/Improvement experience. They will be able to identify waste or opportunity, understand metrics to measure and value the waste and communicate the benefits of capturing this value to the team and the business.
• leader, a key role to decide who, when and what is to be done or not done.
• subject matter expert (SME), a key role to ensure the user stories to be created are informed. Examples of the contribution they will make are
• 1) the SME is going to identify an even simpler/better solution than the prototype so the team can STOP.
• 2) The SME is going to insist that more function is required to ensure the prototype is a minimum viable product (MVP).

A guide and discussion about Industry 4 Prototyping can get wide and deep quickly. This is a map of topics to cover to ensure I layout my thoughts so you might follow and engage as you see fit.

• the team
• the infrastructure chart
• the cloud and its contents
• the edge and its contents
• messages
• iot devices
• smart devices
• apps
• user interfaces
• development software
• examples, tips and tricks

There are no signposts in the sea. -Vita Sackville-West

Lean Engineering has a responsibility to assist the willing. In that spirit, I am undertaking this blog for something I am passionate about, Industry 4.0 Prototyping. Prototyping will improve a business’s understanding of Industry 4.0 principles and the management of risk by having

• demonstrated capture of value,
• user stories are robust and are not “gold plated”
• valid data sets
• users ready to participate

The immediate purpose of this blog is to share how to reduce the formidable barriers to Industry 4.0 prototyping so teams can start or continue where they may otherwise stop. I welcome any contribution you may choose to make to what are my thoughts as I am no prophet/guru and expect to learn from the contribution’s others may make.

Good company in a journey makes the way seem shorter. – Izaak Walton