CBC-PROC-305 Version 1 Last Review Date: Febraury 2025
Feature Requests
1. Overview
What is a Feature Request?
A Feature Request is where a user identifies a change to the system that would require development effort to implement. This usually takes the form of User Interface (UI) changes, such as additional columns on a list view, new fields on a data entity, changes in functionality etc. A Feature Request can be small (one new column), or large (a whole new data entity or piece of functionality).
What Feature Requests will be considered?
To evaluate a feature requests, we consider:
- Impact: Will it significantly improve user experience, efficiency or outcomes?
- Feasibility: Can the feature be implemented within a reasonable timeframe and cost?
- Demand: Are multiple users or teams requesting this feature?
- Compliance Needs: Does it address a legal or regulatory requirement?
What is the process?
A simplified version of the process is presented here:
A user has an idea for a new feature or change.
- Discuss the change with your peers and manager to initially assess it's viability.
The user submits a new Feature Request by copying the template below and emailing CMMS Support.
The Feature Request is evaluated against the criteria outlined above.
If accepted, the Feature Request will enter the development road-map, and be developed.
The change is deployed.
Bugs
It is important to note that bugs, i.e., issues with existing functionality, do not fall into the category of Feature Requests. Raising of bugs should continue as normal, via the usual support channel.
Best Practices for Submitting Requests
- Focus on the problem, not just the solution. This allows the CMMS team to explore the best ways to address your needs.
- Be as specific as possible in your descriptions. Vague or unclear requests are harder to evaluate and prioritise and accordingly may be rejected.
- Use examples from your day-to-day operations to illustrate the importance of the feature.
2. Template
The following template should be used for your Feature Request submission, which can be copied and pasted into your email:
Feature Request
| Field | Response | Example/Options |
|---|---|---|
| Requestor Name | ||
| Requestor Email Address | ||
| Platform | Portal / App / Other | |
| Specific View | i.e., WO View, Quote View, Client List | |
| Proposed Solution | Describe the feature you are requesting and how it would address the issue. Provide examples of workflows or user scenarios where the feature would be helpful. Use specific field names where possible. | |
| Value Proposition | Explain why the feature is important for your team. Highlight the expected outcomes, such as time savings, improved accuracy or better compliance. | |
| Supporting Information | Include screenshots or references to similar features in other systems to help clarify your request. |
3. Submission
Submission of Feature Requests are to be made to the existing CMMS Support email address: CBC CMMS Support