If you have a look at the 188.8.131.52 installation documentation you will see the rules behind a maintenance release.
I suspect because OBIEE is still at 184.108.40.206.x and there not been too many changes relating to configuration with EPM 220.127.116.11 that the process should still be the same but I feel it is worth testing out to be sure.
The blogs outlining the steps in more detail are available at:
If installing EPM 18.104.22.168 on Windows 2012 Server the following OS information is shown in the installer prerequisite checks:
The main new feature is the simplified interface even though it is not really new as it first appeared in 22.214.171.124.500 and was aimed purely at accessing the interface through a tablet which I blogged about here.
Did you know there is an EPM System Activity Report in 126.96.36.199+?
It is not documented and probably was only developed for use with Oracle’s PBCS but nevertheless it does exist and can be run on any EPM server.
The report generates the following statistics:
Did you know that you can alter the frequency or disable the essbase OPMN ping?
This time the randomiser has picked:
Did you know where the EAS console picks the version/patch number from?