The document proposes a Local Emergency Preparedness Data Stores (LEPDS) system to coordinate emergency response across various levels of government. LEPDS would integrate data from household, neighborhood, city, suburban, and rural stakeholders to prepare communities for threats and hazards. It describes key user stakeholders like emergency coordinators and controllers at the community, regional, and state levels. The proposal also outlines external systems like municipal, fire, police, and emergency management that LEPDS would integrate with and significant risks to the system's analysis, design, and ability to exchange data with external systems.

1. SE 430 A1: Product Proposal Your name: Latienda Williams
1.0 Product Name & Description
Product Name: Local Emergency Prepardness Data Stores (LEPDS)
Description: ​Emergency Response prepardness requires coordination across
multi-tiered organizations and governments.
2.0 Product Vision Statement
Target customer: For State Emergency Managment Associations (i.e. Illinois
Emergency Management Agency (IEMA)).
Need or opportunity for
customer:
Community/Local Data Stores serve as collection points in
executing responses to Emergency Prepardness.
Category of product: LEPDS is an Emergency Response System for multi-tiered
Incident Management.
Key benefit: Prepare communities for emergency response to threats and
hazards.
Competing alternative: Different from the current WebEOC system used in Illinois.1
Primary differentiation: LEPDS system provides integration for household,
neighborhood, city, suburbs, and rural areas.
3.0 Key User Stakeholders2
Disasters have affects at different levels and at each level of managing an incident there
are community, local (regional) and state tiers involved in emergency prepardness. Below3
lists the stakeholders that are represented in the Context Diagram in Section 6.0.
1
http://www.illinois.gov/iema/documents/WebEOC_Intro.pdf
2
https://www.jointcommission.org/assets/1/18/planning_guide.pdf
3
http://report.hazelwoodinquiry.vic.gov.au/part­two­fire/preparing­fire/state­planning­fire
Page 1

2. SE 430 A1: Product Proposal Your name: Latienda Williams
User Stakeholder Name​: Community, Regional and State Tiers Emergency Response
Coordinator
User Role(s)​: Administrative Office User, System Administrator User
Expected Use(s)​: Administer Volunteer Management
User Stakeholder Name​: Community, Regional and State Controller
User Role(s)​: Administrative Office User, System Administrator User
Expected Use(s)​: Tracking costs reimbursable by FEMA, documenting disaster expenses
User Stakeholder Name​: Community, Regional and State Agency Commander
User Role(s)​: System Administrator User
Expected Use(s)​: Executive the Emergency Response Plan
User Stakeholder Name​:​​Social Group Emergency Response Coordinator
User Role(s)​: Administrative Office User
Expected Use(s)​: Create Volunteer Organizations, Create Volunteer
User Stakeholder Name​: Muncipal Coordinator
User Role(s)​: Administrative Office User, System Administrator User
Expected Use(s)​: Status reporting of Emergency Response to the Community, Regional
and State Agencies
User Stakeholder Name​: Fire Coordinator
User Role(s)​: Administrative Office User, System Administrator User
Expected Use(s)​: Execute the Emergency Response plan for Fire Services per the State
Manager
User Stakeholder Name​: Police Coordinator
User Role(s)​: Administrative Office User, System Administrator User
Expected Use(s)​: Execute the Emergency Response plan for Police Services per the State
Manager
User Stakeholder Name​: Medical Services Coordinator
User Role(s)​: Administrative Office User, System Administrator User
Expected Use(s)​: Execute the Emergency Response plan for Medical Services per the
State Manager
4.0 External Systems
Page 2

3. SE 430 A1: Product Proposal Your name: Latienda Williams
The external systems listed below each are depicted as entities on the Context Diagram in Section
6.0. An Emergency Response Team and Incident Management Process and Personnel does not
require each Stakeholder/Entity to have access to the proposed system.
External System Name/Description​: Municial Government System
Service Provided: ​Provides the data needed for reporting to regional and state agencies
Benefits​: Level of Coordination and data for the Emergency Response Plan
Analysis and Design Risks​:
1. <The Municipal Government System may change its software
architecture> which may result in <an inability for the proposed system
to connect and exchange needed information.>
External System Name/Description​: Fire Emergency System
Service Provided: ​Provides the data needed for reporting to regional and state agencies
Benefits​: Level of Coordination and data for the Emergency Response Plan
Analysis and Design Risks​:
1. <The Fire Emergency System System may change its software
architecture> which may result in <an inability for the proposed system
to connect and exchange needed information.>
External System Name/Description​: Police Emergency System
Service Provided: ​Provide assistance to the public and protect pubic and priviate
property
Benefits​: Level of Coordination and data for the Emergency Response Plan
Analysis and Design Risks​:
1. <The Police Emergency System System may change its software
architecture> which may result in <an inability for the proposed system
to connect and exchange needed information.>
External System Name/Description​: State Emergency Management Agency System
Service Provided: ​Provides the data needed for reporting to regional, state and federal
agencies
Benefits​: Level of Coordination and data for the Emergency Response Plan
Analysis and Design Risks​:
1. <The State Emergency Management Agency System may change its
software architecture> which may result in <an inability for the
proposed system to connect and exchange needed information.>
External System Name/Description​: Federal Emergency Management Agency System
Page 3

