DeActivated Components – LDARtools

What this report does

Lists every component deactivated under the selected regulation within the selected date range. Each row shows the component's tag, type, deactivation date, reason for deactivation, and the people who suggested and approved the change.

Use this report to audit component removals, verify deactivation reasons, and confirm who authorized each deactivation during a period. For the complementary list of additions, use Activated Components. This report is available directly on the Reports tab.

When to use it

Reviewing all components removed from active status under a regulation during a reporting period.
Confirming deactivation reasons (e.g., physical removal, matching, purge).
Identifying who suggested and approved each deactivation.

Parameters

Parameter	Description	Required	How it filters
Regulation	The regulation to report on	Yes	Only components mapped to this regulation appear
Unit Type	Whether to filter by Process Unit or Location Unit	Yes	Determines how units are identified in the output
Start Date	Beginning of the date window	Yes	Components deactivated on or after this date are included
End Date	End of the date window	Yes	Components deactivated on or before this date are included; expanded to end of day

All units are always shown. There is no Units selection parameter — the report covers every unit of the selected type. Filter by reviewing the Unit column in the output.

Columns

Column	What it shows	Format / Notes
Unit	The unit the component belongs to	Text; rows are grouped by unit, with a per-unit total count at the end of each group
Tag	Component tag number	Text
Type	Component type (level 1)	Text; e.g., "Valve", "Connector", "PRV"
Date DeActivated	Date the component was deactivated	Date; displayed in the component's local time zone
DeActivated Why	The reason the component was deactivated	Text; e.g., "Removed", "Matched", "Purged"
Suggestor	Person who suggested the deactivation	Text; full name
Approver	Person who approved the deactivation	Text; full name

What's included and excluded

Included:

Only components mapped to the selected regulation.
Only components whose deactivation date falls within the selected date range.
All component types.
All units of the selected type.

Excluded:

Components not mapped to the selected regulation.
Components deactivated outside the date range.
Components still active (this report shows deactivations only).

How key values are calculated

Date DeActivated

The date the component's profile changed to Deactivated (DeA), displayed in the component's local time zone.

DeActivated Why

The reason recorded when the deactivation profile change was made. Common values include:

Value	Meaning
Removed	Component was physically removed from service
Matched	Component was matched to or merged with another component record
Purged	Component was purged from the system during a data cleanup

Suggestor and Approver

For components deactivated via a MOC process, these are the people recorded on the MOC record. For components deactivated directly, they are the people recorded on the component profile change.

Tips and common questions

"Why doesn't the report let me filter to a specific unit?" The report always covers all units of the selected type. Export to Excel and filter by the Unit column to focus on a specific unit.
"A component I deactivated is not showing." Verify that the component is mapped to the selected regulation, and that the deactivation date falls within the selected date range. Components deactivated before being mapped to the regulation may not appear.
"The same component appears multiple times." If a component was deactivated more than once during the window (i.e., deactivated, reactivated, then deactivated again), each deactivation event produces its own row.
"How do the deactivation counts here compare to the Component Count Change report?" The Component Count Change report counts deactivations by the month they occurred and shows one row per unit per period. This report shows individual deactivated components with their specific deactivation dates and reasons. If you are reconciling totals, note that this report can show multiple rows for the same component if it was deactivated more than once within the date window. Count distinct component tags rather than total rows when comparing to Component Count Change.

Sample output

Report run for Example Facility, Regulation: HON, Unit Type: Location Unit, StartDate: 8/1/2024, EndDate: 8/31/2024.

What the rows illustrate:

All rows — single unit, single type, single reason: All 26 deactivations in the Crude unit are Valves deactivated under the reason "Decomissioned" — a batch deactivation event rather than individual component removals over time. This illustrates that the DeActivated Why field reflects site-configured values; "Decomissioned" is a custom reason not present in the common defaults listed in the article.
Uniform Suggestor and Approver: Every row shows George Smith as both Suggestor and Approver, indicating these deactivations were processed directly without a separate MOC approver.
Concentrated on a single date: 25 of the 26 components were deactivated on 8/1/24; one (tag 494655.5) was deactivated on 8/2/24. The one-day difference illustrates that batch deactivations entered together can still produce slightly different dates if entries span a day boundary.
Total: 26 – The per-unit count confirms all 26 deactivations fall within the August 2024 date window and are grouped under the single Crude unit section.

Output format

One row per deactivation event, grouped by unit with a per-unit total. Suitable for on-screen viewing, PDF, and Excel export.

Related reports

Activated Components — shows components added during a period; the counterpart to this report.
Reactivated Components — shows components that were deactivated and then brought back into service.
Component Count Change — summarizes net population changes (additions, deactivations, beginning and ending counts) at the unit level.