Professional Documents
Culture Documents
Main process:
Sub process: Click here to enter text.
This document explains how to maintain global and local quality management systems in
SharePoint;
outlines the structure and content
explains how to design pages
explains how to handle document
information flow and responsibilities related to changes to processes or procedures
are described in section 4 of the document
how to create process flow maps and add to SharePoint pages is explained in
HOWTO_072 How to Create Process Flow Maps and Add to SharePoint Pages.
TABLE OF CONTENTS
Doc.no: HOWTO_073
Prepared by: annodeno Security level:
Approved by: hehvno
Version: 3 This document is valid on date of print only.
Modified: 2015-08-07 2020-10-06 Page 1 of 10
How to maintain EMS in Sharepoint
Main process:
Sub process: Click here to enter text.
Figure 1
2.1 Description
- The EMS pages are created using SharePoint.
- Each page is created from a parent page and inherits its properties and permissions.
Doc.no: HOWTO_073
Prepared by: annodeno Security level:
Approved by: hehvno
Version: 3 This document is valid on date of print only.
Modified: 2015-08-07 2020-10-06 Page 2 of 10
How to maintain EMS in Sharepoint
Main process:
Sub process: Click here to enter text.
- An example (simplified) of the global page and a local page is attached overleaf. In some
cases, the local processes follow the global processes, and the boxes in the local flow
charts are simply linked to the global page (see red arrow in Fig. 2).
Main Main
Global Norway
QA page QA page
A1 A2 B1 B2 B3 C1 C2 C3 D1 D2 A1 A2 C1 C2 D1 D2
Figure 2
Doc.no: HOWTO_073
Prepared by: annodeno Security level:
Approved by: hehvno
Version: 3 This document is valid on date of print only.
Modified: 2015-08-07 2020-10-06 Page 3 of 10
How to maintain EMS in Sharepoint
Main process:
Sub process: Click here to enter text.
Figure 3
Doc.no: HOWTO_073
Prepared by: annodeno Security level:
Approved by: hehvno
Version: 3 This document is valid on date of print only.
Modified: 2015-08-07 2020-10-06 Page 4 of 10
How to maintain EMS in Sharepoint
Main process:
Sub process: Click here to enter text.
Figure 4
Click ‘Edit web part’ and change the ‘Title’ of the web part to the appropriate category (for
example ‘Procedures’).
How to configure the Lightning Conductor web part is described in the document “How to
configure Lightning Conductor” which is found on Elvis.
Links are inserted utilizing the ’Links’ web part (click arrow to get the edit view).
To be able to add pages to the lightning conductor all pages has to be created, and
properties (metadata) has to be added in advance.
Follow the “How to configure Lightning Conductor”, but choose the pages library
instead of document library.
o You can use both global and local pages, then you have to choose both global
and local pages library
Figure 5
Doc.no: HOWTO_073
Prepared by: annodeno Security level:
Approved by: hehvno
Version: 3 This document is valid on date of print only.
Modified: 2015-08-07 2020-10-06 Page 5 of 10
How to maintain EMS in Sharepoint
Main process:
Sub process: Click here to enter text.
3 DOCUMENT HANDLING
Additionally, for obsolete documents create a ‘Obsolete documents’ library which has
restricted access this way the documents should do not appear in search results. When
documents in the documents library are obsolete, they are moved to this library so that they
are hidden from regular users.
Figure 6
Sharepoint will prompt a number of different properties to be filled out, such as revision
date, process area and document class. As much information as possible should be filled
out (though it is not mandatory and can be added and changed at a later stage). These
properties enable the data views to display the right documents on the different pages
AND the library view to be organized in the most practical way. Examples of properties
are highlighted in Fig. 7.
Each country’s main page is level 1, the next level is Process area, next level is process
and then sub process. Most areas only have three or four levels. When a document need
to be tagged to different processes, use ; to separate.
One can also upload multiple documents by selecting ‘Upload Multiple Documents’,
however, this method does not prompt filling out properties. The properties must then be
filled in afterwards.
Doc.no: HOWTO_073
Prepared by: annodeno Security level:
Approved by: hehvno
Version: 3 This document is valid on date of print only.
Modified: 2015-08-07 2020-10-06 Page 6 of 10
How to maintain EMS in Sharepoint
Main process:
Sub process: Click here to enter text.
New documents need approval before they are available to regular users. Read more
about approval in the next section.
Figure 7
3.4.1 Versioning
When you edit a document or the properties of a document, revisions of the documents are
saved as version history. This enables you to see when a file and/or its properties were
changed, who changed it, and the change description (comments). You can view a previous
version without overwriting your current version, and you can also restore a previous version.
Minor versions are created in the following situations:
When a file is first created or uploaded. (The file must first be checked in, in order to
create its first version.)
When a file is uploaded that has the same name as an existing file and the ‘Add as a new
version to existing files’ check box is selected.
When a file is opened, edited, and saved. A version is created when you first click Save.
This version is updated with the latest changes that you make to the file before closing it.
(A version is not created every time that you click Save, because this would create too
many versions.)
If you delete a file, all of its versions are deleted. By default, when you delete a document,
the version is sent to the Recycle Bin, where it can be recovered until it is permanently
deleted (after 30 days). Point to the file name in the library and select Version History to see
all versions.
Note that the version number generated by Sharepoint will not necessarily correspond with
the issue number provided in the header of the document.
Doc.no: HOWTO_073
Prepared by: annodeno Security level:
Approved by: hehvno
Version: 3 This document is valid on date of print only.
Modified: 2015-08-07 2020-10-06 Page 7 of 10
How to maintain EMS in Sharepoint
Main process:
Sub process: Click here to enter text.
Figure 8
You then add a comment which describes the changes and if it is a minor or major change,
for example:
Figure 9
Every document that has been edited must follow a workflow for approval. This is done by
pointing to the file name in the library and select workflow,
Figure 10
and select an Approval workflow. If several people are to approve, the names must be added
in the order it is to be approved. An approver in a workflow must be given ‘Approver’
permission in the library settings.
A file remains in a draft or pending state until it is approved or rejected by someone who has
permission to approve it. If the file is approved, it is assigned an Approved status in the list or
library, and it is visible to anyone with permission to view the library. If the new version is
rejected, it remains in a pending state and is visible only to the people with permission to
view drafts.
A pending file is visible only to its creator and to the people with permission to approve items.
The people who have permission to read content but who do not have permission to see
draft items will see the current published major version of the file. If a major version has not
been published yet, the file will not be visible for the people who do not have permission to
see draft items.
Note that it is possible to bypass the approval routing. This should only be done when there
is no doubt that the document has been approved, and if the approver is unable to access
Elvis to approve the document. From the menu, choose ‘Approve/Reject’, tick off ‘Approved’
and add a comment such as ‘Approved by <name> on <date>’.
Doc.no: HOWTO_073
Prepared by: annodeno Security level:
Approved by: hehvno
Version: 3 This document is valid on date of print only.
Modified: 2015-08-07 2020-10-06 Page 8 of 10
How to maintain EMS in Sharepoint
Main process:
Sub process: Click here to enter text.
Approval rules for global documents are described in GPRO_100 Control of documents in
Eltek Management System. Local sites may have different rules, described in local
documents.
Figure 11
The version history can be accessed from the same menu as ‘Publish a Major Version’ and
‘Workflows’ (called ‘Version History’).
Figure 12
4 References
QA page and library instructions are available in this library:
http://elvis2.elasp.ad/QA/Global/QA%20Library%20Usage%20and%20Instructions
Doc.no: HOWTO_073
Prepared by: annodeno Security level:
Approved by: hehvno
Version: 3 This document is valid on date of print only.
Modified: 2015-08-07 2020-10-06 Page 9 of 10
How to maintain EMS in Sharepoint
Main process:
Sub process: Click here to enter text.
Doc.no: HOWTO_073
Prepared by: annodeno Security level:
Approved by: hehvno
Version: 3 This document is valid on date of print only.
Modified: 2015-08-07 2020-10-06 Page 10 of 10