situation awareness in a complex world
DESCRIPTION
A research Seminar based on my doctoral workTRANSCRIPT
Research Seminar
Situation Awareness in Complex World- a knowledge management approach
By
Vikram SorathiaPostdoc Researcher
University of Twente
2
Where I am from….
Data, Information or Knowledge Management
Why• a useful input
What • By providing
– Right information
– To right person
– At right time
– In right format
How• Enabling users in
– Creating, processing, accessing information
3
Common Application Domains• Business, Administration, Production
Common Approach• Model the system
– entities, processes and activities
• Identify the information needs
• Establish information processing requirements
• Design the system
• Deploy, monitor and maintain the system
Common Approach
4
Challenging Application Domains
Emerging Application Domains• Environmental Management, Disaster Management,
• Critical Infrastructure Protection
Challenges in modeling• Model the system
– every entities, activities and processes are not known
Challenges in Information Management• For unknown system elements
– Granularity,– Observability,– Traceability,– Adaptability
5
Stakeholder Activity
6
Motivation
Observation• Systems are failing even in presence of
– Advancing Technology– Commitment in Cooperation and Sharing– Maturing Standards– Improving Know-How– Comprehensive Policies
Opportunity• Identification of the problem will
– improve effectiveness of existing outcomes
• Establishment of new strategy will– govern the future activities
7
Possible Reasons for Failure
Strategy for Agents• Adopting agent outcome: New findings, Technologies, Standards etc
• Tracking agents with negative impact: Monitoring
Goal Statements•Wild Cards in Goal Statements: “All risks”, “All users”, “All levels”
System Scope
•Limitation of Coverage: Categorical, Temporal, Spatial
Resources Capability
•Wild Cards in Capabilities: Computation, Data Storage
•Wild Card Commitments: “I will do the needful”
8
Characteristics
Implied Goal Matching ProblemAs goals only determine the content need of source and sink
Three ProblemsTransient System Element
As lifetime only determine the validity of source and sink
Event Space ProblemAs events only determine the content to be delivered
The Problem
Complex InterdependenceDynamism
9
Implied Goal Matching Example
10
For Complex Interdependence and DynamismConceptual modeling of system elementsInformation processing strategy
– Identification
– Instantiation
– Monitoring
– Evaluating
– Communicating
– Managing
For Scope of Information Management TaskTheoretical framework
– Qualitative Estimate
– Quantitative Estimate
Problem Statement
11
Research Questions
• Characterization of system• Management strategy• Characterize situation• Characterize situation awareness• Modeling strategy• Complex event processing• Requirement identification• Task identification
• Sharing of work products• Integration strategy• Separation of concern• Information requirement• Interaction patterns• Dynamic set of entities• Utilization of resource pools• Information specificity
12
Required Mediation
13
Problem in applicationQualitative estimate
- Domains, goals, complex interdependence
Quantitative estimate- No. of Situation, Update Frequency, Possible break-ups,
- No. of Utterances, Spatial, Temporal coverage
Useful theoretical work Barwise
Situations in UoD
Devlin
14
Elements of Situation
15
Modeling for Situation Awareness
1. Entity Model : for Selection Problem, Ramification Problem
6. Eventing Model : for evaluation of observed status
2. Activity/Process Model : for workflow and dependence
4. Measurement Model : for consistent assignment of values
5. Observation Model : for establishing observation requirement
3. Representation Model : for knowledge representation
7. Information Processing Model : for realization in system environment
Proposed Models
16
Information Processing Model
Proposed Strategies • Assertion Management• Information Need Determination• Information Need Specification• Messaging Pattern Generation• Assignment of Communication Roles• Representation Generation• Event Detection• Action Detection• Granularity Calculation• ETL Specification Generation• Job Specification Generation• Data Provenance Generation• DDM Task Specification Generation
17
ETL Example
18
19
Problem of Limited UtilityContribution by single individual or group
Coverage
Possible SolutionProvision for Collaboration
Identify the activity requirementsMonitor the progressDeliver the outcomeTrack the reuseUpgrade
Limitation of Isolated Contributions
20
Identifying Stakeholders
GroupingObjectives, skill-sets, activities, outcomes
Identified Stakeholder EnvironmentsNatural and Built EnvironmentReporting EnvironmentOrganization EnvironmentSystem design EnvironmentConfiguration Environment
21
Stakeholders Roles, Role-Sets
Activity Tasks, Disciplines
Outcomes Work Products, Domains
Guidance Standard Operating Procedures
Situation Awareness Unified Process (SAUP)
22
Roles with Situation Awareness Requirements
End User Role Sets
RespondentsMain Use Case: Respond to events SA Needs : Response Gaps
Entities: Resources, Services Activity: Response
Events: Availability Work Product: Status Report
Organizational Role Sets
Governmental OrganizationMain Use Case: Policy, Critical Services SA Needs: Policy Gaps
Entities: Policy, Resources, Services Activity: Provisioning
Events: Availability, Updates Work Product: Policy
23
Situation Awareness Unified Process
End User Role Sets
RespondentsMain Use Case: Respond to events SA Needs : Response Gaps
Entities: Resources, Services Activity: Response
Events: Availability Work Product: Status Report
Organizational Role Sets
Governmental OrganizationMain Use Case: Policy, Critical Services SA Needs: Policy Gaps
Entities: Policy, Resources, Services Activity: Provisioning
Events: Availability, Updates Work Product: Policy
24
The Implied Traceability
25
Proposed Configuration Environment
26
Situation Awareness Artifact
Template• Related Roles
• Responsibility
• States
• Creation Logic– How it is generated?
• Update Frequency– How often it must be refreshed?
• Visualization Strategy– How best it can be represented?
• Footprint– Impact
– Possible reuse27
Situation Awareness Architecture Framework (SAAF)
ExampleName: Information Need ETL Traceability Matrix
Traceability: Info Need ETL Job Actor: ETL Engineer
Update Frequency: Continuous Scope: Single Config.
Architectural Products• All Views
• Operation Views
• System view
• Technology view
• Situation Awareness View
28
High Level Operational Graph (dynamic)
29
The Problem of System Design
To support requirements identified for• Modeling
• Information Processing
• Process Framework
• Architectural Framework
30
Design Decisions
StrategiesKnowledge Management: Semantic Web Technology
Information Sources: Human Observations, Sensor Technology
Task Processing: Message Queue
Application Schema: GML
Distributed Computing Architecture: SOA
Virtual Organization: Grid Computing Technology
ETL : OGSA-DAI Middleware
Tool Integration Platform: Eclipse
Method Engineering : Semantic Web Technology
31
System Views
Utilization from Specific Viewpoints Middleware View: Components
Role View : Role Sets and their Information Needs
System View : Processing and Handling in Middleware
Granularity View : Information Specificity
Traceability View : Traceability Across Environments
Artifact View : Work-Product Sharing
Proof of Concept: Application Scenario
32
The Process Content
SA Configuration – Application Stack
33
Implementation ModelRealized as eclipse plug-in
Configuration InstancesConfigured, Monitored, Managed
Transient InstancesGenerated, Managed, Destroyed
Resource PoolConfigured, Utilized
Enterprise ContinuumHost all artifacts
SA Configuration – Middleware View
34
Wild Cards in PoliciesOrganizational Ontology- Domain Ontology
Silos and stove-pipesService Oriented Architecture
Separation of concern: Traceability Matrix, Method Content
SA Configuration – Role View
35
SA Configuration – System View
Wild Cards in Capabilities:ETL Specifications, Job Specifications
Wild Cards in Commitmentsis responsible for/ can help in
Delegation ModelGap Analysis, Action Detection
Data Access Strategy
36
SA Configuration – Artifact View
Alternative to Global Repository • Unified Metadata solution
• (Services, VO Resources, Data, Software Components, Ontology)37
SA Configuration – Service View
38
SA Configuration – Event View
39
78
910
11
12
1
24 5
6
3
SA Configuration – Proof of Concept
40
Definite Start and End: Determined for event
Granularity: Calculated and Delivered
Information Sources Human and Sensor
Observation – Granularity View
41
Observation – Traceability View
42
Conclusion
Data/Information/knowledge Management should• foucs on Situation Awareness of stakeholders• be carried out as a critical infrastructure service• be using appropriate configuration• be able to handle dynamic pool of stakeholders, resources and processes
that affect them
43
Future Work
Theory• Extension for concrete domains• Incorporate new design principles
Content• Domains• SAUP Method Content
System• Establish knowledge representation process• Build and improve visualization capability• Upgradation of SA System Architecture
Application• Establishment Maturity Models
44
Publications
"Data Provenance" A Chapter in Encyclopedia of Data Warehousing and Mining (Second Edition), IDEA Group, 2008, Co-authored with Anutosh Maitra."Discovering mappings between Ontologies" A Chapter in Encyclopedia of Artificial Intelligence, IDEA Group. 2008, Co-authored with Anutosh Maitra.“Building Semantic Business Services” A Chapter in a book “The Semantic Web and its Applications”, Edited by Jorge Cardoso and Amit Sheth, Springer, 2006 Co-authored with Sanjay Chaudhary and Zakir Laliwala
"Communications Middleware Requirements for Situation Awareness Systems", In the Proceedings of the (SKIMA), Nepal, 2008, Co-authored with Anutosh Maitra."Situation Awareness Unified Process", In the Proceedings of the Second International Conference on Software Engineering Advances (ICSEA 2007), France, 2007, Co-authored with Anutosh Maitra."Web Based Requirements Management Approach for Organizational Situation Awareness", In the Proceedings of the (AWSOR'07), held in conjunction with (ICWE), Italy. 2007, Co-authored with Anutosh Maitra."Integrating Stateful Services in Workflow", In the Proceedings of the 13th Asia Pacific Software Engineering Conference (APSEC06), 2006, Co-authored with Sanjay Chaudhary, Prateek Jain and Zakir Laliwala"Spatial Data Access Patterns in Semantic Grid Environment”, In the Proceedings of the (SeBGIS'06), in conjunction with (OTM'06), Montpellier, France, 2006, Co-authored with Anutosh Maitra. “Semantics and Rule Based Event-driven Services-Oriented Agricultural Recommendation System”, “Fifth International Workshop on Distributed Event-Based Systems (DEBS 2006)”, Co-authored with Sanjay Chaudhary and Zakir Laliwala"Semantics based Event-driven Publish/Subscribe Service-Oriented Architecture" In the Proceedings of SOFTPLATFORM2006", co-located with (COMSWARE)", New Delhi, 2006, Co-authored with Sanjay Chaudhary and Zakir Laliwala“Towards Agricultural Marketing Reforms: Web Services Orchestration Approach”, In the Proceedings of the IEEE International Conference on Services Computing (SCC 2005), 2005. Co-authored with Sanjay Chaudhary and Zakir Laliwala“Architecture of Sensor Based Agricultural Information System for Effective Planning of Farm Activities”, In the Proceedings of (SCC 2004), 2004, Co-authored with Sanjay Chaudhary and Zakir Laliwala
45
Key References
C. Schlogl, “Information and knowledge management: dimensions and approaches,” Information Research, vol. 10, no. 4, 2005.L. Comfort, “Information management for complex dynamic systems,” in Health Monitoring and Management of Civil Infrastructure Systems, Proceedings of SPIE Vol. 4337, S. B. Chase and A. E. Aktan, Eds. SPIE, 2001.N. Boccara, Modeling Complex Systems. Springer-Verlag New York, Inc., 2004.S. Gregor, “The nature of theory in information systems,” MIS Quarterly, vol. 30, no. 3, pp. 611–642, 2006.The Open Group, “The open group architecture framework version 8.1, enterprise edition.” The Open Group, San Fransisco, USA., Tech. Rep., 2003.P. Checkland, “Achieving ’desirable and feasible’ change: An application of soft systems methodology,” The Journal of the Operational Research, vol. 36, no. 9, pp. 821–831, 1985.M. R. Endsley, B. Bolte, and D. G. Jones, Designing for situation awareness: An approach to human-centered design. London: Taylor & Francis., 2003.H.-J. Schellnhuber and J. Kropp, “Geocybernetics: Controlling a complex dynamical system under uncertainty,” Naturwissenschaften, vol. 85, no. 9, pp. 411–425, Sept. 1998.J. Barwise and J. Perry, “Situations and attitudes,” The Journal of Philosophy, Seventy-Eighth Annual Meeting of the American Philosophical Association Eastern Division., vol. 78, no. 11, pp. 668–691, 1981.J. Barwise, The Situation in Logic. Center for the Study of Language and Information, 1989.K. Devlin, Handbook of the History of Logic, Volume 7. Elsevier, 2006, ch. Situation theory and situation semantics, pp. 601–664.E. Zalta, “Twenty-five basic theorems in situation and world theory,” Journal of Philosophical Logic, vol. 12, pp. 385–428, 1993.C. Parent, S. Spaccapietra, and E. Zimnyi, Conceptual Modeling for Traditional and Spatio-Temporal Applications: The MADS Approach. Springer-Verlag Berlin Heidelberg, 2006.E. Malinowsk and E. Zimanyi, Advanced Data Warehouse Design: From Conventional to Spatial and Temporal Applications. Springer, 2008.D. Luckham, The Power of Events: An Introduction to Complex Event Processing in Distributed Enterprise Systems. Addison-Wesley Professional, 2002.M. Turoff, M. Chumer, B. V. de Walle, and X. Yao, “The design of a dynamic emergency response management information system (dermis).” Journal of Information Technology Theory and Application, vol. 5, no. 4, p. 136, 2004. 46
Thanks !
47
48
BACKUP SLIDES
49
Possible Solutions
Establish the information need• Need of all the stakeholders
Establish the scope• Only relevant dimensions
Establish the information processing Needs• How to obtain the information
Establish system design• How to design
50
Investigate established theoriesInformation; its use, processing and handling
Indentify the theoretical extensions requiredConceptual modeling, Information System Design, Processing etc
Indentify Method and guidance requiredReference for consistent contribution from collaborators
Indentify System requiredSystem design
Demonstrate usability of approachesA case indicating the applicability
Scope of work
51
Many independent agentsPositive/negative impact
Goal directednessEvolving behaviorNo centralized controlNon linear response
System Characteristics
52
Focus of the thesis
53
Founding strategy on established theoriesDesign Principles
What is information?What is information need?How Complex Dynamical Systems can be modeled and Solved?How to improve usage?How to communicate information?How to process information?
Established Theories
54
55
Situation, its awareness
Situation– Situation is a partial representation of the world restricted
in space, time and semantic reference, communicated by a referrer with implied goal.
Situation Awareness– Actor Situation Awareness is a state achieved when actor is
provided with representation of the universe of discourse at specific space, time and conceptual granularity along with the specification of the required action, events, alerts and guidance determined suitable for carrying out the assumed role(s) in given configuration.
56
Entity Model
57
Process Model
58
Representation Model
59
Measurement Model
60
Observation Model
61
Eventing Model
62
Example of The system
63
1. Information Need Determination
64
2. Information Need Specification
•Number of Patients in Camp
–Collect from Camp Manager Every 5 min until response time
•Number of Doctors in Camp
–Collect from Camp Manager Every 3 hour until response time
•Amount of Medicine in Camp
–Collect from Camp Pharmacist Every 1 hour until response time
•Amount of Food in Camp
–Collect from Camp Pharmacist Every 6 hour until response time
•Amount of Rainfall Recorded in the Camp Area
–Collect from Camp Manager Every 2 hour until response time
•.Amount of Temperature Recorded in the Camp Area
–Collect from Camp Manager Every 2 hour until response time65
3. GML Template Generation
66
4. Messaging Pattern Creation
67
5. Data Collection Request
• To: Camp Manager
• Pattern: Request-Reply
• Message Content: GML Request
• Reply: Furnish <Template> Value from Range
68
6. Snapshot Generation
Time: te+tl• Camp #1
Property Patients : value 20
• Camp #2Property Patients : value 30
• Camp #3Property Patients : value 45
69
7. Event Detection
• Event #1If
• Patients Property is treatment status
• and value Not treated belong to Critical Range of treatment status
70
8. Action Detection
• Action determinationIf
• Current State of Entity is Not treated
• Next goal State is Treated
• Doctor is responsible for transition from Not treated to Treated
• Doctor#1 is active that can render Treatment
71
9. Action Notification
• To: Doctor#1 • Pattern: Publish-Subscribe
• Message Content: Action Request render Treatment
• Reply: Response Status
72
10. ETL Determination
73
11. Job Determination
• Time: te+tmant dataServiceClient
-Ddai.url=http://10.100.64.26:8080/wsrf/services/ogsadai/DataService -Ddai.resource.id=PostgresResourceSADBon48 -Ddai.action=sa/SAPerform/Delivery/PatientInflow#1.xml
74
12. GI Layer
Time: te+tmAdmin Block #1
• Patients : value 60
Admin Block #2
• Patients : value 90
Admin Block #3
• Patients : value 76
75
76
Journal Articles Under Preparation
“Problems and Prospects of Information Management in Complex Dynamical System "
" Situation Awareness Theory for Complex Dynamical Systems "
“Determining Information Needs in Complex Dynamical Systems”
" A Conceptual Modeling Approach for Improved Situation Awareness "
" Information Processing Algorithms for Situation Awareness "
" Distributed Data Management Algorithms for Situation Awareness "
" Situation Awareness Unified Process "
" Situation Awareness Architectural Framework”,
“A Middleware for Situation Awareness Systems”,
" A Case for Situation Awareness System for Disaster Management “
77