|
The original Call For Participation for this TC may be found at http://lists.oasis-open.org/archives/tc-announce/200301/msg00000.html
The charter for this TC was last modified on 11 January 2005 as minuted at http://lists.oasis-open.org/archives/emergency/200501/msg00055.html.
The charter for this TC is as follows.
Name
OASIS Emergency Management Technical Committee
The TC may constitute subcommittees or other groupings as necessary and appropriate to carrying out the TC's purpose.
Statement of Purpose
Across the nation, government agencies, non-governmental organizations and private sector emergency management offices use a wide array of software platforms for managing data about emergency conditions, resources and response activities. Most of these are stand-alone systems with limited capability for data sharing with other agencies or other levels of government.
Advances in information technology have paralleled the movement toward more integrated approaches to emergency management. In particular, the emergence of service-oriented architectures has created new opportunities for interoperability among diverse emergency information systems utilizing existing industry-standard technologies. At the same time, other data communication facilities, such as digital television and radio broadcasting, are being brought to bear on the challenges of emergency information exchange.
Application of these technologies to the emergency management domain requires the design and refinement of new standards for data structures and message-exchange processes. The purpose of this Technical Committee is to design, develop, and release XML-based standards that provide a framework for interoperability among diverse emergency information systems.
Scope of Work
The Technical Committee will apply itself to answering requirements for data exchange among emergency management, public safety, homeland security and related applications and systems. Examples of data-sharing applications within the Technical Committee's scope include:
- Alerting, warning and informing responders and the public
- Incident reporting and tracking
- Resource identification, tasking and tracking
- Geospatial characterization and tracking of hazards and resources
- Planning, modeling
- Financial management of emergency response activities
- Hazard monitoring and data acquisition systems
- Training of emergency responders and managers
- Staff, personnel and organizational management
- Other activities identified within the Department of Homeland Security's "National Incident Management System" (NIMS)
Within this general scope the activities of this Technical Committee may include, but are not limited to:
- Dialog and collaboration with emergency management stakeholders and agencies and other standards activities in the identification and articulation of user requirements, of operational practices and constraints, and of existing art that may be adopted;
- Technical development, refinement and formalization of standards documents to specify data elements, document and message schemas, web service definitions, profiles and any other specifications that may facilitate useful data exchange among data systems for emergency management, public safety, homeland security and allied agencies and organizations;
- Participation in and evaluation of interoperability trials and demonstrations, independently or in concert with other organizations or agencies;
- Development and publication of supplemental materials that may further the adoption or implementation of standards created by or recommended by the Technical Committee; and,
- Collaboration with other OASIS Technical Committees and other standards groups in the development and deployment of standards it deems valuable to emergency management users.
The Technical Committee does NOT anticipate offering compliance certification, product testing or product rating services. However, the Technical Committee may collaborate with other organizations that offer such services on an equitable and nondiscriminatory basis.
List of Deliverables
This revision of the Technical Committee Charter covers the period from its adoption by the Technical Committee and through calendar year 2005. During that period the following milestones are projected:
1st Quarter 2005
- Negotiate and document agreements for stakeholder involvement and requirements development with agencies such as the U.S. Department of Homeland Security and stakeholder organizations such as the Emergency Interoperability Consortium;
- Establish liaison agreements with related standards processes including, but not limited to, the Global Justice XML Data Model program, the IEEE 1512 project and the International Health Consortium TC;
- Complete Technical Committee approval of an update ("version 1.1") of the Common Alerting Protocol standard and submit it for OASIS adoption;
- Develop a prioritized list of specific additional standards projects, based on stakeholder and Technical Committee member inputs;
- Adopt a set of operational and technical goals, requirements and constraints for at least one new standard; and,
- Review and evaluate any work contributed by Technical Committee members.
2nd Quarter 2005
- Complete Technical Committee development, testing and adoption of at least one new technical standard based on identified requirements and/or contributed work and submit it for OASIS adoption;
- Adopt a set of operational and technical goals, requirements and constraints for at least one additional new standard;
- Review and evaluate any work contributed by Technical Committee members.
3rd Quarter 2005
- Complete Technical Committee development of at least one additional new technical standard and submit it for OASIS adoption; and,
- Adopt a set of operational and technical goals, requirements and constraints for at least one additional new standard; and,
- Review and evaluate any work contributed by Technical Committee members.
4th Quarter 2005
- Complete Technical Committee development of at least one additional new technical standard and submit it for OASIS adoption.
Within the general scope described above, the Technical Committee may revise this schedule of milestones as circumstances warrant.
Audience and Users
The users of systems enabled by the work of this Technical Committee will be categorized by the following roles:
- policy makers and preparedness planners,
- system designers and implementers, and
- emergency end-users.
Role 1: Policy makers and preparedness planners include emergency management system policy makers and emergency preparation personnel. These users include, but are not limited to, offices of emergency preparedness and homeland security and departments of emergency management at all jurisdictional levels.
Role 2: System designers and implementers include, but is not limited to, technical and modeling developers of emergency management systems specifically dealing with information and communication exchange.
Role 3: Emergency end-users include individuals and organizations responding to or affected by an emergency situation. These users include, but are not limited to, the global community of emergency first responders, emergency managers, humanitarian and security workers and government agencies that support responders in emergency situations. These users may also include all the people and infrastructure systems affected by an emergency situation.
The immediate audience for technical standards developed by the Emergency Management Technical Committee will be the implementers of emergency information and communication systems included in Role 2. The audience for supplemental publications and activities by the Technical Community will include all three roles.
Language
The Emergency Management Technical Committee will conduct its business in the English language. Subcommittee work, consultations and liaisons may be conducted in other languages as necessary, particularly where multi-lingual capability or internationalization are involved to meet user requirements.
|
