EMOX has a slightly different approach than other engineering companies, we focus on what the client needs and love to work side by side without letting the commercial focus getting in the way. We start out with understanding the problem that needs to be solved, not jumping straight into solutions. We are all programmed to start thinking of solutions, but if the problem is not well defined in advance then it’s highly likely that the solution is lacking, that nice to have elements are embedded or a bit of both. If a sober systems engineering approach is the driver then the problem is quickly transferred to a ConOps (concept of operation) which ensure clients that the high level needs are understood. The ConOps is then transformed into sub requirements, targeting the true needs in sufficient resolutions.
The decades of combined engineering experience in EMOX has clearly pointed out the value of a solid problem definition and how important it is to produce a specification. The process is just as important as the resource experience in a project, everyone need structure to end up with the optimal solution. Ensure all shall’s are embedded and reduce the “nice to have’s” that often get in the way of the true requirements. This is why systems engineering have high focus on the graph depicted below – the further you get the more difficult and costly the change will become. It actually takes less time to do it right from the start