Use Case 5: Information Repository Processes New Data Use Case Description: An Information Repository receives new or updated data and responds by sending the data to any Central Application, External Application, or other Information Repository which may be linked to or using said data from the Information Repository. Preconditions: The Information Repository is able to receive data updates (from Sensors, Actuators, Field Applications, Central Applications, External Applications, and other Information Repositories). A valid relationship has been established between an Information Repository and any actor which is attempting to write new data to or update existing data in the Information Repository. A valid relationship has been established between an Information Repository and any actor which is interested in/subscribed to specific data within the Information Repository. Minimal Guarantees: An Information Repository will not accept data from an unauthorized source (Actor). Data which has been written to or updated in an Information Repository will not be altered by the Information Repository. Success Guarantees: Whenever an Information Repository receives authorized data writes or updates, all interested/subscribed Central Applications, External Applications, or other Information Repositories will be notified. An Information Repository will provide information, such as time and/or quality, about the validity of the data being provided to Central Applications, External Applications, or other Information Repositories. Trigger: This use case is triggered whenever data is received by an Information Repository (from Sensors, Actuators, Applications, Central Applications, External Applications, and other Information Repositories). Diagram: Use Case 5 Information Repository Processes New Data – Main Success Scenario: 1: An Information Repository receives new data from a Sensor, Actuator, Field Application, Central Application, External Application, or other Information Repository. The Information Repository then records the data within its associated storage mechanism. 2: The Information Repository determines if there are any Central Applications that are interested in the data. This may be via a pre-existing publish/subscribe mechanism between the Information Repository and Central Application(s).
Use Case 5: Information Repository Processes New Data Use Case Description: An Information Repository receives new or updated data and responds by sending the data to any Central Application, External Application, or other Information Repository which may be linked to or using said data from the Information Repository. Preconditions: The Information Repository is able to receive data updates (from Sensors, Actuators, Field Applications, Central Applications, External Applications, and other Information Repositories). A valid relationship has been established between an Information Repository and any actor which is attempting to write new data to or update existing data in the Information Repository. A valid relationship has been established between an Information Repository and any actor which is interested in/subscribed to specific data within the Information Repository. Minimal Guarantees: An Information Repository will not accept data from an unauthorized source (Actor). Data which has been written to or updated in an Information Repository will not be altered by the Information Repository. Success Guarantees: Whenever an Information Repository receives authorized data writes or updates, all interested/subscribed Central Applications, External Applications, or other Information Repositories will be notified. An Information Repository will provide information, such as time and/or quality, about the validity of the data being provided to Central Applications, External Applications, or other Information Repositories. Trigger: This use case is triggered whenever data is received by an Information Repository (from Sensors, Actuators, Applications, Central Applications, External Applications, and other Information Repositories). Diagram: Use Case 5 – Information Repository Processes New Data Main Success Scenario: 1: An Information Repository receives new data from a Sensor, Actuator, Field Application, Central Application, External Application, or other Information Repository. The Information Repository then records the data within its associated storage mechanism. 2: The Information Repository determines if there are any Central Applications that are interested in the data. This may be via a pre-existing publish/subscribe mechanism between the Information Repository and Central Application(s).
DM%20Security%20Profile%20-%20v1_0%20-%2020120220.docx