Skip to content

Office Address

1301, Building B, Smart Valley, Country Garden, No. 50, Tiezai Road, Xixiang Street, Bao'an District, Shenzhen, CN

Phone Number

+8613686469587

Email Address

[email protected]

Original Design & Development

From a Product Brief to a Production Line

When an off-the-shelf box is not enough, DataMax engineering designs the hardware and firmware with you — then builds it on our own lines. Six stage gates, signed-off deliverables and IP terms agreed before a single tool is cut.

The development path

Six Gates Between an Idea and a Shippable Product

Each gate has named outputs and one explicit sign-off criterion. Spend never starts before the gate that authorises it.

  1. G0

    Concept & feasibility

    We turn the use-case, target market and feature list into an engineering assessment: platform options, architecture, risk register and whether existing tooling can be reused.

    • Feasibility assessment
    • Platform & architecture options
    • Rough cost structure
    Gate sign-off

    Scope and architecture direction agreed in writing.

  2. G1

    Architecture & BOM lock

    SoC, memory, tuner, connectivity, ports and power architecture are selected, and the bill of materials is frozen with change-controlled substitution rules.

    • Frozen BOM
    • Block diagram & interface map
    • Project & tooling plan
    Gate sign-off

    BOM and specification signed off before tooling spend.

  3. G2

    Engineering verification (EVT)

    Engineering builds verify function, signal integrity, thermal behaviour and power on prototype boards, with firmware brought up on the target hardware branch.

    • EVT prototype units
    • Thermal & power verification
    • Base firmware image
    Gate sign-off

    Core functions verified against the specification.

  4. G3

    Design verification (DVT)

    Tooled units run through reliability, ageing and environmental checks, and the enclosure, cosmetics and packaging design are validated for production.

    • Tooled DVT units
    • Reliability & ageing report
    • Cosmetic & packaging design
    Gate sign-off

    Design is stable, repeatable and manufacturing-ready.

  5. G4

    Pilot run (PVT)

    A first production lot validates fixtures, line balance, test stations and the firmware branch end to end, and produces the golden sample for sign-off.

    • Pilot lot on production tooling
    • Line & test-station validation
    • Golden sample
    Gate sign-off

    Golden sample approved; yield meets the agreed bar.

  6. G5

    Mass production & lifecycle

    Volume production runs under IQC, IPQC, ageing, FQC and OQC, followed by managed OTA, spare-board stock and change-controlled component transitions.

    • Mass production releases
    • OTA & firmware support
    • Spares continuity plan
    Gate sign-off

    Ongoing quality gates applied to every batch.

Why hardware projects fail — and where the gates come from

The Five Failures the Stage-Gate Process Exists to Prevent

Most failed hardware programmes do not fail at soldering. They fail at decisions: a feature added after the design was frozen, moulds cut before the architecture settled, a radio certification discovered after the pilot run, a thermal margin nobody measured, or an ownership question nobody wrote down. The G0–G5 process is not ceremony imported from a large-customer audit — every gate blocks one of those specific failures.

The commercial effect is predictable spend. Engineering, tooling and certification costs are committed only at the gate that authorises them, which is why an ODM project can be paused or stopped between gates with work handed over rather than sunk. It is also why the G0 assessment pushes hard on destination markets and content security early: choices about radio bands, DRM/CAS and operator middleware change the board, and re-opening them after EVT is where schedules collapse.

Not every enquiry needs the full gate path. When the platform already fits and only branding changes, OEM or private label skip the hardware gates entirely — the Android TV box OEM track is the common example, since qualified streaming platforms rarely need new board development; when the hardware is settled and only software must change, custom firmware development runs on a named branch without NPI at all.

  • Requirement drift

    “One more feature” arrives after G1

    Scope added after the BOM lock cascades into board, thermal and certification work. The gates freeze scope deliberately; every change request gets a written impact assessment instead of a silent yes.

  • Tooling before lock

    Moulds cut on an unfrozen design

    Tooling spend begins only after G1 sign-off. Rushing moulds before the architecture is frozen is the single most expensive NPI mistake — it is paid for twice.

  • Late compliance discovery

    Certification treated as end-of-project paperwork

    Radio bands, market approvals and DRM/CAS qualification can change the hardware. They enter at G0 and are built into EVT builds rather than bolted on after DVT.

  • Thermal surprises

    Heat problems discovered in the field

    Small enclosures, sealed optics and 24/7 duty are verified thermally at EVT under real workloads, so a cooling redesign never happens in a customer’s installation.

  • IP ambiguity

    Ownership questioned after the product ships

    Background IP, exclusivity, territories and open-source obligations are allocated at G1 — before engineering starts — so the contract is never reconstructed from a shipped product.

Engineering in-house

Hardware, Firmware and Integration Under One Roof

Hardware engineering

  • Block-diagram and circuit design on Rockchip, Amlogic and Allwinner platforms
  • Memory, tuner, connectivity and power architecture selection
  • Thermal, signal-integrity and power verification
  • ID review, tooling coordination and enclosure qualification

