HomeMy WebLinkAbout26 - Instructions - Permits, Licenses, & Code Enforcement (PLCE) Software and Implementation Services (8)Bozeman, MT
PLCE Deliverable Expectations
For Tab Deliverable Expectations
Please use the descriptions below to complete columns B - F on the subsequent tab.
Note: Cells in gray do not require a response. Respondents shall not modify or remove any dropdowns -- doing so may result in the proposal being deemed Non-Responsive.
Column
A
B
C
D
E
F
For Tab Deliverable Summary
Please use the descriptions below to complete columns B - G on the subsequent tab.
Column
A
B
C
D
E
F
G
H
Header
Expectation
Response
Lead
Support
Pricing
Comments
Header
#
Phase
Deliverable Name
Description
Related Milestone
Format
Assumptions
Comments
Description
Expectation or question related to proposed project management services during implementation.
Use dropdown to select response or enter text if no dropdown provided.
Use dropdown to select party who leads in the deliverable / expectation
Use dropdown to select party who supports in the deliverable / expectation
Use dropdown to select if deliverable is included in the Fixed Fee price, Optional (i.e., additional fee and must be included in the Price Proposal), or Not Applicable (i.e., not provided)
Respondent to provide any clarifying information.
Description
Numbered list of deliverables. Add additional rows as necessary.
Indicate phase of project when deliverable is provided.
Provide name of deliverable.
Provide brief description of deliverable.
Provide the milestone in which the deliverable is provided.
Provide format of deliverable.
Provide any assumptions about the deliverable.
Concisely provide any additional context or information as necessary.
PLCE Deliverable Expections
Expectation
General
Deliverables will be identified and included in the Scope of Work (SOW)?
Deliverables will include a purpose, scope, expectations, assignment of responsibilities, and acceptance criteria?
Deliverables require formal written acceptance by the client?
Project Governance
A project plan will be created that includes key activities, interdependencies, phases, and other relevant details (See Project Management Expectations for additional details).
A project charter will be created with roles, responsibilities, and a governance structure and an RACI matrix.
Phase exit criteria are defined, tied to formal deliverable acceptance, and must be met prior to phase progression.
System Design
Alignment sessions will be held to understand City's current operations and goals for the new system. If Yes, describe this process/activity.
Requirements Traceability Matrix (RTM) is a deliverable and includes requirements from RFP. If Yes, describe in comments how the RTM is used.
Documentation of business process decisions or configuration decisions. If Yes, describe in comments how decisions are documented.
Gap analysis deliverable that identifies where requirements cannot be met out-of-the-box and proposes resolutions.
Documentation includes recommendations for efficient use of system.
Workflow design specifications (for approvals, routing, conditions) are documented.
Security and role design approach is documented.
RTM can be updated during System Design as long as changes do not affect scope of work.
Reports identified in SOW are delivered and specifications documented.
Interface specifications are documented. If Yes, describe in comments.
Non-functional requirements are documented (system performance & availability, security, SLA reporting, auditability, etc.).
Build
Configuration Workbook delivered and maintained throughout build.
Documentation of as-built configuration used in system. If Yes, describe in comments.
Development of use cases from client's configuration that can be used for testing configurations.
Data Conversions
Conversion plan is included as deliverable.
Extraction of client data included.
Cleaning of client data included.
Developing mapping / crosswalk of client data to system requirements.
Loading client data to new system included.
Testing / validating client data in new system included.
Data reconciliation reports provided and formal data sign-off required prior to go-live.
Testing
Testing plan is included as deliverable.
Stakeholder analysis related to testing included in testing plan.
Unit testing of system design included.
Integration testing included.
User acceptance testing included.
Test scripts included as a deliverable.
Test scripts are provided. If Yes, describe how test scripts are developed.
Test scripts are mapped to requirements in RTM. If Yes, describe in comments how this process works.
Defect management process documented (severity levels and resolution tracking).
Go-Live & Support
Cutover plan included as deliverable.
Cutover plan includes go-live readiness assessment.
Rollback / contingency plan documented.
Length of final acceptance period after go-live.
Length of post go-live support included in proposal.
Respondent includes just-in-time support for activities that may occur outside the post go-live support period (e.g., year-end close). If Yes, describe in comments what this support
consists of and any related charges or fees.
Organizational Change Management
Organizational Change Management (OCM) is a deliverable.
OCM includes:
Stakeholder identification and assessment
Communications plan
Stakeholder OCM meetings / trainings
Change Impact Assessment
Readiness assessment at key milestones
Documentation of new business processes. If Yes, please describe in comments
Knowledge Transfer & Training
Training Plan is a deliverable.
Training Plan includes:
Stakeholder identification
Training scope
Training schedule
Development of training materials. If Yes, please describe in comments
Types of training materials provided
Training materials are customized for client
Type of training provided to System Administrators
Type of training provided to "power users"
Type of training provided to end users
Number of trainings per functional area
Can Respondent-led trainings be recorded for future Client use?
Response
Lead
Support
Pricing
Comment
#
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
Phase
Deliverable Name
Description
Related Milestone
Format
Assumptions
Comments