CCWIS IVV Attachment A - IVV Narrative v.2 Updated 11.29.21.docx

STATE OF ILLINOIS

Section 4.D. Project Staffing & Resources

IV&V NarratiVe Offeror: [Offeror Name] Offer Name: [Offer Name] {An Offeror may present multiple offers with differing partners. Please name offers for clarity}

Notes for use of the template:

Items within curly-brackets {} are notes to assist in providing the sought for information. Items within {} should be removed before submission.

Items within <> brackets require direct replacement of the desired field.

ATTACHMENT A: IV&V VENDOR NARRATIVE

Illinois Department of Children and Family Services Enhanced Independent Verification & Validation Services for CCWIS Project – v.2 Updated 11.29.2021 DCFS PO19-165 – BidBuy Bid# B-24914 & B-24915

STATE OF ILLINOIS

STATE OF ILLINOIS

TABLE OF CONTENTS

State of Illinois Attachment A: IV&V Narrative 2

SECTION 1:

Purpose of this Document The IV&V Narrative provides the Offeror’s approach to enhanced IV&V Scope of Work and Deliverables from a business perspective. The purpose of the narrative is to convey what the desired outcomes should be for the Trusted Advisor and traditional IV&V approach and how they will be accomplished. Providing an IV&V Narrative also supports stakeholder communication by providing a complete overview of proposed methods and activities that may be employed by the Offeror to implement IV&V activities. It is the Offeror’s sole responsibility to ensure this document, and the Offeror’s Pricing Table (Attachment B) completely captures all tasks and billable services required for the enhanced IV&V scope of work for the DCFS CCWIS Project. Failure to include any task or billable service does not absolve the Offeror from completing the tasks or billable services at their own expense.

This template shows desired contents of the IV&V Vendor Narrative. This document, in addition to the request work samples, will be used to evaluate the Offeror’s proposed approach, experience, methodologies, tools, and staff. It is the Offeror’s responsibility to review each task and subtask described in the RFP Section D, Scope of Services, to formulate a complete response specific to each task question.

To reduce document length and allow for an expedited review by the Evaluation Committee: DO NOT INCLUDE SALES MATERIAL IN ANY ATTACHMENT.

v.2 Updates are highlighted in red text.

SECTION 2.B IV&V APPROACH

SECTION 2:

IV&V Approach IV&V Vendor AppRoach It is the expectation of the Agency that the awarded IV&V Vendor will work with State staff, other DCFS CCWIS Program vendors, including but not limited to the State’s System Integration Vendor, OCM/BPR Vendor, Project Management Vendor, and CCWIS technical program subcontractors to successfully review, assesses, and report on the CCWIS Project implementation activities. The Vendor is responsible for developing and executing a comprehensive approach to IV&V that ensures successful completion, and federal certification of the DCFS CCWIS Solution.

Attachment A is intended to capture relevant information for all Service Categories: but are not limited to the following broad categories: 1) Technical Compliance (Traditional IV&V), 2) Quality Assurance, 3) Strategic Planning, 4) Project Advisory and/or Consulting (Trusted Advisor), 5) Risk Management, and 6) IT Auditing. Offeror’s are encouraged to keep these service categories in mind while completing this form.

Please Note: In Sections below DCFS requests sample work product. To reduce the length of responses in Attachment A, please attach the sample work product in Packet 2 of your offer and only provide the requested description or narrative in this Attachment A. Sample work product are highlighted in the section they are requested. See the RFP Section C.7. (Page 20) for a complete list of requested sample work product and the relevant section where they can be found. Sample work product will be evaluated in conjunction with Offeror’s response in this attachment.

Instructions: {Please answer the mandatory requirements below, these are requirements of this RFP and will not be scored. The Offeror shall state their agreement and identify by position/title the individual(s) who will be responsible for these activities. Failure to agree to or meet a mandatory requirement may result in the Offeror’s proposal being found non-responsive.} Mandatory 1: IV&V Vendor Certification (RFP Reference Scope of Work IVVM-1) {Demonstrate compliance verifications and validations will be sufficiently independent from nontraditional IV&V services requested in this RFP. Vendor certifies they will comply with the requirements for the IV&V as set forth in the ACF IVV Statement of Work Template.} <Enter Text Here> Mandatory 2: IV&V Management Plan (RFP Reference Scope of Work IVVM-2, IVVM-3) {Develop an IV&V Management Plan and IV&V Checklist and Key Performance Indicator (KPI) dashboard. Vendor certifies they will compile and deliver the IV&V Checklist addressing al project lifecycle phases as identified in the ACF IVV Statement of Work Template. Please describe your Plan and Checklist below and submit a sample IV&V Management Plan and IV&V Checklist, including a draft Deliverable Expectation Document (DED) and Deliverable Observation Report (DOR) (In Packet 2) Samples can be redacted, or you may submit a template with all categories listed to satisfy this request. } <Enter Text Here> Mandatory 3: Periodic IV&V Project Review and Reports, and Debriefings (RFP Reference Scope of Work IVVM-4, IVVM-5, IVVM-6) {Vendor certifies they will conduct periodic IV&V Project Reviews and provide periodic IV&V Review Reports. Vendor shall deliver a draft of each periodic report and correct mistakes of fact the draft version, append to the draft version, redeliver until such time that Federal ACF and DCFS are satisfied the content accurately reflects the ongoing of the CCWIS Project, final copy shall be marked Final and delivered as requested by DCFS. Vendor shall provide debriefings to DCFS and Federal ACF as requested on any Final IV&V Review Report. } <Enter Text Here> Mandatory 4: IV&V Statement of Work Template (RFP Reference: Section E Deliverables (Page 48)) {Vendor certifies they adhere to the IV&V Format and Content Reporting Requirements in the ACF IVV Statement of Work Template.} <Enter Text Here> Mandatory 5: Cross-referencing of Standards (RFP Reference: Section D.2 IV&V Standards (Page 24)) {Vendor certifies they have sufficiently met the following requirement: Where an Offeror has a similar, corresponding, but different set of minimum standards than those cited above, the Offeror will be expected to cross-reference or otherwise map how their own standards meet the same level of detail and scope of review as the industry standards for IV&V cited herein (e.g., CMMI, PMBOK, and IEEE).} <Enter Text Here> Planning and Oversight – Additional Mandatory Requirements: Vendor certifies they will comply with the scope identified below, in this Section B.1.1.

