Timestamp Accuracy

Regina,

To follow-up on the “time-stamp accuracy.”

The “time-stamps” are designed to accurate within 8 seconds of detection.

We can set the badges to be accurate within 1 seconds of detection, but this will decrease the battery life to about 6 months.

We set the badges to be accurate within 8-seconds of detection as the default because this:

1. increases the badges battery life to about 12 months; and
2. accuracy within 8-seconds is usually precise enough for most customer use cases.

The two primary drivers of “time-stamp accuracy” are: (1) badge deployment and (2) equipment deployment.

1. Badge deployment:
   1. Are people wearing their badges?
      1. We can have Sitemetric Field Support onsite for 30-days to help cultivate should help address this on Project Abby—typically it is just a matter of building, encouraging, and cultivating
2. Are people leaving their badges onsite (i.e., stationary badges)?
   1. To address the Stationary Badges we can actively monitor and coordinate with appropriate Clayco people onsite.
   2. Our system automatically flags and reports the “stationary badges”
   3. To address this, we ca
3. Are badges working properly (e.g., badge renewals)?
   1. To better address this, Sitemetric can continue monitoring
4. Equipment deployment:
   1. Is there adequate detection coverage to detect workers within 8-seconds at the site entry/exits gates?
      1. Our initial deployment on Project Abby was designed assuming the nurses were verifying people entering the site. With the transition away from nurses at the main site entrance, vehicles will be passing through at a higher speed.
      2. To address this we can deploy additional detection equipment at the site entrances, parking areas, cross walk, and other activity areas to address this.
5. Is detection coverage appropriate given evolving project needs and conditions?
   1. Project needs and conditions are constantly evolving, typically
6. Does the detection equipment have consistent and reliable power?
   1. We hae

More notes from Patrick

For addressing the time stamp accuracy issue I recommend the following.

What specific time stamp issue are they referring to so we can properly address it?

Our data collection focuses around 3 priorities.

1. Accurate head count.

1. Time on site

1. Location

To achieve stop clock type time accuracy a control point and scanner is required. Without a control point and scanner, detections can vary a few minutes based on the way a user carries their badge and the detection zones they enter. The system is designed to collect data and provide documentation to create patterns and trends. Consistency of attendance, consistency of time on site, and area of most or last detected. This data is used to identify safety issues, contract commitment issues, work area activity.

To address specific time stamp issues a visual inspection of the badge on site is required. Historically, we have notice more time stamp issues with those who are not wearing their badge around the site. Left on desk, in car, or in pocket or under vest against a phone or electronic device. These users are added to the head count but could experience latency detections. In cases where there could be a latency issue it is best too look at a pattern of days of detections to identify a possible interference issue. Most of the focus is typically on the head count unless there is a situation on a particular trade. Then time on site becomes a focus and it is on all the workers of a particular trade not just a particular worker. The intention is to Identify Performance issues not Payroll. We will verify time stamps durning the proof of performance activities in up coming weeks.