Starting from CAD data management , Collaborative PLM represents the stage in the evolutionary chain before complete digitalization in the further development of PDM/PLM solutions in the technical-industrial environment. Collaborative means that PLM processes are expanded beyond company boundaries. In today’s connected world, companies need to think across companies and systems. This enables internally and externally networked process coordination along the entire product life cycle in real time. Controlled via the Collaborative PLM solution, partners, customers and suppliers are integrated into the company processes. What is important here is that the way you work with external parties follows the same rules as the internal PLM processes.
PROCAD has developed PROOM, a collaborative PLM platform for document exchange that is specifically designed to meet the requirements of manufacturing companies. Virtual project rooms enable the assignment and management of user permissions so that the company can specify exactly who can see, edit or exchange what. Activity logs are kept for each project room to ensure traceability. The document exchange itself is done with just a few clicks. All changes to the documents are automatically synchronized.
Today, distributed, specialized teams often work together in technical companies. As part of such development processes, confidential documents are processed by a wide range of partners who operate outside the company’s own boundaries. For this reason, Product Lifecycle Management (PLM solution) must be viewed as an overall solution – the essence of Collaborative PLM . Professional data exchange instruments are required at the interfaces. Until now, email and FTP were the most frequently used transport methods, but they have clear disadvantages: Email traffic is insecure and not very suitable for confidential documents. During FTP transfers, file versions are overwritten in an uncontrolled manner, logging is inadequate, and only uploads and downloads are possible. However, in a business environment you often have to deal with very large files that need to be shared. Document management, control, versioning, rights assignment and setting up individual project rooms are also required.
Data exchange platforms like Dropbox originally come from the private sector, but now often offer a professional corporate version. Although the idea of confidential documents is taken into account by allowing different data rooms to be set up for dedicated user groups, they are still not tailored to the specific requirements of the technical environment.
Security for confidential documents must take place at different levels: both during data transfer and during logged changes to files. The biggest disadvantage of common data exchange platforms is certainly that they are not embedded in the company’s existing collaborative PLM landscape. This means that there is still a gap between the system landscapes. The processes involved in exchanging and working on construction plans, CAD drawings, change orders, tenders and other technical documents are not seamlessly connected.
Virtual data rooms create the bridge for technical companies to access files in a controlled manner. A virtual data room is a digital platform for the quick and secure exchange of information and for increasing the efficiency of the exchange of information between different project members. Such platforms are suitable for use in communication-intensive processes, such as between design departments and external (development) partners. Such development partnerships are about collaborative work, confidentiality and integration into existing systems. The demands on the exchange of information are increasing due to the currently growing technical complexity. External partners, customers or suppliers on the extended workbench must be able to work together consistently and reliably, without system or media breaks. This is where document exchange platforms for professional users come in by connecting processes between internal and external. Such virtual data rooms allow file exchange across system and company boundaries to be carried out securely and comprehensibly.
Particularly in technical companies, there are already established structures, procedures and approval processes that a virtual project room can reflect well. The head of a digital project room can use a sophisticated access authorization concept to precisely control which project members are allowed to do what with the documents and when. All activities can be tracked using integrated monitoring functions and dedicated user rights. By synchronizing, for example, CAD data or technical specifications across the project room, designers and development partners can access the current files at any time. Since the files are not located locally, possibly in an employee’s email inbox, a virtual project room means you are independent of the presence/absences and processing status of other project members. The sync function also provides the option to edit files offline.
PROOM’s virtual project rooms allow those involved in the project to concentrate on the content and not on the administration. This means projects are carried out faster and more successfully and compliance guidelines are adhered to.
Cross-location collaboration for companies that use a PDM/ PLM system at multiple locations is made possible (as with PRO.FILE) via a so-called “Enterprise Transaction Oriented Replication” (ETOR). This provides globally distributed teams with a scalable Collaborative PLM solution.
This is also necessary in view of today’s practice, as not only large companies but also medium-sized manufacturers in mechanical and plant engineering or in the automotive supply industry carry out design and development at internationally distributed locations. This collaboration in teams distributed around the world needs to be coordinated, synchronized and enabled quick access to current data for everyone involved.
ETOR solves this by replicating the development data. This means that all data is provided locally at each location. In order to process CAD data, open, read, display and save it, there is no need to set up a transmission to the central server. Modern database technology ensures that the basic idea of product life cycle management (PDM/ PLM system ), according to which all users work on a common database, is still adhered to.
With a high-performance database, each location can work with its own database and also keep all CAD models and other development documents completely locally. This means that reading, displaying and saving always take place on site. The local server then transfers the data to all other locations in the background. This gives them even more autonomy because even if the connection to the central PLM server is interrupted, they can still continue working. Once the line is back up, the locations and headquarters automatically sync the data.
Data replication at distributed locations significantly simplifies development collaboration in globally distributed teams. A prerequisite is always reliable synchronization between the central database and local changes. If this is the case, distributed teams can continue working even in the event of line interruptions without endangering the data integrity of the entire system. You can replace entire assemblies with one click – safely, error-free and without change conflicts.
A collaborative PLM solution should clearly map cross-company workflows. The designer can create product folders for each product in the PDM/ PLM system according to the structure specified in the CAD system, e.g. AutoCAD, Autodesk Inventor, Creo, Solid Edge or Solidworks. These are filled with drawings, parts lists , technical documents, calculations, etc. A PLM ordering process then usually starts with an incoming order. The project manager creates the new order in the ERP system under a unique number, which is then automatically transferred to the PDM/PLM software with the metadata of the order (customer, product type and number). An order folder with this number will be created there. The designer receives the specification of the order, copies the project structure from the product folder to the order folder and then fills it with life.
The latest versions of the drawings are always documented in the product folder, while the order folder shows what was actually built. Once the order has been put together, the drawings are sent to production. A directory in the PDM/ PLM system records the production status of the product. This provides evidence of when which drawing was sent to the customer or to production in which version. The company can seamlessly document the entire ordering process from order receipt through design to production.
Here again, the property of a PDM/PLM system as a product data backbone proves to be invaluable, as it makes tasks and version statuses of documents traceable and archived at any time during an order. This enables the company to handle its order processes efficiently and deliver finished products to the customer on time. Whether those involved are located at home or abroad, whether they are local or globally distributed teams, does not matter at this point.
Cookie | Duration | Description |
---|---|---|
__hssc | 30 minutes | HubSpot sets this cookie to keep track of sessions and to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. |
__hssrc | session | This cookie is set by Hubspot whenever it changes the session cookie. The __hssrc cookie set to 1 indicates that the user has restarted the browser, and if the cookie does not exist, it is assumed to be a new session. |
_GRECAPTCHA | 5 months 27 days | Google Recaptcha service sets this cookie to identify bots to protect the website against malicious spam attacks. |
cookielawinfo-checkbox-advertisement | 1 year | Set by the GDPR Cookie Consent plugin, this cookie records the user consent for the cookies in the "Advertisement" category. |
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
CookieLawInfoConsent | 1 year | CookieYes sets this cookie to record the default button state of the corresponding category and the status of CCPA. It works only in coordination with the primary cookie. |
elementor | never | The website's WordPress theme uses this cookie. It allows the website owner to implement or change the website's content in real-time. |
JSESSIONID | session | New Relic uses this cookie to store a session identifier so that New Relic can monitor session counts for an application. |
PHPSESSID | session | This cookie is native to PHP applications. The cookie stores and identifies a user's unique session ID to manage user sessions on the website. The cookie is a session cookie and will be deleted when all the browser windows are closed. |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
Cookie | Duration | Description |
---|---|---|
__cf_bm | 30 minutes | Cloudflare set the cookie to support Cloudflare Bot Management. |
_icl_visitor_lang_js | 1 day | WPML sets this cookie to store the redirected language. |
drift_aid | 1 year 1 month 4 days | Drift sets this cookie as a session identifier token. It is used to tie the visitor on your website to a current website session within the Drift system. This enables session-specific features, such as popping up a message only once during a 30 minute session to prevent a disruptive experience. |
drift_campaign_refresh | 30 minutes | Drift sets this cookie as a unique ID for the specific user. This allows the website to target the user with relevant offers through its chat functionality. |
driftt_aid | 1 year 1 month 4 days | Drift sets this cookie as an anonymous identifier token. As people come onto the site, they will get this cookie. |
li_gc | 5 months 27 days | Linkedin set this cookie for storing visitor's consent regarding using cookies for non-essential purposes. |
lidc | 1 day | LinkedIn sets the lidc cookie to facilitate data center selection. |
UserMatchHistory | 1 month | LinkedIn sets this cookie for LinkedIn Ads ID syncing. |
wp-wpml_current_language | session | WordPress multilingual plugin sets this cookie to store the current language/language settings. |
wpml_browser_redirect_test | session | This cookie is set by WPML WordPress plugin and is used to test if cookies are enabled on the browser. |
Cookie | Duration | Description |
---|---|---|
__lotl | 5 months 27 days | Lucky Orange sets this cookie to identify the traffic source URL of the visitor's original referrer, if any. |
_lo_uid | 1 year 1 month 4 days | Lucky Orange sets this cookie as a unique identifier for the visitor. |
_lo_v | 1 year | Lucky Orange sets this cookie to identify the total number of visitor's visits. |
_lorid | 10 minutes | Lucky Orange sets this cookie to record the current ID of visitors. |
Cookie | Duration | Description |
---|---|---|
__hstc | 5 months 27 days | Hubspot set this main cookie for tracking visitors. It contains the domain, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session). |
_fbp | 3 months | Facebook sets this cookie to display advertisements when either on Facebook or on a digital platform powered by Facebook advertising after visiting the website. |
_ga | 1 year 1 month 4 days | Google Analytics sets this cookie to calculate visitor, session and campaign data and track site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognise unique visitors. |
_ga_* | 1 year 1 month 4 days | Google Analytics sets this cookie to store and count page views. |
_gcl_au | 3 months | Google Tag Manager sets the cookie to experiment advertisement efficiency of websites using their services. |
_gd_session | 4 hours | This cookie is used for collecting information on users visit to the website. It collects data such as total number of visits, average time spent on the website and the pages loaded. |
_gd_svisitor | 1 year 1 month 4 days | This cookie is set by the Google Analytics. This cookie is used for tracking the signup commissions via affiliate program. |
_gd_visitor | 1 year 1 month 4 days | This cookie is used for collecting information on the users visit such as number of visits, average time spent on the website and the pages loaded for displaying targeted ads. |
AnalyticsSyncHistory | 1 month | Linkedin set this cookie to store information about the time a sync took place with the lms_analytics cookie. |
CONSENT | 2 years | YouTube sets this cookie via embedded YouTube videos and registers anonymous statistical data. |
hubspotutk | 5 months 27 days | HubSpot sets this cookie to keep track of the visitors to the website. This cookie is passed to HubSpot on form submission and used when deduplicating contacts. |
ifso_visit_counts | 1 year | If So sets this cookie to store number of visits. |
ln_or | 1 day | Linkedin sets this cookie to registers statistical data on users' behaviour on the website for internal analytics. |
vuid | 1 year 1 month 4 days | Vimeo installs this cookie to collect tracking information by setting a unique ID to embed videos on the website. |
Cookie | Duration | Description |
---|---|---|
bcookie | 1 year | LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser IDs. |
bscookie | 1 year | LinkedIn sets this cookie to store performed actions on the website. |
li_sugr | 3 months | LinkedIn sets this cookie to collect user behaviour data to optimise the website and make advertisements on the website more relevant. |
VISITOR_INFO1_LIVE | 5 months 27 days | YouTube sets this cookie to measure bandwidth, determining whether the user gets the new or old player interface. |
YSC | session | Youtube sets this cookie to track the views of embedded videos on Youtube pages. |
yt-remote-connected-devices | never | YouTube sets this cookie to store the user's video preferences using embedded YouTube videos. |
yt-remote-device-id | never | YouTube sets this cookie to store the user's video preferences using embedded YouTube videos. |
yt.innertube::nextId | never | YouTube sets this cookie to register a unique ID to store data on what videos from YouTube the user has seen. |
yt.innertube::requests | never | YouTube sets this cookie to register a unique ID to store data on what videos from YouTube the user has seen. |
Cookie | Duration | Description |
---|---|---|
_an_uid | 7 days | No description available. |
_gd1687981540406 | session | Description is currently not available. |
6suuid | 1 year 1 month 4 days | No description available. |
ifso_page_visits | 1 year 1 month 4 days | No description available. |
oribi_cookie_test | session | Description is currently not available. |
oribili_user_guid | 1 year | Description is currently not available. |