Procurement (Reference Scope of Work PO-1, PO-2, PO-3) {Verify that the obligations of the Vendor, subcontractors, and external staff (terms, conditions, statement of work, requirements, technical standards, performance standards, development milestones, acceptance criteria, delivery dates, etc.) are clearly defined and realistic. This includes verifying that performance metrics have been added that will allow tracking of project performance and progress against criteria set by the State and providing feedback to the State on System Integrator proposals that do not present realistic expectations or metrics.} <Enter Text Here> {Assist Department and awarded SI Vendor with drafting a Master Contract Schedule, using the SI Vendor’s High-Level Project Schedule as a guide.} <Enter Text Here> {Verify the final Contract for the System Integration Vendor team states that the Vendor will participate in the IV&V process, being cooperative for coordination and communication of information and indemnifies the IV&V Vendor for all recommendations provided to the Department as part of the IV&V Vendor’s scope of work and meets all ACF requirements to ensure CCWIS Compliance.} <Enter Text Here>

Instructions: {The following sections will be scored as part of the Responsibility evaluation. Fully describe the proposed approach and strategy to enhanced IV&V on this project for the following items. This description should address the Offeror’s high-level approach to IV&V for the three phases of activities described in the Scope of Work (RFP Section 1 Part D) including the following:} Project Management Project Executive Sponsorship (Reference Scope of Work PM-1, PM-2) {Describe the Offeror’s approach to executive stakeholder management, including communication strategies, and details of a KPI dashboard, including but limited to any other tools.}

<Enter Text Here> Management Assessment (Reference Scope of Work PM-3, PM-4, PM-5, PM-6, PM-7, PM-8, PM-9, PM-10, PM-11) {Describe the Offeror’s approach, tools, and communication used to monitor and track another vendors roadmap, while ensuring alignment with DCFS’ CCWIS requirements; including but not limited to tracking team members (both on-site and remote), resource allocations and schedules, approving development environment schedule, all while assuring lines of reporting and oversight.} <Enter Text Here> Project Management (Reference Scope of Work PM-12, PM-13, PM-14, PM-15, PM-16) {Describe the Offeror’s approach for verifying that the following SI documents are created and being followed and are adequate for a project of this size and scope: project management plan, project reporting plan, milestones, early acceptance of releases incentive terms, issue tracking mechanisms and planned lifecycle development methodology.} <Enter Text Here> Business Process Reengineering (BPR) (Reference Scope of Work PM-17, PM-18, PM-19, PM-20, PM-21, PM-22, PM-23, PM-24, PM-25) {Describe the Offeror’s approach for evaluating and verifying that the BPR Plan(s) is adequate to achieve improvement and performance including BPR tasks, responsibilities and deliverables, schedules, KPIs, risks or issues, migration plan, communication plan, and stakeholder participation.} <Enter Text Here> {Describe the Offeror’s approach for evaluating and documenting current and future state of business process, developing stakeholder participation list, including appropriate executive leadership, and ongoing support to ensure continued adaptation to change.}

Risk Management (Reference Scope of Work PM-26) {Describe the Offeror’s approach to evaluating risk management plans and procedures and escalation process for all programs and subprograms (SI, OCM/BPR and Project Management) to verify that risks are identified and quantified and that mitigation plans are developed, communicated, implemented, monitored and complete.} <Enter Text Here> Change Management (Reference Scope of Work PM-27, PM-28, PM-29) {Describe the Offeror’s approach to coordinating the overall Risk Management Plan, including feedback gathering plan and change adoption strategy; and Change Management approach including at a minimum, user readiness, stakeholder assessment and impact analysis.} <Enter Text Here> Communication Management (Reference Scope of Work PM-30) {Describe the Offeror’s approach to evaluating the communication plan and adherence. Discuss your strategies to ensure that the communication plan and strategies to verify they support communications and work product sharing between all project stakeholders; and assess if communication plans and strategies are effective, implemented, monitored, and complete.} <Enter Text Here> Configuration Management (Reference Scope of Work PM-31, PM-32, PM-33, PM-34, PM-35, PM-36, PM-37) {Describe the Offeror’s approach to reviewing and evaluating the Configuration Management plans and procedures, verifying critical documents are under an appropriate level of control, mechanisms and processes and tools are in place.} <Enter Text Here> Project Estimating and Scheduling (Reference Scope of Work PM38, PM 39) {Describe the Offeror’s approach to reviewing, evaluating, and making recommendations on the estimating and scheduling process to ensure there is adequate budget, time, and resources.} <Enter Text Here> Project Personnel (Reference Scope of Work PM-40, PM-41, PM-42) {Describe the Offeror’s approach to evaluating and monitoring job assignments, monthly staffing reports for adequacy of time and resources and the State’s hiring plan for adherence to SI Vendor personnel retention rate.}

