DAOD 2011-1, Enterprise Architecture Programme

Table of Contents

  1. Introduction
  2. Definition
  3. Overview
  4. Management
  5. Compliance and Consequences
  6. Responsibilities
  7. References

1. Introduction

Date of Issue: 2019-10-16

Application: This DAOD is a directive that applies to employees of the Department of National Defence (DND employees) and an order that applies to officers and non-commissioned members of the Canadian Armed Forces (CAF members).

Supersession: CANFORGEN 017/08, Promulgation of the Department of National Defence and Canadian Forces Architecture Framework (DNDAF) and the Defence Architecture Data Model (DADM)

Approval Authority: Vice Chief of the Defence Staff (VCDS)

Enquiries: Director Enterprise Architecture (DEA)


Top of page

2. Definition

enterprise architecture (architecture d’entreprise)

The collection of strategic information that defines a DND or CAF organization, the elements of the organization and interrelationships necessary to operate the organization to achieve its objectives, and the processes necessary for implementing new capabilities in the organization or the reinvestment or divestment of existing capabilities. (Defence Terminology Bank record number 31723)

Top of page

3. Overview

Context

3.1 The VCDS is responsible for ensuring the effectiveness and efficiency of the processes, procedures and toolsets that support the methodology and practice of enterprise architecture (EA) in the DND and the CAF.

Purpose

3.2 The purpose of this DAOD is to establish the responsibilities necessary for the delivery, management and support of the EA Programme. The need for the adoption of an EA approach is recognized in the Treasury Board Directive on Management of Information Technology. See Appendices C and D of the Directive for additional information.

Expected Results

3.3 The EA Programme in the DND and the CAF is expected to:

  1. be a strategic enabler that aligns investment, divestment and reinvestment decisions to support accountability, control, compliance, risk management and higher level defence strategies;
  2. enable the visualization, through modelling techniques and diagrams, of significant aspects of business capabilities that would otherwise be very difficult to describe and articulate;
  3. enable governance structures and processes and better project portfolio prioritization;
  4. formalize engagement rules and facilitate identification of an organization’s specific EA and linkages with the EA of other organizations;
  5. enable support for timely evidence-based decision making, with knowledge of the impacts and projected effects, and anticipation of future demands and requirements;
  6. provide direction and oversight for organizational change, including the determination of the optimization point for the change, and explicitly shifting the optimization point for change to the enterprise level through a holistic view of end-to-end impact and effects across organizational and functional lines;
  7. allow stakeholders through a holistic approach to prioritize and justify often conflicting technology trade-off decisions, across multiple planning horizons;
  8. allow the leverage of technologies and innovations faster, avoid false starts and minimize the footprint of legacy solutions;
  9. promote knowledge and trust in people, processes and technology that are critical in breaking down the boundaries to information flow, which will allow knowledge to spread across the DND and the CAF by linking users, information providers and technical support personnel in a common effort; and
  10. provide for business capabilities to readily evolve with changes in strategy, resulting in an increased level of innovation, reduced technology complexity and improved component and platform reusability.

Effects of Not Adopting EA

3.4 Guidance for the effective and equitable usage of resources is very critical to ensure the sustainability of DND and CAF strategic objectives. Without the full implementation of the EA Programme, it will be difficult to evaluate, direct and monitor DND and CAF program activities. Incoherent governance activities may result in overlooking critical capabilities, with the risk of developing incompatible or overlapping capabilities. Accordingly, not fully implementing the EA Programme may result in:

  1. an inability to:
    1. reduce organizational complexity and have the required agility to sustain the organization’s change agenda;
    2. align capabilities and processes with business strategies to achieve a higher value for money and demonstrate a higher level of stewardship;
    3. identify program synergies and reallocate investments from sustainment to the change agenda;
    4. identify and track organizational interdependencies to ensure compliance and the effective management of business continuity;
  2. a lack of future state guidance that could result in the DND and the CAF not being able to project the roadmaps for technology investments to anticipate and meet the requirements of business capabilities;
  3. a reduced ability to support governance bodies in leveraging investment, divestment and reinvestment opportunities;
  4. the absence of future state roadmaps and migration plans, which could result in inconsistent and duplicated islands of data, and functional silos with domain or environmental specific system development and procurement; and
  5. the creation of a sub-optimal level of interoperability and agility that reduces the ability to have greater visibility in the execution of organizational programs, which may lead to uncertainties and overlap in roles and responsibilities.

Top of page

4. Management

4.1 DND employees and CAF members must manage the EA Programme in a manner that provides EA practitioners with an effective method for the development and capture of EA.

4.2 For the successful delivery of the EA Programme, essential components such as the EA framework, toolsets, training, client support services and governance must be available and applied.

4.3 Clear, consistent, communicated and managed EA must be used to provide decision makers at all levels with timely and critical information in support of change management and decision making.

Top of page

5. Compliance and Consequences

Compliance

5.1 DND employees and CAF members must comply with this DAOD. Should clarification of the policies or instructions set out in this DAOD be required, DND employees and CAF members may seek direction through their channel of communication or chain of command, as appropriate. Managers and military supervisors have the primary responsibility for and means of ensuring the compliance of their DND employees and CAF members with this DAOD.

Consequences of Non-Compliance

5.2 DND employees and CAF members are accountable to their respective managers and military supervisors for any failure to comply with the direction set out in this DAOD. Non-compliance with this DAOD may result in administrative action, including the imposition of disciplinary measures, for a DND employee, and administrative or disciplinary action, or both, for a CAF member. Non-compliance may also result in the imposition of liability on the part of Her Majesty in right of Canada, DND employees and CAF members.

Note – In respect of the compliance of DND employees, see the Treasury Board Framework for the Management of Compliance for additional information.

Top of page

6. Responsibilities

Responsibility Table

6.1 The following table identifies the responsibilities associated with this DAOD:

The …
is or are responsible for …

VCDS

  • ensuring that approval for EA is mandatory in the project approval process required by the Treasury Board.

level one advisors

  • implementing and managing the EA Programme in their organizations;
  • integrating business, operational and information technology solutions and services in EA;
  • using the DEA repository as the primary storage location of their EA artifacts;
  • ensuring that accurate EA for their organizations are maintained in the DEA repository;
  • ensuring their requirements for EA are provided to the DEA; and
  • identifying offices of primary interest for EA as required.
DEA
  • ensuring the effective and efficient development, implementation and management of the EA Programme in the DND and the CAF;
  • developing and maintaining the EA framework and standards;
  • coordinating the delivery of EA toolsets and training;
  • providing guidance on EA;
  • maintaining a repository for the electronic storage of all EA artifacts; and
  • managing an EA reference library.
project managers
  • ensuring the correctness and completeness of deliverables for their EA projects in all phases of the project approval process; and
  • ensuring deliverables for their EA are integrated in the DEA repository.
DND employees and CAF members
  • complying with all Government of Canada and DND and CAF EA policies, instructions, directives and standards.

Top of page

7. References

Acts, Regulations, Central Agency Policies and Policy DAOD

Other References

Report a problem or mistake on this page
Please select all that apply:

Thank you for your help!

You will not receive a reply. For enquiries, contact us.

Date modified: