eQ at PI PLMx 2020
February 3-4, London
Product Demos
eQube MI API Gateway (Teamcenter + SAP)
Developing Web Application using eQube MI API Gateway - Teamcenter and SAP
Cloud based information exchange
eQube-MI App – File Integration (SharePoint + Database + File System)
This App built using eQube-Mi demonstrates the how users can move files stored in Oracle database as Blobs, to Office365 SharePoint.
A very simple user interface helps the user to upload these files.
The same interface also helps the user to move files present on the file system to be uploaded to SharePoint.
This also has an inbuilt dashboard using eQube-BI which shows the upload audit with successful and failed uploads.
A very simple user interface helps the user to upload these files.
The same interface also helps the user to move files present on the file system to be uploaded to SharePoint.
This also has an inbuilt dashboard using eQube-BI which shows the upload audit with successful and failed uploads.
More...
Video Gallery
eQube Mendix App (Multi PLM + ERP)
This is an example of a For Purpose application. An automotive OEM manages PLM in Teamcenter. This EOM has two key suppliers who deliver the sub-assemblies. But these suppliers do not use Teamcenter to manage their PLM data. They use two different PLM applications -ARAS and Windchill.
The OEM is the design authority and needs to see the consolidated Engineering BOM across all three PLM systems (Teamcenter, ARAS and Windchill).
In addition to the eBOM data, the OEM also needs to see information related material information of the eBOm alon with the Cost in their ERP system.
Here eQube-MI exposes Services to all the applications involved, and an intuitive user interface is built using Mendex, which consumes these services.
The user gets a single view of data spear across 4 systems and is able update data through this single view, to multiple systems, without having to login to the individual systems.
This brings a huge gain in productivity.
The OEM is the design authority and needs to see the consolidated Engineering BOM across all three PLM systems (Teamcenter, ARAS and Windchill).
In addition to the eBOM data, the OEM also needs to see information related material information of the eBOm alon with the Cost in their ERP system.
Here eQube-MI exposes Services to all the applications involved, and an intuitive user interface is built using Mendex, which consumes these services.
The user gets a single view of data spear across 4 systems and is able update data through this single view, to multiple systems, without having to login to the individual systems.
This brings a huge gain in productivity.
More...
eQube Mendix App (Navy Demonstrator)
This is a For Purpose application built as a demonstration for the Navy. All the infrastructure is built into the Amazon Virtual Private Cloud (VPC).
This is a For Purpose application built as a demonstration for the Navy. All the infrastructure is built into the Amazon Virtual Private Cloud (VPC).
The ship referred to as "Afloat" accesses applications in the VPC, and updates Flight recovery logs of planes taking off and landing on the ship. The for purpose application internally connects to multiple applications as shown in the video, and updates multiple applications using a common user interface. Behind the scenes eQube-MI API gateway orchestrates the data movement from each application and provides a simple interface for the user.
The data from this instance (Afloat) instance of the VPC is then synchronized with the Ashore instance. And in a similar manner multiple ships can synchronize data ashore. The demonstration shows a complete app which can very easily manages multiple application such as SAP, Teamcenter, SQL Anywhere as well eQube-BI for Business Intelligence built into this For Purpose application
The ship referred to as "Afloat" accesses applications in the VPC, and updates Flight recovery logs of planes taking off and landing on the ship. The for purpose application internally connects to multiple applications as shown in the video, and updates multiple applications using a common user interface. Behind the scenes eQube-MI API gateway orchestrates the data movement from each application and provides a simple interface for the user.
The data from this instance (Afloat) instance of the VPC is then synchronized with the Ashore instance. And in a similar manner multiple ships can synchronize data ashore. The demonstration shows a complete app which can very easily manages multiple application such as SAP, Teamcenter, SQL Anywhere as well eQube-BI for Business Intelligence built into this For Purpose application
More...
eQube Mendix App (Teamcenter + SAP)
This is an example of data federation between Teamcenter and SAP using eQube-MI & Mendix
This is an example of data federation between Teamcenter and SAP using eQube-MI & Mendix
This is an example of data federation between Teamcenter and SAP using eQube-MI & Mendix More often than not, it is not essential to integrate data between applications within an organization. It is more convenient to view and update related data across two or more systems on a single user interface.
In this example, the eBOM is fetched from Teamcenter, and at the same time the Material information and cost information is fetched from SAP - all related to the same eBOM information. The result is that all information connected to this eBOM can be seen by the user on a single screen. But more importantly the user can work with this consolidated information across multiple applications and edit this information.
Behind the scenes eQube-MI updates the changed data in it's home system transparently. The user no longer needs to log into each of the systems and update the data individually.
eQube-MI API gateway is used to fetch and update data. The services are exposed as ReST Services. These ReST services are consumed by Mendix. Mendix is used to build the federation application UI.
This is an example of data federation between Teamcenter and SAP using eQube-MI & Mendix More often than not, it is not essential to integrate data between applications within an organization. It is more convenient to view and update related data across two or more systems on a single user interface.
In this example, the eBOM is fetched from Teamcenter, and at the same time the Material information and cost information is fetched from SAP - all related to the same eBOM information. The result is that all information connected to this eBOM can be seen by the user on a single screen. But more importantly the user can work with this consolidated information across multiple applications and edit this information.
Behind the scenes eQube-MI updates the changed data in it's home system transparently. The user no longer needs to log into each of the systems and update the data individually.
eQube-MI API gateway is used to fetch and update data. The services are exposed as ReST Services. These ReST services are consumed by Mendix. Mendix is used to build the federation application UI.
More...
Video Gallery
Business Intelligence & 'visibility'
eQube-BI provides analysis of data on-demand, near real-time, providing single version of truth accessed under established security rules. There is no data warehouse required, the data is fetched from production systems on the fly.
eQube-BI provides analysis of data on-demand, near real-time, providing single version of truth accessed under established security rules. There is no data warehouse required, the data is fetched from production systems on the fly.
Businesses require analysis of data on-demand, near real-time, providing single version of truth accessed under established security rules. In addition, business users are not satisfied with having a static final analysis or KPI as the end state. Rather, KPIs, dashboards, or detailed reports represent the beginning of the analysis cycle. They require the ability to drill-down / drill-through the KPIs until they reach a point where 'action (s)' can be taken. Actionable insight is what they are after.
Due to the explosion of technology at dramatically lower price-points, it is creating newer business approaches from marketing to personalized promotions to providing preventive maintenance as required by devices / machines. With the advent of Industrial Internet (IIoT), inexpensive sensors are set to revolutionize medical devices, automobile, shipbuilding, gas turbine manufacturing, aerospace, defense, and retail businesses. These tectonic shifts in technology and their applications are resulting in explosion of volume, variety, and velocity of data - creating a substantial demand for Big Data analytics.
eQube-BI establishes a "Rapid-BI" infrastructure for enterprise-wide visibility. Its technological underpinnings of "in-memory" analytics, "in-context" analytics, and its innovative algorithms allows it to sift through massive amounts of data in parallel and present the necessary analysis in intuitive manner. It is able to correlate and mash-up critical information from streaming data or huge quantity of simulation / analysis data with PLM, ERP, and ALM data for Actionable Insight. Essentially, the eQube-BI architecture is ready today to effectively deal with the challenges of Big-data analysis.
Businesses require analysis of data on-demand, near real-time, providing single version of truth accessed under established security rules. In addition, business users are not satisfied with having a static final analysis or KPI as the end state. Rather, KPIs, dashboards, or detailed reports represent the beginning of the analysis cycle. They require the ability to drill-down / drill-through the KPIs until they reach a point where 'action (s)' can be taken. Actionable insight is what they are after.
Due to the explosion of technology at dramatically lower price-points, it is creating newer business approaches from marketing to personalized promotions to providing preventive maintenance as required by devices / machines. With the advent of Industrial Internet (IIoT), inexpensive sensors are set to revolutionize medical devices, automobile, shipbuilding, gas turbine manufacturing, aerospace, defense, and retail businesses. These tectonic shifts in technology and their applications are resulting in explosion of volume, variety, and velocity of data - creating a substantial demand for Big Data analytics.
eQube-BI establishes a "Rapid-BI" infrastructure for enterprise-wide visibility. Its technological underpinnings of "in-memory" analytics, "in-context" analytics, and its innovative algorithms allows it to sift through massive amounts of data in parallel and present the necessary analysis in intuitive manner. It is able to correlate and mash-up critical information from streaming data or huge quantity of simulation / analysis data with PLM, ERP, and ALM data for Actionable Insight. Essentially, the eQube-BI architecture is ready today to effectively deal with the challenges of Big-data analysis.
More...
Executing 'action' based analytics
Relevant data from multiple applications is aggregated and displayed as KPIs or dashboard. The user can interact with the dashboard and take appropriate actions on this dashboard.
Relevant data from multiple applications is aggregated and displayed as KPIs or dashboard. The user can interact with the dashboard and take appropriate actions on this dashboard.
Using eQube-BI as the front-end for analytics and eQube-MI as the orchestration engine, a solution can be built that has a unified intuitive UI (rendered in an eQ Executing 'action' based on analytics Using eQube-BI as the front-end for analytics and eQube-MI as the orchestration engine, a solution can be built that has a unified intuitive UI (rendered in an eQ Executing 'action' based on analytics
Portal or SharePoint or integrated in application UI or Mendix or any Web UI) displaying KPIs or dashboards and the capability for end users to act. First, using eQube-BI, relevant data from multiple applications is aggregated and displayed as KPIs or dashboard. Then the user can take 'action' of updating or modifying the information in BI or in a form on the UI that is carried out by eQube-MI on-behalf of that user in the underlying application (s) honoring that application's access control and security rules. The video shows Worklist items related dashboard served by eQube-BI with PLM data, rendered in a SharePoint portal, and an in-context form that can be used by the end user to take 'action'
Using eQube-BI as the front-end for analytics and eQube-MI as the orchestration engine, a solution can be built that has a unified intuitive UI (rendered in an eQ Executing 'action' based on analytics Using eQube-BI as the front-end for analytics and eQube-MI as the orchestration engine, a solution can be built that has a unified intuitive UI (rendered in an eQ Executing 'action' based on analytics
Portal or SharePoint or integrated in application UI or Mendix or any Web UI) displaying KPIs or dashboards and the capability for end users to act. First, using eQube-BI, relevant data from multiple applications is aggregated and displayed as KPIs or dashboard. Then the user can take 'action' of updating or modifying the information in BI or in a form on the UI that is carried out by eQube-MI on-behalf of that user in the underlying application (s) honoring that application's access control and security rules. The video shows Worklist items related dashboard served by eQube-BI with PLM data, rendered in a SharePoint portal, and an in-context form that can be used by the end user to take 'action'
More...
Analyzing Excels
Ability to easily analyze information from a single tab or a single excel file or in marked areas of excel or multiple tabs or multiple excel files.
Ability to easily analyze information from a single tab or a single excel file or in marked areas of excel or multiple tabs or multiple excel files.
End users are able to quickly analyze data from a single or multiple excel files. This capability can be extended to multiple tabs of the same excel file or further extended to include data from multiple tabs from multiple excel files.
Data across sheets or excels can be mashed-up together with intuitive UI.
End users are able to quickly analyze data from a single or multiple excel files. This capability can be extended to multiple tabs of the same excel file or further extended to include data from multiple tabs from multiple excel files.
Data across sheets or excels can be mashed-up together with intuitive UI.
More...
Video Gallery
Create Material BOM - SAP S-4 HANA
This demonstration shows how an Material BOM is created in SAP S/4 HANA from the engineering BOM in PLM (Teamcenter), using eQube-MI
Integration - Teamcenter, Primavera P6 & Excel
eQube-MI - Migration & Integration Teamcenter, Primavera, P6 & Excel - Dec 2018
DOORS to Teamcenter Integration
DOORS to Teamcenter Integration using eQube-MI
DOORS to Teamcenter Integration using eQube-MI
This is a scenario in which both DOORS as well as Teamcenter applications participate in workflow accross the organization, with the help of iQube-MI which helps move the data back and forth between the two applications.
This is a scenario in which the requirements is managed in DOORS application, and this information is updated in Teamcenter using eQube-MI. The updated requirement is submitted to the workflow by eQube-MI during the process of updating the change in requirements in Teamcenter for somebody in the Engineering / design team to address this requirement change for allocation of the part.
The design engineer then creates a tracelink for the part allocation, and then user sings off on the worklist in Teamcenter and completing the Part alocation process.
The moment the signoff happens eQube-MI synchronizes back the part allocation event, into DOORS.
The videos shows how the update done in DOORS is propagated to Teamcenter. It shows how the event has got submitted to the workflow, and then how the user signs of the part allocation. Once part is allocated the updated information is shown in DOORS.
It also shows how eQube-MI was configured carry out this organizational process is orchestrated between two different application systems
This is a scenario in which both DOORS as well as Teamcenter applications participate in workflow accross the organization, with the help of iQube-MI which helps move the data back and forth between the two applications.
This is a scenario in which the requirements is managed in DOORS application, and this information is updated in Teamcenter using eQube-MI. The updated requirement is submitted to the workflow by eQube-MI during the process of updating the change in requirements in Teamcenter for somebody in the Engineering / design team to address this requirement change for allocation of the part.
The design engineer then creates a tracelink for the part allocation, and then user sings off on the worklist in Teamcenter and completing the Part alocation process.
The moment the signoff happens eQube-MI synchronizes back the part allocation event, into DOORS.
The videos shows how the update done in DOORS is propagated to Teamcenter. It shows how the event has got submitted to the workflow, and then how the user signs of the part allocation. Once part is allocated the updated information is shown in DOORS.
It also shows how eQube-MI was configured carry out this organizational process is orchestrated between two different application systems
More...
Video Gallery
Teamcenter Dataset migration to SAP Document
DOORS to Teamcenter Migration
This is an example of how Requirements data from DOORS application is migrated to Teamcenter using eQube-MI.
This is an example of how Requirements data from DOORS application is migrated to Teamcenter using eQube-MI.
Requirements include Text, Rich Text, Pictures, table, OLE objects custom attributes long with the links between requirements in DOORS.
The eQube-MI process showing the visual logic used for this migration is shown and finally the migrated requirements data is shown in Teamcenter. eBOM data is shown in Tc UA that has been successfully migrated. And finally the actual eQube-MI process in the visual Business Process Modeler (BPM) of eQube-MI is shown which moved this data using this logic The data moved here is Parts, TechDocs, the relation between the two, & relation of the parts that form the BOM.
Requirements include Text, Rich Text, Pictures, table, OLE objects custom attributes long with the links between requirements in DOORS.
The eQube-MI process showing the visual logic used for this migration is shown and finally the migrated requirements data is shown in Teamcenter. eBOM data is shown in Tc UA that has been successfully migrated. And finally the actual eQube-MI process in the visual Business Process Modeler (BPM) of eQube-MI is shown which moved this data using this logic The data moved here is Parts, TechDocs, the relation between the two, & relation of the parts that form the BOM.
More...
Migration - NX to Teamcenter
This is a typical scenario where many organizations use home grown / legacy PLM systems and use NX for CAD management, and are now looking at moving to Teamcenter for their PLM.
This is a typical scenario where many organizations use home grown / legacy PLM systems and use NX for CAD management, and are now looking at moving to Teamcenter for their PLM.
Here is a demonstration of NX data and PLM data from legacy system is moved to Teamcenter. NX data as well as the metadata from legacy PLM system is inserted into a database for this purpose as a first step. The problem faced here is that the data in NX and the legacy system does not always match
eQube-BI the business intelligence software is used to compare the data between NX files and the legacy PLM system. In this example the report highlights data mismatch between legacy PLM system and NX file.
After analyzing the report comparison, 3 anomalies are highlighted. And after seeing these anomalies, it was decided how to address these situations.
1.The legacy BOM has a Part, but there is no CAD file for it. This could be a bought out item and therefore there is no CAD in NX, and therefore after moving this data to Teamcenter, the "No GEOMETRY flag is set indicating that there is no CAD file is associated with this part.
2.There are instances of excess number of occurrence of the part, in the legacy PLM system compared to the CAD system. Here also the "NO GEOMETRY" Flag is set during the migration
3.There instances of part missing in legacy system, but present in CAD system. In this case "Reference only" flag is set
4.There instances of excess occurrences in CAD system as compared to Legacy system. In such a case during the migration "Reference only" flag is set.
Using the above rules the migration is carried out. The trigger for the migration is shown. The actual Visual process that orchestrated the migration is shown, the mapping / business rule of the data shown in eQube-TM is shown
The Generic migration Process (GMP) configuration on eQube-MI is shown where sequence of migration, number of threads, batches for the migration etc. is configured.
Finally the migrated data is shown in the new application - Teamcenter.
Here is a demonstration of NX data and PLM data from legacy system is moved to Teamcenter. NX data as well as the metadata from legacy PLM system is inserted into a database for this purpose as a first step. The problem faced here is that the data in NX and the legacy system does not always match
eQube-BI the business intelligence software is used to compare the data between NX files and the legacy PLM system. In this example the report highlights data mismatch between legacy PLM system and NX file.
After analyzing the report comparison, 3 anomalies are highlighted. And after seeing these anomalies, it was decided how to address these situations.
1.The legacy BOM has a Part, but there is no CAD file for it. This could be a bought out item and therefore there is no CAD in NX, and therefore after moving this data to Teamcenter, the "No GEOMETRY flag is set indicating that there is no CAD file is associated with this part.
2.There are instances of excess number of occurrence of the part, in the legacy PLM system compared to the CAD system. Here also the "NO GEOMETRY" Flag is set during the migration
3.There instances of part missing in legacy system, but present in CAD system. In this case "Reference only" flag is set
4.There instances of excess occurrences in CAD system as compared to Legacy system. In such a case during the migration "Reference only" flag is set.
Using the above rules the migration is carried out. The trigger for the migration is shown. The actual Visual process that orchestrated the migration is shown, the mapping / business rule of the data shown in eQube-TM is shown
The Generic migration Process (GMP) configuration on eQube-MI is shown where sequence of migration, number of threads, batches for the migration etc. is configured.
Finally the migrated data is shown in the new application - Teamcenter.
More...
Video Gallery
Corporate Video
eQ's platform for enterprise information infrastructure, eQube®, establishes a Digital Backbone of integrated applications and provides enterprise-wide visibility leading to Actionable Insight.
eQube offerings in the market are: eQube-MI, the Digital Backbone, for application migration, synchronization, and integration and eQube-BI (also marketed as Teamcenter Reporting & Analytics or 'TcRA') for enterprise-wide Business Intelligence for Actionable Insight.
In the PLM context, eQube-BI/TcRA democratizes BI with the ability to let end users, use the Self-Serve feature to create powerful dashboards using simple English phrases. It puts analytics in the hands of end-users and it is tightly integrated with Teamcenter and Active Workspace for visibility/analytics that can be extended to enterprise-wide visibility
eQube platform has powerful features which allow data mashup from multiple systems. This results in dashboards which have a holistic view of the information across the organization. Big data analytics along with sensor data data can be mashed up with first class systems such as PLM and ERP, leading to unprecedented information visibility. This is truly information visibility from the "Edge to the Core".
eQube-MI integrates Teamcenter with other systems (ERP, ALM, CAPP, MES, ESM, etc.). In addition, eQube-MI synchronizes legacy systems with Teamcenter leading to orderly migration of legacy systems.
In the PLM context, eQube-BI/TcRA democratizes BI with the ability to let end users, use the Self-Serve feature to create powerful dashboards using simple English phrases. It puts analytics in the hands of end-users and it is tightly integrated with Teamcenter and Active Workspace for visibility/analytics that can be extended to enterprise-wide visibility
eQube platform has powerful features which allow data mashup from multiple systems. This results in dashboards which have a holistic view of the information across the organization. Big data analytics along with sensor data data can be mashed up with first class systems such as PLM and ERP, leading to unprecedented information visibility. This is truly information visibility from the "Edge to the Core".
eQube-MI integrates Teamcenter with other systems (ERP, ALM, CAPP, MES, ESM, etc.). In addition, eQube-MI synchronizes legacy systems with Teamcenter leading to orderly migration of legacy systems.
More...
