AIOE Intake Submission ¶

Customers should submit an AIOE Intake only if the request: 1. Cannot be completed independently and requires guidance or implementation by the AIOE team (e.g., Skill Engineering, Server-Side Agents, Service Tooling, or Operations Tooling); 2. Delivers measurable business value or improves operational efficiency.

Use the link below to submit an intake request to AIOps Enablement (AIOE):

Submit AIOE Intake Request

For detailed guidance on how to fill out each section of the intake form, refer to the AIOE Intake Guide on Confluence.

How to Fill Out the Intake Form ¶

The intake form is pre-populated with a structured template when you click the submission link. Fields marked (Mandatory) must be completed before the request will be reviewed. The form is organized into five sections:

1. Problem & Context ¶

Field	Required	Guidance
Problem Statement	Mandatory	Describe the problem or request in plain business language. Avoid technical jargon.
Current State	Mandatory	Describe the current process, tools being used, and the key pain points that this request addresses.
Primary Users / Process	Mandatory	Identify who will use the solution, who has approval authority, and how it will be used day to day.

2. Impact & Urgency ¶

Field	Required	Guidance
Impact Summary	Mandatory	Identify who is affected and at what scale: teams, users, customers, or systems.
Business Value Summary	Mandatory	Write one paragraph summarizing the value delivered if this request is fulfilled.
Urgency Level	Mandatory	Select one: Critical / High / Medium / Low.
Why Now	If Critical or High	State any deadlines, escalations, or dependencies that drive the urgency. Required when urgency level is Critical or High.

3. Functional Requirements ¶

Field	Required	Guidance
Requirement Summary	Mandatory	Provide a high-level description of what is being requested.
Functional Requirements	Mandatory	List each specific functional requirement as a bullet item, such as Item 1 and Item 2. Requirements should be clear and testable.

4. Readiness ¶

Field	Required	Guidance
Systems Involved	Mandatory	List all systems that will be touched or integrated, such as BEMS, SNOW, or Teams Bot.
Integration Requirements	Mandatory	Specify APIs, batch or stream processing needs, and external dependencies.

5. Success Measurement ¶

Field	Required	Guidance
Business KPIs	Mandatory	Define measurable KPIs such as MTTR reduction, cost savings, revenue impact, SLA improvement, or adoption rate.
Acceptance Criteria	Mandatory	Define clear, testable conditions that must be satisfied for the feature or request to be considered done and acceptable to stakeholders.
Operational Metrics	Optional	Include metrics like error rate and latency targets.

What Happens Next ¶

After submission, Mission Control uses the intake lifecycle to track the request from capture, review, and decision through execution and measurement.