Skip to main content

Welcome to QDMS Now

QDMS Now is Bimser's cloud quality and document management platform. It brings controlled documentation, nonconformity and corrective action management, customer complaints, surveys, process governance, and four kinds of risk assessment β€” occupational, asset, environmental and information security β€” together in a single, auditable system.

This knowledge base explains what each module does, how records move through their lifecycle, and which definitions you need in place before you start.

What QDMS Now covers​

AreaWhat it manages
Document ManagementControlled documents and forms β€” folder hierarchy, approval pipeline, revisions, periodic review, distribution and controlled copies
CAPA & NonconformityCorrective, preventive and improvement records β€” detection, root cause analysis, action planning, closure
Customer ComplaintsComplaint intake, assessment, action tracking and closure, with optional links to CAPA records
Survey ManagementSurvey design, distribution to internal and external participants, answer collection
Health, Safety & RiskOccupational risk registers, before/after scoring, control measures and revisions
Asset RiskWhat an information asset is worth β€” confidentiality, integrity and availability ratings, and its classification
Environmental ManagementEnvironmental aspects and impacts per process, significance, control methods and compliance obligations
Information Security RiskISO 27001 risk assessment β€” threats, vulnerabilities, Annex A controls and the Statement of Applicability
Process ManagementProcess governance records β€” hierarchy, revision chain, opinion/control/approval routing
Action ManagementAction plans and their detail items, with performer change requests
Task ManagementThe unified task inbox every module writes into
OrganizationShared master data: organization units, locations, teams, positions, cost centers, contracts

How the modules fit together​

Most QDMS records share the same underlying mechanics, so learning one module makes the next one easier:

  • State machines. A record moves through named states grouped into categories (for example Draft β†’ In Approval β†’ Published). What you are allowed to do depends on the current state.
  • Tasks. When a record needs someone's attention, the system creates a task for the responsible identity. Tasks from every module land in one place β€” see Task Management.
  • Identities. Responsibilities are assigned to users, roles, user groups, positions or organization units β€” not just to individual people. Membership is resolved at the moment a task is read, so somebody added to a group later still sees the pending work.
  • Matrices. Authorization, distribution, opinion, approval and controlled-copy responsibilities are configured as matrices, usually on a parent record (a folder, a main form, a group) and inherited by the records underneath.
  • Definitions. Every module has lookup lists β€” document types, nonconformity categories, action priorities, hazard classes β€” that must exist before the first real record is created.

The four risk modules go further than that: they are four repetitions of one pattern, so learning one teaches you most of the next three. See Risk Management for what they share and where they differ.

Where to start​

  1. Read General System Usage for the shared screen conventions: lists, filters, detail pages, attachments.
  2. Set up your organization structure and user authorization.
  3. Pick the module you are rolling out first and work through its Getting Started pages, then its Definitions.
  4. Create one end-to-end record in a test environment before configuring the approval matrices for real.
tip

Every module page lists the definitions it depends on. If a dropdown on a screen is empty, the matching definition list is almost always the thing that has not been filled in yet.