Attach_7_Logical_Data_Model_and_Data_Dictionary.pdf

Logical Data Model for FRMT and RDMT

1 | P a g e

Version 1.0 4-23-2015

Interagency Resource Ordering Capability and Resource Data Management Tool (RDMT) Logical Data Model and Data Dictionary

Note: RDMT is synonymous with SDMT and FRMT is synonymous with IROC

Logical Data Model for IROC and RDMT

2 | P a g e

Revision History

Date Version /

Description Approved and Reviewed By

March 20, 2015 V 0.0: Initial Annette Box, and

Tina Vorbeck, US Forest Service

April 23, 2015 V 1.0:

Final

Annette Box and Tina Vorbeck, US Forest Service

July 2015 Submitted to NWCG Data Standards Group Lead; Awaiting Feedback

3 | P a g e

Table of Contents

Revision History Introduction Task #13: Logical Data Models

Logical Data Models with Narratives

LDM Guide and Legends

LDM Notes on Agreement vs Contract Management

LDM: Incident Management

Incident Management Narrative

LDM: Incident Management (Continued)

Incident Management (Continued) Narrative

LDM: Resource Ordering

Resource Ordering Narrative

LDM: Resource Ordering (Continued)

Resource Ordering (Continued) Narrative

LDM: Agreement Management

Resource Management Narrative

LDM: Resource Travel

Resource Travel Narrative

LDM: Resource Management

Resource Management Narrative

LDM: Resource Management (Continued)

Resource Management (Continued) Narrative

LDM: User Management

User Management Narrative

LDM: Reference Data Management Tool

Reference Data Management Tool Narrative

LDM: RDMT Organizational Management

RDMT Organizational Management Narrative

LDM: RDMT Contract Management

RDMT Contract Management Narrative

LDM: RDMT Locations and Airports

RDMT Locations Narrative

RDMT Airports Narrative

4 | P a g e

LDM: RDMT Incident Report

LDM: RDMT at Incident

LDM: RDMT Incident Reference Data

LDM: Document Management

LDM: Document Management Narrative

Task #13: Data Dictionary Common Attributes

Incident Management

Incident

Incident Location

Incident Navigation Aid

Incident Point of Contact

Incident Financial Code

Incident Status

Incident Airport

Incident Aviation Hazard

Incident Radio Frequency

Incident Related Incident

Incident Relation Type

Incident Authorization

Incident Authorization Type

Resource Ordering

Order

Order Order Type

Order Type

Order Order Status

Order Status

Order Resource Item

Order Resource Item Feature

Resource Feature

Order Assignment

Order Assignment Resource Item

Support Order

Order TFR (Temporary Flight Restriction Request)

5 | P a g e

Order Placement

Ordering Channel

Agreement Management

Agreement

Agreement Type

Agreement Resource Item

Agreement Resource Item Organizational Unit

Agreement Extension

Agreement Agreement Status

Agreement Status

Agreement Organizational Unit

Agreement Vendor

Resource Travel

Travel

Travel Leg

Travel Leg Order Assignment Resource Item

Transport Type

Travel Status

Travel Travel Status

Travel Type

Resource Management

Resource Item

Non-Inventory Type

Resource Item Contact

Resource Item Management

Resource Item Activation

Resource Item Resource Item Status

Resource Item Status

Resource Item Transfer

Resource Item Catalog Item

Qualification Status

Catalog Item

Keyword

Catalog Item Keyword

6 | P a g e

Category

Catalog

Catalog Item Alias

Alias

Catalog Item Configuration

Master Roster

Resource Item Release Restriction

Resource Item Release

Resource Item Release Status

Resource Item Release Status

User Management

User

User Account

User Account Organizational Unit

Role

Role Function

Association table

Function

User Contact

User System Notification Type

System Notification Type

Entity

Audit Log

Audit Log Annotation

RDMT- Organizational Management

Dispatch Host

Dispatch Provider

ICBS-R Default Cache

Organizational Unit Contact

Affiliation

Affiliation Type

Affiliation Resource Item

Organizational Unit Reload Base

Organizational Unit Airport

7 | P a g e

Host Radio Frequency

RDMT - Reference Data

Administrative Type

Organizational Unit Administrative Type

Organizational Unit

Organizational Unit Type

Organizational Unit Financial Code

GACC – Geographic Area Control Center

Agency

Political Unit

System

Event Category

Event Kind

Fire Cause

Time Zone

Landowner Kind

Landowner Category

Incident Type

Initial Fire Strategy Designator

Location Use

Management Complexity

Management Organization

ICBS-R Cache

Change Request

Change Request Status

Change Request Change Request Status

Incident Status

Size Class

Contact

Contact Method

RDMT Incident Information Sharing

Incident View

RDMT - Contract Management

Contract

8 | P a g e

Contract Extension

Contract Organizational Unit

Contract Vendor

Contract Resource Item

Contract Resource Item Organizational Unit

Contract Contract Status

Contract Status

Vendor

Vendor Contractor Type

Contractor Type

RDMT - Locations and Airports

Location

County

State

Location Contact

Incident Location Type

Airport

Airport Airport Use

Airport Use

Airport Dispatch

Airport Special Condition

Aviation Hazard Type

Aviation Hazard

Navigation Aid

Document Management

Document Metadata

Appendix A: List of Acronyms Appendix B: Revision 0.1 Detailed Response ...................................................................... Error! Bookmark not defined.

9 | P a g e

Introduction

Data is the most important part of any system. A good, strong, accurate data structure allows application developers to design any processing, user interface, reporting, or statistical analysis ever needed. The only thing more important than a quality data structure in developing systems, are the business requirements. The most elegant, high tech system in the world will be shelved if it does not meet a business requirement. Therefore, logical data modeling combines the two most important components of system development, business requirements and quality data structure.

A Logical Data Model (LDM) is a graphical representation of the information requirements of a business area; it is not a database. The word logical is very critical because it modifies the phrase data modeling to a more specific activity. A logical data model is independent of a physical, data storage device. This is the key concept of the logical data model.

