Emergency Planning Software

The vendor is required to provide emergency planning software (eps) solution that allows stakeholders to manage the emergency planning process and to develop and maintain functional plans in a simple, efficient, and concise manner.
• Make all public- and employee-facing digital content and services accessible by meeting industry standards.
- Implementing and maintaining a recurring, hands-on process that facilitates regular coordination and communication among stakeholders to develop, implement, train, exercise, and maintain emergency plans.
- Comprehensive, secure, cost effective, user-friendly, and forward-thinking eps for agency and our partners that need an emergency operations plan, emergency action plan, or similar plan.
- The commonwealth has outlined the following objectives desired to be considered in the implementation and operations of an eps solution:
• Security, stability, and resiliency performance expectations in a public safety environment.
• The solution shall have a simple, intuitive design that is easy to use.
• The solution should drive the development of functional emergency plans that are simple, clear, concise, and includes the ability to incorporate tools such as checklists, tear sheets, flip charts, etc.
• Scalability and flexibility to support current and future needs and to add other entities that need an emergency plan onto the solution at different timeframes.
• A solution that is accessible and useable on mobile devices.
• Efficient and flexible user registration and management.
- How long the offeror has provided this service.
- Describe any experience planning, designing, developing, implementing, and supporting one or more successful project(s) of similar size, scope, technology, and subject matter; include experience with implementing systems that are subject to state and federal performance and audit requirements.
- Please list contracts maintained during the last two (2) years that relate to the ability to perform the service(s) called for under this proposal.
- Provide details of any industry-recognized quality standard to which it is compliant (e.g. information technology infrastructure library (ITIL), iso27001, iso9000, iso9001) and any industry certifications or awards received.
- provide details of any industry experience with best practices [such as software development life cycle (SDLC)], that the offeror implemented to govern its service delivery; include any certification levels earned by the offeror or key personnel. - Enterprise License: an enterprise license or similar arrangement to allow unlimited users is desired. state agencies, county & local EMAS, dam owners, and potentially educational institutions may use the software to develop EOPS; a variety of stakeholders such a first responders, engineers, etc. will need access to established plans to support emergency operations.
- scaling: the service must be easily scalable as entities may be on boarded to the system at varying times; the service must support automatic vertical and horizontal scaling to support 90% of registered users while maintaining optimal performance.
- lead times: any lead times to increase capacities to include new users, new agencies, or new plan templates, while maintaining compliance with scaling requirements based upon the initial design approach must be defined.
- The methodology and processes for updating the solution for all types of releases, including but not limited to, software releases, commonwealth-requested enhancements, security updates, system maintenance, patches, and system enhancements.
- Ongoing software updates for the proposed solution, as they become available and are thoroughly tested; such updates may include, but are not limited to, bug fixes, patches, and other improvements.
- Describe how the updates will be tested before updating any agency environment.
- Software updates that modify features and functions shall include an update to online help, training tutorials, reference guides, and user manuals.

- Contract Period/Term: 6 months