Skip to main content

Sensor Engagement Pack™

Overview​

Sensor Engagement Pack™ (EGP) is the standard delivery object established by Atlas Runtime Governance™ for investigation collaboration between OEM and Sensor Manufacturer.

When OEM Runtime Investigation determines that an incident may involve a certain Sensor (investigation object candidate / Sensor Candidate), the OEM can generate a Sensor Engagement Pack and send it to the corresponding Sensor FAE (Field Application Engineer).

The goal of EGP is not to regenerate evidence, but to help Sensor FAE quickly understand the investigation background and conduct Sensor Investigation within their own knowledge domain.

Why Sensor Engagement Pack?

Robot runtime incidents typically involve multiple organizations.

For example:

  • OEM
  • Camera Manufacturer
  • LiDAR Manufacturer
  • IMU Manufacturer

OEM already has its own Runtime Investigation.

However, Sensor Manufacturer cannot directly access the OEM's internal investigation system.

Sensor Engagement Pack provides a standard collaboration interface, enabling both parties to share investigation context without sharing the entire internal system.

OEM ↔ Sensor Investigation Workflow

OEM Runtime REF

        │

        ▼

OEM Runtime Investigation

        │

        ▼

OEM REF Ticket
(Status: Pending Sensor Investigation)

        │

        ▼

Generate Sensor Engagement Pack

        │

        ▼

Sensor Manufacturer

        │

        ▼

Create Sensor REF Ticket

        │

        ▼

Sensor Investigation

        │

        ▼

Sensor RGA (IR + LL)

        │

        ▼

Sensor REF Ticket Closed

        │

        ▼

Return Sensor Response

        │

        ▼

OEM Investigation Continues

        │

        ▼

OEM REF Ticket Closed

OEM and Sensor Manufacturer each maintain their own Investigation Workflow.

Both parties establish collaboration through Sensor Engagement Pack.

Investigation Ownership

Throughout the investigation process, both parties maintain independent investigation authority.

OEM is responsible for:

  • OEM REF Ticket
  • Runtime Evidence Pack
  • Runtime Investigation
  • Historical OEM RGA (IR + LL)
  • OEM Ticket Closure

Sensor Manufacturer is responsible for:

  • Sensor REF Ticket
  • Sensor Investigation
  • Sensor Historical RGA (IR + LL)
  • Sensor Ticket Closure

Neither party modifies the other party's investigation records.

Sensor Engagement Pack Architecture

OEM Investigation
        │
        ▼
Sensor Engagement Pack
        │
        ▼
Sensor Investigation

EGP is an exchange object for investigation context.

Not a new Evidence Pack.

What Does a Sensor Engagement Pack Contain?

A standard EGP can contain:

Sensor Engagement Pack
│
├── OEM REF Information
├── Investigation Context
├── Evidence Pack References
├── Runtime Surface Scope
├── Historical Recall Summary
├── Investigation Questions
├── Requested Sensor Scope
└── Collaboration Metadata

EGP does not duplicate Runtime Dataset.

All Runtime Evidence is referenced through Evidence Pack Reference.

OEM REF Information

EGP can include:

  • REF Identifier
  • Incident Summary
  • Incident Time
  • Deployment Environment
  • Incident Type
  • Severity

Helps Sensor FAE quickly establish investigation background.

Investigation Context

EGP references the current Investigation Context.

Including:

  • Runtime Timeline
  • Runtime Surface Coverage
  • Historical Recall
  • Investigation Notes

Sensor FAE can directly conduct investigation based on Context.

Evidence Pack References

EGP references the Evidence Pack already generated by OEM.

Sensor Engagement Pack
        │
        ▼
Primary Evidence Pack

Sensor FAE does not need to regenerate Evidence Pack.

All investigations are based on the same Runtime Evidence.

Runtime Surface Scope

OEM can clearly specify the scope that Sensor FAE should investigate this time.

For example:

  • Camera Runtime
  • LiDAR Runtime
  • IMU Runtime
  • Driver Runtime
  • Sensor Communication

Scope is used to focus investigation.

Historical Recall Summary

OEM can provide a summary of the current Historical Recall.

For example:

  • Similar Runtime Pattern
  • Previous Investigation
  • Similar Runtime Behaviour

Helps Sensor FAE determine if similar historical experience exists.

Investigation Questions

OEM can raise questions that need Sensor FAE assistance to answer.

For example:

  • Does it belong to a known Sensor Runtime Pattern?
  • Is it recommended to check Firmware?
  • Is it recommended to further collect Runtime Observation?

Questions are used to guide collaboration between both parties.

Requested Sensor Scope

OEM can clarify the scope of this collaboration.

For example:

  • Runtime Behaviour Review
  • Driver Review
  • Interface Review
  • Firmware Review

EGP does not require Sensor Manufacturer to investigate the entire robot system.

Sensor Investigation

After receiving EGP, Sensor Manufacturer establishes its own Sensor REF Ticket.

Sensor Engagement Pack
        │
        ▼
Sensor REF Ticket
        │
        ▼
Sensor Historical Recall
        │
        ▼
Sensor Investigation

Sensor Investigation can reference:

  • Sensor Historical RGA
  • Sensor Runtime Experience
  • Sensor Deployment Knowledge

But does not modify OEM Investigation.

Sensor Response

After Sensor Investigation is completed, standard investigation results can be formed.

For example:

Sensor Investigation Result (IR)

Lesson Learned (LL)

Recommended Actions

Response Summary

These results are returned to OEM.

For OEM Runtime Investigation to continue using.

Ticket Closure

Sensor Manufacturer and OEM close their respective Tickets separately.

Sensor REF Ticket

↓

Closed

↓

OEM REF Ticket

↓

Closed

Sensor Ticket Closure does not automatically close OEM REF.

OEM decides final Closure based on complete investigation results.

Collaboration Boundary

Sensor Engagement Pack is only used for investigation collaboration.

Atlas does not require:

  • Sharing complete Runtime Dataset
  • Sharing Historical Repository
  • Sharing internal investigation system

Both parties only share information needed to complete investigation.

Design Principles

Sensor Engagement Pack follows these principles:

  • OEM and Sensor maintain independent investigation processes
  • One OEM REF can correspond to multiple Sensor REFs
  • EGP references existing Evidence Pack, does not generate new Evidence
  • Sensor Investigation uses its own Historical RGA
  • OEM Investigation uses its own Historical RGA
  • Both parties close their respective Investigation Tickets separately
  • OEM ultimately decides OEM REF Ticket Closure
  • Respect data and intellectual property boundaries of both parties

Sensor Engagement Pack vs Evidence Pack

Evidence Pack preserves:

  • Runtime Evidence
  • Runtime Timeline
  • Runtime Dataset References

Sensor Engagement Pack preserves:

  • Investigation Context
  • Collaboration Scope
  • Evidence References
  • Investigation Questions

Evidence Pack is runtime evidence.

Sensor Engagement Pack is the investigation collaboration object between OEM and Sensor.

Summary

Sensor Engagement Pack™ is the standard Runtime Investigation collaboration object between OEM and Sensor Manufacturer.

It references the Investigation Context and Evidence Pack already established by OEM, transmitting investigation background, collaboration scope, and questions to Sensor FAE. Sensor Manufacturer creates Sensor REF Ticket within its own knowledge domain, completes Sensor Investigation, and returns IR, LL, and investigation recommendations. Both parties separately maintain their respective investigation processes and Historical RGA, ultimately with OEM completing the entire Runtime REF's closed-loop investigation and Ticket Closure.

Next Reading

  • Assist Vault™
  • CTO Runtime Governance Dashboard™