PTD Capital LLC
Investor access

Applied Software

Signal Grid Systems

Status
Active
Entry date
2022-06-06
PTD Capital investment
Recorded current value
Ownership
Internal lead
Mina Harrow
Last reviewed
2026-06-24

Overview

Signal Grid Systems develops operational software for teams responsible for distributed assets, field interventions and technical services.

Activities

  • Work orders
  • Planning
  • Asset inventories
  • Intervention reports
  • Operational alerts

Financial history

Investors OnlyAccess

Funded workstreams

SGS-01 / DeploymentCompleted

Field workflow pilot

Test work-order creation, offline completion and supervisor review.

Budget
Spent
Target
2026-05-31
Owner
Mina Harrow

Latest record. The pilot closed with three carry-forward defects.

Next decision. Accept the pilot closure memorandum.

SGS-02 / ProductActive

Offline synchronisation

Reduce failed and duplicated offline submissions.

Budget
Spent
Target
2026-09-16
Owner
Mina Harrow

Latest record. The retry logic entered controlled deployment.

Next decision. Decide release 1.0 inclusion after field test four.

SGS-03 / DataActive

Asset model revision

Align asset identifiers with field-team operating records.

Budget
Spent
Target
2026-10-14
Owner
Maia Lorne

Latest record. Seventeen mappings remain unresolved.

Next decision. Freeze the core model after the September review.

SGS-04 / GovernanceUnder review

Release 1.0 boundary

Define the functions and defects permitted at release 1.0.

Budget
Spent
Target
2026-11-04
Owner
Noor Bellamy

Latest record. The boundary was returned to the project team after the June review.

Next decision. Submit revised release criteria in August.

Project chronology

working session held · Open

Working Session Held

A working session reviewed asset inventories, the related exceptions and the evidence required for closure. Items without sufficient support remained open.

Consequence: Actions were recorded against the existing workstream rather than opened as a new program.

review completed · Open

Review Completed

The work orders review was completed against the accepted period sample. Exceptions were retained separately from completed work and no change was made to the investment perimeter.

Consequence: Completed observations moved to the period record; unresolved items remained in the exception queue.

project moved to next phase · Open

Project Moved To Next Phase

The intervention reports workstream entered its next controlled phase after its owner, evidence requirement and acceptance boundary were confirmed.

Consequence: The new phase began within the existing budget and governance boundary.

priority changed · Open

Priority Changed

The operating sequence was revised so that confirm the release 1.0 boundary became the next recorded priority. The change followed the current capacity and dependency review.

Consequence: Lower-priority work remained visible in the register and can return at a later review.

reporting method revised · Open

Reporting Method Revised

The reporting method for operational alerts moved to a new version after the team identified a classification that was not applied consistently across the available records.

Consequence: The earlier method version remains available and the next comparison is qualified until the revised series has a complete period.

responsibility transferred · Open

Responsibility Transferred

Responsibility for the next asset inventories review transferred within the operating team. The source record, open exceptions and scheduled date moved with the file.

Consequence: The receiving owner accepted the source list, open risks and next review boundary.

review scheduled · Open

Review Scheduled

The work orders file was placed on the October 2025 review cycle after the source register was reconciled with the current responsibility list.

Consequence: The review was assigned to Mina Harrow with a retained period sample and next-decision date.

Program started · Open

Program started

Field workflow pilot entered the operating plan.

Consequence: Budget and review boundary recorded.

Program started · Open

Program started

Offline synchronisation entered the operating plan.

Consequence: Budget and review boundary recorded.

Program started · Open

Program started

Asset model revision entered the operating plan.

Consequence: Budget and review boundary recorded.

timeline delayed · Open

Timeline Delayed

The milestone connected to confirm the release 1.0 boundary moved after the review recorded a continuing dependency: offline synchronisation defects. The earlier target remains in the chronology.

Consequence: The target date was re-baselined without marking the underlying work complete.

Completed · Open

Completed

Field workflow pilot: The pilot closed with three carry-forward defects.

Consequence: Accept the pilot closure memorandum.

Target review · Open

Target review

The scheduled target for Field workflow pilot was recorded.

Consequence: Accept the pilot closure memorandum.

Target review · Open

Target review

The scheduled target for Offline synchronisation was recorded.

Consequence: Decide release 1.0 inclusion after field test four.

Target review · Open

Target review

The scheduled target for Asset model revision was recorded.

Consequence: Freeze the core model after the September review.

Operating indicators

Active field users

146 users

Users completing at least three field actions in the final month

Prior period
128 users
Interpretation
Improved versus prior period (128 users).
As at
2026-09-30
Source
SGS usage register

Open data mappings

17 mappings

Source fields without an accepted destination definition

Prior period
24 mappings
Interpretation
Improved versus prior period (24 mappings).
As at
2026-09-30
Source
SGS deployment ledger

Work orders synchronised

96.1 %

Share of submitted work orders synchronised within 24 hours

Prior period
94.8 %
Interpretation
Improved versus prior period (94.8 %).
As at
2026-09-30
Source
SGS sync log

Current priorities

  • Close the deployment review
  • Reduce unresolved data mappings
  • Complete offline workflow testing
  • Confirm the release 1.0 boundary

Recent developments

  • The field workflow pilot was completed in May 2026.
  • Release 0.9.4 was delayed by nine days.
  • The asset model was revised after operator review.

Principal risks

  • Uneven quality in customer source data
  • Dependency on two deployment leads
  • Offline synchronisation defects

Documents and research