Product case study
From $24 / monthTwo XER files in, a complete weekly progress report out — still on your machine.
Qiyas reads last week’s Primavera P6 export and this week’s export, matches activities by code, and lists everything that moved in the period. A licence unlocks the browser tool; after the engine arrives, neither file is uploaded.
Every update cycle a planner exports this week and last week, then hunts through P6, Claim Digger, or a spreadsheet for what finished, what started, what slipped, and what was added. The question is contractual and weekly. The tools that answer it are either inside a P6 licence, cloud services that cannot see the file, or a manual diff that nobody has time to finish before the meeting.
Qiyas does not rerun CPM. It reports the difference already stored in the two files: status, remaining duration, finish dates, constraints, relationships, and total float. That is honest, and it is enough for a weekly report.
Activities are paired on task code, with the internal id only as a fallback when the code is empty. Added and deleted rows are the ones that did not pair.
Finished, started, progressed, finish slips and pull-ins, adds and deletes, duration and constraint changes, relationship edits, float erosion, and activities that crossed zero total float. Excel gets one sheet per section; CSV and print cover the same lists.
After a licence unlocks the engine, both XER files stay in the browser. Nothing is uploaded and nothing is kept on the server.
The first version produces a period narrative, eight headline counts, and sixteen expandable sections, with Excel, a combined CSV, per-section CSV, a copyable summary, and a printable report. Multi-project exports can pick a project on each side. Dates can be shown in the Jalali calendar.
Product definition, schedule-domain comparison rules, XER parsing, Excel export, interface design.
A licence unlocks the browser tool, updates, and support. Toumar turns the same two-file difference into an evidence pack for a delay or EOT letter. Shaghool remains the health-audit companion for a single file.