1. EPMO Open Source Coordination Office Redaction File Detail Report

Produced by Araxis Merge on 9/6/2017 3:05:07 PM Eastern 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	MCCF EDI TAS BPS PSO PSX Bundle.zip\MCCF EDI TAS BPS PSO PSX Bundle	BPS_1_22_PSO_PSX_ig.docx	Thu Jul 20 17:53:30 2017 UTC
2	MCCF EDI TAS BPS PSO PSX Bundle.zip\MCCF EDI TAS BPS PSO PSX Bundle	BPS_1_22_PSO_PSX_ig.docx	Wed Aug 30 20:42:32 2017 UTC

1.2 Comparison summary

Description	Between Files 1 and 2
Description	Text Blocks	Lines
Unchanged	1	832
Changed	0	0
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	Medical Ca re Collect ion Fund ( MCCF) Elec tronic Dat a Intercha nge (EDI) Transactio n Applicat ions Suite (TAS) ePh armacy Bui ld 2
	2	E Claims M anagement Engine BPS 1.022Out patient Ph armacy PSO 7.0478Co nsolidated Mail Outp atient Pha rmacy PSX* 2.0*81
	3	Deployment , Installa tion, Back -Out, and Rollback G uide
	4	Version 1. 0
	5
	6
	7	July 2017
	8	Department of Vetera ns Affairs
	9	Office of Informatio n and Tech nology (OI &T)
	10
	11
	12	Revision H istory
	13	Date
	14	Version
	15	Descriptio n
	16	Author
	17	July 2017
	18	1.0
	19	Initial Ve rsion
	20	Christine Bullis, Ma rk Dawson, Paul Devi ne
	21
	22	Artifact R ationale
	23	This docum ent descri bes the De ployment, Installati on, Back-o ut, and Ro llback Pla n for new products g oing into the VA Ent erprise. T he plan in cludes inf ormation a bout syste m support, issue tra cking, esc alation pr ocesses, a nd roles a nd respons ibilities involved i n all thos e activiti es. Its pu rpose is t o provide clients, s takeholder s, and sup port perso nnel with a smooth t ransition to the new product o r software , and shou ld be stru ctured app ropriately , to refle ct particu lars of th ese proced ures at a single or at multipl e location s.
	24	Per the Ve teran-focu sed Integr ated Proce ss (VIP) G uide, the Deployment , Installa tion, Back -out, and Rollback P lan is req uired to b e complete d prior to Critical Decision P oint #2 (C D #2), wit h the expe ctation th at it will be update d througho ut the lif ecycle of the projec t for each build, as needed.
	25
	26
	27
	28
	29	Table of C ontents
	30	1Introduct ion1
	31	1.1Purpose 1
	32	1.2Depende ncies1
	33	1.3Constra ints1
	34	2Roles and Responsib ilities1
	35	3Deploymen t2
	36	3.1Timelin e2
	37	3.2Site Re adiness As sessment2
	38	3.2.1Deplo yment Topo logy (Targ eted Archi tecture)2
	39	3.2.2Site Informatio n (Locatio ns, Deploy ment Recip ients)2
	40	3.2.3Site Preparatio n3
	41	3.3Resourc es3
	42	3.3.1Facil ity Specif ics3
	43	3.3.2Hardw are3
	44	3.3.3Softw are3
	45	3.3.4Commu nications4
	46	3.3.4.1Dep loyment/In stallation /Back-Out Checklist4
	47	4Installat ion4
	48	4.1Pre-ins tallation and System Requireme nts4
	49	4.2Platfor m Installa tion and P reparation 5
	50	4.3Downloa d and Extr act Files5
	51	4.4Databas e Creation 5
	52	4.5Install ation Scri pts5
	53	4.6Cron Sc ripts5
	54	4.7Access Requiremen ts and Ski lls Needed for the I nstallatio n5
	55	4.8Install ation Proc edure5
	56	4.9Install ation Veri fication P rocedure5
	57	4.10System Configura tion5
	58	4.11Databa se Tuning5
	59	5Back-Out Procedure6
	60	5.1Back-Ou t Strategy 6
	61	5.1.1Mirro r Testing or Site Pr oduction T esting6
	62	5.1.2After National Release bu t During t he Designa ted Suppor t Period6
	63	5.1.3After National Release an d Warranty Period6
	64	5.2Back-Ou t Consider ations6
	65	5.2.1Load Testing6
	66	5.2.2User Acceptance Testing6
	67	5.3Back-Ou t Criteria 8
	68	5.4Back-Ou t Risks8
	69	5.5Authori ty for Bac k-Out8
	70	5.6Back-Ou t Procedur e8
	71	5.7Back-ou t Verifica tion Proce dure9
	72	6Rollback Procedure9
	73	6.1Rollbac k Consider ations9
	74	6.2Rollbac k Criteria 9
	75	6.3Rollbac k Risks9
	76	6.4Authori ty for Rol lback9
	77	6.5Rollbac k Procedur e9
	78	6.6Rollbac k Verifica tion Proce dure9
	79
	80	Table of T ables
	81	Table 1: D eployment, Installat ion, Back- out, and R ollback Ro les and Re sponsibili ties1
	82	Table 2: S ite Prepar ation3
	83	Table 3: F acility-Sp ecific Fea tures3
	84	Table 4: H ardware Sp ecificatio ns3
	85	Table 5: S oftware Sp ecificatio ns4
	86	Table 6: D eployment/ Installati on/Back-Ou t Checklis t4
	87
	88
	89
	90	Introducti on
	91	This docum ent descri bes how to deploy an d install the multi- build BPS PSO PSX BU NDLE 10.0 (which inc ludes BPS* 1.022, PS O7.0478, PSX2.0*8 1) and how to back-o ut the pro duct and r ollback to a previou s version or data se t.
	92	Purpose
	93	The purpos e of this plan is to provide a single, c ommon docu ment that describes how, when, where, an d to whom the multi- build BPS PSO PSX BU NDLE 10.0 (which inc ludes BPS* 1.022, PS O7.0478, PSX2.0*8 1) will be deployed and instal led, as we ll as how it is to b e backed o ut and rol led back, if necessa ry. The pl an identif ies resour ces, commu nications plan, and rollout sc hedule. Sp ecific ins tructions for instal lation, ba ck-out, an d rollback are inclu ded in thi s document .
	94	Dependenci es
	95	BPS1.020 must be i nstalled B EFORE BPS* 1*22.
	96	PSO7.036 7 and PSO* 7.0448 mu st be inst alled BEFO RE PSO7*4 78.
	97	PSX2.070 , PSX2.0 77, and PS X2.079 m ust be ins talled BEF ORE PSX2 81.
	98	Constraint s
	99	This patch is intend ed for a f ully patch ed VistA s ystem.
	100	Roles and Responsibi lities
	101	Table 1: D eployment, Installat ion, Back- out, and R ollback Ro les and Re sponsibili ties
	102	ID
	103	Team
	104	Phase / Ro le
	105	Tasks
	106	Project Ph ase (See S chedule)
	107	1
	108	VA OI&T, V A OI&T Hea lth Produc t Support & PMO (Lei dos)
	109	Deployment
	110	Plan and s chedule de ployment ( including orchestrat ion with v endors)
	111	Planning
	112	2
	113	Local VAMC and CPAC processes
	114
	115
	116	Deployment
	117	Determine and docume nt the rol es and res ponsibilit ies of tho se involve d in the d eployment.
	118	Planning
	119	3
	120	Field Test ing (Initi al Operati ng Capabil ity - IOC) , Health P roduct Sup port Testi ng & VIP R elease Age nt Approva l
	121	Deployment
	122	Test for o perational readiness
	123	Testing
	124	4
	125	Health pro duct Suppo rt and Fie ld Operati ons
	126	Deployment
	127	Execute de ployment
	128	Deployment
	129	5
	130	Individual Veterans Administra tion Medic al Centers (VAMCs)
	131	Installati on
	132	Plan and s chedule in stallation
	133	Deployment
	134	6
	135	VIP Relea se Agent
	136	Installati on
	137	Ensure aut hority to operate an d that cer tificate a uthority s ecurity do cumentatio n is in pl ace
	138	Deployment
	139	7
	140	N/A for th is patch a s we are u sing only the existi ng VistA s ystem
	141	Installati on
	142	Validate t hrough fac ility POC to ensure that IT eq uipment ha s been acc epted usin g asset in ventory pr ocesses
	143
	144	8
	145	VA’s eBusi ness team
	146	Installati ons
	147	Coordinate training
	148	Deployment
	149	9
	150	VIP releas e Agent, H ealth Prod uct Suppor t & the de velopment team
	151	Back-out
	152	Confirm av ailability of back-o ut instruc tions and back-out s trategy (w hat are th e criteria that trig ger a back -out)
	153	Deployment
	154	10
	155	No changes to curren t process – we are u sing the e xisting Vi stA system
	156	Post Deplo yment
	157	Hardware, Software a nd System Support
	158	Warranty
	159	Deployment
	160	The deploy ment is pl anned as a national rollout.
	161	This secti on provide s the sche dule and m ilestones for the de ployment.
	162	Timeline
	163	The durati on of depl oyment and installat ion is 30 days, as d epicted in the maste r deployme nt schedul e.
	164	Site Readi ness Asses sment
	165	This secti on discuss es the loc ations tha t will rec eive the d eployment of the mul ti-build B PS PSO PSX BUNDLE 10 .0 (which includes B PS1.022, PSO7.04 78, PSX2. 081).
	166	Deployment Topology (Targeted Architectu re)
	167	This multi -build BPS PSO PSX B UNDLE 10.0 (which in cludes BPS 1.022, P SO7.0478 , PSX2.0 81) is to be nationa lly releas ed to all VAMCs.
	168	Site Infor mation (Lo cations, D eployment Recipients )
	169	The test s ites for I OC testing are:
	170	Birmingham
	171	Eastern Ka nsas
	172	Lexington
	173	Little Roc k
	174	Richmond
	175
	176	Upon natio nal releas e all VAMC s are expe cted to in stall this patch pri or to or o n the comp liance dat e.
	177	Site Prepa ration
	178	The follow ing table describes preparatio n required by the si te prior t o deployme nt.
	179	Table 2: S ite Prepar ation
	180	Site/Other
	181	Problem/Ch ange Neede d
	182	Features t o Adapt/Mo dify to Ne w Product
	183	Actions/St eps
	184	Owner
	185	N/A
	186	N/A
	187	N/A
	188	N/A
	189	N/A
	190	Resources
	191	Facility S pecifics
	192	The follow ing table lists faci lity-speci fic featur es require d for depl oyment.
	193	Table 3: F acility-Sp ecific Fea tures
	194	Site
	195	Space/Room
	196	Features N eeded
	197	Other
	198	N/A
	199	N/A
	200	N/A
	201	N/A
	202	Hardware
	203	The follow ing table describes hardware s pecificati ons requir ed at each site prio r to deplo yment.
	204	Table 4: H ardware Sp ecificatio ns
	205	Required H ardware
	206	Model
	207	Version
	208	Configurat ion
	209	Manufactur er
	210	Other
	211	Existing V istA syste m
	212	N/A
	213	N/A
	214	N/A
	215	N/A
	216	N/A
	217	Please see the Roles and Respo nsibilitie s table in Section 2 for detai ls about w ho is resp onsible fo r preparin g the site to meet t hese hardw are specif ications.
	218	Software
	219	The follow ing table describes software s pecificati ons requir ed at each site prio r to deplo yment.
	220	Table 5: S oftware Sp ecificatio ns
	221	Required S oftware
	222	Make
	223	Version
	224	Configurat ion
	225	Manufactur er
	226	Other
	227	Fully patc hed E Clai ms Managem ent Engine package w ithin Vist A
	228	N/A
	229	1.0
	230	N/A
	231	N/A
	232	N/A
	233	Fully patc hed Outpat ient Pharm acy packag e within V istA
	234	N/A
	235	7.0
	236	N/A
	237	N/A
	238	N/A
	239	Fully patc hed Consol idated Mai l Outpatie nt Pharmac y package within Vis tA
	240	N/A
	241	2.0
	242	N/A
	243	N/A
	244	N/A
	245	Prerequisi te patches in BPS, P SO, PSX ye t to be de termined
	246	N/A
	247	Nationally released version
	248	N/A
	249	N/A
	250	N/A
	251	Please see the Roles and Respo nsibilitie s table in Section 2 above for details a bout who i s responsi ble for pr eparing th e site to meet these software specificat ions.
	252	Communicat ions
	253	The sites that are p articipati ng in fiel d testing (IOC) will use the “ Patch Trac king” mess age in Out look to co mmunicate with the e Pharmacy e Business t eam, the d evelopers, and produ ct support personnel .
	254	Deployment /Installat ion/Back-O ut Checkli st
	255	The Releas e Manageme nt team wi ll deploy the multi- build BPS PSO PSX BU NDLE 10.0, which is tracked na tionally f or all VAM Cs in the National P atch Modul e (NPM) in Forum. Fo rum automa tically tr acks the p atches as they are i nstalled i n the diff erent VAMC productio n systems. One can r un a repor t in Forum to identi fy when an d by whom the patch was instal led into t he VistA p roduction at each si te. A repo rt can als o be run t o identify which sit es have no t currentl y installe d the patc h into the ir VistA p roduction system. Th erefore, t his inform ation does not need to be manu ally track ed in the chart belo w.
	256
	257	Table 6: D eployment/ Installati on/Back-Ou t Checklis t
	258	Activity
	259	Day
	260	Time
	261	Individual who compl eted task
	262	Deploy
	263	N/A
	264	N/A
	265	N/A
	266	Install
	267	N/A
	268	N/A
	269	N/A
	270
	271	Installati on
	272	Pre-instal lation and System Re quirements
	273	Multi-buil d BPS PSO PSX BUNDLE 10.0 is i nstallable on a full y patched M(UMPS) Vi stA system and opera tes on the top of th e VistA en vironment provided b y the Vist A infrastr ucture pac kages. The latter pr ovides uti lities whi ch communi cate with the underl ying opera ting syste m and hard ware, ther eby provid ing each V istA packa ge indepen dence from variation s in hardw are and op erating sy stem.
	274	Platform I nstallatio n and Prep aration
	275	Refer to t he BPS1.0 22 docume ntation on the NPM i n Forum fo r the deta iled insta llation in structions . These in structions include a ny pre-ins tallation steps if a pplicable.
	276	Download a nd Extract Files
	277	Refer to t he BPS1.0 22, PSO7 .0478, PS X2.081 d ocumentati on on the NPM to fin d related documentat ion that c an be down loaded. Th e patch de scription of each pa tch will b e transmit ted as a M ailMan mes sage from the NPM an d this mes sage can b e pulled f rom the NP M. The pat ches thems elves are bundled to gether int o the mult i-build BP S PSO PSX BUNDLE 10. 0. The hos t file con taining th ese patche s must be downloaded separatel y. The fil e name is BPS_1_22_P SO_PSX.KID and it ca n be found on the AN ONYMOUS.SO FTWARE dir ectory on any of the VistA FTP servers ( Albany, Hi nes, Salt Lake City) .
	278	Database C reation
	279	Multi-buil d BPS PSO PSX BUNDLE 10.0 modi fies the V istA datab ase. All c hanges can be found on the NPM documenta tion for t his patch.
	280	Installati on Scripts
	281	No install ation scri pts are ne eded for m ulti-build BPS PSO P SX BUNDLE 10.0 insta llation.
	282	Cron Scrip ts
	283	No Cron sc ripts are needed for multi-bui ld BPS PSO PSX BUNDL E 10.0 ins tallation.
	284	Access Req uirements and Skills Needed fo r the Inst allation
	285	Staff perf orming the installat ion of thi s multi-bu ild will n eed access to FORUM’ s NPM to v iew all pa tch descri ptions. St aff will a lso need a ccess and ability to download the host f ile from o ne of the VA’s FTP s ervers. Th e software is to be installed by each si te’s or re gion’s des ignated VA OI&T IT O PERATIONS SERVICE, E nterprise Service Li nes, Vista Applicati ons Divisi on.
	286	Installati on Procedu re
	287	Refer to t he BPS1.0 22 docume ntation on the NPM f or detaile d installa tion instr uctions.
	288	Installati on Verific ation Proc edure
	289	Refer to t he BPS1.0 22 docume ntation on the NPM f or detaile d installa tion instr uctions. T hese instr uctions in clude any post insta llation st eps if app licable.
	290	System Con figuration
	291	No system configurat ion change s are requ ired for t his patch.
	292	Database T uning
	293	No reconfi guration o f the Vist A database , memory a llocations or other resources is necessa ry.
	294	Back-Out P rocedure
	295	Back-Out p ertains to a return to the las t known go od operati onal state of the so ftware and appropria te platfor m settings .
	296	Back-Out S trategy
	297	A decision to back o ut could b e made dur ing Site M irror Test ing, durin g Site Pro duction Te sting, or after Nati onal Relea se to the field (VAM Cs). The b est strate gy decisio n is depen dent on th e stage of testing d uring whic h the deci sion is ma de.
	298	Mirror Tes ting or Si te Product ion Testin g
	299	If a decis ion to bac k out is m ade during Mirror Te sting or S ite Produc tion Testi ng, a new version of the patch can be us ed to rest ore the bu ild compon ents to th eir pre-pa tch condit ion.
	300	After Nati onal Relea se but Dur ing the De signated S upport Per iod
	301	If a decis ion to bac k out is m ade after national r elease and within th e designat ed support period, a new patch will be e ntered int o the NPM in Forum a nd will go through a ll the nec essary mil estone rev iews, etc. as a patc h for a pa tch. This patch coul d be defin ed as an e mergency p atch, and it could b e used to address sp ecific iss ues pertai ning to th e original patch or it could b e used to restore th e build co mponents t o their or iginal pre -patch con dition.
	302	After Nati onal Relea se and War ranty Peri od
	303	After the support pe riod, the VistA Main tenance Pr ogram will produce t he new pat ch, either to correc t the defe ctive comp onents or restore th e build co mponents t o their or iginal pre -patch con dition.
	304	Back-Out C onsiderati ons
	305	Changes im plemented with multi -build BPS PSO PSX B UNDLE 10.0 can be ba cked out i n their en tirety or on an enha ncement-by -enhanceme nt basis. Either cou ld be acco mplished v ia a new v ersion of multi-buil d BPS PSO PSX BUNDLE 10.0 if b efore nati onal relea se or a ne w multi-bu ild if aft er nationa l release.
	306	Load Testi ng
	307	N/A. The b ack-out pr ocess will be execut ed at norm al rather than raise d job prio rity and i s expected to have n o signific ant effect on total system per formance. Subsequent to the re version, t he perform ance deman ds on the system wil l be uncha nged.
	308	User Accep tance Test ing
	309	Below are the accept ance crite ria for ea ch story i ncluded in BPS PSO P SX BUNDLE 10.0.
	310
	311	US22
	312	Confirm th at TRICARE /CHAMPVA p rescriptio ns are not delayed i n being tr ansmitted to CMOP if the claim response is receive d within 2 hours of the claim submission .
	313
	314
	315	US115
	316	Verify tha t a label may not be printed o r reprinte d for a pr escription if there is an unre solved 79, 88, or RR R reject.
	317	Verify tha t the user may not p rocess/fil l a prescr iption if there is a n unresolv ed 79, 88, or RRR re ject.
	318
	319	US174
	320	Confirm th at the fil e BPS NCPD P FIELD DE FS include s the entr ies:
	321	B95-3Z Fac ility ID Q ualifier
	322	B98-34 Rec onciliatio n ID
	323
	324	US178
	325	Confirm th at the fol lowing fie lds are av ailable in the Claim Log and t he Claim R esponse In quiry:
	326	B95-3Z Fac ility ID Q ualifier
	327	B98-34 Rec onciliatio n ID
	328	C01-4N Ori ginal Manu facturer P roduct ID
	329	C02-4P Ori ginal Manu facturer P roduct ID Qualifier
	330	Confirm th e Claim Re sponse Inq uiry conta ins the co rrect valu es for the above fie lds.
	331	Confirm th e Claim Lo g contains the corre ct values for the ab ove fields .
	332	Confirm th e above fi elds only display in the Claim Log when a value is transmitt ed in the field.
	333	Confirm th e above fi elds only display in the Claim Response Inquiry wh en a value is transm itted in t he field.
	334
	335	US209
	336	Verify the new PR Pr int Report (s) action is availa ble under VER View e Pharmacy R x.
	337	When a use r selects the new ac tion PR Pr int Report (s) within the VER V iew ePharm acy Rx, a list of re ports avai lable for printing i s displaye d and the user enter s the name of the re port(s) to print.
	338	Help text is availab le and dis plays when the user enters “?” or “??” a t the sele ct prompt.
	339	The user m ay select one report .
	340	Multiple r eports can be select ed, separa ted by com mas.
	341	The Select Report to Print pro mpt repeat s until th e user hit s enter wi thout maki ng a selec tion.
	342	If a user selects a report mor e than onc e, the rep ort will o nly print once.
	343	Only selec ted report s are prin ted.
	344	The system does not display a default va lue when p rompting t he user fo r the name s of repor ts to prin t.
	345	If the use r enters a n invalid selection, an error message wi ll be disp layed. If the invali d entry wa s one of m any, accep t the vali d entries.
	346	An entry o f “^” esca pes back t o the VER screen.
	347
	348	US576
	349	Confirm th at the use r can reve rt to thei r default view
	350
	351	US579
	352	Confirm th at the Aut o-Reverse parameter will accep t only val ue from 3 to 10.
	353
	354	US583
	355	Confirm th at the Rej ect Inform ation Scre en display s the Tax ID and PCN
	356
	357	US589
	358	Verify tha t the ECME Auto-Reve rsal Proce ss email b ulletin di splays the patients’ eligibili ty and the name of t he drug
	359	Back-Out C riteria
	360	It may be decided to back out this patch if the pr oject is c anceled, t he request ed changes implement ed by mult i-build BP S PSO PSX BUNDLE 10. 0 are no l onger desi red by VA OI&T and t he ePharma cy eBusine ss team, o r the patc h produces catastrop hic proble ms.
	361	Back-Out R isks
	362	Since the ePharmacy software i s tightly integrated with exte rnal syste ms, any at tempt at a back-out should inc lude close consultat ion with t he externa l trading partners s uch as the Financial Services Center (FS C) and the Health Ca re Clearin g House (H CCH) to de termine ri sk.
	363	Authority for Back-O ut
	364	The order would come from: rel ease coord inator (pr oduct supp ort), port folio dire ctor, and health pro duct suppo rt. The or der should be done i n consulta tion with the develo pment team and exter nal tradin g partners such as F SC and the HCCH to d etermine t he appropr iate cours e of actio n. ePharma cy is tigh tly integr ated with these exte rnal partn ers and a decision t o back-out should no t be made without th eir consul tation.
	365	Back-Out P rocedure
	366	Backing ou t enhancem ents to a VistA appl ication is often com plex. Norm ally, defe cts are re paired via a follow- up patch. The develo pment team recommend s that sit es log a t icket if t here is a nationally released patch to b e implemen ted. If no t, the sit e should c ontact the Enterpris e Program Management Office (E PMO) team directly f or specifi c solution s to their unique pr oblems.
	367
	368	Multi-buil d BPS PSO PSX BUNDLE 10.0 cont ains the f ollowing b uild compo nents:
	369	Routines
	370	File entri es in the file BPS N CPDP FIELD DEFS (#90 02313.91)
	371	Data Dicti onary Chan ges
	372	Protocols
	373	List Templ ates
	374
	375	While the VistA KIDS installat ion proced ure allows the insta ller to ba ck up the modified r outines us ing the ‘B ackup a Tr ansport Gl obal’ acti on, the ba ck-out pro cedure for global, d ata dictio nary and o ther VistA component s is more complex an d requires issuance of a follo w-up patch to ensure all compo nents are properly r emoved and /or restor ed. All so ftware com ponents (r outines an d other it ems) must be restore d to their previous state at t he same ti me and in conjunctio n with the restorati on of the data.
	376
	377	Please con tact the E PMO team f or assista nce since this insta lled patch contains components in additi on to rout ines.
	378	Back-out V erificatio n Procedur e
	379	Successful back-out is confirm ed by veri fication t hat the ba ck-out pat ch was suc cessfully installed.
	380	Rollback P rocedure
	381	Rollback p ertains to data. The data chan ges in thi s patch ar e specific to the op erational software a nd platfor m settings . These da ta changes are cover ed in the Back-out p rocedures detailed e lsewhere i n this doc ument.
	382	Rollback C onsiderati ons
	383	Not applic able.
	384	Rollback C riteria
	385	Not applic able.
	386	Rollback R isks
	387	Not applic able.
	388	Authority for Rollba ck
	389	Not applic able.
	390	Rollback P rocedure
	391	Not applic able.
	392	Rollback V erificatio n Procedur e
	393	Not applic able.
	394
	395	Template R evision Hi story
	396	Date
	397	Version
	398	Descriptio n
	399	Author
	400	March 2016
	401	2.2
	402	Changed th e title fr om Install ation, Bac k-Out, and Rollback Guide to D eployment and Instal lation Gui de, with t he underst anding tha t Back-Out and Rollb ack belong with Inst allation.
	403	VIP Team
	404	February 2 016
	405	2.1
	406	Changed ti tle from I nstallatio n, Back-Ou t, and Rol lback Plan to Instal lation, Ba ck-Out, an d Rollback Guide as recommende d by OI&T Documentat ion Standa rds Commit tee
	407	OI&T Docum entation S tandards C ommittee
	408	December 2 015
	409	2.0
	410	The OI&T D ocumentati on Standar ds Committ ee merged the existi ng “Instal lation, Ba ck-Out, Ro llback Pla n” templat e with the content r equirement s in the O I&T End-us er Documen tation Sta ndards for a more co mprehensiv e Installa tion Plan.
	411	OI&T Docum entation S tandards C ommittee
	412	February 2 015
	413	1.0
	414	Initial Dr aft
	415	Lifecycle and Releas e Manageme nt
	416