This article is the sequel to the author ’ s former article Trustworthiness in Industrial System Design [ 1 ] which addressed trustworthiness in the design of industry IoT systems , introducing the Trustworthiness Method as an important trustworthiness implementation technique and the Trustworthiness System Status for assigning trustworthiness methods to keep the system in a specific status .
This new article extends the usage of trustworthiness from the design towards the actual operation of industry IoT systems : During the design of the system , most trustworthiness aspects are seen as “ static ”: Expectations on how the future system will behave and how trustworthiness will be considered and addressed . During the operation of the same system , trustworthiness aspects are growingly “ dynamic ”: Unexpected incidents may weaken the trustworthiness of the system and need to be instantly addressed and avoided in the future by enhancing the system .
If the reader is totally unfamiliar with the concept of trustworthiness , [ 2 ] will be great introduction .
Before looking deeper into the operational details , the Trustworthiness Method from [ 1 ] will be introduced again in the next chapter .
The first challenge of using trustworthiness in an industry IoT system is that none of the trustworthiness characteristics can be implemented as a separate technology and that the trustworthiness of the system cannot be implemented by just combining such technologies : The characteristics may support or block each other : a simple combining of trustworthiness characteristics does not lead to a real trustful system .
The solution is to take the system away from the trustworthiness characteristics and move to methods which are assigned to the specific parts of the system . In traditional systems , such methods had been used extensively but were not classified by the Trustworthiness Characteristics . And this classification can be extended by other attributes .
Definition : A Trustworthiness Method is defined as a component , tool , technology , software application , operational procedure , or a management directive which is assigned to at least one trustworthiness characteristic .
Such methods are referred to as the Trustworthiness Safety Method , Trustworthiness Resilience Method , etc . If a method is assigned to several trustworthiness characteristics , the list of characteristics is separated with a slash e . g ., Trustworthiness Security / Privacy Method .
The definition of such a method is intentionally as broad as possible as only the assignment to one or more trustworthiness characteristics is key .
Journal of Innovation 3