1. EPMO Open Source Coordination Office Redaction File Detail Report

Produced by Araxis Merge on 8/2/2018 1:55:22 PM Central Daylight 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_06152018.zip\BTSSS_CIF_03152018	BTSSS_CMP.docx	Tue Mar 27 16:11:44 2018 UTC
2	BTSSS_CIF_06152018.zip\BTSSS_CIF_03152018	BTSSS_CMP.docx	Wed Aug 1 15:10:42 2018 UTC

1.2 Comparison summary

Description	Between Files 1 and 2
Description	Text Blocks	Lines
Unchanged	4	1228
Changed	3	6
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	December 2 017
	7	Version 4. 03
	8	Department of Vetera ns Affairs
	9
	10
	11	Version Hi story
	12	Date
	13	Version
	14	Descriptio n
	15	Author
	16	12/5/2017
	17	4.03
	18	December M onthly Upd ate – Chan ged date o n cover pa ge and foo ters
	19	Joanne Wuw er-Saukas
	20	11/9/2017
	21	4.02
	22	November M onthly Upd ate – chan ged date o n cover pa ge and foo ters
	23	Christina Silva
	24	10/11/2017
	25	4.01
	26	October Mo nthly Upda te – no ch anges
	27	Christina Silva
	28	9/18/2017
	29	3.04
	30	September Monthly Up date
	31	Christina Silva
	32	8/31/2017
	33	3.03
	34	CRMOL upda te
	35	Christina Silva
	36	8/21/2017
	37	3.02
	38	August Mon thly Updat e
	39	Christina Silva
	40	7/19/2017
	41	3.01
	42	July Month ly Update
	43	Christina Silva
	44	6/16/2017
	45	2.03
	46	June Month ly Update
	47	Christina Silva
	48	5/18/2017
	49	2.02
	50	May Monthl y Update
	51	Christina Silva
	52	4/18/2017
	53	2.01
	54	April Mont hly Update
	55	Christina Silva
	56	3/15/2017
	57	1.03
	58	March Mont hly Update
	59	Christina Silva
	60	2/24/2017
	61	1.02
	62	February M onthly Upd ate
	63	Christina Silva
	64	1/26/2016
	65	1.01
	66	January Mo nthly Upda te
	67	Christina Silva
	68	12/2/2016
	69	0.04
	70	December M onthly Upd ate
	71	Scott Bart el
	72	10/31/2016
	73	0.03
	74	Initial Re lease
	75	Karen Shep herd
	76	10/28/2016
	77	0.02
	78	Edited Doc ument Per Comments
	79	Karen Shep herd
	80	10/26/2016
	81	0.01
	82	Initial Dr aft
	83	Karen Shep herd
	84
	85
	86
	87	Table of C ontents
	88	1.Executiv e Summary1
	89	2.Introduc tion1
	90	2.1Purpose of the Co nfiguratio n Manageme nt Plan1
	91	2.2Scope o f the Conf iguration Management Plan2
	92	2.3Structu re of the Configurat ion Manage ment Plan2
	93	3Configura tion Manag ement Acti vities2
	94	3.1Roles a nd Respons ibilities2
	95	3.2Communi cation4
	96	3.3System Configurat ion Baseli ne4
	97	3.4Configu ration Con trol Proce ss (CCP)5
	98	3.5Configu ration Man agement Re sources7
	99	APPENDIX A : CONFIGUR ATION MANA GEMENT PLA N APPROVAL 8
	100	Appendix B : Referenc es9
	101	Appendix C : Key Term s10
	102	Appendix D : Suggeste d Configur ation Item s Data Ele ments11
	103	Appendix E : [Facilit y] Current Configura tion Basel ine Report 16
	104	Appendix F : Configur ation Item s (CI) Sho wing Syste m Boundari es17
	105	Appendix G : Change O rder Appro val Checkl ist18
	106	Appendix H : Change O rder Imple mentation Plan Templ ate19
	107	Appendix I : Business Case Just ification2 0
	108	Appendix J : Change M anagement Back-Out P lan Templa te21
	109
	110	Executive Summary
	111	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.
	112	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 proces s and proc edures out lined in t his docume nt will co nform with the exist ing VA CM tools and the overar ching VA C onfigurati on Managem ent Plan ( CMP) in th e Rational repositor y. The CMP will also support t he unified Veteran I nformation Portal (V IP) Releas e process utilizing agile deve lopment, f requent bu ilds and r eleases, a nd a high level of i ntegration with Agil e Lifecycl e Manageme nt (ALM) t ools, with automated builds an d testing. ALM and t esting dat a will nee d to be st ored in th e VIP Rati onal Repos itory.
	113	Introducti on
	114	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).
	115	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.
	116	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).
	117
	118	Purpose of the Confi guration M anagement Plan
	119	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.
	120	Scope of t he Configu ration Man agement Pl an
	121	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:
	122	Identifyin g, definin g, and bas e-lining C Is
	123	Creating C I Records
	124	Identifyin g relation ships
	125	Controllin g modifica tions and releases o f CIs
	126	Reporting and record ing status of CIs an d any requ ired modif ications
	127	Ensuring c ompletenes s, consist ency, and correctnes s of CIs
	128	Controllin g storage, handling, and deliv ery of the CIs
	129	Structure of the Con figuration Managemen t Plan
	130	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.
	131	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.
	132	Configurat ion Manage ment Activ ities
	133	Roles and Responsibi lities
	134	Table 1: R oles and R esponsibil ities
	135	Role
	136	Responsibi lity
	137	Program Ma nager
	138	• Oversees the softw are config uration ma nagement p rocess.
	139	• Ensures proper exe cution of the BTSSS Plan.
	140	• Identify dependent projects.
	141	Configurat ion Manage r
	142
	143	• 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 .
	144	• Educates project t eam member s in SCM “ best pract ices.”
	145	• Accounta ble for in stituting the establ ished proc esses and reporting progress s tatistics based on c hange requ ests.
	146	• Identifi es product baselines as necess ary of all products within the ir assigne d projects .
	147	• Responsi ble for SC M audits a nd necessa ry status accounting related t o the prod uct.
	148	• Maintain s artifact s followin g proper v ersion con trol proce dures.
	149	Software C hange/Buil d Administ rator
	150	• Develops and maint ains artif acts follo wing prope r version control pr ocedures.
	151	• Establis hes, promo tes, and r eleases ba selines.
	152	• Performs or valida tes interi m and fina l builds.
	153	• Identifi es product baselines as necess ary of all products within the ir assigne d projects .
	154	Developmen t Manager/ Technical Lead
	155	• Prepares release p ackage, re lease arch ives and V ersion Des cription D ocuments ( VDD).
	156	• 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.
	157	• 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 .
	158	Developers /System Ad ministrati on
	159	• 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.
	160	• 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.
	161	• Provide impact ana lysis repo rting prob lems or ch anges, inc luding doc umentation of sugges ted soluti ons.
	162	• Document ation of b uild, rele ase, and i nstallatio n instruct ions.
	163	Software Q uality Ass urance Ana lyst/Testi ng Analyst
	164	• Update s tories ass igned to t hem accord ing to tes t activity results.
	165	• Determin es Pass/Fa il for eac h story sc heduled fo r a sprint release.
	166	• 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.
	167	Technical Writer
	168	• Develops technical deliverab le documen tation to support th e software deliverab les.
	169	• Provides editing, formatting , and grap hics suppo rt for doc umentation .
	170	Implementa tion Team/ Operations Team
	171	• 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 .
	172	• 365 Clou d
	173
	174	Communicat ion
	175	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.
	176	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.
	177	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.
	178	System Con figuration Baseline
	179	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.
	180	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:
	181
	182	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.
	183	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.
	184	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.
	185	Build – Id entifies a set of so lution fil e versions used to b uild and a ssemble de ployable p ackages.
	186	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.
	187	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 es a Produ ct Release .
	188	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 proje ct documen tation mus t adhere t o VA polic y on prote ction of V A security and VA ar chitecture content, desensitiz ation of p atient dat a content, Freedom o f Informat ion Act (F OIA) conte nt redacti on restric tions, 508 accessibi lity stand ards, and documentat ion standa rds where applicable .
	189	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.
	190	Configurat ion Contro l Process (CCP)
	191	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.
	192	Step 1: Es tablish Sy stem Confi guration B aseline
	193	Step 2: Re view backl og, identi fy changes , and crea te change story
	194	Step 3: Id entify cha nge storie s and plan Sprint
	195	Step 4: Pe rform conf iguration changes
	196	Step 5: Pe rform Secu rity and O perational Impact An alysis
	197	Step 6: Im plement co nfiguratio n changes
	198	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 .
	199	Step 8: Pe rform Conf iguration Status Acc ounting
	200	Step 9: Co nduct Retr ospective which incl udes Confi guration V erificatio n and Audi t.
	201	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.
	202	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.
	203	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.
	204	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.
	205	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 Proce dure Manua l(s) and w ork instru ctions. Th ese docume nts provid e objectiv es, requir ements, an d step-by- step instr uction on the perfor mance of C hange Cont rol activi ties withi n the SCM Environmen t for each VA Produc t. The doc ument will also prov ide sectio ns with in formation on key pro cess areas such as:
	206	The organi zation of personnel and the di vision of tasks for the VA tea m members.
	207	Decision c riteria an d escalati on require ments spec ific to ea ch level o f change r equest rev iew.
	208	The overal l Change M anagement Process de scription and flow.
	209	The descri ption of t he change control to ols and ho w the team will use them
	210	Configurat ion Manage ment Resou rces
	211	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.
	212	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.
	213	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.
	214	APPENDIX A : CONFIGUR ATION MANA GEMENT PLA N APPROVAL
	215
	216	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.
	217
	218	__________ __________ __________ __________ __________ __________ __________ ________
	219	Signature: Date:
	220	Print Name :
	221	Title:
	222	Role:
	223
	224	__________ __________ __________ __________ __________ __________ __________ ________
	225	Signature: Date:
	226	Title:
	227	Role:
	228
	229	__________ __________ __________ __________ __________ __________ __________ ________
	230	Signature: Date:
	231	Print Name :
	232	Title:
	233	Role:
	234
	235	Appendix B : Referenc es
	236	The follow ing table summarizes the docum ents refer enced in t his docume nt.
	237
	238	Document N ame
	239	Descriptio n
	240	Location
	241	VA Directi ve 6500
	242	Managing I nformation Security Risk: VA I nformation Security Program
	243	https://ww w.va.gov/v apubs/sear ch_action. cfm?dType= 2
	244
	245	VA Handboo k 6500
	246	Risk Manag ement Fram ework for VA Informa tion Syste ms – Tier 3: VA Info rmation Se curity Pro gram
	247	https://ww w.va.gov/v apubs/sear ch_action. cfm?dType= 2
	248	OIT Config uration Ma nagement P rocess
	249	OIT Config uration Ma nagement P roPath def ined proce ss and sup porting do cument
	250	https:// u r l /
	251	sites/fo/c ommittees/ ccb/CMDB/
	252	Definitive %20Documen t%20Storag e/
	253	oit_config uration_ma nagement_p rocess_doc ument.pdf
	254	OIT Change Managemen t Process Document
	255	OIT Change Managemen t ProPath defined pr ocess and supporting document
	256	https:// u r l /
	257	sites/fo/c ommittees/ ccb/CMDB/
	258	Definitive %20Documen t%20Storag e/
	259	oit_change _managemen t_process_ document.p df
	260	SDE Change Managemen t SOP
	261	SDE Change Managemen t Standard Operation Procedure
	262	https:// u r l /
	263	sites/fo/c ommittees/ ccb/CMDB/
	264	Definitive %20Documen t%20Storag e/
	265	National%2 0ChM%20Pro cess%20SOP .pdf
	266	Master Tes t Plan
	267	Master Tes t Plan Tem plate
	268	https://wa rriortechn ology.shar epoint.com /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
	269
	270	Appendix C : Key Term s
	271	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.
	272	Term
	273	Definition
	274	ALM
	275	Agile Life cycle Mana gement
	276	BTSSS
	277	Beneficiar y Travel S elf-Servic e System
	278	CAB
	279	Change Adv isory Boar d
	280	CCB
	281	Change Con trol Board
	282	CCP
	283	Configurat ion Contro l Process
	284	CI
	285	Configurat ion Item
	286	CM
	287	Configurat ion Manage ment
	288	CMS
	289	Change Man agement Sy stems
	290	CMDB
	291	Configurat ion Manage ment Datab ase
	292	CMP
	293	Configurat ion Manage ment Plan
	294	COR
	295	Contractin g Officer Representa tive
	296	CRMOL
	297	Customer R elationshi p Manageme nt Online
	298	DNS
	299	Domain Nam e Service
	300	FCIO
	301	Facility C hief Infor mation Off icer
	302	FOIA
	303	Freedom of Informati on Act
	304	IT
	305	Informatio n Technolo gy
	306	OIT
	307	Office of Informatio n & Techno logy
	308	OS
	309	Operating System
	310	POC
	311	Point of C ontact
	312	RACI
	313	Responsibl e, Account able, Cons ulted, and Informed
	314	RFC
	315	Request fo r Change
	316	SCM
	317	Software C onfigurati on Managem ent
	318	SDE
	319	Service De livery and Engineeri ng
	320	SOP
	321	Standard O perating P rocedure
	322	VA
	323	Veterans A ffairs
	324	VDD
	325	Version De scription Documents
	326	VIP
	327	Veteran In formation Portal
	328	VISN
	329	Veterans I ntegrated Service Ne twork
	330	Appendix D : Suggeste d Configur ation Item s Data Ele ments
	331	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.
	332	Field Name
	333	Data Type
	334	CI Type
	335	Descriptio n
	336	Resource N ame
	337	Indexed Te xt
	338	Hardware / Software / Service / Document
	339	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).
	340	DNS Name
	341	Indexed Te xt
	342	Hardware
	343	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 .
	344	Status
	345	Lookup Tab le
	346	Hardware / Software / Service / Document
	347	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.
	348	Descriptio n
	349	Free Text Multiple L ines
	350	Hardware / Software / Service / Document
	351	A short de scription that will provide ad ditional f eedback to the end u ser when l ooking up the CI.
	352	CI Type
	353	Lookup Tab le
	354	Hardware / Software / Service / Document
	355	This is th e type tha t the CI b elongs to. See list of suggest ed family types.
	356	Asset Clas s
	357	Lookup Tab le
	358	Hardware / Software / Service / Document
	359	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.
	360	Comments
	361	Free Text Multiple L ines
	362	Hardware / Software / Service / Document
	363	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.
	364	COR
	365	Contact Ta ble Lookup
	366	Hardware / Software / Service
	367	Contractin g Officer Representa tive (COR) associate d with thi s particul ar purchas e or CI.
	368	Customer N ame
	369	Contact Ta ble Lookup
	370	Hardware / Software / Service / Document
	371	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.
	372	Customer O rganizatio n
	373	Lookup Tab le
	374	Hardware / Software / Service / Document
	375	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.
	376	Deployed D ate
	377	Date
	378	Hardware / Software / Service / Document
	379	The date t hat a serv ice, syste m, etc. wa s deployed to the pr oduction e nvironment .
	380	Financial Reference
	381	Free Text
	382	Hardware / Software
	383	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.
	384	Function
	385	Lookup Tab le
	386	Hardware
	387	The functi on or purp ose that t he hardwar e Configur ation Item serves.
	388	Host Name
	389	Free Text
	390	Hardware
	391	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.
	392	License Co unt
	393	Numeric
	394	Software
	395	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.
	396	Type of Li censes
	397	Lookup Tab le
	398	Software
	399	The type o f license that has b een procur ed, perpet ual or rec urring.
	400	License Ke y Maintain ed By
	401	Contact ta ble Lookup
	402	Software
	403	Who mainta ins the So ftware Lic ense Key t hat is use d to insta ll the sof tware?
	404	Lifecycle Date
	405	Date
	406	Hardware / Software / Service
	407	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.
	408	Location
	409	Lookup Tab le
	410	Hardware / Software / Service / Document
	411	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.
	412	Maintenanc e Organiza tion
	413	Lookup Tab le
	414	Hardware / Software / Service
	415	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.
	416	Maintenanc e Vendor
	417	Lookup Tab le
	418	Hardware / Software / Service
	419	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.
	420	Manufactur er
	421	Lookup Tab le
	422	Hardware / Software
	423	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.
	424	Model
	425	Lookup Tab le
	426	Hardware / Software
	427	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.
	428	Version Nu mber
	429	Free Text
	430	Software / Document
	431	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.
	432	Maintenanc e Window
	433	Free Text
	434	Hardware / Software / Service
	435	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 availab le, and th e hours of the day t hat they c an be used . Example: Recurring - Monday – Friday 7 to 11 PM Contact (n ame or rol e of the p erson that should be contacted to valida te/verify the mainte nance wind ow).
	436	Operating System
	437	Look Up Ta ble
	438	Hardware / Software
	439	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.
	440	Published Date
	441	Date
	442	Document
	443	The date t hat a docu ment was p ublished f or general consumpti on.
	444	Region
	445	Lookup Tab le
	446	Hardware / Software / Service / Document
	447	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.
	448	Relationsh ips
	449	Lookup Tab le
	450	Hardware / Software / Service / Document
	451	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:
	452	Changes Ap proved By
	453	Connects T o
	454	Is Documen ted By
	455	Runs/Runs On
	456	Renewal Da te
	457	Date
	458	Hardware / Software
	459	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.
	460	Cost of Ma intenance Agreement
	461	Numbers
	462	Hardware / Software
	463	Recurring cost of ma intenance agreements purchased under the contract.
	464	Responsibl e Organiza tion
	465	Lookup Tab le
	466	Hardware / Software / Service / Document
	467	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.
	468	Responsibl e Owner
	469	Contact Lo okup Table
	470	Hardware / Software / Service / Document
	471	A primary point of c ontact who has been identified as the Po int of Con tact (POC) for the R esponsible Organizat ion.
	472	Responsibl e Vendor
	473	Lookup Tab le
	474	Hardware / Software
	475	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 .
	476	Secondary Contact
	477	Contact Lo okup Table
	478	Hardware / Software / Service / Document
	479	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,
	480	Serial Num ber
	481	Alpha-Nume ric Free T ext
	482	Hardware
	483	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.
	484	Service Li ne
	485	Lookup Tab le
	486	Hardware / Software / Service / Document
	487	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 .
	488	Service Li ne Team/Di vision
	489	Lookup Tab le
	490	Hardware / Software / Service / Document
	491	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.
	492	Source Sup plier
	493	Lookup Tab le
	494	Hardware
	495	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.
	496	Created By
	497	System Con tact Field
	498	Hardware / Software / Service / Document
	499	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.
	500	Created Da te
	501	System Dat e Field
	502	Hardware / Software / Service / Document
	503	Initial da te of crea tion of th e Configur ation Item Record.
	504	Modified B y
	505	System Con tact Field
	506	Hardware / Software / Service / Document
	507	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.
	508	Modified D ate
	509	System Dat e Field
	510	Hardware / Software / Service / Document
	511	Date the C onfigurati on Item Re cord was l ast modifi ed.
	512
	513	Appendix E : [Facilit y] Current Configura tion Basel ine Report
	514
	515	The follow ing table details th e Hardware /Software and Servic es associa ted with t he system under this CMP.
	516
	517
	518	Appendix F : Configur ation Item s (CI) Sho wing Syste m Boundari es
	519
	520
	521
	522	Appendix G : Change O rder Appro val Checkl ist
	523
	524	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)
	525	Correct lo cation ent ered?
	526	Change Ord er descrip tion conta ins requir ed informa tion
	527	What is be ing done?
	528	The busine ss case fo r doing it .
	529	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)?
	530	What else may be imp acted?
	531	What will occur if w e don’t do the chang e?
	532	The implem entation p lan should be attach ed, never be pasted, into the descriptio n.
	533	Were the c ustomers/s takeholder s notified as per th e Change A dvisory Bo ard (CAB) process?
	534	CAB notifi cation in the ticket .
	535	Facility O IT respons e or ignor e entered as a log c omment.
	536	Is the imp lementatio n plan att ached?
	537	Is the Not ification and Escala tion secti on complet e?
	538	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 ?
	539	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?
	540	Are verifi cation ste ps (Test P lan) inclu ded?
	541	Do the ver ification steps ensu re the cus tomers are functioni ng and not just the item modif ied is wor king?
	542	Is the bac k-out plan attached?
	543	Is the not ification plan inclu ded?
	544	Are verifi cation ste ps include d?
	545	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?
	546	Is the nee d by date realistic?
	547	Is there a n implemen tation dat e/time pri or to the need by da te?
	548
	549	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 .
	550
	551
	552	Appendix H : Change O rder Imple mentation Plan Templ ate
	553	Local faci lity Notif ication an d Escalati on Contact s
	554	Name/Role
	555	Business
	556	After-hour s
	557	John Doe, FCIO
	558	333-345-67 89
	559	333-987-65 43
	560
	561
	562
	563	VISN/Servi ce Line No tification and Escal ation Cont acts
	564	Name/Role
	565	Business
	566	After-hour s
	567
	568
	569
	570	Any pre-im plementati on work th at will be required
	571
	572	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
	573
	574	Identifica tion of ar eas that m ight cause problems
	575
	576	Identifica tion of ro ll-back po ints and/o r criteria for initi ating the Back-out p lan
	577
	578	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)
	579
	580
	581
	582
	583	Appendix I : Business Case Just ification
	584
	585	Please pro vide a det ailed desc ription of this chan ge.
	586
	587	List the r equirement s needed f or the cha nge (i.e., servers, switches, software, etc.).
	588
	589	Describe t he effect the change may have upon the e nd user, b usiness op eration, a nd infrast ructure, i f known.
	590
	591	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).
	592
	593	Describe t he effect of not imp lementing the change .
	594
	595	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.
	596
	597	Estimate a ny additio nal ongoin g resource s required if the ch ange is im plemented.
	598
	599	Document d owntime pr ocedures.
	600
	601
	602	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).
	603
	604
	605
	606	Appendix J : Change M anagement Back-Out P lan Templa te
	607	Change Ord er
	608	Affected S ystems
	609
	610
	611	Estimated time-frame s for rest oring serv ice
	612
	613	Any pre-im plementati on work th at will be required
	614
	615	Step-by-st ep guidanc e to resto re service to the pr e-change s tate
	616
	617