After the BEA accqusisition we have three tools for BPM in the Oracle product stack, each one of them addressing different use cases. At high level there's the BPA Suite for process modelling in BPMN and for enterprise architecture stuff. Then there's a product new to the Oracle stack: BEA Aqualogic BPM (Fuego). This tool is used for human centric business process modelling, with the capability of being executed directly. So there's no need for a transformation from the modelling language to an execution language, like it is done today with the transformation from BPMN to BPEL. The new name of this is Oracle BPM Suite. Finally we have the BPEL Process Manager in the stack, which will be used much more for integration purposes. In the near future, both the BPM Suite and the Oracle BPEL PM use JDeveloper for disign time and will be able to run on a joined runtime engine. Will be interesting to see that.