This is part two in a seven part series from our ePaper - 6 Critical Steps to Adding Mobility to your Control System
Similar to other solution challenges, the important first step for adding mobility to a control system is to clearly define the problem you are trying to solve. The objective of this step is start with the end in mind. Defining the comprehensive, measurable problem statement sets the foundation for discussion among the key stakeholders about how the problem can be solved and what the characteristics of and effective solution are.
Specificity in the problem definition is this is a key objective in the problem definition stage. You want to be specific about the exact characteristics that make up a great solution, along with the metrics that will be used to measure the success of the solution. Whether the the success metrics consist of business objectives, additional functionality, cost savings, or even additional revenues - it is important that the results can be measured and compared to the defined success objectives.
During the problem definition and desired outcome definition stage it's very likely that problem discussions among stakeholders will lead to proposed solutions and subsequently define the boundaries of the project. If this thought progression doesn't occur organically, then the team should explore boundaries that could include technology, delivery timeframe, cost, and resource availability available to arrive at a successful solution.
While defining the problem may seem like an unnecessary step in arriving at a solution the fact is defining the problem enables teams to share a common understanding of both the challenges and the required components that will ultimately define the project success.
Check back later today for Part 3 – Step2 – Identify Use Case. To get your copy of “6 Critical Steps to Adding Mobility to your Control System” now, Click Here!
