Skip to content
Africa Tech FestivalMeet us in Cape Town, 17–19 Nov.

Presentations

From your estate to a board-ready deck.

Pick a template. The genie drafts an outline for you to approve if you choose, then builds the full pack from your model as PowerPoint (pptx), PDF or Confluence pages.

Illustrative

How it works

Four steps from template to pack.

  1. 01

    Pick a template

    Choose one of the four templates and what it covers: an initiative, an assessment, or your whole estate.

  2. 02

    Approve the outline (optional)

    The genie proposes the outline; you can review and approve it before the pack is assembled, changing which chapters it keeps and their titles.

  3. 03

    The genie builds it

    It loads the records in scope, draws the views, writes the text around the figures, renders each format and checks the result.

  4. 04

    Download or publish

    Download the files, or publish to Confluence, with an optional sign-off first.

The outline lists the chapters the template proposes. Untick a chapter to leave it out or rename one, then approve, and the genie builds from your outline.

Cancel instead, and nothing is built.

Illustrative

Architecture Initiative

Proposed outline

  • The initiative
  • Architecture impact
  • Application impact assessment
  • Architecture views
  • Readiness & risk
  • Strategy, options & vendors (left out)
  • Assurance
  • Appendix
  • Next steps
Approve the outlineCancel the build

Building the pack from the approved outline.

Templates

Four templates.

Architecture Initiative

Audience: Steering committee

The architecture assessment of one initiative: what it asks for, the systems it touches and what happens to each, the as-is and to-be views, readiness and risk, the options and vendors, and the decisions it now needs.

  • PowerPoint (pptx)
  • PDF slides
  • PDF document
  • Confluence pages
What’s inside
  1. The initiative
  2. Architecture impact
  3. Application impact assessment
  4. Architecture views
  5. Readiness & risk
  6. Strategy, options & vendors
  7. Assurance
  8. Appendix
  9. Next steps

Capability Maps

Audience: Steering committee

The landscape of your whole estate, one chapter per map: ODA capability, TM Forum application map (TAM) function, eTOM process, and applications and integration, each with its coverage and white space.

  • PowerPoint (pptx)
  • PDF slides
  • PDF document
  • Confluence pages
What’s inside
  1. ODA capability
  2. TAM function
  3. eTOM process
  4. Application & integration
  5. What to firm up before sign-off
  6. Inventory and method
  7. Next steps

Digital Initiative

Audience: Workshop

A digital initiative from the customer’s side: the designed experience comes straight after the initiative, then the application and architecture impact and the readiness assessment.

  • PowerPoint (pptx)
  • PDF slides
  • PDF document
  • Confluence pages
What’s inside
  1. The initiative
  2. Experience design
  3. Application impact
  4. Architecture impact
  5. Readiness assessment
  6. Additional detail
  7. Assurance
  8. Appendix
  9. Next steps

BSS Assessment

Audience: Steering committee

The publication of one BSS assessment: executive summary, maturity, domain scorecards, rating distribution, recommendations, vendor coverage and gaps, ODA readiness and standards, application dispositions and next steps. Every figure is drawn from the BSS Assessment report pack, so the deck, the document and the Confluence pages agree with the screens.

  • PowerPoint (pptx)
  • PDF document
  • Confluence pages
What’s inside
  1. Executive summary
  2. Maturity
  3. Domain scorecards
  4. Rating distribution
  5. Recommendations
  6. Vendor coverage and gaps
  7. ODA readiness and standards
  8. Application dispositions
  9. Next steps
See the BSS Assessment report pages

Formats

One pack, four formats.

  • PowerPoint (pptx)

    The pack as 16:9 slides.

  • PDF slides

    The same slides as a PDF, one page per slide.

  • PDF document

    An A4 document that reflows the pack, with table headers repeated on every page.

  • Confluence pages

    A tree of pages in your Confluence space, kept up to date.

Illustrative

Numbers you can trace

The figures come from the model. The genie writes the words around them.

  • Figures are taken when you ask

    Figures are the snapshot taken, with your own access, when the pack was requested, so they show only what you can see. The publication record keeps which snapshot was used.

  • The genie never writes its own numbers

    Every number in the text comes from the model. Each passage is checked before it is used.

  • If the text fails its check, the pack still works

    If a passage cannot be written cleanly, it falls back to a plain sentence built from the figures’ labels, and the pack says so.

Illustrative

  • Each pack opens with how it was built and closes with where each figure came from.
  • When a chapter’s records are missing, the chapter drops out and the pack says so.

Quality

Every pack is checked before anyone sees it.

Each pack is stored with its quality verdict. The checks cover structure, wording, overlapping text and layout, and each template adds its own, such as required chapters, readable text size and accessible colour contrast.

A pack that fails cannot be published. Only an administrator can override the gate, and the override is recorded.

A pack whose diagrams failed to render is held back too.

Illustrative

Quality verdict

Passed
  • Structure
  • Wording
  • Overlap
  • Layout

Quality verdict

Not passed
  • Structure
  • Wording
  • Overlap (failed)
  • Layout

Fix and rebuild, or ask an admin to override.

Publish to Confluence (unavailable)

Publish to Confluence

Signed off, then published to Confluence.

You can ask a named reviewer to sign off before publishing (optional); every pack must pass its quality check. The decision is recorded with the pack, and republishing updates the same pages.

  1. 01

    Sign off

    If you ask for sign-off, a task goes to the reviewer you name, or to you if you name nobody. They approve it, or reject it with a reason.

  2. 02

    Publish

    The pack is published to your Confluence space as a tree of pages.

  3. 03

    Kept up to date

    Publish again, or publish a later pack of the same scope, and the same pages are updated.

Illustrative

Sign off

Sign off the presentation pack for publication

Sam

ApproveReject
Later packSame scope, signed off

Publication record

Signed off by Sam

Date of sign-off

Figures snapshot recorded

  • Architecture
  • Initiative X
  • Architecture assessmentupdated
  • Architecture impactupdated
  • Readiness & riskupdated
  • Next stepsupdated

Published to Confluence. A later pack of the same scope updates the same pages.

  • Sign-off is a normal review task

    It sits on the Tasks board with your other reviews, and you can decide it in EcoGenie or from its card in Microsoft Teams.

  • A publication record

    The pack is kept with who signed it off, when, and the figure snapshot it was drawn from.

  • No duplicate pages

    Republishing never creates duplicate pages, and each scope keeps its own.

  • A sign-off has a due date. If nobody decides before the task expires, nothing is published.
  • If Confluence can’t take the pages, the run says why and the pack itself is untouched.

Need slides from a single diagram? The Diagramming genie turns the canvas into editable PowerPoint in one click.

Slides straight from a diagram

See EcoGenie on your own architecture.

Bring a change you’re planning. We’ll show you how the genies assess it, and who signs it off.