The reason that a logical data model must be independent of technology is simply because technology is changing so rapidly.

Most business areas do not change as rapidly as technology. They performed this business without computers and now perform it on mainframes, minicomputers, PCs, networks, and the Internet. What the business does, has not changed, but how the work is accomplished, has changed significantly. This difference between what the business requirements are and how they are accomplished describes the difference between a logical data model and physical database.

An organization’s data will be physically stored in many different places, e.g. paper files, computer files. This data will almost inevitably contain duplications and compromises due to the physical restrictions of storage, processing or practicality. For example, in typical supply chain fashion a physical purchase order form will hold information about products (product name, product number, and product price), suppliers (supplier name, supplier address), the order’s heading (purchase order number, purchase order date) as well as the quantity of each product ordered (quantity ordered). While there may have been a single physical grouping of data on one purchase order form, there is actually information about several different things - products, suppliers, and purchase orders.

The majority of data required for the future system will be the same in content or meaning as that used currently. The approach of starting with an analysis of existing data (or even re-using existing data models) will provide a rigorous and efficient approach.

The vehicle for analyzing the logical structure of an organization’s information is the Logical Data Model. A Logical Data Model is a way of graphically representing what that information is really all about, how it relates to other information and business concepts. Data modeling requires a different mindset than requirements gathering for application development and process-oriented tasks. It is important to think “what” is of interest instead of “how” tasks are accomplished.

The most important reason to build a logical data model is to confirm the understanding of the business requirements to assure that the system developed satisfies the business need. Most business area experts can articulate problems, and often times, solutions. Unfortunately their problems and solutions are often based on current system constraints, not true business needs. Each business process is tied to the LDM to assure that all data and process model components have been discovered.

10 | P a g e

Task #13: Logical Data Models

The Logical Data Model (LDM) deliverable consists of three parts, a data dictionary, a diagram and set of narratives that explain each part of the diagram. In logical models, relationships represent business associations and not physical links.

The entities and relationships that are related are linked by a line on the LDM. The number of occurrences of each entity type participating in a given relationship is denoted by the degree or cardinality of that relationship, and illustrated on the LDM by adding ‘crow’s feet’ to the relationship’s line.

There are three types of degree:

• Many to Many (m:n). This tells us that each occurrence of A is related to one or more occurrences of B, and each occurrence of B is related to one or more occurrences of A.

• One to Many (1:m). This tells us that each occurrence of A is related to one or more occurrences of B, but each occurrence of B is related to only one occurrence of A.

• One to One (1:1). This tells us that each occurrence of A is related to only one occurrence of B, and each occurrence of B is related to only one occurrence of A.

Each relationship is further annotated to show if it must exist for all occurrences of the participating entity types. If there can be occurrences of one entity that are not related to at least one occurrence of the other, then the relationship is said to be optional for that entity.

11 | P a g e

Logical Data Models with Narratives

LDM Guide and Legends

12 | P a g e

• Primary Keys are unique identifier attributes within an entity. In this document, Primary keys are named after the entity plus the word ID. Primary keys can be automatically generated unique numbers.

• The primary keys with the suffix “Number” mean the identifier can be manually entered or is generated by an algorithm.

• Foreign keys have a page number in parenthesis to easily find the foreign entity associated with that key.

• Begin-End Dates allow for a record to be soft-deleted but remain available for accurate historical reporting.

• Some entities show a bulleted list of possible values with an ellipsis (…) at the end of the list. This means the list can grow to include other values during the design and system maintenance project phases.

• Some associations are modeled directly, instead of going through an association table. For example, Catalog Item is associated to the Keyword entity through a third intermediate association table.

• Overrides and/or Exceptions for business rules shall always be documented with appropriate information.

• Timestamps shall be stored in GMT, Time Zone data shall be added to Time and Date stamps to enable localization.

• When designing database architecture for tables that will be shared in concept and/or content, RDMT shall be consulted for architecture standards. For example, the Contact entity will be found within RDMT but also in IROC without sharing any records, these two tables shall have exactly the same structure to keep consistency.

• Source of Record is the repository system. Authoritative Data Source is the System or Tool that deposited the record into the Source of Record repository.

• GUIDs are unique specially formatted numeric strings generated by a “GUID generation tool.” GUIDs can be generated at http://www.guidgenerator.com.

• In this document, agreements are managed within IROC and contracts flow through the RDMT but will be managed through VIPR or another tool.

http://www.guidgenerator.com/

13 | P a g e

LDM Notes on Agreement vs Contract Management

System language and user language often use the same words with entirely different meanings. In the new model, there was a need to separate the different types of contracts, compacts and agreements between IROC and RDMT, so the result is the system language used has a different meaning from the user community language. For example, currently pre-negotiated compact agreements are called agreements by the user community. The new model considers the compact agreement to be a contract since it pre-negotiated with multiple approvers.

In both systems, the functionality to manage contracts, compacts and agreements are documented in the LDM and SRS deliverables. Ideally in the new model, on-the-fly agreements and call when needed would be the only agreement types entered directly into IROC. All other contract types, contracts, compacts, state and local vendors, exclusive use and purchase agreements, would ideally be processed through RDMT either directly or through other systems. If RDMT is not implemented IROC can manage contracts or import contracts from other contract management systems like VIPR.

Below is more detail on how the new model for IROC and RDMT differentiated the types of agreement and contract management.

Agreement: The system definition of an Agreement as listed on the IROC LDM is a short duration, ad hoc, or “on the fly” agreement, contract or purchase order that is not pre-negotiated before the incident or needing multiple approvals.

• Entered (into IROC) directly (IROC = SoR)

• BUYER inputted, at the incident

• Short in duration (Ex: For the life of an incident)

Contract: The system definition of a Contract as listed on the RDMT LDM is a longer duration agreement, compact or contract that is pre-negotiated and/or needs multiple approvals.

