Output Service

One shared job context

Output Service connects Teamcenter, NX, and custom applications to Output Suite. It receives the job and keeps files, output options, status, messages, and results together. The initiating client can identify the same job throughout processing.

Output options for the task at hand

The choices an application offers depend on the process context. This can include job type, language, group, and object type. The intended options can be requested through the public interface and offered in a custom user interface.

Different clients share the same foundation for output processing while retaining the user experience of their own enterprise application.

Provide files or collect PLM content

File-based jobs transfer their documents directly. Teamcenter jobs provide the product context from which PLM Data Collector retrieves the intended documents and metadata.

Creating a job and starting processing are separate steps. Status queries and file downloads allow the initiating application to incorporate the subsequent workflow.

Integrate with custom applications

The Open Client API makes job functions accessible to MES, ERP, and custom applications. A production order can trigger the appropriate document process; the resulting files can then be used in the established workflow.

Access and user context are aligned with the intended integration. Output Service remains the public entry point into the platform.

From individual jobs to operations

The embedded Output Tracker combines job details with a processing overview. Messages and result files support review of the output; status information helps assess operations.

Output Service can run on Windows, Linux, and in containers. Alongside Processing Hub, additional processing solutions and third-party systems can be connected.