Evaluate your mission reference architecture and interoperability architecture artifacts developed against the ISE maturity model. The ISE maturity model is broken down by FEAF common approach domains (business, data, applications and services, security, infrastructure, and performance) with characteristics established for each level of interoperability (adhoc, repeatable, enhanced, managed, and optimized) and for each interoperability requirement. For each element determine the maturity level of your mission architecture by moving across each row and matching your current state. During this step you should also note the characteristics of each requirement where the requirement/element maturity is less than your desired level (Ex., your interoperability level is at ‘repeatable’; you need to be at ‘managed’). Note that mission-specific architectures will have different goals for each element maturity level based on the operational needs or organizational policy of the mission architecture.
After completing the previous steps and determining which interoperability elements should be incorporated into each enterprise architecture domain, build a plan and roadmap that leads to interoperability at the applicable maturity level for your mission- specific EA. The plan and roadmap should address each interoperability requirement where improvement is deemed necessary. The roadmap should consider the availability of both intra- and inter-agency shared services which will require coordination.
The following graphic is provided to show the relationship between the Maturity Model Assessment, the Architecture Artifact Build, the Reference Architecture Template Activity, and the building of the Interoperability Roadmap, as well as inputs and outputs of each activity. The Interoperability Roadmap build activity will also require the interoperability goals for the specific mission architectures since the maturity level (ad-hoc, repeatable, enhanced, managed, or optimized) goals will be different for each mission architecture based on its needs.
It would be advantageous to interoperability efforts if this roadmap/plan were maintained to monitor progress towards interoperability goals and to coordinate plans across departments and agencies. Options for monitoring include: 1) ISA IPC via the Senior Architect’s Forum, 2) OMB via E-Gov Initiative, 3) the Federal CIO Council.
The Interoperability Maturity Model addresses five domains of interoperability. Each domain is supported by applicable questions and maturity model assessment criteria. Each row in the maturity models represents a functional area within the domain. Each column represents a different stage of maturity. Interdependencies between functional areas exist but the goal is to assess a system independently for each functional area.
The purpose of the business domain is to ensure that the system, program or reference architecture aligns to an organization’s mission requirements and clearly describes the scope, goals, and purpose of the architecture. The business domain typically describes:
References to policies, guidance, and laws that affect the reference architecture and related mission objectives
Governance groups responsible for oversight of the reference architecture
Mission vision, objectives, and requirements
Lines of business, capabilities, and activities
Planned achievement of capabilities by timeframes and what constrains/policies apply.
Interoperability objectives of the business domain include:
Description of how a reference architecture supports the operational enterprise
Incorporating information sharing functions into mission-specific activities (e.g., address the information sharing lifecycle activities such as collection, analysis, dissemination, storage, and retirement)
Using standards-based approaches to capture business requirements and document business processes and information flows
Identifying common information exchanges for a specific mission scenario/use case
Capturing information sharing requirements, constraints, and rules between partners.
The Business Domain maturity model is divided into functions or process groups (rows) and maturity levels (column). The maturity model is followed by several supporting questions.
Stage: Ad hoc: Formalized definitions of the business processes do not exist.
Stage: Repeatable: Definitions of the business processes are formalized and understood within the organization.
Stage: Enhanced: The formalized definitions of the business processes are understood by external partners.
Stage: Managed: Internal and external partners understand the various roles within the business process through manual workflows.
Stage: Optimized: All internal and external partners understand the various roles within the business process through automated workflows. The business process definitions are improved as necessary through monitoring feedback from current processes and to better serve the organization’s particular needs.
Stage: Ad Hoc: Formalized business process models that describe the information sharing flows are not defined.
Stage: Repeatable: N/A
Stage: Enhanced: Business process models that describe the information sharing flows are defined by a modeling standard and are aligned to applicable policy, guidance, or law. The models employ repeatable exchange patterns.
Stage: Managed: N/A
Stage: Optimized: The formalized business process models use a modeling standard (e.g., BPMN, WS-BPEL, IDEF0, or XPDL 2.1) and share and reuse processes. The models are available online to all authorized users.
Stage: Ad hoc: An ISA does not exist.
Stage: Repeatable: The ISA documents the purpose, scope, and authorized users of the data exchanges.
Stage: Enhanced: The ISA is understood by all users who are involved in the data exchanges and can be manually provided to authorized users.
Stage: Managed: The ISA is available online to authorized users and compliance is manually monitored.
Stage: Optimized: Compliance to the ISA is automated. Metrics are collected and used to enhance interoperability across agencies.
The purpose of the data domain is to describe what data is available to promote the common identification, use, and appropriate sharing of data/information across the government. It provides guidance for consistently describing, categorizing, and sharing data, and facilitates the discovery and exchange of information across boundaries. It describes structure (logical and schema) of the data/information at a level necessary for users to understand both what types of data/information is available and the data’s structure. The semantic meaning of the data/information should also be addressed within this domain in order to enable the interoperability of the data/information to be exchanged. This domain typically describes how:
Data is classified within a given data source by the mission or business context in which the data is used
Structured, semi-structured, and unstructured data is stored, managed, and used in a system
Services and processes reference and manipulate data
Business context is applied to data so that it can be searched
Standardization of information exchange between information sharing partners.
Interoperability objectives of the data domain include:
Describing how data is structured, what standards are used, how data/information can be exchanged so users are able to both have access to and use the data/information
Specify/describe the data/information flow, including tagging, discovery, and retrieval of the data
Demonstrating the commonly occurring need for exchanges of data/information between the domain and users
Describing how data/information is secured throughout the lifecycle
Specifying how data/information is tagged/structured, and how specific data tagging standards are used
Describing principles, roles, and responsibilities for data management and stewardship.
The Data Domain maturity model is divided into functions or process groups (rows) and maturity levels (column). The maturity model is followed by several supporting questions.
Stage: Ad hoc: Business context is applied to the data. Organization stores and manages defined, semi-defined, and undefined data for use by internal services and processes.
Stage: Repeatable: N/A
Stage: Enhanced: Organization stores and manages defined, semi-defined, and undefined data for use by internal services and processes.
Stage: Managed: N/A
Stage: Optimized: Data is exchanged across agencies and missions using open standards.
Stage: Ad hoc: The data structure is defined.
Stage: Repeatable: Standards consistently define the data structure. Some automated data structuring and manual record-level tagging exists.
Stage: Enhanced: A consistent, agency-adopted format with mostly automated structuring and manual record-level tagging of the data exists.
Stage: Managed: Data tagging is semi-automated at the attribute-level with a community-adopted metadata format.
Stage: Optimized: Smart data tagged at the attribute-level with open metadata standards.
Stage: Ad hoc: Basic dataset-wide search capability exists.
Stage: Repeatable: Basic system-wide search. Business context is applied to the data so it is discoverable within the agency.
Stage: Enhanced: Basic search of data assets that is configurable to federate from any system using a specific agency-adopted service contract.
Stage: Managed: Advanced search of data assets that is configurable to federate from any system using a community-adopted service contract.
Stage: Optimized: Advanced search of data assets that is configurable to federate, is discoverable, available, and accessible across agencies and missions by using open standards.
Stage: Ad hoc: Exceptions are solely handled manually.
Stage: Repeatable: N/A
Stage: Enhanced: The system semi-automatically resolves the majority of exceptions.
Stage: Managed: N/A
Stage: Optimized: The system automatically resolves the majority of exceptions.
Stage: Ad hoc: Security and privacy achieved through isolation of systems and implementing current regulatory mandates or laws.
Stage: Repeatable: Supporting policies identified and under consideration.
Stage: Enhanced: Supporting policies in process of development and implementation.
Stage: Managed: Security and privacy is documented by consistent supporting policies, which are mostly implemented.
Stage: Optimized: Security and privacy is documented by consistent supporting policies, which are implemented.
The applications and services domain describes the technical services supporting the common activities used for discovering, identifying, distributing, protecting, and managing the data/information that external users require. It should:
Provide any applicable service standards, application architecture approaches (e.g., SOA), or other information required to interact with the applications/services within the domain
Describe the relationships between systems, applications, and interfaces
Interoperability objectives of the applications and services domain include:
Capturing the specifications and functional requirements of the applications/services to the level necessary so external application developers can interface with applications/services
Describing recommended and/or possible implementation approaches (e.g., cloud, SOA, mobile)
Identifying services and common activities, their service components, and the interfaces/interconnections between the services and data assets that are exchanged
Identifying the functions performed by the applications/services and any constraints on the data used and the flow of the data
Specifying service standards used or required by the applications/services
Specifying rules/laws with respect to products, data, and/or information generated by the applications/services
Publishing/exposing application programming interfaces (APIs) so future users can access and create applications with the data/information, and describing how the developers access the APIs
Describing extensibility approaches for future users/applications to add additional functionality
Describing how application architecture scales for more users
Describing how services are made discoverable
Specifying the provider and user roles and responsibilities with respect to application/service lifecycle (from development to operations and maintenance, to retirement)
The Applications and Services Domain maturity model is divided into functions or process groups (rows) and maturity levels (column). The maturity model is followed by several supporting questions.
Stage: Ad hoc: Formalized business service models that depict information flows, relationships, and dependencies between services are not defined.
Stage: Repeatable: N/A
Stage: Enhanced: Business service models are defined by a modeling standard and are aligned to applicable policy, guidance, and laws. The models employ repeatable exchange patterns.
Stage: Managed: N/A
Stage: Optimized: The formalized business service models are available online to authorized users.
Stage: Ad hoc: Service is not discoverable.
Stage: Repeatable: Service has undergone agency publication process, and is discoverable and accessible within the agency.
Stage: Enhanced: Service is discoverable and accessible by authorized users.
Stage: Managed: N/A
Stage: Optimized: Service is discoverable and accessible by authorized external users through an online service registration and discovery mechanism.
Stage: Ad hoc: Data exchange occurs physically, by telephone, or by email.
Stage: Repeatable: Data is exchanged by a system-specific service with mostly automated pushes and pulls.
Stage: Enhanced: Data is exchanged through an agency-wide service with entirely automated pushes and pulls.
Stage: Managed: The method of data exchange is configurable to operate with any system using a community-adopted proprietary format with entirely automated pushes and pulls.
Stage: Optimized: The method of data exchange is configurable to operate with any system using an open standard with entirely automated pushes and pulls.
Stage: Ad hoc: No SLA
Stage: Repeatable: N/A
Stage: Enhanced: The SLA exists and includes requirements for service availability, serviceability, performance, operation, as well as the roles and responsibilities between the service provider and service consumer to deliver and maintain the service. Compliance of the SLA is not monitored.
Stage: Managed: The SLA includes the standard/ specification that addresses any interoperability considerations or constraints that affect implementation of the services. Compliance of the SLA is manually monitored.
Stage: Optimized: The SLA includes the standard/ specification that addresses any interoperability considerations or constraints that affect implementation of the services. Compliance monitoring of the SLA is automated.
The purpose of security domain is to describe the security policies and considerations required for external users that need to interface and get access to the data/information. The Interoperability Maturity Matrix uses the Federal Identity, Credential and Access Management (ICAM) Maturity Model to assess the progress of an agency’s business processes and technical capabilities against the ICAM segment architecture, as related to interoperability within the security domain.
Interoperability objectives of the security domain include:
Describing how proper security controls are used by the architecture to ensure data/information protection and allow access by external users
Describing high-level security needs from an interoperability perspective, such as the use of common security standards/protocols
Identifying controls required for specific types of information and any handling caveats (i.e., address confidentiality, integrity, and availability requirements)
Describing how proper security controls are used to ensure data protection and ensure access
Determining if information must be exchanged across different security enclaves
Using metadata to tag data and describe its pedigree, lineage, source, timeliness, confidence, or other attributes associated with trust
Identifying digital security rules, guidelines, and standards for securely exchanging data and services across security domains
Describing, with enough detail for an external application developer, the event trace of the interactions of the architecture with regard to security controls
Describing the identity management system used to allow/deny access to the data/information (i.e., role or attribute based)
Describing the plan to manage/control your identity accounts and provide access controls to systems (for users, system administrators, developers, and super users)
Describing how new users/developers are granted access to the data/information at all stages of the lifecycle
Describing data/information access audit methods or standards, include the lifecycle for the storage of the audit data
The purpose of the performance domain is to provide linkage to investments or activities and an organization’s strategic vision. This domain typically:
Provides a direct line of sight between strategic planning and the investment review process
Identifies common performance elements across investments or activities
Provides a high-level overview of recommended metrics to be considered that will measure the successes of the architecture (inputs, outputs, and outcomes).
Interoperability objectives of the performance domain include:
Define performance goals that align to applicable policy, guidance and laws
Review investments and ensure they clearly incorporate interoperability requirements and adhere to relevant performance goals
The Performance Domain maturity model is divided into functions or process groups (rows) and maturity levels (column). The maturity model is followed by several supporting questions.
Stage: Ad hoc: Formalized performance metrics that provide direct line of sight between strategic planning and the investment review process do not exist.
Stage: Repeatable: Formalized performance metrics exist and align with strategic goals of organization as well as to applicable policy, guidance, and laws.
Stage: Enhanced: Formalized performance metrics that identify common performance elements across investments or activities exists.
Stage: Managed: N/A
Stage: Optimized: Formalized performance metrics are used to inform gap analysis of interoperability requirements and adhere to relevant performance goals.