Planning & Scheduling

Establishes the project schedule by creating logical dependencies between activities to form an activity network, then running a scheduling calculation in Project Scheduler or Project Gantt. Dependency types (FS, FF, SS, SF with lag) and activity constraints (Start Not Earlier Than, Must Start On, etc.) drive the calculation of early/late dates, float and the critical path.

Plans resource demand by assigning resource groups (with planned hours, cost and capacity) to activities, then allocates specific resources (persons, machines, tools, crews) to satisfy that demand. Allocations can be by hours or percentage of available time, fixed or activity-duration-bound, and support self-allocation via My Project Allocations.

Uses Project Gantt to visualize the project schedule and activity network based on early dates, edit the plan interactively, and run scheduling calculations. Dragging activity bars updates early start/finish dates, and critical activities are highlighted after a scheduling run.

Creates project baselines that snapshot planned hours, cost and Early Start/Finish dates as the reference plan against which execution is measured. Multiple baselines can be set as scope, schedule or cost change, and the selected Earned Value Method determines whether earned value and scheduled work are calculated on baseline or planned values.

Captures activity progress using a configured progress method (Duration, Template, Manual, Consumption Based, Tasks, Connected Objects) and updates actual start/finish dates. Actual dates lock scheduling for those activities, and rescheduling recalculates remaining early/late dates and float across the dependent network.

Turns the construction WBS into a logic-linked, resourced and baselined programme inside IFS Cloud, or keeps IFS aligned with a programme owned in Primavera P6 or Microsoft Project. Activity dependencies form the network that IFS Project Scheduler uses to calculate early and late dates, float and the critical path, and the accepted baseline becomes the reference for progress, delay and extension of time claims. This is the process that decides whether IFS is the planning tool or the system of record for a programme planned elsewhere.

Turns the network build strategy into a funded, resourced and sequenced rollout programme covering site counts, regions, capital phasing and delivery partners. In IFS Cloud the programme is a Project hierarchy with standard site Sub Projects, baselined cost and revenue plans, and resource demand that feeds scheduling and procurement. It gives the telecom CFO and programme director a single view of committed and forecast capital across labour, subcontract, material and equipment.