36C10B20Q0218-006.xlsx

XLSX spreadsheet Posted

Attached to
D306--VBA Performance Testing Services Federal contract opportunity
Solicitation number
36C10B20Q0218
Issued by
Department of Veterans Affairs Technology Acquisition Center Austin

About this file

36C10B20Q0218 SIO Fiscal Release Schedule 2021.xlsx

View the file

Other files for this federal contract opportunity

Other files attached to D306--VBA Performance Testing Services, newest first.
File Type Posted
36C10B20Q0218-004.pdf PDF
36C10B20Q0218-002.xls XLS spreadsheet
36C10B20Q0218-008.pdf PDF
36C10B20Q0218-005.pdf PDF
36C10B20Q0218-001.docx DOCX document
36C10B20Q0218-009.pdf PDF
36C10B20Q0218-000.docx DOCX document
36C10B20Q0218-007.docx DOCX document
36C10B20Q0218-003.pdf PDF

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

2021 Implementation Schedule

ABCDEFGHIJKLM
Week 1Week 2Week 3Week 3Week 4Week 5Week 5Week 4
Coordinated

Implementation Number PIAs due to

SIOSIO Accepts
ApplicationsITOPS InstallsITOPS Installs to VBAPERF and SIO Preprod Lab

Hines Installs in VBAPERF SIO sends 2 Week Notice for Required Implementations Regression & Performance Test Week Implement Web & Non-Web Memos PRR Cab Review Weekend for Coordinated Install

(Sat & Sunday)Deploy Client
Only AppsLevel of InstallsField OT

(Overtime) Availability

Refresh and Restage
VBAPERF, VBAPPRDVBAPPRD
(VBAPPRD Outage)Austin Installs to VBAPERF(Go/No Go Call)Coord Install

Compl Date

FINAL ATT
Receive Dateand Preprod for Solaris PatchingSolaris Patching (Sun)
09/12/1909/19/1909/23/1909/25/1909/27/1909/30/1910/07/1910/12/1910/14/19O
UNIX Maintenenance Only08/28/1610/08/2016*4Sat & Sun
19.10.CI.109/12/1909/19/1909/23/1909/25/1909/27/1909/30/1910/07/1910/09/1910/12-13/201910/15/193Sat, No Sun
CCA10/19/1710/26/1710/30/1711/01/1711/03/1711/06/1711/13/1711/18/1711/20/173N
20.10.CI.109/10/2009/17/2009/22/2009/23/2009/25/2009/28/2010/05/2010/07/2010/10-11//202010/13/203Sat, No Sun
Database Maintenenance Only10/22/2016*4Sat & Sun
09/10/2009/17/2009/21/2009/23/2009/25/2009/28/2010/05/2010/10/2010/12/20Sat, No Sun
Corp Comp ADJ10/22/2010/29/2011/02/2011/04/2011/06/2011/09/2011/16/2011/21/2011/23/203No Sat or Sun

Corp Comp ADJ 20.11.CI.1 N/A N/A N/A N/A N/A N/A N/A 11/14-15/2020 N/A 3 No Sat or Sun

