Learn how Rana4 works and how to use the platform.
Rana4 is a structured scheduling platform that lets you define standards, build fragment networks (fragnets), model activities with dual durations (best and likely), and export deterministic schedules. It is designed for programme and project control where consistency and traceability matter.
A fragnet (fragment network) is a set of activities and relationships that belong to a single standard. You create fragnets per standard, add activities with codes and durations, and link them with predecessor-successor relationships (FS, SS, FF, SF). Fragnets are the unit of export: you choose a fragnet and a duration scenario to download a ZIP with an Excel workbook (TASK, TASKPRED, optional RSRC) and an XER containing the project shell, WBS, resources, and activity code definitions. TASK rows use stable WBS path strings, a comma-separated resource_list aligned with the rate card / XER resources, and optional actv_code_…_id columns for semantic activity code values. If you have uploaded a rate card, the workbook also includes an RSRC sheet (resource definitions in Primavera layout).
Each activity has two duration fields: best and likely. When you export, you choose a scenario: "best" uses the best duration for every activity in the export; "likely" uses the likely duration. This supports dual-duration modelling for risk and scenario analysis without changing the structure of the schedule.
Go to Export in the app, select a standard and then a fragnet, and choose the scenario (best or likely). Click download to get a ZIP with Excel (TASK, TASKPRED, RSRC when a rate card is present) plus XER for structure and activity code metadata. Activity IDs in the export are deterministically mapped (e.g. A1000, A1001) so the same fragnet always produces the same IDs.