Loading...
Community presentation
Create a polished, executive 16:9 PowerPoint deck for the KICK-OFF MEETING of the project: “Gestión Técnica de la Prueba de Concepto CAS Nivel 9 — BHP Spence” IMPORTANT — SOURCE…
Create your own version
Use this visual direction as inspiration for a new Presenton deck.
Use this designCreator prompt
Create a polished, executive 16:9 PowerPoint deck for the KICK-OFF MEETING of the project: “Gestión Técnica de la Prueba de Concepto CAS Nivel 9 — BHP Spence” IMPORTANT — SOURCE HIERARCHY Use the attached files with the following hierarchy: 1. “Propuesta_Tellus_Gestion_Tecnica_PoC_CAS_L9_BHP_Spence_REV2_con_Capabilities” = SOURCE OF TRUTH for project content, scope, responsibilities, gates, dates, team allocation, deliverables and dependencies. 2. “Digital Safety - Congestion Data review” = PRIMARY VISUAL REFERENCE. Reuse its visual language: BHP-style clean white technical slides, teal accents, dark blue/grey typography, orange BHP highlights, outlined technical icons, clear boxes, strong hierarchy, generous whitespace and Tellus + BHP branding. The cover should take inspiration from its dark mine-background opening slide. 3. “01_Kick off - Toolkit AMSA” = STRUCTURAL / STORYTELLING REFERENCE ONLY. Use its executive kick-off logic, especially how it presents objective, plan, governance and next steps. Do NOT copy AMSA branding, colors or project content. GOAL This is a simple executive kick-off deck, not a proposal and not a sales presentation. The narrative should answer: WHY are we here? WHAT will we execute? HOW is the PoC governed through gates? WHAT happens in Stage 1? WHAT happens in Stage 2? WHAT must be agreed today to start effectively? KEEP THE DECK TO 6 SLIDES TOTAL. Do not create an agenda slide. Do not include commercial pricing. Do not include payment milestones. Do not include optional services. Do not include generic company capability slides. Do not repeat the proposal. Do not invent project facts. Do not invent names for BHP stakeholders or suppliers. Do not overuse text. Language: SPANISH. Tone: technical, executive, collaborative and precise. Audience: BHP Spence project stakeholders, technical stakeholders, safety stakeholders and Tellus project team. -------------------------------------------------- SLIDE 1 — COVER -------------------------------------------------- Title: KICK-OFF MEETING Main title: Gestión Técnica de la Prueba de Concepto CAS Nivel 9 — BHP Spence Subtitle: BHP SPENCE | TELLUS Octubre 2026 VISUAL: Use a dark, high-quality open-pit mining image as background with a dark blue overlay, similar to the attached Digital Safety cover. Use BHP orange as a secondary accent and Tellus teal / blue as complementary accents. BHP and Tellus logos at the bottom. Keep it sophisticated and minimal. -------------------------------------------------- SLIDE 2 — CONTEXTO, OBJETIVO Y PROPÓSITO -------------------------------------------------- Title: Contexto y objetivo de la PoC Main message: “Reducir la incertidumbre técnica y operacional de la integración CAS GEN3–MIC–máquina antes de una decisión de mayor escala.” Build this slide around THREE visual blocks: A. CONTEXTO • PoC de CAS de alta precisión con intervención sobre máquina. • Alineamiento con EMESRT Nivel 9. • Evaluación controlada de interacciones dentro de los escenarios definidos para la PoC. • Arquitectura funcional de referencia: CAS GEN3 → MIC → Máquina • Vehículos livianos participan con CAS sin MIC. B. OBJETIVO DEL SERVICIO • Acompañar técnicamente el ciclo completo de la PoC. • Mantener continuidad entre arquitectura, interfaces, pruebas, evidencia y decisiones. • Reducir incertidumbres antes de ampliar la solución. • Emitir una recomendación técnica independiente al cierre. C. QUÉ QUEREMOS CERRAR EN ESTE KICK-OFF • Alcance y límites. • Gobernanza e interfaces. • Inputs y responsables. • Secuencia y próximos hitos. VISUAL: Do NOT make this a text-heavy slide. Strongly consider a central CAS GEN3 → MIC → MACHINE technical diagram, with the three information blocks arranged around it. Use simple industrial icons. -------------------------------------------------- SLIDE 3 — ALCANCE Y MODELO DE GATES -------------------------------------------------- Title: Alcance de la PoC y modelo de decisión Create a strong CENTRAL HORIZONTAL PROCESS: G1 DESIGN READINESS Oct 2026 → G2 INTEGRATION READINESS Nov 2026 → WINDOW: IMPLEMENTACIÓN BHP / PROVEEDORES Fechas TBD → G3 FIELD TEST READINESS Jan 2027 → G4 TEST COMPLETION Feb 2027 → G5 POC CONCLUSION Mar 2027 Under the gates, summarize the logic: G1 Diseño, arquitectura, ICD y matriz V&V. G2 Bench Test CAS–MIC y readiness de integración. G3 Instalación y commissioning revisados. G4 Pruebas controladas completadas. G5 V&V, riesgos residuales y recomendación final. Also show the FOUR execution fronts: 1. Diseño e integración 2. Assurance 3. Pruebas controladas 4. V&V y cierre At the bottom create a clear “RESPONSIBILITY BOUNDARY” strip: TELLUS Observa · Verifica · Analiza · Recomienda BHP Autoriza · Opera · Gestiona HSE/MoC · Decide gates PROVEEDORES Producto · Ingeniería · Configuración · Instalación / Commissioning IMPORTANT: Make the external BHP / supplier implementation window visually different from the Tellus active work windows. The audience must immediately understand that Tellus provides independent technical assurance and is NOT the product installer, operator or OEM. VISUAL: This should be one of the strongest slides in the deck. Use an infographic / roadmap rather than a table. -------------------------------------------------- SLIDE 4 — STAGE 1 -------------------------------------------------- Title: Stage 1 — Preparation & Integration Assurance Subtitle: Octubre – Noviembre 2026 | G1 + G2 Design the slide in TWO MAIN AREAS: LEFT / ~65%: A compact executive GANTT / timeline for Stage 1. OCTOBER • Kick-off y consolidación de antecedentes • Cierre de alcance y arquitectura • ICD Assurance Review • Matriz de pruebas y Plan V&V • Design Readiness • G1 NOVEMBER • Preparación del Bench Test • Bench Test Protocol • Bench Test Assurance • Registro de defectos y restricciones • Acciones pendientes / readiness • G2 Integration Readiness Use bars, milestone diamonds and gate markers. Do not use a dense MS Project-style Gantt. RIGHT / ~35%: TEAM / ORGANIZATION FOR STAGE 1 Create an elegant mini organization diagram based on ROLES — do not invent names. Jefe de Proyecto 10% Líder Técnico 60% Ingeniero de Proyectos 65% SME Tecnologías Mina 10% Highlight: STAGE 1 FOCUS Diseño · Integración · ICD · Protocolos · Bench Test · G1/G2 At the bottom, include a small dependency callout: DEPENDENCIA CRÍTICA La preparación del Bench Test depende de la disponibilidad de antecedentes, equipos, especialistas, versiones y documentación de proveedores. VISUAL: Use the visual sophistication of the Digital Safety slides but the kick-off clarity of the AMSA deck. -------------------------------------------------- SLIDE 5 — STAGE 2 -------------------------------------------------- Title: Stage 2 — Readiness, Controlled Testing & V&V Subtitle: Enero – Marzo 2027 | G3 + G4 + G5 Maintain EXACTLY the same visual grammar as Slide 4. LEFT / ~65%: Executive GANTT / timeline. JANUARY • Revisión de evidencia de instalación • Configuración y calibración • Installation & Commissioning Readiness Review • Defectos / restricciones abiertas • G3 Field Test Readiness FEBRUARY • Prueba 0 • Pruebas controladas autorizadas • Escenarios HV–LV definidos para la PoC • Logs, video, timestamps y evidencia • Registro de desviaciones / NCR • G4 Test Completion MARCH • Consolidación de evidencia • Evaluación T1–T5 • Riesgos residuales • Lecciones y restricciones • Informe Final de V&V • Recomendación técnica independiente • G5 PoC Conclusion RIGHT / ~35%: TEAM / ORGANIZATION FOR STAGE 2 Jefe de Proyecto 10% Líder Técnico 60% Ingeniero de Proyectos 65% SME Tecnologías Mina 7.5% Highlight: STAGE 2 FOCUS Readiness · Pruebas · Evidencia · NCR · V&V · Conclusión Also include a visible callout: VENTANA PREVIA — BHP / PROVEEDORES Ingeniería · Hardware · Instalación · Configuración · Commissioning · HSE/MoC Fechas detalladas a confirmar. IMPORTANT: Do not suggest that Tellus executes installation, commissioning or equipment operation. -------------------------------------------------- SLIDE 6 — ARRANQUE Y PRÓXIMOS PASOS -------------------------------------------------- Title: Arranque del proyecto Subtitle: Acuerdos requeridos para movilizar Stage 1 Create FIVE numbered action blocks. 1. CONFIRMAR GOBERNANZA • Contraparte diaria • Sponsor / responsables de decisión • Participantes de sesiones técnicas y Gate Reviews 2. CONFIRMAR ACTIVOS Y ARQUITECTURA • Activos candidatos HV / LV • CAS GEN3 • MIC • Versiones / configuraciones • Responsables de proveedor 3. ACTIVAR PAQUETE DE INPUTS • SOW • Arquitectura vigente • ICD CAS–MIC–máquina • Documentación y configuraciones • Antecedentes HSE / MoC • Información técnica relevante 4. CONFIRMAR CALENDARIO • Ventana G1 • Ventana G2 / Bench Test • Ubicación del Bench Test • Dependencias de proveedores • Ventanas preliminares para Stage 2 5. ESTABLECER CADENCIA • Reunión semanal de coordinación • Sesiones técnicas según necesidad • Gate Reviews G1–G5 • Reporte quincenal o por gate At the bottom create a strong closing statement: “Una línea base común desde el inicio permitirá mantener trazabilidad entre diseño, pruebas, evidencia y decisiones de gate.” VISUAL: Inspired by the “Próximos pasos” slide of the AMSA kick-off, but using BHP / Digital Safety aesthetics. This slide should work as an actual meeting checklist: people should be able to discuss the five items and leave the meeting with owners / actions. -------------------------------------------------- GLOBAL DESIGN RULES -------------------------------------------------- • 16:9 widescreen. • Professional mining / industrial aesthetic. • Minimal white-space-driven BHP visual language. • Use BHP orange sparingly for emphasis and milestones. • Use Tellus teal / blue for technical flows and assurance activities. • Dark blue / slate typography. • White or very light grey backgrounds for Slides 2–6. • Avoid gradients except on the cover. • Avoid decorative illustrations that look like generic AI artwork. • Prefer technical line icons, diagrams and process flows. • Avoid excessive rounded cards. • No 3D effects. • No stock-photo collage layouts. • No giant paragraphs. • Avoid more than ~6 main visual elements per slide. • Maintain strong alignment and consistent spacing. • Use a consistent gate color system across Slides 3–5. • Maintain identical Gantt and organization grammar between Stage 1 and Stage 2. • Use BHP and Tellus logos consistently but discreetly. • The deck should look like a real BHP technical project presentation, not a consulting sales deck. CONTENT CONTROL: Do not invent activities, deliverables, stakeholders, contractual obligations or project dates. If something is not supported by the proposal, leave it generic or omit it. Do not include: - commercial values - payment conditions - optional services - Tellus capabilities appendix - long methodology descriptions - company profile - generic EMESRT training content FINAL EXPECTATION: The finished presentation should feel like a concise, technically credible project launch deck that can be used directly in a 30–45 minute BHP Spence kick-off meeting. Prioritize clarity, technical credibility and visual storytelling over quantity of information.
Presentation overview
This community presentation was shared by Diego Canales (Jack Viper) as a complete 6-slide example. Create a polished, executive 16:9 PowerPoint deck for the KICK-OFF MEETING of the project: “Gestión Técnica de la Prueba de Concepto CAS Nivel 9 — BHP Spence” IMPORTANT — SOURCE… The preview lets you review the full sequence in order, rather than judging the design from a single cover image.
Use it as a reference for planning your own deck: notice how the amount of information changes from slide to slide, where visual emphasis appears, and how repeated design choices help the presentation feel connected. Community examples are inspiration, not locked templates, so you can keep the ideas that fit your audience and replace anything that does not.
Learn from the example
Look at the job each slide performs. Identify where the deck introduces its subject, develops the main points, adds evidence or examples, and moves toward a conclusion.
Notice which element attracts attention first and how headings, supporting text, images, and data are separated. Strong hierarchy makes the intended reading order obvious.
Compare spacing, typography, color, and repeated components across the slides. Consistent rules help varied content feel like one presentation instead of unrelated screens.
Make it your own
Begin with your audience and the decision, lesson, or action the presentation should support. Replace the topic, examples, evidence, and visuals with material you can verify, then edit every slide for one clear takeaway. You can borrow the visual direction without copying the creator's wording or message. Presenton will use this community deck as a design reference while you develop content for your own purpose.
