Tech Support : support@biometrica.com

VP LABOR RELATIONS

Identity Intelligence Built for SMART-TD, BLET, the Boilermakers, and the Brotherhood — Not Around Them.

Major freight-rail unions have challenged monitoring technology at peer carriers through grievance, arbitration, and NLRB process. Safience is designed for that environment from the ground up: consent at onboarding for eMotive, entry-threshold-only for RTIS/RVIS, RAC human verification before any alert fires, and architecturally enforced no-automated-adverse-action. Non-match data is deleted instantly — there is no historical record of employee movement to subpoena or grieve.

eMotive (Consent-Based) RTIS/RVIS (Entry-Threshold Only) RAC Union Brief
Consent
eMotive Architecture

Express written consent at onboarding. Criminal arrest records only. Not performance. Not attendance. Not location. Not behavior.

Entry Threshold
RTIS/RVIS Deployment

Pedestrian thresholds only. Not the work floor. Not the locomotive bay. Not the dispatch console. Not the crew break room.

RAC
Human Verification

Architecturally required. No biometric match alone ever triggers an alert, much less an adverse action.

Zero
Historical Entry Record

Non-match images are deleted instantly. There is no biometric record of employee movement to subpoena, grieve, or arbitrate.

The Question Is Not Whether Monitoring Tech Will Face a Grievance. The Question Is Whether the Architecture Answers the Grievance.

You are not a buyer. You are the highest-probability deployment blocker in the Class I rail security program, and the higher the probability of CBA conflict, the more important it is that you read the architecture before procurement does. SMART Transportation, BLET, the Boilermakers, and the Brotherhood have a long, public record of challenging monitoring technology at peer carriers — through grievance, arbitration, NLRB process, and, occasionally, press response. Safience is built for the opposite posture. Two structural design facts make the deployment defensible: eMotive is consent-based at onboarding — criminal arrest records only, no performance, no attendance, no location, no behavioral monitoring — and RTIS/RVIS operates only at the facility entry threshold, not on the work floor. RAC (aankh.biometrica.com) human verification means no automated adverse action is ever triggered by a biometric match alone — architecturally enforced, not merely procedural. Non-match data is deleted instantly. For eMotive specifically: the dual face-and-name matching methodology (patented, US20240193715A1) means the monitoring system is comparing the person just booked into jail against your roster — not surveilling employees at work. The carrier-side workflow is FCRA-compliant: consent at onboarding, encrypted alert to HR only, full HR decision authority.

  1. The Surveillance-Framing Gap

    Most monitoring tech enters the environment with surveillance-framing exposure: cameras on the work floor, behavioral analytics, location tracking, performance correlation. eMotive monitors criminal arrest records only — not performance, attendance, location, or behavior. RTIS/RVIS operates at the entry threshold, not the work floor.

  2. The Automated Adverse Action Gap

    Most monitoring tech can produce an automated adverse action — a flag, a card deactivation, an alert that triggers a manager response — based on a single algorithmic match. Safience is architecturally incapable of this. RAC human verification is required before any alert fires. eMotive routes only to HR with full decision authority.

  3. The Historical Movement Record Gap

    Most monitoring tech accumulates a historical record of employee entry patterns — which becomes subpoenable in litigation, grievable in arbitration, and discoverable in NLRB process. Non-match RTIS/RVIS images are deleted instantly. No biometric record of entry patterns is ever built.

  4. The Consent Gap (eMotive)

    Most continuous-monitoring databases do not have a consent architecture designed for unionized environments. eMotive is opt-in via express written consent at onboarding. The consent is FCRA-compliant. The roster of monitored individuals is the carrier’s own — not Safience’s. The data is not exposed to anyone outside the designated HR user.

Union Compatibility Review of Safience: Step by Step

The architecture answers the grievance before the grievance is filed.

  1. Read the union brief

    We send a one-page technical brief written specifically for union review. It covers consent architecture, entry-threshold-only deployment, no automated adverse action, instant non-match deletion, and FCRA workflow for eMotive.

  2. Validate against CBA terms

    Your labor function reviews against current CBA language for monitoring, surveillance, performance evaluation, and discipline procedures. The architecture is designed to coexist with — not amend — existing CBA terms.

  3. Validate the no-automated-adverse-action guarantee

    Your labor function confirms with the architecture team that no biometric match alone ever produces an adverse action. RAC human verification is architecturally required.

  4. Brief the national union counterpart proactively

    For carriers with sensitive union relationships, we recommend proactive briefing of national union counterparts before deployment — using the same one-page brief.

  5. Deploy with documentation

    With the union brief, CBA validation, and (if appropriate) national-counterpart brief on file, deployment proceeds with documentation that anticipates and answers the grievance posture the architecture was designed for.

Typical Monitoring Technology Posture vs. Safience Union-Defensible Architecture

Capability Typical Monitoring Tech Safience Architecture
Scope of monitoring Performance, attendance, location, behavior Criminal arrest records only (eMotive); pedestrian threshold only (RTIS/RVIS)
Consent model Often implied by employment Express written consent at onboarding for eMotive
Adverse action trigger Automated alert can trigger discipline RAC human verification required; HR retains full decision authority
Work-floor surveillance Cameras, analytics, location None — entry threshold only
Historical movement record Accumulated None — non-match deleted instantly
FCRA accuracy defense Probabilistic / name-only Patented dual face + name match (US20240193715A1)
Union briefing material Not provided One-page brief written for union review
CBA reopener risk High Designed to coexist with existing CBA terms

Products for VP Labor Relations

Labor Relations is the highest-probability deployment blocker. The architecture is designed to answer the grievance posture before it forms.

eMotive Consent Architecture

Express written consent at onboarding. Criminal arrest records only. HR-only routing. No automated adverse action.

RTIS/RVIS Entry-Threshold Framing

Pedestrian thresholds only. Not work floor, locomotive bay, dispatch, or break rooms.

RAC Human Verification

Architecturally required adjudication before any alert reaches the carrier.

Instant Non-Match Deletion

No historical entry-pattern record built — nothing to subpoena, grieve, or discover in NLRB process.

Union Brief (one page)

Written for SMART-TD, BLET, Boilermakers, and Brotherhood national review.

Walk Your CBA Through the Architecture Before Procurement Does.

Request the Union Brief. We will send the one-page technical document written specifically for SMART-TD, BLET, Boilermakers, and Brotherhood review, the eMotive consent architecture documentation, the RAC human-verification guarantee, and the FCRA workflow — everything your labor function and your CBA committee will ask for.