Document No

STANDARD OPERATING PROCEDURE [Document Number]

APPROVALS:
Name Signature Date

REVISION HISTORY:
Revision Initials and Date Summary of Changes
00

Instructions on completing this document

- Montrium has inserted instructions in blue text into this document to help you
understand the information in each section. Once you have modified this
document to meet the specifics of your organization, please delete the blue text.

- Blue italicized text in this document indicates elements which should be revised
or completed by you so that the text meets your company’s needs and quality
system requirements. Once you have completed this information, please remove
the italics in the document.

Confidential Page 1 of 5
 Document No
STANDARD OPERATING PROCEDURE [Document Number]
<ENTER COMPANY LOGO> Revision: [00]
TITLE Effective date
Configuration Management [Effective Date]

Contents
1.0 PURPOSE .............................................................................................................................. 3
2.0 SCOPE .................................................................................................................................. 3
3.0 DEFINITIONS ........................................................................................................................ 3
3.1 Acronyms ......................................................................................................................... 3
3.1.1 IT – Information Technology ................................................................................... 3
3.1.2 QA – Quality Assurance ........................................................................................... 3
3.1.3 SOP – Standard Operating Procedure ..................................................................... 3
3.2 Terms ............................................................................................................................... 3
3.2.1 Controlled Environment .......................................................................................... 3
3.2.2 Non-Controlled Environment .................................................................................. 3
4.0 RESPONSIBILITY ................................................................................................................... 4
4.1 IT Manager, representative or designee ......................................................................... 4
5.0 PROCEDURE ......................................................................................................................... 4
5.1 Configuration Management ............................................................................................ 4
5.1.1 Hardware ................................................................................................................. 4
5.1.2 Servers ..................................................................................................................... 4
5.1.3 Applications ............................................................................................................. 4
5.1.4 SharePoint ............................................................................................................... 4
5.2 Periodic Review ............................................................................................................... 4
6.0 REFERENCES ........................................................................................................................ 5

Confidential Page 2 of 5
 Document No
STANDARD OPERATING PROCEDURE [Document Number]
<ENTER COMPANY LOGO> Revision: [00]
TITLE Effective date
Configuration Management [Effective Date]

1.0 PURPOSE Commented [MTM1]: In this section, you should insert a short
statement describing the purpose of the procedural document to
The purpose of this procedure is to ensure that all updates to baseline items are controlled and describe why it is needed, and what it is being implemented to
accomplish.
traceable.

2.0 SCOPE Commented [MTM2]: In this section, you should insert a short
statement describing the scope of the procedural document,
This document applies to QA and Production environments supporting Company Name outline the reason the document was created and define its
intended audience.
activities.
If the text in Section 2 is acceptable, you need only insert your
Company name to replace the italicized field.
3.0 DEFINITIONS Commented [MTM3]: In this section define acronyms and
terms that would help team members better understand the
3.1 Acronyms content of this Procedure.
3.1.1 IT – Information Technology
3.1.2 QA – Quality Assurance
3.1.3 SOP – Standard Operating Procedure
3.2 Terms
3.2.1 Controlled Environment
A controlled environment supports regulated activities and must be documented and
maintained following strict guidelines as defined within governing procedures (i.e. Configuration
Management and Change Control).
3.2.2 Non-Controlled Environment
These environments support operational and business activities that are not governed by
predicate rules. Though it is best practice to document a non-controlled environment (i.e.
through Configuration Management) to ensure easy maintenance, it is not a requirement. The
control of such environments does not require strict governance.

Confidential Page 3 of 5
 Document No
STANDARD OPERATING PROCEDURE [Document Number]
<ENTER COMPANY LOGO> Revision: [00]
TITLE Effective date
Configuration Management [Effective Date]

4.0 RESPONSIBILITY Commented [MTM4]:

4.1 IT Manager, representative or designee

5.0 PROCEDURE
5.1 Configuration Management Commented [MTM5]:

5.1.1 Hardware

5.1.2 Servers

5.1.3 Applications

5.1.4 Commented [MTM6]:

5.2 Periodic Review

Confidential Page 4 of 5
 Document No
STANDARD OPERATING PROCEDURE [Document Number]
<ENTER COMPANY LOGO> Revision: [00]
TITLE Effective date
Configuration Management [Effective Date]

6.0 REFERENCES
Document Number Document Title

Confidential Page 5 of 5