Triark EDM is built on a few core concepts. They are explained here, with a glossary at the end.
Project, document and revision
Project: The main container. Documents and workflows belong to a project, and companies and persons are added to it. The project number is unique in your organisation. You can organise projects by customer, location or discipline, and control who can see and change their content.
Document: Not the file itself, but the item you track: a drawing, a spec, a report. A document has a number, a name, a category and a status, and belongs to one project or to the product library. The document number is unique within the project.
Revision: One version of the document. The revisions hold the files, and a revision can have several files. Add a new revision when the work changes. The newest revision automatically becomes the current one, and older revisions stay in the history. If you rename a document or change its category, Triark EDM does not add a revision.
A revision can be locked once it is settled. You cannot edit or delete a locked revision, and you cannot add files to it or remove files from it.
Draft: A numbered set of files gathered for review before they become a revision. You find drafts on the document's Drafts tab.
The files come from your computer, from a revision, from SharePoint or from the file share. A draft has a number and can be locked, but has no name, status or responsible person. When the files have been checked, you add a revision with the same files. The draft stays as a record of what was checked. Drafts are part of the base product.
Work in progress is written in the document's SharePoint tab (Draft/SharePoint integration add-on) or File Share tab (File Share add-on). See Draft and SharePoint and File share.
Read more in Document list and Revisions.
Category and status
A category sorts a document. Categories form a tree, and a document can have several categories. A status shows where the document is in its lifecycle.
Statuses are defined per category, so you can only choose statuses that fit the category. If you change the category and the status does not belong to the new category, the status stays. Triark EDM marks it Invalid, and you pick a new one. A document with no category can have any status.
Projects, products and companies have their own categories and statuses. Workflows have types and statuses. See Categories and statuses.
Products
A product is something the project delivers or installs, and that the documents are about. A product can have child products. Documents and products are linked without one owning the other, so one drawing can cover several products. Products in the product library are defined once and added to the projects that use them.
Products need the Product add-on, and the product library needs the Product library add-on. See Product list.
Workflows
A workflow sends files to people and asks for something back: a comment, an approval or a signature. A workflow has one task per person, each with its own deadline. Tasks are grouped into steps. The steps can run in order, so a step only starts once every task in the step before it is finished.
You can approve or sign a file only when you have a task to approve or sign it. Approvals and signed files are seen only by the person assigned the task and by Admin. An approval workflow takes PDF files only. Workflows need the Workflow add-on. See Workflows.
References and structure
A reference links a document to something else in Triark, such as a product, a folder, a WBS item, a zone or another document. A reference between two documents shows on both documents. See References.
A project has three independent ways to organise documents:
- WBS: by what the work is.
- Folders: by where the document is filed.
- Zones: by where things physically are.
The same document can sit in both a folder and a zone. See Folders, WBS and zones.
Person, user and access
A person is someone the system knows about, such as a contact at a supplier. When a company is added to the project, you can choose its persons as responsible for a document. You can also give them tasks in a workflow. They do not need a login for this. If you remove the company from the project, its persons show as Unknown wherever they were used in the project. You cannot delete a person. Remove the person from the company and block their user instead.
A user is a person who has been given a login. With the Custom access control add-on, access is granted on top of that, per person and project. Each area, such as the project's persons, folders or zones, is granted as read, write and delete separately. Access to workflows is granted on its own. A new user then sees nothing until they are given access. Responsibility for a document is not the same as access to it.
Every user has a user type:
- Admin: full access, including managing users.
- Standard: access according to what an administrator sets under System Access: read, write and delete.
- Reader: can only read.
Without the Custom access control add-on, every user is Admin: the Usertype field is hidden, and the project access tabs are not shown. The Standard and Reader user types and project, document, product and workflow access come with the add-on.
Access tags decide who can see documents and products: you tag them and grant access to the tag. If you change a document's access tags, you change who can see it. Access tags also need the Custom access control add-on. See Users and Access.
Glossary
| Term | Meaning |
|---|---|
| Project | The container for the work. Documents and workflows belong to a project; companies and persons are added to it. |
| Document | The item you track, with a number, name, category and status. Holds the revisions. |
| Revision | One version of the document, with one or more files. |
| Current revision | The newest revision, the version everyone sees. |
| Draft | A numbered set of files gathered for review before they become a revision. |
| Category | Sorts documents, products, projects and companies. Forms a tree. |
| Status | Shows where something is in its lifecycle. Defined per category. |
| Reference | Link between a document and a product, folder, WBS item, zone or another document. |
| Folder | Organises documents by where they are filed in the project. |
| WBS | Work breakdown structure for the project. |
| Zone | A physical place or area in the project, such as a floor. |
| Product | Something the project delivers or installs. Can have child products. |
| Library product | A product defined once for the whole organisation and used in several projects. |
| Workflow | A package of files sent to people for review, approval or signature. |
| Task | One person's part of a workflow, with its own deadline. |
| Company | An organisation you work with, registered under Companies. |
| Person | Someone the system knows about, with or without a login. |
| User | A person who has a login to Triark EDM. |
| User type | Admin, Standard or Reader. Decides what a user can do. |
| Access tag | A label on documents or products. Access granted to the tag covers everything that carries it. |
Your administrator defines the categories and statuses. See Categories and statuses.
