Indeema

Hardware & Electronics

Hardware and electronics engineering for connected products

Indeema takes responsibility for the electronics inside a connected product, from architecture and component choices through boards, bring-up and validation to the files a manufacturer builds from. Bring us one board that has to be right, the electronics of the whole device, or hardware that has to work with its firmware and connectivity.

See what we take responsibility for

Where hardware work begins

Most hardware work begins with one of these

  • The product concept exists. The electronics architecture does not.

  • The board has to work with firmware and a stack that are already chosen.

  • The design has to become files a manufacturer can build from.

  • The device cannot be updated as built, so its hardware has to change.

  • This is your first hardware product, and you need to know what to decide when.

  • The next generation has to fit a different physical product.

What Indeema takes responsibility for

IoT hardware development, from architecture to manufacturing files

Once units exist, choices of platform, power and physical fit are expensive to undo. Responsibility is ordered by that: the hardest decisions to reverse come first, each made against the firmware and the product it serves.

The work spans the architecture, the schematics and PCB design, and the prototypes that prove them.

  1. Architecture

    Turns requirements into a hardware architecture: the platform, the sensing and power approach, and the limits the board must respect.

    You no longer carry aloneWhat is this device made of?

    Seam Indeema ownsFirmware: which platform, which peripherals.

  2. Electronics design

    Selects components, draws the schematics and lays out the board.

    You no longer carry aloneIs the design correct and complete?

    Seam Indeema ownsFirmware: pinout, power and programming access.

  3. Physical integration

    Fits the board and the sensor position to the product they sit in: layout and placement against its dimensions.

    You no longer carry aloneWill it fit the product and work inside it?

    Seam Indeema ownsThe enclosure and dimensions you set.

  4. Proof

    Has prototypes built, brings the first boards up and tests the design against its requirements.

    You no longer carry aloneDoes it work, and how do we know?

    Seam Indeema ownsFirmware bring-up on the same boards.

  5. Production handoff

    Prepares the bill of materials, manufacturing files and assembly drawings a contract manufacturer builds from.

    You no longer carry aloneCan someone else build it?

    Seam Indeema ownsThe manufacturer you choose.

  6. Revision & continuity

    Redesigns for a new generation, a new constraint or a device that has to become updatable.

    You no longer carry aloneWhat changes when the product changes?

    Seam Indeema ownsThe firmware and devices you already have.

Where hardware meets firmware

  • Pinout and peripherals
  • Power and power budget
  • Boot, programming and debug access

Hardware decides what the device is physically able to do, and that it can be built. Firmware decides how it behaves within that ability. Once the board exists, the software that brings it to life and keeps it updatable. Embedded & Firmware

Three development boards in a row on glass plates, from a prototype with jumper wires to a cleaner revision

Three revisions of one board: hardware is revised until it is right.

Scope of responsibility

How much of the device’s electronics should Indeema own?

Scopes, not tiers. Hardware development can start at any of them, including redesigning a device that already ships.

  1. Discipline

    A board, a subsystem or one electronics problem.

    • A power stage, a sensor and its placement, or a hardware change so a device can be updated

  2. Layer

    The electronics of the device as one design.

    • Platform, power, sensing, board, prototypes and manufacturing files

  3. Connected layers

    Electronics designed together with the firmware and connectivity that depend on it.

    • Interfaces agreed and proven on the same boards
    Embedded & Firmware

  4. Whole product

    The device as one part of the whole product.

    • Electronics, firmware, cloud and applications under one architecture
    IoT Product Engineering

At every scopeDesignBuildProveHand off

Scope follows where the problem is, not the size of the engagement.

Method and handover

Seven gates, and a loop that runs until the design is right

Each gate ends with something your team can read, build or check. If the platform is not yet decided, start with Product Discovery & Technical Strategy.

  1. Architect

    Turns requirements into a hardware architecture.

    You receiveSpecification record; platform and component decisions

    DecisionCommit to a platform, or stop.

  2. Design

    Selects components, draws schematics, lays out the board.

    You receiveSchematics; PCB design package

    DecisionApprove the design for a first build.

  3. Prototype

    Has the first boards built through a manufacturing partner.

    You receivePrototype boards, and each revision after them

    DecisionContinue, change or stop.

  4. Bring up

    Powers and debugs the first boards.

    You receiveBring-up notes and debugging protocols

    DecisionFix the design, or go on to validate.

  5. Validate

    Tests the design against its requirements.

    You receiveTest reports

    DecisionPrepare for production, or revise.

  6. Prepare for production

    Produces the bill of materials, manufacturing files and assembly drawings.

    You receiveManufacturing package

    DecisionHand it to a manufacturer.

  7. Evolve

    Redesigns for a new generation, a new constraint or an update need.

    You receiveRevised design and the record of what changed

    DecisionGo to the next generation, or hold.

Revision loop. What bring-up and validation find goes back to Design, as many times as the design needs. Each revision is kept and recorded.

The full handover is agreed for each engagement. Firmware bring-up runs on the same boards, and is described under Embedded & Firmware.

What this has looked like

Three situations, and what Indeema owned in each

Client names and figures are not shown.

  1. LayerFrom concept to manufacturing files

    A drone concept existed, with no assets beyond the idea.

    Indeema owned
    Requirements and specification, then schematics and PCB layout for a flight controller and a speed controller built to work with a chosen open-source flight stack. The bill of materials, manufacturing files and assembly drawings for a contract manufacturer. Bring-up of the first boards.
    What changed
    The concept became boards that a manufacturer built and tested, with test reports.
    Flight-controller and speed-controller boards
  2. LayerA first hardware product, and a second generation

    A client entering device production for the first time needed a monitoring device to fit a product it had already drawn.

    Indeema owned
    Selecting the sensors and the main processor, deciding where the sensor sits inside the unit, and reworking the internal layout and PCB placement to fit the required dimensions. Two device generations built as prototypes.
    What changed
    The client had prototypes of two device generations ready for beta testing.
    Indoor air-quality monitoring device
  3. DisciplineChanging hardware so a device can evolve

    A sensor unit could not be re-flashed once assembled.

    Indeema owned
    A schematic and PCB change so the unit could be programmed over USB without opening its enclosure, alongside a firmware migration to a current framework.
    What changed
    The unit could be updated and maintained.
    Sensor unit modernization

Reading: What is inside a connected device

Ways to work with Indeema

Start with the electronics of your device

  1. Engineering ownership

    Indeema is accountable for a defined hardware scope, from architecture to the files a manufacturer builds from. You decide at agreed gates.

  2. Joint product team

    Indeema hardware engineers work inside your team, against interfaces agreed with your firmware and mechanical engineers.

Also available: specialist team extension. A defined hardware specialty joins a team you lead.

Bring us

  • The concept, or the board you have
  • What it must do, and the limits it lives in
  • The firmware and enclosure it has to work with
  • The part you want owned
Discuss your hardware scope

Where the boundary sits

Sector context: Drones & UAV · Smart home

Privacy controls

Choose optional measurement

Your choice is remembered in this browser for 180 days, then we ask again. Analytics measures page views and interactions and stores campaign attribution. You can withdraw consent in Privacy settings.

Advertising measurement remains disabled.