Business Opportunities

• Variety of electronic systems manage or track part or part related information
• The Part data is enhanced, augmented, modified and reorganized while it flows from system to system in automated or manual ways
• The need to sustain the aircraft using most of this data has brought a focus on the discontinuities and variety in part data
• The solution requires that digital thread or digital tapestry be established to increase automation assist in identifying relationships of this data across all the enterprise systems
• The goal of the Common Parts Registry (CPR) is to provide an index to the various data entries and their relationships

Features

• A true MDM (Master Data Management) Solution
• Only identities are replicated into “Object-Relationship” Store
• Extensible data-model to add more systems, date-elements and relationships to establish digital-thread
• Provides services/APIs to search, validate and trace links while preserving data security of each source system

eQube^® Products used

• eQube^®-MI, eQube^®-TM, eQube^®-AG
• eQube^® Connectors used: Teamcenter SOA, Teamcenter Enterprise , AbstractER, Oracle, Excel, Text File
• Process driven MDM approach
• eQube^® API Gateway used to expose services

eQube^® Benefits

• Seamless integration of parts data from Teamcenter, SAP, ATLAS and other systems with Object-Relationship datastore
• Code-less last-mile connectivity to systems using COTS eQube^® connectors
• Rapid eQube^® solution deployment (within few months) without disrupting or deploying any component on end-systems

Business Opportunities

Lockheed Martin required the following artefacts to be submitted to the design authority and there was no mechanism available to achieve this. Lockheed Martin needed an end-to-end system to achieve this

• EDFP Report (PDF) with a title page, a system generated parts list, the PDM system derived Separate Notes List (SNL), 2D Drawings, Associated Tech Docs for some part types, 3D visualization data (JT), and Redline documents like AEAs or Record Changes
• Metadata and summary files

Features

• OOTB easy mechanism to achieve a printable report layout that includes multiple data grids spanning across pages with appropriately placed headers, footers and page breaks
• Federated data – OpenText Livelink, Teamcenter Enterprise, Teamcenter Unified, File System
• Parallel report generation using eQube^®-BI EMS mechanism
• Update provisioning attributes in the report PDF without redundant data fetch

File types embedded in the mail report PDF

eQube^® Benefits

• User interface to feed input data and generate EDFP dataset, metadata and summary file
• This eQube^®-BI report is designed using Traditional Reporting widget that facilitates printable data layout along with the ability to embed documents into the exported PDF
• Documents of various formats such as HTML, PPT, TXT, PDF, XLSX, WORD and GL can be embedded in the eQube^®-BI Report
• Workable 3D model can be embedded in the eQube^®-BI report using eQube^®-BI OOTB 3D Insight widget. Teamcenter JT Optimization is utilized by the eQube^®-BI report to embed an optimized version of the 3D model
• Facility to update provisioning attribute values in the Report PDFs

eQube^® Products Used

• eQube^®-BI and eQube^®-MI
• eQube^®-BI EMS mechanism that interfaces between eQube^®-MI and eQube^®-BI
• eQube^® Connectors used: Teamcenter Enterprise, Teamcenter Unified, Databases, Excel, File System and files
• eQube^®-API gateway and eQube^® UI services

Business Opportunities

• Too many tickets submitted for rudimentary issues
• Adient wanted to replace all level1 / level2 ticket services with the help of Chatbot
• Aim is to reduce customizations on Teamcenter for simple utilities like “enabling accounts”, “changing project members”, etc.

Features

• eQube^® process initiated by chat-bot
• eQube^®-BI report definition, filters were exposed as APIs for MI to use
• Executing eQube^®-BI reports on behalf of the user via eQube^®-MI

eQube^® Benefits

• Seamless integration of MS Team based chat-bot with Teamcenter services
• Executing eQube^®-BI reports via NLP commands on chat-bot
• Code-less last-mile connectivity to systems using COTS eQube^® connectors
• Rapid eQube^® solution deployment (within 3 months) without disrupting business or deploying any component on end-systems

eQube^® Products used

• eQube^®-BI and eQube^®-MI
• eQube^® Connectors used: Teamcenter
• API driven integration approach