Eclipse Product Lifecycle Management Platform initial contribution on GitHub
by Florent Garin
The EPLMP project, the PLM platform for Eclipse, has uploaded its initial contribution. EPLMP’s mission is to provide solutions to organize, share, search and visualize product information. Florent Garin, the project lead tells us more about EPLMP in this blog post.
EPLMP, the Eclipse Product Lifecycle Management Platform, is essentially the PLM solution from PolarSys. And, what is PLM about? It's simply about product data and processes. EPLMP’s mission is to provide solutions to organize, share, search and visualize product information.
The term ‘product’ has to be understood in its wider sense: it can refer to a manufactured product, a chemical product, consumer goods, apparel, or even a complex service offering. The related managed data can be structured (metadata) or unstructured (pdf, Office documents, CAD files, etc). The EPLMP domain model respects the ISO 10303 (step) concepts. That means two things. The first one is that EPLMP integrates all the notions needed to precisely structure the data of products: product structure with alternate and substitute parts, bill of materials, baselines, effectivity, serial numbered instances, config-spec, etc. The second one is that EPLMP has the capability to connect easily to third party PLM systems and to import/export Step models.
EPLMP offers support for cross-functional processes. Its functionalities are designed with distributed teams in mind. To give an example, wherever the name of a user appears on the screen UI (as the creator of a data entity or the recipient of a task) a special popup menu indicates his availability and proposes direct links to engage a conversation (chat, video conference). EPLMP also offers a notification system where users can subscribe to be notified by email, SMS or mobile alerts, when events are triggered. For large and distributed enterprises, this enables crucial communication for concurrent engineering processes.
Last but not least, our recent efforts have been focused on the cloud and platform aspects. An example of extensions we’ve made for cloud requirements include adding JWT and OpenID Connect as options. In doing so, we made all the necessary adjustments, (microservice architecture, health check API...) in order to achieve a worldwide auto-scalable infrastructure that supports thousands of concurrent users. We deployed this infrastructure by leveraging the various AWS PaaS solutions (EC2, S3, Aurora, CloudFront, ELB, etc).
For more information visit the project site.