BMS Point Schedule & I/O Planner
Build point lists, count signal requirements and assign controllers without choosing a manufacturer.
Loading planner…
1 · Project
Changes stay in this tab only. Download JSON to keep controllers and settings; CSV stores points only. Extra channels = ceil(point count × allowance / 100), calculated separately for each I/O type.
2 · Equipment & points
Duplicate equipment
Copies keep point specifications, clear controller/terminal assignments and use at least two digits. Existing equipment names are rejected.
Paste from Excel / import CSV
Include these eight headers (any order): equipment, point, connection, type, signal, controller, terminal, notes. One row = one point. Connection: Hardwired or BACnet. Type: AI/AO/BI/BO (BACnet value categories do not consume physical channels).
Import appends atomically; it does not create controllers. Register imported controller names below. Maximum 5,000 points, 200 controllers and 3 MB per file.
3 · Optional controller inventory
Enter unique names. Blank capacity means unknown; zero means no channels. AI/BI/AO/BO counts are dedicated pools. UI is a separate shared AI/BI input pool: do not count those channels again as dedicated inputs. UIO output sharing and expansion bus/power limits are outside this prototype.
| Name | AI | BI | UI shared | AO | BO | Supported signals (optional) | Action |
|---|
Optional signal list uses semicolons, for example: Pt1000; 4–20mA; 0–10V. A match only confirms membership in your list, not terminal-specific compatibility. Renaming a controller updates its point assignments.
4 · Point schedule
| Equipment | Point name | Connection | I/O / value type | Signal / curve | Controller | Terminal | Notes |
|---|
Add equipment, a blank point, or import a schedule to start.
Filters affect the schedule and CSV export. Project totals include every row. One physical terminal per point; terminal labels are free text. Assign equipment in bulk by filtering, selecting rows and choosing a controller. BACnet rows need no physical terminal.
5 · Project requirements
Hardwired signals
Controller capacity review
Schedule checks
Checks cover missing fields, duplicate names/terminals, unregistered controllers and entered signal lists. No issues does not mean the design or wiring is approved. Fixing a signal list mismatch does not establish electrical compatibility.
Method, assumptions & limitations
Physical I/O is counted from Hardwired rows only. BACnet analog/binary input/output categories are integration records, not physical channel requirements. Feedback requires its own row. Counts include incomplete rows when their type is known; incomplete rows remain flagged.
Input pool shortfall = max(0, max(0, AI demand − dedicated AI) + max(0, BI demand − dedicated BI) − shared UI). UI is counted once. Input checking requires all three capacities to be known. AO/BO are checked independently. This checks available counts, not actual terminal mapping or signal ratings.
Exported formula-leading spreadsheet cells receive a leading apostrophe. Reimport restores that prefix for supported round trips. CSV preserves point rows only. Project JSON preserves all points, inventory and allowance. Nothing is uploaded or saved automatically.
Prototype specification and verification · Engineering disclaimer