1. EPMO Open Source Coordination Office Redaction File Detail Report

Produced by Araxis Merge on 11/16/2018 4:08:11 PM Central 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_101518.zip\BTSSS_CIF_10152018	BTSSS_CMP.doc	Thu Nov 15 16:05:19 2018 UTC
2	BTSSS_CIF_101518.zip\BTSSS_CIF_10152018	BTSSS_CMP.doc	Thu Nov 15 21:18:16 2018 UTC

1.2 Comparison summary

Description	Between Files 1 and 2
Description	Text Blocks	Lines
Unchanged	5	570
Changed	4	11
Inserted	0	0
Removed	2	5

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	April 2018
	5	Version 5. 01
	6	Department of Vetera ns Affairs
	7	Version Hi story
	8	DateVersio nDescripti onAuthor4/ 9/20185.01 Updated fo r AprilJoa nne Wuwer- Saukas12/5 /20174.03D ecember Mo nthly Upda te – Chang ed date on cover pag e and foot ersJoanne Wuwer-Sauk as11/9/201 74.02Novem ber Monthl y Update – changed d ate on cov er page an d footers Christina Silva10/11 /20174.01O ctober Mon thly Updat e – no cha ngesChrist ina Silva9 /18/20173. 04Septembe r Monthly UpdateChri stina Silv a8/31/2017 3.03CRMOL updateChri stina Silv a8/21/2017 3.02August Monthly U pdateChris tina Silva 7/19/20173 .01July Mo nthly Upda teChristin a Silva6/1 6/20172.03 June Month ly UpdateC hristina S ilva5/18/2 0172.02May Monthly U pdateChris tina Silva 4/18/20172 .01April M onthly Upd ateChristi na Silva3/ 15/20171.0 3March Mon thly Updat eChristina Silva 2/2 4/20171.02 February M onthly Upd ateChristi na Silva 1 /26/20161. 01January Monthly Up dateChrist ina Silva1 2/2/20160. 04December Monthly U pdateScott Bartel10/ 31/20160.0 3Initial R eleaseKare n Shepherd 10/28/2016 0.02Edited Document Per Commen tsKaren Sh epherd10/2 6/20160.01 Initial Dr aft Karen ShepherdTa ble of Con tents
	9	11.
	10	Executive Summary
	11
	12
	13	12.
	14	Introducti on
	15
	16
	17	12.1
	18	Purpose of the Confi guration M anagement Plan
	19
	20
	21	22.2
	22	Scope of t he Configu ration Man agement Pl an
	23
	24
	25	22.3
	26	Structure of the Con figuration Managemen t Plan
	27
	28
	29	23
	30	Configurat ion Manage ment Activ ities
	31
	32
	33	23.1
	34	Roles and Responsibi lities
	35
	36
	37	43.2
	38	Communicat ion
	39
	40
	41	43.3
	42	System Con figuration Baseline
	43
	44
	45	53.4
	46	Configurat ion Contro l Process (CCP)
	47
	48
	49	73.5
	50	Configurat ion Manage ment Resou rces
	51
	52
	53	8APPENDIX A: CONFIGU RATION MAN AGEMENT PL AN APPROVA L
	54
	55
	56	9Appendix B: Referen ces
	57
	58
	59	10Appendix C: Key Te rms
	60
	61
	62	11Appendix D: Sugges ted Config uration It ems Data E lements
	63
	64
	65	16Appendix E: [Facil ity] Curre nt Configu ration Bas eline Repo rt
	66
	67
	68	17Appendix F: Config uration It ems (CI) S howing Sys tem Bounda ries
	69
	70
	71	18Appendix G: Change Order App roval Chec klist
	72
	73
	74	19Appendix H: Change Order Imp lementatio n Plan Tem plate
	75
	76
	77	20Appendix I: Busine ss Case Ju stificatio n
	78
	79
	80	21Appendix J: Change Managemen t Back-Out Plan Temp late
	81
	82
	83
	84
	85	Executive Summary
	86	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.
	87	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.
	88	Introducti on
	89	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).
	90	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.
	91	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).
	92	Purpose of the Confi guration M anagement Plan
	93	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.
	94	Scope of t he Configu ration Man agement Pl an
	95	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:
	96	Identifyin g, definin g, and bas e-lining C Is
	97	Creating C I Records
	98	Identifyin g relation ships
	99	Controllin g modifica tions and releases o f CIs
	100	Reporting and record ing status of CIs an d any requ ired modif ications
	101	Ensuring c ompletenes s, consist ency, and correctnes s of CIs
	102	Controllin g storage, handling, and deliv ery of the CIs
	103	Structure of the Con figuration Managemen t Plan
	104	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.
	105	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.
	106	Configurat ion Manage ment Activ ities
	107	Roles and Responsibi lities
	108	Table 1: R oles and R esponsibil ities
	109	RoleRespon sibilityPr ogram Mana ger• Overs ees the so ftware con figuration managemen t process.
	110	• Ensures proper exe cution of the BTSSS Plan.
	111	• Identify dependent projects. Configurat ion Manage r
	112	• 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 .
	113	• Educates project t eam member s in SCM “ best pract ices.”
	114	• Accounta ble for in stituting the establ ished proc esses and reporting progress s tatistics based on c hange requ ests.
	115	• Identifi es product baselines as necess ary of all products within the ir assigne d projects .
	116	• Responsi ble for SC M audits a nd necessa ry status accounting related t o the prod uct.
	117	• Maintain s artifact s followin g proper v ersion con trol proce dures.Soft ware Chang e/Build Ad ministrato r • Devel ops and ma intains ar tifacts fo llowing pr oper versi on control procedure s.
	118	• Establis hes, promo tes, and r eleases ba selines.
	119	• Performs or valida tes interi m and fina l builds.
	120	• Identifi es product baselines as necess ary of all products within the ir assigne d projects .Developme nt Manager /Technical Lead• Pre pares rele ase packag e, release archives and Versio n Descript ion Docume nts (VDD).
	121	• 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.
	122	• 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 .Developer s/System A dministrat ion• Devel ops and ma intains ar tifacts fo llowing pr oper versi on control procedure s using th e SCM Proc edures Man ual and wo rk instruc tions.
	123	• 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.
	124	• Provide impact ana lysis repo rting prob lems or ch anges, inc luding doc umentation of sugges ted soluti ons.
	125	• Document ation of b uild, rele ase, and i nstallatio n instruct ions.Softw are Qualit y Assuranc e Analyst/ Testing An alyst• Upd ate storie s assigned to them a ccording t o test act ivity resu lts.
	126	• Determin es Pass/Fa il for eac h story sc heduled fo r a sprint release.
	127	• 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.Tec hnical Wri ter• Devel ops techni cal delive rable docu mentation to support the softw are delive rables.
	128	• Provides editing, formatting , and grap hics suppo rt for doc umentation .Implement ation Team /Operation s Team• Co ordinates the releas e and depl oyment of software u pdates to the existi ng BTSSS C ustomer Re lationship Managemen t (CRMOL) system.
	129	• 365 Clou dCommunica tion
	130	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.
	131	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.
	132	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.
	133	System Con figuration Baseline
	134	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.
	135	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:
	136	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.
	137	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.
	138	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.
	139	Build – Id entifies a set of so lution fil e versions used to b uild and a ssemble de ployable p ackages.
	140	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.
	141	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 .
	142	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 .
	143	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.
	144	Configurat ion Contro l Process (CCP)
	145	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.
	146	Step 1: Es tablish Sy stem Confi guration B aseline
	147	Step 2: Re view backl og, identi fy changes , and crea te change story
	148	Step 3: Id entify cha nge storie s and plan Sprint
	149	Step 4: Pe rform conf iguration changes
	150	Step 5: Pe rform Secu rity and O perational Impact An alysis
	151	Step 6: Im plement co nfiguratio n changes
	152	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 .
	153	Step 8: Pe rform Conf iguration Status Acc ounting
	154	Step 9: Co nduct Retr ospective which incl udes Confi guration V erificatio n and Audi t.
	155	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.
	156	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.
	157	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.
	158	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.
	159	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:
	160	The organi zation of personnel and the di vision of tasks for the VA tea m members.
	161	Decision c riteria an d escalati on require ments spec ific to ea ch level o f change r equest rev iew.
	162	The overal l Change M anagement Process de scription and flow.
	163	The descri ption of t he change control to ols and ho w the team will use them
	164	Configurat ion Manage ment Resou rces
	165	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.
	166	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.
	167	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.
	168	APPENDIX A : CONFIGUR ATION MANA GEMENT PLA N APPROVAL
	169	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.
	170	__________ __________ __________ __________ __________ __________ __________ ________
	171	Signature:
	172	Date:
	173
	174	Print Name :
	175	Title:
	176	Role:
	177	__________ __________ __________ __________ __________ __________ __________ ________
	178	Signature:
	179	Date:
	180
	181	Title:
	182	Role:
	183	__________ __________ __________ __________ __________ __________ __________ ________
	184	Signature:
	185	Date:
	186
	187	Print Name :
	188	Title:
	189	Role:
	190	Appendix B : Referenc es
	191	The follow ing table summarizes the docum ents refer enced in t his docume nt.
	192	Document N ameDescrip tionLocati onVA Direc tive 6500M anaging In formation Security R isk: VA In formation Security P rogramhttp s://www. URL /vapubs/se arch_actio n.cfm?dTyp e=2
	193	VA Handboo k 6500Risk Managemen t Framewor k for VA I nformation Systems – Tier 3: V A Informat ion Securi ty Program https://ww w. DNS /vapubs/se arch_actio n.cfm?dTyp e=2OIT Con figuration Managemen t ProcessO IT Configu ration Man agement Pr oPath defi ned proces s and supp orting doc umenthttps :// URL/ s it e s/f o /c o mmittees/c cb/CMDB /

	194	Definitive %20Documen t%20Storag e/
	195	oit_config uration_ma nagement_p rocess_doc ument.pdfO IT Change Management Process D ocumentOIT Change Ma nagement P roPath def ined proce ss and sup porting do cumenthttp s:// DNS .sde.porta l. DNS /
	196	sites/fo/c ommittees/ ccb/CMDB/
	197	Definitive %20Documen t%20Storag e/
	198	oit_change _managemen t_process_ document.p dfSDE Chan ge Managem ent SOPSDE Change Ma nagement S tandard Op eration Pr ocedurehtt ps:// DNS .sde.porta l. DNS /
	199	sites/fo/c ommittees/ ccb/CMDB/
	200	Definitive %20Documen t%20Storag e/
	201	National%2 0ChM%20Pro cess%20SOP .pdfMaster Test Plan Master Tes t Plan Tem platehttps ://warrior technology .sharepoin t.com/site s/btsss/Sh ared%20Doc uments/For ms/AllItem s.aspx?id= %2Fsites%2 Fbtsss%2FS hared%20Do cuments%2F Data%20Lib rary%2FPro ject%20Doc s%2FMTPApp endix C: K ey Terms
	202	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.
	203	TermDefini tionALMAgi le Lifecyc le Managem entBTSSSBe neficiary Travel Sel f-Service SystemCABC hange Advi sory Board CCBChange Control Bo ardCCPConf iguration Control Pr ocessCICon figuration ItemCMCon figuration Managemen tCMSChange Managemen t SystemsC MDBConfigu ration Man agement Da tabaseCMPC onfigurati on Managem ent PlanCO RContracti ng Officer Represent ativeCRMOL Customer R elationshi p Manageme nt OnlineD NSDomain N ame Servic eFCIOFacil ity Chief Informatio n OfficerF OIAFreedom of Inform ation ActI TInformati on Technol ogyOITOffi ce of Info rmation & Technology OSOperatin g SystemPO CPoint of Contact RA CIResponsi ble, Accou ntable, Co nsulted, a nd Informe dRFCReques t for Chan geSCMSoftw are Config uration Ma nagementSD EService D elivery an d Engineer ingSOPStan dard Opera ting Proce dureVAVete rans Affai rsVDDVersi on Descrip tion Docum entsVIPVet eran Infor mation Por talVISNVet erans Inte grated Ser vice Netwo rkAppendix D: Sugges ted Config uration It ems Data E lements
	204	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.
	205	Field Name Data TypeC I TypeDesc riptionRes ource Name Indexed Te xtHardware / Softwar e / Servic e / Docume ntA unique name of t he Configu ration Ite m (CI). A name that represent s the Reso urce and i s easy to identify w hat it is; a key sea rch field within the Configura tion Manag ement Data base (CMDB ).DNS Name Indexed Te xtHardware 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 .StatusLoo kup TableH ardware / Software / Service / DocumentT he current status of the CI. F or example : when fir st added t o the CMDB , the CI m ay be in a status of Registere d, then la ter it may be Accept ed. This i dentifies how the re cord moves through t he status/ lifecycle; if a chan ge is bein g performe d on the C I the stat us would b e changed to Change in Progres s, thus id entifying CI’s that are curren tly underg oing some form of a change.Des criptionFr ee Text Mu ltiple Lin esHardware / Softwar e / Servic e / Docume ntA short descriptio n that wil l provide additional feedback to the end user when looking u p the CI.C I TypeLook up TableHa rdware / S oftware / Service / DocumentTh is is the type that the CI bel ongs to. S ee list of suggested family ty pes.Asset ClassLooku p TableHar dware / So ftware / S ervice / D ocumentThi s is the c lassificat ion of the configura tion item; it is rel ated to th e family, but is a m ore specif ic classif ication of an asset. This is t he sub-typ e that the CI belong s to; it i s used to group comm on types o n configur ation item s. An exam ple would be “Laptop ”; the “La ptop” Clas s is withi n the hard ware Type. CommentsFr ee Text Mu ltiple Lin esHardware / Softwar e / Servic e / Docume ntComments regarding the speci fic CI; no tes that n eed to be part of th e record h istory but are not w ithin the Descriptio n of the C I.CORConta ct Table L ookupHardw are / Soft ware / Ser viceContra cting Offi cer Repres entative ( COR) assoc iated with this part icular pur chase or C I.Customer NameConta ct Table L ookupHardw are / Soft ware / Ser vice / Doc umentName of the Cus tomer poin t of conta ct for iss ues with t he CI. Thi s person o r group is the prima ry focus p oint when issues or changes ar e related to the CI. Customer O rganizatio nLookup Ta bleHardwar e / Softwa re / Servi ce / Docum entName of the Organ ization th at the cus tomer belo ngs to. Pr ovides rep orting inf ormation a bout what CI’s are a ssociated to a speci fic organi zation.Dep loyed Date DateHardwa re / Softw are / Serv ice / Docu mentThe da te that a service, s ystem, etc . was depl oyed to th e producti on environ ment.Finan cial Refer enceFree T extHardwar e / Softwa reA Purcha se Order t hat was us ed to obta in the har dware or s oftware. I t is usefu l when loo king up ot her inform ation that may be fo und in rel ated datab ases like the Asset Management system.Fu nctionLook up TableHa rdwareThe function o r purpose that the h ardware Co nfiguratio n Item ser ves.Host N ameFree Te xtHardware 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.Licens e CountNum ericSoftwa reA number of copies that a pa rticular l icense all ows the ow ner to dis tribute. I t can be u sed to det ermine if additional software licenses a re needed or if ther e are too many licen ses unused .Type of L icensesLoo kup TableS oftwareThe type of l icense tha t has been procured, perpetual or recurr ing.Licens e Key Main tained ByC ontact tab le LookupS oftwareWho maintains the Softw are Licens e Key that is used t o install the softwa re?Lifecyc le DateDat eHardware / Software / Service This is a date in t he future derived fr om the ins tall date and Inform ation Tech nology (IT ) equipmen t life exp ectancy.Lo cationLook up TableHa rdware / S oftware / Service / DocumentTh e location where thi s particul ar CI is h osted or i nstalled. More speci fic locati on fields may be nee ded, such as room, f loor, and rack as pa rt of the physical l ocation.Ma intenance Organizati onLookup T ableHardwa re / Softw are / Serv ice Name o f the Orga nization t hat has Ma intenance responsibi lity over the CI; no rmally fou nd within the Operat ions and M aintenance (O&M) Pla n.Maintena nce Vendor Lookup Tab leHardware / Softwar e / Servic e The vend or that wo uld suppor t the Main tenance Or ganization with a Wa rranty or other type of mainte nance agre ement.Manu facturerLo okup Table Hardware / SoftwareM anufacture r of the C I being en tered into the CMDB. Name used for repor ting maint enance con tracts or other data related t o a specif ic manufac turer.Mode lLookup Ta bleHardwar e / Softwa reThe manu facturer’s model nam e for the device. R elates to the manufa cturer; us ed for rep orting and for maint enance con tracts.Ver sion Numbe rFree Text Software / DocumentV ersion Num ber of sof tware or d ocuments. This prov ides a bas eline as t o what ver sion of so ftware is installed/ authorized in produc tion or th e version of a docum ent that w as approve d and publ ished. No version ch anges unle ss there i s a change process f or it.Main tenance Wi ndowFree T extHardwar e / Softwa re / Servi ceMaintena nce window s are esta blished ba sed on Ser vice Level Agreement s (SLA’s) or other a greements for specif ic service s that are available to the en d user. Th e Maintena nce window s that are associate d with the CI’s shou ld clearly state if
	206	they are r ecurring m aintenance windows, the days o f the week that they are avail able, and the hours of the day that they can be us ed. Exampl e: Recurri ng - Monda y – Friday 7 to 11 P M Contact (name or r ole of the person th at should be contact ed to vali date/verif y the main tenance wi ndow).Oper ating Syst emLook Up TableHardw are / Soft ware Ident ifies the Operating System (OS ) running on the ser ver, virtu al machine , laptops or worksta tions. It is used fo r patching , SA assig nment, rep orting pur poses, lic ensing, et c. NOTE: If this in formation is availab le from ot her tools that can r eport this informati on and is not needed as part o f internal reporting or linked to other fields tha t are not part of th e external data sour ce, then t his field could be l eft out.Pu blished Da teDateDocu mentThe da te that a document w as publish ed for gen eral consu mption.Reg ionLookup TableHardw are / Soft ware / Ser vice / Doc umentOIT i s broken o ut into di fferent re gional are as. Most h ave their own proces ses and pr ocedures o r have equ ipment and software that is re gionalized . If the C MDB holds cross-regi onal CI’s these shou ld be iden tified for reporting purposes; otherwise , the Orga nizational field sho uld provid e the need ed feedbac k.Relation shipsLooku p TableHar dware / So ftware / S ervice / D ocumentFie ld is a on e-to-many relationsh ip used to identify a relation ship betwe en 2 or mo re CI’s an d the type of relati onship tha t the CI h as. This r elationshi p could be with cont acts, othe r hardware , software , services or docume nt CI’s. A n example of types o f relation ships are listed bel ow:
	207	Changes Ap proved By
	208	Connects T o
	209	Is Documen ted By
	210	Runs/Runs OnRenewal DateDateHa rdware / S oftwareA r enewal dat e is used to establi sh when a particular CI’s main tenance ag reement wi ll expire and would require re newal to c ontinue wi th the ser vice.Cost of Mainten ance Agree mentNumber sHardware / Software Recurring cost of ma intenance agreements purchased under the contract. Responsibl e Organiza tionLookup TableHard ware / Sof tware / Se rvice / Do cumentThe Organizati on that ha s responsi bility ove r the CI. It may be the same a s maintena nce or cus tomer orga nization o r a differ ent one.Re sponsible OwnerConta ct Lookup TableHardw are / Soft ware / Ser vice / Doc umentA pri mary point of contac t who has been ident ified as t he Point o f Contact (POC) for the Respon sible Orga nization.R esponsible VendorLoo kup TableH ardware / SoftwareTh e Responsi ble Vendor for a par ticular CI may be th e same as Maintenanc e Vendor o r may be a different vendor if maintenan ce is sub- contracted out by th e Primary Responsibl e Vendor.S econdary C ontactCont act Lookup TableHard ware / Sof tware / Se rvice / Do cumentThis would be an alterna te Point o f Contact that could be contac ted in the absence o f the Prim ary POC,Se rial Numbe rAlpha-Num eric Free TextHardwa reSerial N umbers are unique id entificati on element s that are directly related to asset man agement; b ut by incl uding it w ithin your CMDB you could link to other databases that track their CI’ s by Seria l Number.S ervice Lin eLookup Ta bleHardwar e / Softwa re / Servi ce / Docum entSupport is broken down by S ervice Lin es within OIT Field Operations , providin g a Servic e Line ass ociated to the CI wo uld expedi te mainten ance issue s and prov ide report ing capabi lities on the type a nd number of CI’s be ing mainta ined by a particular service l ine.Servic e Line Tea m/Division Lookup Tab leHardware / Softwar e / Servic e / Docume ntAs Servi ce Lines a re stood u p, so are the Servic e Line Tea ms/Divisio ns that su pport the service li ne and hav e a more d efined sco pe of thei r responsi bilities. Capturing this type of informa tion would provide y ou with th e same inf ormation a s Service Line would but allow you to br eak it dow n by the S ervice Lin e Team Div ision.Sour ce Supplie rLookup Ta bleHardwar eUsed for hardware s upport, th is is the vendor tha t purchase d the equi pment from the manuf acturer. I t is recei ved obtain ed from th e Purchase Order Con tract.Crea ted BySyst em Contact FieldHard ware / Sof tware / Se rvice / Do cumentThis is an aud it field; it capture s the name of the pe rson that created th e record. This shoul d be a sys tem field and captur ed based o n who was logged in during the creation of the rec ord.Create d DateSyst em Date Fi eldHardwar e / Softwa re / Servi ce / Docum entInitial date of c reation of the Confi guration I tem Record .Modified BySystem C ontact Fie ldHardware / Softwar e / Servic e / Docume ntThis is an audit f ield; the person who last edit ed the rec ord would be listed. This shou ld be a sy stem field and captu red based on who was logged in during th e modifica tion.Modif ied DateSy stem Date FieldHardw are / Soft ware / Ser vice / Doc umentDate the Config uration It em Record was last m odified.Ap pendix E: [Facility] Current C onfigurati on Baselin e Report
	211	The follow ing table details th e Hardware /Software and Servic es associa ted with t he system under this CMP.
	212
	213	Appendix F : Configur ation Item s (CI) Sho wing Syste m Boundari es
	214

	215	Appendix G : Change O rder Appro val Checkl ist
	216
	217	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)
	218
	219	Correct lo cation ent ered?
	220
	221	Change Ord er descrip tion conta ins requir ed informa tion
	222
	223	What is be ing done?
	224
	225	The busine ss case fo r doing it .
	226
	227	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)?
	228
	229	What else may be imp acted?
	230
	231	What will occur if w e don’t do the chang e?
	232
	233	The implem entation p lan should be attach ed, never be pasted, into the descriptio n.
	234
	235	Were the c ustomers/s takeholder s notified as per th e Change A dvisory Bo ard (CAB) process?
	236
	237	CAB notifi cation in the ticket .
	238
	239	Facility O IT respons e or ignor e entered as a log c omment.
	240
	241	Is the imp lementatio n plan att ached?
	242
	243	Is the Not ification and Escala tion secti on complet e?
	244
	245	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 ?
	246
	247	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?
	248
	249	Are verifi cation ste ps (Test P lan) inclu ded?
	250
	251	Do the ver ification steps ensu re the cus tomers are functioni ng and not just the item modif ied is wor king?
	252
	253	Is the bac k-out plan attached?
	254
	255	Is the not ification plan inclu ded?
	256
	257	Are verifi cation ste ps include d?
	258
	259	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?
	260
	261	Is the nee d by date realistic?
	262
	263	Is there a n implemen tation dat e/time pri or to the need by da te?
	264	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 .
	265
	266	Appendix H : Change O rder Imple mentation Plan Templ ate
	267	Local faci lity Notif ication an d Escalati on Contact s
	268	Name/RoleB usinessAft er-hoursJo hn Doe, FC IO333-345- 6789333-98 7-6543VISN /Service L ine Notifi cation and Escalatio n Contacts
	269	Name/RoleB usinessAft er-hoursAn y pre-impl ementation work that will be r equired
	270	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
	271	Identifica tion of ar eas that m ight cause problems
	272	Identifica tion of ro ll-back po ints and/o r criteria for initi ating the Back-out p lan
	273	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)
	274
	275	Appendix I : Business Case Just ification
	276	Please pro vide a det ailed desc ription of this chan ge.
	277	List the r equirement s needed f or the cha nge (i.e., servers, switches, software, etc.).
	278	Describe t he effect the change may have upon the e nd user, b usiness op eration, a nd infrast ructure, i f known.
	279	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).
	280	Describe t he effect of not imp lementing the change .
	281	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.
	282	Estimate a ny additio nal ongoin g resource s required if the ch ange is im plemented.
	283	Document d owntime pr ocedures.
	284	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).
	285
	286	Appendix J : Change M anagement Back-Out P lan Templa te
	287	Change Ord erAffected SystemsEs timated ti me-frames for restor ing servic e
	288	Any pre-im plementati on work th at will be required
	289	Step-by-st ep guidanc e to resto re service to the pr e-change s tate
	290