Sustainability & Risk/ Health & Safety / Management Reports

Incidents Count report

With this report, you can generate a bar graph report that shows a count of incidents (on the Y axis) according to various criteria, including by type, by type over time, by site, by property, or by building (on the X axis). You can further filter this data by date range, injury category, affected employee, and other criteria.

To run the Incident Count report:

1. In the filter, complete the Group By option to determine if you want to report on incidents by:

• Incident Type
• Incident Type Over Time
• Site
• Property
• Business Unit
• Division
• Department

2. Incident count data is often more meaningful when analyzed in terms of the number of employees or size of the building. For example, if two buildings have roughly the same number of incidents but one building houses double the number of employees, you may want to check as to why the building with fewer employees has so many incidents. To break down your data by building size or number of employees:

• If you completed Group By with a value other than Business Unit, Division, or Department, you can now optionally complete the Divide Totals By option with Headcount or Unit Area.
• The system divides the number of incidents by the building's area, then multiplies by 1000 to provide a more readable output, since the number of incidents will hopefully always be proportionally much less than the number of square feet or meters of a building's area. For example, if Building HQ has 30 incidents and if building HQ is 200,000 feet, the bar graph will show .15 ; that is (30/200,000)x1000.
• Similarly, if building HQ with 30 incidents houses 600 employees and you use the headcount option, the bar graph will show .05 for building HQ : that is, (30/600).

3. Complete any additional criteria by which you want to filter and click Show.
4. In the bottom pane, the system presents a bar graph of the incident count per your selected Group By option (building, property, incident type, etc).

• If you group by business unit, division, or department, the system presents an additional bar for Non-Employees. This bar includes incidents for which the incident reporter either chose a value for Affected Non-Employee Contact (a person in the Contacts table) or typed in a value in Non-Employee Name; that is to say, the incident is not associated with a specific department, division, or building unit because the involved party is not a company employee.
• If you chose "Incident Type over Time", the report presents a bar graph set for each month for which incident data exists. You can further refine this bar set by setting a specific date range using the Incident Date From and Incident Date to options in the filter console.

5. You can click on any bar in the report to access a pop-up window listing the specific incidents contributing to the bar's data.
6. From this list of incidents, you can click on a particular incident to access its details, including resolution, witnesses, resulting required training, and resulting work restrictions. You can also generate the OSHA Accident Report (Form 301) from the incident details.
7. To see a list of all incidents (not just those contributing to a specific bar in the chart), choose the All Details button in the report's upper right corner. From here, you can click on an incident to see its particular details and generate the OSHA Accident Report (Form 301) report.

Parent and Child Incidents

This report does not intend to convey the total count of incidents across all locations and categories as much as it intends to show the number of incidents that affected any given location, organizational unit, etc. The report does not double-count parent and child incidents within the same grouping. However, the report does count the same incident once for each group if multiple incident records with the same parent_incident_id are split between the different chart groups. This is as designed; if the report were to exclude child incidents in all cases and an incident did affect multiple people in multiple buildings simultaneously, querying incidents at any one of the buildings might not show the expected results. For example, if an incident affected buildings A, B, and C, with the 'parent' incident record associated with building A, you might filter show to only buildings B and C and not see record of the event's effects on those buildings.

When you click a chart bar to see detailed records, you may observe cases where there is a Grouped Incident Code with no matching Incident Codes. This would indicate that the incident spans multiple chart groups and therefore may affect the count displayed in more than one bar, even though the counts stem from a single incident.

Calculations

The following explains how the headcount and area values are calculated for some of the “Group by” options.

Since there is typically a small number of incidents and big numbers for the areas, the report normalizes the value by multiplying by 0.001.

Incidents Count Group by Building:

- Area: use value of bl.area_gross_int for the division
- Headcount:
SELECT count(em.em_id) FROM em where em.bl_id = ehs_incidents.bl_id
if is not zero, else:
SELECT bl.count_em FROM bl WHERE bl.bl_id = ehs_incidents.bl_id
if bl.count_em is also zero AND count of incidents >=1, then return 1 as the final result for the building; but if number of incidents = 0 then the result is 0

Incidents Count Group by Property:

- Area: use value of property.area_bl_gross_int for the division.
- Headcount:
SELECT count(em.em_id) FROM em WHERE em.bl_id = bl.bl_id AND bl.pr_id = ehs_incidents.pr_id
if is not zero, else:
SELECT SUM(bl.count_em) FROM bl WHERE bl.pr_id =
ehs_incidents.pr_id
Same comments as above regarding 0 or 1 as final result for the grouping (normalized) value.

Incidents Count Group by Site:

- Area: use value of site.area_gros_int for the division.
- Headcount:
SELECT count(em.em_id) FROM em, bl WHERE em.bl_id = bl.bl_id AND bl.site_id = ehs_incidents.site_id
if is not zero, else:
SELECT SUM(bl.count_em) FROM bl WHERE bl.site_id = ehs_incidents.site_id
Same comments as above regarding 0 or 1 as final result for the grouping (normalized) value.

Other Notes

If a user queries incidents by property, then selects to normalize by headcount, and if both values are non-zero, the system uses:

total number of incidents both for employees and non-employees together associated with the property & its buildings/
total number of employees, (that is, headcount for all buildings on that property)