1. EPMO Open Source Coordination Office Redaction File Detail Report

Produced by Araxis Merge on 11/6/2017 5:08:35 PM Eastern Standard Time. See www.araxis.com for information about Merge. This report uses XHTML and CSS2, and is best viewed with a modern standards-compliant browser. For optimum results when printing this report, use landscape orientation and enable printing of background images and colours in your browser.

1.1 Files compared

#	Location	File	Last Modified
1	BTSSS_CIF_10162017.zip\BTSSS_CIF_10162017	BTSSS_CMP.docx	Tue Sep 19 13:53:42 2017 UTC
2	BTSSS_CIF_10162017.zip\BTSSS_CIF_10162017	BTSSS_CMP.docx	Mon Nov 6 22:01:10 2017 UTC

1.2 Comparison summary

Description	Between Files 1 and 2
Description	Text Blocks	Lines
Unchanged	8	1192
Changed	7	15
Inserted	0	0
Removed	0	0

1.3 Comparison options

Whitespace
Character case	Differences in character case are significant
Line endings	Differences in line endings (`CR` and `LF` characters) are ignored
CR/LF characters	Not shown in the comparison detail

1.4 Active regular expressions

No regular expressions were active.

1.5 Comparison detail

1	Configurat ion Manage ment Plan
2	Beneficiar y Travel S elf-Servic e System ( BTSSS)
3
4
5
6	September 2017
7	Version 3. 04
8	Department of Vetera ns Affairs
9
10
11	Version Hi story
12	Date
13	Version
14	Descriptio n
15	Author
16	9/18/2017
17	3.04
18	September Monthly Up date
19	Christina Silva
20	8/31/2017
21	3.03
22	CRMOL upda te
23	Christina Silva
24	8/21/2017
25	3.02
26	August Mon thly Updat e
27	Christina Silva
28	7/19/2017
29	3.01
30	July Month ly Update
31	Christina Silva
32	6/16/2017
33	2.03
34	June Month ly Update
35	Christina Silva
36	5/18/2017
37	2.02
38	May Monthl y Update
39	Christina Silva
40	4/18/2017
41	2.01
42	April Mont hly Update
43	Christina Silva
44	3/15/2017
45	1.03
46	March Mont hly Update
47	Christina Silva
48	2/24/2017
49	1.02
50	February M onthly Upd ate
51	Christina Silva
52	1/26/2016
53	1.01
54	January Mo nthly Upda te
55	Christina Silva
56	12/2/2016
57	0.04
58	December M onthly Upd ate
59	Scott Bart el
60	10/31/2016
61	0.03
62	Initial Re lease
63	Karen Shep herd
64	10/28/2016
65	0.02
66	Edited Doc ument Per Comments
67	Karen Shep herd
68	10/26/2016
69	0.01
70	Initial Dr aft
71	Karen Shep herd
72
73
74
75	Table of C ontents
76	1.Executiv e Summary1
77	2.Introduc tion1
78	2.1Purpose of the Co nfiguratio n Manageme nt Plan1
79	2.2Scope o f the Conf iguration Management Plan2
80	2.3Structu re of the Configurat ion Manage ment Plan2
81	3Configura tion Manag ement Acti vities2
82	3.1Roles a nd Respons ibilities2
83	3.2Communi cation4
84	3.3System Configurat ion Baseli ne4
85	3.4Configu ration Con trol Proce ss (CCP)5
86	3.5Configu ration Man agement Re sources7
87	APPENDIX A : CONFIGUR ATION MANA GEMENT PLA N APPROVAL 8
88	Appendix B : Referenc es9
89	Appendix C : Key Term s10
90	Appendix D : Suggeste d Configur ation Item s Data Ele ments11
91	Appendix E : [Facilit y] Current Configura tion Basel ine Report 16
92	Appendix F : Configur ation Item s (CI) Sho wing Syste m Boundari es17
93	Appendix G : Change O rder Appro val Checkl ist18
94	Appendix H : Change O rder Imple mentation Plan Templ ate19
95	Appendix I : Business Case Just ification2 0
96	Appendix J : Change M anagement Back-Out P lan Templa te21
97
98	Executive Summary
99	The implem entation o f a Benefi ciary Trav el Self-Se rvice Syst em (BTSSS) Solution serves to fulfill th e Departme nt of Vete rans Affai rs (VA) co mmitment t o Veterans and to th e American public to serve as good stewa rds of pub lic resour ces.
100	This docum ent will p rovide hig h level in formation on the Con figuration Managemen t (CM) pro cesses imp lemented t hroughout all phases for the B TSSS softw are projec t includin g software , systems, and docum entation. The proce ss and pro cedures ou tlined in this docum ent will c onform wit h the exis ting VA CM tools and the overa rching VA Configurat ion Manage ment Plan (CMP) in t he Rationa l reposito ry. The C MP will al so support the unifi ed Veteran Informati on Portal (VIP) Rele ase proces s utilizin g agile de velopment, frequent builds and releases, and a hig h level of integrati on with Ag ile Lifecy cle Manage ment (ALM) tools, wi th automat ed builds and testin g. ALM and testing d ata will n eed to be stored in the VIP Ra tional Rep ository.
101	Introducti on
102	The Benefi ciary Trav el Self-Se rvice Syst em (BTSSS) will enab le the VA to provide travel re imbursemen t to autho rized Vete rans and t heir benef iciaries a t the poin t-of-care as well as through s tandard we b browsers and the V etLink kio sk at vari ous VA fac ilities. I t will use state-of- the-art te chnology t hat will a llow Veter ans to sub mit expens es for tra vel reimbu rsement ut ilizing th e BTSSS ap plication and receiv e timely r eimburseme nt via Ele ctronic Fu nds Transf er (EFT).
103	The BTSSS software s olution wi ll be deve loped and implemente d using Mi crosoft Dy namics 365 for Custo mer Servic e which is a COTS-ba sed soluti on that pr ovides str ong custom er support and acces s to a use r communit y.
104	Due to thi s projects use of mu ltiple thi rd party v endors, th e Configur ation Mana gement pro cess will initially be split b etween mul tiple tool s. However due to th e VA’s req uirement t hat all fi nalized co de be stor ed within its Config uration Ma nagement T ool, this project wi ll only be providing the final code rele ases in IB M Rational Team Conc ert (RTC).
105
106	Purpose of the Confi guration M anagement Plan
107	The overal l objectiv e of this CMP is to identify C M roles an d responsi bilities, resources, and forma l processe s and proc edures to ensure tha t all deve lopment of the BTSSS software system are evaluated and appro ved before implement ation. Thi s also inc ludes the processes and proced ures for m anaging an d controll ing the de velopment, delivery, and maint enance of all softwa re and doc umentation products used for c ontrolling implement ation, eva luation, a nd auditin g of the C M processe s and Conf iguration Items (CIs ), to incl ude mainta ining a cu rrent base line confi guration o f the syst em under C onfigurati on Managem ent Contro l. This CM P also out lines the BTSSS orga nization, responsibi lities, an d requirem ents to be followed by teams p roducing o r modifyin g software within th e system. The BTSSS CMP will a id both ma nagement a nd technic al staff i n the prod uction of high-quali ty softwar e products and all t he informa tion perti nent to th e BTSSS sy stem.
108	Scope of t he Configu ration Man agement Pl an
109	The Benefi ciary Trav el Self-Se rvice Syst em (BTSSS) CMP docum ent, along with the correspond ing CM Sta ndard Oper ating Proc edure (SOP ), defines the Infor mation Sys tem’s stru cture and methods fo r:
110	Identifyin g, definin g, and bas e-lining C Is
111	Creating C I Records
112	Identifyin g relation ships
113	Controllin g modifica tions and releases o f CIs
114	Reporting and record ing status of CIs an d any requ ired modif ications
115	Ensuring c ompletenes s, consist ency, and correctnes s of CIs
116	Controllin g storage, handling, and deliv ery of the CIs
117	Structure of the Con figuration Managemen t Plan
118	The intend ed audienc e of the C MP are sys tem owners , Organiza tional Ser vice Lines and divis ions, faci lity chief informati on officer s, system administra tors, info rmation se curity off icers and informatio n owners, and Office of Inform ation and Technology (OIT) sta ff within these iden tified are as respons ible for t he day-to- day mainte nance of t he configu ration ite ms on the BTSSS soft ware devel opment pro ject. This includes others who have a re quirement or need to develop, change, fi x, or enha nce softwa re artifac ts on the BTSSS soft ware devel opment pro ject.
119	This CMP, in conjunc tion with the OIT Co nfiguratio n and Chan ge Managem ent Proces s Document s, and Ser vice, Deli very and E ngineering (SDE) Cha nge Manage ment Polic y and Stan dard Opera ting Proce dures, ide ntifies co nfiguratio n manageme nt and cha nge manage ment roles and respo nsibilitie s and syst em relatio nships. In addition, the scope includes the automa ted tools and proces ses used t o manage t he informa tion syste m baseline configura tion.
120	Configurat ion Manage ment Activ ities
121	Roles and Responsibi lities
122	Table 1: R oles and R esponsibil ities
123	Role
124	Responsibi lity
125	Program Ma nager
126	• Oversees the softw are config uration ma nagement p rocess.
127	• Ensures proper exe cution of the BTSSS Plan.
128	• Identify dependent projects.
129	Configurat ion Manage r
130
131	• Develop and mainta in Softwar e Configur ation Mana gement (SC M) Procedu res Manual and work instructio ns for eac h VA produ ct they ar e assigned .
132	• Educates project t eam member s in SCM “ best pract ices.”
133	• Accounta ble for in stituting the establ ished proc esses and reporting progress s tatistics based on c hange requ ests.
134	• Identifi es product baselines as necess ary of all products within the ir assigne d projects .
135	• Responsi ble for SC M audits a nd necessa ry status accounting related t o the prod uct.
136	• Maintain s artifact s followin g proper v ersion con trol proce dures.
137	Software C hange/Buil d Administ rator
138	• Develops and maint ains artif acts follo wing prope r version control pr ocedures.
139	• Establis hes, promo tes, and r eleases ba selines.
140	• Performs or valida tes interi m and fina l builds.
141	• Identifi es product baselines as necess ary of all products within the ir assigne d projects .
142	Developmen t Manager/ Technical Lead
143	• Prepares release p ackage, re lease arch ives and V ersion Des cription D ocuments ( VDD).
144	• Ensures all SCM Pr ocedures M anual and work instr uctions ar e implemen ted and fo llowed for all softw are, docum entation, and/or any other com ponents fo r which th ey are res ponsible.
145	• Ensures all develo pers’ work within th e specifie d SCM proc ess and re lated guid elines as specified in the SCM Procedure s Manual a nd work in structions .
146	Developers /System Ad ministrati on
147	• Develops and maint ains artif acts follo wing prope r version control pr ocedures u sing the S CM Procedu res Manual and work instructio ns.
148	• Maintain accurate, detailed informatio n for all assigned s tories, in the Ratio nal databa se, relate d to the a pplicable developmen t detail o f the Agil e lifecycl e.
149	• Provide impact ana lysis repo rting prob lems or ch anges, inc luding doc umentation of sugges ted soluti ons.
150	• Document ation of b uild, rele ase, and i nstallatio n instruct ions.
151	Software Q uality Ass urance Ana lyst/Testi ng Analyst
152	• Update s tories ass igned to t hem accord ing to tes t activity results.
153	• Determin es Pass/Fa il for eac h story sc heduled fo r a sprint release.
154	• Identifi es defect( s) and/or enhancemen t(s) for a ny newly d iscovered problems d uring test ing and cr eates stor ies or def ects in Ra tional.
155	Technical Writer
156	• Develops technical deliverab le documen tation to support th e software deliverab les.
157	• Provides editing, formatting , and grap hics suppo rt for doc umentation .
158	Implementa tion Team/ Operations Team
159	• Coordina tes the re lease and deployment of softwa re updates to the ex isting BTS SS Custome r Relation ship Manag ement (CRM OL) system .
160	• 365 Clou d
161
162	Communicat ion
163	Communicat ion within the BTSSS project w ill utiliz e the feat ures withi n the Rati onal Confi guration M anagement tool (RTC) that allo ws for tas ks, work i tems, buil ds, and de ployments to be proc essed thro ugh a life cycle. Th at cycle p rogression is accomp lished by allocating to each a ctivity, t ask, or de cision the role that is accoun table and/ or respons ible for i t as well as those r oles to be consulted with befo rehand, or informed afterward. The OIT C onfigurati on Managem ent Proces s document provides a Responsi ble, Accou ntable, Co nsulted, a nd Informe d (RACI) M atrix to d efine acti vities and roles.
164	BTSSS will utilize t his matrix to define the roles and respo nsibilitie s within t he project and will provide co mmunicatio n via dail y scrum me etings, we ekly team meetings, and variou s develope r, test an d deployme nt meeting s as neede d.
165	Requests f or Change (RFC)/Stor ies are en tered in t he appropr iate Chang e Manageme nt System (VA) for r eview, app roval, and implement ation by t he appropr iate Servi cing Divis ions. Chan ge Control and Advis ory Board reviews ar e required for chang es that im pose downt ime for th e system o r service or pose a risk or af fect multi ple facili ties or se rvices. I t is the r esponsibil ity of the implement ation team to notify potential ly affecte d customer s and pers onnel requ ired to pr ovide supp ort, e.g. Organizati onal Servi cing Divis ions, Netw ork Chief Informatio n Officer (NCIO), Fa cility Chi ef Informa tion Offic er (FCIO), etc.
166	System Con figuration Baseline
167	Configurat ion identi fication i s the proc ess of ide ntifying, selecting, naming, a nd classif ying the d evelopment items sub ject to ch ange contr ol. This i nvolves de fining the product s tructure a nd definin g identifi cation con ventions t o be used for baseli nes of pro ducts, doc uments, so ftware bui lds, and r eleases pa ckages. It ems are no rmally pla ced under change con trol as so on as they are insta ntiated, a s tracking the confi guration a nd new con tents and implementa tion statu s of new r equirement s going in to an init ial releas e is equal ly as impo rtant as t racking la ter change s.
168	Within the Rational Team Conce rt (RTC) r epository, unique id entifiers will be ap plied to p roducts an d their as sociated c ontent. T he followi ng are the types of identifier s used in accordance with the formats de fined in t he applica ble proced ure docume nts:
169
170	File versi ons - Iden tifies the version o r revision identifie r of each software i tem that c omprise th e Product at any spe cific base line. It a llows iden tification of unique items tha t make up the invent ory of a b aseline. S oftware id entificati on provide s the foun dation for traceabil ity of rel ated artif acts. The software i dentificat ion versio n number i s assigned by the ve rsion cont rol automa ted tool a nd control led in the developme nt reposit ory. The V DD lists a ll softwar e, its ver sion, and related ch ange docum ent number s.
171	Change rec ords– Iden tifies a s et of work product v ersions cr eated to r esolve a s pecific Ch ange Reque st. The id entifier i s created, controlle d, and tra cked by th e Change M anagement System.
172	Baseline – Identifie s a set of specifica tions or w ork produc ts that ha s been for mally revi ewed and a greed upon , which se rves as th e basis fo r further developmen t, and whi ch can be changed on ly through change co ntrol proc edures.
173	Build – Id entifies a set of so lution fil e versions used to b uild and a ssemble de ployable p ackages.
174	Release Pa ckage – Id entifies a set of de ployable f ile versio ns and del iverable d ocument ve rsions tha t constitu te a compl ete releas e package.
175	Release Ca ndidate – Identifies the distr ibution of the basel ine or app lication m odificatio ns to the baseline t hat is bei ng staged for produc tion befor e it becom e a Produc t Release.
176	For the BT SSS progra m all proj ect relate d document s will be managed an d controll ed in the Rational T eam Concer t designat ed reposit ory for th at type of document. All proj ect docume ntation mu st adhere to VA poli cy on prot ection of VA securit y and VA a rchitectur e content, desensiti zation of patient da ta content , Freedom of Informa tion Act ( FOIA) cont ent redact ion restri ctions, 50 8 accessib ility stan dards, and documenta tion stand ards where applicabl e.
177	Product Ar tifacts ar e those th at change along with the devel oped produ ct and mos t likely, will exper ience chan ge over ti me and thu s require baselining and Chang e Manageme nt. They a lso typica lly repres ent specif ic configu rations an d criteria required by the dev eloped rel ease of th e product to which t hey are as sociated w ith and th us should be package d and migr ated throu gh the sam e series o f life cyc les stages as all ot her baseli ned artifa cts within the devel opment env ironment a rchitectur e and util ities.
178	Configurat ion Contro l Process (CCP)
179	OIT and SD E have est ablished p rocess and procedure s that dic tate the c onfigurati on change control fo r all hard ware and s oftware co nfiguratio n items. A VA tool i s used for requestin g, approvi ng, implem enting, mo nitoring, and tracki ng, auditi ng and clo sing chang e orders a ffecting c onfigurati on items u nder chang e and conf iguration control.
180	Step 1: Es tablish Sy stem Confi guration B aseline
181	Step 2: Re view backl og, identi fy changes , and crea te change story
182	Step 3: Id entify cha nge storie s and plan Sprint
183	Step 4: Pe rform conf iguration changes
184	Step 5: Pe rform Secu rity and O perational Impact An alysis
185	Step 6: Im plement co nfiguratio n changes
186	Step 7: Ve rify imple mented cha nges are s uccessful and did no t introduc e addition al issues/ incidents into the e nvironment .
187	Step 8: Pe rform Conf iguration Status Acc ounting
188	Step 9: Co nduct Retr ospective which incl udes Confi guration V erificatio n and Audi t.
189	All produc t assets a re expecte d to be ma naged suff iciently t o provide a stable, traceable, dependabl e, and sec ured devel opment, te st, and, p roduction environmen t within V A and for VA informa tion asset s managed outside th e VA for t he purpose s of condu cting busi ness with or on beha lf of the VA. Config uration it ems in the scope of this docum ent are de fined as a ny object (software, hardware, data, doc umentation , environm ent config urations, etc.) that may exper ience chan ge over ti me.
190	The act of creating any softwa re deliver able impli es that ob jects will be create d and modi fied in th e design a nd develop ment proce ss, which by definit ion become CIs along with the environmen ts and doc umentation developed to suppor t them. Af ter develo pment is c omplete, t esting for validatio n and cert ification is require d. This ca n only be accomplish ed accurat ely if the integrity of the so ftware del iverable c an be main tained thr ough forma l change c ontrol.
191	Formal cha nge contro l involves the manag ement of c hanges and versions to the CIs that are introduced to the ba seline. Ch ange contr ol will al so apply t o product migration beyond dev elopment, to the var ious phase s of testi ng and cer tification , and unti l it is re leased int o a produc tion envir onment.
192	There are at least t wo levels of change control th at this do cument is addressing . The cha nge contro l that tak es place d uring the Software D evelopment Life Cycl e (SDLC) i s managed with the S CM change management processes and proce dures and the Operat ions chang e control is managed by OIT Ch ange Manag ement proc esses and procedures . The han doff betwe en softwar e developm ent and OI T will be handled by assigned staff from both depa rtments th at the SCM Manager w ill coordi nate.
193	The comple xity invol ved in the Change Co ntrol proc ess requir es the imp lementatio n of forma l processe s and proc edures to be documen ted in det ail for ea ch VA prod uct in the SCM. Proc edure Manu al(s) and work instr uctions. T hese docum ents provi de objecti ves, requi rements, a nd step-by -step inst ruction on the perfo rmance of Change Con trol activ ities with in the SCM Environme nt for eac h VA Produ ct. The do cument wil l also pro vide secti ons with i nformation on key pr ocess area s such as:
194	The organi zation of personnel and the di vision of tasks for the VA tea m members.
195	Decision c riteria an d escalati on require ments spec ific to ea ch level o f change r equest rev iew.
196	The overal l Change M anagement Process de scription and flow.
197	The descri ption of t he change control to ols and ho w the team will use them
198	Configurat ion Manage ment Resou rces
199	The Change Managemen t Systems (CMS) is t he automat ed mechani sm that is used for tracking p roposed ch anges to c onfigurati on items. Change ord ers are en tered into the syste m and work orders as signed to the approp riate grou ps for rev iew, appro val, imple mentation, configura tion statu s accounti ng and con figuration verificat ion. Chang es are tim e stamped to provide a timelin e and revi ewed per l ocal proce ss and pro cedures to ensure th at changes are proce ssed corre ctly and a re impleme nted to me et establi shed requi rements. C hanges are not imple mented wit hout appro val per OI T and SDE Change Man agement Po licy and p rocedures.
200	Each area of the org anization managing c hanges has a Change and Config uration Ma nagement D ivision th at is resp onsible of ensuring that appro priate con trol is pu t in place to manage the confi guration i tems per V A Handbook 6500 Conf iguration Management controls.
201	The VA uti lizes the Rational T eam Concer t tools to manage al l requirem ents, conf iguration items, tas ks, activi ties, buil ds and tes ting. This all-encom passing to ol provide s project staff and VA managem ent the ab ility to t rack any f ile, task, requireme nt or test ing throug h the vari ous stages of concep tion to de livery.
202	APPENDIX A : CONFIGUR ATION MANA GEMENT PLA N APPROVAL
203
204	The unders igned ackn owledge th at they ha ve reviewe d the BTSS S Configur ation Mana gement Pla n and agre e with the informati on present ed within this docum ent. Chang es to this Configura tion Manag ement Plan will be c oordinated with, and approved by, the un dersigned, or their designated represent atives.
205
206	__________ __________ __________ __________ __________ __________ __________ ________
207	Signature: Date:
208	Print Name :
209	Title:
210	Role:
211
212	__________ __________ __________ __________ __________ __________ __________ ________
213	Signature: Date:
214	Title:
215	Role:
216
217	__________ __________ __________ __________ __________ __________ __________ ________
218	Signature: Date:
219	Print Name :
220	Title:
221	Role:
222
223	Appendix B : Referenc es
224	The follow ing table summarizes the docum ents refer enced in t his docume nt.
225
226	Document N ame
227	Descriptio n
228	Location
229	VA Directi ve 6500
230	Managing I nformation Security Risk: VA I nformation Security Program
231	https:// DNS /vapubs/se arch_actio n.cfm?dTyp e=2
232
233	VA Handboo k 6500
234	Risk Manag ement Fram ework for VA Informa tion Syste ms – Tier 3: VA Info rmation Se curity Pro gram
235	https://ww w. DNS /vapubs/se arch_actio n.cfm?dTyp e=2
236	OIT Config uration Ma nagement P rocess
237	OIT Config uration Ma nagement P roPath def ined proce ss and sup porting do cument
238	https://DN S/
239	sites/fo/c ommittees/ ccb/CMDB/
240	Definitive %20Documen t%20Storag e/
241	oit_config uration_ma nagement_p rocess_doc ument.pdf
242	OIT Change Managemen t Process Document
243	OIT Change Managemen t ProPath defined pr ocess and supporting document
244	https://DN S/
245	sites/fo/c ommittees/ ccb/CMDB/
246	Definitive %20Documen t%20Storag e/
247	oit_change _managemen t_process_ document.p df
248	SDE Change Managemen t SOP
249	SDE Change Managemen t Standard Operation Procedure
250	https://DN Sv/
251	sites/fo/c ommittees/ ccb/CMDB/
252	Definitive %20Documen t%20Storag e/
253	National%2 0ChM%20Pro cess%20SOP .pdf
254	Master Tes t Plan
255	Master Tes t Plan Tem plate
256	https:// DNS /sites/bts ss/Shared% 20Document s/Forms/Al lItems.asp x?id=%2Fsi tes%2Fbtss s%2FShared %20Documen ts%2FData% 20Library% 2FProject% 20Docs%2FM TP
257
258	Appendix C : Key Term s
259	The follow ing table provides d efinitions and expla nations fo r terms an d acronyms relevant to the con tent prese nted withi n this doc ument.
260	Term
261	Definition
262	ALM
263	Agile Life cycle Mana gement
264	CAB
265	Change Adv isory Boar d
266	CCB
267	Change Con trol Board
268	CCP
269	Configurat ion Contro l Process
270	CI
271	Configurat ion Item
272	CM
273	Configurat ion Manage ment
274	CMS
275	Change Man agement Sy stems
276	CMDB
277	Configurat ion Manage ment Datab ase
278	CMP
279	Configurat ion Manage ment Plan
280	COR
281	Contractin g Officer Representa tive
282	CRMOL
283	Customer R elationshi p Manageme nt Online
284	DNS
285	Domain Nam e Service
286	FCIO
287	Facility C hief Infor mation Off icer
288	FOIA
289	Freedom of Informati on Act
290	IT
291	Informatio n Technolo gy
292	OIT
293	Office of Informatio n & Techno logy
294	OS
295	Operating System
296	POC
297	Point of C ontact
298	RACI
299	Responsibl e, Account able, Cons ulted, and Informed
300	RFC
301	Request fo r Change
302	SCM
303	Software C onfigurati on Managem ent
304	SDE
305	Service De livery and Engineeri ng
306	SOP
307	Standard O perating P rocedure
308	VA
309	Veterans A ffairs
310	VDD
311	Version De scription Documents
312	VIP
313	Veteran In formation Portal
314	VISN
315	Veterans I ntegrated Service Ne twork
316	Appendix D : Suggeste d Configur ation Item s Data Ele ments
317	Suggested standard d ata elemen ts (Data T ype and CI Type) and what type of data w ould be co llected an d how it w ould be us ed.
318	Field Name
319	Data Type
320	CI Type
321	Descriptio n
322	Resource N ame
323	Indexed Te xt
324	Hardware / Software / Service / Document
325	A unique n ame of the Configura tion Item (CI). A n ame that r epresents the Resour ce and is easy to id entify wha t it is; a key searc h field wi thin the C onfigurati on Managem ent Databa se (CMDB).
326	DNS Name
327	Indexed Te xt
328	Hardware
329	The name o f the CI a s identifi ed within your Domai n Name Ser vice (DNS) ; this hel ps with as sociation of service s or serve rs to a CI .
330	Status
331	Lookup Tab le
332	Hardware / Software / Service / Document
333	The curren t status o f the CI. For exampl e: when fi rst added to the CMD B, the CI may be in a status o f Register ed, then l ater it ma y be Accep ted. This identifies how the r ecord move s through the status /lifecycle ; if a cha nge is bei ng perform ed on the CI the sta tus would be changed to Change in Progre ss, thus i dentifying CI’s that are curre ntly under going some form of a change.
334	Descriptio n
335	Free Text Multiple L ines
336	Hardware / Software / Service / Document
337	A short de scription that will provide ad ditional f eedback to the end u ser when l ooking up the CI.
338	CI Type
339	Lookup Tab le
340	Hardware / Software / Service / Document
341	This is th e type tha t the CI b elongs to. See list of suggest ed family types.
342	Asset Clas s
343	Lookup Tab le
344	Hardware / Software / Service / Document
345	This is th e classifi cation of the config uration it em; it is related to the famil y, but is a more spe cific clas sification of an ass et. This i s the sub- type that the CI bel ongs to; i t is used to group c ommon type s on confi guration i tems. An e xample wou ld be “Lap top”; the “Laptop” C lass is wi thin the h ardware Ty pe.
346	Comments
347	Free Text Multiple L ines
348	Hardware / Software / Service / Document
349	Comments r egarding t he specifi c CI; note s that nee d to be pa rt of the record his tory but a re not wit hin the De scription of the CI.
350	COR
351	Contact Ta ble Lookup
352	Hardware / Software / Service
353	Contractin g Officer Representa tive (COR) associate d with thi s particul ar purchas e or CI.
354	Customer N ame
355	Contact Ta ble Lookup
356	Hardware / Software / Service / Document
357	Name of th e Customer point of contact fo r issues w ith the CI . This per son or gro up is the primary fo cus point when issue s or chang es are rel ated to th e CI.
358	Customer O rganizatio n
359	Lookup Tab le
360	Hardware / Software / Service / Document
361	Name of th e Organiza tion that the custom er belongs to. Provi des report ing inform ation abou t what CI’ s are asso ciated to a specific organizat ion.
362	Deployed D ate
363	Date
364	Hardware / Software / Service / Document
365	The date t hat a serv ice, syste m, etc. wa s deployed to the pr oduction e nvironment .
366	Financial Reference
367	Free Text
368	Hardware / Software
369	A Purchase Order tha t was used to obtain the hardw are or sof tware. It is useful when looki ng up othe r informat ion that m ay be foun d in relat ed databas es like th e Asset Ma nagement s ystem.
370	Function
371	Lookup Tab le
372	Hardware
373	The functi on or purp ose that t he hardwar e Configur ation Item serves.
374	Host Name
375	Free Text
376	Hardware
377	In some ca ses, like UNIX, ther e is a pur pose to id entify the host name ; this is on the sam e as DNS N ame.
378	License Co unt
379	Numeric
380	Software
381	A number o f copies t hat a part icular lic ense allow s the owne r to distr ibute. It can be use d to deter mine if ad ditional s oftware li censes are needed or if there are too ma ny license s unused.
382	Type of Li censes
383	Lookup Tab le
384	Software
385	The type o f license that has b een procur ed, perpet ual or rec urring.
386	License Ke y Maintain ed By
387	Contact ta ble Lookup
388	Software
389	Who mainta ins the So ftware Lic ense Key t hat is use d to insta ll the sof tware?
390	Lifecycle Date
391	Date
392	Hardware / Software / Service
393	This is a date in th e future d erived fro m the inst all date a nd Informa tion Techn ology (IT) equipment life expe ctancy.
394	Location
395	Lookup Tab le
396	Hardware / Software / Service / Document
397	The locati on where t his partic ular CI is hosted or installed . More spe cific loca tion field s may be n eeded, suc h as room, floor, an d rack as part of th e physical location.
398	Maintenanc e Organiza tion
399	Lookup Tab le
400	Hardware / Software / Service
401	Name of th e Organiza tion that has Mainte nance resp onsibility over the CI; normal ly found w ithin the Operations and Maint enance (O& M) Plan.
402	Maintenanc e Vendor
403	Lookup Tab le
404	Hardware / Software / Service
405	The vendor that woul d support the Mainte nance Orga nization w ith a Warr anty or ot her type o f maintena nce agreem ent.
406	Manufactur er
407	Lookup Tab le
408	Hardware / Software
409	Manufactur er of the CI being e ntered int o the CMDB . Name use d for repo rting main tenance co ntracts or other dat a related to a speci fic manufa cturer.
410	Model
411	Lookup Tab le
412	Hardware / Software
413	The manufa cturer’s m odel name for the de vice. Rel ates to th e manufact urer; used for repor ting and f or mainten ance contr acts.
414	Version Nu mber
415	Free Text
416	Software / Document
417	Version Nu mber of so ftware or documents. This pro vides a ba seline as to what ve rsion of s oftware is installed /authorize d in produ ction or t he version of a docu ment that was approv ed and pub lished. No version c hanges unl ess there is a chang e process for it.
418	Maintenanc e Window
419	Free Text
420	Hardware / Software / Service
421	Maintenanc e windows are establ ished base d on Servi ce Level A greements (SLA’s) or other agr eements fo r specific services that are a vailable t o the end user. The Maintenanc e windows that are a ssociated with the C I’s should clearly s tate if th ey are rec urring mai ntenance w indows, th e days of the week t hat they a re ava
		422	ilable, an d the hour s of the d ay that th ey can be used. Exam ple: Recur ring - Mon day – Frid ay 7 to 11 PM Contac t (name or role of t he person that shoul d be conta cted to va lidate/ver ify the ma intenance window).
