Prepare the activity
Bring the objective, schedule, responsible people, procedure, and expected state into one planning context. Record the conditions that would change the activity.
Mission systems
Mission Grid
A software workspace for mission teams connecting activity plans, telemetry, procedures, and the decisions carried into the next handover.
Discuss Mission Grid
PRODUCT FOCUS
Plans, telemetry, and handovers in the same workspace.
For mission planners, ground-operations staff, telemetry engineers, and research teams working across activity schedules and incoming data. Mission Grid is software for the mission team’s information and decisions; the team supplies the mission requirements and operating procedures.
- 01Activity and procedure planning
- 02Telemetry and event review
- 03Decision and handover records
Connect the plan to the event and the decision.
Review telemetry and events
Relate incoming or recorded data to the planned activity. Keep timestamps, quality flags, thresholds, and supporting context available to the person reviewing an event.
Carry the decision forward
Record the decision, its owner, and any change to the plan. Assemble unresolved events and relevant activity into a handover for the next shift or review.
Sources and connections.
Telemetry contracts, timing, data quality, roles, replay needs, and acceptance criteria shape the software scope. The responsible mission team defines mission-domain requirements, operating procedures, and the integration review.
Telemetry and event sources
Start with documented feeds, recorded data, or a simulator interface. Define field meanings, units, timestamps, quality flags, and expected update behaviour.
Plans and procedures
Identify the schedules, activity records, procedures, and asset information the team already maintains. Agree which information the workspace owns and which it references.
Mission-team records
Connect event review to the team’s issue, decision, and handover process. Roles, access, and operating responsibilities are defined with the mission specialists.
What the workflow
needs to deliver.
- Activity plans linked to procedures, owners, and expected states
- Telemetry and event views with timing and quality context
- Decision records connected to the event and updated plan
- Handover summaries with unresolved items and responsible people
Bring one mission workflow and a representative data set.
A planning task, event review, or shift handover provides a focused starting point. We can review the source contracts and interface needs with the responsible mission team before defining the software scope.
- Does each value retain its units, timing, and quality information?
- Can the reviewer connect an event to the planned activity?
- Are the decision owner and unresolved items visible?
- Can recorded data support the same review workflow?
Discuss Mission Grid.
What is Mission Grid intended to support?
The software scope covers activity planning, telemetry and event review, procedures, decision records, and handovers. The enquiry identifies which of those workflows the mission team needs to connect.
Does SpaceTech7 operate the satellites?
SpaceTech7 builds software for mission teams. The satellite or mission operator remains responsible for the hardware, mission operations, procedures, and operational acceptance.
Can we begin before a live feed is available?
Recorded telemetry, a simulator interface, or a documented feed contract can support an initial software workflow. Live integration requirements and review are agreed with the mission team.
What telemetry information should we share?
Bring representative records with field definitions, units, timestamps, quality flags, expected update behaviour, and the decisions they support. Redacted or synthetic data can support an initial discussion.
How are mission requirements reviewed?
The responsible domain specialists define the operating constraints and acceptance criteria. We use those requirements to scope the interfaces, source contracts, replay scenarios, and integration checks.