Person to Person Export Definitions

Knowledge Base > Products > Software > Loop Cloud > Loop Cloud Export Guides > Person to Person Export Definitions

Person to Person Summary Definitions

Date From

Starting Date for the range requested in Loop Cloud.

Date To

Ending Date for the range requested in Loop Cloud.

Primary Contact

The Person/ID whose data follows in the rest of the cells. Each person with any events in the selected date range should show up in the .csv once.

Type

Type of Event: Person for Person to Person events.

Nearby Total Duration (s)

Total duration of Nearby events for this Person/ID during the selected date range.

Nearby Total Contacts

Total count of Nearby events for this Person/ID during the selected date range.

Nearby Total Unique Contacts

Total count of “unique” other Persons/IDs for Nearby events during the selected date range. “Unique” is only going to count each individual a single time, regardless of how many events they share with the Primary Contact.

Contact Total Duration (s)

Total duration of Contact events for this Person/ID during the selected date range.

Contact Total Contacts

Total count of Contact events for this Person/ID during the selected date range.

Contact Total Unique Contacts

Total count of “unique” other Persons/IDs for Contact events during the selected date range. “Unique” is only going to count each individual a single time, regardless of how many events they share with the Primary Contact.

Person to Person Log Definitions

Primary Contact

The Person/ID/Tag whose data follows in the rest of the cells. Each row is a single event, so a Person/ID can show up multiple times.

Primary Contact Type

Type of topology set up in the system: Person for Person to Person events.

Primary Contact Description

Currently an unused field.

Primary Contact Tag

The MAC address of the SafetyTag associated with the Primary Contact. This is found beneath the QR code on the front of the Tag.

Secondary Contact

The Person/ID who was a part of the event with the Primary Contact.

Secondary Contact Type

Type of topology set up in the system: Person for Person to Person events.

Secondary Contact Description

Currently an unused field.

Secondary Contact Tag

The MAC address of the SafetyTag associated with the Secondary Contact. This is found beneath the QR code on the front of the Tag.

Start

The start time of the Nearby/Contact event.

End

The end time of the Nearby/Contact event.

Duration (s)

Total duration (in seconds) of the Nearby/Contact event.

Proximity

Type of event: Nearby or Contact

Boundary (m)

Predefined range (in meters) that triggers a particular event type, i.e., how close tags need to get to each other to trigger each event type. This is commonly set to 1.83 meters for Contact and 3 meters for Nearby.

Closest Distance (m)

The closest distance the two tags were to one another (in meters) during their Nearby/Contact event.

Timed Out – [Yes/No]

Did the event close because it timed out? Typically tags intentionally close an event because they exceed the boundary distance. Sometimes events stop because tags lose connection with each other, closing the event via a time out.

On Charge – [Yes/No]

Did the event close because the tag was put on a charger? If tags are actively engaged in an event and one goes on charge, the event will stop and this field will be flagged for that event.

Timesync Issue – [Yes/No]

Were there any time synchronization issues between the tags?

Duplicate – [Yes/No]

Is this a duplicate event? Both tags will create events and Loop Cloud will recognize when the 2nd upload of the same event happens, so it does not double up on the duration of events. This will primarily be why some lines in the logs will be greyed out in Loop Cloud.

Stereotype

Currently an unused field.

Reported By Primary – [Yes/No]

Indicates whether or not the event was uploaded by the Primary Contact or created by the Secondary Contact during their offload.

Timestamp Conflict

This field is flagged as true or false depending on whether the two pairs of events that get offloaded and created by each tag for a given event have the same timestamp.

Offload ProxPoint

MAC address of the ProxPoint that offloaded the event.

Processing Delay (s)

Time it took for the event offload to be processed.

 

Navigation