Progress in Developing the National Asset Database
Progress in Developing the National Asset Database
Progress in Developing the National Asset Database
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
a risk assessment. Without a method to clean such assets from <strong>the</strong> <strong>in</strong>ventory,time and money will be wasted to repeatedly filter out such assets for eachanalysis, and perhaps more importantly, <strong>the</strong>ir presence undercuts confidence<strong>in</strong> <strong>the</strong> <strong>in</strong>ventory. Such out of place assets should be addressed.IP already elim<strong>in</strong>ates assets of “extreme <strong>in</strong>significance,” although criteria foridentify<strong>in</strong>g such assets have not been determ<strong>in</strong>ed. Based on follow-upconversations with IP, most removed assets were removed because <strong>the</strong>y weredeterm<strong>in</strong>ed to not exist, but <strong>in</strong> rare <strong>in</strong>stances, some assets were removedbecause <strong>the</strong>y were deemed to have negligible value. This suggests that IPrecognizes some value <strong>in</strong> elim<strong>in</strong>at<strong>in</strong>g out of place assets. We suggest that IPmore clearly def<strong>in</strong>e assets of “extreme <strong>in</strong>significance.” This <strong>in</strong>cludes assetsthat are obviously out-of-place, as were many mentioned <strong>in</strong> this review.Recommendation #1: Unresolved - OpenRecommendation #2: Provide state homeland security advisors <strong>the</strong>opportunity to (a) review <strong>the</strong>ir previously submitted assets (with <strong>the</strong>taxonomy if necessary) that <strong>the</strong>y believe fall with<strong>in</strong> <strong>the</strong> def<strong>in</strong>ition of“extremely <strong>in</strong>significant” and (b) recommend to DHS whe<strong>the</strong>r to reta<strong>in</strong><strong>the</strong>m.Preparedness concurred with our recommendation. IP <strong>in</strong>tends to provideassets ma<strong>in</strong>ta<strong>in</strong>ed with<strong>in</strong> <strong>the</strong> NADB to <strong>the</strong> respective states <strong>in</strong> <strong>the</strong> next datacall to reduce duplicate submissions. States will also have <strong>the</strong> opportunity toidentify assets that <strong>the</strong>y believe not be <strong>in</strong>cluded <strong>in</strong> <strong>the</strong> <strong>in</strong>ventory.Because IP will consider revis<strong>in</strong>g state assets <strong>in</strong> light of state concerns, wemodified our recommendation to better reflect IP’s plans. We agree that this<strong>in</strong>formation shar<strong>in</strong>g may be productive <strong>in</strong> identify<strong>in</strong>g assets that may not berelevant to <strong>the</strong> database, dependent on IP’s assessment of <strong>the</strong> assets. It isunclear whe<strong>the</strong>r IP will give <strong>the</strong> same discretion to <strong>the</strong> state <strong>in</strong> remov<strong>in</strong>gassets as <strong>in</strong> submitt<strong>in</strong>g <strong>the</strong>m. As part of its action plan, Preparedness shouldestablish standards to guide <strong>the</strong> determ<strong>in</strong>ation of assets.Recommendation #2: Resolved - Open<strong>Progress</strong> <strong>in</strong> Develop<strong>in</strong>g <strong>the</strong> <strong>National</strong> <strong>Asset</strong> <strong>Database</strong>24