W3C home > Mailing lists > Public > public-disaster-management-ont@w3.org > January to February 2009

Fwd: [iaem-list] FEMA Disaster Management Stakeholder Requirements Review Period Opens; Comments Requested

From: Gavin Treadgold <gt@kestrel.co.nz>
Date: Mon, 23 Feb 2009 12:30:15 +1300
Cc: W3C Disaster Management Ontology List <public-disaster-management-ont@w3.org>
Message-Id: <A2F96C12-7C7C-4B04-B9F7-B883B15496B4@kestrel.co.nz>
To: Sahana <humanitarian-ict@yahoogroups.com>
FYI

Cheers Gav


Begin forwarded message:

> Date: 21 February 2009 10:32:58
> To: iaem-list@iaem.com
> Subject: [iaem-list] FEMA Disaster Management Stakeholder  
> Requirements Review Period Opens; Comments Requested
>
> IAEM Discussion Group:
>
> Overview:
>
> We appreciate the time it takes to review the DM Framework and DM- 
> OPEN requirements.  Your feedback and suggestions are critical to  
> the success of these systems and we pledge that we will read each  
> and every review in detail and consider all of your input as we  
> develop future plans and requirements for the DM Framework and DM- 
> OPEN systems.  These systems exist to serve the needs of the  
> emergency management community and we firmly believe that the best  
> approach to improving these systems is through soliciting your  
> comments and feedback.
>
> We have been working over the past couple of months to develop draft  
> requirements documents for the proposed replacement of the existing  
> DMIS and OPEN systems.  We developed the draft requirements  
> documents by analyzing historical feedback obtained from DMIS and  
> OPEN stakeholders, existing DMIS and OPEN functionality, and  
> requirements related to support of existing, new and emerging  
> emergency management messaging standards.  We now believe we are at  
> a point where it is critical for us to engage further with the user,  
> vendor and other stakeholder communities to review the draft  
> requirements and provide us with feedback on the documented  
> requirements and suggestions for new requirements that we have not  
> included in the draft documents.
>
> DM Framework and DM-OPEN are the names that we are using to refer to  
> our next generation systems.  We are referring to the collection of  
> documents associated with the requirements review as the   
> ”Requirements Review Package.  The Requirements Review Package  
> consists of four documents that can be downloaded from the following  
> URL:
>
> http://www.disasterhelp.gov/disastermanagement/about/about-ioc.shtm
>
> Please read the Overview document first as it explains the contents  
> of the other three documents.  The other three documents included in  
> the Requirements Review Package are:
>
> 1.     Concept of Operations (CONOPS) – Provides an understanding of  
> how these systems and your system will work together.
>
> 2.     DM Framework Full Requirements – Provides an explanation of  
> each major component followed by a table of detailed requirements  
> for each component.
>
> 3.     DM-OPEN Full Requirements - Provides an explanation of each  
> major component followed by a table of detailed requirements for  
> each component.
>
> You are free to comment on the CONOPS but we are specifically  
> looking for feedback on the two draft requirements documents.  The  
> draft requirements documents are organized by component and relate  
> specific requirements with each identified component.  Definitions  
> for component and requirement are included below to clarify the  
> exact meaning that we wish to convey.
>
> Definitions:
>
> Component – A grouping of requirements that relate to a major system  
> functional capability.
>
> Requirement – A “shall statement” that defines an aspect of the  
> component to be implemented.
>
> In order to provide some structure and guidance for providing  
> feedback we have developed a list of questions to facilitate the  
> requirements review process.  The questions are broken down into  
> three categories.  Category A deals with the identified components,  
> Category B deals with specific requirements related to additional  
> components you may identify, and Category C provides an opportunity  
> to submit comments related to any relevant topic.
>
> As you review the documents and answer the questions below please  
> provide the reasoning behind your answers.  You are free to comment  
> on any of the components and requirements, but it is not required  
> that you address each and every component and requirement.  Please  
> focus on the items that are important to you and omit comments on  
> topics that are immaterial to your interests.
>
> Questions List for Feedback Process:
>
> Category A – requirements related to identified components
>
> 1. Are there any requirements related to identified components that  
> are missing?
>
> 2. Are there any requirements identified for IOC that could be  
> deferred to post IOC?
>
> 3. Are there any identified requirements that need rewording for  
> clarification?  Please suggest the rewording for the requirement.
>
>
>
> Category B – requirements related to additional components not  
> previously identified
>
> 1. Are there additional components that need to be added to either  
> of the two systems?
>
> 2. What requirements should be associated with new components  
> identified in the previous question?
>
>
>
> Category C – General comments
>
> 1. Are there any comments about anything that you have seen in these  
> documents that you would like us to know about?
>
>
>
> How to submit feedback:
>
> Please provide all feedback in the following format:
>
> 1.     Identify which of the three documents you are providing  
> feedback on (DM Framework, DM-OPEN, CONOPS)
>
> 2.     Identify the specific component by number
>
> 3.     Identify the specific requirement by number
>
> 4.     If you are suggesting a new component and additional  
> requirement(s) make sure you indicate that they are new.
>
> 5.     Please provide details for your recommendations including the  
> rationale and importance to your needs.
>
> 6.     Feedback may be provided as text in the body of an email or  
> as an attachment to an email.
>
>
>
>  Where to submit feedback:
>
> Please submit all comments to the following email address:
>
> DMReview@eyestreet.com
>
>
>
> When to submit feedback:
>
> We would like to receive feedback by March 6, 2009.  We realize this  
> is a short timeframe and if you require more time to provide  
> feedback then please let us know by sending an email to DMReview@eyestreet.com
>
>
>
> Next steps:
>
> The schedule for implementing your new requirements currently  
> provides for an initial operating capability (IOC) release in the  
> Fall of 2009.  The current objective for IOC is to implement the  
> existing functionality in DMIS and OPEN on an enhanced platform that  
> will provide the foundation for adding new capabilities in  
> subsequent releases.  This strategy will allow us to retire the  
> existing DMIS and OPEN systems without any impact to existing or new  
> users
>
>
>
> Regards,
Received on Sunday, 22 February 2009 23:31:03 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 22 February 2009 23:31:04 GMT