Framework: Fujitsu Macroscope

Framework: Fujitsu Macroscope

Classification: Industry Practice (proprietary methodology suite, Fujitsu Canada) Maintained by: Fujitsu Consulting (Canada) Inc. Version: 5.0 (June 2012) / 5.2 (latest documented update) Evaluation: N/A — auto-approved as Industry Practice (client-mandated at STM)

What It Is

Macroscope is an integrated methodology suite developed and maintained by Fujitsu Consulting (Canada). It provides a comprehensive, adaptable framework for enterprise IT transformation — covering strategy, enterprise architecture, solution delivery, project management, and benefits realization within a single coordinated system.

Originally created by DMR Consulting Group (Montreal, 1973) as structured IT delivery guides in the 1980s, Macroscope evolved through multiple versions before being rebranded under Fujitsu's ownership in 2002. The name is borrowed from Joel de Rosnay's concept of a "macroscope" — an instrument for observing and understanding the infinitely complex.

Macroscope is heavily adopted in Quebec-based organizations (STM, Desjardins, Hydro-Quebec, Government of Quebec) and across Fujitsu's Canadian consulting practice. It is primarily used as Fujitsu's core body of knowledge for consulting services and is also licensed as a commercial product to client organizations.

Client context: STM (Societe de transport de Montreal) uses Macroscope as their standard methodology for IT project delivery, enterprise architecture, and organizational change management. Their architects think in Macroscope artifact codes (A-codes) and follow Macroscope's process domains.

When to Use It

Select Macroscope when the client context includes:

  • Client uses Macroscope — The organization has adopted Macroscope as their standard methodology (STM, other Fujitsu consulting clients). All architecture work must align with their existing artifact structure and process domains.
  • Quebec/Canadian government or transit organizations — Macroscope is the dominant EA/delivery methodology in this market. Architects and IT leaders will expect Macroscope terminology and artifact types.
  • Full-lifecycle transformation — The engagement spans from strategy through architecture, solution delivery, change management, and benefits tracking. Macroscope covers all of these in one integrated framework.
  • Hybrid methodology needs — The client uses both traditional (waterfall) and agile approaches. Macroscope 5.0 explicitly supports hybrid delivery with agile techniques integrated into its Solution domain.
  • Organizational change management — The engagement includes significant organizational transformation alongside IT changes. Macroscope's "Changement Organisationnel" domain provides structured change management (complemented by Gyroscope, its dedicated change management tool).

Macroscope is less suited for organizations that have standardized on TOGAF or another global framework, pure software development shops (use agile/DevOps frameworks), or small-scale single-application engagements.

Complementary use: Macroscope and TOGAF overlap significantly in the Architecture domain. When working with a Macroscope client, use Macroscope's artifact structure and terminology as the primary lens, but map concepts to TOGAF equivalents for interoperability (see the Cross-Reference section below).

Key Concepts

Five Process Domains

Macroscope organizes all methodology content into five process domains (historically named with product brands):

Domain Historical Name Purpose
Vision StrategyForum Capture, structure, and confirm the organization's business and IT strategy
Architecture ArchitectureLab Define and evolve the enterprise architecture — business, data, application, and technology layers
Solution ProductivityCentre Envision, design, build, deliver, operate, and maintain information system solutions
Benefits ResultStation Formulate, select, and manage change programs to maximize business value from investments
Project ManagementSuite Plan, resource, manage risk, and control projects to deliver expected capabilities

Each domain contains processes (workflows with phases, steps, and activities), deliverables (work products with templates and examples), techniques (detailed methods for producing deliverable content), and roles (responsibility assignments).

Artifact Numbering System (A-Codes)

Macroscope assigns unique identifiers to all deliverables using an A-code system. These codes are how STM architects reference specific artifacts:

Exigences d'entreprise (Enterprise Requirements)

Code Name (FR) Name (EN) Description
A140 Contexte d'entreprise Enterprise Context Organizational structure, value streams, market context
A130 Scenarios d'affaires Business Scenarios Desired business outcomes and use cases
A240 Exigences d'entreprise Enterprise Requirements High-level goals driving architecture decisions
A360 Principes et regles d'entreprise Business Principles & Rules Architecture principles and governance rules

Architecture d'entreprise (Enterprise Architecture)

Code Name (FR) Name (EN) Description
A230 Orientations d'architecture Architecture Orientations Strategic direction documents driving architecture scenarios
A200 Capacites d'affaires Business Capabilities Business capability map (L1-L4 hierarchy)
A251 Processus Business Processes Business process catalog with maturity assessment
A250 Systemes Systems (Application Portfolio) Application inventory with lifecycle and fit assessment
A170 Architecture de l'information Information Architecture Data entities, data flows, information assets
A219 Architecture logicielle Software Architecture Software component architecture
A239 Ressources humaines Human Resources HR organizational structure, teams, roles
A269 Environnements de travail Work Environments Physical/virtual workspace architecture
A285 Autres ressources Other Resources Catch-all for technology and infrastructure resources
A370 Architecture de l'infrastructure Technology Infrastructure Technology infrastructure: hardware, cloud, platforms
A150 Architecture des donnees Data Architecture Data storage, data management architecture

Gestion des services (Service Management)

Code Name (FR) Name (EN) Description
A400 Catalogue des services Service Catalog IT service catalog (ITIL-aligned)
A401 Contrat de service Service Contract SLAs and service agreements

Changement organisationnel (Organizational Change)

