5-BPM004453 Change Log TemplateV1.xlsx
XLSX spreadsheet 16 KB Posted
- Attached to
- Master Agreement AZ|CTR062780
- Contract number
- CTR062780
- Issued by
- Arizona
About this file
This document is a Change Log for a Best and Final Offer (BAFO) related to the Arizona Department of Child Services (AZ DCS) IT Maintenance and Operations Services contract. The primary contractor is IBM, who is updating various attachments and sections of their original proposal in response to negotiations with the state agency. The change log details modifications across multiple attachments, including key personnel changes, organizational profile updates, and revisions to specific service requirements.
The contract covers comprehensive IT services including managed cloud services, operational support services, routine application support, minor development services, major enhancements, solution architecture, and business analytics and reporting. Key changes include replacing key personnel (Sanjeev Gypta with Mihir Shah), optimizing staffing with onshore and offshore resources, updating Azure DevOps processes, and refining service boundaries. The document indicates a flexible service model with provisions for shared services, 24x7 support coverage, and optional services like solution architecture assessment and human-centered design. Pricing was updated across all tabs of the master pricing sheet, suggesting potential adjustments to the overall contract value and rate structure.
View the file
Other files
Show all 46
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Change Log
| Best and Final Offer (BAFO) Change Log: BPM004453 - DCS IT Maintenance and Operations Services | |||
| *** Note: All Changes to your Original Bid Must be Documented in the Change Log *** | |||
| DOCUMENT | LOCATION | BRIEF DESCRIPTION OF CHANGE | |
| Attachment 1--Offer and Acceptance Form | Page 1 | Dated and signed | |
| DOCUMENT | LOCATION | BRIEF DESCRIPTION OF CHANGE | |
| Attachment 2--Boycott of Israel Disclosure-Signature Page | Not Applicable | No update required | |
| DOCUMENT | LOCATION | BRIEF DESCRIPTION OF CHANGE | |
| Attachment 3--Confidential Information-Signature Page | Not Applicable | No update required | |
| Attachment 3--Supplement | Not Applicable | No update required | |
| DOCUMENT | LOCATION | BRIEF DESCRIPTION OF CHANGE | |
| Attachment 4--Conformance Statements and Supplements | Updated to change conformance to scope of work and pricing to "Yes". | ||
| Attachment 4 Supplement 2 | Not Applicable | Deleted this supplement, and removed exceptions from original proposal submission. | |
| Attachment 4 Supplement 3 | Not Applicable | Based on negotiations with AZ DCS, this supplement has been updated with only the agreed to exceptions and language. | |
| Attachment 4 Supplement 4 | Not Applicable | Deleted this supplement. This was a track changes version of the exceptions against the original solicitation document. These are not being submitted only in Supplement 3. | |
| DOCUMENT | LOCATION | BRIEF DESCRIPTION OF CHANGE | |
| Attachment 5--Key Personnel | Page 1- 2 | Replaced resume for Sanjeev Gypta with Mihir Shah, DPE for Maintenance and Operations | |
| Attachment 5--Key Personnel | Page 6 | Included resume of Linz Philip as additional key personnel, Client Partner Executive | |
| Attachment 5--Supplement | Page 1-3 | Replaced resume for Sanjeev Gypta with Mihir Shah, DPE for Maintenance and Operations | |
| Attachment 5--Supplement | Page 15 | Added resume for Linz Philip, Client Partner Executive | |
| DOCUMENT | LOCATION | BRIEF DESCRIPTION OF CHANGE | |
| Attachment 6--Letter of Insurability | Not Applicable | No update required | |
| DOCUMENT | LOCATION | BRIEF DESCRIPTION OF CHANGE | |
| Attachment 7--Organizational Profile | Attachment 7 | Updated information about its expiration date | |
| Attachment 7 Supplement 1 | Attachment 7 Supplement 1 | New MS Gold Certification letter included | |
| DOCUMENT | LOCATION | BRIEF DESCRIPTION OF CHANGE | |
| Attachment 8--Proposed Contractors | Not Applicable | No update required | |
| Attachment 8 Supplement | Attachment 8 Supplement | New certification form | |
| DOCUMENT | LOCATION | BRIEF DESCRIPTION OF CHANGE | |
| Attachment 9 | Question 1: Company Profile | Updated details associated with IBM's MS Dynamics and Azure experience; added additional Gold Partner accreditations; Updated the Organizational Chart | |
| Attachment 9 | Question 2: | Company Experience | Changed the years of Partnership with CWS/CMS in ST of CA from 20 years to 30 years |
| Attachment 9 | Question 4: | Use of On-Shore and Off-Shore Resource | Based on BAFO discussions, optimized the staffing by adding offshore resources in Operational Support Services, Routine Application Support and Minor Development Services; added IBM best practices with onshore/offshore model |
| Attachment 9 | Question 5: | Use of Subcontractors | Added a paragraph on the work arrangement with Subcontracting firms and IBM's SPOC for any tasks assigned to them |
| Attachment 9 | Question 6: | Staffing Plan | Updated the Organizational Chart |
| Attachment 9 | Question 2: Requirement 3.0 General | Moved In-Scope Security Services and Boundaries to Section 4.4.3 and deleted it from this section | |
| Attachment 9 | Question 3: Requirement 4.1 Transition Plan | Removed the Transition Org Chart to have consistency in the document; changed the assumptions to responsibilities based on the BAFO discussions; added required SME support; Minor wording changes for consistency | |
| Attachment 9 | Question 4: Requirement 4.2 Transition Services | Updated the Table with list of portfolios in-scope for transition in response to the clarification questions requested by the State; Replaced the Overall Transition timelines chart to be in consistent with the orals presentation; Removed the Transition Org Chart to have consistency in the document ; Replaced the Transition governance diagram with the one from orals presentation; Minor wording changes for consistency | |
| Attachment 9 | Question 5: Requirement 4.3.1 Program Management Services | Minor wording changes for consistency | |
| Attachment 9 | Question 6: Requirement 4.3.2 Program Management Services | Minor wording changes for consistency; Added the boundary conditions based on our BAFO discussions | |
| Attachment 9 | Question 7: Requirement 4.3.3 Program Management Services | Minor wording changes for consistency | |
| Attachment 9 | Question 9: Requirement 4.4.1 Managed Cloud Services | Based on BAFO discussions, updated to reflect Shared services model; added statements on how to integrate IBM's tools with State tools and do the transition; Added the scope boundaries as discussed during the BAFO | |
| Attachment 9 | Question 10: Requirement 4.4.2 Managed Cloud Services | Based on BAFO discussions, updated to reflect Shared services model | |
| Attachment 9 | Question 11: Requirement 4.4.3 Managed Cloud Services | Updated section to align the security scope as per the discussion during BAFO | |
| Attachment 9 | Question 16: Requirement 4.4.8 Managed Cloud Services | Updated section to align the security scope as per the discussion during BAFO | |
| Attachment 9 | Question 18: Requirement 4.4.10 Managed Cloud Services | Based on BAFO discussions, updated to reflect Shared services model | |
| Attachment 9 | Question 19: Requirement 4.4.11 Managed Cloud Services | Based on BAFO discussions, updated to reflect Shared services model | |
| Attachment 9 | Question 20: Requirement 4.4.12 Managed Cloud Services | Minor wording changes for consistency | |
| Attachment 9 | Question 21: Requirement 4.4.13 Managed Cloud Services | Based on BAFO discussions, updated to reflect Shared services model | |
| Attachment 9 | Question 25: Requirement 4.5.1 Operational Support Services | Clarified IBM support team's 24x7 coverage model; Provided fixed capacity team structure | |
| Attachment 9 | Question 26: Requirement 4.5.2 Operational Support Services | Minor wording changes for consistency | |
| Attachment 9 | Question 27: Requirement 4.5.3 Operational Support Services | Minor wording changes for consistency | |
| Attachment 9 | Question 29: Requirement 4.5.5 Operational Support Services | Minor wording changes for consistency | |
| Attachment 9 | Question 30: Requirement 4.5.6 Operational Support Services | Minor wording changes for consistency | |
| Attachment 9 | Question 32: Requirement 4.5.8 Operational Support Services | Based on BAFO discussion, aligned the responsibilities of IBM and AZ DCS in developing any new interfaces | |
| Attachment 9 | Question 33: Requirement 4.5.9 Operational Support Services | Minor wording changes for consistency | |
| Attachment 9 | Question 34: Requirement 4.5.10 Operational Support Services | Minor wording changes for consistency | |
| Attachment 9 | Question 35: Requirement 4.5.11 Operational Support Services | Minor wording changes for consistency | |
| Attachment 9 | Question 36: Requirement 4.5.12 Operational Support Services | Based on BAFO discussion, clarified the Design, Development and implementation of a new BC/DR would be thru Major Enhancements ; Minor wording changes for consistency | |
| Attachment 9 | Question 37: Requirement 4.5.13 Operational Support Services | Minor wording changes for consistency | |
| Attachment 9 | Question 38: Requirement 4.5.14 Operational Support Services | Minor wording changes for consistency | |
| Attachment 9 | Question 39: Requirement 4.5.15 Operational Support Services | Minor wording changes for consistency | |
| Attachment 9 | Question 40: Requirement 4.5.16 Operational Support Services | Minor wording changes for consistency | |
| Attachment 9 | Question 41: Requirement 4.5.17 Operational Support Services | Minor wording changes for consistency | |
| Attachment 9 | Question 42: Requirement 4.5.18 Operational Support Services | Minor wording changes for consistency | |
| Attachment 9 | Question 43: Requirement 4.5.19 Operational Support Services | Minor wording changes for consistency | |
| Attachment 9 | Question 44: Requirement 4.5.20 Operational Support Services | Minor wording changes for consistency | |
| Attachment 9 | Question 45: Requirement 4.5.21 Operational Support Services | Minor wording changes for consistency | |
| Attachment 9 | Question 46: Requirement 4.5.22 Operational Support Services | Minor wording changes for consistency | |
| Attachment 9 | Question 47: Requirement 4.5.23 Operational Support Services | Minor wording changes for consistency | |
| Attachment 9 | Question 48: Requirement 4.5.24 Operational Support Services | Based on BAFO discussion, clarified the use of training tools and training under operational support services | |
| Attachment 9 | Question 49: Requirement 4.5.25 Operational Support Services | Updated this section as per the clarification questions from the State related to training and training tools | |
| Attachment 9 | Question 50: Requirement 4.5.26 Operational Support Services | Minor wording changes for consistency | |
| Attachment 9 | Question 51: Requirement 4.5.27 Operational Support Services | Minor wording changes for consistency | |
| Attachment 9 | Question 52: Requirement 4.5.28 Operational Support Services | Minor wording changes for consistency | |
| Attachment 9 | Question 53: Requirement 4.5.29 Operational Support Services | Minor wording changes for consistency | |
| Attachment 9 | Question 54: Requirement 4.5.30 Operational Support Services | As per the BAFO discussion, IBM Blueworks will not be used in AZ DCS for business flow diagrams | |
| Attachment 9 | Question 55: Requirement 4.5.31 Operational Support Services | Minor wording changes for consistency | |
| Attachment 9 | Question 56: Requirement 4.5.32 Operational Support Services | Minor wording changes for consistency | |
| Attachment 9 | Question 58: Requirement 4.6.1 Routine Guardian Application Support and Minor Development Services | Based on BAFO discussion, provided a description of fixed capacity team structure | |
| Attachment 9 | Question 59: Requirement 4.6.2 Routine Guardian Application Support and Minor Development Services | Updated the IBM proposed Azure DevOps processes flow to be consistent with the orals presentation | |
| Attachment 9 | Question 60: Requirement 4.6.3 Routine Guardian Application Support and Minor Development Services | Based on the BAFO discussions, included Azure DevOps Boards as the software development tracking tool | |
| Attachment 9 | Question 61: Requirement 4.6.4 Routine Guardian Application Support and Minor Development Services | Minor wording changes for consistency | |
| Attachment 9 | Question 62: Requirement 4.6.5 Routine Guardian Application Support and Minor Development Services | Minor wording changes for consistency | |
| Attachment 9 | Question 63: Requirement 4.6.6 Routine Guardian Application Support and Minor Development Services | Minor wording changes for consistency | |
| Attachment 9 | Question 64: Requirement 4.6.7 Routine Guardian Application Support and Minor Development Services | Minor wording changes for consistency | |
| Attachment 9 | Question 65: Requirement 4.6.8 Routine Guardian Application Support and Minor Development Services | Minor wording changes for consistency | |
| Attachment 9 | Question 67: Requirement 4.6.10 Routine Guardian Application Support and Minor Development Services | Minor wording changes for consistency | |
| Attachment 9 | Question 68: Requirement 4.6.11 Routine Guardian Application Support and Minor Development Services | Minor wording changes for consistency | |
| Attachment 9 | Question 71: Requirement 4.6.14 Routine Guardian Application Support and Minor Development Services | Minor wording changes for consistency | |
| Attachment 9 | Question 72: Requirement 4.6.15 Routine Guardian Application Support and Minor Development Services | Based on BAFO discussion, revised the Data Obfuscation Scope | |
| Attachment 9 | Question 73: Requirement 4.7.1 Guardian Major Enhancements and Solution Architecture Services | Clarified approach to utilize the Major and Minor enhancement hours based on the response to clarification questions from the State | |
| Attachment 9 | Question 75: Requirement 4.7.3 Guardian Major Enhancements and Solution Architecture Services | Minor wording changes for consistency | |
| Attachment 9 | Question 77: Requirement 4.7.5 Guardian Major Enhancements and Solution Architecture Services | Minor wording changes for consistency | |
| Attachment 9 | Question 78: Requirement 4.7.6 Guardian Major Enhancements and Solution Architecture Services | Minor wording changes for consistency | |
| Attachment 9 | Question 79: Requirement 4.7.7 Guardian Major Enhancements and Solution Architecture Services | Minor wording changes for consistency | |
| Attachment 9 | Question 80: Requirement 4.7.8 Guardian Major Enhancements and Solution Architecture Services | Minor wording changes for consistency | |
| Attachment 9 | Question 81: Requirement 4.7.9 Guardian Major Enhancements and Solution Architecture Services. | Minor wording changes for consistency | |
| Attachment 9 | Question 82: Requirement 4.7.10 Guardian Major Enhancements and Solution Architecture Services | Minor wording changes for consistency; Based on BAFO discussions, moved DR testing out of this section and retained it in Question 42 | |
| Attachment 9 | Question 84: Requirement 4.7.12 Guardian Major Enhancements and Solution Architecture Services | Minor wording changes for consistency | |
| Attachment 9 | Question 93: Requirement 4.8.7 Business Analytics and Reporting Services | Minor wording changes for consistency | |
| Attachment 9 | Question 98: Requirement 4.8.12 Business Analytics and Reporting Services | Added a paragraph on how the data lineage be traced from Dynamics to Power BI as per the clarification questions from the State | |
| Attachment 9 | Question 99: Requirement 4.8.13 Business Analytics and Reporting Services | Minor wording changes for consistency | |
| Attachment 9 | Question 101: Requirement 4.8.15 Business Analytics and Reporting Services | Updated this section in response to the clarification questions requested by the State | |
| Attachment 9 | Question 102: Requirement 4.8.16 Business Analytics and Reporting Services | Updated this section in response to the clarification questions requested by the State | |
| Attachment 9 | Question 103: Requirement 4.8.17 Business Analytics and Reporting Services | Updated this section in response to the clarification questions requested by the State | |
| Attachment 9 | Question 106: Requirement 4.8.20 Business Analytics and Reporting Services | Updated this section in response to the clarification questions requested by the State | |
| Attachment 9 | Question 108: Requirement 4.8.22 Business Analytics and Reporting Services. | Updated this section in response to the clarification questions requested by the State | |
| Attachment 9 | Question 110: Requirement 4.9.2 Staffing | Revised the Key Personnel Table - Replaced Sanjiv Gupta with Mihir Shah | |
| Attachment 9 | Question 111: Requirement 4.9.3 Staffing | Minor wording changes for consistency | |
| Attachment 9 | Question 112: Requirement 4.9.4 Staffing | Minor wording changes for consistency | |
| Attachment 9 | Question 113: Requirement 4.9.5 Staffing | Minor wording changes for consistency | |
| Attachment 9 | Question 118: Requirement 4.9.10 Staffing | Minor wording changes for consistency | |
| Attachment 9 | Question 119: Requirement 4.9.11 Staffing | As per BAFO discussions, clarified that drug test may be required only for onshore resources; Minor wording changes for consistency | |
| Attachment 9 | Question 121: Requirement 5.1.1 Optional: Solution Architecture Assessment | Clarified the difference between the Architecture assessment and Backlog review during transition; Minor wording changes for consistency | |
| Attachment 9 | Question 123: Requirement 5.1.3 Optional: Solution Architecture Assessment | Minor wording changes for consistency | |
| Attachment 9 | Question 124: Requirement 5.1.4 Optional: Solution Architecture Assessment | Minor wording changes for consistency | |
| Attachment 9 | Question 125: Requirement 5.1.5 Optional: Solution Architecture Assessment | Minor wording changes for consistency | |
| Attachment 9 | Question 126: Requirement 5.1.6 Optional: Solution Architecture Assessment | Minor wording changes for consistency | |
| Attachment 9 | Question 127: Requirement 5.1.7 Optional: Solution Architecture Assessment | Minor wording changes for consistency | |
| Attachment 9 | Question 128: Requirement 5.1.8 Optional: Solution Architecture Assessment | Based on BAFO discussions, focused the scope on State's highest priorities related to data | |
| Attachment 9 | Question 129: Requirement 5.1.9 Optional: Solution Architecture Assessment | Minor wording changes for consistency | |
| Attachment 9 | Question 130: Requirement 5.2.1 Optional: Human Centered Design | Revised the scope of HCD based on BAFO discussions | |
| Attachment 9 | Question 131: Requirement 5.2.2 Optional: Human Centered Design | Revised the scope of HCD based on BAFO discussions | |
| Attachment 9 | Question 132: Requirement 5.2.3 Optional: Human Centered Design | Revised the scope of HCD based on BAFO discussions | |
| Attachment 9 | Question 133: Requirement 6.1 Performance Management | Based on BAFO discussions, confirmed that the SLA's will be defined and mutually agreed upon during the transition | |
| Attachment 9 | Question 134: Requirement 6.2 Performance Management | Based on BAFO discussions, confirmed that the SLA's will be defined and mutually agreed upon during the transition | |
| Attachment 9 | Question 135: Requirement 6.3 Performance Management | Based on BAFO discussions, confirmed that the SLA's will be defined and mutually agreed upon during the transition | |
| Attachment 9 | Question 136: Requirement 6.4 Performance Management | Minor wording changes for consistency | |
| Attachment 9 | Question 137: Requirement 6.5 Performance Management | Minor wording changes for consistency | |
| Attachment 9 | Question 138: Requirement 6.6 Performance Management | Based on BAFO discussions, confirmed that the SLA's will be defined and mutually agreed upon during the transition | |
| DOCUMENT | LOCATION | BRIEF DESCRIPTION OF CHANGE | |
| Attachment 10 | Not Applicable | No update required | |
| DOCUMENT | LOCATION | BRIEF DESCRIPTION OF CHANGE | |
| SPO Form 205 - Forced Labor of Ethnic Uyghurs Ban | New document | Selected the correct option and Signed the document | |
| DOCUMENT | LOCATION | BRIEF DESCRIPTION OF CHANGE | |
| Master Pricing Sheet | All Tabs | Updated with new price |
File details come from the government source that posted it. Updated .