Manage the service portfolio

This path is for product owners, service owners, portfolio managers, and customer-success teams responsible for BullSequana AI as a service rather than only as infrastructure.

Outcome

You can define a service offer, onboard an accountable tenant, observe adoption and friction, connect demand to capacity, and manage change or retirement without weakening sovereignty or tenant isolation.

1. Define the service offer

Document:

• intended users and business outcomes
• included AI, Data, and Foundation capabilities
• tenant and team model
• support and escalation boundaries
• capacity, quota, and consumption rules
• security, sovereignty, and evidence commitments
• onboarding, change, and retirement expectations

Use Explore the platform to describe product domains without exposing internal component structure.

2. Onboard an accountable tenant

Identify the customer owner, service owner, tenant administrator, security contact, and platform contact. Define federation, team structure, initial entitlements, data boundaries, and the first measurable use case before opening broad access.

Use Administration and operations and Govern and administer.

3. Measure adoption and friction

Track signals that explain whether customers can reach value:

• time from request to first successful use
• active tenants, teams, and approved use cases
• repeated access, model, data, or deployment failures
• workload latency and reliability
• capacity pressure and blocked demand
• support themes and documentation gaps

BullSequana AI keeps service reporting customer-controlled and tenant-scoped without mandatory phone-home telemetry. Configure portfolio analytics so they preserve those product boundaries.

4. Connect demand to capacity

Translate onboarding and use-case demand into model-serving, accelerator, storage, database, and operational requirements. Review saturation and growth before service quality degrades.

Use Administration and operations and Foundation inference.

5. Manage change

Communicate changes through release notes, documented compatibility, maintenance windows, and owned rollback paths. Separate product adoption decisions from the technical deployment sequence, but connect both through one change owner.

Use Release notes, Upgrade and release process, and Deploy and operate.

6. Review or retire the service

Periodically review outcomes, entitlement fit, inactive tenants, unresolved risk, cost drivers, and recovery obligations. Retirement must cover access revocation, data and model disposition, audit retention, credentials, integrations, and customer communication.

You are done when

• the service has a named owner and measurable outcomes
• each tenant has accountable administrative and security contacts
• adoption signals explain friction without exposing customer content
• capacity planning is connected to demand
• changes and retirement have customer-safe lifecycle paths