01 · Process stage
PlannedMaster data definition
Identify the appropriate identification structures, intended destination markets and related numbering requirement rules.
Capabilities · Packaging, assembly & serialisation
Serialisation & aggregation
A proposed service scope for product identification, connecting unit-level data assignment, hierarchy building, data exchange and market-specific pack tracking.
PlannedCatalogue scope
Service statusPlanned
Planned.
Technical boundaries and readiness need confirmation before an activity could be presented as available.
Basis · Catalogue scope
- Status
- PlannedNo available service asserted
- Source-plan relationship
- Catalogue scopeProposed catalogue expansion
- Readiness
- Not establishedProduct and process evidence needed
- Facility roadmap
- First commercial batch target Q1 2028 · indicativeNot a service date
01 · Proposed service scope
Start with the product and its container.
Serialisation and aggregation are presented as a planned service domain. The exact product, destination market requirements, packaging hierarchy and data exchange technical route would define its scope.
The initial Boten formulation-and-filling plan identifies vial, ampoule and cartridge presentations. This serialisation domain represents a proposed expansion for technical discussion, and any such scope would require separate confirmation.
Unit-level printing, vision inspection and data hierarchy management represent distinct technical boundaries. Inclusion in a common catalogue does not establish that integrated data generation is possible for a particular pack.
Catalogue boundary
A planned catalogue for scoped evaluation. Inclusion does not establish installed, qualified, licensed or available capability.
02 · Presentation families
Match the route to the format.
| Format | Planning note | Basis | Status |
|---|---|---|---|
| Unit-level serialisation | Unique identifier printing and vision verification at the saleable unit level. | Catalogue scope | Planned |
| Case and pallet aggregation | Building a parent-child data hierarchy for secondary and tertiary packaging combinations. | Catalogue scope | Planned |
| Data exchange integration | Planned interface routing for master data receipt and event transmission. | Catalogue scope | Planned |
03 · Process scope for discussion
Make the sequence and its evidence visible.
02 · Process stage
PlannedPrinting and vision assessment
Consider the physical suitability of the chosen packaging material for distinct code application and automated camera verification.
03 · Process stage
PlannedData hierarchy design
Define the required relationship between individual primary units, secondary bundles, shipping cases and transport pallets.
04 · Process stage
PlannedEvent recording specifications
Establish the required commissioning, aggregation, parent-child linkage and potential decommissioning data event generation steps.
05 · Process stage
PlannedSystem interface configuration
Connect site-level data repositories with external routing hubs or designated repository destination systems.
06 · Process stage
PlannedException handling procedures
Define the appropriate technical steps for unreadable codes, dropped items, rejected units or parent-child hierarchy rework.
Illustrative sequence
This is a technical discussion structure, not an operating procedure, approved process flow or representation of installed equipment.
04 · Supporting services
No service stands alone.
01PlannedCatalogue scope
Primary packaging
Blisters, bottles, sachets, tubes and presentation-specific container systems.
Explore proposed scope02PlannedCatalogue scope
Secondary packaging
Cartoning, labelling, leaflet insertion and pack configuration.
Explore proposed scope03PlannedCatalogue scope
Clinical & commercial batch programmes
Distinct batch purposes, controls and applicable permissions.
Explore proposed scope05 · Readiness questions
A service claim needs a defined evidence base.
- Product and market
- Exact market requirements, coding formats and relevant numbering standards.
- Facility and systems
- Relevant installed printing equipment, vision systems and data repositories.
- Process evidence
- Defined data workflows, appropriate equipment qualification and vision system testing.
- Quality responsibilities
- Controlled data review, system access rules and event decision rights.
- Regulatory context
- Applicable market rules for data formatting, reporting and retention periods.
- Technical agreement
- Responsibilities, system ownership, data disclosure and boundaries for any engagement.
06 · Practical questions
Before a technical discussion.
Is this service currently available?
No. The service is Planned. This page is a scope proposal and does not establish an operating serialisation service.
Does this domain include data repository hosting?
No. The proposed scope considers site-level data generation and exchange interfaces, but long-term enterprise repository hosting would require separate evaluation.
What information helps define the question?
Identify the proposed product, packaging format, target market, identification standard and the technical or documentation question. Confidential data should only be shared through an agreed route.
Is there a service launch quarter?
No. No service-specific quarter is established. The project-wide indicative milestones do not commit any individual service to a start date.
Does a technical discussion establish supply?
No. Feasibility, scope, permissions, system integration evidence and any data exchange agreement would need to be established before a service commitment.
Professional enquiries
Discuss a defined question.
Describe the presentation, development question and destination relevant to the proposed scope. Do not infer service availability from this planning page.