A Business and Technologies journey

As we explained in the part #1 , in MarkLogic we can store PLM objects (Part, Assembly, etc.) and product structure section as XML or JSON documents.   MarkLogic being an operational database, it provides all transactional capabilities required to perform read/write access to these objects.  Today we will deep dive into MarkLogic semantics and multi-model capabilities. From documents to semantic triples A natural product structure.... We mentioned before that the product structure management can vary from one solution to the other.  As the objective is to create a unified source of truth for all PLM data coming from internal and external (providers, partners) PLM systems, it's also important to be able to manipulate the business concepts using a shared knowledge. This is where the semantics is important.  Template Driven Extraction TDE principles The first thing is so to lift the data which currently live in documents into a semantic layer...

I have been working for manufacturers in the automotive and aerospace industries for about two years. During this period I met industry experts in PLM, technical documentation and after sales from client and partners.  This industry is quite new for me so the below post is a humble contribution which aims at illustrating how MarkLogic can quickly deliver value in such a context as we do for other industries and with minimum development. In this first part, we will present: The context and challenges What MarkLogic provides in the PLM context The specificities of the PLM data (The condition of applicability and the product structure) In the second part, we will explain how to leverage semantic and apply all the concepts mentioned before. Context and challenges Manufacturers are used to leverage distributed manufacturing using a network of  geographically dispersed suppliers, manufacturing facilities and distribution networks. Moreover the l...