All available labor should be shown in WO Tracking/Assignments tab regardless of the default workzone - http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=85313
All relevant labor should be shown in WO Tracking/Assignments tab regardless of the primary craft -
You can vote by clicking on the link and then selecting the link at the bottom of the RFE to vote for it. Please also click on the “Add to my watchlist” link to also show your interest. In practice this doesn’t seem to result in additional emails etc.
You may be presented with an advert/dialog box for IBM Bluemix. This is not related to the RFE in anyway.
Untick all the boxes and click continue.
If this RFE is for a component that you don’t use then there are still reasons to vote for this as described in “Why vote for a change to a solution/component that my company does not use?”
Why vote for a change to a solution/component that my company does not use?
There are several reasons:
- Maximo has a number of common components so a change in one solution may be applicable to your solution (e.g. IBM Cloud Control Desk uses the same framework as Maximo Asset Management)
- As the Maximo product improves it makes it easier to sell in the future which encourages IBM to invest more in the product.
- Your company may also adopt the component at some point in the future.
- Maximo development is split across a number of teams/locations.
Industry solutions (e.g. Service Provider) and components (e.g. Scheduler) are developed by separate teams of developers who are not part of the core Maximo team that work on the major Maximo releases (e.g. 7.6).
This means that you can vote to influence the product and it won’t take resources away from RFEs your company is interested in.
If everyone consistently votes together then other people will vote for RFEs that your company is interested in.
How quickly would an RFE be implemented?
In practice it is at least a year before an RFE is implemented if it is selected for inclusion.
Votes can help push IBM to consider implementing things that they may not have planned to or to bring forward those implementation plans.
In Janurary 2016 Vetasi led a push for votes for a Websphere Single Sign On RFE (55555) which significantly increased the votes for that RFE. Six days later the status changed to uncommitted candidate. The RFE was first raised in July 2014 and had only gathered a handful of votes and so it had not been listed for inclusion.
16 of the RFEs that Vetasi have promoted have been moved to a status of uncomitted candidate or later e.g. delivered.
In some cases the RFEs had been raised over a year earlier and had not progressed due to a lack of votes.
Vetasi are also working behind the scenes to speed up the adoption of Vetasi raised RFEs and we expect to see some of the RFEs being implemented more quickly where they fit in with IBM’s development plans.
IBM tutorials - http://www.ibm.com/developerworks/rfe/execute?use_case=tutorials
RFEs need to be written like business cases and require careful wording. If you have an idea for a possible enhancement then contact me and I can investigate how feasible it is and I can raise it and promote it to gain the most votes. This is normally provided free of charge.