Reference · built on requestConnectorPLC, SCADA & MES

Plex

Sales orders, jobs, production and scrap history, inventory, and workcenter status from Plex through the connect.plex.com APIs.

Request accessPricing ↗

About

Plex is a cloud ERP and MES for manufacturers, published by Rockwell Automation. Its Developer Portal documents REST APIs under https://connect.plex.com/{collection}/{version}/{resource}, grouped into products such as Sales Orders, Job Scheduling, Production Operations Management, Inventory Operations Management, Customer Shippers, Equipment, and Plex APM. Every request carries a subscription key in the X-Plex-Connect-Api-Key header and runs against one default tenant, which Plex also calls an entity or PCN.

Through Fibric, an operator reads jobs, production and scrap entries, and workcenter status entries on a schedule, then proposes what follows: hold a job, set a workcenter status, or schedule releases on a customer shipper. You approve. Each change is sent once and leaves a receipt: what changed, why, and how to undo it.

This is a reference listing. It documents what Fibric would read from Plex and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Sales orders and order lines through the Sales Orders API: List Sales Orders, Get Sales Order, and List Sales Order Lines
  • Jobs, job operations, and operation batches through the Job Scheduling API: List Jobs, List Job Operations, List Job Operation Batches
  • Production history through the Production Operations Management API: List Production Entries, List Scrap Entries, and List Labor Entries
  • Workcenters, workcenter status entries, and workcenter events from the production-definitions and production-history endpoints
  • Containers, lots, parts, locations, receipts, and shipments through the Inventory Operations Management API
  • Customer shippers, shipper lines, and line containers through the Customer Shippers API
  • Asset tag values and elapsed-time events from Plex APM through /cm/exhaust/v1 and the /cm/odata/v2/events endpoint

Proposed actions

  • Target capability: propose holding or releasing a job through POST /scheduling/v1/jobs/{id}/hold and /release-hold
  • Target capability: propose a workcenter status change through POST /production/v1/control/workcenters/{workcenterId}/status
  • Target capability: propose scheduling releases on, or shipping, a customer shipper through the v1-beta1 Customer Shippers endpoints
  • Target capability: propose updating a customer purchase order or one of its lines through PUT /sales/v1/orders/{id}

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Hold a job when a lot fails inspection

    A deviation or scrap entry against a lot appears. The operator proposes Hold Job on the affected job, names the lot and reason, and waits for your approval before the hold endpoint is called.

    With Quality Hold, Lot Quarantine

  • Explain a workcenter's downtime, hour by hour

    Workcenter status entries and the production entries summary are read each shift. The operator lists the longest non-running stretches per workcenter and drafts a note for the supervisor.

    With Line Downtime, OEE Loss

  • Chase scrap by reason

    List Scrap Entries and List Scrap Reasons feed a per-part scrap view. When one reason climbs, the operator proposes a review and files the entries it used.

    With Scrap Rate

  • Check a promise date against the job schedule

    A sales order line's due date is compared with its jobs' scheduled operations. The operator flags lines whose jobs finish after the due date and proposes a customer notice.

    With Promise Date, Order Risk

Requirements

  • Plex IAM activated and a Developer Portal account, arranged through your Plex Champion by support case
  • An app under My Apps subscribed to the API products you need, which yields the Consumer Key and Consumer Secret
  • The X-Plex-Connect-Tenant-Id header on requests for any PCN other than your default tenant
  • Separate keys for test.connect.plex.com and production; Plex requires the two to differ
Authentication
A subscription key from an app you create in the Plex Developer Portal, sent as the X-Plex-Connect-Api-Key header; the portal account itself requires Plex IAM.

Limits

  • The API catalog lists no webhook or event subscription; Fibric finds changes by polling list endpoints with date filters
  • Several shipping and inventory operations are v1-beta1; Plex says beta endpoints have limited support duration and may change
  • The Plex APM OData events endpoint serves 40K requests per day, a filter window of at most 31 days, and $top of at most 50000
  • Date-time inputs must be UTC in the form YYYY-MM-DDThh:mm:ss.fffffffZ; dates without times are rejected

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Plex ↗

Questions and answers

Which header authenticates a Plex API request?
X-Plex-Connect-Api-Key, carrying a subscription key from an app you create in the Developer Portal under My Apps. A missing or invalid key returns REQUEST_NOT_AUTHENTICATED. X-Plex-Connect-Tenant-Id selects a tenant other than your default.
Does Plex offer a test environment?
Yes. Managed endpoints follow https://[tier.]connect.plex.com/{collection}/{version}/{resource}, and the test tier is test.connect.plex.com. Plex states that test and production keys must be different keys.
Can Fibric read machine data from Plex APM?
Yes, where Plex APM is in use. The Plex APM API returns assets, latest tag values, and elapsed-time events under /cm/exhaust/v1. The OData endpoint /cm/odata/v2/events returns data points and events with $filter, $select, and $top.
Ask about Plex

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Plex through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy