Modules
Five packs, twenty-four modules: twenty-three applications that carry the project, and one exchange layer that keeps them agreeing.
Each module is installed and run on its own. They agree with one another because they exchange documents through Link, not because they were bolted into one oversized program. They are grouped into five packs by the work they cover; a pack, or a single module, can be adopted on its own.
Pack 1
Plan and Estimate
From the FEED gate to a priced, scheduled bid.
VRFEED, VREST, VRSCH, VRPreCon, VRTAR, VRPlanner
FEED tracking
VRFEED
Front-end engineering design through the sanction gates. Gate readiness is scored rather than asserted, and the estimate carries the class it was actually built to.
Gate readiness
Readiness scoring across G0 to G3, so a sanction gate is argued from evidence rather than from a date.
Deliverables
FEED deliverables tracked against a 21-milestone skeleton.
Optioneering
A study register recording the options considered and the basis on which each was carried or dropped.
Estimate basis
The estimate basis recorded by AACE class, so the accuracy being relied on is stated.
Duration benchmark
A three-method FEED duration benchmark against the schedule the gate is being asked to accept.
Pre-FID risk
The pre-FID risk register carried into the sanction decision instead of alongside it.
Estimating
VREST
Discipline takeoff and cost estimating for industrial piping, equipment, engineering and construction scope — the workbook discipline this whole suite grew out of. Every discipline carries three possible methods, and only the one you select feeds the rollup, so the basis of the number is never in doubt. The budget is handed forward to PCS and Cost rather than retyped.
Methods
Parametric, known quantity and detailed takeoff sit side by side per discipline. Only the active method contributes direct cost, man-hours, labor and material; selecting detailed takeoff is refused if no takeoff lines exist.
Takeoff
Line-level quantities against library keys, with discipline, global and item factors, weld factors and craft assignment, priced at all-in craft rates.
Library
Man-hour library, weld factors, craft rates and material prices, each row carrying its source. Values generated for the demonstration are labelled as such.
Indirects
A code-of-accounts build-up from direct cost to total installed cost — EPCM, field indirects, owner cost, escalation and contingency, shown as a waterfall.
Engineering
FEED and detail phase man-hours, or a factored EPCM percentage. A double-count guard keeps only one engineering source live at a time.
Benchmark
An independent man-hour-per-USD-1,000 intensity cross-check against the built-up hours, with variance beyond ±20 per cent flagged.
Proposal
Estimate class, accuracy range, pricing basis and the fee to produce the estimate, with status moving Draft to In Review to Issued.
QA gate & audit
An estimate cannot be marked Issued while quality checks are open, and every method switch, line edit and status change is written to the audit trail.
PDF takeoff
Count, length and area measured on the drawing itself after setting its scale.
Estimate register
Several estimates kept side by side: start a new one blank or as a copy of the open estimate, and reopen working or issued (historical) estimates from one list.
Bid Desk
Drawing sets and spec books indexed by sheet and MasterFormat section; tag, member-size and symbol counts reviewed hit by hit and posted as takeoff lines, with steel tonnage from weight per foot; trade scope sheets to Excel; checks for missing sheets and spec sections that raise RFIs; a weighted go / no-go score. Rule-based, in the browser.
Benchmark intensities and library man-hours shown in the demonstration were generated for it and are not drawn from any proprietary man-hour manual.
Scheduling and schedule analysis
VRSCH
Schedule development, analysis and maintenance alongside the Primavera P6 data the rest of the suite consumes, keeping activity structure aligned to the work breakdown structure that progress is measured against. A native schedule editor builds the CPM network in VissRad itself — activities, WBS, calendars with holidays, FS/SS/FF/SF logic with lags, constraints, progress at a data date and a baseline — recalculates the critical path on every change and exports to P6 XER or Microsoft Project XML when a client needs one. The same analysis views run over a schedule built here or one imported from P6, so the schedule conversation happens on evidence rather than opinion.
Schedule editor
Grid and bar chart side by side: type durations and predecessors such as A1010SS+2, and the forward and backward pass, total float and critical path update as you go. Choose the columns shown, roll up to any WBS level, and read the date under the pointer on the bar chart. Undo and redo, open-end and loop checks.
Cover sheet
Project, data date, baseline and the headline dates and durations the rest of the views are measured against.
S-curve and FTE curve
Planned, earned and actual curves on one dated axis, with the baseline retained for comparison. Alongside it, a weekly or monthly resource curve in FTE or hours from the labor assignments, filtered by discipline and contractor where the schedule codes them. Move the pointer over either chart for the values at that date.
Earned value
PV, EV, AC and BL with CPI and SPI derived from the same activity set, not re-entered.
Critical path
The driving path with total float, so the activities that actually move the finish date are visible.
Float distribution
How much float the schedule is carrying and where, which is usually the first sign of a schedule built to please.
Milestones
Contract and internal milestones with variance against baseline finish.
Look-ahead plan
A rolling window for the field, generated from the same schedule rather than maintained separately.
WBS summary & quality
WBS rollup alongside schedule quality checks — open ends, negative float, constraints and logic gaps.
CPM check
A forward and backward pass over the file’s own logic, compared with the dates P6 reported. Redundant links — finish-to-start links already implied by another path — are listed for review.
DCMA 14-point
The fourteen schedule-quality checks with thresholds you can set. An assessment, not a certified schedule audit.
Baselines
Baselines kept alongside the current schedule and compared by activity and by finish; the DCMA checks use the active one.
Compare versions
Two updates of a schedule compared by Activity ID: activities and relationships added and deleted, durations, calendars and constraints changed, actual dates altered after they were recorded, and the finish movement. A half-step analysis, after AACE RP 29R-03, splits that movement into the part caused by progress and the part caused by revisions to the plan. It splits the movement; it does not assign responsibility.
What-if scenarios
Named copies of the plan saved beside it, edited separately and compared with the plan of record, so an acceleration or a change of method can be tested without touching the schedule of record.
Risk (Monte Carlo)
Triangular duration ranges run through the network to P10, P50 and P80 finish dates, and the cost at completion with them.
Resource levelling
Limits from the file’s resource rates or typed in, with before and after histograms and the activities delayed. A serial heuristic: it will not reproduce P6’s levelling exactly.
Resource files
Resources, limits and assignments are read from P6 and Microsoft Project XML. A separate resource file — P6 XML, .xer, MSP XML, Excel or CSV — can be added to a schedule and is matched by Activity ID, so a schedule exported without resources can still be levelled and resource-loaded.
Schedule library
A schedule loaded once is kept in the browser and offered as a selectable source in VRSCH, VRConstruction and the Link data sources, rather than being opened again in each module.
Preconstruction
VRPreCon
Making a sanctioned project buildable. Constructability, contracting, procurement float, craft labor, logistics and permits, ending in a mobilisation readiness case rather than a start date.
Constructability
Reviews recorded with the comments raised and where each one landed in the design.
Contracting strategy
The contracting strategy and the bid packages it breaks into.
Long-lead procurement
Long-lead items tracked with float to need-by, so a slipping order is visible while it can still be recovered.
Craft labor & logistics
Craft labor build-up and site logistics for the execution window.
Permits
The permit register and its status against the works each permit gates.
Mobilisation readiness
A readiness case that states what is in place and what is not before anyone mobilises.
Bid levelling
Bids side by side, with exclusions priced at plug values, a technical pass mark and a recommendation. Bidders not prequalified in VRARAP are flagged and not recommended. The award goes to VRCost as a commitment.
Bidder portal
On VissRad Server, each bidder gets a single-use link to the package, its scope items and its documents, and submits a base bid, exclusions and clarifications straight into the levelling sheet. Bidders never see the estimate or the other bids.
Turnaround estimating
VRTAR
Turnaround scope is estimated one item at a time from a module library. Each module asks its own short set of questions — the size of the exchanger, whether the bundle is pulled, how many tubes are plugged — and the answers switch tasks on and off and drive the formulas for duration, crew, equipment and material. Every scope item on the worklist keeps its answers, so the whole event can be re-priced by changing a rate or an answer rather than by re-keying an estimate.
Module wizard
Numbered scope questions and sizing variables are asked one at a time, and only the questions that still matter are shown. A live estimate follows every answer before the item is added to the worklist.
Fragnet per scope item
Tasks carry logic, so each item produces a fragnet with its critical path. The worklist rolls onto the turnaround clock from feed-out, with the driving item and the window shown against each other. Every item sits in one of 187 standard refinery and chemical plant units, from crude, conversion and sulfur recovery to olefins, polymers, utilities and offsites, and the unit becomes its P6 WBS node.
Material estimating
Modules carry material quantity formulas priced from a site price book with waste allowances. Quoted or owner-furnished items are added per scope item, and the event material take-off is grouped by item with tax and freight.
Crews and manpower
Crafts and equipment are held in a resource manager with rates and a site productivity factor. The event produces a manpower histogram by shift and a resource summary by craft.
Module Editor
Questions, tasks, crews, logic and material lines are authored and validated in the browser, test-run against default answers and saved to the library. Estimating-tool Excel exports can be imported as a starting point.
Exports
Estimate and event workbooks, CSV, Primavera P6 XER, MPX, SAP PM operation lists, the material take-off and a printable field worksheet per scope item.
No sign-in. The library, worklist and price book are held in the browser on the computer running it.
Capital work planning
VRPlanner
The work of a capital project is planned before it is loaded into the schedule. Each work item — a run of pipe rack piles, an area of spools, a substation lineup — is stepped out from a module that asks its own questions, and the answers give the work steps, the crew size by craft, the equipment, the hours and the materials. Work items are sequenced on the project's working calendar, the manpower and equipment loading follows, and the plan goes into the schedule as activities with logic and resources rather than as a list to be keyed again.
Step-out
Civil, structural steel, piping, mechanical equipment, electrical, instrumentation, coatings and insulation, access and completions modules. Only the questions that still matter are asked, and the work steps, duration, hours and cost follow every answer before the item is added.
Crews and equipment
Each step carries its crew by craft and its equipment units. Craft productivity factors and rates are held in a resource manager, and crafts can be tied to the suite resource library so the rates in force on the planned start are used.
Logic on a working calendar
Steps within an item carry their own logic; a work item starts after the items it follows and not before its earliest working day. Durations are laid out on the project's hours a day and working days a week, against a target finish, with the driving item shown.
Loading
Manpower by working day and craft, equipment on the job per working day, and a craft and equipment requirement with peaks. Labor hours, material and cost roll up by area, with deferred items left out.
Into the schedule
The plan is added to the schedule open in the Schedule Editor under the WBS node chosen, with clashing activity IDs renamed and one undo to take it out, or opened as a new schedule. Its crafts and equipment become resource assignments in hours.
Load files
Primavera P6 XER with the project calendar, the WBS by area and work package, planned dates, logic, resources with rates and assignments; MPX for Microsoft Project; a project workbook, a steps CSV and the material take-off. VRConstruction takes the XER for P6 delivery and field status.
No sign-in. The library, work items and price book are held in the browser on the computer running it. The demonstration project is synthetic.
Pack 2
Control
Progress, cost, change and payment held to one record.
VRPCS, VRCost, VRChange, VRERP, VRARAP
Project controls
VRPCS
One project per .vrpcs file. Progress, completions, certification and cost live in the same record, so a certificate cannot be issued against work the field never signed off, and a forecast cannot ignore a commitment that has already been placed.
Project health
A single dashboard for schedule, progress, cost and certification status with the current blockers surfaced rather than buried.
Completions
Unit to system to subsystem hierarchy, a tag register, ITRs, and punch items graded A through D.
Certificates
MCC, RFCC and RFSU packs that show their live blockers — outstanding ITRs and category A and B punch — before anyone signs.
Progress & earned value
Progress by WBS, discipline and unit of measure, with weighted rule-of-credit steps, a performance factor, CPI, and shift-by-shift quantity entry.
Cost
Cost report, commitments, changes and trends, cash flow and forecast, with CPI, EAC and VAC computed from the same actuals.
Forecasting
Five estimate-at-completion methods — CPI performance, remaining-to-plan, full reforecast, manual ETC with a mandatory written reason, and committed plus remaining — alongside a contingency drawdown register.
Schedule data arrives as a Primavera P6 CSV export requiring activity ID, start date and finish date. Unmatched activities are reported, not absorbed.
Cost management
VRCost
A cost breakdown structure with a locked original budget, commitments, actuals, change management, pay applications and forecasting — the EcoSys-shaped discipline, sized for a project team rather than an enterprise rollout. It extends the same cost engine PCS reports from.
Twelve views
Dashboard, Structure, Budgets, Commitments, Actuals, Changes, T&M Tickets, Pay Applications, Forecast, Earned Value, Risk & FX and Reports.
Change control
Trends and approved changes move the control budget explicitly, with the original budget preserved for comparison.
Forecast
Forecast at completion by cost account, reconciled against committed value and remaining scope.
Earned value
The same CPI, SPI, EAC and VAC definitions used across the suite — not a second, differently-defined set.
Pay applications
Schedule of values and continuation sheet in the G702/G703 layout. On VissRad Server the owner’s representative can approve or reject by a single-use link; it is applied only if the figures are unchanged.
T&M tickets
Labor priced from resource rates, materials and equipment, a field signature, and a link to the change and cost account.
Risk & FX
Commitments in any currency with a monthly rate table, FX exposure, forward cover and a reporting-currency view, plus a cost Monte Carlo that can take its delay from the schedule risk run.
Change management, trend to incorporation
VRChange
The change register of the project: trends, change notices, change orders, variations and claims. Each change carries its reason, an estimate build-up of labor, material, equipment, subcontract and indirects, and the schedule effect. It is routed for approval by delegation of authority, and every decision is recorded. Approved changes pass to VRPCS to be incorporated into the budget and forecast. Management of change for plant modifications runs alongside.
Incoming
RFIs answered with cost or schedule impact and VRDEng design changes wait in one queue to be raised as changes, with the project, discipline, cost and days filled in. The change number shows back on the RFI.
Approvals
The route is set by value and schedule effect from the delegation-of-authority matrix. Each approver approves or rejects with a comment; the build-up is locked once submitted and recalled to re-estimate.
Change orders and exposure
Client and subcontract change orders with their commercial terms, and the pending exposure by status and reason, weighted by probability, against what is already approved and incorporated.
Management of change
Plant modifications with a risk ranking and a checklist: hazard review, P&IDs and process safety information, relief, area classification, procedures, training and the pre-start-up safety review. Temporary changes carry an expiry date.
Financial & management accounting
VRERP
General ledger, accounts payable and receivable, cost centre accounting and internal orders, driven from a Ctrl+K transaction-code command bar with /n and /o prefixes and description search. It is the ledger the ARAP payment chain posts into, so a certified payment and its accounting entry are the same event.
GL documents
Header and line posting with document type, posting date, header text and balanced debit and credit.
Chart of accounts
The account master behind every posting, with account group and type driving where a balance lands.
Trial balance
Period and year-to-date balances that tie back to the documents that produced them.
AP and AR
Vendor and customer open items, ageing and clearing, fed by the ARAP invoice and certification chain.
Controlling
Cost centre accounting and internal orders, so project cost and financial cost reconcile rather than argue.
Period close
Posting-period control, balance carry-forward, the recurring-entry run and the ZCLOSECHK and ZRECON checks.
Audit
Every posting, clearing and close step recorded with user, timestamp and before-and-after values.
Scope, stated plainly
276 standard FI and CO transaction codes are catalogued; 66 of 280 screens are fully built. The rest are listed rather than implied.
Accounts payable & receivable
VRARAP
The payables desk, wired to the field. Progress claims are verified against certified quantities from PCS before they reach the approval queue, and retention is withheld and released against real certificates rather than a calendar.
Dashboards
AP and AR aging, cash forecast, approval bottlenecks, early-payment discount capture and DPO.
Matching
Three-way purchase order, receipt and invoice match, plus progress-claim verification against PCS field data.
Approval
A queue with delegation and escalation, so an absent approver is a routing event and not a two-week hold.
Retention
Withheld on invoice and released on certificate — the certificate, not the promise, is what moves the money.
Payment run
Exports NACHA, ISO 20022 pain.001, a check register CSV and a remittance advice PDF.
Coding
GL coding with line-total validation, and duplicate detection on invoice intake.
Prequalification
A questionnaire with scoring, safety statistics (TRIR, EMR), insurance and financial checks, and approval with an expiry date. VRPreCon checks it before recommending a bidder.
Payment files are format-correct but not bank-certified; demo output carries a “DEMO — NOT FOR TRANSMISSION” banner. Bulk invoice import from CSV and PDF is a labeled stub.
Pack 3
Engineer and Procure
Deliverables, documents, questions and materials, with VRMarkup on every drawing.
VRDEng, VRProCure, VRRFI · VRMarkup built in
Detailed engineering
VRDEng
Engineering to IFC. Deliverables are tracked by revision and issue code, man-hour progress is earned by rule of credit rather than claimed, and quantity growth is reported while it can still be priced.
Deliverable register
Every deliverable by revision and issue code — IFR, IFA, IFD, IFC and AB.
Drawings
The drawing for each deliverable, with pins for comments and RFIs placed on the sheet; an RFI pin can raise the RFI with the deliverable already filled in.
Document repository
Every controlled document in one list: deliverables, plant P&IDs, procedures and check-sheet forms, standards, O&M manuals, specification sections, vendor documents from VRProCure and FEED deliverables. Tags, assets, check sheets, RFIs, requisitions, MOCs and bid packages in the other modules link straight to the document and its file.
Man-hour progress
Man-hours earned by rule of credit against the deliverable register, not by percentage typed on a cover sheet.
Reviews & transmittals
Review and transmittal cycles, with the turnaround each one is actually taking.
Submittals
Shop drawings, product data, samples and test reports logged against specification sections and routed through a sequential review with stamps; a Revise or Reject stamp opens the next revision with the same workflow.
DEng RFI
The RFIs raised against the engineering, with ball in court, answer-by dates, cost and schedule impact and the RFI letters that go with them. Raised from a drawing or the tab; VRRFI keeps the log.
Correspondence
The project correspondence register: letters, notices, instructions and memos in and out, with reply threads, response tracking and references to RFIs, submittals and transmittals.
MTO quantity growth
Quantity growth between material take-offs, reported by discipline.
Changes & TQs
Changes and technical queries tracked against the deliverables they affect.
EWP handover
Engineering work package handover to the field, so packaging inherits issued drawings rather than drafts.
Drawing-set split
A multi-sheet PDF is split into the register by reading the drawing number, title and revision from the title block. It reads the PDF text layer; scanned sheets are not read.
Built into every module
VRMarkup
The drawing reader and markup editor inside the suite. It is not a separate module: any PDF attached to a record, and any drawing in VRDEng, opens in it, and it is the first entry in the suite bar on every page. Markups are kept with the record they belong to, and a markup can become an RFI, punch item, change or takeoff line without retyping.
Reading
Page thumbnails, zoom, fit width or page, rotate, pan and text search across every page. Scanned sheets with no text layer cannot be searched.
Markup tools
Pen, highlight, line, arrow, polyline, box, ellipse, polygon, revision cloud, callout, text box and review stamps that carry the author and date.
Measurement
Length, polylength, area and count at a chosen architectural, engineering or metric scale, or calibrated against a known dimension. The scale is kept with the document.
Markups list
Subject, status, author, date and comment for each markup, with measurement totals and CSV export.
Compare revisions
Another revision of the same document side by side, with page, zoom and scrolling linked.
Raise records from a markup
RFI, punch item or change from a selected markup, and takeoff lines from measurements, opened with the drawing and page filled in. The record number is written back onto the markup.
Output
Save PDF writes the markups onto the pages with a summary page; the marked-up copy can be attached back to the record, printed, or the original downloaded.
Phone and tablet
A touch layout with bottom-sheet panels, pinch zoom and touch pan for use in the field.
Procurement and material management
VRProCure
The supply chain for the project, from the engineering take-off to the material issued to the crew. Requisitions come from the VRDEng MTO and VRPreCon long-lead items rather than being keyed again, and every order is tracked to the date it is needed on site.
Incoming
MTO lines in VRDEng with no requisition, quantity growth since the last requisition, and VRPreCon long-lead items not yet requisitioned. One click raises the requisition with project, discipline, commodity, quantity and need date filled in.
Requisitions
Material requisitions with lines, need dates and revisions, approved before they go out to the market.
Enquiries & bids
Enquiries to prequalified suppliers, clarifications, and a bid tabulation weighted between commercial and technical scores. The recommended bid becomes a draft purchase order.
Purchase orders
Orders routed for approval by value under the delegation of authority, then issued with lines, terms and cost codes. Revisions and change orders carry the VRChange reference, and the commitment goes through Link to VRPCS, Cost, AWP and ARAP.
Expediting
Order milestones, forecast delivery against the required-on-site date and the float between them, with the vendor contact log. Orders at risk are listed first.
Vendor documents
The VDRL for each order: what each vendor owes, when it is due, and the review code on every return.
Inspection
Pre-inspection meetings, in-process inspection, factory acceptance tests and final release, with the punch items that hold a release note.
Logistics
Shipments from release to arrival on site, with mode, forwarder, bill of lading and oversize-load permits.
Receiving
Material receiving reports with accepted quantity, location and heat number, and over, short and damaged reports. Posted receipts feed the three-way match in VRARAP.
Material control
Site stock by warehouse and laydown, reservations and issues to VRAWP IWPs, IWP material readiness, preservation checks and heat-number traceability from receipt to the IWP it was issued to.
Suppliers
The supplier register with prequalification expiry, and performance calculated from the orders: on-time delivery, vendor documents on time, inspection first-pass rate, clean receipts (no over, short or damaged material) and win rate. A weighted score and an A–D grade follow from those measures, and the grade is shown against each bidder in the bid tabulation.
Requests for information, FEED to handover
VRRFI
The question-and-answer record of the project. RFIs and the letters that go with them each carry a ball in court and a due date, so the dashboard shows who is holding what and for how long. Every RFI carries its project phase, FEED through commissioning and handover. An RFI with cost or schedule impact asks VRDEng for a design change, and the link runs both ways.
RFIs
Question, assignees, distribution, response due date, official response and cost and schedule impact, with a full activity log.
Raised where the question arises
An RFI can be raised at any stage: from a FEED deliverable or study, a PreCon constructability finding, bid package, long-lead item or permit, a VRDEng drawing pin, a VRConstruction daily report, a VRAWP work package, or a VRSU&C system, punch item, package or certificate. The project, phase and reference are filled in.
RFI correspondence
The letters that go with an RFI at any stage: a formal notice of cost or schedule impact, a reminder of a late answer, a response under cover letter. Each letter carries its RFI and shows on the RFI, alongside any VRDEng project letter that references it.
Dashboard
Ball in court across RFIs and RFI letters, ageing of open RFIs, open and raised RFIs by project phase, cost and schedule exposure, and one list of everything overdue.
Design change link
A design change requested from an RFI appears on the VRDEng Changes & TQs tab; the change number shows back on the RFI once raised.
Pack 4
Execute
Work packages, worksteps, safety and sequence in the field.
VRAWP, VRConstruction, VRSHE, VR4D
Advanced work packaging
VRAWP
Construction work areas down to installation work packages, with a release gate that actually holds. An IWP is released when its constraints are clear — materials, drawings, access, permits, labor — not when the lookahead needs it to be.
Package hierarchy
CWA to CWP to EWP, PWP and IWP, with registers at each level and the path of construction sequence at the top.
Area map and packaging
A plot plan of every component, coloured by IWP status or readiness. Box-select unpackaged components to create an IWP, or use the rule-based packaging assistant to split a CWP by crew-week.
3D model and IFC
The same colours on a 3D view: a massing model drawn from the component register, or an imported IFC model whose elements link to components by GlobalId or tag. Shift-click unpackaged scope to create an IWP; unlinked elements can be added to the register.
Rule-linked constraints
Constraints are tied to their source: an EWP put under revision raises a change notice and holds the released IWPs; material received at site or a scaffold tagged as inspected clears the matching constraint.
Release gate
An IWP cannot be released with open blocking constraints or outstanding sign-offs from the planner, superintendent, safety and quality.
Scaffold
Scaffold requests linked to IWPs, from request through erection, inspection and tagging to dismantle, with shared scaffolds across disciplines.
Test and turnover
Components roll up to systems, test packs and turnover packages, with walkdown and hand-over status.
Field progress
Rules-of-credit progress by component step, planned against earned hours, schedule index and productivity by area.
Foreman view and P6 link
A tablet view of the week's IWPs for each foreman, a printable IWP pack, field-update files for work away from the network (imports only raise credit; conflicts are listed), XER import to update CWP windows, and a progress export for P6.
Meetings
Meeting minutes with actions that carry over to the next meeting until they are closed.
Construction planning and execution
VRConstruction
The step between an estimate and a schedule. Work packages are broken into worksteps from commodity templates — quantity times the template’s productivity rate gives the budget hours, crew size gives the duration — and everything the plan names is checked against the target Primavera P6 project as it was exported before a single row is written. What leaves is a plan P6 can take on the first attempt, in whichever form the deployment actually allows.
Deployment mode
REST where the database exposes it, a watched folder on a network where the Job Service is installed, or a spreadsheet imported by hand. The mode is chosen on entry and decides which write routes are offered, rather than promising a route the site cannot use.
Field execution
Daily construction reports with labor, equipment, weather and delays, crew timesheets and permits to work with the job safety analysis. An RFI can be raised from a daily report. The Safety tab shows the VRSHE summary and opens an incident or observation there with the area and company filled in.
Weekly work plan
Each foreman’s commitments for the week, linked to activities, with a readiness check on prerequisite work, materials, information, permit, crew and equipment. At the end of the week each line is marked done or not done with a reason; percent plan complete is tracked week by week against an 80 % target, with the reasons for misses ranked.
Worksteps from templates
Ten commodity templates carry the productivity rate, crew mix, rule-of-credit steps, calendar, WBS node and cost account. The planner sets how much work and how many crews, not the method.
Pre-flight gate
Every calendar, resource, cost account, WBS node and activity code value named in the plan is checked against the target project. A spreadsheet import will otherwise succeed quietly with the assignment missing, which is the failure nobody notices until the hours do not appear.
Work already done
Scope that was built before it was planned can be typed in with the plan — installed quantity and hours to date, with the dates it happened. Credit is derived from quantity or from the rule-of-credit steps, never accepted as a typed percentage.
Field sheets and returns
Sheets are issued by work package and come back as installed quantity and completed steps. The return carries who reported it and when it was captured, so a number can be traced to a sheet.
Writing to P6
XLSX to the published Oracle import field names, XER, P6 XML, CSV, Job Service actions XML, or a REST preview. The activity’s percent complete type decides which field carries progress — physical, units or remaining duration — because P6 calculates the rest.
Photos
Tagged construction photos grouped into albums by area, date or activity, with the time taken and GPS position where the file carries it.
Target project from a P6 export
The target P6 project is loaded from a .xer or P6 XML export — WBS, activities, calendars, resources, activity codes and UDFs — or picked from the schedule library, and kept in browser storage. The pre-flight gate checks the plan against that export instead of demonstration values.
Two passes, in order: the plan load creates the activities, the progress write statuses them. P6 cannot status an activity that does not exist yet, so the gate holds progress until the plan has been loaded.
Safety, health and environment
VRSHE
The site safety and environmental record. It took over the VRConstruction safety log, keeping each entry’s original number, and reads exposure hours, rain and permits from the daily reports, so the rates and the stormwater schedule are worked from the same numbers the field reported.
Incidents and recordability
Injury cases carry the OSHA questions: work-related, new case, then death, days away, restriction, medical treatment beyond first aid, loss of consciousness or a significant diagnosis. The answers classify the case and place it on the employer’s 300 log with a case number; first aid is the published list, anything else is medical treatment.
Severe-injury reporting
A fatality shows an eight-hour report-by time, an in-patient hospitalisation, amputation or loss of an eye a 24-hour one, counted from when the employer learned of it, until the report reference is entered.
Investigation and actions
Five whys, contributing factors and corrective actions with owners and due dates. Actions from incidents, observations, inspections and environmental events sit in one list; an incident cannot close with an action open.
Leading and lagging indicators
TRIR, DART and LTIR on the 200,000-hour base by employer and for the project, next to observations, at-risk topics, inspections on time, actions closed and training current.
Inspections, talks and training
Inspections scheduled from templates, a failed item raising an action. Toolbox talks with a printed sign-in sheet, offered to the daily report. A training matrix by worker and course with expiries.
Environmental
Spills and releases with the reporting test (oil reaching water or leaving a sheen, or a hazardous substance at its reportable quantity), hazardous waste generator category, container accumulation limits and manifests, stormwater inspections after rain, air and noise monitoring against limits, and permit obligations by due date.
OSHA logs
The 300 log and 300A summary equivalents by employer and year, printed or exported, with monthly hours and headcount checked against the daily reports, and the posting and electronic submission dates.
Records and photos
Photos, statements, reports and disposal records attached to the incident, observation, inspection or event they belong to, with an audit trail of every change.
The forms are equivalents laid out like the OSHA forms. State-plan states may add their own requirements; check the electronic submission list for your industry and size.
4D schedule visualization
VR4D
Schedule time painted onto a picture of the job. Give it one P6 schedule and one elevation drawing — no model required — and it will show the planned sequence, progress against plan, and the forecast, with the SPI and finish variance to argue from.
Two inputs
One P6 schedule in XER, XML, CSV or XLSX, and one elevation drawing. That is the whole setup.
Three modes
Planned sequence, progress versus plan, and forecast.
The numbers
SPI, finish variance, an S-curve and a full activity register alongside the visual.
Optional live 3D
Autodesk Platform Services translation of NWD, RVT, IFC and DWG to SVF2 with TimeLiner mapping, when your entitlements allow it.
IFC models and BCF
VR4D opens IFC2x3 and IFC4 files in the browser, colours them by IFC class, storey or schedule status, and raises BCF 2.1 issues with viewpoints (import and export).
Clash detection
Several IFC files shown together, each on or off. Clash tests between sets chosen by model and IFC class find hard clashes and clearance breaches, and are tracked to closure as BCF issues. Models are not aligned on load.
Standalone
VR4D runs on its own and does not require the Link exchange layer.
Pack 5
Turnover and Operate
Completions, certification and handover into maintenance.
VRSU&C, VRCMMS
Startup & commissioning
VRSU&C
Systemisation through to handover in eight working tabs, driving a gated certificate ladder. Nothing advances a gate on optimism — the check sheets and punch status decide.
The gate ladder
RVC to MCC to RFC to SCC to DCC to HOC, each gate holding until its evidence exists.
Eight tabs
Dashboard, Systemisation, Check Sheets, Punch List, Packages, Certificates, 3D Model, and Exports & Audit.
Navisworks, properly
A COM bridge to a running Navisworks session, plus file exchange — search-set XML, appearance profiles, TimeLiner CSV and a DataTools ODBC definition.
Browser viewer
A Three.js viewer for reviewing system coloring without a Navisworks seat on every desk.
Inspections
General field inspections, with failed items raised straight to punch.
Package rules
Completion packages built by rule from system, subsystem and discipline, each with a readiness survey and a gate check.
Handover dataset
The turnover records exported as one ZIP from the Exports tab.
Maintenance management
VRCMMS
The maintenance system that starts at turnover. Instead of keying the asset register in after handover, VRCMMS builds it from the SU&C tag register, so the owner’s maintenance team inherits the same tags, systems and certificates the completions team closed out.
Handover from SU&C
Assets imported by subsystem once received. RVC, MCC and RFC set asset status, and RFC switches preservation routines to operations PMs, with maintenance readiness and craft hours per year.
Assets and locations
Site, area, system and subsystem hierarchy, with asset classes, meters, spares and full repair history per tag.
Work orders
Requests to approved, planned, scheduled, in progress, complete and closed. Corrective work needs problem, cause and remedy codes; parts are issued from stores on completion.
Preventive maintenance
Time- and meter-based plans for the preservation and operations phases. Due work orders are generated without duplicating open ones, and each plan rolls forward on completion.
Planning and backlog
Backlog hours against craft capacity, a weekly schedule and a library of standard job plans with labor, parts and safety steps.
Inventory and reliability
Stores with min/max reorder and a transaction log; failure Pareto by problem and cause, with mean time between failures and to repair.
QR asset labels
Labels printed at 50×25, 70×36 or 100×50 mm with the asset number and a QR code. Scanned with a phone camera, the code opens the asset with its history and open work; Scan asset reads labels with a device camera where the browser supports it, or takes a typed number or a handheld scanner.
Across every pack
Portfolio, reporting and exchange
The view above the packs, the reporting out of them, and the layer that keeps them agreeing.
VRPortfolio, VRBI, VRAI, VRLink
Portfolio health
VRPortfolio
The overview that sits above every other module. Stage-gate pipeline health, the cost and forecast position, schedule and earned value, and the risk and readiness exceptions that need a decision this week — across all five delivery phases: FEED, preconstruction, detailed engineering, execution and commissioning.
Dashboard
The portfolio position in one view — pipeline, cost, schedule and the exceptions that need a decision this week.
Delivery phases
FEED, preconstruction, detailed engineering, execution and commissioning, each reported in the same terms.
Stage-gate pipeline
Where every project sits in the gate sequence, and what is holding the next gate.
Cost & forecast
The cost and forecast position across the portfolio, on the same definitions the project modules use.
Schedule & earned value
Schedule status and earned value rolled up from the projects rather than restated by hand.
Risk & exceptions
Risk and readiness exceptions raised to the level where the decision can actually be taken.
Project detail
The single-project drill-down behind any line in the portfolio view.
Audit
The record of what changed, when, and on whose entry.
Craft workforce
Planned headcount by craft across every project, taken from each schedule’s resource loading and set against the craft available.
Reporting & exports
VRBI
The reporting layer over the star-schema exports — project, portfolio and executive views built on the same facts the applications wrote, with Power BI and Excel reading through ODBC. Nothing here re-derives a number; it reads the fact tables the other applications produced and shows when each one was last refreshed.
Dashboard
The state of the reporting estate — families, pages, refresh status and the period each set of numbers belongs to.
Schema
The star-schema model itself: fact and dimension tables, keys and cardinality, published so a reporting team can build against it.
Man-hour loading
Hours by month and discipline, drawn from the progress and schedule facts rather than a separate spreadsheet.
EVA
Earned value analysis over the same cost and progress facts the Cost and PCS applications wrote.
Controls
The controls pack — progress, cost and schedule indicators in the format a monthly report expects.
Report families
Reports grouped into families with their route, page count and status, so ownership of each report is explicit.
Pipeline
Refresh state per dataset with period, last-refreshed time, source path and who ran it.
Downloads
Exports for Power BI and Excel, produced from the published schema rather than hand-assembled.
Project assistant
VRAI
Questions about the project, answered from the project’s own records. VRAI looks the answer up in the other modules — RFIs, the deliverable register, commitments, punch, packages — and quotes the record numbers it used, so every figure can be checked in the module it came from. It reads; it does not change records.
- Hosted workspace — behind the same sign-in as the rest of VissRad Server; the workspace key stays on the server and each person sees only the projects and modules they can open
- Single computer — optional, with your own key for any OpenAI-compatible service, or a model running locally with Ollama
- Shows its work — each answer lists the modules and tables it read
- Research desk — the VissRad Computer application for document research online with citations, or offline over an index of your own PDFs, workbooks and XER files
The public demo does not call a language model. You supply the model key; nothing is routed through VissRad.
Exchange layer
VRLink
Link is not an application at all. It is the outbox, inbox, document schema and transports that make the applications behave as one system — a certified quantity leaving PCS arrives in Cost as the same document, with the same identity, or it fails loudly and waits.
Dashboard
Queue depth, in-flight, acked and failed counts across every flow, with the last error visible rather than buried.
Outbox and inbox
Every document with its type, route, idempotency key, attempt count and status, on both sides of the exchange.
Flows
Which application sends what to which, as a declared route rather than a convention someone remembers.
Transports
File drop, shared folder or HTTP endpoint per route, so the same document schema works on an air-gapped plant network or across sites.
Settings and replay
Retry ladder, idempotent resend and full replay from the hub console, so a failed transfer is repaired rather than retyped.
Audit
The transfer history itself — what was sent, when, by which attempt, and what the receiving application did with it.
Data sources
Excel, CSV and P6 files can be mapped into Link documents. A .xer is read into ready-to-map Activities, WBS, Resources, Resource assignments and Relationships sheets, and schedules in the schedule library appear as sources without being loaded again.
The document schema and the eleven business document types are described on the platform page. How Link works.
Evaluate
Open it rather than read about it.
There is a running demonstration of the suite with a populated project dataset, and a guided walkthrough if you would rather be shown the chain from field quantity to withheld payment.
