Skip to content

Team Overview & Onboarding

Purpose

The purpose of this page is to capture details of onboarded teams/namespaces, and a detailed description of what activities are required when onboarding teams. See also Standard Platform Services

Teams Overview

KaaS Platform teams (Platform, Mgmt and Pilot) are owned and managed by Product Owner, Service Manager and Lead Architect.

Namespace Team Owner Data Owner Cost Center OBA ID KaaS Workspace use-case(s)
Karen AVNO AVNO 9786 F-00968593 x (Clinical) Development - IDEA squad, supporting the entire area across Submission & Labelling, Study Management, Site Collaboration, Analytics and Safety
MasterData_Products VSE DJTS 8331 F-01007721 x Global Data Office, definition and distribution of key MasterData objects.
Team is using Informaticas MDM Cloud Edition
MasterData_ReferenceData VSE DJTS 8331 F-01007721 x Global Data Office, definition and distribution of key MasterData objects.
Team is using Informaticas MDM Cloud Edition
Labs (012) PSDB PSDB TBD F-01091520 x Product Supply - Laboratory Solutions, POC's for event exchange of e.g. LIMS and PEMS metadata in samples (location, handling containerID, pH value, Particle count ID etc)
Poul QUEZ KZJE 1970 F-01095452 x HR - People and Organization, early discovery related to event distribution of HR data
Team is primarily using SAP (Successfactors) & also looking into SAP Event Mesh (Solace)
MasterData_Vendor BVKA BVKA 8331 F-01007721 x Global Data Office, definition and distribution of key MasterData objects.
Team is using Informaticas MDM Cloud Edition
MasterData_Facility RKXS RKXS 8331 F-01007721 x Global Data Office, definition and distribution of key MasterData objects.
Team is using Informaticas MDM Cloud Edition
sapint TQLN TQLN NA F-01285927 x Sapint is streaming material master data for our pilot purposes
oee ETJ ETJ 9212 F-01281867 x The purpose of the project is: Calculate Overall Equipment Efficiency (OEE) for production equipment across PS based on the data from production lines.
Team is using Informaticas MDM Cloud Edition
research_svclayer CRGD IHQA 8387 F-01301328 x The purpose of this project is Research & Development currently faces a fragmented API landscape with point-to-point integrations, inconsistent security, and limited reuse of services.
To tackle this, the Service Layer Integration (SLI) team build's a unified set of integration API’s with extensive observability built in from the start.
The SLI team will also build event integrations between services.

How to Onboard a new Team/Namespace

High-level Diagram

See also Standard Platform Services

  1. LOB Team contact initiates contact to Platform Team via mail/Teams or ServiceNow Ticket

    • The following information needs to be captured before the Team should be onboarded.
    • Team owner (approving/rejecting new users to the team).
    • Data owner (approving/rejecting usage of topics (data records) from other team and use-cases).
    • Team Name (and associated domain - ideally coordinated with LOB / domain architects to prevent Team sprawl).
    • Named users - their emails for invites, and their respective roles (Developer, Supporter, Operator)
    • Cost Center and Approver for chargeback and Product ownership of consumption based resources.
    • Signed Onboarding Agreement to ensure understanding of obligations/responsibilities of data and operations.
  2. Raise Standard CHG in ServiceNow - ServiceNow Std CHG - KaaS: Team/namespace Onboarding.

  3. Platform Team creates requests to shared NN service teams; - [ ] AD Group creation - ServiceNow Request MAN Group creation (Note: Remember to attach Manager approval!). - [ ] novoAccess Onboarding - SharePoint Guide - submit request as described in guide.

  4. Reach out to Lead Architect via mail or Teams, so he can add AD Group to Entra AD, KaaS SSO config Guide.

  5. Update configuration in 'Team Provisioning Pipeline' (access-mgmt-config-prod) with AD group Mappings and Namespace configuration, see detailed Operation Guide.

  6. Pull Request 'Configuration Review' template with Peer.
  7. Execute Team Provisioning Pipeline (access-mgmt-prod).

When NN service requests fulfilled, Inform owner and users that their roles have been setup and that they can be requested in novoAccess.

Pipeline Enablement

The How to use Data Product Pipeline Template should be read and done by LOB team.

Note! If the team/namespace has selected 'KaaS Workspace' in their Service Request, reach out to Platform Build Team via Teams for access creation and fulfilment of below steps as "LOB Team ADO Project Administrator".

  1. In AWS (AWS-NN-KaaS-PRD), Create AWS IAM Role as described here.
  2. Reach out to a LOB Team ADO Project administrator, to create a service connection as described in AWS OIDC guide.
  3. In ADO, ensure Agent Pool configuration as described here (used for Pipeline connectivity).

The Service Manager is responsible for Creating CHG and referencing PRs, Pipeline Run IDs and RITM for service requests in the CHG before closing.