Halliburton · RWC Controls Pricing

Meeting Summary

The pricing approach must preserve training realism while making hardware, software integration, and fabrication assumptions explicit.

Primary direction

Prioritize an exact, one-to-one physical control layout. A desktop/tabletop console is the current baseline; a suitcase form factor is a useful enhancement, not the core requirement.

Pricing Structure

Build tiered options around generic commercial controls, direct OEM-style implementation, and a premium portable configuration.
Base pricing on a verified control inventory, part numbers, manufacturing differences, and integration effort per control type.

Schedule & Risk

Unity upgrades and the newer input system add baseline software work before control-specific integration.
The team discussed a 20-month planning horizon and at least three consoles, making early design approval critical.

Separate R&D

Bluetooth-enabled controls could improve portability and reduce dependence on a dedicated PC.
This is an unfunded research path and should remain outside the current Halliburton scope unless separately approved.

Immediate Actions

Rachel: mark physical versus virtual controls, assemble open questions, and obtain parts and effort estimates.
Devin: validate layouts and produce concept images using high-resolution console references.
Adam: align scope, pricing assumptions, and follow-up once technical inputs are complete.