A planned service line for cloud architecture, migration, deployment and operational support in customer environments. Proposed work includes database administration, monitoring, recovery planning and cost review, with support coverage and operating responsibilities agreed separately.
The expanded managed cloud offering is in development. Availability, support hours, response commitments and service levels will be defined in a separate agreement.
WHEN THIS SERVICE FITS
Business needs & intended audience
Cloud resources, application dependencies and operational tasks need clear ownership, documented procedures and a defined support scope.
Organizations with a customer-owned cloud environment
IT teams seeking operational support
Application owners planning a cloud transition
SCOPE & DELIVERY
What the engagement covers
Service scope
Cloud environment and application dependency review
Cloud architecture design, migration planning and deployment coordination
Configuration, database administration and operational documentation
Monitoring and backup configuration with agreed verification procedures
Disaster recovery planning and validation against contractually agreed recovery objectives
Resource and spending review with recommendations for cost optimization
Change coordination, issue triage and provider escalation within the contracted scope
Expected deliverables
Architecture, migration plan and responsibility matrix
Configuration records and operating procedures
Agreed monitoring, backup, recovery and change-management plan
Resource and cost review with prioritized recommendations
DEPLOYMENT & ENGAGEMENT
Define the environment and operating model.
Customer-owned cloud subscriptions
Selected provider services with authorized administrative access
Hybrid operations with agreed boundaries for customer premises
SHARED RESPONSIBILITIES
Clear ownership before work begins.
Customer responsibilities
Own the cloud account and approve access and changes
Set business priorities, security policies and recovery requirements
Retain responsibility for application decisions and provider spending
Prime Science responsibilities
Perform the operational tasks covered by the agreement
Maintain agreed procedures and coordinate approved changes
Triage issues and escalate to the relevant provider within the agreed coverage
Cloud / infrastructure provider responsibilities
Operate the underlying cloud infrastructure and platform
Provide its contracted availability, support and security controls
Handle provider-side incidents and service billing
HOW WE WORK
A clear path from requirements to operation.
Each engagement starts with a defined scope. Delivery and operational responsibilities are agreed before implementation.
01
Assess requirements
Assess the business goal, users, existing systems and the decisions the project must support.
OUTPUT
Agreed requirements and initial scope
02
Design the architecture
Compare architecture and provider options, review dependencies and assign customer, service and provider responsibilities.
OUTPUT
Architecture, responsibility matrix and delivery plan
03
Implement and validate
Implement the contracted scope and evaluate it with agreed business, technical and acceptance criteria.
OUTPUT
Project deliverables and acceptance results
04
Deploy, operate and hand over
Prepare deployment, documentation and operating procedures. Provide ongoing operations only within the agreed contract scope, with a defined handover and escalation plan.
Develop business applications and connect them to the systems you use.
Based on existing application development and system integration capabilities. Each application is scoped as a project; no proprietary SaaS product catalog is offered here.
Turn cloud requirements into a clear provider and subscription decision.
Procurement and subscription support is being developed. Any purchasing arrangement or provider authorization must be confirmed for the specific engagement.
Assess the infrastructure needed to move an AI workload toward implementation.
AI infrastructure and feasibility assessment can be scoped by project. GPU hosting is planned; hardware availability, deployment location and delivery timing require separate confirmation.