Can someone using the Enterprise Business Process Analysis Solution tell me if the framework limits certain templates to certain folders like the Enterprise Architecture framework does?

Hi Andres, Thanks for your question. EBPA (Enterprise Business Process Analysis) - is a collection of standards, frameworks, and case-studies that allow EA architects to rally & lead the wider organization into a more coherent way of doing EBPA. It includes the following items: 1. Set of EBPA visio templates (e.g., BPMN, Customer Journey, Process on Page, Capability on a Page, Value Steam and others). 2. Meta-model extensions, including new object types, new relationship types, and new attributes (e.g., APQC Identifier, Process Manual or Automated, Waste Type and others). 3. Process Reference Framework (APQC) with actual data inside the repository. 4. Set of iServer Views for structuring, analyzing, and maintaining business process information. 5. Other items like case-study, folder structures, and sample diagrams. The standard is more of a collection of various items than a concrete practice. The intention behind this extension is to provide various architecture building blocks that you can use in discussions & solution building yourself. So there is no single folder that contains all templates or a pre-defined workflow/procedure for EBPA to follow. You will find that EBPA is peppered though many folders inside the [Case Studies], [State], and [Resource Center] libraries. You can easily merge all templates into a single folder, which might work good for a demo but is not recommended for actual daily use (too many templates to govern within a single folder). A good approach is to first understand what exactly your organization is looking for in the EBPA? 1. Process Classification? This could be addressed by using APQC for establishing a process model based on your industry. 2. Process Standardization & Definition? This could be addressed by using APQC + BPMN Standard. 3. Process Improvement? This could be addressed by using BPMN + Lean Extensions. 4. EBPA from higher level view to define business needs & flows? Capability Maps, Value Stream Maps, Process/Capability on a Page type diagrams. All these items are loosely connected and getting traction in one direction will most certainly boost other areas. As for ghost relationships, I'm not sure what you mean by this. Do you have connectors that don't create relationships in the DB; you have more relationships than you have created; you have relationships that show up in repository but not on your Entity Rel Diagram; or something completely different?