Appendix 8 - 2026 RFP Deliverabls - Addendum (1).docx
DOCX document 24 KB Posted
- Solicitation number
- BPM057747
- Issued by
- Baltimore County, Maryland
About this file
This file is an Appendix to a Request for Proposals (RFP) issued by the Department of General Services on behalf of the Maryland Lottery and Gaming Control Agency (MLGCA) for a comprehensive lottery central monitoring and control system. The RFP seeks a contractor to provide full installation, implementation, operation, maintenance, and related services for the system. The deliverables summary table outlines multiple required submissions across several categories including project management, operational procedures, security planning, and testing activities. Key deliverable due dates range from 30 days after the effective date for the Conversion Plan to 120 days after the Notice to Proceed (NTP) for Ticket Samples. Notable submissions include an Integrated Project Schedule due 45 business days after NTP with weekly updates, Standard Operating Procedures due 45 days prior to system start-up, a Disaster Recovery Plan due within 45 days of the effective date with annual updates thereafter, and a LCMCS Security Plan due no later than 90 days prior to start-up. Additional recurring deliverables include monthly preventative maintenance status reports due on the 5th of each month, weekly hotline call statistics, and annual penetration testing reports beginning 30 days after go-live.
The document establishes comprehensive quality and acceptance criteria that all deliverables must meet, including requirements for appropriate formatting, logical organization, factual accuracy, industry best practices compliance, and freedom from structural errors such as grammar and spelling mistakes. The Contract Monitor is responsible for reviewing final deliverables for compliance with specified acceptance criteria and may request draft versions prior to final submission. Contractors must subject all deliverables to internal quality-control processes before submission and are required to correct any deficiencies identified by the Contract Monitor within agreed-upon timeframes. Written deliverables must be compatible with Microsoft Office, Microsoft Project, PDF, or Microsoft Visio within two versions of the current software version. The document permits contractors to suggest additional subtasks, artifacts, or deliverables to enhance the quality and success of assigned tasks.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| BPM057747_LCMCS_2026_RFP v2.docx | DOCX document | |
| Appendix 4 - 2026 RFP Required Reports and Queries (1).docx | DOCX document | |
| Appendix 1 - 2026 RFP ABBREVIATIONS and DEFINITIONS (1) (1).docx | DOCX document | |
| Appendix 9. Electronic Transaction Fee.docx | DOCX document | |
| Appendix 10 - SAMPLE CONTRACT (1).pdf | ||
| Appendix 6 - RFP 2026 Liquidated Damages other than MBE (1).docx | DOCX document | |
| Appendix 3 - 2026 RFP Data Feeds – Types of Filed and Frequency of Uploads (1).docx | DOCX document | |
| Appendix 5 - 2026 RFP Information Technology - Addendum (1).docx | DOCX document | |
| Appendix 9 - 2026 RFP Monitors Deployed (1).docx | DOCX document | |
| Appendix 2 - BM057747 Price Form and Instructions.xlsx | XLSX spreadsheet | |
| Appendix 7 - 2026 RFP MBE Liquidated Damages (1).docx | DOCX document | |
| BPM057747 LCMCS 2026 RFP.docx | DOCX document | |
| BPM057747 LCMCS 2026 RFP.docx | DOCX document |
Show all 13
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
REQUEST FOR PROPOSALS (RFP) 2026-XX
LOTTERY CENTRAL MONITORING AND CONTROL SYSTEM AND RELATED SERVICES
Appendix 8
DELIVERABLES
Post Contract Award
1. Deliverable Submission
1. For every deliverable, the Contractor shall request the Contract Monitor confirm receipt of that deliverable by sending an e-mail identifying the deliverable name and date of receipt.
1. Unless specified otherwise, written deliverables shall be compatible with Microsoft Office, Microsoft Project, PDF or Microsoft Visio within two (2) versions of the current version. At the Contract Monitor’s discretion, the Contract Monitor may request one hard copy of a written deliverable.
1. For any written deliverable, the Contract Monitor may request a draft version of the deliverable, to comply with the minimum deliverable quality criteria listed in Section 3 Minimum Deliverable Quality.
2. Deliverable Acceptance
1. A final deliverable shall satisfy the scope and requirements of this RFP for that deliverable, including the quality and acceptance criteria for a final deliverable as defined in Section 4 Deliverable Descriptions/Acceptance Criteria.
1. The Contract Monitor shall review a final deliverable to determine compliance with the acceptance criteria as defined for that deliverable. The Contract Monitor is responsible for coordinating comments and input from various team members and stakeholders. The Contract Monitor is responsible for providing clear guidance and direction to the Contractor in the event of divergent feedback from various team members.
1. The Contract Monitor will issue to the Contractor a notice of acceptance or rejection of the deliverable in the DPAF (see online sample).
F. In the event of rejection, the Contract Monitor will formally communicate in writing any deliverable deficiencies or non-conformities to the Contractor, describing in those deficiencies what shall be corrected prior to acceptance of the deliverable in sufficient detail for the Contractor to address the deficiencies. The Contractor shall correct deficiencies and resubmit the corrected deliverable for acceptance within the agreed-upon time period for correction.
3. Minimum Deliverable Quality The Contractor shall subject each deliverable to its internal quality-control process prior to submitting the deliverable to the State.
Each deliverable shall meet the following minimum acceptance criteria:
1. Be presented in a format appropriate for the subject matter and depth of discussion.
1. Be organized in a manner that presents a logical flow of the deliverable’s content.
1. Represent factual information reasonably expected to have been known at the time of submittal.
1. In each section of the deliverable, include only information relevant to that section of the deliverable.
1. Contain content and presentation consistent with industry best practices in terms of deliverable completeness, clarity, and quality.
1. Meets the acceptance criteria applicable to that deliverable, including any State policies, functional or non-functional requirements, or industry standards.
1. Contains no structural errors such as poor grammar, misspellings or incorrect punctuation.
1. Must contain the date, author, and page numbers. When applicable for a deliverable, a revision table must be included.
1. A draft written deliverable may contain limited structural errors such as incorrect punctuation, and shall represent a significant level of completeness toward the associated final written deliverable. The draft written deliverable shall otherwise comply with minimum deliverable quality criteria above.
4. Deliverable Descriptions/Acceptance Criteria In addition to the items identified in the table below, the Contractor may suggest other subtasks, artifacts, or deliverables to improve the quality and success of the assigned tasks.
5. Deliverables Summary Table*
| Deliverable |
| Acceptance Criteria |
| Due Date / Frequency |
| Integrated Project Schedule |
| Microsoft Project schedule demonstrating tasks, task estimates, resource assignments, and dependencies for both Agency and Contractor Personnel, with tasks no less than 8 hours and no greater than 80 hours. |
| Initial Delivery: NTP+ 45 Business Days |
Updates: Weekly
| Standard Operating Procedures |
| The Contractor shall create and document the procedures for computer operations staff, especially regarding failure situations |
| 45 Days prior to Start-up Date |
| Disaster Recovery Plan |
| The Contractor shall develop a disaster recovery plan and submit it to MLGCA for approval. The Contractor shall maintain an up to date disaster recovery plan with annual updates |
| Within 45 Days of Effective Date |
| Preventative / Scheduled Maintenance Plan |
| The Contractor shall provide the MLGCA with monthly reports of the status of preventive maintenance as designed and requested by the MLGCA |
| Due: 5th of each month |
Frequency: Monthly
| Ticket Samples |
| The Contractor shall submit for approval by the MLGCA ten (10) Ticket samples of its Ticket stock for evaluation of anti-counterfeiting characteristics, graphics and durability |
| Within 120 days of NTP |
| Maintenance SOP – Retailer/Sales related equipment |
| The Contractor shall provide a detailed plan for establishing a field service schedule to maintain all Terminals, Monitors, and other Retailer location Hardware used for the sales, validations, and cashing of Tickets |
| 60 Days prior to Start-up Date |
| Field Asset Inventory List |
| The Contractor shall produce a detailed inventory of all existing and newly installed Hardware |
| Initial: 60 Days prior to Start-up Date; then |
Due: 5th of each month Frequency: monthly
| Hotline Support Report |
| The Contractor shall provide weekly Hotline call statistics |
| Due: Within 5 Days of the End of the Business Week |
Frequency: Weekly
| Customer Support Training Program |
| Provide a Hotline Quality Assurance and Training Program, which is subject to approval by the MLGCA |
| 60 Days prior to Start-up |
| Conversion Plan |
| The Contractor shall submit a detailed and final version of the Conversion Plan which, when approved by the MLGCA, shall become the basis for the Conversion. |
| Within 30 days of Effective Date |
| Data Conversion Plan |
| The Contractor shall provide the MLGCA with the plan for Conversion of all required data |
| Within 60 days of Effective Date |
| LCMCS Software SRS |
| Upon receiving MLGCA approval of its Business Requirements Documents, the Contractor shall develop corresponding Software Requirements Specification (“SRS”) documents |
| Within 45 days of approval of each Business Requirements Document |
| LCMCS Security Plan |
| The Contractor shall submit a detailed security plan to the MLGCA for approval |
| No Later than 90 Days prior to Start-up Date |
| Data Security Plan |
| The Contractor shall develop, document and implement a data security plan that is appropriate for the level of sensitivity/confidentiality of the information being processed |
| No Later than 90 Days prior to Start-up Date; then |
Due: on the anniversary date of the first Data Security Plan Frequency: Annually
| Penetration Test |
| The MLGCA requires external, independent penetration tests and security reviews to be conducted regularly. The Contractor shall provide for independent, professional and The Contractor shall provide for independent, professional and credible security firms offering such security and penetration testing services |
| No later than 30 days from go live date; then |
Due: on the anniversary date of the first Penetration Test Frequency: Annually
| Failover Report |
| A written report of failover testing shall be supplied to the Contract Manager |
| Due: Within 5 days of failover testing |
Frequency: As tests are conducted
| PEP |
| The Contractor shall provide the Problem Escalation Procedure |
| No later than 60 days after Contract award |
| Standard User Operating Procedures |
| User Manuals for all key functions, as agreed to by Contractor and the Agency |
| Completed no later than 90 days from Effective Date |
| Game and System Specifications |
| Specifications for all terminals, games, and processes. The list will be developed jointly by the Contractor and the Agency. |
| Completed no later than 120 prior to go-live date |
*The Deliverables Summary Table may not list every contractually-required deliverable. Offerors and Contractors should read the RFP thoroughly for all Contract requirements and deliverables.
File details come from the government source that posted it. Updated .