This is one of the possible Use Cases.
A user wishes to access information relevant to a planned operation, including data and services that enable assessment of the environment in which the operation is to take place. The user wishes to monitor a dynamic situation and adapt to changing conditions as an operation unfolds.
Proposed to the First F2F WG meeting as Use Case MITRE-2, by DeborahNichols. This case is instantiated as a mission use case for convoy operations, developed by the MITRE Sponsored Research project, Towards a Standard Rule Language for Semantic Enterprise Integration.
The use case was first described by Suzette Stoutenburg at the W3C Workshop on Rule Languages for Interoperability in April 2005 http://www.w3.org/2004/12/rules-ws/.
3. Benefits of Interchange
Benefit 1: Ability to utilize data from multiple sources.
Benefit 2: Ability to import situation-assessment rules from multiple sources.
4. Requirements on the RIF
Requirement 1. RIF should be able to reference ontologies in which rule content is defined.
Requirement 2. RIF should include representation for logical information encoded in ontologies from which rule content is derived; e.g., cardinality constraints, existential quantification, equivalent classes, disjointness, classical negation.
Requirement 3. RIF should provide representation for closed-world assumption with some situation-assessment rules.
Requirement 4. RIF should support the ability to manage rule sets dynamically under changing conditions.
Requirement 5. RIF should include representation for uncertainty.
Requirement 6. RIF should provide for identifying a query language appropriate to the rule(s) type.
... more to be added
5.1. Actors and their Goals
End-User: The end-user wants information, including data represented in reports and expertise represented in rules, to enable her to conduct an operation safely in a potentially hostile environment.
Data Provider: The data providers want their information to be distributed and utilized in a timely, accurate, and useful manner.
Mid-level Management: Mid-level management wants to apply lessons learned and distribute new operating procedures to enable end-users to respond adaptably and flexibly to changing situations.
Upper Management: Upper management wants to track the big picture and ensure that goals are achieved while organizational policies are followed.
5.2. Main Sequence
Step 1. Upper management establishes and publishes organizational policies.
Step 2. Data Providers collect data from multiple sources, including human observation, data bases, and automated sensors/monitors, and publish information using a common or interchangeable format.
Step 3. Mid-level Management publishes operating procedures embodying background knowledge and lessons learned, in some machine-processible form of rules that can be exchanged via RIF.
Step 4. End-User collects information prior to a planned operation. Parameters of the planned operation (e.g., route) are included in a query to a system that provides intelligence from multiple sources. The relevant intelligence is assessed, and a representation of the situation is created. Rules that represent safety considerations and recommendations are fired to generate situation assessments, alerts, and recommendations.
Step 5. Situation assessment is dynamically updated as new data or rules are received.
5.3. Alternate Sequences
Describe possible variations of the main sequence in separate subsections, assigning a title to each.
5.3.1. (Title of Alternate Sequence)
Describe the alternate sequence, referring to the steps in the main sequence above if convenient (to avoid repetition).
6.1. Rule-Guided Convoy Operations: Situation Assessment and Adaptation
A supply convoy commander (End-User) wishes to access battlespace information relevant to the next trip. The convoy information is entered into the local system and transmitted to the command and control (C2) center (Management). The C2 system creates a "safety zone" around the convoy, with parameters according to Standard Operating Procedures (SOPs), and logs the route critical points. The system assembles relevant data about threats in the area; sources include Ground Moving Target Indicators (GMTIs), data bases, and human intelligence summaries (Intsums) (Data Providers). With the situation picture established, the system evaluates rules that embody SOPs and situation assessment.
Results in the form of Alerts or other Messages (including Recommendations, e.g., advise following alternate route) are pushed out to the convoy commander, who may decide to make adaptive changes to the operation (e.g., changing route). There may be additional resources -- e.g., an unmanned aerial vehicle (UAV) or security forces -- available for the convoy commander to call in to investigate data that is potentially a threat. Changes to plan or requests for additional resources are updated to the situation.
The MITRE-2 use case scenario, while designed for military convoy operations, can be extended to aid situation awareness and adaptability of non-governmental organizations (NGOs) and other civilian operations in areas threatened by hostilities or natural disasters. At a more general level, the use case is applicable to situation monitoring and assessment for ongoing or emergency operations, wherever data and operating procedures are available in a shared or interchangeable format.