• Federal vendors (only) o Set up in VIPR (VIPR = SoR) o Imported into RDMT o Set up pre-season o Set up yearly

• State and Local vendors o Set up in “other” contract management systems (OCMS = SoR) o Imported into RDMT o Set up pre-season (*may not be for all local contracts) o Set up yearly

• Compact (SoR) o Entered (into RDMT) directly (RDMT = SoR) o Data Steward inputted or electronically o Set up pre-season o Set up yearly (*may be longer in duration)

14 | P a g e

LDM: Incident Management

15 | P a g e

Incident Management Narrative

Entity: Incident

Supports the Primary Function: Incident Management

Primary Key: Incident Number. Description: System generated, unique ID, sequential. Used once, then retired.

• Primary Data Elements:

o Incident Name o Description o Reported By o Min and Max Elevation o Hazard Radius o Begin-End Dates

• Supported By (other Entities):

o Incident Type ID o Event Type ID o Organizational Unit o System ID

Primary Relationship With:

o Incident Location o Incident Navigation Aid o Incident Point of Contact o Incident Financial Code o Incident Status o Incident Airport o Incident Aviation Hazard

Supported by Aviation Hazard o Incident Radio Frequency o Related Incident o Incident Complex

Supporting Relationship With:

o N/A

Supporting Process: TBD

16 | P a g e

LDM: Incident Management (Continued)

17 | P a g e

Incident Management (Continued) Narrative

Entity: Incident

Supports the Primary Function: Incident Management

Primary Key: Incident Number. Description: System Generated, unique ID, sequential. Used once, then retired.

• Primary Data Elements:

o Incident Code

• Supported By (other Entities):

o N/A

Primary Relationship With:

o Incident Authorization

Supporting Relationship With:

o RDMT (external system)

Incident Code Incident Type Event Type Organizational Unit System ID

18 | P a g e

LDM: Resource Ordering

19 | P a g e

Resource Ordering Narrative

Entity: Order

Supports the Primary Function: Resource Ordering

Primary Key: Order. Description: System generated, unique ID, sequential. Used once, then retired.

• Primary Data Elements:

o Resource Billing Data o Non-Catalog Item o DOI Delivery Order Number

• Supported By (other Entities):

o Organizational Unit o Incident Number o Contract Number o Agreement Number

Primary Relationship With:

o Order Status o Order Resource Item

Order Assignment

• Order Assignment Resource Item

Order Resource Item Feature

• Resource Feature o Support Order

Supporting Relationship With:

o Incident Number o Order Order Type

Order Type

Supporting Process: Resource recommendation.

20 | P a g e

LDM: Resource Ordering (Continued)

21 | P a g e

Resource Ordering (Continued) Narrative

Entity: Order

Supports the Primary Function: Order Placement

Primary Key: Order. Description: System generated, unique ID, sequential. Used once, then retired.

• Primary Data Elements:

o Resource Billing Data o Non-Catalog Item o DOI Delivery Order Number o Incident Number o Contract Number o Order Temporary Flight Restriction

Supporting Relationship With:

o Order Placement Dispatch Resource Item

• Ordering Channel

Supporting Process: Dispatch Resource Item.

22 | P a g e

LDM: Agreement Management

23 | P a g e

Resource Management Narrative

Entity: Agreement

Supports the Primary Function: Agreement Management

Primary Key: Agreement. Description: Agreement number system generated, unique ID, sequential. Used once, then retired.

• Primary Data Elements:

o Agreement Type o Agreement Data o Geographical Area o Begin-End Dates

• Supported By (other Entities):

o Organizational Unit o On The Fly Agreement Order ID

Primary Relationship With:

o Agreement Type o Agreement Resource Item

Agreement Resource Item Organizational Unit o Agreement Status o Agreement Extension o Agreement Organizational Unit o Agreement Vendor

Vendor Vendor Contact Vendor Contractor Type

Supporting Relationship With:

o RDMT (external system)

Vendor Vendor Contact Vendor Contractor Type

24 | P a g e

LDM: Resource Travel

25 | P a g e

Resource Travel Narrative

Entity: Travel

Supports the Primary Function: Resource Travel

Primary Key: Travel. Description: Travel agency integrated upload or manually entered.

• Primary Data Elements:

o Travel Type o Travel To Location o Travel From Location o Incident ID o Organizational Unit ID o Order Assignment Resource Item o Travel Type o Travel Leg

Travel Leg Order Assignment Resource Item Transport Type o Travel Status

26 | P a g e

LDM: Resource Management

27 | P a g e

Resource Management Narrative

Entity: Resource Item

Supports the Primary Function: Resource Management

Primary Key: Resource Item. Description: Inventoried and non-Inventoried cataloged resource items.

• Primary Data Elements:

o Resource Item Name o Begin-End Dates o Available Multiple Incidents o Non-Inventory Type o Organizational ID Home Dispatch o Location ID o Unit of Measure o Unit Cost o Resource Item Management o Resource Item Activation o Resource Item Status o Resource Item Transfer o Resource Item Catalog Item

Catalog Item

• Keyword

• Catalog Item Alias o Alias

• Category o Catalog o Resource Item Contact

28 | P a g e

LDM: Resource Management (Continued)

29 | P a g e

Resource Management (Continued) Narrative

Entity: Resource Item

Supports the Primary Function: Resource Management

Primary Key: Resource Item. Description: Inventoried and non-Inventoried cataloged resource items.

• Primary Data Elements:

o Resource Item Name o Begin-End Dates o Available Multiple Incidents o Non-Inventory Type o Organizational ID Home Dispatch o Location ID o Resource Item Release Restriction o Resource Item Release

Resource Item Release Status

Supporting Relationship With:

o Master Roster Catalog Item

• Catalog Item Configuration

30 | P a g e

LDM: User Management

31 | P a g e

User Management Narrative

Entity: User

Supports the Primary Function: User Management

Primary Key: User. Description: User identifier created in NAP (NESS Application Portal).

• Primary Data Elements:

