# DRAFT PROPOSAL — NRFP #56-26 ## ERP Solution and Implementation Services ### City of Prince Albert **Prepared by:** NimbleStride Inc. (operating as MGR Infotech) **Prepared for:** Sean Peterson, Cascadia Partners **Date:** September 9, 2026 **RFP Reference:** NRFP #56-26 --- > **HUMAN REVIEW REQUIRED BEFORE SUBMISSION — CRITICAL FLAGS** > > This draft contains multiple material gaps that must be resolved before this proposal can be submitted competitively or compliantly. Key issues: > > 1. **⚠️ CRITICAL GAP — ERP Solution:** NimbleStride Inc. / MGR Infotech does not appear to own or resell a SaaS ERP product. The solicitation requires a cloud-based (SaaS) ERP solution covering the City's core functional areas. A software publisher or implementation partner may bid, but *both the software and implementation services must be proposed together.* This proposal cannot proceed without identifying a specific SaaS ERP platform to be proposed. **This is the single most important gap to resolve.** > 2. **⚠️ CRITICAL GAP — Insurance:** The solicitation requires $5,000,000 CGL. NimbleStride currently carries $2,000,000. Coverage must be increased before submission or contract award. > 3. **⚠️ CRITICAL GAP — References:** Three client references for comparable ERP implementations at similar-sized municipalities within the last five years are required. None exist in the dossier. > 4. **⚠️ CRITICAL GAP — ERP Requirements Form:** Must be completed in the City's prescribed format. This draft cannot complete it. > 5. **⚠️ CRITICAL GAP — Pricing Form:** Must be completed separately. This draft cannot complete it. > 6. **WARNING — Business License:** A City of Prince Albert Business License is required before operations begin (confirmed at contract award). > 7. **WARNING — Personnel:** Named ERP-experienced project manager and implementation staff with Canadian municipal ERP experience must be identified. --- # 1. Cover Letter **[NOTE: This cover letter must NOT restrict the proposal in any way. Remove any qualifying or limiting language before submission. The signed Appendix A (Bid Form) serves as the formal cover page — this letter is supplementary context only.]** --- 1209 Waterford Dr Chestermere, AB T1X 3A1 support@nimblestride.ca +1 (613) 407-0895 Insert the actual calendar date on which the proposal package is finalized and submitted. **Attention:** Sean Peterson Cascadia Partners speterson@cascadiapartners.ca **Re: NRFP #56-26 — ERP Solution and Implementation Services, City of Prince Albert** Dear Mr. Peterson, NimbleStride Inc. (Alberta), operating as MGR Infotech in Saskatchewan, is pleased to submit this proposal in response to the City of Prince Albert's NRFP #56-26 for an ERP Solution and Implementation Services. NimbleStride Inc. is identified as the **prime contractor** and will hold sole contractual responsibility to the City for the performance of the entire engagement, including any work performed by partners, subcontractors, or other third parties. This submission consists of three components as required: - **(a)** This PDF document, including the completed and signed Appendix A (Bid Form / Cover Page) and narrative responses to Appendix B (Vendor Questions); - **(b)** The completed ERP Requirements Form in the City's prescribed format (submitted as a separate labelled file); and - **(c)** The ERP Pricing Form, submitted independently as a separate labelled file. All files are labelled with our legal company name, **NimbleStride Inc.**, and the RFP number **NRFP #56-26**. This proposal is open and irrevocable for 180 calendar days from the submission deadline, and all prices quoted are firm for that period. Yours sincerely, ___________________________ **Mohammed Yousuf Shariff** Principal & Authorized Signing Officer NimbleStride Inc. support@nimblestride.ca | +1 (613) 407-0895 --- # 2. Company Overview NimbleStride Inc. is an Alberta-incorporated company operating under the trade name MGR Infotech in Saskatchewan. Together, the two entities form a single integrated delivery organization serving public- and private-sector clients across Alberta, Saskatchewan, and Manitoba. **NimbleStride Inc.** focuses on custom software, AI, and web platform development. **MGR Infotech** delivers IT infrastructure, hardware supply, Microsoft services, and physical security systems. **Prime Contractor:** NimbleStride Inc. is the identified prime contractor for this engagement and will hold sole contractual responsibility to the City for all deliverables, including any work performed by subcontractors or partners. | Field | Detail | |---|---| | Legal Name | NimbleStride Inc. | | Operating Name | MGR Infotech (Saskatchewan) | | Registered Address | 1209 Waterford Dr, Chestermere, AB T1X 3A1 | | Primary Contact | Mohammed Yousuf Shariff | | Email | support@nimblestride.ca | | Phone | +1 (613) 407-0895 | | CRA Business Number | [PROVIDE: CRA Business Number] | | AB Corporate Registry # | [PROVIDE: Alberta Corporate Registry number] | | SK Business Registration # | [PROVIDE: Saskatchewan business registration number] | | WCB / Workers' Compensation | [PROVIDE: WCB account number(s) for AB and SK] | **Proposed ERP Platform:** [PROVIDE: Legal name of the SaaS ERP software vendor/platform being proposed (e.g., Tyler Technologies, Questica, Infor, Unit4, Dynamics 365, etc.). This is mandatory — the solicitation requires a named cloud-based SaaS solution. Confirm whether NimbleStride is acting as (a) the software publisher, (b) an authorized reseller/implementation partner, or (c) proposing a partnership with a named ERP vendor. Attach any partner authorization letter if applicable.] **Subcontractors / Partners:** [PROVIDE: List all subcontractors and partners, their legal names, roles in the engagement, and the nature of the contractual relationship with NimbleStride Inc. as prime. If the ERP software vendor is a separate entity, they must be named here.] --- # 3. Compliance Response ## 3.1 Proposal Structure & Submission Format **Requirement [p.4 / p.18 · format/submission]:** The submission must include three components: (a) a single PDF containing the completed and signed Appendix A and narrative responses to Appendix B; (b) a completed ERP Requirements Form in the City's prescribed format; (c) a separate ERP Pricing Form. All files must be clearly labelled with the Proponent's legal company name and NRFP #56-26. Individual email submissions must not exceed 50 MB. The proposal must not be restricted by any statement or covering letter. **How we comply:** NimbleStride Inc. will submit all three components as separate, clearly labelled files: - `NimbleStride_Inc_NRFP-56-26_Proposal.pdf` — containing signed Appendix A and Appendix B narrative responses; - `NimbleStride_Inc_NRFP-56-26_ERP_Requirements_Form.[format]` — completed in the City's prescribed format; - `NimbleStride_Inc_NRFP-56-26_Pricing_Form.[format]` — submitted independently. Total file size will be managed to remain within the 50 MB per-email limit. If the combined size approaches this limit, files will be split across multiple emails clearly labelled as Part 1 of N, Part 2 of N, etc., and submitted before the deadline. NimbleStride Inc. is prepared to submit via any method acceptable to the City of Prince Albert / Cascadia Partners. If the complete proposal package exceeds email size limits, we request confirmation that a secure file-transfer link (e.g., WeTransfer, SharePoint, or equivalent) will be accepted in lieu of or in addition to email submission. This proposal contains no restricting statements or qualifications in the covering letter or elsewhere. --- ## 3.2 Prime Contractor & Partnership Structure **Requirement [p.4 · other]:** One organization must be identified as the prime contractor and will hold sole contractual responsibility to the City for the entire engagement, including work by any partner, subcontractor, or third party. Proponents submitting with partners must clearly identify the prime and describe the contractual and working relationship. **How we comply:** **NimbleStride Inc.** is the prime contractor. NimbleStride Inc. will execute the contract with the City of Prince Albert and will be solely accountable for all deliverables, timelines, quality, and performance obligations, regardless of which subcontractors or partners contribute to delivery. [PROVIDE: Describe the specific contractual relationship between NimbleStride Inc. and any named ERP software vendor or implementation subcontractor — e.g., reseller agreement, teaming agreement, subcontract. Attach any partner authorization letter from the ERP software vendor confirming NimbleStride's authority to resell or implement their platform.] --- ## 3.3 Software Publisher / Implementation Partner Eligibility **Requirement [p.4 · other]:** Proposals may be submitted by a software publisher or a systems implementation partner, so long as the proposal covers both the software solution and implementation services. **How we comply:** NimbleStride Inc. is proposing as [PROVIDE: select one — (a) a software publisher proposing its own SaaS ERP platform; (b) an authorized implementation partner proposing a named third-party SaaS ERP platform; (c) a prime contractor teaming with a named ERP software vendor]. The proposal covers both the software solution ([PROVIDE: platform name]) and full implementation services delivered by NimbleStride Inc. as prime. --- ## 3.4 Cloud-Based (SaaS) Solution Requirement **Requirement [p.11 · other]:** The City requires a cloud-based (SaaS) solution. On-premise or self-hosted deployments will not be considered. The solution must cover the City's core functional areas, minimizing the number of separate systems and custom integrations. **How we comply:** The proposed solution, [PROVIDE: ERP platform name], is a cloud-hosted SaaS platform. [PROVIDE: Confirm the platform's SaaS architecture, hosting region (confirm Canadian data residency), and the core functional modules covered — e.g., Finance, HR/Payroll, Procurement, Asset Management, Permitting, etc. Confirm that the proposed scope covers all mandatory functional areas identified in the City's ERP Requirements Form without requiring significant custom integrations for day-to-day operations.] **⚠️ POTENTIAL GAP:** If NimbleStride does not have an existing SaaS ERP product or a formal partnership with one, this mandatory requirement cannot be met. Resolve before submission. --- ## 3.5 ERP Requirements Form — Mandatory Requirements **Requirement [p.14 · submission]:** Proposals are reviewed against mandatory requirements in the ERP Requirements Form. Proposals not meeting all mandatory requirements will not proceed to further evaluation. **How we comply:** NimbleStride Inc. will complete the ERP Requirements Form in the City's prescribed format, submitted as a separate labelled component of this bid package. [PROVIDE: Complete the City's ERP Requirements Form in full, responding to each mandatory and rated requirement. This document cannot be drafted here — it must be completed using the City's own form template against the capabilities of the specific ERP platform being proposed.] --- ## 3.6 Project Manager & Governance Structure **Requirement [p.13 · personnel]:** The Proponent must assign a dedicated project manager to lead planning, scheduling, and coordination across all phases, supported by a defined governance structure with clear escalation paths, regular status reporting, and risk and issue tracking. **How we comply:** Mohammed Yousuf Shariff (Principal, SAFe SPC 6, CSM, PRINCE2, ITIL; 17+ years enterprise delivery) will serve as Mohammed Yousuf Shariff will serve as the dedicated Project Manager for this engagement, providing direct, accountable leadership across all phases — discovery, configuration, data migration, testing, training, go-live, and stabilization — leveraging his SAFe SPC 6, CSM, and PRINCE2 credentials and 17+ years of enterprise program delivery experience.. A formal governance structure will be established at project initiation, including: - Defined escalation paths from delivery team → Project Manager → City Project Sponsor; - Weekly status reporting against the project schedule; - A risk and issue register maintained throughout the engagement; - Defined change-control process for scope changes. [PROVIDE: If a separate dedicated Project Manager (not Mr. Shariff) is to be named, provide their name, résumé, role, location, and relevant Canadian municipal ERP experience. The solicitation requires a *dedicated* PM — confirm whether Mr. Shariff can be dedicated to this role or whether an additional named resource is required.] --- ## 3.7 Data Migration Strategy **Requirement [p.13 · other]:** The Proponent must provide a data migration strategy covering data mapping, transformation, cleansing guidance, loading, and reconciliation, and a plan for validating migrated data prior to cutover. **How we comply:** [PROVIDE: A detailed data migration strategy must be developed in collaboration with the named ERP platform vendor and submitted as part of the Technical Approach (Section 4). At minimum, address: (a) data mapping from legacy systems to the new ERP; (b) transformation and cleansing rules; (c) migration tooling; (d) parallel-run or reconciliation approach; (e) go/no-go data validation criteria before cutover. This section cannot be completed without knowing the specific ERP platform and the City's current legacy systems.] --- ## 3.8 Go-Live Support & Stabilization **Requirement [p.13 · other]:** The Proponent must provide hands-on support during and immediately after go-live, including defined go/no-go criteria, issue triage and resolution, and a stabilization period to address defects before transitioning to standard support. **How we comply:** Following go-live, NimbleStride will provide a dedicated hypercare period of four (4) weeks during which the project team remains on-call (remote, with on-site availability upon request) to resolve issues in real time. Go/no-go criteria include: successful parallel-run reconciliation, completion of user-acceptance testing with sign-off, and zero open P1 defects. During hypercare, issues are classified as P1 (system down / critical business process blocked — 2-hour response, same-business-day resolution target), P2 (major function impaired — 4-hour response, 2-business-day resolution), and P3 (minor issue / workaround available — next-business-day response). Transition from hypercare to standard SLA-based support is triggered by 10 consecutive business days with no P1 or P2 incidents and formal written acceptance by the City's project sponsor. --- ## 3.9 Ongoing Support & SLA **Requirement [p.13 · other]:** Following stabilization, the Proponent or software vendor must provide ongoing support under a defined SLA covering defect resolution, system updates, and (for cloud-hosted solutions) hosting and infrastructure management. **How we comply:** Post-stabilization support is provided through a two-layer model: (1) the SaaS platform vendor's standard support agreement (including automatic updates, patch management, and platform SLAs) is assigned or passed through directly to the City; and (2) NimbleStride provides a managed application-support wrapper covering configuration changes, user queries, report development, and integration monitoring under a defined SLA — P1: 4-hour response / 1-business-day resolution; P2: 1-business-day response / 3-business-day resolution; P3: 3-business-day response / 10-business-day resolution. All hosting and infrastructure is managed by the SaaS vendor within Canadian data-residency boundaries; NimbleStride coordinates vendor escalations on the City's behalf. --- ## 3.10 Insurance **Requirement [p.17 · insurance]:** Comprehensive General Liability Insurance including Public Liability Insurance in a minimum amount of **$5,000,000**. **How we comply:** **⚠️ CRITICAL GAP.** NimbleStride Inc. currently carries Commercial General Liability (CGL) insurance with a limit of **$2,000,000 per occurrence**, which does not meet the $5,000,000 minimum required by this solicitation. [PROVIDE: Before submitting this proposal, obtain a CGL policy with a minimum $5,000,000 per-occurrence limit, or confirm with your broker whether an umbrella/excess liability policy can be layered to reach $5,000,000. Provide the insurer name, policy number, and certificate expiry date. A certificate of insurance naming the City of Prince Albert as an additional insured will be required prior to contract execution.] [CONFIRM: Whether E&O (Errors & Omissions) and Cyber Liability insurance are also required by this solicitation — review the full RFP and any addenda. Neither policy is currently in place.] --- ## 3.11 City of Prince Albert Business License **Requirement [p.17 · certification]:** All businesses operating or providing services within the corporate boundaries of the City of Prince Albert must have a valid City of Prince Albert Business License, issued before operations begin. This qualification will be confirmed at contract award, not at proposal stage. **How we comply:** NimbleStride Inc. acknowledges this requirement. A City of Prince Albert Business License will be obtained prior to commencement of any operations within the City's boundaries, as required. [PROVIDE: Confirm this commitment with the authorized signing officer and initiate the business license application upon notification of award.] --- ## 3.12 Legislative & Regulatory Compliance **Requirement [p.17 · certification]:** Must meet all legislated requirements for the Scope of Work (Occupational Health and Safety, Environment, etc.). **How we comply:** NimbleStride Inc. commits to complying with all applicable federal, provincial (Saskatchewan and Alberta), and municipal legislation relevant to the scope of this engagement, including but not limited to the Saskatchewan Occupational Health and Safety Act and applicable environmental regulations. [PROVIDE: Confirm WCB clearance certificates for Alberta and Saskatchewan are in good standing and can be provided upon request.] --- ## 3.13 Conflict of Interest Disclosure **Requirement [p.20 · submission]:** Each Proponent must disclose any circumstance giving rise to an actual, potential, or perceived conflict of interest in relation to this RFP or the resulting engagement. **How we comply:** NimbleStride Inc. and MGR Infotech confirm that, to the best of their knowledge, no actual, potential, or perceived conflict of interest exists with respect to NRFP #56-26. Neither entity, nor principal Mohammed Yousuf Shariff, holds a current employment, financial, or familial relationship with any employee of the City of Prince Albert or Cascadia Partners that could improperly influence the award or delivery of this contract. Should any conflict arise during the engagement, NimbleStride Inc. commits to disclosing it immediately in writing to the City's designated contract authority. NimbleStride Inc. and MGR Infotech confirm that, to the best of their knowledge, no actual, potential, or perceived conflict of interest exists with respect to this procurement. Neither entity, nor principal Mohammed Yousuf Shariff, holds a current employment, financial, or familial relationship with any employee or elected official of the City of Prince Albert that could improperly influence the award or delivery of this contract. Should any conflict arise during the engagement, NimbleStride Inc. commits to disclosing it immediately in writing to the City's designated Contract Authority and cooperating fully with any required mitigation measures. --- ## 3.14 Proposal Validity — 180-Day Irrevocability **Requirement [p.18 · submission]:** The Proposal shall be open and irrevocable for 180 calendar days from the Proposal closing time and date. Prices quoted are to remain firm for at least 180 days. **How we comply:** NimbleStride Inc. confirms that this proposal is open, irrevocable, and that all prices quoted in the ERP Pricing Form are firm for a minimum of 180 calendar days from September 9, 2026 at 2:00 PM CST. --- ## 3.15 Addenda Acknowledgement **Requirement [p.5 · submission]:** Any addendum issued will form part of this RFP. Proponents are responsible for accounting for its content in their submission. **How we comply:** NimbleStride Inc. has reviewed all addenda issued to date. [PROVIDE: List all addenda received and their dates, e.g., "Addendum No. 1 dated [date] — acknowledged." If no addenda have been issued, state: "No addenda have been issued as of the date of this submission."] --- ## 3.16 Pricing in Canadian Funds **Requirement [p.18 · financial]:** Pricing must be quoted in Canadian Funds. **How we comply:** All pricing submitted in the ERP Pricing Form is quoted in Canadian dollars (CAD), inclusive of applicable taxes as noted therein. --- ## 3.17 No Restrictions on Proposal **Requirement [p.18 · submission]:** The Proposal must not be restricted by any statement added or by a covering letter. **How we comply:** This proposal contains no restricting statements, qualifications, or conditions in the covering letter or elsewhere in the submission documents. --- ## 3.18 Bid Form (Appendix A) — Signed Cover Page **Requirement [p.18 / p.21 · submission]:** The Bid Form (Appendix A) must be completed, signed by an authorized officer, and included as the cover page of the PDF submission. It must be signed by an individual authorized to legally bind the Proponent. **How we comply:** Appendix A has been completed and signed by Mohammed Yousuf Shariff, Principal and authorized signing officer of NimbleStride Inc., and is included as the cover page of the PDF proposal document. [PROVIDE: Ensure Appendix A is fully completed with all fields — legal name, address, contact information, authorized signature, and any other fields required by the City's form. Wet or electronic signature as accepted by the City.] --- # 4. Technical Approach > **Note:** The technical approach below is structured as an outline. Each section requires substantive content that depends on the specific ERP platform being proposed and the City's detailed requirements. All sections marked [PROVIDE] must be completed before submission. ## 4.1 Understanding of Requirements NimbleStride Inc. understands that the City of Prince Albert (population ~37,000) is seeking to replace or significantly modernize its current ERP environment to consolidate fragmented systems and improve operational efficiency across core municipal functions including Finance, HR/Payroll, Procurement, Asset Management, Permitting/Licensing, and Utility Billing. The City's objectives — as understood from the NRFP — include reducing manual processes and data silos, improving reporting and decision-support, enabling self-service for staff and citizens, and ensuring a scalable, supportable platform for the long term. The initial implementation scope covers the core functional modules identified in the City's ERP Requirements Form, with additional modules (e.g., Permitting, GIS integration) treated as optional or future-phase deliverables consistent with the City's phasing preferences. ## 4.2 Proposed ERP Solution Overview [PROVIDE: Name and describe the proposed SaaS ERP platform. Include: (a) vendor name and platform name; (b) SaaS architecture overview; (c) Canadian data residency confirmation (hosting region); (d) core modules included in the proposed scope; (e) how the solution minimizes separate systems and custom integrations; (f) platform's track record with Canadian municipalities of similar size to Prince Albert (population ~37,000).] ## 4.3 Functional Coverage — Core Areas [PROVIDE: For each mandatory functional area identified in the City's ERP Requirements Form, describe how the proposed platform meets the requirement natively (out-of-the-box), through configuration, or through a supported integration. Flag any gaps. This section should align directly with the ERP Requirements Form responses.] **Indicative functional areas to address (confirm against the City's actual requirements):** - Financial Management (GL, AP, AR, Budgeting, Reporting) - Human Resources & Payroll - Procurement & Contract Management - Asset Management - [PROVIDE: additional modules identified in the RFP] ## 4.4 Implementation Methodology NimbleStride Inc. proposes a structured, five-phase implementation approach: (1) Discovery & Planning — stakeholder workshops, current-state process mapping, requirements validation, data-audit, and finalization of the project charter and detailed work plan; (2) Configuration & Development — platform configuration by module, integration build, and iterative review sessions with City subject-matter experts; (3) Data Migration — data cleansing, mapping, migration scripting, and parallel-run validation to ensure data integrity at go-live; (4) Testing & Training — system integration testing (SIT), user acceptance testing (UAT) with City staff, defect remediation, and role-based end-user training delivered in-person and via recorded materials; (5) Go-Live & Stabilization — cutover execution, hypercare support for 60–90 days post-go-live, knowledge transfer, and transition to steady-state support. Each phase concludes with a formal sign-off milestone before the next phase begins. ### 4.4.1 Project Phases & Timeline [PROVIDE: High-level project plan with phases (e.g., Discovery/Planning → Configuration → Data Migration → Testing → Training → Go-Live → Stabilization), estimated duration per phase, and proposed go-live date. Include a Gantt chart or milestone table.] ### 4.4.2 Agile / Iterative Delivery Approach NimbleStride Inc. delivers using an Agile/SAFe-aligned iterative approach led by a SAFe Program Consultant (SPC 6), Certified Scrum Master, and PRINCE2 Practitioner with 17+ years of enterprise delivery. Work is broken into short increments with working demonstrations each cycle, a clear Definition of Done, quality gates, and transparent flow metrics, providing the City with honest visibility into progress and risks throughout. NimbleStride Inc. applies Agile principles within a structured ERP delivery framework, led by Mohammed Yousuf Shariff (SAFe SPC 6, CSM, PRINCE2). Configuration and testing work is organized into two-week sprints, each producing a demonstrable, tested increment of configured functionality reviewed by City subject-matter experts at a sprint review. City staff are embedded as product owners for each functional area (Finance, HR, etc.), ensuring requirements are validated continuously rather than at the end. A Definition of Done for each sprint requires: configuration complete, unit-tested, integrated with adjacent modules, and signed off by the City SME. Change requests are managed through a lightweight change-control board meeting bi-weekly, keeping scope, schedule, and budget transparent throughout. Training materials are developed iteratively alongside configuration so that end-user readiness keeps pace with system readiness. ### 4.4.3 Governance Structure The proposed governance model includes: (a) Steering Committee — City CAO or designate, City CFO, and NimbleStride Principal (Mohammed Yousuf Shariff), meeting monthly to review progress, resolve escalations, and approve scope changes; (b) Project Management — NimbleStride Project Manager (Mohammed Yousuf Shariff / named associate) and City-side Project Coordinator meet weekly; (c) City-Side Responsibilities — designated SMEs per functional area, timely UAT participation, data-cleansing ownership, and IT environment access; (d) Escalation Path — operational issues resolved at PM level within 5 business days; unresolved issues escalated to Steering Committee within 10 business days; (e) Status Reporting — bi-weekly written status report covering RAG status, milestone progress, risks/issues log, and budget burn; (f) Change Control — all scope changes documented on a Change Request form, impact-assessed, and approved by both the City Project Coordinator and NimbleStride PM before work proceeds; (g) Risk & Issue Management — a live RAID log (Risks, Assumptions, Issues, Decisions) maintained by the NimbleStride PM and reviewed at every weekly meeting. ## 4.5 Data Migration Strategy Needs_input note: A credible ERP data migration strategy requires knowing the specific ERP platform being proposed and the City's current source systems (e.g., legacy finance, HR, payroll, utility billing). However, a framework answer is provided below as a starting point. Our data migration strategy follows five phases: (1) Discovery & Inventory — catalogue all source systems, data entities, volumes, and data-quality issues in collaboration with City staff; (2) Data Mapping & Cleansing — map source fields to target ERP schema, define transformation rules, and cleanse/de-duplicate records before migration; (3) Migration Tooling & Trial Runs — use the ERP vendor's native migration utilities or ETL tooling (e.g., Azure Data Factory or equivalent) to execute at least two full trial migrations in a non-production environment, validating record counts and business rules; (4) Parallel Validation — City staff reconcile migrated data against source-system reports for key entities (chart of accounts, vendor master, employee records, open transactions) before cutover approval; (5) Cutover & Freeze — a defined data-freeze window is agreed with the City, final delta migration is executed, and a signed data-acceptance sign-off is obtained before go-live. All migration scripts and mapping documentation are delivered as project artifacts. - **Data Discovery & Inventory:** Identification of all data sources in the City's current systems - **Data Mapping:** Mapping legacy data fields to the new ERP data model - **Data Cleansing:** Rules and guidance for identifying and resolving data quality issues - **Transformation:** ETL (Extract, Transform, Load) approach and tooling - **Migration Runs:** Approach to trial migrations and reconciliation - **Validation:** Criteria and process for validating migrated data prior to cutover - **Cutover Plan:** Final migration steps and rollback plan if validation fails ## 4.6 Testing Strategy NimbleStride Inc. builds quality in, not bolted on: automated unit and integration tests, security testing, accessibility testing, and structured user-acceptance testing (UAT) with real end users. Each increment must meet an explicit Definition of Done and pass defined quality gates before it is considered complete. Our ERP testing approach is structured across four layers: (1) Configuration Testing — each configured module (GL, AP, AR, Payroll, HR, etc.) is tested against documented business rules immediately after configuration, with defects logged and resolved before progressing; (2) Integration Testing — all interfaces between the ERP and external systems (banking, GIS, utility billing, reporting) are tested end-to-end using realistic data volumes, with pass/fail criteria defined in an Integration Test Plan; (3) User Acceptance Testing (UAT) — City staff execute scripted test scenarios mapped to their day-to-day processes across all in-scope modules; a UAT coordinator from our team supports City testers, tracks defects in a shared register, and obtains formal sign-off before go-live; (4) Performance Testing — load and stress tests are run against the hosted environment to confirm response times meet agreed SLAs under peak concurrent-user conditions; (5) Regression Testing for Updates — a regression test suite is maintained and executed against each vendor patch or upgrade in a staging environment before promotion to production, protecting configuration and integrations from unintended changes. ## 4.7 Training Strategy Our training approach covers six elements: (a) Training Needs Assessment — at project outset we conduct a structured TNA with department leads to identify user roles, current skill levels, and module-specific learning objectives; (b) Role-Based Curriculum — training is organized by role (e.g., Finance Clerk, Payroll Administrator, Department Manager, System Administrator) so each group receives only the content relevant to their daily tasks, reducing time away from operations; (c) Delivery Format — we offer a blended model: live instructor-led sessions (virtual or on-site in Prince Albert, per City preference) for initial training, supplemented by recorded walkthroughs hosted on a shared drive or LMS for ongoing reference; (d) Training Materials — we deliver quick-reference cards, step-by-step process guides, and annotated screenshots for each role; all materials are provided in editable formats so the City can update them after future upgrades; (e) Train-the-Trainer — we identify and train a small cohort of City 'super users' who receive deeper system knowledge and can support colleagues post-go-live, reducing dependency on the implementation team; (f) Post-Go-Live Refresher Training — scheduled refresher sessions at 30 and 90 days post-go-live address questions arising from live use, and additional sessions are provided when major vendor updates are applied. ## 4.8 Go-Live & Hypercare Support Our go-live approach uses a phased cutover model: (1) Go/No-Go Criteria — a formal checklist (UAT sign-off, data migration validation, integration smoke tests, training completion, support model activated) must be satisfied before cutover is authorized; (2) Cutover Plan — a detailed, hour-by-hour cutover runbook is prepared and rehearsed in a dress-rehearsal run at least two weeks before go-live, identifying rollback triggers and responsible owners; (3) Cutover Window — the production cutover is scheduled during a low-activity period (e.g., after month-end close) to minimize operational disruption; (4) Hypercare Period — the implementation team provides on-site or dedicated remote support for a minimum of 10 business days post-go-live, with same-day response to critical issues; (5) Rollback Plan — a documented rollback procedure is maintained so that, if critical issues arise during cutover, the City can revert to legacy systems with minimal data loss; (6) Stakeholder Communication — a go-live communication plan notifies all affected City staff and external parties (e.g., banking partners) of the transition timeline and support contacts. - Go/no-go criteria and decision-making process - Cutover plan and timeline - Hypercare/stabilization period duration and staffing - Issue triage and severity classification during hypercare - Transition criteria from hypercare to standard support ## 4.9 Ongoing Support Model Post-stabilization support is structured across three tiers: (1) Stabilization Support (Days 1–60 post-go-live) — dedicated hypercare support with defined SLAs: Critical (system down) — 2-hour response, 4-hour resolution target; High (major function impaired) — 4-hour response; Medium/Low — next business day; (2) Ongoing Managed Support — after stabilization, a retainer-based support model provides a defined number of monthly support hours for break-fix, configuration adjustments, user queries, and minor enhancements, with unused hours rolling forward or reconciled quarterly; (3) Vendor Patch & Upgrade Management — our team coordinates with the ERP vendor on scheduled releases, executes regression testing in staging, and promotes approved updates to production with City sign-off; (4) Escalation Path — issues beyond our resolution scope are escalated directly to the ERP vendor's support tier under the City's software maintenance agreement, with our team acting as the City's advocate; (5) Knowledge Transfer — all support runbooks, configuration documentation, and known-issue logs are maintained in a shared repository accessible to City IT staff, supporting eventual in-house capability. [PROVIDE: confirm the City's preferred support-hours window (e.g., 8 a.m.–5 p.m. CST, Monday–Friday) and whether after-hours on-call coverage is required, so SLA commitments can be priced accurately.] - Support channels (phone, email, portal) - SLA tiers — response and resolution times by severity (P1/P2/P3/P4) - Defect resolution process - System update and patch management - Hosting and infrastructure management (SaaS vendor responsibility) - Escalation to ERP software vendor if applicable ## 4.10 Accessibility All user-facing interfaces are designed and tested to meet WCAG 2.1 AA, including keyboard navigation, screen-reader compatibility, sufficient colour contrast, and responsive layouts. Accessibility is validated through automated tooling and manual testing as part of the Definition of Done. [PROVIDE: Confirm the proposed ERP platform's WCAG 2.1 AA compliance status and any accessibility audit reports available from the software vendor.] ## 4.11 Data Security & Residency All data will be hosted and processed in Canada on Canadian-region cloud infrastructure. Data is encrypted at rest (AES-256) and in transit (TLS 1.2+), with role-based least-privilege access and full audit logging. In-Canada data residency is standard practice; NimbleStride can guarantee in-Canada storage and processing, with no data subject to foreign extraterritorial claims. [PROVIDE: Confirm the specific hosting region for the proposed ERP SaaS platform (must be Canadian). Confirm the software vendor's SOC 2 Type II or equivalent certification. Address any Protected A/B data handling requirements identified in the RFP.] ## 4.12 Integration Architecture [PROVIDE: Identify all integrations required between the proposed ERP and the City's existing systems (e.g., banking, GIS, permitting, utility billing, reporting tools). Describe the integration approach (APIs, middleware, native connectors) and how the solution minimizes custom integration requirements.] --- # 5. Key Personnel > **⚠️ NOTE:** The solicitation requires résumés for **all** proposed personnel, including subcontractors, identifying each person's role, location, and relevant **Canadian municipal ERP experience** [p.22]. The dossier provides information on one individual only. All additional personnel must be identified and their résumés provided. ## 5.1 Mohammed Yousuf Shariff — Principal & Delivery Lead Mohammed Yousuf Shariff serves as Principal and Delivery Lead for NimbleStride Inc. and MGR Infotech. He brings 17+ years of experience spanning software development, IT operations, and program delivery. **Technical expertise:** Hands-on design and development of production AI and software platforms — ClearBid (public-sector compliance AI), ClearBind (AI InsurTech), an OSFI E-23 model-risk-management platform for Canadian financial institutions, and GridWitness (energy/carbon) — built in TypeScript, Python, Next.js/React, Node.js, and Terraform with AI/LLM integration. **Delivery leadership:** 9+ years of scaled Agile delivery leadership (SAFe SPC 6, CSM, PRINCE2, ITIL) as Release Train Engineer and Scrum Master at Northbridge Insurance, Intact Insurance, CIBC, Servus Credit Union, and AT&T. **Earlier experience:** Presales and solutioning for SapphireIMS, an ITOM/ITSM data-centre management product. **Education:** B.Tech, Electrical & Electronics Engineering. **Proposed Role:** Mohammed Yousuf Shariff will serve as Project Manager and Solution Architect for this engagement, providing direct leadership across both delivery governance and technical solutioning. He will be available at a minimum of 80% dedication during active project phases (Discovery, Design, Build, UAT, Go-Live) and 50% during stabilization and support. He is based in Chestermere, AB, and is available to travel to Prince Albert, SK for key on-site milestones (kick-off, UAT, go-live) as required by the City. [PROVIDE: confirm whether the City requires a named on-site presence in Prince Albert for the duration of the engagement, and the expected project start date, so availability can be formally confirmed.] **⚠️ GAP — Municipal ERP Experience:** The dossier does not establish Canadian municipal ERP implementation experience for Mr. Shariff. This is a specific requirement of the solicitation [p.22]. [PROVIDE: If Mr. Shariff has municipal ERP experience not captured in the dossier, document it here. If not, this gap must be addressed by naming additional personnel with the required experience.] [PROVIDE: Current résumé for Mr. Shariff formatted to the City's required template (if specified), confirming availability for this engagement.] --- ## 5.2 Additional Proposed Personnel [PROVIDE: For each additional team member proposed (including subcontractors), provide:] - Full name - Proposed role (e.g., ERP Functional Consultant — Finance, ERP Technical Consultant, Change Management Lead, Training Lead, Data Migration Specialist) - Location (city, province) - Relevant Canadian municipal ERP experience (client names, ERP platform, dates, modules) - Résumé **⚠️ CRITICAL GAP:** NimbleStride operates a principal-led model engaging vetted associate consultants. For this solicitation, named individuals with demonstrated Canadian municipal ERP experience must be identified and their résumés included. This is a mandatory requirement [p.22]. Engaging resources "within a week" is not sufficient — named, committed personnel are required at proposal stage. [PROVIDE: Identify and confirm availability of all personnel to be named in this proposal. Obtain signed teaming or subcontract agreements with any associates or subcontractors before submission.] --- # 6. Relevant Experience & References > **⚠️ CRITICAL GAP:** The solicitation requires **three references for client organizations of similar size and scope where comparable ERP implementation services were delivered within the last five years**, including contact information, project dates, modules implemented, and contract value [p.22]. The dossier does not contain any ERP implementation references. The references provided in the dossier are for enterprise IT delivery by the principal as an individual contributor at other organizations — not for NimbleStride/MGR Infotech company-level ERP implementations. ## 6.1 Company Experience NimbleStride Inc. has designed and delivered multiple production-grade software and AI platforms, demonstrating end-to-end capability from requirements and architecture through deployment and operation: 1. **ClearBid** — a Canadian public-sector compliance-screening AI platform. 2. **ClearBind** — an AI-powered InsurTech platform. 3. **OSFI E-23 Model Risk Management Platform** — built for a Canadian federally regulated financial institution, meeting stringent regulatory and data-governance requirements. 4. **GridWitness** — an energy and carbon data platform. MGR Infotech has delivered IT infrastructure and managed-services engagements, including deployment of approximately 200 computers and laptops, CCTV and physical security system installations, point-of-sale system installations, and Microsoft Active Directory and Office 365 setup and administration. [PROVIDE: For each project above — client name, project dates, contract value, and a reference contact (name, title, phone, email). These are required to cite as formal bid references. Without client names and contacts, these cannot be submitted as verifiable references.] --- ## 6.2 Formal Client References (Mandatory — Three Required) **⚠️ CRITICAL GAP:** Three references for comparable ERP implementations at organizations of similar size and scope to the City of Prince Albert, delivered within the last five years, are required [p.22]. None are available from the dossier. [PROVIDE: Three client references in the following format for each:] | Field | Reference 1 | Reference 2 | Reference 3 | |---|---|---|---| | Client Organization Name | [PROVIDE] | [PROVIDE] | [PROVIDE] | | Client Size (population / employees) | [PROVIDE] | [PROVIDE] | [PROVIDE] | | Contact Name & Title | [PROVIDE] | [PROVIDE] | [PROVIDE