20.12.CI.111/12/2011/19/2011/24/2011/25/2011/27/2011/30/2012/07/2012/09/2012/12-13/202012/14/203Sat, No Sun
11/12/2011/19/2011/24/2011/25/2011/27/2011/30/2012/07/2012/12/2012/14/20O
19.10.IN.1Solaris Monthly Patching10/01/1910/26/194Sat & Sun
19.11.IN.1Solaris Monthly Patching11/17/1911/30/194Sat & Sun
21.01.CI.112/10/2012/17/2012/22/2012/23/2012/28/2012/28/2001/04/2101/06/2101/09-10/202101/11/213Sat, No Sun
12/10/2012/17/2012/22/2012/23/2012/25/2012/28/2001/04/2101/09/2101/11/213Sat, No Sun
UNIX Maintenenance Only11/27/1612/17/2016*4Sat & Sun
19.12.IN.1Solaris Monthly Patching12/22/1912/28/194Sat & Sun
21.02.CI.101/14/2101/21/2101/26/2101/27/2101/29/2102/01/2102/08/2102/10/2102/13-14/202102/16/213Sat, No Sun
01/14/2101/21/2101/25/2101/27/2101/29/2102/01/2102/08/2102/13/2102/15/213Sat, No Sun
Database Maintenenance Only01/17/1701/21/2017*4Sat & Sun
02/11/2102/18/2102/22/2102/24/2102/26/2103/01/2103/08/2103/13/2103/15/213Sat, No Sun
21.03.CI.102/11/2102/18/2102/23/2102/24/2102/26/2103/01/2103/08/2103/10/2103/13-14/202103/15/213Sat, No Sun
20.01.IN.1Solaris Monthly Patching01/19/2001/25/204Sat & Sun
20.02.IN.1Solaris Monthly Patching02/16/2002/29/204Sat & Sun
21.04.CI.103/11/2103/18/2103/23/2103/24/2103/26/2103/29/2104/05/2104/07/2104/10-11/202104/12/213Sat, No Sun
03/11/2103/18/2103/22/2103/24/2103/26/2103/29/2104/05/2104/07/2104/10/2104/12/213Sat, No Sun
UNIX Maintenenance Only02/26/1703/25/2017*4Sat & Sun
20.03.IN.1Solaris Monthly Patching03/22/2003/28/204Sat & Sun
21.05.CI.104/15/2104/22/2104/27/2104/28/2104/30/2105/03/2105/10/2105/12/2105/15-16/202105/17/213Sat, No Sun
04/15/2104/22/2104/27/2104/28/2104/30/2105/03/2105/10/2105/12/2105/15/2105/17/213Sat, No Sun
Database Maintenenance Only04/10/1704/15/2017*4Sat & Sun
20.04.IN.1Solaris Monthly Patching04/19/2004/25/204Sat & Sun
21.06.CI.105/13/2105/20/2105/25/2105/26/2105/28/2106/01/2106/07/2106/09/2106/12-13/202106/14/213Sat, No Sun
Web Infrastructure Upgrade Only05/15/1705/20/2017*4Sat & Sun
06/10/2106/17/2106/21/2106/23/2106/25/2106/28/2107/05/2107/07/2107/10/2107/12/213Sat, No Sun
21.07.CI.106/10/2106/17/2106/22/2106/23/2106/25/2106/28/2107/06/2107/07/2107/10-11/202107/12/213Sat, No Sun
20.05.IN.1Solaris Monthly Patching05/17/2005/30/204Sat & Sun
UNIX Maintenenance Only05/28/1706/24/2017*4Sat & Sun
20.06.IN.1Solaris Monthly Patching06/21/2006/27/204Sat & Sun
21.08.CI.107/15/2107/22/2107/27/2107/28/2107/30/2108/02/2108/09/2108/11/2108/14-15/202108/16/213Sat, No Sun
07/15/2107/22/2107/26/2107/28/2107/30/2108/02/2108/09/2108/14/2108/16/213Sat, No Sun
Database Maintenenance Only07/10/1707/15/2017*4Sat & Sun
20.07.IN.1Solaris Monthly Patching07/19/2007/25/204Sat & Sun
21.09.CI.108/12/2108/19/2108/24/2108/25/2108/27/2108/30/2109/07/2109/08/2109/11-12/202109/13/213Sat, No Sun
08/12/2108/19/2108/23/2108/25/2108/27/2108/30/2109/06/2109/11/2109/13/213Sat, No Sun
20.08.IN.1Solaris Monthly Patching08/16/2008/29/204Sat & Sun
Dimensions Application /Database Upgrade - Field users not impacted09/24/2016***4Sat & Sun
20.09.IN.1Solaris Monthly Patching09/20/2009/26/204Sat & Sun
NOTES:
Special Note: A sprint is defined as a finished portion of a product that is delivered between one week and one month. To be more flexible and comply with a
with a more agile methodology schedule, the SIO schedule has been revised to meet the upper limits of requirements for scheduling.
Note: Corporate Sun, Desktop Client Only, and Enterprise Architecture (WebLogic) Applications all follow this same schedule of installations (includes VN releases for March and August).
Note: Solaris Monthly Patching are implemented by the Austin ITC. PPRD/PERF instalsl occur every 3rd Sunday of the month from 7:00 am to 1:00 pm CT. Production every last Saturday of the month from 6:00 pm to 11:59 pm.
*Note: UNIX/Database/Tuxedo/Web Enterprise infrastructure Maintenance/Upgrade. No application changes allowed. System WILL be available for Saturday OT and taken offline at 6:00 pm CT on Saturday.
**Note: This is NOT an install weekend. This weekend has required Field unavailablity to complete the annual Corporate Comp Adjust Run. No Field OT.
***Note: Dimensions Application/Database Upgrade to the new release. Affects Development Systems and Dimension Production, but NOT field users.
1. Column A defines the coordinated installation release number - a unique identifier for each cycle. See Key for details.
2. Column B defines the date that the PIAs are due to SIO for the current cycle.
3. Column C defines the last day during which SIO will accept application software and instructions from the developer (ATT actioned to SIO) and during which VBAPERF
will be refreshed from the CDCI image and restaged by NGIT. VBAPPRD will be restaged by SIO. No software will be accepted after this date without a change order.
4. Column D defines the time period set aside for VBAPPRD to be offline for the beginning of the VBAPPRD installations. This includes downtime for the Tuxedo environment.
5. Column E defines the time period set aside for Hines to install applications in VBAPERF and SIO Lab. Additional day provided, if needed.
6. Column F defines the date when a two week notification must be sent to the ROs for a required coordinated installation.
7. Column G defines the time period for NGIT to accomplish performance testing in VBAPERF and defines the date when regression testing will be accomplished in Preprod.
Regression testing may start earlier than scheduled if the ITOPS installs are completed.
8. Column H defines the start date for release of Web and Non-Web (client-only) coordinated apps release memo to the Regional Offices.
9. Column I defines the date of the Go/No Go call conference call as established by ITOPS Senior Leadership and lead by OBPI. It occurs at 12 pm CT/1 pm ET. This call is used to decide if the weekend install can proceed.
10. Column J defines the weekend of the coordinated installation for application installation, validation, field testing and implementation. Or defines the Friday Solaris patching schedule.
11. Column K defines the Monday by which all required coordinated installations dependent on database changes must be completed.
12. Column L defines the level of installs for an agile methodology schedule. See Level of Install Key.
13. Column M defines the times when regular overtime to the field will be impacted or not impacted for the installation weekend. See OT Availability Key.
3/18/20