o User Data o User Unique Identifier

Primary Relationship With:

o User Contact o User System Notification

System Notification Type o User Account

Audit Log

• Audit Log Annotation

• Entity

User Account Organizational Unit

• Role

• Function

32 | P a g e

LDM: Reference Data Management Tool

33 | P a g e

Reference Data Management Tool Narrative

Overall, Supports the Primary Function: Maintain Reference Data

Key Lookup Tables:

o Organizational Unit

Organizational Unit Administrative Type

• Administrative Type

Agency Time Zone Organizational Unit Financial Code

• Fire Code (external system) o System o Incident Type o Event Type o Change Request

Entity: Organizational Unit

Primary Key: Organizational Unit. Description: System generated, unique ID, sequential. Used once, then retired.

Primary Data Elements:

o Organizational Name o Organizational Unit Parent o Agency Code o Begin-End Dates

Supported By (other Entities):

o Location o Time Zone

Primary Relationship With:

o Organization Unit Administrative Type o Organizational Unit Financial Code

Fire Code (external system)

Supporting Relationship With:

o Time Zone

34 | P a g e

Entity: System

Primary Key: System. Description: Various external systems.

Primary Data Elements:

o System Name o Begin-End Dates

Supported By (other Entities):

o N/A

Primary Relationship With:

o N/A

Supporting Relationship With:

o Fire Code (external system)

Organizational Unit Financial Code o IROC (external system)

System ID o CAD (external system)

Incident Type Event Type o VIPR (external system) Contractor Type o FAA (external system) Location Use o IQCS, IQS, EQS Resource Qualifications

Supporting Process: TBD

Entity: Incident Type

Primary Key: Incident Type. Description: Various incident types, maintained by data stewards.

Primary Data Elements:

o Type

Supported By (other Entities):

o N/A

Primary Relationship With:

o N/A

Supporting Relationship With:

35 | P a g e

Entity: Event Type

Primary Key: Event Type. Description: Various event types, maintained by data stewards.

Primary Data Elements:

o Name

Supported By (other Entities):

o N/A

Primary Relationship With:

o N/A

Entity: Change Request

Primary Key: Change Request. Description: System generated, unique ID, sequential. Used once, then retired.

Primary Data Elements:

o Change Information o Email Address

Supported By (other Entities):

36 | P a g e

LDM: RDMT Organizational Management

37 | P a g e

RDMT Organizational Management Narrative

Entity: Organizational Unit

Supports the Primary Function: Organizational Management

Primary Key: Organizational Unit. Description: Unique identifier from RDMT.

• Primary Data Elements:

o Organization Name o Organizational Unit Parent o Unit Number o Agency Code o Location o Dispatch Host o Dispatch Provider o ICBS-R Default Cache o Organizational Unit

Contact o Affiliation

Affiliation Resource Item Affiliation Type o Organizational Unit Reload Base o Organizational Unit Airport o Host Radio Frequency o RDMT (external system)

38 | P a g e

LDM: RDMT Contract Management

39 | P a g e

RDMT Contract Management Narrative

Entity: Contract

Supports the Primary Function: Contract Management

Primary Key: Contract Number. Description: Contract number supplied from external system or system generated, unique ID, sequential. Used once, then retired.

• Primary Data Elements:

o Contract Type o Contract Data o Payment Data o Geographical Area

Primary Relationship With:

o Contract Resource Item Contract Resource Item Organizational Unit o Contract Status o Contract Extension o Contract Organizational Unit o Contract Vendor

Vendor

• Contact

Vendor Contractor Type

• Contractor Type o VIPR (external system) o Other Contract Management System TBD

40 | P a g e

LDM: RDMT Locations and Airports

41 | P a g e

RDMT Locations Narrative

Entity: Location

Supports the Primary Function: Location

Primary Key: Location. Description: Location information for any address or lat/long.

• Primary Data Elements:

o Lat/Long Coordinates o Address o TRS Data o UTM Coordinates o System o Location Contact o Location Location Use

Location Use

Supporting Relationship With:

Airport

42 | P a g e

RDMT Airports Narrative

Entity: Airport

Supports the Primary Functions: Airport

Primary Key: Airport. Description: Airport names and airport codes with navigation information.

• Primary Data Elements:

o Name o Permanent Tanker Base o FAA Code o Location ID o Airport Dispatch Organizational Unit o Airport Special Condition o FAA Code

Navigation Aid

Supporting Relationship With:

o FAA (external system) o Aviation Hazard Type

43 | P a g e

LDM: RDMT Incident Report

44 | P a g e

LDM: RDMT at Incident

45 | P a g e

LDM: RDMT Incident Reference Data

46 | P a g e

LDM: Document Management

47 | P a g e

LDM: Document Management Narrative

Entity: Document MetaData

Supports the Primary Function: Document Management

Primary Key: Document MetaData. Description:

• Primary Data Elements:

o Timestamp o Description o Computer o Operating System o Browser Info o User Account o Organizational Unit o Entity o Entity Record o System o Document o User Account o Entity

Supports the Secondary Function

Logical Data Model for FRMT and RDMT

48 | P a g e

Task #13: Data Dictionary

Common Attributes These attributes should be added to every table to keep audit logs and periods of effectiveness.

For convenience, a link has been added for Foreign keys to the Foreign Table, use “ctrl+click” on the name of the foreign table in the description cell to peek at the foreign key data structure.

Attribute Type Min-Max Field Length

Format Source of Record

Authoritative Data Source

Possible Values Description

Begin Date 8-8 YYYY-MM-DD IROC IROC Record valid from this date

End Date 0-8 YYYY-MM-DD IROC IROC Record valid through this date

User Account ID Creator

Number IROC IROC Foreign Key to User Account table

Date-time created Datetime 25-25 YYYY-MM- DDThh:mm:

ss.fffZ

IROC IROC

User Account ID last Modified

Number IROC IROC Foreign Key to User Account master table

Date-time last modified