4. SE 430 A1: Product Proposal Your name: Latienda Williams
Service Provided: ​Provides the data needed for reporting to regional and state agencies
Benefits​: Level of Coordination and data for the Emergency Response Plan
Analysis and Design Risks​:
1. <The Federal Emergency Management Agency System may change its
software architecture> which may result in <an inability for the
proposed system to connect and exchange needed information.>
5.0 Significant Analysis and Design Risks
1. <A stakeholder will not be included in the design of this system> which
may result in/resulting in <incomplete requirements.>
2. <The stakeholders listed on the community, regional and state level may not
have given accurate information> which may result in/resulting in
<requirements that are not extensive enough to provde the level-of-detail
required for the system.>
3. <Selection of the architecture components of the system are not sufficent
enough to provide the expected outcome> which may result in <component
downtime and inability to complete needed tasks to prepare for an incident
reponse.>
4. <Monitor and manage social media outlets of employees, vendors and
contractors for theft of data> which may result in <loss of data by outside
attacks on the system.>
5. <Improper policies, hardware, software and procedures in place for the
equipment used in emergency response planning> which may result in
<decreased ability to meet threats to requested resources.>
6. <Proposed system neglects to consider the laws and regulations at each
level-of-government> which may result in <incorrect information, incomplete
reporting requirements and lack of data needed to management an incident
response.>
Page 4

5. SE 430 A1: Product Proposal Your name: Latienda Williams
7. <Insecure control systems implemented> which may result in <the lack of the
information needed for administering the response to the incident.>
8. <External Systems are not authorized to administer protected data in
accordance with local, state, and federal entities> which may result in <a data
breach, fines and penalties, identify theft, damage to repution, loss of grant
funding and incomplete assessments of the resources needed.>
9. <External system component failure> which may result in <inability of the
needed system to complete business processes.>
10. <System Administrator users for the external systems may have limited and/or
incomplete training to properly manage a Incident> which may result in
<incomplete data reporting, inadequate resources and delay in response of
appropriate team member.>
11. <The Municipal Government System may change its software architecture>
which may result in <an inability for the proposed system to connect and
exchange needed information.>
12. <The Fire Emergency System System may change its software architecture>
which may result in <an inability for the proposed system to connect and
exchange needed information.>
13. <The Police Emergency System System may change its software
architecture> which may result in <an inability for the proposed system to
connect and exchange needed information.>
14. <The State Emergency Management Agency System may change its software
architecture> which may result in <an inability for the proposed system to
connect and exchange needed information.>
15. <The Federal Emergency Management Agency System may change its
software architecture> which may result in <an inability for the proposed
system to connect and exchange needed information.>
Page 5

6. SE 430 A1: Product Proposal Your name: Latienda Williams
6.0 Product Context Diagram4
4
Aydinoglu
Page 6

7. SE 430 A1: Product Proposal Your name: Latienda Williams
7.0 References (optional)
1. https://training.fema.gov/emiweb/downloads/hdr/session%204%20powerpoi
nt.pdf
2. https://www.fema.gov/media­library­data/20130726­1813­25045­0649/whole_
community_dec2011__2_.pdf
3. http://www.rand.org/content/dam/rand/pubs/occasional_papers/2008/RAND
_OP234.pdf
4. http://www­01.ibm.com/common/ssi/cgi­bin/ssialias?subtype=BR&infotype=
PM&htmlfid=PUB03004USEN&attachment=PUB03004USEN.PDF
5. http://doc.utwente.nl/78516/1/ADSZ­AGMJ.df
6. Aydinoglu, Arif Cagdas, Tashsin Tomarlioglu et.al. Modeling Emergency
Management Data by UML as an Extension of a Geographic Data Sharing
Model: ASAT Approach, Proceedings of the TIEMS Conference 2009
Annual Conference. pge 1­12.
7. https://www.jointcommission.org/assets/1/18/planning_guide.pdf
8. Introduction to Emergency Management By Michael K. Lindell, Ph.D., Carla
Prater, Ronald W. Perry, Ph.D.
9. http://report.hazelwoodinquiry.vic.gov.au/part­two­fire/preparing­fire/state­
planning­fire
Page 7