OPS Enterprise Architecture Artefacts - Appendix B - Corporate Enterprise Architecture Review Requirements Guidebook - Version 1.7

Sep 13, 2026

Appendix B of the Government of Ontario IT Standard (GO-ITS) No. 56 sets out approved requirements for conducting a Corporate Enterprise Architecture Review within OPS. It defines what enterprise architecture artefact types must be prepared and reviewed across multiple layers, from contextual and conceptual models to logical and physical artefacts. The guidebook includes detailed coverage of resource, program, service, information and semantic models, governance, business scenarios, functional requirements, application design, deployment, and database inventory, with navigation to supporting artefact templates and internal-access guidance.

LanguageEnglish

CategoryPresentations

FormatPDF

Pages94

Reading Time33 min

AccessFree to download

Contextual

Resource Type

Line of Business Profile

Program

Service

Program Profile

Location Type

Geographic Area Type

Party Type

Role Type

Target Group Type

Event Type

Cycle Type

Need

Goal

Mandate

Target Group / Needs Cross Reference

Conceptual

Information Model

Conceptual Data Model

Interface Data Requirements Document

Semantic Model

Fact and Dimension Matrix

Service Life Cycle

Business Function Model

Governance Model

Organization Chart

Business Scenario

State Transition Diagram

Service Objectives

Logical

Logical Data Model

System Functional Requirements

System Architecture Document

Logical Application Design Document

Solution Pattern Match

Logical Application Deployment Model

Supplementary Specification

Physical

Physical Data Model

Database Inventory

Physical Dimensional Model

Physical Application Design Document

Government of Ontario IT Standard (GO-ITS) Number 56 OPS Enterprise Architecture Artefacts Appendix B – Corporate Enterprise Architecture Review Requirements Guidebook Version 1.7 Status: Approved Note: 􀁸 This appendix contains hyperlinks that are intended for use on the OPS intranet only. In particular, hyperlinks that point to artefact templates and examples will not work outside the OPS intranet. 􀁸 However, for external accessibility, the artefact templates have been included as separate files in Appendix D – Artefact Template Files. 􀁸 See Appendix C – Corporate Enterprise Architecture Artefact Template Information for more information and instructions on how to access the included template files. Table of Contents Row 1: Contextual........................................................................... 5 Resource Type ................................................................................ 5 Line of Business Profile..................................................................... 7 Program ......................................................................................... 8 Service .......................................................................................... 9 Program Profile .............................................................................. 10 Location Type ................................................................................ 11 Geographic Area Type ..................................................................... 12 Party Type ..................................................................................... 13 Role Type ...................................................................................... 13 Target Group Type ......................................................................... 14 Event Type .................................................................................... 15 Cycle Type..................................................................................... 16 Need............................................................................................. 17 Goal ............................................................................................. 17 Mandate ........................................................................................ 18 Target Group / Needs Cross Reference .............................................. 19 Row 2: Conceptual ........................................................................ 21 Information Model ..........................................................................21 Conceptual Data Model....................................................................22 Conceptual Data Model (Acquired Solution) .......................................24 Interface Data Requirements Document ............................................25 Semantic Model..............................................................................26 Fact and Dimension Matrix ..............................................................29 Service Life Cycle ...........................................................................31 Business Function Model..................................................................32 Service Integration Accountability Model ...........................................34 Service Profile ................................................................................36 Business Process Model ...................................................................38 SOA Service Specification ................................................................40 Business Network Model ..................................................................41 Governance Model ..........................................................................42 Organization Chart .........................................................................44 Business Scenario............................

FAQs

What is the purpose of OPS Enterprise Architecture Artefacts Appendix B?

It provides the requirements guidebook for a Corporate Enterprise Architecture Review under GO-ITS OPS, specifying what artefacts must be addressed across architecture layers.

Which architecture layers and artefact categories are covered?

The guidebook structures requirements into Contextual, Conceptual, Logical, and Physical rows, including models and specifications such as data models, governance, business scenarios, functional requirements, and application/deployment artefacts.

Are the included hyperlinks accessible outside the OPS intranet?

Hyperlinks intended for OPS intranet artefact templates and examples may not work externally; external accessibility is handled by separate template files referenced in other appendices.

Sep 13, 2026

Uploaded by Riley West