Datetime 25-25 YYYY-MM- DDThh:mm:

ss.fffZ

IROC IROC

System ID Number FMRT RDMT Foreign Key to System domain table.

The source system or origination of the data.

Time Zone ID Number IROC RDMT Foreign key to Time Zone domain table

49 | P a g e

Incident Management

Incident Master table to collect the main information about a particular incident from birth to total containment.

Attribute Type Min-Max Field Length

Format Source of Record

Authoritative Data Source

Possible Values Description

Incident ID GUID H=hexadecimal digit

{HHHHHHHH-HHHH-

HHHH-HHHH-

HHHHHHHHHHHH}

IROC RDMT Generated Global Unique Identifier

Local Incident Identifier

Varchar 6-10 XXXXXX IROC IROC 000025 A number or code that uniquely identifies an incident for a particular local fire management organization within a particular calendar year.

Incident Number Varchar 17-22 YYYY-SSUUUU-

XXXXXX

IROC IROC 2015-IDBOF-000025 Unique identifier assigned to each Wildland fire. YYYY = calendar year, SSUUUU = POO responsible unit identifier (5 or 6 characters), XXXXXX = local incident identifier (6 to 10 characters)

Incident Name Varchar 2-50 IROC CAD, IROC The name assigned to an incident.

Description Varchar 2-800 IROC CAD, IROC Free text area to elaborate on incident description Reported by Varchar 1-100 IROC CAD, IROC Free area to enter data for person who reported the incident.

Elevation Minimum

Number IROC CAD, IROC

Elevation Maximum

Number IROC CAD, IROC

Aviation Hazard Radius

Number IROC CAD, IROC Used to obtain a circled area around the incident coordinates, any aviation hazards located within this area should be associated with the incident

Incident Type ID Number IROC CAD, IROC Foreign Key Incident Type table, refers to the administrative type of incident.

Attribute Type Min-Max Format Source of Authoritative Possible Values Description

50 | P a g e

Field Length Record Data Source

Event Category Code

Varchar 2-2 XX IROC CAD, IROC Foreign Key to Event Category table.

Refers to code that identifies the types of incidents and planned events to which the interagency wildland fire community responds.

The Event Category is a sub-group of the Event Kind (See the Event Kind table) code and description. The Event Kind provides a general, high-level description. The Event Category further breaks down the Event Kind into more specific event categories.

Organizational Unit ID Dispatch

Number IROC CAD, IROC Foreign Key to Organizational Unit master table. Refers to the Organizational Unit that will be in charge of supplying resources during the incident’s response.

Organizational Unit ID Host

Number IROC CAD, IROC Foreign Key to Organizational Unit master table. Refers to the Organizational Unit of the Incident’s Host. The incident host is a government organizational unit at any level of geographic scope that has administrative responsibility for managing incidents or projects supported by the wildland fire community. In most cases, the host of an incident is the organizational unit that has jurisdiction (i.e., land ownership) and responsibility for management of the area involved. In situations where a government organizational unit provides emergency response services for incidents on private lands, that government unit is the incident host.

Attribute Type Min-Max Field Length

Format Source of Record

Authoritative Data Source

Possible Values Description

51 | P a g e

Fire Cause ID Number IROC CAD, IROC Foreign key to Fire Cause domain table. Examples: Natural, Human, Undetermined.

Fire Discovery Date Time

Datetime 25-25 YYYYMMDDhhmmss.

ss

IROC CAD, IROC The date and time a fire was reported as discovered or confirmed to exist.

May also be the start date for reporting purposes.

Fire Out Date Time Datetime YYYYMMDDhhmmss.

ss

IROC CAD, IROC The date when all observable combustion has ceased or there is no risk of the fire again becoming active and requiring additional control or management actions. All management activities directly relating to suppression (including mop-up), monitoring, or burning efforts have concluded; however, there may be secondary management efforts, such as burned area rehabilitation or hazard mitigation, still in process. In this implementation, the fire out date may also capture the date on which the fire was enveloped in the scenario where multiple fires have merged together.

Organizational Unit ID Protecting

Number FMRT CAD, IROC Foreign Key to Organizational Unit master table. NWCG Unit Identifier data standard to identify the agency with primary fire protection responsibility at the point of origin of a fire.

Size Class Char 1-1 X IROC IROC, CAD A (> 0 but <= 0.25 Acres), B (0.26 - 9.9 Acres), C (10.0 - 99.9 Acres), D (100 - 299 Acres), E (300 - 999 Acres), F (1000 - 4999 Acres),G(5000- 9999Acres),H(10000- 49999Acres),I(50000- 99999Acres),J(100000- 499999Acres),K(500000

Foreign Key to Size Class domain table.

Size Class is a code identifying the fire size based on number of acres within the final fire perimeter. The value entered should reflect the final fire acre quantity.

52 | P a g e

999999Acres),L(100000 0+Acres)

Discovery Acres Number IROC IROC, CAD As a minimum, fires greater than one acre will at least be reported to the nearest acre (i.e.

first digit to the right of the decimal point for fires > 1 acre)

An estimate of acres burning upon the discovery of the fire. More specifically when the fire is first reported by the first person that calls in the fire. The estimate should include number of acres within the current perimeter of a specific, individual incident, including unburned and unburnable islands.

As a minimum, fires less than one acre will be reported to the tenth of an acre.

Final Acres Number DD.D IROC IROC, CAD Number of acres within the final fire perimeter polygon of a specific, individual incident, including unburned and unburnable islands. For fires that have a fire perimeter mapped in GIS, the final fire size reported should equal the fire size calculated from the GIS perimeter (wildland fire perimeter polygon).

Total should include 1 decimal place.

(ArcGIS: Precision=10; Scale=1).

Example: 14.

Perimeter Exists Char 1-1 X IROC IROC, CAD Y or N Identifies if a related wildland fire perimeter polygon exists for the wildland fire location point feature.

Initial Fire Strategy Designator

