Documents from pds project and service knowledge, with the source.

Not necessarily, but the route is different: instead of mirroring a directory, pds needs to make the documents available somewhere. Whether and how that works depends on your contract and version – we clarify it with you and your support partner beforehand, not halfway through the set-up. Until then, you can upload project folders, emails, site photos and voice notes, including whole folder trees. That can be a sensible first step anyway if that is where your older construction projects from before pds are kept.

No. Both go into the same knowledge base, and both structures stay as they are. From the customer and property master data in the export, the system knows that the 2019 construction project and last winter’s service call concern the same address. So a question about the property brings up the drawing from the construction phase and the report from the last call-out side by side – whoever goes out to the fault can see what was installed at the time. We check beforehand how well your master data supports this link.

All revisions come across, and the answer tells them apart by file, revision and date. Quietly picking one would be the wrong approach here; where two revisions contradict each other, the answer says so. You decide which one was used for construction, with both sources in front of you. If an old revision shouldn’t appear at all, that is handled through the document type, not by deleting anything: in pds it stays where it is.

That’s up to you. The simplest option is to leave the payroll area out altogether – anything that isn’t in the knowledge base can’t appear in an answer. If it should go in because accounts work with it, it gets its own document type that only that role can see. For the site team, you might release drawings, daily site reports and manufacturer documents; new documents are assigned through their document type, without anyone having to manage them file by file.