1. Overview: What Are Spectrum Plans?
A spectrum plan is a proposed change to a market's channel allocation. You duplicate a market's current lineup, reassign channel types (for example, converting Analog Video slots to DOCSIS 3.1), set a target implementation date, then export the plan as a JSON file for review, approval, or later re-import.
Plans are exported per market. Each JSON file captures the full before and after spectrum layout along with a change-by-change log, so anyone who opens it gets complete context without needing the dashboard open.
Open Market
→
Duplicate
→
Edit
→
Set Date
→
Export
2. Creating a Plan
- Use the Region, State, or Search filters to locate your target market.
- Click the market's row in the table. A detail modal opens showing the current channel map.
- Click the Duplicate for Planning button. This creates an editable copy. The original is never modified.
Safe by design: The original lineup data is read-only. All edits happen on the duplicated copy only.
3. Editing Channels
Click to Cycle Mode (default)
Click any channel cell in the PLANNED grid and it cycles through the types:
MSR→
O→
AV→
DV→
D3.0→
D3.1→
PLT→
(wraps)
Paint Mode (Bulk Editing)
- Click Paint Mode in the toolbar toggle.
- A color palette appears. Click the target type (e.g., the purple D3.1 button).
- Click any channel cell to assign that type instantly.
- Hold the mouse button and drag across multiple cells to paint in bulk.
Tip: Paint mode is ideal for large block conversions. Select D3.1 from the palette and drag across the target range.
Changed Channel Indicators
Modified channels show a yellow dot in the top-right corner plus a yellow outline. The diff summary lists every change with its frequency, EIA number, and the from/to type.
Resetting
Click Reset Changes to revert the planned lineup back to the original state.
4. Setting the Implementation Date
- In the plan metadata bar, find the Conversion Date field.
- Click the date picker and select the target date.
- If the date is unknown, leave it blank. The export will record it as
"TBD".
You can also enter a Plan Name in the text field, e.g. "Stephenville Q3 2026 D3.1 Migration".
The plan name and date are both stored in the exported JSON, giving full context to anyone who reviews the file.
5. Comparing Current vs. Planned
Side by Side
Shows CURRENT (original) on the left and PLANNED (editable) on the right for easy visual comparison.
Inline Diff
Single grid showing the planned layout with changed channels highlighted. A badge shows the total change count. More compact for smaller screens.
Both views include the diff summary table listing each changed channel.
6. Exporting a Plan to JSON
- After editing and setting the date, click Export Plan JSON.
- Your browser downloads a
.json file named after the city (e.g., Stephenville_plan.json).
- Share this file via email, Teams, or a shared drive.
What's in the file: Plan name, conversion date (or TBD), export timestamp, market metadata, a list of every changed channel with from/to types, and the complete current and planned spectrum arrays.
7. Importing a Plan from JSON
- On the main dashboard toolbar, click Import Plan.
- Select a previously exported
.json plan file.
- The dashboard locates the matching market, opens the modal, and restores all edits, the plan name, and the date.
- You can continue editing, update the date, or re-export a revised version.
Note: Import matches by city name and state code. If the name doesn't match, you'll see an alert. Verify the spelling matches the dashboard data.
8. JSON File Format Reference
{
"planName": "Stephenville Q3 2026 D3.1 Migration",
"conversionDate": "2026-09-15", // or "TBD"
"exportedAt": "2026-03-18T12:34:56.789Z",
"market": {
"region": "Mid South",
"state": "TX",
"city": "Stephenville",
"forwardMHz": 1200,
"returnMHz": 85,
"cmts": "CMTS-StephenvilleTX"
},
"totalChanges": 12,
"changes": [
{ "channelIndex":47, "frequency":339,
"eia":42, "fromType":"AV",
"toType":"D3.1" }
],
"currentSpectrum": [ /* 192 entries */ ],
"plannedSpectrum": [ /* 192 entries */ ]
}
conversionDate is either YYYY-MM-DD or "TBD" if no date was set.
changes is the convenience diff with channel index, frequency, EIA number, and from/to type codes.
currentSpectrum / plannedSpectrum are the full 192-element arrays, making each file completely self-contained.
9. Recommended Workflow
Create
→
Export
→
Share
→
Review
→
Revise
→
Final
- Identify the market. Filter to region/state, click the market row.
- Duplicate the lineup. Click "Duplicate for Planning."
- Make changes. Use Click to Cycle for precision or Paint Mode for bulk.
- Name the plan and set the date. Use TBD if pending approval.
- Review. Toggle between Side by Side and Inline Diff.
- Export. Download the JSON file.
- Share for review. Email or upload to shared location.
- Reviewer imports. Opens dashboard, clicks Import Plan, selects the file.
- Iterate. Edit further, update date, re-export if needed.
10. Tips and Troubleshooting
All editing happens in your browser. Nothing saves to a server. Always export before closing the page.
Multiple plans for one market? Yes. Each export is standalone. Name them for different scenarios.
Closed without exporting? The plan is lost. Always export first.
Import says "Market not found"? City and state in the JSON must exactly match the dashboard data. Check for trailing spaces.
Can I switch editing modes mid-session? Yes. Toggle freely between Click to Cycle and Paint Mode. Edits are preserved.
Keyboard: Press Esc to close modals or this help panel.