An organization can submit an NFS (New Feature Suggestion) to any vendor for which they are a client. Each vendor has their own process for reviewing and responding to an NFS. The procedure that Unisys follows is detailed below.
If an NFS is rejected or allowed to expire, regardless of the vendor, a UNITE member can submit a requirement to the UNITE Board of Directors that the NFS be reconsidered. A requirement can also be submitted for other issues besides product features, but it should still begin with communication with the vendor. The UNITE requirements process takes over when the member has exhausted the communication process with the vendor.
There is an online form for submitting a requirement on the UNITE web site under the Community menu/Submit Requirement Form. Alternatively, a written requirement can be emailed or postal mailed to the Board of Directors. The essential information to include is submitter name and address, company name and address, a requirement headline, background description, and action that should be taken.
Once the proper documentation has been submitted to the UNITE board, the User Advocacy Chair will bring it up as an agenda item at a UNITE Board of Directors meeting. If the requirement is approved by a majority vote of the Board of Directors, it will be submitted to Unisys and tracked by the User Advocacy committee.
User Advocacy is a formal committee within UNITE that is responsible for reviewing and presenting information relative to ongoing requirements. The committee is to review responses and track and monitor compliance. The committee chair is a member of the Board of Directors appointed by the Chairman of the Board. The Chairman of the Board can also appoint additional committee members when needed.
Unisys New Feature Suggestion (NFS) Process
New Feature Suggestions (NFSs) may be initiated against products that are currently being enhanced (Support Category 1).
NFSs are submitted through the Unisys Client Support Center or via the web using Support Online.
The NFS Policy adopts a business approach to the acceptance and implementation of NFSs. This policy aligns the acceptance of NFSs with Unisys internal business planning cycles and ensures the features implemented are in alignment with the strategic direction of Unisys products.
NFS Policy Procedure
The submission incorporates an initiator ‘value statement’ and quantifies the business benefits. This should be entered in the “Description” field of the NFS.
Unisys clients may review the NFSs and their status on the Unisys World Wide Web site (Support Online).
NFSs must be submitted in English. Supporting documentation, if required, also in English.
Initiator Defined Priority Definitions
NFS would provide significant value to the site. It is also a requirement for Priority “A” classification that the submitter’s perspective is that the suggestion have a broad appeal across multiple users.
NFS would provide benefit to this user. Value and other operational benefit to others is unknown.
NFS would provide some benefit, but may not provide measurable added value and operational benefits.
Review of NFSs by Unisys
An acknowledgement response is sent to the initiator upon receipt of the NFS. The NFS will then be opened for requirements review. During the first pass through the business planning cycle, NFSs not meeting Unisys criteria will be closed with a notification to the initiator. As part of the business planning cycle, all remaining NFSs and those retained from prior cycles will be reviewed for possible inclusion into a future release of the product. Initiators will be notified as NFSs are accepted and funded for implementation. When the accepted/funded NFS is scheduled for release the initiator will be notified prior to release.
Closure of NFSs Not Implemented
After 3-5 release cycles, Unisys reserves the right to close an open NFS that has not been implemented. Unisys will notify the initiator if they close their NFS.