Project Organization (Reference Scope of Work PM-43, PM-44) {Describe the Offeror’s approach to verifying adequate organizational technical and managerial oversight, including training, process definition, independent Quality Assurance, Configuration Management, product evaluation. Provide any other project organization functions critical to the project’s success.} <Enter Text Here> Subcontractors and External Staff (Reference Scope of Work PM-45, PM-46, PM-47, PM-48, PM-49) {Describe the Offeror’s approach to evaluating and verifying the use and obligations of subcontractors or external project staff to verify they are clearly defined, their software development methodologies and standards are compatible with the system’s standards and environments, and the subcontractor has the skills, resources, and tools that will not restrict future maintainability, portability, and reusability of the system.} <Enter Text Here> State Oversight (Reference Scope of Work PM-50, PM-51, PM-52) {Describe the Offeror’s approach to verifying State Oversight is provided via monthly reports and reviews, the State has defined technical and managerial inputs for subcontractors needs, and State staff has ultimate responsibility for monitoring project cost and schedule.} <Enter Text Here> Issue Management Plan (Reference Scope of Work PM-53) {Describe the Offeror’s approach to creating and monitoring an Issue Management Plan and process, with responsibility for cataloging key issues for the program, including development of mitigation strategies for each risk, ensuring risks are properly managed and resolved. Narrative should include but is not limited to; issue identification, evaluation methodology, prioritization, resolution, monitoring, and the ongoing evaluation and improvement of the issue management process across all project vendors. Please describe Offeror’s approach to recording, tracking, and maintaining an Issue Log / Register. Describe any lessons learned, good and bod, and how those lessons can be leveraged on this project. Please describe how this approach will specifically address potential issues within the DCFS CCWIS Implementation.} <Enter Text Here> Risk Management Plan and Analysis (Reference Scope of Work PM-54, PM-55) {Describe the Offeror’s approach to creating and monitoring a Risk Management Plan and process, with responsibility for process for identifying potential risks, monitoring that risks are planned for, communicated, and acted upon. Narrative should include but is not limited to; risk evaluation methodology, prioritization, mitigation, monitoring, and the ongoing evaluation and improvement of the risk management process. Please describe how Offeror’s plan will support critical operational decision making including the tools that will be utilized. Please describe Offeror’s approach to recording, tracking, and maintaining a Risk Log / Register. Describe any lessons learned, good and bod, and how those lessons can be leveraged on this project. Please describe how this approach will specifically address potential risks within the DCFS CCWIS Implementation.} <Enter Text Here> Scope Management Plan (Reference Scope of Work PM-56) {Describe the Offeror’s approach to developing and monitoring a Scope Management Plan that defines the processes and procedures used to ensure that all required tasks are completed, and out-of-scope tasks are identified. Please describe Offeror’s processes for out-of-scope tasks. Describe any lessons learned, good and bod, and how those lessons can be leveraged on this project. Please describe how this approach will specifically address managing scope within the DCFS CCWIS Implementation.} <Enter Text Here> IV&V Dashboard (Reference Scope of Work PM-57) {Describe the Offeror’s approach to working with DCFS to develop a systematically updated dashboard for Executive staff and how the dashboard will assure requirements and business process activities are being completed as expected. Please provide a list of key performance indicators and metrics the Offeror believes will be important on the CCWIS Project and why (please see PM-57 for a list of metrics DCFS believes may be important to CCWIS success. Please describe Offeror’s experience, outcomes and lessons learned using a similar dashboard on previous projects and how those experiences can be leveraged on the CCWIS Implementation.} <Enter Text Here> ACF CCWIS Compliance (Reference Scope of Work PM-58) {Describe the Offeror’s experience and approach to ensuring large scale IT implementation receive Federal, State, or Local certification or compliance based on a set of defined, yet high-level or possibly incomplete, set of requirements. Include Offeror’s plan to continuously monitor and measure progress towards previously identified requirements. Describe any lessons learned, good and bod, and how those lessons can be leveraged on this project. Additional points will be awarded to offerors with relevant recent experience with Federal compliance in a health and/or human services sector IT project implementation.} <Enter Text Here> Quality Assurance Quality Assurance (Reference Scope of Work QA-1, QA-2, QA-3, QA-4, QA-5, QA-6, QA-7, QA-8, QA-9) {Describe the Offeror’s approach to evaluating, verifying, and making recommendations on QA plans being implemented to fidelity, have appropriate level of independence from Project Management, QA contractor organizations are monitoring fidelity of defined processes in all project phases, periodic assessments of CMM activities, and processes in place for self-evaluation and process improvement.} <Enter Text Here> Process Definition and Product Standards (Reference Scope of Work QA-10, QA-11, QA-12, QA-13) {Describe the Offeror’s approach to reviewing, verifying, and making recommendations for ensuring major development processes are defined and followed ongoing, processes and standards are compatible with each other, and process definitions and standards are complete, up-to-date and clear, and available to project personnel.} <Enter Text Here> Training User Training and Documentation (Reference Scope of Work TR-1) {Describe the Offeror’s approach for verifying key metrics are effective before training begins and how you will utilize the IV&V-vendor developed checklist in your approach.} <Enter Text Here> User Training and Documentation (Reference Scope of Work TR-2, TR-3, TR-4, TR-5, TR-6, TR-7) {Describe the Offeror’s approach for reviewing, verifying, and making recommendations on OCM/BPR vendor training on revised policies and procedures are communicated, and audiences are prepared for training before it begins, training uses sufficient methodology and tools, training materials, help desk services, policies, and procedures are user friendly and available to users, and training is technically adequate. Approach shall include plan for staff to be on-site for at least one training for each role (external and internal) for each Release. Please describe Offeror’s approach to monitoring, documenting, and reporting on trainee feedback. } <Enter Text Here> Developer Training and Documentation (Reference Scope of Work TR-8, TR-9, TR-10; TR-11) {Describe the Offeror’s approach for reviewing, verifying, and evaluating for effectiveness, and making recommendations for Tier 1, Tier 2, and Tier 3 staff training, process for verifying training and future training is adequate, appropriate for development phase, and includes all necessary documentation.} <Enter Text Here> Requirements Management Requirements Management (Reference Scope of Work RM-1, RM-2, RM-3, RM-4, RM-5) {Describe the Offeror’s approach for evaluating, verifying, and making recommendations on processes and procedures for managing requirements, evaluating the allocation of system requirements, and verifying software requirements can be traced to ensure the system performs as intended and are under formal configuration control.} <Enter Text Here> Security Requirements (Reference Scope of Work RM-6, RM-7, RM-8, RM-9) {Describe the Offeror’s approach for evaluating, verifying, and making recommendations on security policies and procedures, restrictions on system and data access, security and risk analysis, and backup client and project data and files.} <Enter Text Here> Requirements Analysis (Reference Scope of Work RM-10, RM-11, RM-12, RM-13, RM-14, RM-15) {Describe the Offeror’s approach for analyzing requirements including verifying an analysis of client, State and federal needs, each Release meets CCWIS Compliance requirements, stakeholders have been involved in desired functionality and prototyping and project changes, performance requirements meet user needs, and user maintenance requirements are completely specified.} <Enter Text Here> Interface Requirements (Reference Scope of Work RM-16, RM-17, RM-18) {Describe the Offeror’s approach for verifying prior to each release and after final release that all system interfaces are as described, and approved interface documents are available and in place with all agencies and organizations supporting the interfaces.} <Enter Text Here>

Requirements Allocation and Specification (Reference Scope of Work RM-19, RM-20) {Describe the Offeror’s approach for verifying all system requirements have been documented and allocated to either a software or hardware subsystem and that requirements specifications have been developed in sufficient detail.} <Enter Text Here> Reverse Engineering (Reference Scope of Work RM-21) {Describe the Offeror’s approach for verifying the legacy system transfer plan and process is well defined, in place, and followed for reengineering the system.} <Enter Text Here> Operating Environment System Hardware (Reference Scope of Work OE-1, OE-2, OE-3) {Describe the Offeror’s approach for evaluating the adequacy of all relevant system hardware configurations to determine they meet existing and proposed system and CCWIS Compliance requirements.} <Enter Text Here> {Describe the Offeror’s approach to verifying hardware is compatible with existing environment, maintainable, and upgradeable.} <Enter Text Here> {Describe the Offeror’s approach to evaluate current and projected vendor support of hardware and State’s hardware configuration management plans and maintenance and operations procedures.} <Enter Text Here> System Software (Reference Scope of Work OE-4, OE-5, OE-6) {Describe the Offeror’s approach for evaluating new and existing system software to determine if it meets existing and proposed system and CCWIS Certification requirements.} <Enter Text Here> {Describe the Offeror’s approach to verifying software is compatible with hardware and software environment, upgradeable, maintainable, and will meet CCWIS certification requirements.} <Enter Text Here> {Describe the Offeror’s approach to evaluate current and projected vendor support of hardware and State’s hardware configuration management plans and maintenance and operations procedures.}

Database Software (Reference Scope of Work OE-7, OE-8) {Describe the Offeror’s approach for reviewing the adequacy of databases, architecture, and design to meet current and future needs, as well as the approach to verifying that adequate ongoing support is addressed and training of state staff in support activities the State will assume is addressed.} <Enter Text Here> System Capacity (Reference Scope of Work OE-9, OE-10, OE-11) {Describe the Offeror’s approach for evaluating the processing capacity of the implemented system and verifying it is adequate for current statewide needs and results of performance for stress testing.

<Enter Text Here> {Describe the Offeror’s approach to evaluating the availability and reliability of the system.

<Enter Text Here> Development Environment Development Hardware (Reference Scope of Work DE-1, DE-2, DE-3, DE-4) {Describe the Offeror’s approach for evaluating development hardware configurations and determining hardware is maintainable, upgradeable, and compatible with the State’s existing development and processing environment.} <Enter Text Here> {Describe the Offeror’s approach for evaluating the current and projected vendor support of the hardware and the State’s hardware configuration management plans and procedures.} <Enter Text Here> Development Software (Reference Scope of Work DE-5, DE-6, DE-7, DE-8, DE-9) {Describe the Offeror’s approach for evaluating relevant development software adequacy to meet system development requirements and is maintainable, upgradeable, and compatible with the State’s existing hardware and software environment.} <Enter Text Here> {Describe the Offeror’s approach for evaluating the entire environment to determine if it shows an adequate degree of integration compatible with good development.} <Enter Text Here> {Describe the Offeror’s approach for evaluating the current and projected vendor support of the software and the State’s software support, acquisition plans, and procedures.}

Software Development High-Level Design (Reference Scope of Work SD-1, SD-2, SD-3, SD-4, SD-5) {Describe the Offeror’s approach for evaluating, verifying, and making recommendations on existing high-level design products, including design and analysis processes.} <Enter Text Here> {Describe the Offeror’s approach for evaluating, verifying, and making recommendations for improvement on the design and analysis processes used to develop the design, traceability of design requirements to the system requirements, and design products are under configuration control and formally approved before detailed design begins.} <Enter Text Here> Detailed Design (Reference Scope of Work SD-6, SD-7, SD-8, SD-9, SD-10, SD-11) {Describe the Offeror’s approach for evaluating and making recommendations on existing detailed design products to ensure they are workable, efficient, and satisfy all high-level design requirements and adhere to the project design methodology and standards.} <Enter Text Here> {Describe the Offeror’s approach for evaluating and making recommendations on the process used to develop the design, design standards and methodology, and design requirements can be traced back to system requirements and high-level design, are design products are under figuration control and formally approved before coding begins.} <Enter Text Here> Job Control (Reference Scope of Work SD-12, SD-13, SD-14, SD-15, SD-16) {Describe the Offeror’s approach for evaluating and making recommendations with early notification of issues to the State on existing job control and the process for designing job control.} <Enter Text Here> {Describe the Offeror’s approach for evaluating batch jobs for appropriate scheduling, timing, and internal and external dependencies, appropriate use of OS scheduling software is used, and verifying job control language scripts are under an appropriate level of configuration control.} <Enter Text Here> Code (Reference Scope of Work SD-17, SD-18, SD-19, SD-20, SD-21, SD-22) {Describe the Offeror’s approach for evaluating and making recommendations on standards and process currently in place for code development, existing code base maintainability, code documentation, coding standards and guidelines and project’s compliance with standards and guidelines.} <Enter Text Here>

{Describe the Offeror’s approach for conducting code reviews and verifying development code is under appropriate configuration and control and accessible to developers.} <Enter Text Here> {Describe the Offeror’s approach to evaluating the project’s use of software metrics in management and quality assurance.} <Enter Text Here> Unit Test (Reference Scope of Work SD-23, SD-24, SD-25) {Describe the Offeror’s approach for evaluating plans, requirements, environment, tools, procedure for unit testing system modules, level of test automation, interactive testing, and interactive debugging in test environment.} <Enter Text Here> {Describe the Offeror’s approach for verifying an appropriate level of test covering is achieved by the test process.} <Enter Text Here> System and Acceptance Testing System Integration Test (Reference Scope of Work ST-1, ST-2, ST-3, ST-4) {Describe the Offeror’s approach for evaluating the plans, requirements, environment, tools, and procedures for system module integration testing and the level of automation and availability of the system test environment. Approach shall include plan for staff to be on-site for all UAT. Please describe Offeror’s approach to monitoring, documenting, and reporting on tester issues.} <Enter Text Here> {Describe the Offeror’s approach for evaluating the plans, requirements, environment, tools, and procedures for system module integration testing and the level of automation and availability of the system test environment.} <Enter Text Here> {Describe the Offeror’s approach to verifying the test process, tests results are verified, correct configuration code has been tested, tests are appropriately documented, and test organization has an appropriate level of independence from the development organization.} <Enter Text Here> Pilot Test (Reference Scope of Work ST-5, ST-6, ST-7, ST-8, ST-9) {Describe the Offeror’s approach for evaluating pilot testing for the system and for verifying that a sufficient number and type of case scenarios are used to ensure comprehensive but manageable testing and tests are run in a realistic, real-time environment.} <Enter Text Here> {Describe the Offeror’s approach for evaluating and verifying test scripts are complete, test results verified, correct code configuration has been used, test runs are documented, and the test organization has appropriate level of independence from the development organization.} <Enter Text Here> Interface Testing (Reference Scope of Work ST-10) {Describe the Offeror’s approach for evaluating interface testing plans and procedures for compliance with industry standards.} <Enter Text Here> Acceptance and Turnover (Reference Scope of Work ST-11, ST-12, ST-13, ST-14, ST-15, ST-16) {Describe the Offeror’s approach for defining, reviewing, and approving acceptance procedures prior to testing and documenting test results.} <Enter Text Here> {Describe the Offeror’s approach for verifying that appropriate acceptance testing is based on the defined acceptance criteria and is performed satisfactorily before acceptance of software products, and the acceptance test organization has an appropriate level of independence from the development program.} <Enter Text Here> {Describe the Offeror’s approach for verifying that training on contractor-supplied software is ongoing through the development process.} <Enter Text Here> {Describe the Offeror’s approach in reviewing and evaluating the Implementation Plan} <Enter Text Here> {Describe the Offeror’s approach to evaluating the thoroughness of User Acceptance Plans and execution testing.} <Enter Text Here> Data Management Data Cleansing (Reference Scope of Work DM-1, DM-2, DM-3, DM-4, DM-5, DM-6, DM-7) {Describe the Offeror’s approach for verifying procedures in place are being followed to review the cleansed data and the SI’s Data Migration and Conversion plan includes adequate procedures for cleansing, transferring, validating, and synchronizing data through the entire process.} <Enter Text Here> {Describe the Offeror’s approach for collaborating with the State’s Quality Enhancement Unit, providing upfront and ongoing evaluation of existing Data Cleansing Plan and strategies in place.} <Enter Text Here> {Describe the Offeror’s approach to verifying the data cleansing tools, processes, resources, and automation procedures are in place, that data sources are confirmed and analyzed, strategies are in place that follow agencies administrative rules, and evaluating the data archival strategy.} <Enter Text Here>

Data Integration (Reference Scope of Work DM-8, DM-9, DM-10, DM-11, DM-12, DM-13, DM-14, DM-15) {Describe the Offeror’s approach to evaluating the Data Integration Plan, verifying a complete Risk Management strategy and Data Integration Plan is being implemented accurately, and risks are actively managed.} <Enter Text Here> {Describe the Offeror’s approach to evaluating the Data Security strategies in place during all stages of Data Integration.} <Enter Text Here> {Describe the Offeror’s approach to evaluating the strategies and processes in place for testing the systems thoroughly before implementation to verify that Data Quality rules and Data Mappings have been implemented correctly.} <Enter Text Here> {Describe the Offeror’s approach to periodically verifying the data migration process. What methods of validation in addition to inspections, walkthroughs, and checks of documentation and code and cleansing progresses would the Offeror recommend?} <Enter Text Here> {Describe the Offeror’s approach to verifying data integration includes and supports data sharing as per CMS Final Rule 1355.52} <Enter Text Here> {Describe the Offeror’s approach to evaluating the Data Backup Plan and verifying it has been executed successfully with controls in place to validate periodic data backup, and the Data Recovery Plan recovery procedures are clearly stated, and plan is tested on a periodic basis.} <Enter Text Here> Data Quality (Reference Scope of Work DM-16, DM-17) {Describe the Offeror’s approach for conducting a biannual rigorous evaluation of data quality and verifying proper staging of data during conversion and migration to ensure data integrity and to support data quality operations.} <Enter Text Here> Data Conversion (Reference Scope of Work DM-18, DM-19, DM-20, DM-21) {Describe the Offeror’s approach to evaluating the SI’s existing and proposed plans, procedures, and software for data conversion and determining conversion error rates and error rates meet SI Team and State criteria.} <Enter Text Here> {Describe the Offeror’s approach to evaluating the existing conversion process in place and making recommendations on improving conversion process efficiency and maintaining data integrity during conversion.} <Enter Text Here> {Describe the Offeror’s approach to analyzing data conversion results documentation.} <Enter Text Here> Database Design (Reference Scope of Work DM-22, DM-23, DM-24, DM-25) {Describe the Offeror’s approach to evaluating new and existing database designs against meeting existing and proposed system requirements and recommending improvements to database designs.} <Enter Text Here> {Describe the Offeror’s approach to evaluating the database design for factors affecting performance and data integrity.} <Enter Text Here> {Describe the Offeror’s approach to evaluating the project’s process for administering the database.} <Enter Text Here> System Integration System Integration (Reference Scope of Work SI-01, SI-02, SI-03) {Describe the Offeror’s approach to reviewing and evaluating the system’s capability to interface with internal and other external systems as per the DCFS Intergovernmental Agreements (IGA) and information data sharing policy.} <Enter Text Here> {Describe the Offeror’s approach to identifying issues or flaws with interfaces between each CCWIS component or between CCWIS components and external systems that may impact CCWIS Certification and providing recommendations to eliminate or mitigate flaws or issues.} <Enter Text Here> {Describe the Offeror’s approach to evaluating integration quality, including controls in place to identify potential failures and response procedures for failures identified.} <Enter Text Here> Maintenance and Operations (M&O) Oversight Operational Change Tracking (Reference Scope of Work MO-01, MO-02, MO-03) {Describe the Offeror’s approach to evaluating the M&O Plan taking into account future operational and maintenance needs.} <Enter Text Here> {Describe the Offeror’s approach to evaluating the statewide Solution’s change request and defect tracking processes.} <Enter Text Here> {Describe the Offeror’s approach to evaluating implementation of process activities and request volumes to verify processes are effective and being followed.} <Enter Text Here>

Operational Goals (Reference Scope of Work MO-04) {Describe the Offeror’s approach to evaluating the impact of each release and the Solution as a whole after implementation on program goals and performance standards for meeting CCWIS Compliance.} <Enter Text Here> Release Management (Reference Scope of Work MO-05) {Describe the Offeror’s approach to verifying adherence to methodology for releases from development through user acceptance testing to ensure adequate governance throughout the process.} <Enter Text Here> Operational Transition (Reference Scope of Work MO-06) {Describe the Offeror’s approach for verifying that plans, processes, and procedures for the transition of new systems from project mode into maintenance and operations are adequate and effective, taking into account the strengths and weaknesses of the business environment in terms of its capacity to absorb the change with minimal disruptions to operations.} <Enter Text Here> Operational Documentation (Reference Scope of Work MO-07) {Describe the Offeror’s approach for verifying all operational documentation is available to stakeholders.} <Enter Text Here> Operational Processes and Activity (Reference Scope of Work MO-08, MO-09, MO-10) {Describe the Offeror’s approach for evaluating implementation of process activities including backup, disaster recovery, and day-to-day operations and that they are being followed.} <Enter Text Here> {Describe the Offeror’s approach for conducting Payment Error Rate Measurement (PERM) eligibility reviews.} System Performance and Capacity Analysis System Performance and Capacity (Reference Scope of Work SPCA-01, SPCA-02, SPCA-03, SPCA-04) {Describe the Offeror’s approach for reviewing and cataloging relevant components of the State’s current system architecture.} <Enter Text Here> {Describe the Offeror’s approach to conducting an initial ((prior to implementation) review of the SI’s proposal and conducting interviews with the SI, as well as annual and ongoing, end-to-end evaluation of the entire plan and system to identify initial opportunities to optimize TCO and ROI. Also, describe the Offeror’s experience and provide a sample Optimization Analysis Report (In Packet 2) that includes but is not limited to TCO and ROI.} <Enter Text Here> {Describe the Offeror’s approach to making recommendations annually on changes in processing hardware, storage, network systems, operating systems, COTS software, and software design to meet future growth and improve system performance.} <Enter Text Here> IT Audit IT Audit (Reference Scope of Work ITA-1, ITA-2) {Describe the Offeror’s approach, methodologies, and tools for conducting IT Audit Review, including coordination, conducting a risk evaluation, establishing a control environment, developing objectives and procedures, and documenting all steps, policies, and procedures.} <Enter Text Here> IT Audit (Reference Scope of Work ITA-3, ITA-5, ITA-6) {Describe the Offeror’s approach, methodologies, and tools for drafting IT Audit reports. Include relevant history and experience on projects of similar size, scope and complexity. Include experience with State and Federal projects, Federal certification and/or compliance. Specifically, detail experience with drafting Pre-implementation Audit Reports, conducting on-going Audit monitoring, and completing Post Implementation Audit Reports. Please include sample Pre-Implementation Report (In Packet 2). Sample can be redacted, or you may submit a template with all categories listed to satisfy this request.} <Enter Text Here> IT Audit (Reference Scope of Work ITA-4, ITA-7) {Describe the Offeror’s approach, methodology, and tools for providing technical IT Audit assistance and training to Chief Internal Auditor staff. Please describe all related experience. } <Enter Text Here>

IV&V EXPERIENCE

{Provide a description of projects of a similar size and scope, a detailed assessment of what the primary factors contributing to successful projects, as well as a detailed assessment of lessons learned and identified risk factors. Offeror should include their experience with project owner issues with subcontractors and, if applicable, how they have handled a subcontractor leaving a project. How will those lessons learned benefit this project and what is your approach to mitigate known and unknown risks?} <Enter Text Here> Federal Certification Experience {Describe the Offeror’s approach to assisting the Department in meeting federal CCWIS compliance for this project. Also, describe your experience in meeting SACWIS Federal Certification (legacy projects), and describe your experience with any federally-certified project. Specifically, please detail past projects that were successful in passing Federal certification and/or compliance, the Offeror’s role in the project, how the experience differs from this project, and lessons learned that would benefit the Illinois CCWIS Project. See attached background architecture for additional information.} <Enter Text Here> Oversight & Coordination {Describe the role of an IV&V Vendor (enhanced IV&V as described in the RFP); working with State staff, other vendors, and subcontractors to integrate large scale comprehensive solutions.} <Enter Text Here> Oversight & Coordination Processes {Describe processes and methods that the Offeror intends to use to ensure communications, coordination, and project reporting are optimized for overall project success. Describe processes and methods that the Offeror intends to use to effectively coordinate efforts between internal and external stakeholders.} <Enter Text Here> Vendor Coordination {Describe the approach that the Offeror intends to use to coordinate efforts with Offeror’s subcontractors, the System Integrator, the OCM/BPR Vendor, and the Program Management Vendor. Specifically address approach to working independently and operating in an oversight capacity while holding a Contract directly with the project owner.} <Enter Text Here>

Commitment to diversity Assistance {Describe your efforts to assist businesses owned by women, minorities, or persons with disabilities. Identify who was assisted and the nature of the assistance. Please provided any relevant documentation to substantiate claims of assistance. Assistance may include obtaining lines of credit, insurance, necessary equipment, supplies, materials, or related assistance or services within the past 5 years. Please list all that apply.} <Enter Text Here> Spend {Identify the percentage of spend involving businesses owned by women minorities, or persons with disabilities, and provide the nature of the involvement. Due to the pandemic, the Department request the last full uninterrupted fiscal year spend for this criteria. Please indicate the nature of the good or services provided by the minority firm and whether this was a one-time use or long-term partnership or commitment. Please document Offeror’s effort to increase spend and how this effort relates to Offeror’s overall diversity plan. Please provided any relevant documentation to substantiate claims of assistance.

The percentage of spend may include donations, direct purchases, subcontracting opportunities, indirect purchases, one-time or long-term partnerships, etc. Please list all that apply.} <Enter Text Here>

Plan {Please describe Offeror’s written supplier diversity program, including, but not limited to, use of diversity vendors in the supply chain and a training or mentoring program with businesses owned by women, minorities, or persons with disabilities. Please include any other diversity programs/efforts not listed above. Narrative should indicate applicable internal roles/units, staffing, and funding dedicated to all diversity efforts. Narrative should include plan’s goals, expected outcome(s), duration, success metrics, future goals, and any other information you would like considered for evaluation. Please include the plan’s genesis and evolution. If sharable, please submit a copy of Offeror’s supplier diversity program plan to enhance the evaluation committee’s review. (Packet 2)} <Enter Text Here> Staffing {Provide the percentage of governing board, senior executives, managers, and staff who are women, minorities, or persons with disabilities. For the purposes of this evaluation, Offerors may use the highest level of achievement during the preceding 24-month period.} <Enter Text Here>

STATE OF ILLINOIS

SECTION 2.B. IV&V APPROACH

State of Illinois Attachment A: IV&V Narrative 20

SECTION 3:

Methodologies, Deliverables &Tools ProGram Management Methodology {Describe the Program Management methodology the Offeror intends to use and how the methodology has proven successful on projects of a similar size, scope, and nature to the work required for this project. The description should address the following items: governance, alignment, assurance, management, integration, finances, infrastructure, planning, improvement, change and issue tracking and resolution, subcontractor management, and tool(s), software or services used to enhance project efficiency and the relationship with the Project Management Methodology} <Enter Text Here> Project Management Methodology {Describe the Project Management Methodology that the Offeror intends to use and how the methodology has proven successful on IV&V projects of a similar size, scope, and nature to the work required for this project. The description should address the four key project success factors: Planning – including all planning and forecasting activities; Processes - overall approach to all activities and specific project governance; People - Including dynamics of how individuals collaborate and communicate; Power - Lines of authority, decision-makers.} <Enter Text Here> Project Management Tools {Provide a list of project management tools the Offeror intends to use to execute its proposed Project Management Methodology and approach, including the IV&V Vendor developed checklist and Key Performance Indicator (KPI) Dashboard. The list should include the tool title, description of what the tool is used for and any benefits of the tool(s).} This list shall include the required vendor-created Dashboard checklist. Please include sample(s) Dashboard views and/or Checklist (In Packet 2).

<Enter Text Here> Communication Strategy {Describe the Offeror’s method for assessing risks, documenting issues, and communicating them to the State and Project Teams.} <Enter Text Here> Project Deliverables {Describe the Offeror’s review methods and how an outcome for a missed deliverable will be reported. Provide a list of Project Management deliverables and work products that Offeror intends to use and deliver to ensure a successful implementation of the Solution. The deliverables should support the Offeror’s approach and complement the Project Management Methodology. The list should include the deliverable/work product title, type of document (deliverable or work product), the frequency of the deliverable/work product, and a brief description of the document.} (RFP Section 1, Part E).

<Enter Text Here> Templates {As discussed in RFP Section 1, Part E.1, Identify additional deliverables and reports that may be required based on your experience and expertise. Provide templates for the named reports/deliverables and identify the assigned team member role / title responsible.} <Enter Text Here> Reports {Describe the Offeror’s experience with creating reports, the typical reports offeror has created, and the purpose, and outcome of the reports. Provide one or more sample report(s) (In Packet 2) on previous projects and describe below the value they provided. Examples may include, but are not limited to: cost optimization, performance, security, data management, reducing defects, increasing reliability, or uncovering high risks early in the development lifecycle, or reducing the need for reworking.} <Enter Text Here> C.2.5. Quality Assurance {Provide a sample QA report (In Packet 2) (may be redacted or template version) on previous projects and describe it below and the value it provided into determining any static errors, ensuring that the logic is implemented correctly, all the design/requirements are captured, and no unintended functionality is introduced in the code.} <Enter Text Here>

STATE OF ILLINOIS

Section 3.c. Methodologies, Deliverables & tools

State of Illinois Attachment A: IV&V Narrative 21

SECTION 4:

Proposed Project Staffing {Provide an organization chart, Offeror’s Key Personnel Roles List and Vendor’s Key Personnel Biographies, including all subcontractor’s Key Personnel and Biographies as instructed below.