Print

 

For softwaremakers the pressure is always on, and to be able to make software for a complicated application is always hard. But if you start out with a solid base and make sure to use terms that the end user are familiar with, the job gets a lot easier, as you do not have to educate your target group.

For a while I have been using part of the PackML standard ISA-tr88.00.02. I was convinced that it was the new thing, as my colleuages also used it, so the excuse was to use it, so it would be easier for the end user.

The issue
But as I was writing complex software for applications operated by non educated personal, it became a big struggle to succeed with the PackML Statemachine. Simply, to many things(conditions) could go wrong, and it became difficult to explain all the certain scenarios to the end user.

In the end I felt it was time to simplify things.

The PackML Concept with the modules, modes and states is all in all not bad, and makes a lot of scense for programmers. There just is a whole lot of layers that in general not really is needed to have a good stable base for your modules.

The solution
So with that in mind, I took a look at what needed to be done to kind of simplify the statemachine from PackML.

 

 

The solution is as shown in the video above, a more simple and slightly redesigned statemachine

 

The highlights are: