ConfidentialHJMT Solutions Patent Position Review
Section 09.1

EquipmentShare — Industrial Equipment Mapping

Technology-enabled construction and industrial equipment rental. EquipmentShare describes T3 as a proprietary full-stack hardware and software platform connecting assets, people, jobsites, telematics, workflows, rental operations, service, asset access and data.

09.1.0

Publicly Observable Architecture

AssetsPeopleJobsitesTelematicsWorkflowsRental OperationsServiceAsset AccessData
Review Priority

Very High-Priority Technical Review Environment

EquipmentShare publicly states that all its assets are managed through T3, and that the platform also manages third-party-owned equipment through its OWN Program.

Physical Equipment

01

Embedded Hardware

02

Telematics / Sensor Data

03

T3 Cloud Platform

04

Asset / Operator / Service / Rental Workflows

05

Control Action

06
09.1

EquipmentShare — Company Profile

Company
EquipmentShare
Vertical
Technology-enabled construction and industrial equipment rental
Evidence Basis
Publicly available first-party material
Review Note
Very high-priority technical review environment.

EquipmentShare describes T3 as a proprietary full-stack hardware and software platform connecting assets, people, jobsites, telematics, workflows, rental operations, service, asset access and data.

EquipmentShare publicly states that all its assets are managed through T3, and that the platform also manages third-party-owned equipment through its OWN Program.

AssetsPeopleJobsitesTelematicsWorkflowsRental OperationsServiceAsset AccessData
09.1.1

T3 Architecture

Public observation

EquipmentShare publicly describes T3 as integrating embedded telematics hardware, software applications, cloud infrastructure, GPS, Bluetooth, engine / CAN data, sensors, access-control keypads, AI-supported data analysis, service workflows, dispatch and fleet-management tools.

HJMT technical analysis

The described architecture places physical asset data, cloud processing and operational workflows within a single control environment, which is directly relevant to several MarketMind elements concerning intake, asset control, monitoring and integration.

Relevant MarketMind technical elements
02 — Multi-Variable Transaction Intake05 — Asset-Driven Transaction Control06 — Dynamic Risk Modelling13 — Live Transaction Monitoring14 — Event-Based Trigger Engine16 — Location-Based Control21 — Programmable Transaction Framework22 — State-Based Transaction Control25 — API-Driven External Platform Integration26 — Cross-Platform Control Architecture

Physical Equipment

01

Embedded Hardware

02

Telematics / Sensor Data

03

T3 Cloud Platform

04

Asset / Operator / Service / Rental Workflows

05

Control Action

06
Assessment
02Multi-Variable Transaction IntakeStrong Correspondence
05Asset-Driven Transaction ControlStrong Correspondence
13Live Transaction MonitoringStrong Correspondence
16Location-Based ControlStrong Correspondence
21Programmable Transaction FrameworkStrong Correspondence
26Cross-Platform Control ArchitectureStrong Correspondence
Evidence confidence — High
  • High — first-party platform and corporate material.
09.1.2

Live Asset Monitoring

Public observation

EquipmentShare states that T3 provides real-time visibility into asset location, asset health, utilisation, machine performance, service requirements and jobsite activity, and that the platform supports predictive maintenance and uptime workflows.

HJMT technical analysis

Monitoring is coupled to service, logistics and operational response rather than being presented as reporting alone.

Relevant MarketMind technical elements
05 — Asset-Driven Transaction Control06 — Dynamic Risk Modelling13 — Live Transaction Monitoring14 — Event-Based Trigger Engine15 — Exception Management16 — Location-Based Control17 — Environmental & Contextual Conditioning21 — Programmable Transaction Framework

Active Rental Asset

01

Live Location / Utilisation / Health / Engine Data

02

T3 Monitoring

03

Service / Logistics / Operational Action

04
Assessment
14Event-Based Trigger EngineStrong Correspondence
15Exception ManagementStrong Correspondence
Evidence confidence — High
  • High — first-party product documentation.
09.1.3

Predictive Maintenance

Public observation

EquipmentShare states that T3 uses machine and performance data to support predictive maintenance and reduce unplanned downtime, and that T3 can automate or improve service workflows.

HJMT technical analysis

Predictive maintenance is publicly disclosed, but full MarketMind-style transaction-outcome learning is not established by this evidence alone.

Relevant MarketMind technical elements
06 — Dynamic Risk Modelling13 — Live Transaction Monitoring14 — Event-Based Trigger Engine15 — Exception Management17 — Environmental & Contextual Conditioning21 — Programmable Transaction Framework23 — Adaptive Learning

Machine Performance Data

01

Analysis

02

Predictive Service Need

03

Service Workflow

04

Asset Availability / Uptime Response

05
Assessment
06Dynamic Risk ModellingStrong Correspondence
23Adaptive LearningRelevant Correspondence

Recorded as Partial / Relevant Correspondence: predictive maintenance is disclosed; transaction-outcome learning is not established.

Evidence confidence — High
  • High for predictive maintenance. Medium for adaptive learning.
09.1.4

Operator Access Control

Public observation

EquipmentShare publicly states that its cloud-connected keypad technology can restrict machine operation to authorised personnel, using operator-specific access codes, digital credentials or keycards.

EquipmentShare states that customers can remotely control machine access and view operator activity.

HJMT technical analysis

Physical asset operation is conditioned on verified digital credentials, which corresponds closely to MarketMind's verification-driven and state-based control concepts.

Relevant MarketMind technical elements
01 — Event-Driven Transaction Activation03 — Behavioural Intelligence08 — Dynamic Transaction Conditioning19 — Verification-Driven Control21 — Programmable Transaction Framework22 — State-Based Transaction Control

Operator

01

Digital Credential

02

Authorised?

03

Yes → Equipment Access

04

No → Access Restricted

05
Assessment
01Event-Driven Transaction ActivationStrong Correspondence
19Verification-Driven ControlStrong Correspondence
22State-Based Transaction ControlStrong Correspondence
Evidence confidence — High
  • High — first-party access-control material.
09.1.5

Third-Party Asset Integration — OWN Program

Public observation

EquipmentShare's OWN Program incorporates third-party-owned equipment into the T3 operating environment, and EquipmentShare publicly states that these assets are managed alongside company-owned assets.

Owners receive data concerning location, usage, health and performance, and the rental experience is intended to remain consistent regardless of underlying ownership.

HJMT technical analysis

A single control environment spanning differently owned assets is relevant to MarketMind's cross-platform control and external integration concepts.

Relevant MarketMind technical elements
02 — Multi-Variable Transaction Intake05 — Asset-Driven Transaction Control13 — Live Transaction Monitoring22 — State-Based Transaction Control25 — API-Driven External Platform Integration26 — Cross-Platform Control Architecture

Company-Owned Assets + Third-Party-Owned Assets

01

Common T3 Control Environment

02

Rental Customer

03
Assessment
25API-Driven External Platform IntegrationStrong Correspondence
Evidence confidence — High
  • High — published program material.
09.1.6

Data Does Not Stop at Visibility

Public observation

EquipmentShare states that T3 connects live equipment data to dispatch, service, predictive maintenance, asset allocation, fleet purchasing, uptime support, logistics and operator access.

HJMT technical analysis

The observed relationship runs from observed data to decisioning, to workflow, to physical or operational action. This integrated control relationship is the specific characteristic most relevant to MarketMind in this vertical.

Relevant MarketMind technical elements
06 — Dynamic Risk Modelling08 — Dynamic Transaction Conditioning13 — Live Transaction Monitoring14 — Event-Based Trigger Engine15 — Exception Management21 — Programmable Transaction Framework

Observed Data

01

Decisioning

02

Workflow

03

Physical / Operational Action

04
Assessment
08Dynamic Transaction ConditioningRelevant Correspondence
Evidence confidence — High
  • High — first-party platform material.
09.1.7

EquipmentShare — Summary

Current high-value observations
Full-stack hardware + software platformConnected rental fleetEmbedded telematicsReal-time locationReal-time healthUtilisationPredictive maintenanceAutomated service workflowsDispatch integrationCloud-based operator access controlDigital credentialsRemote access controlThird-party asset integrationMulti-ownership fleet managementJobsite intelligenceAI-supported analysis
Strongest MarketMind reference areas
Asset-Driven ControlMulti-Variable IntakeLive MonitoringEvent TriggeringLocation ControlVerificationState-Based ControlProgrammable Transaction FrameworkPredictive ModellingCross-Platform Architecture

No overall Technical Correspondence Index is generated for this company.

09.1.8

EquipmentShare — Evidence Gaps

Dynamic bond / security architecture not established.Conditional escrow not established.Behavioural-history-to-financial conditioning not established.Conditional settlement requires more evidence.Transaction-outcome adaptive learning requires further review.

Gap classification recorded for this review: Implementation Detail Limited. Missing evidence has not been filled with assumptions.

09.1.9

EquipmentShare — Potential MarketMind Enhancement

If MarketMind were integrated around the observed platform environment, what additional control capability could the architecture potentially provide?
  • MarketMind could potentially extend the transaction-control architecture with predictive damage risk.
  • MarketMind could potentially extend the architecture with predictive late-return risk.
  • MarketMind could potentially extend the architecture with operator behavioural reliability inputs.
  • MarketMind could potentially extend the architecture with dynamic security requirements.
  • MarketMind could potentially extend the architecture with insurance decisioning.
  • MarketMind could potentially extend the architecture with location / jobsite risk conditioning.
  • MarketMind could potentially extend the architecture with weather and environmental conditions.
  • MarketMind could potentially extend the architecture with a transaction reliability score.
  • MarketMind could potentially extend the architecture with conditional financial holds.
  • MarketMind could potentially extend the architecture with verified settlement.
  • MarketMind could potentially extend the architecture with cross-platform behavioural intelligence.
  • MarketMind could potentially extend the architecture with adaptive future transaction conditions.
  • MarketMind could potentially extend the architecture with downstream availability protection.

These are potential extensions of the architecture. They are not statements that the platform lacks the capability.

09.1.10

EquipmentShare — Public Evidence Sources

Publication date not stated by source · Current status requires confirmation
Mapped elements: 02, 05, 13, 21, 25, 26
EquipmentShareT3 platform materialOfficial Product Documentation
Publication date not stated by source · Current status requires confirmation
Mapped elements: 02, 05, 13, 14, 16, 21, 22, 25, 26
EquipmentShareFleet managementOfficial Product Documentation
Publication date not stated by source · Current status requires confirmation
Mapped elements: 05, 13, 16, 22
EquipmentShareAccess controlOfficial Product Documentation
Publication date not stated by source · Current status requires confirmation
Mapped elements: 01, 03, 08, 19, 21, 22
EquipmentShareOWN ProgramOfficial Program Material
Publication date not stated by source · Current status requires confirmation
Mapped elements: 02, 05, 13, 22, 25, 26
Publication date not stated by source · Current status requires confirmation
Mapped elements: 06, 13, 14, 15, 17, 21, 23
09.1.Z

Next