OpenText Lens - Data Visibility - Centric Software Integration and Automation

Common Integration Use Cases Between OpenText Lens - Data Visibility and Centric

1. Identify and remove obsolete product development content before PLM migration

Data flow: OpenText Lens - Data Visibility → Centric

Before migrating legacy design files, specifications, and supporting documents into Centric, OpenText Lens - Data Visibility can scan shared drives, file repositories, and collaboration spaces to identify duplicate, outdated, or low-value content. Business and product teams can then migrate only the approved, current assets into Centric, reducing clutter and lowering migration cost.

• Reduces unnecessary data migration volume
• Improves quality of product records in Centric
• Supports cleaner go-live and faster user adoption

2. Detect sensitive content in product documentation before it is centralized in Centric

Data flow: OpenText Lens - Data Visibility → Centric

OpenText Lens - Data Visibility can analyze unstructured content such as supplier agreements, technical drawings, test reports, and product launch documents to identify sensitive or regulated information. That insight helps teams determine which files can be safely stored in Centric, which require restricted access, and which should remain outside the PLM environment.

• Improves information governance for product data
• Helps enforce access controls by content sensitivity
• Reduces compliance and confidentiality risk

3. Support product data cleanup before new product introduction programs

Data flow: OpenText Lens - Data Visibility → Centric

During new product introduction, teams often work with large volumes of unstructured content across engineering, design, quality, and sourcing. OpenText Lens - Data Visibility can classify and surface the most relevant documents, helping teams eliminate redundant drafts and outdated versions before they are loaded or linked into Centric. This creates a more reliable product development workspace.

• Improves version accuracy in product development
• Reduces confusion caused by duplicate files
• Speeds up review and approval cycles

4. Create a governed handoff from design repositories into PLM

Data flow: OpenText Lens - Data Visibility → Centric

When design teams store content across multiple repositories, OpenText Lens - Data Visibility can map where product-related files reside and identify the authoritative source set. Those approved assets can then be transferred into Centric as controlled product records, ensuring that only validated content is used in downstream development and launch processes.

• Establishes a clear source of truth for product content
• Improves traceability from source files to PLM records
• Supports stronger governance across design and product teams

5. Find and archive obsolete product development records after launch

Data flow: Centric → OpenText Lens - Data Visibility

After a product reaches launch, Centric contains working files, supporting documents, and historical product data that may no longer need active retention. OpenText Lens - Data Visibility can analyze exported or connected content from Centric to identify obsolete drafts, superseded specifications, and inactive project materials for archival or disposal according to retention policy.

• Reduces storage and administrative overhead
• Improves retention policy compliance
• Keeps Centric focused on active product work

6. Improve audit readiness for product development and compliance reviews

Data flow: Bi-directional

OpenText Lens - Data Visibility can help locate regulated or sensitive content across repositories, while Centric provides structured product lifecycle records and approvals. Together, they support audit preparation by linking unstructured evidence such as test results, certifications, and supplier documents to the relevant product record in Centric, making it easier to demonstrate compliance during internal or external reviews.

• Speeds up audit evidence collection
• Improves traceability between documents and product records
• Supports quality, regulatory, and legal teams

7. Reduce risk in supplier and co-development document exchanges

Data flow: OpenText Lens - Data Visibility → Centric

Supplier-submitted documents often include mixed content such as technical drawings, pricing files, and confidential agreements. OpenText Lens - Data Visibility can classify these files before they are attached or referenced in Centric, helping teams determine what should be stored in the PLM system, what should be restricted, and what should be excluded entirely.

• Improves control over third-party content
• Protects confidential commercial information
• Supports cleaner supplier collaboration workflows

8. Prioritize product content remediation during digital transformation programs

Data flow: OpenText Lens - Data Visibility → Centric

Organizations modernizing product development often need to consolidate scattered content into Centric. OpenText Lens - Data Visibility can profile existing repositories to show which product documents are complete, current, sensitive, or redundant. That insight helps program teams decide what to migrate, what to archive, and what to remediate before onboarding into Centric.

• Improves migration planning and execution
• Reduces risk of carrying legacy content issues into the new platform
• Helps business teams focus remediation on high-value content