The vocabulary LogicReader uses, and what we mean by it. We try to use plain language where we can; some terms come from CPM scheduling and we keep them rather than invent new ones. Where we use a word in a non-standard way, we say so explicitly.
Schedule vocabulary
- Activity — a unit of work in the schedule. P6 calls these tasks; we use the planner-friendlier “activity.”
- Dependency (or relationship, or link) — a directed connection from one activity to another, indicating that the second cannot start (or finish) until the first does.
- WBS (Work Breakdown Structure) — the hierarchical grouping of activities into phases, areas, disciplines.
- Critical path — the longest chain of activities through the schedule. Any delay along this chain shifts the project finish.
- Total float — the amount an activity can be delayed without delaying the project finish.
- Free float — the amount an activity can be delayed without delaying its immediate successors.
- FS / SS / FF / SF — the four standard P6 relationship types: Finish-to-Start, Start-to-Start, Finish-to-Finish, Start-to-Finish.
- Lag — a delay (positive) or overlap (negative) added to a dependency.
LogicReader vocabulary
- Network view — the main canvas. Activities as nodes, dependencies as arrows. The default LogicReader view.
- Time-positioned layout — activities are placed left-to-right by their planned start date. Reads like a Gantt chart but with every cross-link a Gantt chart hides.
- Isolate — remove everything from the canvas except the selected activities (and their dependencies). See Isolate mode.
- Compare — load two revisions of the same schedule and overlay the differences in green / red / amber. See Compare two revisions.
- Level-of-detail (LOD) — the renderer simplifies as you zoom out so the canvas stays interactive on very large schedules. Automatic, no setting required.
Vocabulary you’ll see soon
These terms are on the roadmap and worth knowing now:
- Typed dependency — a link that carries its kind (technical, resource, information, safety, commercial, preference, interface), an owner, and a confidence band. The reasoning behind a logic link, written on the link itself.
- Decision memory — a layer attached to activities and links that captures why they are the way they are. The audit trail a senior planner has carried in their head, finally written down.
- Resource flow view — where people, plant and materials actually move across the schedule. A first-class view, not a filter.
- Ghost activity / link — a what-if proposal that lives in a separate state from the source schedule. Promoted to real, archived, or rejected.
- Buffer node — an explicit, first-class buffer in the graph (project, feeding, or resource buffer), with a consumption percentage and a status band.
Words we deliberately don’t use
- “AI-powered.” Some of LogicReader’s roadmap features will involve large-language-model help (parsing a tender into a starting WBS, for instance). We’ll describe what they do, not advertise the engine.
- “Real-time collaboration.” LogicReader today is single-user-per-session. Multi-user is V2.
- “Replaces P6.” We do not replace your scheduling engine. We make the logic in your schedule legible.