Firmware engineering

  • AOSP board bring-up, kernel and device-tree work
  • Custom launcher, system UI, kiosk mode and provisioning
  • Private APIs and middleware integration
  • OTA channel, firmware branching and release management

Integration & compliance

  • DRM/CAS and operator middleware integration
  • Remote, HDMI-CEC, AV-over-IP and peripheral integration
  • Destination configuration for FCC-class, CE/RED-class and regional schemes
  • Test packs and documentation for laboratory qualification
Your IP

What stays with the brand owner

  • Your brand, trademarks and supplied creative assets
  • Your use-case definition, content roadmap and operator requirements
  • Custom configurations, layouts and provisioning rules made for you
  • Usage and update rights defined in the project contract
Platform & licensed IP

How background and third-party IP is handled

  • Underlying AOSP and third-party code remains with its rights holders
  • DataMax platform IP, reference designs and tooling know-how stay ours
  • Your exclusive scope and territories are stated per project
  • Open-source obligations and source terms are documented, not implied

Exclusivity, territories and update rights are project-specific contract terms, agreed at G1.

Choosing the engagement model

OEM, ODM, Private Label and Custom Firmware in One Table

All four routes share the same factory, quality system and fixed-BOM discipline — they differ in how much of the product is created for the programme.

  OEM ODM Private label Custom firmware
What changes Configuration and branding on an already qualified platform A new hardware and firmware specification, tooled and brought up from scratch Brand assets and packaging on an existing shipping model Firmware and software on an existing qualified board
Tooling / NRE Little to none; shared tooling Project-scoped, agreed at G1 before spend None; cosmetics and carton only Software-scoped engineering time
Relative timeline Shortest route after sample sign-off Gate-planned; scales with hardware novelty Very short for label-ready stock models Weeks to months, scoped against the change set
Best when The platform fits and speed to market matters No existing product meets the specification The product is right and only the brand is missing Hardware is settled and only software must change

ODM FAQ

New-Product Development, Without the Blind Spots

Only need branding on a qualified model? OEM and private label are faster, lower-cost routes.

When should we choose ODM instead of OEM?

Choose ODM when no existing platform meets the specification — for example a new form factor, specific tuner or connectivity combination, integrated AV-over-IP engine, or enclosure designed for your deployment. OEM configures an already qualified platform; ODM creates a new product through the stage-gate process.

How long does an ODM project take?

There is no honest single number: timeline scales with hardware novelty, tooling and integration depth. A cosmetic or firmware-focused programme is much shorter than one with new tooling and operator middleware. After the G0 assessment we provide a project plan with gate dates, and we track the programme against those gates rather than quote a generic figure.

Who pays for tooling and engineering?

Tooling and non-recurring engineering are scoped at G1 and confirmed before spend. Depending on the project they may be quoted separately, amortised into unit price, or shared against committed volume. The structure is written into the agreement so there are no surprise charges mid-project.

Who owns the resulting design and firmware?

IP is allocated explicitly. Your brand assets, custom configuration and specified work belong to you within the agreed scope; the underlying platform, reference design and AOSP/third-party code remain with their owners. Exclusivity, territories and update rights are contract terms, not marketing promises.

Can you integrate our middleware or DRM/CAS provider?

Yes. Firmware engineering covers middleware, DRM/CAS, provisioning and private-API integration on a named firmware branch. Where a provider requires its own agreement or credentials, we build against its SDK and support joint qualification with that provider.

What do we receive at each gate?

Every gate produces concrete outputs — assessments, the frozen BOM, EVT and DVT builds, verification reports and a golden sample — plus a defined sign-off criterion. You do not move into spend (tooling, then mass production) until the previous gate is approved.

What is the minimum brief needed to start a G0 assessment?

Enough to evaluate feasibility honestly: the target use case and user, destination market, the must-have feature and peripheral list (tuners, connectivity, ports, 24/7 duty), rough volume expectations and any hard constraints such as an existing middleware provider or enclosure size. Early numbers can be approximate — the G0 output exists precisely to turn them into architecture options, a risk register and a rough cost structure.

Can we pause or stop the programme at a gate?

Yes; that is what the gates are for. Each gate is a contractual checkpoint with delivered outputs, so a programme may pause after sign-off while budgets or markets are reviewed, or stop with the work completed to that point paid for and handed over — EVT files, BOM and reports are not held hostage. No commitment to tooling or volume exists before the gate that authorises it.

When do radio and market certifications happen in the gates?

They are scoped at G0/G1 alongside the architecture — target bands and approvals affect antenna design and the board — laboratory runs take place on EVT/DVT-intent builds, and final compliance evidence is complete against the production configuration before the G4 pilot releases product for shipment. The market access hub describes the regional dossiers, and the certifications page covers the evidence kept per named SKU.

Bring the Brief. We’ll Engineer the Rest.

Share the use case, feature set and target market. Engineering returns a G0 feasibility assessment with architecture options and a gate plan.

Stay Updated with the Latest TV Box Trends

Subscribe to our newsletter and be the first to know about new products, OEM/ODM tips, exclusive offers, and factory updates.

Your experience on this site will be improved by allowing cookies.
Chat with us on WhatsApp