Seal vs Arena QMS

1Arena QMS and Seal, side by side.

Arena and Seal are designed for different kinds of product. Arena QMS is a product-centric quality system: it links quality issues and change processes to the active product record, structured as a bill of materials, and runs on one cloud platform with Arena PLM for companies that design high-tech and medical device products.¹² Seal is the GxP operating system for biopharma: teams configure laboratory, manufacturing and quality workflows on one platform around a shared ontology, in which a sample belongs to a batch and a result comes from a test. Where a biopharma company also makes devices or combination products, Seal’s device workflows keep each unit’s record as built.

2What Arena QMS is built for.

Arena QMS is built for companies that design and make hardware, above all medical devices, and want quality records connected to the product design. Arena describes itself as Arena by PTC, a cloud-native PLM and QMS provider.³ PTC completed its acquisition of Arena Solutions on 19 January 2021 and placed Arena in a software-as-a-service business unit with Onshape and Vuforia.⁴ Arena’s industries, listed under the heading “Designed for Complex Technology Products”, include medical devices and biotechnology alongside aerospace and defence, clean tech, consumer and high-tech electronics, semiconductors and electric vehicles.⁵ Arena calls its QMS “the clear choice for medical device manufacturers”.⁶

Arena QMS documents and tracks closed-loop processes for device master records, design history files, training records and CAPAs in the context of the product record and bill of materials, on a multi-tenant cloud platform.⁶ Its quality processes connect to parts, BOMs, drawings and documents, with quality templates linked to change processes and help desk integration for complaints, and Arena says more than 1,500 companies use its solutions.⁷ Engineering change requests and orders run with automated approvals, and no-code automations start the change and quality processes that follow.⁸ Arena Tickets track issues linked to affected product records, quality actions, requirements and engineering changes.⁹ Supply chain partners work in the same system with role-based access, and Arena says 92% of top EMS providers access Arena customer systems.¹

For validation, Arena Validate supplies documentation for each Arena PLM and QMS release, with early release notes carrying a risk assessment and impact analysis and more than 1,600 user requirements and test cases; Arena does most of the validation work and leaves the customer to determine its intended uses.¹⁰ Arena’s AI summarises and compares files, produces AI item redlines across revisions and summarises training documents,⁸¹¹ and its Supply Chain Intelligence adds AI-driven electronic component intelligence to product development.⁶

3As designed and as built.

Arena keeps the record of what a device should be; Seal’s device workflows keep the record of what each unit was.

In Arena, a change or a quality issue attaches to the product record as designed. Engineering changes are reviewed in context with the items, BOMs, drawings and SOPs they touch,⁸ issues link to the affected product records,⁹ and the product record forms a complete device master record: components, approved manufacturer lists, labelling and packaging specifications, and manufacturing and test instructions.¹

In Seal, the approved definition becomes guided execution, and the record accumulates around the actual serial or lot as the work happens. In the example in Seal’s eDHR blueprint, order MO-0814 is for 240 Revision G devices. The record for pump P4-26-001842 shows controller board PCB-77, serial 44871, installed at operation 110 and torqued to 4.2 N·m with tool TQ-08; firmware 3.8.1 verified by checksum; UDI label v12; and final inspection INS-1044 with all 18 characteristics accepted before QA release. A torque exception, NC-0221, was resolved with verified rework, and the record keeps the original failed state beside the rework.

Seal freezes the applicable configuration when execution begins, so each serial keeps the revision it was built to, and an engineering change identifies the open orders, inventory, training, inspection programmes, labels and released populations it affects before it takes effect. A finding about a component lot, a tool or a firmware version traces forward to the units that used it, and a field complaint traces back to the build evidence. Seal’s blueprint sets the boundary with PLM explicitly: PLM may own design structures and engineering changes, and ERP demand and inventory, while Seal can own the effective manufacturing configuration, execution, genealogy, inspections, exceptions and disposition. Paradromics runs its brain–computer interface manufacturing travelers and quality records in Seal; its customer story reports 80% less operator paperwork and 90% less traveler review time for engineers.

4Devices, batches and who each is for.

Arena is organised around items and assemblies; a biopharma operation is organised around lots, batches, samples and specifications. That difference matters more than any single feature.

