Design and reference engineering
Mad develops the agreed design, interfaces and requirements for the wider project team to use.
Design at Mad ↗MAD INSIGHTS
Mad can supply technology, specialist engineering and implementation support within an agreed project scope, alongside an owner’s selected delivery partners.
THE PRACTICAL QUESTION
An owner may have an established integrator, a preferred exhibit fabricator or a delivery structure already in place. Mad can contribute a defined technology or engineering package within that team. The useful first conversation is about the experience, the interfaces and who will be responsible for delivering them.
Mad’s technology includes patented and patent-pending work. The public patent records explain particular inventions; the project agreement establishes what technology and services are actually supplied and the terms of their use.
WAYS TO WORK TOGETHER
Mad develops the agreed design, interfaces and requirements for the wider project team to use.
Design at Mad ↗Mad supplies agreed technology together with the configuration, training and support needed to use it.
Work with Mad ↗Teams divide fabrication, installation, programming and commissioning around a clear scope and joint acceptance plan.
Integration ↗| Topic | What the project agreement should establish |
|---|---|
| Included technology | The software, methods, documentation and capabilities being supplied for the actual application. |
| Permitted use | The sites, systems and uses covered by the agreement, and the process for later changes. |
| Interfaces | Data formats, control protocols, network and hardware dependencies, plus each party’s responsibilities. |
| Commercial terms | Fees, term, support, maintenance, updates and any renewal provisions agreed for the project. |
| Acceptance and handover | The tests, records, training and configuration access required for the intended operating model. |
Standard computer hardware can be sourced and maintained differently from software and patented methods. These questions should be addressed separately, so a familiar hardware platform does not imply unrestricted rights to every application or method running on it.
PROJECT COORDINATION
A defined Mad scope can sit alongside the client’s prime integrator and local partners. Establish who configures each system, who controls each interface and how the teams test the combined result. The same clarity should continue into support and future upgrades.
Discuss these arrangements when they become relevant to the project. An early decision can prevent rework, but an existing installation or a project already under way can also be assessed.
The IP and patents page distinguishes selected granted records, patent-pending work and registered technology names. A patent’s claims and jurisdiction determine its scope. A general technology description does not establish that every related feature or implementation requires the same rights.
RELATED READING
LET’S BUILD WHAT COMES NEXT
Mad can join an early brief, contribute a defined scope or assess an existing installation. Tell us the decision you need to make next.
Start a conversation