OASIS Emergency Management Adoption Technical Committee

The original Call For Participation for this TC may be found at http://lists.oasis-open.org/archives/tc-announce/200904/msg00001.html

  1. Name:

    OASIS Emergency Management Adoption Technical Committee

  2. Statement of Purpose:

    The OASIS Emergency Management Adoption TC members will collaborate to provide expertise and resources to educate the marketplace on the value of the Emergency Management OASIS Standards. By raising awareness of the benefits offered by OASIS Emergency Management Standards (CAP and EDXL), the Emergency Management Adoption TC expects to increase the demand for, and availability of, CAP and EDXL conforming products and services, resulting in a greater choice of tools and platforms and an expanded community of EM standards users, suppliers, and consultants.

    Since EM adoption is strong in the US and growing in the rest of the world, especially the European Union, the Technical Committee will actively solicit participation from non-US members and help to facilitate providing information promoting CAP and EDXL adoption globally.

    The Emergency Management Adoption TC intends to appoint an individual who is an active, voting member of this TC to serve as a liaison to the OASIS Emergency Management TC, to actively communicate the work of the Emergency Management Adoption TC, and to request the assistance of the Emergency Management TC on technical issues concerning specifications. Through the liaison, the Emergency Management Adoption TC is encouraged to bring issues to the Emergency Management TC concerning user needs in improving specifications. The Emergency Management TC is encouraged to bring issues to the Emergency Management Adoption TC concerning the use cases or user scenarios around proposed changes and enhancements to the specification, as well as suggestions for other adoption-related work.

    By advancing the adoption of CAP and EDXL, and other OASIS Emergency Management specifications, the Emergency Management Adoption TC will:

    • Collaborate within the security of the OASIS open process
    • Maximize message credibility by working on behalf of a vendor-neutral standards consortium
    • Build on existing market awareness of OASIS as the producer of EM standards
    • Leverage the combined resources of all participants
    • Reinforce the benefits of adopting CAP, EDXL, and any other OASIS EM specification, as they are the result of an open, transparent process guided by multiple vendors, communities, and individuals
    • Openly share content and coordinate program execution with other entities that share a common or similar statement of purpose on a worldwide scope
    • Actively solicit participation from members outside North America and help to facilitate the provision of information promoting CAP, EDXL, and any other OASIS EM specification adoption globally
  3. Scope of Work:

    OASIS Emergency Management Adoption Technical Committee activities may extend to any of the following activities:

    • Provide support for the OASIS Emergency Interoperability (EI) Member Section website
    • Review and ensure accuracy of CAP, EDXL and any other OASIS EM specification references in commonly used resources such as Wikipedia
    • Host educational, vendor-neutral webinars
    • Organize vendor-neutral workshops and tracks at OASIS events and other conferences
    • Produce OASIS-branded primers, white papers, and position papers, slide presentations, datasheets, and other collateral materials
    • Develop best practice guidelines
    • Establish liaisons, according to the OASIS Liaison Policy, with other organizations who may assist in building awareness of CAP, EDXL and any other OASIS EM specifications, and promoting these OASIS Standards in a variety of user communities
    • Assist in coordinating promotional efforts of members, leveraging activities wherever beneficial
    • Assist in coordinating press and analyst relations such as briefings, releases, and announcements with the support of OASIS staff and in accordance with the OASIS Media Relations Policy
    • Work with other OASIS technical committees to mutually promote related work with standards, best practices and other documentation from those TC's.
    • Encourage and coordinate volunteer efforts to translate the CAP, EDXL, and any other OASIS EM specifications and other committee documents into other languages
    • Interface with other OASIS TCs to define how CAP, EDXL, and any other OASIS EM specification can be best integrated with other standards to address specific scenarios
    • Stage interoperability and/or proof-of-concept demonstrations at industry conferences
    • Support efforts by other organizations to develop active testing and certification programs for conformance, interoperability and reliability.
    • Other projects aimed at increasing adoption as identified by Committee Members
    • Other activities that are considered appropriate to forwarding the goals of the Technical Committee.

    The OASIS Emergency Management Adoption Technical Committee will refer suggestions and requests for changes to and clarification of the CAP, EDXL, and any other OASIS EM specifications to the Emergency Management Technical Committee.

  4. List of Deliverables:
    • First best practice issued within 6 months of formation.
    • First webinar produced jointly with the Emergency Management Technical Committee and sponsored by OASIS.
    • Ongoing maintenance of the OASIS Emergency Interoperability (EI) Member Section website.
    • Additional materials supportive of the above scope.

    The OASIS Emergency Management Adoption Technical Committee is an on-going activity with no specific end date for its activities established in advance.

  5. IPR Mode:

    Royalty-Free on limited terms.

  6. Anticipated Audience/Users:

    Anyone involved in the implementation of the CAP, EDXL, and any other EM OASIS Standards in their own organizations, including government agencies, public safety organizations and associations, information-development managers, consultants supporting implementations, and vendors providing tools to support public alerts, emergency management and disaster management.

  7. Language in which the TC will conduct business:

    English.

 

TOP OF PAGE