AS-IS process to be improved in a new TO-BE process with
the support of the knowledge that each organization can provide,
the TO-BE processes need the data that sensors provide
to keep running the process, the sensor strategy defines the
sensor ontology that incorporates the definition of the sensors
and the relationships between each another, as well as their
implementations. Once the collaboration operation starts in
the tactical and operative levels, the process is monitored taking
into account the KPIs defined in previous phases, so that
the contract is confirmed as being fulfilled, and in the technological
level the sensors that have been installed generate
a behaviour pattern that triggers the process operations that
generate data and Information. This collaborative process
operation generates knowledge that is shared among enterprises.
In the evolution phase, the performance assessment is
executed, if the results are in accordance with the objectives,
the process continues in a normal way. If not, the joint business
and sensor strategies have to be double-checked and the
contract will be modified as well as the processes and behaviour
patterns. This phase generates the knowledge extraction.
The contract has to have a clause that indicates the moment
or situation that triggers its completion. When this happens,
the CN in its continuous learning process produces learning
lessons that have to be stored as well as the sensors used in
order to re-use them in subsequent CNs, generating continuous
knowledge.
Validation
In order to implement the FISEA in a business environment,
the instantiation of its elements has to be complete. Those
elements in modelling language are called building blocks,
and Table 3 describes each building block and how has it to
be instantiated, as well as the modelling view and the life
cycle phases that it belongs to.