TR
Go to App
Product
Overview SystemsSolutionsIV-INPROIV-PROJECTIV-FINANCEIV-SCHEDULEPricing
Docs
Overview API ReferenceZIYA System AssistantSecurity
PilotContact
TR
Go to App
IV-SCHEDULE Pilot Stage

IV-SCHEDULE — Scheduling and Critical Path Control

Manages work packages, dates, duration, dependencies and critical path calculation in its own system boundary, separate from IV-PROJECT's cost and progress-payment decisions. It shares only verified time, deviation and progress signal with IV-PROJECT.

Who Is It For?

IV-SCHEDULE is for project planners, site chiefs and technical offices who need scheduling depth that goes beyond IV-PROJECT's cost/progress-payment core. Teams already using IV-PROJECT license this separately to run critical path and dependency management on the same data model.

  • Project planners and technical offices — Work package, duration, dependency and critical path calculation
  • Site chiefs and field teams — Short-term lookahead and field progress feedback
  • Project managers (alongside IV-PROJECT) — Carries verified time and deviation signal into the decision package
  • Teams using XER files — Bring an existing schedule in through controlled import

IV-SCHEDULE Overview

Stage

Pilot

First Output

Critical path and deviation report

Data Sources

XER, manual, MSP XML

Price

Set together during pilot

Request Pilot

Features

The evidence layer for critical path and dependency management

Critical Path (CPM) Engine

Calculates duration, dependency and float for work packages using critical path logic, flagging activities at risk of delay.

Dependency Management

Supports start-to-start, finish-to-finish, finish-to-start and start-to-finish (SS/FF/FS/SF) relationship types.

Baseline Tracking

Tracks deviation against the approved baseline. Multi-baseline version comparison is on the roadmap (Phase 2).

Resource Load Visibility

Shows activity-level resource load. Automated resource leveling is not yet in scope.

Field Progress / Lookahead

Feeds field progress signal back into the schedule and presents a short-term lookahead view.

XER Import

Imports schedule files in XER format. Binary .mpp support is handled as a separate technical phase.

Workflow

How a critical path check happens in IV-SCHEDULE

  1. Schedule Data Entry — Activity, WBS, date, duration and dependency data is entered manually or via XER import.
  2. Dependencies and Baseline — Relationship types are defined and the baseline is locked with authorized approval.
  3. Critical Path Calculation — The CPM engine calculates the critical path and float.
  4. Deviation Check — Deviation and delay signals are generated against the baseline.
  5. IV-PROJECT Signal — Verified time and progress signal is passed to IV-PROJECT; cost and progress-payment decisions stay there.
  6. Trace Record — Schedule changes and approvals are kept as an auditable record.

System Boundary

What IV-SCHEDULE is not

IV-SCHEDULE does not produce project cost, progress-payment or cash flow decisions — those stay within IV-PROJECT's boundary. It does not produce formal drawings, BIM or CAD output. Here too, ZIYA only provides suggestions and a second opinion; ZIYA does not set the critical path, the baseline, or an approval — that authority stays with the authorized user.

  • Resource leveling and multi-baseline version comparison are currently on the roadmap (Phase 2).
  • Binary .mpp import is not yet supported; XER and MSP XML imports are the supported schedule paths today.
  • IV-SCHEDULE does not replace IV-PROJECT; the two work together as separately licensed systems.

Related Content

Evidence-backed pages for project cost and field control

IV-PROJECT

Project budget, progress payment and resource cost control — the system that carries IV-SCHEDULE's time signal into the decision package.

Pilot Program

Apply to run IV-SCHEDULE alongside IV-PROJECT on a live project.

Start a pilot with IV-SCHEDULE

Turn your critical path, dependency and baseline data into a verified time signal connected to IV-PROJECT.