Varchar 2-3 XXX FRM IROC, CAD IA, LS, RX, WFU Foreign key to Initial Fire Strategy Designator domain table. The fire strategy initially used on a wildland fire.

The initial fire strategy is the general plan or direction utilized until it succeeds or changes. The NWCG glossary defines strategy as: The general plan or direction selected to accomplish incident objectives.

Initial Response Acres

Number IROC CAD, IROC As a minimum, fires less than one acre will be reported to the tenth of an acre.

As a minimum, fires

An estimate of acres burning at the time of initial response. More specifically when the IC arrives and performs initial size up. The minimum size must be 0.1. The estimate should

53 | P a g e greater than one acre will at least be reported to the nearest acre (i.e.

first digit to the right of the decimal point for fires > 1 acre).

include number of acres within the current perimeter of a specific, individual incident, including unburned and unburnable islands.

Management Complexity ID

Number IROC CAD, IROC, RDMT

Foreign key to Management Complexity domain table. Refers to the highest management level utilized to manage a fire event.

Management Organization ID

Number IROC CAD, IROC, RDMT

Foreign key to Management Organization domain table.

Incident Location Locations associated with Incident. Locations are data records that contain data about a specific place.

Attribute Type Min-Max Field Length

Format Source of Record

Authoritative Data Source

Possible Values Description

Incident ID GUID IROC IROC Foreign Key to Incident master table

Location ID Number Foreign Key to Location table

Incident Location Type ID

Number IROC IROC Shipping, Point of Origin

Foreign key to Incident Location Type domain table

Incident Navigation Aid Navigation Aids associated with Incident.

Attribute Type Min-Max Field Length

Format Source of Record

Authoritative Data Source

Possible Values Description

Incident Navigation Aid ID

Number IROC IROC Generated unique identifier

Incident ID GUID IROC IROC Foreign Key to Incident master table

Navigation Aid ID Number

IROC

IROC, RDMT,

FADDS

Foreign Key to Navigation Aid domain

Incident Point of Contact Contacts associated with Incident.

54 | P a g e

Attribute Type Min-Max Field Length

Format Source of Record Authoritative Data Source

Possible Values

Description

Incident ID GUID IROC CAD, IROC Foreign Key to Incident master table

Contact ID Number IROC CAD, IROC Foreign Key to Contact master table

Incident Financial Code Financial codes associated with Incident.

Attribute Type Min-Max Field Length

Format Source of Record

Authoritative Data Source

Possible Values Description

Incident ID GUID IROC IROC Foreign Key to Incident master table

Financial Code Varchar 4-4 XXXX FIRECODE FIRECODE Identifier established by an agency's fiscal organization to track expenditures.

Is Default for Ordering

Boolean IROC IROC True, False Automatically default an order created for this incident to this code

Is Active Boolean IROC IROC It can be used for ordering

Incident Status Status associated with Incident.

Attribute Type Min-Max Field Length

Format Source of Record

Authoritative Data Source

Possible Values Description

Incident ID GUID IROC IROC Foreign Key to Incident master table

Status ID Number IROC RDMT Foreign Key to Incident Status table in

RDMT.

Incident Airport Airports associated with Incident

Attribute Type Min-Max Field Length

Format Source of Record

Authoritative

55 | P a g e

Incident ID GUID IROC IROC Foreign Key to Incident master table

Airport ID Number IROC RDMT Foreign Key to Airport domain table

Incident Aviation Hazard Aviation hazards associated with Incident

Attribute Type Min-Max Field Length

Format Source of Record

Authoritative Data Source

Possible Values Description

Incident ID GUID IROC IROC Foreign Key to Incident master table

Aviation Hazard

ID

Number IROC IROC Foreign Key to Aviation Hazard master table

Incident Radio Frequency Radio frequencies associated with Incident

Attribute Type Min-Max Field Length

Format Source of Record

Authoritative Data Source

Possible Values Description

Incident ID GUID IROC IROC Foreign Key to Incident master table

Host Radio Frequency ID

Number IROC IROC Foreign Key to Host Radio Frequency table

Incident Related Incident Incidents associated with Incident. This association table will be supporting scenarios like merging incidents, splitting incidents, tying multiple incidents that are managed as a complex.

Attribute Type Min-Max Field Length

Format Source of Record

Authoritative Data Source

Possible Values Description

Incident ID GUID IROC IROC Foreign Key to Incident master table Related Incident

ID

GUID IROC IROC Foreign Key to Incident master table

Incident Relation Type ID

Number IROC IROC Foreign Key to Incident Relation Type domain table.

Incident Relation Type Domain table for Incident Relation Type.

Attribute Type Min-Max Field

Length Format Source of

Record Authoritative

56 | P a g e

Incident Relation Type ID

Number IROC IROC Generated Unique Identifier

Incident Relation Type Name

Varchar IROC IROC Predecessor, Follow On, Merged From, Initial Report, Split To, Complex, Incident Authorization Authorizations associated with Incident.

Attribute Type Min-Max Field Length

Format Source of Record

Authoritative Data Source

Possible Values Description

Incident ID GUID IROC IROC Foreign Key to Incident master table Organizational Unit ID Managing

Number IROC IROC Foreign Key to Organizational Unit master table. Refers to the organizational unit (and associated user accounts) being granted authorization

Incident Authorization Type ID

Number IROC IROC Foreign Key to Incident Authorization Type domain table

Incident Authorization Type Domain table, refers to authorization types available for Incidents.

Attribute Type Min-Max Field Length

Format Source of Record

Authoritative Data Source

Possible Values Description

Incident Authorization Type ID

Number IROC IROC Generated unique identifier

Authorization Type

Varchar IROC IROC Merge, Reassign Resources, …

57 | P a g e

Resource Ordering

Order Master table.

Attribute Type Min-Max Field Length

Format Source of Record

Authoritative Data Source

Possible Values

Description

Order ID Number IROC IROC Generated unique identifier

Resource Billing Data

Varchar IROC IROC

