Rukon
Back to Project Overview
Full Case StudySystems / ERP / WMS NDA-Safe Architecture

BBTech Laptop Tool

BBTech Laptop Tool: Portable Hardware QC, SMBIOS Identity & Refurbishment Audit Utility

BBTech Laptop Tool mark
Role
Sole Developer
Affiliation / Client
Blue Bee Technologies Sdn. Bhd.
Timeline
2025 - 2026
Documentation Level
5 Engineering Sections

Operational Workflow & State Machine

End-to-End Pipeline
  1. 01Plug USB on incoming refurbished laptop and launch single self-contained executable
  2. 02Utility queries Win32 WMI and SMBIOS to retrieve BIOS serial, motherboard UUID, CPU, memory, and drive health
  3. 03Technician exercises interactive QC checklist: display test, keyboard matrix, webcam, audio, ports, and battery test
  4. 04Generates verified QC report, signs encrypted local log, and formats payload for ITMS inventory ingestion
01

The Refurbishment Challenge

Refurbishment technicians previously had to manually transcribe processor tiers, memory capacities, battery wear percentages, and serial numbers into inventory forms. Human error led to mismatched stock codes, mislabeled specifications, and an inability to detect when an identical physical laptop returned to the facility after a warranty claim.

Furthermore, standard Windows settings screens frequently mask critical hardware limitations: dynamic turbo clocks disguise baseline frequencies, and software-level asset tags are wiped clean whenever a drive is reformatted.

BBTech Laptop Tool was engineered as a zero-install, single-file Windows executable (.NET 8 WPF) run directly from a technician's USB drive to automate hardware profiling and enforce an immutable quality-control audit trail.

02

Hardware Identity Engineering

Rather than trusting user-editable Windows machine names or generated asset tags, the tool queries low-level Win32 WMI providers and raw SMBIOS tables to retrieve the manufacturer's immutable hardware identity: BIOS serial number (Win32_BIOS.SerialNumber), baseboard serial number (Win32_BaseBoard.SerialNumber), and system UUID (Win32_ComputerSystemProduct.UUID).

If a motherboard manufacturer populated generic placeholder strings (such as 'Default string', 'None', or 'To be filled by O.E.M.'), the engine activates heuristic fallback trees incorporating network adapter permanent MAC addresses (Win32_NetworkAdapter.MACAddress) and storage controller device IDs to guarantee deterministic machine identification across refurb cycles.

03

Interactive QC Testing Workflow

Beyond passive hardware inspection, the tool guides technicians through an interactive quality-control sequence before approving a unit for packaging:

1. Display Matrix: Cycles full-screen RGB and white/black solid fills to expose stuck pixels, backlight bleeding, and IPS pressure marks.

2. Keyboard Matrix: Uses raw Win32 input hooks to track individual key depress and release cycles in an interactive visual layout, identifying dead keys and ghosting.

3. Battery Health & Degradation: Queries Win32_Battery to compare DesignCapacity against FullChargeCapacity, calculating wear percentages and alerting if health falls below the refurbishment threshold (typically 80%).

4. Audio & Ports: Executes loopback audio tone verification and active USB port enumeration.

04

Encrypted On-Device Journal

To provide tamper-evident records independent of live network availability, each machine writes an append-only cryptographic JSON journal stored in C:\ProgramData\BBTech\LaptopTool\. Payloads are protected using Windows DPAPI (ProtectedData.Protect scoped to DataProtectionScope.LocalMachine).

When a machine is re-scanned months later, the tool immediately detects previous refurbishment cycles, battery degradation rates, and historical technician sign-offs, preventing fraudulent warranty claims or repeated unresolved defects.

05

Testing and Verification

The codebase includes 685 automated xUnit tests validating WMI fallback parsers, display aspect ratio calculations, keyboard matrix hit testing, battery wear calculations, and cryptographic payload serialization.

Automated tests verify that every known OEM placeholder string properly triggers the UUID and MAC fallback hierarchy, ensuring 100% deterministic device fingerprinting even on stripped or customized firmware.

What's live, and what isn't

“It exists in the repository” and “it runs in production” are different claims. This is the difference, stated rather than left to be assumed.

  • ImplementedHardware extraction engine (BIOS, Motherboard, RAM, Battery)Direct WMI query layer with fallback heuristics for OEM-specific tables.
  • ImplementedWPF GUI & Technician QC WorkflowInteractive testing screens for display, keyboard, audio, and battery wear.
  • ImplementedEncrypted on-device audit journalAppend-only encrypted local storage preserving full refurbishment history.
  • ImplementedAutomated xUnit test suite685 passing unit tests validating hardware models, validators, and crypto storage.
  • Built, not liveDirect ITMS API transport connectorLocal payload format complete; live network transport toggle disabled in bench build pending token provisioning.

Technical stack

Application & UI

C#.NET 8WPFMVVM PatternCommunityToolkit.Mvvm

Hardware Abstraction

Win32_BaseBoardWin32_BIOSWin32_DiskDriveWin32_BatterySMBIOS UUID

Security & Storage

Protected on-device JSON journalDPAPI / AES encryptionSystem.Text.Json

Testing & Quality

xUnitFluentAssertionsMoq685 unit tests

Limitations

  • Designed specifically for Windows 10/11 x64 systems; does not run on Linux or macOS.
  • Certain white-label generic motherboards report placeholder serials ('To be filled by O.E.M.'), triggering MAC/UUID fallback.
  • Direct ITMS cloud sync toggle currently set to local export pending floor network authorization.
  • Local working tree contains 29 modified and 7 untracked files in progress.

What's next

  1. 01Automated barcode label print generation via RPOMS Print Engine relay
  2. 02Direct ITMS OAuth2 automated upload connector
  3. 03Integrated battery discharge load curve benchmark

Source and further reading

Built for Blue Bee Technologies refurbishment operations. System architecture and test metrics are reported; proprietary operational endpoints and technician keys are omitted.

Finished the technical breakdown?

Return to the concise HR overview or discover other projects in the portfolio.