BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//HasGeek//NONSGML Funnel//EN
DESCRIPTION:Share what it takes to run AI inside an enterprise: architectu
 res\, trade-offs\, and lessons from production.
X-WR-CALDESC:Share what it takes to run AI inside an enterprise: architect
 ures\, trade-offs\, and lessons from production.
NAME:Enterprise AI in Production: Mumbai Call for Proposals
X-WR-CALNAME:Enterprise AI in Production: Mumbai Call for Proposals
REFRESH-INTERVAL;VALUE=DURATION:PT12H
SUMMARY:Enterprise AI in Production: Mumbai Call for Proposals
TIMEZONE-ID:Asia/Kolkata
X-PUBLISHED-TTL:PT12H
X-WR-TIMEZONE:Asia/Kolkata
BEGIN:VEVENT
SUMMARY:Enterprise AI in Production: Mumbai Call for Proposals
DTSTART:20261031T053000Z
DTEND:20261031T103000Z
DTSTAMP:20261116T011725Z
UID:session/BcvEBiutsJvDkuem1dPS9t@hasgeek.com
SEQUENCE:15
CREATED:20261002T033044Z
DESCRIPTION:# Call for Proposals: Enterprise AI in Production\, Mumbai\n**
 Co-hosted at Mumbai FOSS**  \n**Saturday\, 31 October 2026 · 10 AM - 2 PM
  · Mumbai**  \n**Venue: IIT Bombay\, Powai**\n**Registration page - https
 ://hasgeek.com/fifthelephant/enterprise-ai-in-production-mumbai-edition/**
 \n\nLive streaming will be available for [The Fifth Elephant annual member
 s](https://hasgeek.com/fifthelephant#memberships). \n\n**Submit your propo
 sal — https://hasgeek.com/fifthelephant/enterprise-ai-in-production-mumb
 ai-cfp/sub**\n\n## Why this meet-up\nPutting AI into an enterprise means g
 etting through security reviews\, integrating with legacy systems\, workin
 g within budgets\, and earning the trust of the people who use it.\n\nThis
  meet-up brings together architects\, platform engineers\, data leaders\, 
 security and risk practitioners\, and delivery teams to share what that wo
 rk actually involves. Mumbai’s banks\, insurers\, payment networks\, and
  industrial and consumer enterprises provide a setting for these conversat
 ions.\n\nWe want architectures\, numbers\, trade-offs\, and failure storie
 s: what you put into production\, what broke\, and what you changed.\n\n##
  Who should submit\nSubmit if you have worked on an enterprise AI deployme
 nt and can explain its implementation and outcomes. We welcome proposals f
 rom:\n\n- Enterprise and solution architects designing integration pattern
 s\, shared platforms\, and guardrails.\n- Platform\, ML\, and software eng
 ineers operating LLM\, retrieval\, or agent workloads in production.\n- Da
 ta engineering and governance practitioners making enterprise data usable\
 , permissioned\, and auditable.\n- Security\, risk\, compliance\, and audi
 t practitioners who have approved\, blocked\, or reshaped deployments.\n- 
 Delivery and programme leaders who can connect implementation decisions to
  sustained adoption and measurable results.\n\nWe especially welcome exper
 ience from banking\, financial services\, insurance\, payments\, healthcar
 e\, telecom\, manufacturing\, and the public sector. First-time speakers a
 re welcome\; prior speaking experience is not a requirement.\n\n## What we
  want to hear about\n\n### Reference architecture and platform design\nHow
  do you build an AI platform that multiple teams can use safely? Share dec
 isions about central versus team ownership\, model gateways\, routing and 
 fallbacks\, hosted versus self-hosted models\, and build versus buy. Expla
 in the boundaries you chose and how they held up.\n\n### Integration with 
 legacy and core systems\nShow how AI works with mainframes\, ERPs\, core b
 anking systems\, and existing APIs. Topics include safe tool access\, MCP 
 or API wrappers\, transaction boundaries\, idempotency\, rollback\, and wo
 rking within change windows and release calendars.\n\n### Data readiness\,
  retrieval\, and knowledge quality\nShare lessons from enterprise RAG\, do
 cument permissions\, freshness\, metadata\, deduplication\, and retrieval 
 evaluation. We also welcome structured-data and text-to-SQL case studies\,
  including semantic layers and where they failed.\n\n### Governance\, risk
 \, and audit\nExplain how you turned policy and applicable regulatory requ
 irements into working controls. Topics include approval workflows\, model 
 inventories\, audit trails\, data residency\, sensitive-data handling\, ve
 ndor risk\, and kill switches. Be specific about the requirements and orga
 nisational context of your deployment.\n\n### Evaluation\, testing\, and r
 eliability\nHow do you know the system is working? Show evaluation sets bu
 ilt from real workflows\, regression testing across model and data changes
 \, tracing\, incident response\, and lessons from production failures.\n\n
 ### Agents and workflow automation\nWe want agents with real permissions a
 nd consequences. Share how you handle identity\, authorisation\, human app
 roval\, prompt injection\, loops\, runaway costs\, and silent errors—and
  how you measure whether automation helps.\n\n### Cost\, capacity\, and un
 it economics\nExplain inference costs\, GPU capacity\, caching\, smaller-m
 odel strategies\, and cost attribution across teams. Share the production 
 bill\, the assumptions that changed\, or why you decided to stop running a
  use case.\n\n### Adoption and operating models\nShow how team structures\
 , skills\, user feedback\, and operational ownership affected adoption. Co
 nnect organisational lessons to a specific implementation\, including use 
 cases that did not deliver the expected results.\n\nProposals may address 
 several themes or explore one in depth.\n\n## Session formats\n\n| Format 
 | Total session time\, including questions | Best suited to |\n| --- | ---
  | --- |\n| Talk | 30 minutes | One system or decision\, with architecture
 \, trade-offs\, and outcomes |\n| Deep dive | 45 minutes | A complex imple
 mentation with diagrams\, detailed examples\, or a walkthrough |\n\nChoose
  the format that fits your proposal. The editorial team may suggest a diff
 erent format during review.\n\n## What makes a strong proposal\n\n- **Prod
 uction evidence:** a system that is live\, or was live and was retired for
  reasons you can explain. Include duration in production and relevant meas
 ures such as users\, requests\, latency\, cost\, or error rates.\n- **Arch
 itecture you can explain:** components\, data flows\, trust boundaries\, a
 nd choices you rejected.\n- **Honest trade-offs:** what failed\, how you d
 iscovered it\, and what you changed.\n- **Clear constraints:** legacy syst
 ems\, security requirements\, budget\, headcount\, procurement\, or operat
 ing conditions.\n- **Useful takeaways:** specific lessons another practiti
 oner can apply.\n\nWe will decline sales pitches\, tool tours without prod
 uction context\, generic frameworks\, and principles without implementatio
 n evidence. Vendor practitioners are welcome when the proposal shares subs
 tantive implementation lessons and clearly discloses commercial interests.
 \n\nIf your work is confidential\, anonymise the organisation and use rang
 es or relative measures where necessary. Explain these limitations in your
  proposal. Submit only material you are authorised to share\; do not inclu
 de confidential information in attachments.\n\n## What to include\n1. **Ti
 tle and one-line pitch:** what will the audience learn?\n2. **Abstract\, 2
 00–400 words:** the problem\, implementation\, key decisions\, and outco
 me.\n3. **Architecture summary:** components\, data flows\, models\, and t
 ools. A diagram is welcome.\n4. **Production evidence:** scale\, time in p
 roduction\, measured results\, and how you measured them. State where figu
 res are approximate or anonymised.\n5. **Failures and trade-offs:** at lea
 st one thing that went wrong or that you would do differently.\n6. **Three
  takeaways:** specific things attendees can apply.\n7. **Audience and prer
 equisites:** who the session is for and what they should already know.\n8.
  **Preferred format:** 30-minute talk or 45-minute deep dive\, including q
 uestions.\n9. **Speaker details:** name\, role\, organisation\, short biog
 raphy\, contact details\, and a professional profile. Prior talks or writi
 ng are optional.\n10. **Disclosures and availability:** commercial interes
 ts\, confidentiality constraints\, and your availability to speak in Mumba
 i on 31 October and take part in editorial preparation.\n\nDraft slides or
  a short recorded walkthrough are optional. \n\n## Selection and preparati
 on\nThe editorial team will review proposals for relevance\, implementatio
 n depth\, evidence\, clarity\, and usefulness to practitioners. We will al
 so consider the balance of topics across the programme.\n\nShortlisted spe
 akers may be asked for clarifications or revisions. Accepted speakers shou
 ld plan for an editorial review of their slides before the meet-up.\n\n| M
 ilestone | Date |\n| --- | --- |\n| Venue announced | By Wednesday\, 7 Oct
 ober |\n| Proposals close | Sunday\, 11 October\, 11:59 PM IST |\n| Clarif
 ications and proposal revisions | 12–14 October |\n| Selection decisions
  sent | Thursday\, 15 October |\n| Selected speakers confirm participation
  | Friday\, 16 October |\n| Schedule announced | Monday\, 19 October |\n| 
 First slide drafts due | Friday\, 23 October |\n| Editorial reviews and wa
 lkthroughs | 24–28 October |\n| Final slides due | Thursday\, 29 October
  |\n| Meet-up in Mumbai | Saturday\, 31 October 2026\, 11 AM–4 PM IST |\
 n\nAll deadlines are in Indian Standard Time (IST).\n\n## Submit your prop
 osal\n\n**Submit your proposal — https://hasgeek.com/fifthelephant/enter
 prise-ai-in-production-mumbai-cfp/sub** by **18 October\, 11:59 PM IST**.\
 n\nFor questions or early feedback on an idea\, contact info@hasgeek.com o
 r 7676332020\n\nIf you have solved a difficult problem in putting AI to wo
 rk inside an enterprise\, we want to hear what you learned.
LAST-MODIFIED:20261027T033136Z
LOCATION:Mumbai - https://hasgeek.com/fifthelephant/enterprise-ai-in-produ
 ction-mumbai-cfp/
ORGANIZER;CN="The Fifth Elephant":MAILTO:no-reply@hasgeek.com
URL:https://hasgeek.com/fifthelephant/enterprise-ai-in-production-mumbai-c
 fp/
BEGIN:VALARM
ACTION:display
DESCRIPTION:Enterprise AI in Production: Mumbai Call for Proposals in 5 mi
 nutes
TRIGGER:-PT5M
END:VALARM
END:VEVENT
END:VCALENDAR
