Are you integrating labeling to more than one application?

by Maureen Perroni, on March 3, 2016

Screen_Shot_2015-11-18_at_4.35.37_PM.pngThere are definitely cases where you need to integrate your labeilng with more than one application or repository. The first and most obvious case is when you’ve got multiple different types of data that exist in different systems or applications.

You could have regulatory data in one system and transactional data in another system. It also could be important when you’ve got a centralized deployment of an enterprise application and have regional locations where labeling is being performed locally. In some cases you may need transactional data from the centralized system but also need more localized information, such as language specific components or production information that needs to be retrieved from a local system or repository. Ultimately you may need to marry the two sets of data together so that you’re getting exactly what you need to appear on the label.

Integrating with more than one application is also critical in helping to support business continuity. This would be true when a connection with a local system as a backup provides a vehicle for continuous production of labels in case the connection to the centralized system is lost.

The other case where you might need to integrate to more than one application is when global organizations are growing and acquiring other businesses. When this happens companies may need to integrate different enterprise solutions and data sources. It is quite often the case where businesses need to leverage their existing systems with net new systems to provide the data needed to deliver complete labels. Having flexible integration capabilities to support these scenarios today and tomorrow is important in enabling companies to grow and scale.

To find out more about integrating your labeling with business processes download the full Q&A today.

Integrating Labeling Q&A