&"Arial,Bold"&16&USIO FISCAL YEAR IMPLEMENTATION SCHEDULE 2021 Rev. 8

Misc

ABCDEFGHIJKL
Weeks 1 & 2Week 3Week 4Week 5Week 6Week 6
Release CoordinatorsHines AcceptsHines InstallsRegressionRelease ClientBeta Testing/Weekend forDeploy ClientLast Date for
PIAsSends E-Mail to SIOApplicationsIn VBAPERF and VBAPPRD and& PerformanceOnly Apps to BetaFeedback to SIOCoordinatedOnly AppsRO End UserAcadVNTRAIN
Due toMailbox ListingRefresh and RestageSIO PreProd LabTest WeekSend 2 Wk Notice& MINOR ChgsInstallCoord InstallAvailabilityInstallInstall
SIOApplications withVBAPERF, VBAPPRDfor Req Installsto InstructionsCompl DateCompleteComplete
Version Numbers forFINALCont. Regression(Sat & Sunday)
Pre-Production CycleReceive Date& Perf Testing

08/20/08 09/05/08 09/19/08 09/29/08 10/13/08 10/20/08 10/27/08 11/01/08 11/03/08 11/08/08 10/30/08 11/06/08

&"Arial,Bold"&16HINES ITC 2008 PRE-PRODUCTION SCHEDULE

Version 1.0 Draft June 2007

Keys OT Availability Key Coordinated Implementation Number

Sat & Sun OT available
NO weekend OT availableA unique identifier for each
OT available on Sat; NO OT available SunCoordinated Release
Limited OT available on Sat; OT available SunFormat: YY.MM.CI.#
Sat, Sun & Mon OT available; Limited systemYY=Year
availability.MM=Month
CI=Coordinated Installation
IN=Infrastructure Installation
Non-Coordinated Installation Weekend System Availability#=Scheduled release for the
Saturdays: 6:00 am - 6:00 pm (CT)month
Sundays: 6:00 am to 6:00 pm (CT)
Level of Installs
Level 1: Productivity/Payment Critical Install
•BPSC will define a priority matrix that will be used to determine when an install must happen in less than
48 hours to address system critical issues.
•High Risk install acceptance implied due to minimal to no PreProd testing and no performance testing.
Level 2: Weekly Supplemental installs which can’t wait for the next Level 3 or 4 install but are not Level 1 critical
•BPSC will define a Productivity/Payment/Correspondence priority matrix that will determine when an install
can't wait for the next install cycle.
•Level 2 installs will be done weekly so that fixes can be grouped and tested.
•Moderate to High Risk install acceptance implied due to reduced PreProd testing and no performance testing.
Level 3: These will be coordinated installs that occur on a four-week basis
•Freeze three weeks before the install.
•14 days before the install, field production outage for the install will need to be evaluated and agreed to.
•Level 3 installs should not have major impact to a majority of weekend field users working production OT.
Level 4: This is an expanded Level 3 install that will occur in place of a Level 3 install with a minimum of 60 to 90 days notice
•These installs will need extended down time for major system upgrades that affect large numbers of applications

such as an Oracle upgrade or Solaris upgrade or a major database architecture change.

•Level 4 installs will be reviewed and approved at the standard monthly install impact review that occurs 60 to 90 days prior to the requested install date.

HINES ITC 2014 PRE-PRODUCTION SCHEDULE KEY

Feedback on draft

DateSubmitted byIssue/Concern
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26

File details come from the government source that posted it. Updated .