Code Name (FR) Name (EN) Description
A100 Solutions d'entreprise Enterprise Solutions Solution proposals for business transformation
A280 Impacts Impacts Impact analysis of proposed changes
A290 Couts et benefices Costs & Benefits Cost-benefit analysis of solutions
A270 Strategie de livraison Delivery Strategy Implementation phasing and timeline
A275 Strategie de changement org. Org Change Strategy Organizational change management plan
A715 Materiel de communication Communication Materials Change communication artifacts

Assurance qualite (Quality Assurance)

Code Name (FR) Name (EN) Description
A610 Criteres d'evaluation Evaluation Criteria Architecture evaluation criteria and standards
A620 Evaluation de l'architecture Architecture Evaluation Assessment of architecture against criteria
A920 Analyse d'ecart des capacites Capability Gap Analysis Gap analysis between current and target capabilities
A900 Suivi des exigences Requirements Tracking Requirements traceability and progress monitoring
A905 Audit de la reponse aux exigences Requirements Compliance Audit Compliance audit against requirements
A915 Matrice de tracabilite des capacites Capability Traceability Matrix Traceability from requirements to capabilities to solutions

Knowledge Areas

Central to Macroscope's design are Knowledge Areas — modular building blocks that practitioners assemble into tailored methodologies. Each Knowledge Area encompasses techniques, roles, and fundamentals that can be selectively combined. For example, integrating agile delivery from the Solution Domain with project controls from the Project Domain.

Methodology Adaptation

The first fundamental principle of Macroscope is "Adapt the method to your context." The framework is designed to be tailored — method elements are selected and adapted based on project characteristics:

  • Project size and complexity (simple, standard, complex)
  • Delivery approach (waterfall, agile, hybrid, accelerated)
  • Technology context (custom development, package implementation, cloud migration)
  • Organizational maturity (initial adoption vs. optimized practice)

Macroscope 360

A specialized extension providing a comprehensive 360-degree requirements view for digital delivery projects. It emphasizes aligning business value with IT capabilities through examination of stakeholder needs, functional and non-functional requirements, and measurable service outcomes.

Gyroscope

A dedicated change management companion tool focusing on leadership practices, stakeholder relationship-building, and organizational alignment to facilitate smooth transitions during digital transformations.

Cross-Reference: Macroscope to TOGAF

Macroscope Domain Macroscope Concept TOGAF Equivalent
Vision Business Strategy Preliminary Phase + Phase A (Architecture Vision)
Architecture Business Capabilities (A200) Phase B (Business Architecture)
Architecture Systems / Applications (A250) Phase C (Application Architecture)
Architecture Information Architecture (A170) Phase C (Data Architecture)
Architecture Technology Infrastructure (A370) Phase D (Technology Architecture)
Architecture Architecture Orientations (A230) Phase E (Opportunities and Solutions)
Changement Solutions d'entreprise (A100) Phase E + Phase F (Migration Planning)
Changement Impacts (A280) Gap Analysis (Phases B/C/D)
Changement Delivery Strategy (A270) Phase F (Migration Planning)
Quality Evaluation Criteria (A610) Architecture Governance (Phase G)
Quality Architecture Evaluation (A620) Architecture Compliance Review
Project Project Management Not covered (TOGAF assumes PM exists separately)
Benefits Benefits Realization Not covered (TOGAF focuses on architecture, not value tracking)

Cross-Reference: Macroscope to LeanIX

This mapping is the operational bridge for STM. Their architects work in Macroscope artifacts; the data lives in LeanIX Fact Sheets.

Macroscope Service Artifact LeanIX Fact Sheet Type Mapping Type Notes
Exigences A130 Business Scenarios Objective (tactical) Partial Scenarios describe desired outcomes
Exigences A140 Enterprise Context Organization + BusinessContext Composite Org structure + value streams
Exigences A240 Enterprise Requirements Objective (strategic/operational) Direct Goals driving architecture
Exigences A360 Business Principles Objective (strategic) Partial Principles as strategic objectives
Architecture A200 Business Capabilities BusinessCapability (L1-L4) Direct 1:1 mapping — capability hierarchy
Architecture A230 Architecture Orientations Initiative (idea) Direct 1 orientation = 1 initiative
Architecture A250 Systems Application (all subtypes) Direct 1:1 — system inventory
Architecture A251 Business Processes BusinessProcess Direct 1:1 — process hierarchy
Architecture A170 Information Architecture DataObject Direct Data entities = DataObject fact sheets
Architecture A219 Software Architecture Application + ITComponent Composite Microservices/components
Architecture A239 Human Resources Organization (team) Partial HR org structure
Architecture A269 Work Environments ITComponent (hardware) Partial Physical/virtual workspaces
Architecture A285 Other Resources ITComponent (various) Partial Catch-all tech resources
Architecture A370 Technology Infrastructure ITComponent + TechnicalStack + Platform Composite Full tech stack
Changement A100 Enterprise Solutions Initiative (project/program) Direct Solution proposals
Changement A280 Impacts Initiative relation attributes Direct lxImpactType + transformationType
Changement A290 Costs & Benefits Initiative (costBudget, costActual) Partial Budget/actuals on initiatives
Changement A270 Delivery Strategy Initiative lifecycle + dates Partial Phases as lifecycle stages
Changement A275 Org Change Strategy Initiative + Organization Composite Change affecting org units
Changement A715 Communication Materials — Custom No LeanIX equivalent
Quality A610 Evaluation Criteria qualitySeal config Partial Quality Seal rules
Quality A620 Architecture Evaluation functionalSuitability, technicalSuitability Partial Fit scores on fact sheets
Quality A900 Requirements Tracking Objective (progress) Partial Progress field (0-100%)
Quality A905 Compliance Audit qualitySeal workflow Partial DRAFT to APPROVED workflow

Official Resources