Reading Library 6 - Legacy SOP_Change and Configuration Management_Redacted.pdf
PDF 3 MB Posted
- Attached to
- Defense Enclave Services (DES) RFP
- Solicitation number
- HC104720R0014
- Issued by
-
Defense Information Systems Agency
About this file
This standard operating procedure document outlines configuration management and change management procedures for the Defense Information Systems Agency's information technology infrastructure. It defines configuration item categories, triggers for change requests, and procedures for initial population, adding, deleting, or modifying configuration items in the configuration management database. Roles and responsibilities are included for various change and configuration management roles. The document also provides details on configuration management and change control board processes, acronym definitions, standard change request categories and required attachments, and related workflow diagrams. Appendices include additional information on creating scheduled change calendar entries and lists of referenced documents.
This federal contract opportunity posting is for the Defense Enclave Services Indefinite Delivery Indefinite Quantity contract with an anticipated award in the first quarter of fiscal year 2022. The single-award IDIQ is expected to have a ceiling of multiple billions of dollars over a ten-year period consisting of a four-year base and three two-year options. The contract will include firm-fixed-price, labor hour, and cost reimbursable line items. A minimum 25% small business participation goal has been set for the $11.2 billion ceiling value. The Defense Information Systems Agency will leverage this contract to manage, operate, and support the network architecture for 22 Defense Agencies and Field Activities within the Fourth Estate, providing integrated and standardized information technology services to improve security, availability, and reliability.
View the file
Other files
Show 40 more
Latest 50 of 73 listed here. See the rest on GovTribe.
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
IT Enterprise Change and Configuration Management Standard Operating Procedure
Version 2.6 Page | iii
Table of Contents
1 Purpose
2 Scope
2.1 Configuration Item Categories
3 Trigger
4 Procedures
4.1 Change Management Procedures
4.1.1 Information Technology Service Management
4.2 Configuration Management Procedures
4.2.1 Initial Population
4.2.2 Adding, Deleting, or Modifying a Configuration Item
4.2.3 DISANet Requirements Board/Change and Control Board
4.2.4 Verification and Audit Process
Appendix A: Roles and Responsibilities
Appendix B: Acronyms
Appendix C: Standard and Normal SRM CR Categories
Appendix D: Workflow Diagrams
Appendix E: Creating an Entry in the Scheduled Changes Calendar
Appendix F: Related Documents/Links
Appendix G: References
Authorizing Signatures
Hist ori ca l R efe ren ce D oc um en t
Version 2.6 Page | iv
List of Tables Table 1: Configuration Item Categories Table 2: CM and ChM Roles and Responsibilities Table 3: RACI Defined Table 4: CI Owner Team RACI Chart Table 5: Acronym List Table 6: Standard and Normal SRM Change Request Categories
List of Figures Figure 1: Initial Population of the CMDB Figure 2: Verification and Audit Process Figure 3: HBSS Exception for External HDD Request (S005) Figure 4: BPA Purchase Request (S005) Figure 5: Re-image Request (S005) Figure 6: Software Request (S006) Figure 7: Firewall Change Request (S007) Figure 8: Physical Port Activation (S009) Figure 9: DNS IP Request (S012) ca l R efe ren ce D oc um
Version 2.6
Page | 4
4.2.2 Adding, Deleting, or Modifying a Configuration Item
To add, delete, or modify a CI, the first step is to submit a CR via the SRM to request the addition/deletion/modification of the CI. All DISANet customers have access to SRM through the DISA Enterprise Portal Services (DEPS) homepage. DISANet services and products can be requested using this tool. These are the most appropriate SRM categories for CIs:
• Normal changes:
o S005 – Hardware o S007 – New Network Device/Configuration o S011 – Server o S012 – DNS/IP
• Standard changes:
o S006 – Approved Software (software must be on Approved Software List) o S009 – Physical Port Activation
Each request type needs specific required attachments and follows a unique workflow. See Appendix C for the table of required attachments and Appendix D for request workflows. Once the user has completed their desired request category and attached the required attachments, the request will be converted into a REQ (Request Identification) and routed to the Approval Central module. Within Approval Central, the requestor’s supervisor can review the REQ and must approve the REQ before the REQ is routed to th Change Management (ChM) Team for review.
The status of the REQ will not change until approved by the ChM Team. ChM verifies that the REQ has the required documents and will either Reject, Hold, or Approve the REQ:
• Rejecting the REQ will no ify the user and provide a justification for rejection. Users are then able to resubmit the REQ with corrections entered.
• Putting the REQ on hold will keep the REQ within Approval Central until DRB review can take place.
• Approving the REQ will route the REQ to the Change Management Module (CMM) and create a CR identification for the request. ChM will need to go into the CMM to route the request to the appropriate request coordinator.
4.2.3 DISANet Requirements Board/Change and Control Board
All normal requests submitted via SRM require DRB/CCB review prior to implementation. For details of the DRB/CCB process, please refer to the IT Enterprise DRB and CCB Meetings SOP, located as DRB/CCB SOP in Appendix F: Related Documents/Links. Hist ori ca l R efe ren ce
D oc um
Page | 7
The individual(s) who needs to be informed after a decision or action is taken. This incorporates one-way communication.
ca l R efe ren ce D oc um
Page | 14
Appendix D: Workflow Diagrams
Figure 3: HBSS Exception for External HDD Request (S005) ca l R efe ren ce D oc um
Page | 15
Figure 4: BPA Purchase Request (S005) ca l R efe ren ce D oc um
Page | 16
Figure 5: Re-image Request (S005) ca l R efe ren ce D oc um
Page | 17
Figure 6: Software Request (S006) ca l R efe ren ce D oc um
Page | 18
Figure 7: Firewall Change Request (S007) ca l R efe ren ce
D oc um
Page | 19
Figure 8: Physical Port Activation (S009) ca l R efe ren ce D oc um
Page | 20
Figure 9: DNS IP Request (S012) ca l R efe ren ce D oc um
Page | 21
Appendix E: Creating an Entry in the Scheduled Changes Calendar
1. Go to https://disa.deps.mil/org/SE6/DEMI/Lists/DEMI/Date%20List.aspx.
2. Scroll to the bottom of the page.
3. Click on the + Add new item link.
4. The “DEMI _ New Item” window displays.
ca l R efe ren ce D oc um
Page | 22
5. Fill out the following fields:
a. Title
b. Network
c. NCR Sites
d. Remote Sites
e. Propped – Date entry created
f. Suspense – Date of Action
g. Completed – Date Action completed
h. DCCB Reviewer
i. Subject
j. Notice Required
k. Subject Type
l. DISANET Asset Name
m. Status
n. Is rollback plan included?
o. Comments
6. Click Save.
7. The entry has now been added to the Scheduled Changes Calendar.
ca l R efe ren ce D oc um
Page | 23
Appendix F: Related Documents/Links
1. BMC Remedy ITSM system:
https://webitsm.csd.disa.mil/arsys/forms/itsmapp1.csd.disa.mil/SHR:LandingConsole/Def ault+Administrator+View/?cacheid=8deae312
2. DRB/CCB SOP:
https://disa.deps.mil/org/SE6/ISCDESS/EnterpriseArchitecture/SitePages/Home.aspx
3. DISANet Scheduled Change Calendar:
https://disa.deps.mil/org/SE6/DEMI/Lists/DEMI/Date%20List.aspx ca l R efe ren ce D oc um
Page | 24
Appendix G: References
1. System Change Request SOP
2. Remedy ITSM Request Fulfillment SOP
3. Release and Deployment/SCCM SOP ca l R efe ren ce D oc um
File details come from the government source that posted it. Updated .