ATTACHMENT 23- REQUEST FOR CHANGE FORM.pdf

PDF 140 KB Posted

Attached to
Cannabis Integration System (CSI) - DCC
Solicitation number
0000039409
Issued by
California

About this file

This document is a Request for Change (RFC) Form template for the Cannabis Systems Integration (CSI) Project, a state-level initiative involving system development and management. The form is designed to facilitate formal change requests throughout the project lifecycle, with structured sections for requestors to propose modifications to the system while establishing a clear approval and validation pathway. The RFC process requires initial submission by a requestor with general information including the change title, impact area classification (Licensing, Compliance, Cashiering, Technical, Interface, or Other), and detailed justification that includes current problems, expected benefits, potential workarounds, and alternative solutions. Subsequent validation stages involve Product Owner review, Technical Validation, State Project Management review, and an IT Governance Change Control (ITGC) review before final approval decisions are rendered.

The RFC form incorporates multiple approval layers and financial tracking mechanisms to ensure comprehensive evaluation of proposed changes. Following initial ITGC approval for impact analysis, a detailed Impact Analysis attachment (Attachment A) must be completed by the contractor, including technical impact assessments, implementation schedules, and cost estimates broken down by labor classifications such as Project Manager, Scrum Master, Business Analyst, Configuration Lead, and Technical Lead. The process culminates in RFC closeout procedures that verify baseline updates, schedule incorporation, and stakeholder sign-offs. The form structure supports both zero-cost actions and unanticipated tasks while requiring documentation of funding sources and approval authorities, ensuring that all system modifications are tracked, justified, and properly budgeted throughout the Cannabis Systems Integration Project's execution.

View the file

Other files

File Type Posted
ATTACHMENT 21- WORK ORDER AUTHORIZATION FORM.pdf PDF
ATTACHMENT 11- COMMERCIALLY USEFUL FUNCTION (CUF) CERTIFICATION.pdf PDF
ATTACHMENT 18- SOLUTION DEMONSTRATION.pdf PDF
ATTACHMENT 7- BIDDER DECLARATION GSPD 05-105.pdf PDF
ATTACHMENT 16.5- Business Analyst Lead - QUALIFICATIONS FORM.pdf PDF
ATTACHMENT 5- RESPONSE TO ADMINISTRATIVE REQUIREMENTS.pdf PDF
Exhibit_C_Cost_Workbook.xlsx XLSX spreadsheet
ATTACHMENT 22- KEY STAFF REPLACEMENT FORM.pdf PDF
ATTACHMENT 1- TEMPLATE FOR QUESTION SUBMITTAL.pdf PDF
Exhibit_A_Functional_Non-Functional_Requirements.xlsx XLSX spreadsheet
ATTACHMENT 19- CUS. REF. FOR PRODUCTIVE USE REQ. CERT..pdf PDF
EXHIBIT B- DELIVERABLES TABLE.pdf PDF
ATTACHMENT 17- NARRATIVE RESPONSE.pdf PDF
ATTACHMENT 10- DVBE DECLARATIONS.pdf PDF
EXHIBIT E- SECURITY AND DATA PROTECTION.pdf PDF
ATTACHMENT 16.3- Scrum Master - QUALIFICATIONS FORM.pdf PDF
ATTACHMENT 8- WORKERS_ COMPENSATION CERTIFICATION.pdf PDF
ATTACHMENT 16.10- Technical Architect Lead - REFERENCE FORM.pdf PDF
ATTACHMENT 16.9- Technical Architect Lead - QUALIFICATIONS FORM.pdf PDF
ATTACHMENT 6- CONFIDENTIALITY STATEMENT.pdf PDF
EXHIBIT D- IT - GP CLOUD - DGS PD 402-ITGP (Cloud).pdf PDF
ATTACHMENT 25- APPENDIX A - STATEMENT OF WORK.pdf PDF
ATTACHMENT 16.8- Configuration Lead - REFERENCE FORM.pdf PDF
ATTACHMENT 14- BIDDER QUALIFICATIONS FORM.pdf PDF
ATTACHMENT 16.6- Business Analyst Lead - REFERENCE FORM.pdf PDF
ATTACHMENT 16.2- Project Manager - REFERENCE FORM.pdf PDF
ATTACHMENT 13- BIDDER QUALIFICATIONS FORM - INSTRUCTIONS.pdf PDF
ATTACHMENT 16- KEY STAFF QUALIFICATIONS FORM _ INSTRUCTIONS.pdf PDF
ATTACHMENT 16.4- Scrum Master - REFERENCE FORM.pdf PDF
ATTACHMENT 3- FOLLOW-ON CONTRACT DISCLOSURE FORM.pdf PDF
ATTACHMENT 2- INTENT TO BID.pdf PDF
ATTACHMENT 16.1- Project Manager - QUALIFICATIONS FORM.pdf PDF
ATTACHMENT 9- BIDDING PREFERENCES AND INCENTIVES.pdf PDF
EXHIBIT A- FUNCTIONAL AND NON-FUNCTIONAL R.pdf PDF
ATTACHMENT 20- DELIVERABLE EXPECTATION DOCUMENT (DED).pdf PDF
ATTACHMENT 12- TACPA PREFERENCE REQUEST FORMS.pdf PDF
CDT_OSTP_Request_For_Proposal.pdf PDF
ATTACHMENT 4- COVER LETTER FORM.pdf PDF
EXHIBIT C- COST WORKSHEETS.pdf PDF
ATTACHMENT 15- BIDDER REFERENCE FORM.pdf PDF
ATTACHMENT 16.7- Configuration Lead - QUALIFICATIONS FORM.pdf PDF
ATTACHMENT 24- GLOSSARY OF TERMS.pdf PDF
DCC_-_Cannabis_Integration_System_CSI.pdf PDF
Show all 43

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

