LPA/IPA naming standards

We have Interfaces that start with an assigned interface number (e.g. I114APInterface). Subsequent IPAs that are from called within the main IPA are named free-form (e.g. APControlReport, APMatrixReport, APVendorList)

This makes it difficult to know by site what triggers or relates to what without checking out the IPA and review or having a reference doc.

Anyone care to weigh in on the plusses and minuses of naming?

For example, if the above I114APInterface runs and you see APControlReport_I114, APMatrixReport_I114, APVendorList_I114 we would know it is related to the I114APInterface. However, if APVendorList can be called by many different process flows, we would drop the _I114 to show it is not related to one particular Process flow.

Then Process flows that do not interface in/out but automates a process, would start with "prc"

Any thoughts, caveats or suggestions?

Thanks!
Erin