1. Scope

1.1. Identification

This Architecture Design document (version 2.10.0) describes the proposed high-level design of the Distributed Incident Management System (DIMS) architecture. Its purpose is to provide the reader with an overview of the major system components of the former Public Regional Information Security Event Management (PRISEM) system, the Operational Security Trust (Ops-Trust) portal system (now Trident), and the components of the DIMS dashboard front-end and data processing back end that integrate these two existing systems.

DIMS is funded by the Department of Homeland Security under contract HSHQDC- 13-C-B0013. For more information, see the documents DIMS Operational Concept Description v 2.9.0, DIMS System Requirements v 2.9.0, and other documents referenced in Section Referenced documents.

The scope of this document is limited to description of the architectural elements, data types (and their sources, volumes, and retention periods), data flows, user interfaces, etc. It is assumed the reader is familiar with the underlying motivations for the system as described in the DIMS Operational Concept Description v 2.9.0 and DIMS System Requirements v 2.9.0 documents.

Attention

This document was originally written in the months after the initial start of period of performance of the DIMS project contract, which was September 13, 2013. Things have changed over the Base Period, Option Period, and two extensions. This, and all related DIMS documents, were originally written as forward-looking documents using future tense. This, and all related project documents, are undergoing updates to reflect changes that have occured (including switching to past tense and renaming as necessary) on a best-effort basis. Keep this in mind while reading this document, and feel free to report any errors you encounter by filing a bug report or issuing a pull request.

1.2. Document overview

The structure of this document has been adapted principally from MIL-STD-498 (see Section Referenced documents). Following this section are:

• Section Referenced documents lists related documents.
• Section System-wide design decisions describes the system-wide decisions that guide the design of the Distributed Incident Management System.
• Section DIMS architectural design describes the DIMS architectural design.
• Section DIMS detailed design provides details on the hardware and software subsystem design.
• Section Requirements traceability describes traceability back to requirements expressed in the DIMS System Requirements v 2.9.0 document.
• Section Notes provides an alphabetical listing of acronyms and abbreviations used in this document.
• Section License includes the copyright and software license under which DIMS is being released.