3. What is the nature and description of the request?
RHEV engine-upgrade-check says no updates available when the rhevm-setup package is up to date, but this does not neccessary mean the engine is up to date. One can run yum update on the the system and have the rhevm-setup up to date but still have an outdated rhevm because engine-setup didn't run.
Eg, 

# engine-upgrade-check
VERB: queue package rhevm-setup for update
VERB: Downloading: repomdE9SThbtmp.xml (0%)
VERB: Downloading: repomdE9SThbtmp.xml 2.1 k(100%)
VERB: Downloading: repomdFpcNa_tmp.xml (0%)
VERB: Downloading: repomdFpcNa_tmp.xml 2.1 k(100%)
VERB: Building transaction
VERB: Empty transaction
VERB: Transaction Summary:
No upgrade

4. Why does the customer need this? (List the business requirements here)
The current behaviour is confusing. Engine-upgrade-check says the system is up to date, while it's not.

5. How would the customer like to achieve this? (List the functional requirements here)
Change engine-upgrade-check and make it check all engine rpm's and not just the one for rhevm-setup

6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
run yum update on a system without running engine-setup. Run engine-upgrade-check and check if there's a message like eg "The rhevm-setup is already updated. Please run engine-setup to update the rhev-m as well"

7. Is there already an existing RFE upstream or in Red Hat Bugzilla?
Not aware of any

8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
no

9. Is the sales team involved in this request and do they have any additional input?
no

10. List any affected packages or components.
rhevm*.rpm

11. Would the customer be able to assist in testing this functionality if implemented? 
yes, but I don't think it's difficult to test this at RH. :-)