AFIMSC Tactical Mission Dependency Index
Matrix was retained by the Air Force Installation and Mission Support Center to develop and propagate a segmented infrastructure criticality factor for utility infrastructure and road networks. The Air Force had previously adopted a criticality factor for facilities called Tactical Mission Dependency Index (TMDI) through a series of in-person interviews over several years at over 80 different installation locations. Armed with that data, Matrix was asked to automate propagation of the facility TMDI to infrastructure using an inherency rule in which the TMDI value of the facility was inherited by the supporting infrastructure.
Matrix’s effort sought to develop a reliable, repeatable, defensible, and automated methodology for assigning survey based TMDI values to roads, parking, and utilities. Multiple stakeholder meetings and workshops were conducted and effectively facilitated in an entirely virtual platform accommodating groups as large as 50 people. Geographic Information Systems (GIS) was harnessed to apply a spatial solution for associating vertical assets with supporting infrastructure. A customized model was developed to assign TMDI values for each asset type of interest. The model was tested on five different installations and is now ready for enterprise-wide implementation that can be performed remotely in months versus the years it took for the facility TMDI to be developed in person.
The GIS solution was a first of its kind implementation of Esri’s trace network tool, available in ArcGIS Pro, customized using the python scripting language. A trace network was selected over the traditional utility network because it allowed for more variance in the quality of the underlying network, saving the Air Force both time and money. The customized model utilized an automated tracing loop to associate a facility to its supporting infrastructure. Hundreds of consecutive traces were performed in a logical order in accordance with assigned business rules. TMDI values for each asset were then programmatically adjusted to accommodate multiple scenarios. The final deliverable included infrastructure assets prioritized based on mission, and modeled dependencies and interdependencies, creating a risk management framework for each test installation.