Validation Tester // Configuration + Monitoring
Validation Tester
Rivian builds electric adventure vehicles. They are designed to drive on uneven terrain which requires significant testing before the product goes to market.
Building an efficient test system can be challenging and time-consuming. The Rivian validation tester I designed is an easy-to-use system building tool for setting up test systems from scratch.
My design makes configuration intuitive without having to sift through code.
Rivian builds electric adventure vehicles. They are designed to drive on uneven terrain which requires significant testing before the product goes to market.
Building an efficient test system can be challenging and time-consuming. The Rivian validation tester I designed is an easy-to-use system building tool for setting up test systems from scratch.
My design makes configuration intuitive without having to sift through code.
Rivian builds electric adventure vehicles. They are designed to drive on uneven terrain which requires significant testing before the product goes to market.
Building an efficient test system can be challenging and time-consuming. The Rivian validation tester I designed is an easy-to-use system building tool for setting up test systems from scratch.
My design makes configuration intuitive without having to sift through code.
Context
Context
Rivian, Electrical Hardware Team, August 2022
Rivian, Electrical Hardware Team, August 2022
Role
Role
Design Lead, Front-end Development
Design Lead, Front-end Development
Execution
Execution
Prototypes built in Figma, desktop app built with LabVIEW, web app built with HTML/CSS
Prototypes built in Figma, desktop app built with LabVIEW, web app built with HTML/CSS
JSON Config: This JSON template is what engineers used to use to build and configure their systems.
JSON Config: This JSON template is what engineers used to use to build and configure their systems.
JSON Config: This JSON template is what engineers used to use to build and configure their systems.
Designing for specific users:
Designing for specific users:
Designing for specific users:
System Developer
System Developer
Engineers, high system knowledge
Engineers, high system knowledge
Validation Tester
Validation Tester
Tests ECUs, low knowledge/training
Tests ECUs, low training
Tests ECUs, low training
The limitations of building systems through JSON templates was prohibiting validation testers from being able to test Electronic Control Units (ECUs) independently.
Without visualizing the system configuration, only system developers were able to test ECUs.
By allowing validation testers and system developers to build and configure a test system, we cut back on training required to operate a test.
The limitations of building systems through JSON templates was prohibiting validation testers from being able to test Electronic Control Units (ECUs) independently.
Without visualizing the system configuration, only system developers were able to test ECUs.
By allowing validation testers and system developers to build and configure a test system, we cut back on training required to operate a test.
The limitations of building systems through JSON templates was prohibiting validation testers from being able to test Electronic Control Units (ECUs) independently.
Without visualizing the system configuration, only system developers were able to test ECUs.
By allowing validation testers and system developers to build and configure a test system, we cut back on training required to operate a test.
Visual System Tree: This no-code interface offers the same config options as the JSON editor. Not the full prototype, but try out the scrollable instrument pane!
Visual System Tree: This no-code interface offers the same config options as the JSON editor. Not the full prototype, but try out the scrollable instrument pane!
Visual System Tree: This no-code interface offers the same config options as the JSON editor. Not the full prototype, but try out the scrollable instrument pane!
Building a testing interface as complex as this without limiting the configuration options comes with a few key design challenges.
Building a testing interface as complex as this without limiting the configuration options comes with a few key design challenges.
Building a testing interface as complex as this without limiting the configuration options comes with a few key design challenges.
Data Heaviness: There is too much information to display on screen
Solutions:
Collaborated with engineers to indentify the must-show data
Allowed deeper inspection with expanding and collapsing cards
Scrollable content where necessary
LabVIEW Constraints: Not all languages have the same design capabilities
Solutions:
Incorporated atomic design principles for dynamic scaling
Built using developer best practices for smooth hand off to engineers
Established parity with codebase
Remote Test Monitoring: Validation testers needed the ability to check in on multi-day tests.
Remote Test Monitoring: Validation testers needed the ability to check in on multi-day tests.
Remote Test Monitoring: Validation testers needed the ability to check in on multi-day tests.
In collaboration with engineers and validation testers I selected key test components to display on a mobile dashboard. This monitoring tool was not meant to replace the validation tester, rather to increase the operators flexibility in how and where they perform tests.
In collaboration with engineers and validation testers I selected key test components to display on a mobile dashboard. This monitoring tool was not meant to replace the validation tester, rather to increase the operators flexibility in how and where they perform tests.
In collaboration with engineers and validation testers I selected key test components to display on a mobile dashboard. This monitoring tool was not meant to replace the validation tester, rather to increase the operators flexibility in how and where they perform tests.
My approach to designing the validation tester was not limited by it’s constraints, but highlighted my skillset and flexibility. I built and delivered solutions that made the testers job as easy as possible while improving functionality.
My approach to designing the validation tester was not limited by it’s constraints, but highlighted my skillset and flexibility. I built and delivered solutions that made the testers job as easy as possible while improving functionality.
My approach to designing the validation tester was not limited by it’s constraints, but highlighted my skillset and flexibility. I built and delivered solutions that made the testers job as easy as possible while improving functionality.
Data Heaviness: There is too much information to display on screen
Solutions:
Collaborated with engineers to indentify the must-show data
Allowed deeper inspection with expanding and collapsing cards
Scrollable content where necessary
Data Heaviness: There is too much information to display on screen
Solutions:
Collaborated with engineers to indentify the must-show data
Allowed deeper inspection with expanding and collapsing cards
Scrollable content where necessary
LabVIEW Constraints: Not all languages have the same design capabilities
Solutions:
Incorporated atomic design principles for dynamic scaling
Built using developer best practices for smooth hand off to engineers
Established parity with codebase
LabVIEW Constraints: Not all languages have the same design capabilities
Solutions:
Incorporated atomic design principles for dynamic scaling
Built using developer best practices for smooth hand off to engineers
Established parity with codebase
Validation Tester
Validation Tester