Home/Process library/Placeholders generated from rules
Process library · EngineeringPlaceholders generated from rules
Before the first drawing exists, the project already knows every document it will deliver. The project manager picks the placeholder sets; M-Files creates the empty documents in one go, with the right group, name, rights and review steps.
In short
In this blueprint an engineering firm takes its projects from its project system into M-Files. Per project, the project manager decides which review steps apply, for example internal review, client review and final. Then they generate placeholders: empty documents that reserve a spot for every expected deliverable. A placeholder set, such as a set for safety documents, is chosen and generated, several times if needed. M-Files creates all placeholders in one go and tags each one with the project and a group numbering in three levels, names it by the naming convention, sets the rights, attaches the review workflow and publishes it, in the background. Engineers then drag their file onto the placeholder; it keeps the metadata, and the name follows the convention. SoftAdvice built and documented the process.
Every project delivers the same kinds of documents
A new project starts. Each engineer creates and names their files their own way. At the end, three deliverables turn out to be missing.
An engineering firm runs many projects at once. Each one delivers specifications, calculations, drawings and safety documents, grouped by a numbering the whole sector knows. And each client expects a slightly different review route.
When every engineer creates and names files their own way, nobody can say which deliverables are still missing, and the same document exists under three names.
- A reserved spot for every expected deliverable
- Group numbering in three levels
- Names built from the metadata
- Only the review steps this project needs
What happens from project start to the first upload
The structure is set once, at the start. After that, engineers only add content.
When the project arrives
Project in M-Files
The project comes from the project system, with client, manager and dates.
At the kick-off
Choose the review steps
The project manager decides which review steps the documents of this project go through.
Right after
Generate the placeholders
One or more placeholder sets are generated in one go, in the background.
During the project
Fill them
Engineers drag their files onto the placeholders; the empty ones show what is still missing.
From project to ready placeholders, step by step
Two decisions for the project manager, one gesture for the engineer. M-Files does the rest and records it in the history.
Take over the project
Projects come from the project system into M-Files, grouped by their state, with client, project manager, department and dates.
Choose the review steps
On the project, the project manager ticks the review steps that apply, for example internal review, client review and final.
Pick the placeholder sets
With the project selected, the project manager picks one or more placeholder sets, each with how many times it is needed, and presses generate.
Generate
M-Files creates every placeholder in one go: tagged with the project and the three group levels, named by the convention, with its rights, its review workflow, published. The team keeps working meanwhile.
Fill the placeholder
The engineer drags the file onto its placeholder and adds the client’s document and revision number. The name is built from the metadata.
Into review
The document starts in draft and only offers the review steps chosen for this project.
From reserved spot to reviewed document
A placeholder is a document from the first second. It only gets its content later, and then follows the review steps of its project.
Deliverable
From creating documents to filling them
The project manager sees on day one what the project will deliver, and every day what is still missing.
Before
- Every engineer names files their own way
- Missing deliverables found at the end
- Group codes typed by hand
- One review route for every client
Now
- Names built from the metadata
- Empty placeholders show what is missing
- Group levels set by the generator
- Review steps chosen per project
M-Files and the SoftAdvice Engineering Pack
The same building blocks as the overview blueprint, configured and documented by SoftAdvice.
Placeholder generator
Placeholder sets defined once, generated per project in one click, in the background.
Projects from your project system
Projects, clients and project managers come in from the system you already use.
Document control
Naming convention, external document and revision numbers, and a review workflow per project.
Questions about this blueprint
What exactly is a placeholder?
An empty document created in advance for a deliverable you know will come. It already has its project, group, name, rights and workflow. You drop the real file onto it later.
Who defines the placeholder sets?
Your team, together with SoftAdvice, once. A set lists the documents a type of work always needs, with their groups. After that, generating is one click per project.
Can a project skip review steps?
Yes. The project manager chooses the steps per project, and the documents of that project only offer those steps.
How does your next project get its structure?
In a one-hour demo we generate the placeholders of a project with you and fill the first one.
