Feasibility & Investment
Compare project options before committing to a scope or budget. Keep the assumptions and open questions visible.
Planned moduleView tasks and outputs →New platform examples are currently available in English and Russian. The template library and knowledge centre keep your chosen language.
From a project question to a working document
Define a scope. Prepare a tender. Compare offers. Keep track of change. Find the right document and see how connected project information can support the next decision.

The catalogue below describes the planned scope of 18 modules. Each page shows the intended inputs, outputs and review responsibilities. These are not 18 available AI services. Existing templates remain in the library.
A · PMC Pilot
Compare project options before committing to a scope or budget. Keep the assumptions and open questions visible.
Planned moduleView tasks and outputs →Organise asset records, identify evidence gaps and decide what needs inspection before a transaction or investment.
Planned moduleView tasks and outputs →Set out what the project must achieve, who can decide and how risks, approvals and actions will be followed through.
Planned moduleView tasks and outputs →B · PMC Pilot
Check whether the design team has the requirements, surveys and decisions needed to start the next stage.
Planned moduleView tasks and outputs →Bring supplier information, design requirements and technical questions into one review trail so that interfaces are not overlooked.
Planned moduleView tasks and outputs →Know which revision the team is using. Track transmittals and differences between documents without losing approved information.
Planned moduleView tasks and outputs →C · PMC Pilot
Turn tender instructions into a clear submission checklist and proposal outline based on the bidder’s actual evidence.
Planned moduleView tasks and outputs →Define purchasing packages, request the right information and check supplier qualifications before evaluating offers.
Planned moduleView tasks and outputs →Compare what each bidder actually offers. Keep technical suitability separate from price and make exclusions visible before a purchase decision.
Planned moduleView tasks and outputs →D · PMC Pilot
Follow equipment from order through manufacture and delivery. Relate missing items and late documents to the work that depends on them.
Planned moduleView tasks and outputs →Check how quantities, rates and contract terms form a cost or payment claim. Keep the calculation traceable to its inputs.
Planned moduleView tasks and outputs →Compare the programme with recorded progress, identify missing schedule logic and plan the next period around actual constraints.
Planned moduleView tasks and outputs →E · PMC Pilot
Connect every inspection point to a requirement, a responsible person and the record that will demonstrate the check.
Planned moduleView tasks and outputs →Turn dated site notes and photographs into a clear account of progress, observations and actions for the project team.
Planned moduleView tasks and outputs →Organise safety and environmental records so the responsible specialist can see missing evidence and outstanding actions.
Planned moduleView tasks and outputs →F · PMC Pilot
Track what the contract requires, which event starts an obligation and what evidence supports the team’s response.
Planned moduleView tasks and outputs →Build a clear record of a change: what happened, which contract provisions may apply and what evidence supports time and cost effects.
Planned moduleView tasks and outputs →Check each system’s handover requirements against available records and keep open items visible to the operations team.
Planned moduleView tasks and outputs →Built around engineering practice
PMC Pilot is being developed as a product of ALMECO, an engineering company. The aim is practical: connect what the team knows, what remains uncertain and what a document needs to record.
The engineer and the project team retain responsibility for checking and authorizing the result.
Explore the project journey →