Competent, Quality Consulting and Solutions.

About PARTS

PARTS IEPD                  Project Sponsor                  Mandates & Directives                  About Paragon


Resource Management is a critical part of any emergency response scenario. Being prepared for an emergency situation by knowing the resources you have prior to an incident is equally important to the timely identification, location, and dispatch of a resource during an emergency situation.  Per National Incident Management System (NIMS) guidelines and in accordance with appropriate Incident Command Systems, an automated identification, tracking and management system for Resource Tracking and Management can serve as a central nexus bridging emergency incident resource actions across incident management chains and organizations effectively.

This system (PARTS) has been engineered from the ground up incorporating the direct feedback of industry practitioners to allow it to meet the mission-critical needs of emergency managers in both preparing for and responding to emergency scenarios across a diverse range of localities and conditions.

Management of personnel, facilities, equipment, supplies, and other resources is a critical part of NIMS and has been thoroughly defined by the associated organizations. However, through the utilization of PARTS and the direct feedback of responders using the systems real lessons have been learned that allow new best practices to be layered atop the existing NIMS framework. By gaining this real world application experience, PARTS allows governing bodies to expand upon the standards already present. As PARTS matures, so too does NIMS.


PARTS is compreshensive and uniquely designed to optimize resources across organization and geographies.  A comprehensive data blueprint that models categorizing resources by size, capacity, capability, skill, and other characteristics enabling better and more efficient resource ordering and dispatch processes within jurisdictions, across jurisdictions, and between governmental and nongovernmental entities.

PARTS is a simple and effective web based application that is compatible with existing software via adapters customized to the host application. The IEPD (see below) defines a standard for messaging which maps critical fields to each other across platforms and thus functions as a universal exchange model.


For screen shots of the PARTS application see the Library section of this site.

       __________________________________________________________________________


PARTS IEPD
The PARTS exchange model covers several subject areas and has been tested by way of the pilot application program (PPaP). Local front line business units and emergency responders were instrumental in the validation of requirements and the continued evolution of the model by way of this pilot application now referred to as PARTS.

The PARTS IEPD was developed in cooperation with stakeholders at multiple levels of government. The messages supported in EDXL-RM are enhanced by the PARTS IEPD allowing for the facilitation of additional information exchange such as contacts, organizations, and resource typing information. The PARTS-IEPD utilizes resource class to represent resource type information graduating from EDXL-RM's use of a value list.


The PARTS IEPD messages are designed as payloads of Emergency Data Exchange Language Distribution Element (EDXL-DE) routed messages. EDXL-DE contains message routing information and is the envelope for PARTS IEPD messages. Using EDXL-DE is not mandatory however, and the PARTS IEPD can be used under any message exchange framework.


For preparedness functionality, PARTS provides resource inventory maintenance, organization and contact update ability, as well as resource typing information exchange between users.


       __________________________________________________________________________


Sponsor

PARTS was originally sponsored in 2007 by the United States government as a means to mature the standards for emergency information exchange used in the field by front line personnel and emergency managers.

The initial design, development and pilot phase were accomplish through a collaborative engagement between Federal, State, Local and Tribal bodies, including the Department of Homeland Security.


       __________________________________________________________________________


Mandates & Directives

The National Incident Management System (NIMS) was created through the Homeland Security Presidential Directive (HSPD) - 5, Management of Domestic Incidents, as put forth by President George W. Bush in February of 2003. HSPD-5 directed the Secretary of Homeland Security to develop and administer a system by which federal agencies could coordinate individual domestic incident management and emergency prevention, preparedness, response, recovery, and mitigation programs and activities. The directive further required federal departments to make adoption of NIMS including NIMS training and compliance, mandatory for state, tribal, and local organizations as pre-condition for federal preparedness assistance.

The Department of Homeland Security released NIMS in March of 2004. This original version was updated in December 2008 when FEMA, after consultation with over 100 representatives from various government agencies and organizations, released a revised version designed to clarify the original NIMS foundation concepts, while offering refined strategies for preparedness activities. Beyond this, recent large-scale emergency scenarios, including Hurricane Katrina in 2005, and the Oil Spill off the Louisiana Coast in 2010, have propelled emergency preparedness, particularly resource typing elements, onto center stage as a priority for all levels of government in order to ensure timely responses and accurate communication when mitigating emergency situations. This focus will likely result in greater emphasis on these underlying concepts and a continued effort to maintain a system of high utility that serves responders across all government sectors and arenas. The early feedback from initial PARTS users will prove invaluable in developing these enhanced methodologies procedures and systems going forward.


       __________________________________________________________________________


About Paragon

Paragon Technology Group was founded in 1997 and is headquartered in Vienna, VA just outside of Washington DC. Paragon has a distinguished history of supporting various public and private sector entities and has a core business focus centered directly on Information Technology Program Support Services. For more information about Paragon Technology Group please refer to the corporate website located at www.paragontech.net.