Non-catalog Item Varchar IROC IROC Ice bag, toilet paper, …

DOI Delivery Order Number

Varchar IROC IROC

Organizational Unit ID Managing

Number RDMT IROC Foreign Key to Organizational Unit master table

Incident ID GUID IROC IROC Foreign Key to Incident master table

Contract Number Varchar RDMT IROC Foreign key to Contract master table

Agreement ID Number IROC IROC Foreign key to Agreement master table

Location ID Number IROC IROC Incident location by default but can be changed for procurement purposes

Foreign Key to Organizational Unit master table

58 | P a g e

Order Order Type Order types associated with an Order.

Attribute Type Min-Max Field Length

Format Source of Record

Authoritative Data Source

Possible Values Description

Order Order Type

ID

Number IROC IROC Generated unique identifier

Order Type ID Number IROC IROC Foreign Key to Order Type domain table

Order ID Number IROC IROC Foreign Key to Order master table

Order Type Domain table.

Attribute Type Min-Max Field Length

Format Source of Record

Authoritative Data Source

Possible Values Description

Order Type ID Number IROC IROC Generated unique identifier

Order Type Varchar IROC IROC Pre-order (no associated incident), Detail (for long-term resources), Replacement

Order Order Status Status associated with an Order.

Attribute Type Min-Max Field Length

Format Source of Record

Authoritative Data Source

Possible Values

Description

Order Status ID Number IROC IROC Generated unique identifier

Organizational Unit ID Filling

Number IROC IROC Foreign Key to Organizational Unit master table, can be the organizational unit that retrieved the Order in order to fulfill it

Order Status ID Number IROC IROC Foreign Key to Order Status domain table

59 | P a g e

Order Status Domain Table.

Attribute Type Min-Max Field Length

Format Source of Record

Authoritative Data Source

Possible Values Description

Order Status ID Number IROC IROC Generated unique identifier

Status Varchar IROC IROC Pending, In Progress, UTF (Unable to Fill), Filled, Cancelled, Deleted

Order Resource Item Order detail table, Resource Items associated with an Order.

Attribute Type Min-Max Field Length

Format Source of Record

Authoritative Data Source

Possible Values

Description

Order Resource Item ID Number IROC IROC Generated unique identifier

Order ID Number IROC IROC Foreign Key to Order master table

Resource Item ID Number IROC IROC Foreign Key to Resource Item master table, optional when Catalog Item present. In the case no resource item ID is entered, assignment is recommended based on Qualifications/Classifications.

Catalog Item ID Number IROC IROC Foreign key to Catalog Item domain table

Quantity Number IROC IROC

Catalog Item Configuration ID

Number IROC IROC Foreign key to Catalog Item Configuration table

Master Roster ID Number IROC IROC Foreign key to Master Roster table, optional. User should select from mater rosters associated with Catalog Item Configuration ID

60 | P a g e

Order Resource Item Feature Resource Item features associated with an Order Resource Item line.

Attribute Type Min-Max Field Length

Format Source of Record

Authoritative Data Source

Possible Values Description

Order Resource Item Feature ID

Number IROC IROC Generated unique identifier

Resource Feature ID Number IROC IROC Foreign Key to Resource Feature table

Order Resource Item ID Number IROC IROC Foreign Key to Order Resource Item table

Resource Feature Domain table.

Attribute Type Min-Max Field Length

Format Source of Record

Authoritative Data Source

Possible Values Description

Resource Feature ID Number IROC IROC Generated unique identifier

Feature Varchar IROC IROC 4wheel drive, Lights, …

Order Assignment Master table for Order Assignment Resource Item it groups Order Resource item records to allow the system to assign different filling Organizational Units to items in the same order.

Attribute Type Min-Max Field Length

Format Source of Record

Authoritative Data Source

Possible Values Description

Order Assignment ID Number IROC IROC Generated unique identifier

Order Resource Item ID Number IROC IROC Foreign Key to Order Resource Item table

Organizational Unit ID Filling

Number IROC IROC Foreign Key to Organizational Unit

61 | P a g e

Order Assignment Resource Item This table will store the resource items that fulfill an Order Resource Item. It can include resource items configured in a Master Roster.

Attribute Type Min-Max Field Length

Format Source of Record

Authoritative Data Source

Possible Values Description

Order Assignment Resource Item ID

Number IROC IROC Generated unique identifier

Order Assignment ID Number IROC IROC Foreign Key to Order Assignment master table, this is the supported Order.

Resource Item ID Number IROC IROC Foreign Key to Resource Item master table

Order Assignment Resource Item ID Parent

Number IROC IROC Foreign Key to same Order Assignment Resource Item table, this supports handling of master rosters and subordinate order items

Travel Needs Varchar IROC IROC Describe travel needs for resource, can include: commercial, agency, private …

Master Roster ID Number IROC IROC Foreign Key to Master Roster table

Support Order Support Order associated with an Order.

Attribute Type Min-Max Field Length

Format Source of Record

Authoritative Data Source

Possible Values Description

Order ID Number IROC IROC Foreign Key to Order master table, the supporting Order.

Order ID Parent Number IROC IROC Foreign Key to Order master table, this is the supported Order.

62 | P a g e

Order TFR (Temporary Flight Restriction Request) TFRs associated with an Order.

Attribute Type Min-Max Field Length

Format Source of Record

Authoritative Data Source

Possible Values Description

Order TFR ID Number IROC IROC Generated unique identifier

TFR Data Varchar IROC IROC

Order ID Number IROC IROC Foreign Key to Order master table

Order Placement Place an Order to another dispatch when no local resource item will do.

Attribute Type Min-Max Field Length

Format Source of Record

Authoritative Data Source

Possible Values Description

Order Placement ID Number IROC IROC Generated unique identifier

Order ID Number IROC IROC Foreign Key to Order master table

Organizational Unit ID Filling

Number IROC IROC Foreign Key to Organizational Unit master table, refers to the organizational unit assigned to supply the order

Override ordering chain Boolean IROC IROC True, False