Arena’s biotechnology page addresses biotech companies through design controls for design history files and device master records, quality processes connected to the product record, and collaboration with suppliers and outsourced manufacturing partners.⁵ Its medical device page argues that document-centric quality tools fail to manage the full product record or bill of materials.¹² For a device or diagnostics maker whose product has a BOM, that model fits naturally.

Seal starts from the batch. Laboratory, manufacturing and quality work share one set of records, so an out-of-specification investigation links back to the sample, method, instrument file and specification behind the result, a deviation points to the step that produced it, and batch disposition remains a distinct, authorised decision. A drug or biologic manufacturer evaluating Arena should ask how batch genealogy, laboratory results and release would be represented; a device maker evaluating Seal should ask how parts, BOMs and engineering changes from its PLM reach the build.

5Where Arena QMS is the better fit.

Arena is the better fit for companies that design hardware and want quality tied to the product record they engineer.

• You design medical devices, diagnostics or electronics and manage parts, BOMs and engineering changes as the backbone of your quality system.⁶⁸
• You want PLM and QMS from one vendor on one cloud platform.²
• You work closely with contract manufacturers and suppliers who need controlled access to parts of the product record, with information such as cost hidden.¹¹³
• You want the vendor to supply validation documentation, requirements and test cases for each release.¹⁰
• You source electronic components and want component intelligence inside product development.⁶

6Where Seal is the better fit.

Seal is the better fit when the product is made in batches and released on test results, or when device production evidence should sit on the same records as quality.

• You make drugs, biologics or combination products, and your quality decisions turn on batches, samples, specifications and results.
• You want the record of each lot or serial captured as the work happens: components, equipment, inspections, labels, exceptions and release, with rework that keeps the original failed state.
• You want a corrective action released as a change to the executed workflow, with its verification, while each unit keeps the revision it was built to.
• You want Neil to prepare the work: the configuration from your device master data and procedures, the population a finding affects and the changeset with its verification cases. Your team tests and approves each change before it goes live. In line with the EU’s draft GMP Annex 22 on AI, Neil is not used in GMP execution. It helps set up configuration, which your team verifies and releases under change control.

7Running Seal alongside Arena QMS.

Arena can stay the design and change record while manufacturing execution or a quality process runs in Seal. No dedicated Arena connector exists on Seal’s integrations list. Seal’s REST API and Scripts are the general route, and Seal can review Arena’s interfaces with you. On Arena’s side, the Developer Platform provides a RESTful API with OAuth 2.0, single sign-on and webhooks, a Data Extract Service for mass export and a low-code integration engine, and Arena Connect, an embedded integration platform, links Arena to ERP, MES and other systems.¹⁴

Arena’s webhooks and outbound event integrations can send data to a target system, which can write to Seal through Seal’s API; or a Seal Script, versioned Python run after an event or on a schedule, can call Arena’s API.¹⁴ Either way, agree credentials, direction and failure handling first, and treat Scripts like any configuration: changed through a changeset and tested. Each interface needs more than a field map: object identity, which system is authoritative, acknowledgement, duplicate handling, behaviour during an outage and reconciliation. That design is part of validation, because it decides which system a reviewer trusts when values disagree or messages arrive late. Start by reading the released revision and BOM, and treat any write-back to Arena as a separate decision; the regulatory guide sets out the checks.

8Moving from Arena QMS to Seal.

For most device companies the move is partial: design stays in Arena, and the build moves to Seal one device at a time.

1. Choose one representative device and run it from component receipt through serial assignment, assembly, inspection, a failed check, approved rework, UDI labelling, review and release.
2. Bring the released BOM revision, routing, work instructions, inspection plan, label templates and a recent traveler. Sample material works for a first look, and an NDA covers anything confidential.
3. Neil proposes the device configuration, the guided steps and their review states from that material. Once the scope is agreed and the inputs received, Seal prepares the first working process and its supporting validation pack within 48 hours; production release follows your intended-use assessment and quality controls.
4. Trace backward from the released serial and forward from a component lot, then rehearse a calibration failure, incorrect firmware, a label reprint, missing supplier evidence and a field complaint.
5. Agree which records move and which stay retrievable in Arena. Design history files and device master records can remain there, and representative records are reconciled before you rely on the new workflow.

Retention obligations continue for the records that stay in Arena. The eDHR and medical device blueprints show the workflows in detail.