Remote virtual FAT with traceable PLC testing and customer review
Connect test sessions, software versions, signal mapping and evidence per scenario
Our role
We designed the evidence model, session capture, build and mapping traceability, issue workflow, replay experience, and customer acceptance portal around PLC-linked twin testing.
The Problem
A virtual FAT can look convincing in a video meeting, yet the next day it may be unclear which PLC build, digital model and I/O mapping the demonstration used. When comments and faults are spread across email and spreadsheets, retesting becomes difficult to compare.
- Pass, fail, blocked, and open-issue states are not consistently tied to the exact scenario execution
- Evidence loses technical context when PLC builds, twin builds, I/O mappings, or configuration snapshots change
- Customers in different locations cannot review, comment, and accept results asynchronously in one traceable workflow
Why It Matters
FAT is not simply showing that a machine model moves. A customer needs to understand the test conditions, expected behaviour, result and remaining issues. Evidence must be linked to the exact versions and decisions behind each scenario.
- Traceability from scenario execution to build identities, mapping snapshots, and review evidence
- Visibility and closure quality of failed, blocked, and open-issue scenarios
- Readiness of customer reviewers to assess and accept results asynchronously
Our Solution
Session workspace connecting PLC-linked twin runs to named scenarios with pass, fail, blocked, and open-issue status
Execution record containing controller build, twin build, sold configuration, I/O mapping snapshot, participants, and timestamps
Replay evidence package with synchronized recordings, event traces, expected behavior, observations, and reviewer comments
Asynchronous customer review workflow for questions, issue linkage, retest evidence, approval, and acceptance history
Results
Live virtual FAT calls followed by scattered recordings, issue lists, build notes, and customer approvals
Evidence portal where each scenario, technical baseline, replay, issue, retest, and acceptance decision remains connected
- A scenario-level view of execution, status and relevant software/model versions
- Traceability from finding to issue, fix and comparable retest
- A bounded review record where customers can comment on and assess documented evidence
Project context
A machine builder conducting remote virtual FAT needed more than meeting recordings and a shared issue list. neexo connected scenario execution to controller and twin baselines, packaged replayable evidence, and created an asynchronous review and acceptance flow for project teams and customers across locations.
Deliverables
- Virtual FAT scenario portal with execution status, technical baseline, participants, and evidence records
- Replay package linking recordings, event traces, mapping snapshots, observations, and open issues
- Customer review, retest, approval, and acceptance workflow with durable traceability
Want virtual FAT evidence customers can review and accept without another live meeting?
We can help analyze your situation and identify opportunities for similar solutions.