IBM Systems Magazine, Power Systems - May 2017 - 29
In Butterill's experience, the
process of exchanging ideas
between users and IBM works
like a well-oiled machine. Any
IBM i user can go to the COMMON
Requirements Portal, where they
may choose between IBM i or
AIX* requirements. They can review existing requirements to see
what's already been submitted,
and add requirements of their
own. Users may also submit hand
written requirements during the
annual meetings, but most opt
for the online method, which is
The advisory council then
reviews these requirements and
determines whether they should
be submitted to IBM. And in most
cases, they do.
"The council reads through and
prioritizes everything submitted, going back to clients to get more information if necessary," says Butterill.
"Then they meet with us monthly by
phone, and twice a year face to face,
to share those requirements."
Once IBM receives a client
requirement, it is assigned to an
appropriate IBM developer, who
determines next steps. Depending on the requirement itself, the
request may be handled in an
upcoming technology refresh or
release. Others may require more
in-depth consideration and are
placed on the list for possible
inclusion in a future release.
This process gives users
an opportunity to make IBM
Power Systems better for their
entire user community, while
also giving them a powerful voice
to IBM. "Our development team
takes these requirements seriously," says Dawn May, IBM liaison
to IBM i client advisory councils.
"And we deliver somewhere
around 70 percent of all customer
requirements that we receive."
ibmsystemsmag.com MAY 2017 // 29