ATTACHMENT 23: REQUEST FOR CHANGE FORM

Request for Change (RFC) Form

Cannabis Systems Integration (CSI) Project

REQUEST FOR CHANGE (RFC) FORM

Change Request Title:

Change Request Number:

SECTION 1: GENERAL INFORMATION

[To be completed by the Requestor]

Date Submitted:

Requestor Name:

Organization:

Email Address:

Phone Number:

General Impact Area (Choose Best One) ☐ Licensing ☐ Compliance ☐ Cashiering Technical ☐ Interface ☐ Other (explain):

Is this RFC being generated from a JIRA Issue# or ServiceNow Ticket#?

☐ JIRA Issue ☐ ServiceNow ISSUE/TICKET #:

Request Information Proposed Change: (Explain the change requested and include a succinct requirement statement for the change.)

Is this feature or functionality currently available in the Acella systems?

☐ Yes ☐ No

Current Problem: (Explain the current situation that has brought about the need for a change)

Expected Benefits/Justification: (Describe benefits in terms of amount of work saved, or costs or delays avoided.)

Impact if Request is denied:

Workarounds: (If the change is not implemented, is there any workarounds available?)

A workaround using legacy and manual systems is possible but would create workflow and staffing issues.

Alternative Solutions: (Different ways to implement the proposed change.)

Description Advantages Disadvantages 1 • •

2 •

Deputy Director Approval:

Signature

Date

Printed Name:

If attachments are included as part of Section 1, then indicate filename(s).

SECTION 2: PO VALIDATION

[To be completed by Project Management]

Product OwnerValidation:

Comments: (List assumed impacts if approved/denied, and recommendation to approve/deny; document impacted baselines below)

If denied:

Knowledge Transfer (KT) Required? ☐ YES ☐ NO Data Conversion Required? ☐ YES ☐ NO Divisions Impacted:

Product Owner Name (Please Print):

Signature: Date:

Technical Validation:

Comments: (List assumed impacts if approved/denied, and recommendation to approve/ deny; document impacted baselines below)

Signature:

Date:

State PM Review:

Baselines Impacted: (List approved baseline(s) by Release impacted by change.)

Project Requirements

Recommend for Impact Analysis? ☐ Yes ☐ No

Comments: (List comments in addition to above.)

Signature:

Date:

SECTION 3: ITGC REVIEW

[To be completed by the Change Control Manager/Project Director/ITCG Chair]

Impact Analysis Approval

Approved for Impact Analysis (IA)? ☐ Yes ☐ No If “yes” – IA due back to ITGC by:

Approval Assumptions: (List assumptions that, if true, constitute ITGC’s Approval of this

RFC.)

SECTION 4: RFC ACTION

[To be completed by the Change Control Manager/Project Director/ITGC Chair]

Approval Assumptions Met? ☐ Yes ☐ No ☐ N/A Issues or additional information requiring additional ITGC Action?

☐ Yes ☐ No

ITGC Action

Comments: (List additional approval/rejection details as appropriate. Please indicate selection of any alternative)

☐ Approve ☐ Reject Funding Source: ☐ Unanticipated Task; ☐ Zero Cost Action resulted from: ☐ Assumptions; ☐ ITGC Vote; ☐ PD Authority; ☐ Emergency

Approver Signature Date

Printed Name and Title

SECTION 5: RFC CLOSEOUT

[To be completed by the Change Control Manger/Project Director/Project Manager]

Have the impacted baselines been updated with the change and accepted? ☐ Yes ☐ No Comments:

CCM/PD/ PM Signature: Date:

Printed Name and Title:

Scheduler Verification (if needed)

Has Change been incorporated into Schedule? ☐ Yes ☐ No ☐ N/A

If Yes, which schedule?

Have appropriate milestones been shared with additional work plans? ☐ Yes ☐ No ☐ N/A

Scheduler Signature: Date:

Requestor Verification (if needed)

Requestor Signature: Date:

ATTACHMENT A: IMPACT ANALYSIS

[To be completed by the Contractor]

Impact Assessment Complete description of the work to be performed to implement the change:

Technical Impacts: (Architecture and Solution Software impacted by the change)

Schedule for the work to be performed, including any impacts to phase or release milestones:

Chargeable Hours Estimate: (Use Hours and Classifications from Contract Cost Worksheet) Hours Classification Rate per Hour Total Cost

Project Manager $

Scrum Master $ $ Business Analyst $ $ Configuration Lead $ $ Technical Lead $ $ Other $ $ Other $ $

Total Contractor Hours:

Final cost to implement change: $

Baselines impacted, needing revision, or new Deliverables to be produced:

Is an impact analysis alternative attached? ☐ Yes ☐ No If yes, how many? _ Impact Analysis Owner Approval:

Signature: Date:

ATTACHMENT 23: REQUEST FOR CHANGE FORM
Request for Change (RFC) Form

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