COP
Shared Operational Picture
Bring mission entities, locations, routes, areas, tasking, and status into one spatial operating surface.
Operator Interface / Common Operating Picture
BASECAMPSee the operation. Act with context.
Basecamp is BLK_MTN's operator-facing environment for mapping, mission planning, messaging, tasking, situational awareness, and network-aware operations.
Operation NorthstarPLANLIVEREPLAYNetwork degraded
OPSNETSIGLOGAIR
Team AlphaNode 04SupplyContact
MessagesTasksEventsTimelineTransport Queue3 queued / 1 transmitting
Common Operating Picture
The map is the center of gravity.
Basecamp keeps operational entities, routes, areas, tasks, network state, messages, and contextual actions connected to one shared view of the operation instead of splitting them into disconnected tools.
CTX
Contextual Inspection
Select an entity once and carry the same context across maps, tables, tasks, messages, and alerts.
FRS
Freshness & Provenance
Show operators when information is current, stale, reported, observed, inferred, or otherwise uncertain.
NET
Network Awareness
Expose relevant reachability, transport, queue, and link state without turning the UI into a networking console.
MSG
Messaging & Tasking
Keep communications and mission actions available directly from the operational context that gives them meaning.
ALT
Operational Alerts
Connect alerts to affected entities and places so operators can understand what changed and what can be done.
Three Operating Modes
Plan. Operate. Understand what happened.
PLAN
Build missions, areas, objectives, assets, tasks, timelines, logistics, network assumptions, and review packages before authoritative submission.
LIVE
Operate from the current Common Operating Picture with current mission state, connectivity, transport status, tasking, and alerts.
REPLAY
Review historical operational state and timelines without confusing reconstructed history with live command capability.
Degraded-Network Native
A button click is not the same thing as delivery.
Basecamp keeps local intent, transport progress, and authoritative outcome separate. When connectivity degrades, operators can see whether an action is drafted, queued, transmitting, delivered, confirmed, failed, or expired.
Transport QueueCurrent link: degraded
Message · Team Alpha12:42:08Confirmed
Task update · Sector 312:42:33Transmitting
Plan revision · Northstar12:43:17Queued
Position request · Node 1112:43:25Queued
Mission Planning
Planning deserves its own surface.
Basecamp separates planning from live operation while reusing the same spatial model. Operators can develop a mission locally, validate it, prepare it for submission, and clearly distinguish that preparation from MMGR authorization or publication.
Operation Northstar
Mission brief
Operation Northstar
Restore local communications and support field assessment across Sector North.
Connect the field
Prepare a temporary communications backbone and two mobile teams.
Sector North
18.4 km² area with three planned waypoints and a local map package.
Prepare, deploy, verify
Sequence the plan around site access, radio setup, and coverage checks.
Desired outcomes
Define success before deployment.
Objectives connect intent to tasks and measurable completion criteria.
Establish local communications
Verify a route between the field teams and the support site.
Assess three waypoints
Attach a field report to each planned assessment location.
Sustain the operating window
Plan battery changes and a return check for both teams.
Resource assignments
People and equipment in context.
Planned allocations for this illustrative mission; availability must be confirmed before publication.
| Asset | Planned role | Plan status |
|---|---|---|
| Team Alpha | Field assessment | Assigned |
| Team Bravo | Field assessment | Assigned |
| Hermes 01 | Alpha communications | Allocated |
| Hermes 02 | Bravo communications | Allocated |
| Atlas 01 / Piston | Backbone relay | Allocated |
| Support vehicle | Transport / supplies | Allocated |
| UAS 01 | Optional area survey | Approval required |
Task relationships
Assign work and dependencies.
T03–T06 precede field assessments. Report consolidation follows T07–T09; all tasks remain planned.
| ID | Task | Owner |
|---|---|---|
| T01 | Confirm site access | Alpha |
| T02 | Stage supplies | Support |
| T03 | Position Atlas | Support |
| T04 | Configure relay | Support |
| T05 | Verify Alpha link | Alpha |
| T06 | Verify Bravo link | Bravo |
| T07 | Assess waypoint 1 | Alpha |
| T08 | Assess waypoint 2 | Bravo |
| T09 | Assess waypoint 3 | Alpha |
| T10 | Consolidate reports | Support |
| T11 | Rotate batteries | Support |
| T12 | Return check | Both teams |
Planned sequence / UTC
A shared order of operations.
Illustrative times show intended sequence, not observed progress.
Brief and stage
Confirm assignments, supplies, and site access.
Establish relay
Position Atlas and verify team links.
Field assessment
Visit the three planned waypoints.
Reconcile reports
Collect observations; flag missing updates.
Sustainment check
Review batteries and remaining supplies.
Return and review
Account for teams and prepare the handoff.
Sustainment
Keep the plan supportable.
Associate supplies and movement with the teams that depend on them.
| Resource | Allocation | Check |
|---|---|---|
| Spare batteries | 2 per handheld | Confirm charge |
| Atlas power | Primary + reserve | Verify load budget |
| Water / field kits | 2 team sets | Confirm inventory |
| Support vehicle | Staging point | Confirm access |
| Recovery supplies | Support site | Check before departure |
Connectivity assumptions
Plan for gaps in reachability.
Describe intended relationships and delivery behavior before live link information exists.
Atlas 01 / Piston
Proposed relay between the support site and mobile participants.
Hermes 01 + Hermes 02
Both teams participate through Condor; actual routes adapt in operation.
Queue and reconcile
Keep pending intent visible. A queued update is not a confirmed outcome.
Conditional air plan
Make air activity explicit.
A future planning surface for air assets, mission relationships, constraints, and human review.
UAS 01
Optional survey support; not part of the critical communications path.
Sector North survey area
Proposed collection area must be checked against applicable restrictions.
Hold for review
No launch or autonomous action is implied by preparing this plan.
Submission readiness
Review before requesting authority.
Check local structure, assumptions, and unresolved approvals before a future MMGR submission.
| Review item | Local result |
|---|---|
| Area and map package | Prepared |
| Objectives and task links | Valid |
| Asset references | 7 assigned |
| Task structure | 12 / 12 locally valid |
| Readiness and inventory | Needs confirmation |
| Air / UAS approval | Outstanding |
| MMGR authorization | Not requested |
| Publication | Not published |
Interactive planning concept · Illustrative mission data · Select a view to explore.
Operational Workspaces
Different lenses. One operational world.
Basecamp workspaces change the tools, overlays, and data emphasis around the operator while preserving shared mission context, selection, and the underlying entity model.
01 / Operations
Operations
The default mission COP for entities, objectives, routes, AOIs, tasking, and execution.
02 / Network
Network
Reachability, nodes, selected relationships, transport path, link quality, and partitions.
03 / Logistics
Logistics
Supplies, movement, readiness, sustainment relationships, and mission support.
04 / Specialized
Signals / Intelligence / Air
Specialized operational lenses exposed through MMGR services without turning backend service names into operator navigation.
Offline Geospatial
The map should not disappear when the internet does.
Basecamp is designed toward locally cacheable, self-hosted map packages and mission/AO pinning. Cached data remains available during map-service disruption while clearly retaining age, provenance, and package state.
BLK_MTN Dark TacticalActive / local
Mission AO PackagePinned
Topographic OverlayAvailable offline
Remote Map ServiceUnavailable
The BLK_MTN Platform
Where the system becomes usable by people.
Marmot brings BLK_MTN into the field. Condor moves information. MMGR provides mission services and authority. Basecamp turns those capabilities into an operational interface.
BasecampOperator Interface
MMGRMission Services
CondorResilient Networking
MarmotEdge Hardware
Development Status
Active Development
UI / Mapping / Integration
Basecamp's application shell, mapping stack, mission-planning surfaces, entity/workspace model, and BLK_MTN service integration are under active development. Offline geospatial packaging, complete MMGR publication workflows, broader workspace functionality, and deployment qualification remain part of the development program.
BLK_MTN Technologies
Give operators the whole picture without pretending the network is perfect.
Explore how Basecamp brings mapping, mission state, communications, planning, and degraded-network awareness into one operator environment.