Telecom AI operations architecture, IT system overviews, digital transformation proposals, smart infrastructure reports.
ppt169
6
cover
toc
chapter
content
ending
reference_style
ai_ops - Enterprise Digital Intelligence Design Specification
Suitable for telecom operator AI operations architecture, digital transformation proposals, smart infrastructure reports, IT system overview diagrams, and other high-information-density scenarios.
Style Reference: See reference_style.svg (Telecom Operator AI Operations Architecture Overview), which demonstrates the core visual language of this template.
I. Template Overview
Property
Description
Template Name
ai_ops (Enterprise Digital Intelligence)
Use Cases
Telecom AI operations architecture, IT system overviews, digital transformation proposals, smart infrastructure reports
High density — a single page can accommodate 6-10 information modules, matching telecom reporting conventions
II. Canvas Specification
Property
Value
Format
Standard 16:9
Dimensions
1280 × 720 px
viewBox
0 0 1280 720
Page Margins
Left/right 30-50px, top 20px, bottom 40px
Content Safe Area
x: 30-1250, y: 80-680
Title Area
y: 20-80
Grid Baseline
20px (high-density layouts require a finer grid)
Note: Margins are narrower than standard templates (30px vs 60px) to accommodate the high-information-density reporting style common in telecom presentations.
III. Core Design Principles
Telecom High-Density Information Style
This template emulates the visual language of telecom technical reports. The core characteristics are "modular zoning + high information density + red-blue dual-color hierarchy".
Left Red Vertical Bar: A red rectangle (10×40px) before titles serves as a visual anchor — the most essential title identifier throughout the template.
Number Badges: Red square badges (30×30px with white numbers) identify key initiatives/capability numbers (e.g., numbers 1-5 in "Five Key Initiatives").
Dashed Zone Frames: stroke-dasharray="5 5" dashed rectangles group content modules, creating a structured, modular visual effect — a common "zone frame" in telecom reports.
Blue Label Bars: #2E75B6 blue-filled rectangles (full-width or fixed-width) serve as scenario/category headers carrying scenario names.
Warm Gray Overview Panels: Panels with #FDF3EB background + #F8CBAD border carry overviews, summaries, and open platform entries.
Metric Card Groups: White cards with #F2F2F2 borders, closely arranged to display KPI metrics; values highlighted in #C00000 red.
Light Blue Sub-modules: #5B9BD5 filled small rectangular cards displaying specific feature items (e.g., "AI One-Click Troubleshooting Assistant").
Gray Capability Base Cards: Cards with #E7E6E6 / #F2F2F2 background for displaying foundational capabilities/platform components.
Advanced Features
Triangle Decorations: The top area may use light semi-transparent triangles (fill-opacity="0.3") as visual guides.
Capability modules, team assignments, project lists
Table
Metric comparisons, progress tracking
Recommended: Telecom reports commonly use the "Architecture Overview" pattern — a single page presenting the complete architecture from objectives → results → scenarios → orchestration → foundational capabilities, unfolding top to bottom.
VIII. Common Components
Title Vertical Bar Decoration
<!-- Red vertical bar + title --><rectx="30"y="20"width="10"height="40"fill="#C00000"/><textx="50"y="55"font-family="Microsoft YaHei, sans-serif"font-size="36"font-weight="bold"fill="#C00000">Page Title</text>
Number Badge
<!-- Red square number badge --><rectx="80"y="560"width="30"height="30"fill="#C00000"/><textx="95"y="582"font-family="Arial, sans-serif"font-size="18"font-weight="bold"fill="#FFFFFF"text-anchor="middle">1</text>
Blue Scenario Label
<!-- Blue label bar --><rectx="120"y="310"width="220"height="40"fill="#2E75B6"/><textx="230"y="336"font-family="Microsoft YaHei, sans-serif"font-size="16"font-weight="bold"fill="#FFFFFF"text-anchor="middle">Fault Boundary Identification</text>
Metric Card
<!-- White metric card (values highlighted in red) --><rectx="120"y="215"width="140"height="35"fill="#FFFFFF"stroke="#F2F2F2"stroke-width="2"/><textx="190"y="239"font-family="Microsoft YaHei, sans-serif"font-size="14"font-weight="bold"fill="#000000"text-anchor="middle">Fault tickets reduced by<tspanfill="#C00000">30%</tspan></text>
Dashed Zone Frame
<!-- Dashed content zone --><rectx="120"y="390"width="940"height="150"fill="none"stroke="#C00000"stroke-width="2"stroke-dasharray="5 5"/>
Warm Gray Overview Bar
<!-- Full-width warm gray overview/summary bar --><rectx="30"y="80"width="1220"height="60"fill="#F2F2F2"/><textx="640"y="115"font-family="Microsoft YaHei, sans-serif"font-size="16"fill="#000000"text-anchor="middle">Overview text content...</text>
Compact Principle: The telecom style pursues maximum information per page; spacing is generally 30-50% smaller than standard templates.
X. SVG Technical Constraints
Mandatory Rules
viewBox: 0 0 1280 720
Use <rect> elements for backgrounds
Use <tspan> for text wrapping (<foreignObject> is strictly prohibited)
Use fill-opacity / stroke-opacity for transparency; rgba() is prohibited
Prohibited: mask, <style>, class, foreignObject (id inside <defs> is allowed). clipPath is allowed only on <image> under shared-standards.md §1.2
Prohibited: textPath, animate*, script
Prohibited: <symbol>+<use>, <iframe>, @font-face
Prohibited: <g opacity="..."> (group opacity) — set opacity on each child element individually
marker-start / marker-end conditionally allowed (marker in <defs>, orient="auto", shape = triangle/diamond/oval) — see shared-standards.md §1.1
Use only system fonts and inline styles
PPT Compatibility Rules
Use overlay layers instead of image opacity
Define gradients using <linearGradient> inside <defs>
Use rx/ry attributes for rounded rectangles (post-processing converts to Path)
XI. Placeholder Specification
The template uses {{PLACEHOLDER}} format placeholders:
Placeholder
Description
Applicable Template
{{TITLE}}
Main title
Cover
{{SUBTITLE}}
Subtitle/overview
Cover
{{AUTHOR}}
Speaker/organization
Cover
{{DATE}}
Date
Cover
{{CHAPTER_NUM}}
Chapter number
Chapter page
{{CHAPTER_TITLE}}
Chapter title
Chapter page
{{CHAPTER_DESC}}
Chapter description
Chapter page
{{PAGE_TITLE}}
Page title
Content page
{{CONTENT_AREA}}
Content area identifier
Content page
{{SECTION_NAME}}
Section name (footer)
Content page
{{SOURCE}}
Data source (footer)
Content page
{{PAGE_NUM}}
Page number
Content/ending page
{{THANK_YOU}}
Thank-you message
Ending page
{{ENDING_SUBTITLE}}
Slogan/tagline
Ending page
{{CONTACT_INFO}}
Contact information
Ending page
{{COPYRIGHT}}
Copyright
Ending page
XII. Usage Notes
Copy this template directory to the project templates/ directory
Review reference_style.svg to understand the core visual style
Select appropriate page templates based on content needs
Mark content to be replaced using placeholders
Generate final SVG through the Executor role
For high-information-density pages, refer to the multi-module zoning layout in reference_style.svg
XIII. Design Highlights
Telecom DNA: Derived from real telecom AI operations architecture reports, naturally suited for telecom/enterprise presentation styles
High Information Density: A single page can accommodate a complete architecture view (objectives → results → scenarios → orchestration → foundational capabilities)
Red-Blue Dual-Color Hierarchy: Red = core/emphasis/objectives, Blue = scenarios/modules/capabilities — clear visual hierarchy
Number Badge System: Red square numbers throughout create a "N Key Initiatives" visual narrative
Three-Level Nested Zoning: Dashed outer frame → category labels → feature cards for structured expression of complex architectures
Metric Card Groups: Compactly arranged KPI metrics with red-highlighted values for instant readability