IoT engineering insights

Practical IoT Engineering for Real Operations

Articles from T2K Group about IoT requirements, hardware and software boundaries, connectivity, device-to-cloud architecture and learning efficiently before deployment.

How to choose connectivity for an IoT product

A practical way to compare cellular, Wi-Fi, LoRaWAN and short-range options using coverage, mobility, power, data and offline behaviour.

Read the article
Device → connectivity → cloudIcon-only article marker

Start with the operation, not the IoT device

Define the operational requirement before selecting hardware, connectivity or a platform.

Read the article

Hardware and software boundaries in an IoT product

Connected systems fail at handovers as often as they fail inside components. Make those interfaces explicit and testable.

Read the article

Prototype the uncertainty, not the whole IoT product

A useful prototype answers an expensive question. It does not need to imitate every part of the finished system.

Read the article

From location point to operational record

Explore how ATLAS connects physical-asset location with movement history, events and operational context.

Read on the ATLAS website
What we write about

Useful detail without technology theatre.

The T2K Group blog focuses on the decisions that affect whether connected technology works beyond a demonstration: requirements, interfaces, field constraints, operational software and evidence-led iteration.

ATLAS product guidance and industry-specific content remain on the dedicated ATLAS website.

01Systems thinkingHow physical, digital and human layers affect one another.
02Engineering practiceWays to frame, prototype, test and review technical work.
03Product lessonsReasoning that informs ATLAS and other connected-system work.

Have a system problem worth unpacking?

Tell us about the operation, constraint or interface that is making progress difficult.