A generic term to describe tasks that named users must perform. See also Stage Actions.
In the generic sense, this describes a named individual responsible for performing actions within Q-Pulse. For example, a Non-Conformance has three levels of ownership, the Non-Conformance owner, Stage Owners and Stage Action Owners.
The number that appears beside a Workload metric to indicate the number of actions due. Workload Metrics may appear against LaunchPad module panels, the My Actions tile in the List Screen or in Workload.
The current revision of a Document record.
Objects in the system that cannot be deleted for historical reasons may instead be archived. After archival the item may no longer be assigned to records but it is possible to search for a record that was associated with an item before it was archived. Both People and List Items may be archived.
Tools and resources deemed integral to the operation or upkeep of an organisation also known as Equipment Items.
Classification of an Asset Item for example Multimeters.
The application associated with files of a type in Windows, eg 'DOC' files are associated with Microsoft Word. Attachments are opened in their associated application.
An attachment is a collection of one or more files and/or folders associated with a record.
Audit records describe the scope, findings and people involved in an Audit. Audits are recorded in the Audit module.
Collection of questions that an Auditor may use in the course of an Audit.
A "note" of something that was observed in an Audit; however its gravity was such that it did not warrant the initiation of a Non-Conformance.
Area that is the focus of an Audit i.e. Areas of Standards, Departments, Products/Services, Suppliers and Active Document Revisions.
Area that is the focus of an Audit i.e. Areas of Standards, Departments, Products/Services, Suppliers, Active Document Revisions
Relationships set by user between the following Scope Items (for use when focusing on Audit coverage): Documents, Departments, Area of Standards, Processes, Other
Areas that are covered as part of an Audit i.e Documents, Departments, Area of Standards, Processes, Suppliers
The title of the audit, initially derived from the Audit Primary Scope Item.
The individual who represents the particular area under audit by an Auditor. The Auditee is required to supply information to support the questions asked by the Auditor.
An individual, typically, employed by an organisation to perform Audits on identified areas of the organisation (both internal and external).
A collection of items and their attributes, e.g. stock location, which have been affected by the Non-Conformance.
Corrective and Preventive Action
An individual who is responsible for the overall success of the CA/PA Management system. The CA/PA Manager's main responsibility is the monitoring of the effectiveness and integrity of the system.
An individual who identifies a problem or opportunity against defined organisational areas, eg Department, Process, and Documents, that requires action to remedy. The problem may originate from an Audit or at any point in normal business practice, eg a Customer Complaint. This person's name is entered in the 'Raised By' field of the Non-Conformance record. NB The Record Originator may identify a problem on behalf of an organisation's external customer(s), ie act as a proxy.
An individual who is the overall owner of the Non-Conformance and has ultimate responsibility of any activities highlighted, their implementation and subsequent success or otherwise. This person's name is entered in the 'Owner' field on the Non-Conformance record.
Describe the breakdown of the activities taken to resolve (Corrective Action) and prevent problems (Preventive Action) that occur. See also Non-Conformance.
Typically a managed collective of Actions that drive to an overall conclusion for (for example): Containment Prevent Recurrence Corrective Action
Non-Conformances may be based on a CA/PA Template. The template may define defaults for: Ownership, Target Dates, Stages (and their Workflow), and Stage Actions to perform. A template may be assigned to Source values.
An individual who wishes to view the details or status of a CA/PA record. They may have a direct relation to the record, eg the overall owner, or have a vested interest in it, eg as a manager.
One method of raising a Non-Conformance is via a Wizard. Wizard steps may be user defined/customised to suit and/or new Wizards created.
A request to amend a Document revision.
An Audit that has a Closed date and Person who closed assigned.
An attachment consists of one or more files, this is known as a collection. See also Attachment.
A printing option on a List screen, where the view of information on the screen is what is printed. See also WYSIWYG.
A Non-Conformance associated with (raised by) a customer.
The window in which the main information about a record is viewed.
The people who report directly to a Person.
Can have a number of revisions. At most, one can be active, one can be draft
Content is held in an External File - eg Word, Excel, Visio.
A unique version of a Document record. Revisions can exist in the following states: 'Active' 'Draft', 'Obsolete' and 'Inactive'.
The intended future revision of a Document that may be submitted to Document Approvers for review, approval and comment.
The combination of permissions granted directly to an account or inherited via Security Group membership. This list gives the most accurate description of what an account may do within the system. NB It cannot account for the effect of membership of Dynamic Security Groups.
Embedded files are moved/copied to and stored in the Q-Pulse database itself.
Description of a system field that can be amended by user to reflect their terminology or language
An issue raised during an audit. The Finding may be a Non-Conformance or an Observation.
See Reference Group and Security Group.
A pro-active method of raising an issue within the Quality System. Improvement ideas are logged from the Q-Pulse Launchpad using a pre-defined wizard. They are stored as Non-Conformance records within the system.
A revision of a Document that may be reactivated in the future.
A file that allows a user access to all other files in an attachment collection. For example, an HTML document may be made up of several files, one of which links to all the others. In this case you would set that file to be the index.
An Auditor who performs the team leader role and is main point of contact for overall Audit.
An attachment that is not managed by the system. Attachments of this type will exist on disk in the location indicated by the user and will never be moved/copied or embedded in the database.
A (result) list of records within a module (known as the Register in Document Management).
Managed Lists consist of items that can be re-used/selected by users, for example: CA/PA Severity, Source and Status.
Nominated fields which must be completed before a record can be saved.
An issue raised as a result of day-to-day process failures, Audit Findings, Customer Complaints or Supplier based issues. All Non-Conformances may be viewed within the CA/PA module or from the context in which they were raised, e.g. Customer record. Non-Conformances may be Analysed in the Analysis module.
A date and time stamped addendum that may be added to any record in the system.
Audit with an Actual Audit Start Date, Duration and End Date complete
Permissions are the entities granted to Security Groups, Dynamic Security Groups or Accounts in the system. Permissions define which records a user may see in the system and which actions they may perform, e.g. edit, delete etc. See also Effective Permissions.
A Person in the system who can be referenced against records can be of type Employee or Contact..
This flag will determine whether the Person is internal or external (Supplier or Customer contact) to the organisation.
Audit with a Scheduled Start/End date that has not yet been confirmed.
Additional information about a record that is stored in the Properties screen, e.g. Attachments, Notes, Batches etc.
The section of the Details screen common to all records, e.g. Audit, Document etc. that always appears below other sections. Used to summarise additional information about a record that has been entered using the Properties Screen.
Generic term used to describe the main entities added to a module, e.g. Non-Conformance record.
Logical groupings of people created in the People module. Used for ease of filtering and/or selection, e.g. a Reference Group can be selected as message recipients.
A list of records within the Document Management module. The Register may only show Active, Draft, Inactive or Obsolete records at any one time.
Documents who refer to a selected Document as a related Document
Audit with Schedule Start date, Duration and End Date complete and 'confirmed'
Generic name for Windows/Dialogs/Forms used in Q-Pulse, e.g. the Question Bank Management screen
A security group is a collection of permissions that will be inherited by People, or other security groups that are made members of the group. See also Dynamic Security Group.
Selected functions can be identified as requiring additional electronic authentication (confirmation of username and password) to complete the function, e.g. closing a Non-Conformance.
Non-Conformances may be broken down into Stages, e.g. Corrective Action, Preventive Action etc. Each stage may have to be performed in a pre-defined workflow order. Complex Stages may be further broken down into Stage Actions.
Complex Non-Conformance Stages may be broken down into Stage Actions.
The overall owner of the Stage who has ultimate responsibility for the Stage and any Stage Actions within the Stage, their implementation and subsequent success or otherwise.
Reference to the Standard Item's certificate that was issued as a result of that Asset passing appropriate Activity.
A password that will protect data from unauthorised access. A strong password consists of at least six characters (and the more characters, the stronger the password) that are a combination of letters, numbers and symbols (@, #, $, %, etc.). Passwords are case-sensitive.
The area (on the left) of every List screen that hosts the My Actions, Quick Search, Search Folders and My Folders tiles. The Task Pane may be shown or hidden.
Templates make the creation of new records more efficient by pre-populating fields with appropriate values, eg CA/PA Templates may define Stages, Stage Actions etc.
Fields which have no default purpose as set by system but allow the user to add further information to embellish records.
The order in which certain tasks must be performed. Workflow may be applied to Non-Conformance Stages and Document Approval. Workflow may be defined as parallel (i.e. the stages or approvals may be performed at the same time) or sequential (i.e. one or more Stages/Approvals must be completed before the next set can begin) or as a mixture of both parallel and sequential.
What You See Is What You Get - Term used in the context of printing where the view of information on the screen is what is printed.