We use six industry frameworks: BIAN, DODAF, FEAF, TMForum ODF, and IndEA.
Finance and Banking Architecture Framework - BIAN
BIAN is the Banking Industry Architecture Network. A consortium of financial services companies developed it. The BIAN Service Landscape is a blueprint for the logical components of a bank’s IT environment. Leveraging this blueprint and the Service Domain Specifications will significantly speed up architecture initiatives—be it in the planning of change initiatives, in the procurement of components, or benchmarking of an existing landscape against best practices.
>>> Compare BIAN and TOGAF (TOGAF vs. BIAN)
Architecture Framework for Defence
DODAF is the Department of Defense Architecture Framework. The United States Department of Defense develops DODAF.The central problem defense agencies face is integrating long-lived systems and diverse organizations into common missions and capabilities. Many weapons systems have decade-long development and can be expected to be in use for 30-40 years.
The DODAF viewpoint library is optimized around communications and integration to address this problem. We routinely use DODAF's viewpoints where we have an integration problem across independent organizations.
Besides DODAF, other NATO countries have developed their own specialized defence architecture frameworks. Canada developed DNDAF, The United Kingdom developed MODAF and NATO uses NAF. DODAF-based defence architecture frameworks focus on the core problem of interoperability.
>>> Compare DODAF and TOGAF (TOGAF vs. DODAF)
Government Architecture Framework - FEAF
FEAF is the United States Federal Enterprise Architecture Framework. The central problem government agencies face is duplication of process, IT system, and data across independently developed services and programs.
They designed the FEAF Reference models to highlight duplication. By describing business, IT systems, data, and infrastructure through a common language, duplication is uncovered. This allows the agency to ensure that duplicative processes, systems, and data are in the service interests of the program stakeholders.
We routinely used FEAF's approach, and derived reference models during acquisition and merger projects. Duplication isn't necessarily bad. It needs to be justified based on your organization's value proposition and operating model.
The Government of India has developed IndEA. IndEA takes a broader approach than FEAF. Besides duplication, IndEA attempts to set standards for enterprise architecture modelling and the description of many enterprise architecture domains..
TM Forum's Open Digital Framework
The TM Forum Open Digital Framework (ODF) is designed for the telecommunications industry. They optimize it for their challenges, which center around migrating from legacy IT systems and processes to modular, cloud native systems.
TM Forum member organizations develop ODF.
We have used TM Forum's FrameworX Business Process Model several times with consumer-facing organizations. The separation of eTOM into customer facing and operational systems has highlighted challenges in managing consolidated and simplified operations in the face of specialized offering to customers.
