Technical Guide
How to createa mission.
Complete walkthrough for creating and managing missions in Mission Fabric. From initial planning through manifests, SoIs, payloads, participants, and phase progression to after-action review.
Overview
What is a Mission?
A Mission is the root container that orchestrates all operational activities in Mission Fabric. Missions bring together assets, personnel, locations, and objectives into a coherent operational framework.
Every mission has a defined lifecycle from planning through execution to after-action review. Mission Fabric tracks all activities, maintains audit trails, and provides real-time situational awareness throughout.
Missions can range from simple single-objective tasks to complex multi-phase operations with dozens of participants, hundreds of assets, and sophisticated coordination requirements.
Mission Components
Quick Start
Your First Mission in 4 Steps
Get started quickly with a basic mission. You can add more detail later.
Create the Mission
Go to Mission Fabric → Missions and click "Create Mission". Enter a name, select type, and set dates.
Start with just the basics - you can add details later.
Add a Manifest
In the Manifests tab, create at least one manifest (e.g., Personnel) and add your team members.
This organizes who and what is part of the mission.
Link a SoI
In the SoI tab, link or create a Sphere of Influence to define your operational area.
This sets the spatial boundaries for the mission.
Activate the Mission
Change status from Draft to Planned, then Active when ready to begin operations.
You're now running a mission with tracking and coordination.
Ready for More?
See the detailed step-by-step guide below for comprehensive mission configuration including objectives, multiple manifests, participants, and timeline planning.
Detailed Guide
Complete Mission Setup
Follow these steps to create a complete mission from scratch. Each step builds on the previous, creating a comprehensive operational framework.
Define Mission Basics
Start by creating the mission record with core identifying information.
- Mission name and code designation
- Mission type (training, operational, exercise, etc.)
- Planned start and end dates
- Mission commander and primary contacts
- Classification level and access controls
Set Objectives
Define what the mission aims to accomplish with measurable success criteria.
- Primary objective statement
- Secondary objectives (optional)
- Success criteria and metrics
- Constraints and limitations
- Risk tolerance parameters
Configure SoIs
Define the spatial boundaries and policies for mission operations.
- Primary operational area SoI
- Entry and exit policies
- Device restrictions
- Clearance requirements
- Parameter overrides for the mission
Create Manifests
Organize mission assets by type and operational role.
- Launch manifest for propulsion systems
- Payload manifest for mission-critical cargo
- Personnel manifest for human operators
- Sensor manifest for ISR systems
- Vehicle and recovery manifests as needed
Assign Participants
Add personnel and define their roles within the mission.
- Mission commander and leadership
- Operators and technical staff
- Support personnel
- Role-based permissions
- Communication channels and procedures
Define Timeline
Create the mission timeline with phases and milestones.
- Phase definitions and transitions
- Key milestones and checkpoints
- Go/No-Go decision points
- Contingency windows
- Recovery and AAR scheduling
Lifecycle
Mission Statuses
Missions progress through defined statuses that reflect their current operational state. Status transitions are logged and can trigger automated workflows.
Draft
Mission is being planned
Planned
Mission is approved and scheduled
Active
Mission is currently executing
Paused
Mission execution is paused
Completed
Mission objectives achieved
Aborted
Mission terminated early
Status Flow
Note: Active missions can be Paused and resumed. Any mission can be Aborted if required.
Phases
Mission Phases
Missions are organized into phases that represent distinct operational stages. Phase transitions can be manual or triggered by conditions.
Planning
Define objectives, allocate resources, assign personnel
Planning
Define objectives, allocate resources, assign personnel
Preparation
Configure systems, stage assets, conduct rehearsals
Preparation
Configure systems, stage assets, conduct rehearsals
Execution
Active mission operations with real-time monitoring
Execution
Active mission operations with real-time monitoring
Recovery
Recover assets, secure data, begin documentation
Recovery
Recover assets, secure data, begin documentation
After-Action Review
Analyze performance, capture lessons, archive data
After-Action Review
Analyze performance, capture lessons, archive data
Assets
Working with Mission Manifests
Manifests organize mission assets by operational role. Each mission can have multiple manifests of each type.
Launch
Propulsion and launch systems
Payload
Mission-critical cargo
Personnel
Human operators and crews
Sensor
ISR and monitoring systems
Vehicle
Transport platforms
Recovery
Asset retrieval systems
Linking Manifests
Manifests can be linked to missions in two ways:
Create a new manifest directly within the mission context
Link an existing manifest from your asset library to the mission
Manifest States
Operations
Mission Control
Mission Control provides the unified operational workspace for monitoring and managing active missions.
Situational Awareness
Real-time view of all mission assets, positions, and status. 2D/3D visualization modes.
Communications
Integrated communication channels, message logs, and alert management for mission coordination.
Decision Support
Go/No-Go checklists, risk assessments, and automated alerts for mission-critical events.
API Reference
Mission Operations
Core API operations for creating and managing missions programmatically.
/api/missionsCreate a new mission
{
"name": "Operation Nightfall",
"code": "NF-2024-001",
"type": "operational",
"classification": "confidential",
"planned_start": "2024-03-15T00:00:00Z",
"planned_end": "2024-03-17T00:00:00Z",
"commander_id": "user_abc123",
"objectives": [
{
"description": "Establish forward operating base",
"priority": "primary",
"success_criteria": "Base operational within 4 hours"
}
],
"soi_ids": ["soi_operations_zone"]
}/api/missions/:id/statusUpdate mission status
{
"status": "active",
"activated_by": "user_abc123",
"activation_notes": "All systems nominal, commencing operations"
}/api/missions/:id/manifestsLink a manifest to the mission
{
"manifest_id": "manifest_payload_001",
"role": "primary",
"deployment_phase": "execution"
}/api/missions/:id/phases/:phase/transitionTransition to a new mission phase
{
"target_phase": "execution",
"authorized_by": "user_abc123",
"checklist_completed": true,
"notes": "All preparation tasks complete, proceeding to execution"
}Best Practices
Mission Planning Tips
Define Clear Objectives
Vague objectives lead to scope creep. Define specific, measurable success criteria before proceeding.
Plan for Contingencies
Include abort procedures, fallback positions, and emergency protocols in your mission plan.
Use Rehearsals
Run mission simulations in Preparation phase. Identify issues before they become problems in execution.
Document Everything
Comprehensive documentation enables effective after-action review and improves future operations.
Right-Size Manifests
Don't over-complicate. Use the minimum number of manifests needed. Combine when appropriate.
Configure SoIs Early
Set up your operational SoIs before adding assets. This ensures proper policy enforcement from the start.