423	Operating System
424	Look Up Ta ble
425	Hardware / Software
426	Identifies the Opera ting Syste m (OS) run ning on th e server, virtual ma chine, lap tops or wo rkstations . It is us ed for pat ching, SA assignment , reportin g purposes , licensin g, etc. N OTE: If th is informa tion is av ailable fr om other t ools that can report this info rmation an d is not n eeded as p art of int ernal repo rting or l inked to o ther field s that are not part of the ext ernal data source, t hen this f ield could be left o ut.
427	Published Date
428	Date
429	Document
430	The date t hat a docu ment was p ublished f or general consumpti on.
431	Region
432	Lookup Tab le
433	Hardware / Software / Service / Document
434	OIT is bro ken out in to differe nt regiona l areas. M ost have t heir own p rocesses a nd procedu res or hav e equipmen t and soft ware that is regiona lized. If the CMDB h olds cross -regional CI’s these should be identifie d for repo rting purp oses; othe rwise, the Organizat ional fiel d should p rovide the needed fe edback.
435	Relationsh ips
436	Lookup Tab le
437	Hardware / Software / Service / Document
438	Field is a one-to-ma ny relatio nship used to identi fy a relat ionship be tween 2 or more CI’s and the t ype of rel ationship that the C I has. Thi s relation ship could be with c ontacts, o ther hardw are, softw are, servi ces or doc ument CI’s . An examp le of type s of relat ionships a re listed below:
439	Changes Ap proved By
440	Connects T o
441	Is Documen ted By
442	Runs/Runs On
443	Renewal Da te
444	Date
445	Hardware / Software
446	A renewal date is us ed to esta blish when a particu lar CI’s m aintenance agreement will expi re and wou ld require renewal t o continue with the service.
447	Cost of Ma intenance Agreement
448	Numbers
449	Hardware / Software
450	Recurring cost of ma intenance agreements purchased under the contract.
451	Responsibl e Organiza tion
452	Lookup Tab le
453	Hardware / Software / Service / Document
454	The Organi zation tha t has resp onsibility over the CI. It may be the sa me as main tenance or customer organizati on or a di fferent on e.
455	Responsibl e Owner
456	Contact Lo okup Table
457	Hardware / Software / Service / Document
458	A primary point of c ontact who has been identified as the Po int of Con tact (POC) for the R esponsible Organizat ion.
459	Responsibl e Vendor
460	Lookup Tab le
461	Hardware / Software
462	The Respon sible Vend or for a p articular CI may be the same a s Maintena nce Vendor or may be a differe nt vendor if mainten ance is su b-contract ed out by the Primar y Responsi ble Vendor .
463	Secondary Contact
464	Contact Lo okup Table
465	Hardware / Software / Service / Document
466	This would be an alt ernate Poi nt of Cont act that c ould be co ntacted in the absen ce of the Primary PO C,
467	Serial Num ber
468	Alpha-Nume ric Free T ext
469	Hardware
470	Serial Num bers are u nique iden tification elements that are d irectly re lated to a sset manag ement; but by includ ing it wit hin your C MDB you co uld link t o other da tabases th at track t heir CI’s by Serial Number.
471	Service Li ne
472	Lookup Tab le
473	Hardware / Software / Service / Document
474	Support is broken do wn by Serv ice Lines within OIT Field Ope rations, p roviding a Service L ine associ ated to th e CI would expedite maintenanc e issues a nd provide reporting capabilit ies on the type and number of CI’s being maintaine d by a par ticular se rvice line .
475	Service Li ne Team/Di vision
476	Lookup Tab le
477	Hardware / Software / Service / Document
478	As Service Lines are stood up, so are th e Service Line Teams /Divisions that supp ort the se rvice line and have a more def ined scope of their responsibi lities. Ca pturing th is type of informati on would p rovide you with the same infor mation as Service Li ne would b ut allow y ou to brea k it down by the Ser vice Line Team Divis ion.
479	Source Sup plier
480	Lookup Tab le
481	Hardware
482	Used for h ardware su pport, thi s is the v endor that purchased the equip ment from the manufa cturer. It is receiv ed obtaine d from the Purchase Order Cont ract.
483	Created By
484	System Con tact Field
485	Hardware / Software / Service / Document
486	This is an audit fie ld; it cap tures the name of th e person t hat create d the reco rd. This s hould be a system fi eld and ca ptured bas ed on who was logged in during the creat ion of the record.
487	Created Da te
488	System Dat e Field
489	Hardware / Software / Service / Document
490	Initial da te of crea tion of th e Configur ation Item Record.
491	Modified B y
492	System Con tact Field
493	Hardware / Software / Service / Document
494	This is an audit fie ld; the pe rson who l ast edited the recor d would be listed. T his should be a syst em field a nd capture d based on who was l ogged in d uring the modificati on.
495	Modified D ate
496	System Dat e Field
497	Hardware / Software / Service / Document
498	Date the C onfigurati on Item Re cord was l ast modifi ed.
499
500	Appendix E : [Facilit y] Current Configura tion Basel ine Report
501
502	The follow ing table details th e Hardware /Software and Servic es associa ted with t he system under this CMP.
503
504
505	Appendix F : Configur ation Item s (CI) Sho wing Syste m Boundari es
506
507
508
509	Appendix G : Change O rder Appro val Checkl ist
510
511	Reviewer a nd Approve r must be different (the perso n putting together t he plan, a nd the per son approv ing the pl an)
512	Correct lo cation ent ered?
513	Change Ord er descrip tion conta ins requir ed informa tion
514	What is be ing done?
515	The busine ss case fo r doing it .
516	What is th e impact o f the chan ge (what s ervices wi ll be impa cted and w hat will t he impact most likel y be)?
517	What else may be imp acted?
518	What will occur if w e don’t do the chang e?
519	The implem entation p lan should be attach ed, never be pasted, into the descriptio n.
520	Were the c ustomers/s takeholder s notified as per th e Change A dvisory Bo ard (CAB) process?
521	CAB notifi cation in the ticket .
522	Facility O IT respons e or ignor e entered as a log c omment.
523	Is the imp lementatio n plan att ached?
524	Is the Not ification and Escala tion secti on complet e?
525	Does the i mplementat ion plan p rovide suf ficient de tail so th at a peer who is unf amiliar wi th the par ticular fa cility whe re the imp lementatio n is takin g place co uld execut e the plan ?
526	Does the i mplementat ion plan i nclude a t est plan t hat contai ns checkpo ints for v erificatio n, coordin ation, or implementi ng back-ou t?
527	Are verifi cation ste ps (Test P lan) inclu ded?
528	Do the ver ification steps ensu re the cus tomers are functioni ng and not just the item modif ied is wor king?
529	Is the bac k-out plan attached?
530	Is the not ification plan inclu ded?
531	Are verifi cation ste ps include d?
532	Do the ver ification steps ensu re the cus tomers are functioni ng, the se rvices imp acted are operationa l, and not just the item modif ied is wor king?
533	Is the nee d by date realistic?
534	Is there a n implemen tation dat e/time pri or to the need by da te?
535
536	If everyth ing is acc urate and all docume ntation at tached, ch ange Statu s to Appro ved and/or escalate to next le vel Change Control B oard (CCB) if this i s a signif icant chan ge/downtim e required .
537
538
539	Appendix H : Change O rder Imple mentation Plan Templ ate
540	Local faci lity Notif ication an d Escalati on Contact s
541	Name/Role
542	Business
543	After-hour s
544	John Doe, FCIO
545	333-345-67 89
546	333-987-65 43
547
548
549
550	VISN/Servi ce Line No tification and Escal ation Cont acts
551	Name/Role
552	Business
553	After-hour s
554
555
556
557	Any pre-im plementati on work th at will be required
558
559	Step-by-st ep guidanc e for what needs to be done in cluding ti me estimat es, escala tion and c oordinatio n points
560
561	Identifica tion of ar eas that m ight cause problems
562
563	Identifica tion of ro ll-back po ints and/o r criteria for initi ating the Back-out p lan
564
565	Test/valid ation step s for the verificati on phase – include v alidation that custo mers are f unctioning and not j ust the it em modifie d (See Mas ter Test P lan Templa te)
566
567
568
569
570	Appendix I : Business Case Just ification
571
572	Please pro vide a det ailed desc ription of this chan ge.
573
574	List the r equirement s needed f or the cha nge (i.e., servers, switches, software, etc.).
575
576	Describe t he effect the change may have upon the e nd user, b usiness op eration, a nd infrast ructure, i f known.
577
578	Describe t he impact on and the availabil ity to oth er service s that run on the sa me infrast ructure (o r on softw are develo pment proj ects).
579
580	Describe t he effect of not imp lementing the change .
581
582	Estimate t he IT, bus iness, and other res ources req uired to i mplement t he change, including the likel y costs, t he number and availa bility of people req uired, the elapsed t ime, and a ny new inf rastructur e elements required.
583
584	Estimate a ny additio nal ongoin g resource s required if the ch ange is im plemented.
585
586	Document d owntime pr ocedures.
587
588
589	Document c ommunicati on procedu res (i.e., who needs to be not ified in t he event o f schedule d/unschedu led downti me and how to notify this pers on).
590
591
592
593	Appendix J : Change M anagement Back-Out P lan Templa te
594	Change Ord er
595	Affected S ystems
596
597
598	Estimated time-frame s for rest oring serv ice
599
600	Any pre-im plementati on work th at will be required
601
602	Step-by-st ep guidanc e to resto re service to the pr e-change s tate
603
604