New Feature Requests

A new feature request (NFR) is a specific need, want, or suggestion from an existing cloud ecosystem tenant for a new feature, enhancement, or connectivity request as the product evolves and/or a change is needed. These types of changes are typically those that enhance a product’s existing features to improve usability and/or accessibility and fix minor bugs or glitches.

Generic requests with high levels of effort, planned maintenance, and routine infrastructure changes (e.g., service accounts, S3, networks, security group, firewall, etc.) are considered out of scope for a new feature.

Request a New Feature

Tenants may request a New Feature Request through Jira Service Management (JSM).

Request NFR

FCS NFR Internal Review Process

When FCS receives a New Feature Request, a collaborative process begins to ensure:

All information is accurately collected.
The correct determination is made on each request.

This process requires involvement from teams across the program and we are committed to providing our customers with a timely response. Due to the comprehensive nature of these requests your patience is kindly requested as we work to provide the most accurate response possible.

FCS NFR Internal Review Process

NFR Pathways

There are many factors that impact FCS’s ability to approve and move forward with an NFR including, but not limited to, funding, product availability, and resource availability. Each NFR will either be approved, placed on hold, transferred or closed. Once ticket status is determined, updated information will be communicated directly via the JSM ticket. See below for the various paths an NFR can follow:

Approved

NFR Planned for Current or Future Time

If FCS determines the NFR should move forward, the product or service team will determine the prioritization. Once the projected timeline is determined, it will be communicated via the JSM ticket. The NFR ticket will remain open while the NFR work is being done. Once the work is completed, the tenant will be notified of implementation via JSM.

Actions Currently in Progress

If the feature requested is already in progress due to a request from a different tenant or pre-planned FCS enhancement, the tenant will be notified and provided with the details and timing surrounding that new feature implementation. The NFR ticket will be placed on hold during execution and the tenant will be informed when the work is completed. Once the work is completed, the tenant can then request this feature directly by opening a general request ticket in JSM.

Requested Feature Currently Available

If the feature requested is currently available, the tenant will be notified and provided with the relevant details. At that point, the NFR ticket will be closed. The tenant can then request this feature directly by opening a general request ticket in JSM.

Transferred

Cloud Advisory Intake

If FCS determines the NFR closely aligns to the Cloud Advisory intake process and the start of the Cloud Smart Journey (e.g., new initiative, new project, new service onboarding, architecture changes or security impact, level of effort is too complex, solutioning and/or funding discussions are required), the NFR ticket will be closed and a new Cloud Advisory ticket will be opened to determine the next steps. The requestor will receive communication via the new Cloud Advisory JSM ticket.

Rough Order of Magnitude (ROM) Request

If the tenant is seeking a ROM, a new request will be opened with Cloud Advisory. Communication regarding next steps or other information from Cloud Advisory will be shared via the new JSM ticket.

Technology is Not an Available Capability

If the requested feature is not a viable function/capability used or implemented/available by FCS, this ticket will be transferred to Cloud Advisory to discuss alternative solutions. Cloud Advisory will share information and communicate directly with the tenant via the JSM ticket.

On Hold

Follow-up Required

If FCS requires additional details to make a determination on the request, FCS will communicate via JSM and ask the tenant to provide specific information. Once the information is provided, FCS will continue to analyze the request. During this analysis period, the request will be placed on hold.

Lack of Funding

If an NFR has been requested, but funding is not available, the request will be placed on hold until funding is approved. The tenant will receive communications via the JSM ticket.

Feature Adds Program Risk

If FCS determines that the request cannot be completed at this time due to a potential risk to the program, agency, etc., the requestor will receive a notification from FCS with specific details. The NFR will be placed on hold until such risk is resolved and/or any identified next steps are achieved.

External Dependencies

If, upon review, it is determined that the request has one or more external dependencies that are beyond the scope, visibility, and control of FCS, the requestor will receive communications with specific details via JSM. The NFR will be placed on hold until the external dependencies have been resolved.

Awaiting Tenant Actions

If additional information is requested, FCS will communicate the needed information, actions, etc. via the JSM ticket. The NFR request will be placed on hold until the information is received.

Closed

Alternative Solution Proposed or Available

In the event that FCS has developed and deployed an alternative solution for the NFR that aligns with FCS infrastructure, that information will be provided via JSM. The NFR ticket will be closed.

NFR Is No Longer Needed

If, at any point, the NFR is no longer needed or required, the JSM ticket will be closed. A new NFR can always be opened if the need arises again.

NFR Work Completed

Once an NFR is fully implemented the ticket will be closed.