| |
* Requirement: 3.3.1 # 1
1. Power Users shall be able to start an Incident Action Plan (IAP). |
| |
|
|
|
|
| |
* Requirement: 3.3.1 # 1
2. Power Users shall be able to close an Incident Action Plan (IAP). |
| |
|
|
|
|
| |
* Requirement: 3.3.1 # 1
3. Power Users shall be able to delete an Incident Action Plan (IAP). |
| |
|
|
|
|
| |
* Requirement: 3.3.1 # 2
4. ORMS shall automatically initialize section/role specific pages within the IAP such as,
Report,s Access, Days/Shifts, Sites/Locations, Resource Planning (Requests, Acquisitions, Allocations), Teams, Rosters, Special Equipment, Lodging, Bed Assignments, Arrangements (Meal, Fuel, Laundry, Restroom, Transportation and Dashboards |
| |
|
|
|
|
| |
* Requirement: 3.3.2 # 1 - IAP > Access
5. Power Users or Incident Commander shall be able to grant relevant access to the IAP by adding or removing users to relevant IAP specific ICS roles such as Incident Commander, System Crew Tracker, Regional Crew Tracker, Logistics Lodging and Logistics Staging. |
| |
|
|
|
|
| |
* Requirement: 3.3.3 # 1 - IAP > Days
6. System Crew Tracker or Regional Crew Tracker shall be able to plan day for responding to the emergency. |
| |
|
|
|
|
| |
* Requirement: 3.3.3 # 1 - IAP > Days
7. System Crew Tracker or Regional Crew Tracker shall be able to update day for responding to the emergency. |
| |
|
|
|
|
| |
* Requirement: 3.3.3 # 1 - IAP > Days
8. System Crew Tracker or Regional Crew Tracker shall be able to delete days for responding to the emergency. |
| |
|
|
|
|
| |
Requirement: 3.3.4 # 1 - IAP > Sites
9. User with Logistics Staging access Director shall be able to Activate sites for responding to emergency. |
| |
|
|
|
|
| |
* Requirement: 3.3.4 # 1 - IAP > Sites
10. User with Logistics Staging access Director shall be able to de-activate sites for responding to emergency. |
| |
|
|
|
|
Loading...
