Team Data Separation within the Tempo Manufacturing Cloud (v6.5.x)

General Environment Overview

Apprentice offers a cloud-native platform built for the needs of pharma and hosting its SaaS (Software as a Service) solution on behalf of customers. Each customer deployment includes Tempo Development, Validation, and Production environments.

• Development Environment
  • A non-GxP environment for preparation of the system configuration, materials, equipment and batch processing components which allows for iterative, application configuration and early development testing.
• Validation Environment
  • A qualified GxP environment to execute all validation activity prior to release of software configuration, processes and master data for production use.
• Production Environment
  • A qualified GxP environment used for day-to-day manufacturing operations.

Within each environment, the Tempo Manufacturing Cloud provides further visual separation of data within Tempo tenants. With 6.5.x versions of Tempo, each Tempo tenant is designed to support the equivalent of a single customer team within a specific and distinct customer site.

Apprentice product development decisions are made around the principle that multiple customer teams are logically separated into their own tenants. The deployment of multiple teams within a single tenant is not a supported use of Tempo; this use of the system is not a part of internal Apprentice performance testing and is not a future-proofed configuration when it comes to a customer’s upgrade planning.

Examples of supported uses of Tempo Environments and Tenants can be seen in Figures 1 and 2 below.

Figure 1 - Multi-Site Environment with Individual Teams (Tenants)

Figure 2 - Private Environments for a single Site with Multiple Teams (Tenants)

Benefits of separating team data

Customer users experience significant benefits to the separation of team data within different tenants, including the following:

Upgrade process based on a single site’s schedule

Rather than coordinating ongoing Tempo system upgrades across multiple sites on potentially disparate manufacturing schedules, the separation of data by site and team allows sites more flexibility when planning their upgrade schedules (see Figure 2 above). For ultimate flexibility, customers may choose to have each site team in its own environment.

User-intuitive system experience throughout the manufacturing lifecycle

When managing a complex manufacturing operation, any unnecessary uncertainty increases the chance of lost time or error. From resource staging to procedure authoring to batch execution to exception handling, the simplest way to remove uncertainty is to ensure that only the information that is relevant to a particular team is available to them. This keeps team members focused on their team’s processes and deliverables.

Customer compliance effort risk mitigation

Tenant separation ensures full data segregation and integrity by mitigating the risk for cross-pollination within cloud computing.

Support for team-specific integration capabilities

Tempo integrations allow customers to configure a secure integration with the critical systems and equipment their organization uses as part of their process. Integration-related development decisions are based around anticipated customer integration requirements for a single team’s use of each tenant.

Tenant flexibility

Additional tenants can be created to fulfill other customer needs, such as the creation of a training tenant to allow staff to learn specific Tempo versions outside of their production tenant.