Changes between Version 26 and Version 27 of BluePrintRegionsAndIncidents

Timestamp:

04/10/11 21:24:25 (14 years ago)

Author:

Pat Tressel

Comment:

--

BluePrintRegionsAndIncidents

@@ -14 +14 @@
 An "incident" is a more fine-grained concept, involving not just location but also time and assigned personnel and resources.  Don Cameron points out the importance of being able to specify an incident and identify what's associated with it, in order to implement an ICS (incident command system).
 
-Incidents can overlap in time, region, personnel, and resources.
+Incidents can overlap in time, region, personnel, and resources, thus the means we adopt of associating resources with incidents should not in general force a resource to be exclusively tied to one incident.
+
+Please note: This is not a general discussion of incidents nor of an incident command system. Rather, it is about how to accommodate multiple incidents active at the same time in one server. 
 
 ==== Common features ====
@@ -20 +22 @@
 Regions and incidents touch on each other in several ways:
 
+For both, we will very likely want to support multiple instances in the same server, and same database.
+How we handle multiple regions may provide some hints on how to handle for multiple incidents.
+
 The user will want a way to select which they're working on at the moment.
 
-The definition of a region or incident should be shared among (appropriate) users.  That is, a site admin should be able to configure a region or incident.
+The definition of a region or incident should be shared among (appropriate) users.  An authorized person should be able to configure a region or incident.
 
 An incident will probably need a region as part of its specification.