Using a Web Archive (WA) document type for a QMS


Web archive

Recently we announced a case study with a partner, Primilis, in which they used a CogniDox feature to implement a Graphical Quality Management System (G-QMS). It's available to download (no registration required) in PDF format.

A typical QMS is a set of pages each describing a company process or procedure to ensure a standard and consistent level of business quality. Those pages often contain workflow graphics in the form of flow diagrams. They're a lot more user-friendly and interactive when presented on-screen within a web browser.

Primilis created two QMS solutions for a couple of existing customers. How best to store these within CogniDox?

The answer is to create them as Web Archive (WA) document types.

By way of background, normally CogniDox allows user companies to decide what they want to name their document types but there are three special or reserved types that come with built-in functionality. These are:

  • Document Holder (DH) for structured lists of contained documents
  • Licensee Source (LS) for packages of software source or binaries
  • Web Archive (WA) for zip files containing HTML pages

Example uses for Web Archives are:

  •     Automatically generated documentation
  •     Containers for legacy documentation
  •     Packaging websites e.g. a marketing or sales promotion micro-site

Web archives are zip files containing an index.html page at the top level. Once the zip file is uploaded they can be directly browsed from both CogniDox and the Customer View. An example might look like this (note the highlighted index file):

web archive

When the zip file is uploaded it is represented by a Zip icon as the master file and an HTML icon as the 'derived' file. When a user clicks on the HTML icon it opens the entire package as a website within the same browser that's being used for CogniDox, with the index file as the home page. The user can then follow any links that have been coded in the HTML.

The WA file is like any other document - you can call for reviews and ultimately it can be approved and published. When it is published it can be licensed to appear on a customer portal and again there it will display as a set of web pages,

There's a certain elegance to the fact that one of the controlled documents is itself the entire company QMS.

Value of DMS for Product Development


Tags: quality management system, Document management and control, New Product Development

Paul Walsh

Written by Paul Walsh

Paul Walsh was one of the founders of Cognidox. After a period as an academic working in user experience (UX) research, Paul started a 25-year career in software development. He's worked for multinational telecom companies (Nortel), two $1B Cambridge companies (Ionica, Virata), and co-founded a couple of startup companies. His experience includes network management software, embedded software on silicon, enterprise software, and cloud computing.

Related Posts

A short guide to non-conformance reports; what, why and how

How do you log and deal with non-conformities so that faulty products don't end up in the hands of ...

How to build a supplier quality management system in 4 simple steps

How do you transform regular supplier reviews from a box-ticking exercise into a genuinely useful ...

ISO 9001 vs ISO 13485. What’s the difference?

ISO 9001 is the internationally recognised standard for quality management used in many sectors ...

Medical Device Technical File requirements: what you need to know

What is the medical device technical file? What should it contain and how should it be structured? ...

Why not just use SharePoint as a Document Management System?

What’s wrong with SharePoint, anyway? Why shouldn’t it be used as a document management system ...

8 Tips for Improving the Document Review Process

How is the quality of your document review process affecting the speed and efficiency of the way ...

The evolution of a Quality Management System

A focus on a quality management system shouldn’t just mean a ‘box ticking’ exercise for an ...

Can Product Innovation Tools help you go 'virtual first?'

Colocation was one of the central tenets of the Agile manifesto, but times have changed. With all ...

Why your QMS needs to be an eQMS

If you want to develop a Quality Management System that meets the regulation and powers your ...