Ordering Channel Supports ordering channel fulfillment business rules.

Attribute Type Min-Max Field Length

Format Source of Record

Authoritative Data Source

Possible Values Description

Ordering Channel ID Number IROC IROC Generated unique identifier

Organizational Unit ID Parent

Number RDMT IROC Foreign Key to Organizational Unit master table

Organizational Unit ID Number RDMT IROC Foreign Key to Organizational Unit

63 | P a g e

Agreement Management Agreements are stored and managed by IROC, as opposed to contracts stored and managed by the RDMT (Reference Data Management Tool).

Agreement Master table.

Attribute Type Min-Max Field

Length Format Source of

Record Authoritative Data Source

Possible Values Description

Agreement ID Number IROC IROC Unique identifier

Agreement Type ID Number IROC IROC Foreign Key to Agreement Type domain table

Agreement Data Varchar IROC IROC This attribute needs more elaboration

Payment Data Varchar IROC IROC This attribute needs more elaboration

Organizational Unit ID Contracting Office

Number RDMT RDMT Foreign Key to Organizational Unit master table

Organizational Unit ID Managing Dispatch

Number RDMT RDMT Foreign Key to Organizational Unit master table

On the Fly Agreement Order ID

Number IROC IROC Foreign Key to Order master table

Geographical Area Geo-spatial

To allow the system’s ordering recommendation and validation to determine the agreement’s resource availability by geographical intersection.

Agreement Type Domain table.

Attribute Type Min-Max Field

Length Format Source of

Record Authoritative Data Source

Possible Values Description

Agreement Type ID Number IROC IROC Generated unique Identifier

Agreement Type Varchar IROC IROC On The Fly, CWN (Call when Needed), AGR (Agreement), 64 | P a g e

PA (Purchase Agreement )

Agreement Resource Item Resource items associated with an Agreement Attribute Type Min-Max Field

Length Format Source of

Record Authoritative Data Source

Possible Values Description

Agreement Resource Item

ID

Number IROC IROC Generated unique Identifier

Agreement ID Number IROC IROC Foreign key to Agreement master table

Catalog Item ID Number IROC IROC Foreign Key to Catalog Item master table, optional if Resource Item ID present

Resource Item ID Number IROC IROC Foreign Key to Resource Item master table, optional if Catalog Item ID present

Organizational Unit ID Responsible for Operator

Number IROC IROC Foreign Key to Organizational Unit master table

Vendor ID Responsible for Operator

Number RDMT RDMT Foreign Key to Vendor master table

Maximum Number of Operators

Number FRM IROC

Vendor Resource Code Varchar FRM IROC Corresponding Vendor Id for Resource Item

Unit of Measurement Varchar Day, hour, unit, box …

Unit Cost Number Allow the system to make recommendations based on cost-effective analysis

Agreement Resource Item Organizational Unit Organizational units associated with a particular Resource Item within an Agreement

65 | P a g e

Format Source of Record

Authoritative Data Source

Possible Values Description

Agreement Resource Item Organizational Unit ID

Number IROC IROC Generated unique Identifier

Agreement Resource Item

ID

Number IROC IROC Foreign Key to Agreement Resource Item table

Organizational Unit ID Management Allowed

Number RDMT RDMT Foreign Key to Organizational Unit master table

Organizational Unit ID Direct Access to Dispatch

Number RDMT RDMT Foreign Key to Organizational Unit master table

Agreement Extension Extensions associated with an Agreement Attribute Type Min-Max Field

Length Format Source of

Record Authoritative Data Source

Possible Values Description

Agreement Extension ID Number IROC IROC Generated unique Identifier Agreement ID Number IROC IROC Foreign key to Agreement master table Extension Information Varchar IROC IROC

Agreement Agreement Status Agreement Status associated with Agreement Attribute Type Min-Max Field

Length Format Source of

Record Authoritative Data Source

Possible Values Description

Agreement Agreement Status ID

Number IROC IROC Generated unique Identifier

Agreement ID Number IROC IROC Foreign key to Agreement master table

Agreement Status ID Varchar IROC IROC Active, Under consideration, Expired Extended

Foreign Key to Agreement Status domain table

Agreement Status Domain table

66 | P a g e

Format Source of Record

Authoritative Data Source

Possible Values Description

Agreement Status ID Number IROC IROC Generated unique Identifier

Agreement Status Varchar IROC IROC Active, Under consideration, Expired Extended

Agreement Organizational Unit Organizational units associated with an Agreement

Attribute Type Min-Max Field Length

Format Source of Record

Authoritative Data Source

Possible Values Description

Agreement Organizational Unit ID

Number IROC IROC Generated unique Identifier

Agreement ID Number IROC IROC Foreign key to Agreement master table

Organizational Unit ID Provider

Number RDMT RDMT Foreign Key to Organizational Unit master table

Agreement Vendor Vendors associated with an Agreement

Attribute Type Min-Max Field Length

Format Source of Record

Authoritative Data Source

Possible Values Description

Agreement Vendor ID Number IROC IROC Generated unique Identifier

Agreement ID Number IROC IROC Foreign key to Agreement master table

Vendor ID Provider Number RDMT RDMT Foreign Key to Vendor master

67 | P a g e

Resource Travel

Travel Master table

Attribute Type Min-Max Field Length

Format Source of Record

Authoritative Data Source

Possible Values Description

Travel ID Number IROC IROC Generated unique identifier

Location ID Travel From Number IROC IROC Foreign Key to master Location table

Location Id Travel To Number IROC IROC Foreign Key to master Location table

Incident ID Number IROC IROC Foreign Key to Incident master table

Travel Type ID Number IROC IROC Foreign Key to Travel Type domain table

Organizational Unit ID Managing

Number IROC IROC Foreign Key to Organizational Unit master table

Order Assignment Resource Item ID

Number IROC IROC Foreign Key to Order Assignment Resource Item table, only if only one resource item traveling

Travel Leg Transaction table, detail…