For German language blog
The internet was built on the ability to link information across servers. Using the fundamental standards that drove the growth of the internet and adding additional capabilities to structure semantic information, we can link engineering data across repositories.
Working in a heterogeneous set of tools sometimes feels frustrating. Users need ways to relate the information inside every tool of their toolchain, without caring much for the how.
OSLC, which stands for Open Services for Lifecycle Collaboration, is an open and scalable approach to engineering lifecycle integration. Using the Linked Data concept, OSLC provides a seamless integration between heterogenous tools through specified services and interfaces.
When working on complex systems, a small error in a single engineering data element can have a significant negative impact on the system or product design or decision-making process. The error can propagate through all areas of the engineering lifecycle, including requirements management, design, implementation, test management, and more. Customer retention is at risk.
Using the OSLC standard, we are able to define which repositories we want to connect with each other, the type of engineering data to share or use, and a common format for how we access engineering data. OSLC provides the ability to link data in a standardized way that is independent of the endpoints. Therefore, an application can implement OSLC interfaces once and can link data across all other OSLC-compatible applications, without the need to implement a new interface.
The OSLC standard was built on the powerful concepts of linked data and the web. SodiusWillert’s OSLC Connect products leverage OSLC technology to provide deep integration of engineering lifecycle applications - making the most complex data integration simple to deploy and use.
The concept of linked data ensures that the data displayed in your expert tool environment is the latest, up-to-date version. When you click or hover over an OSLC link, the actual data in the target repository is retrieved and displayed in your tool, meaning it is the current value for that information - always. That is the power of OSLC.
When you copy data, you must also copy the access controls for that data or else we lose the ability to enforce our security model and ensure that only authorized users have access. However, using OSLC, we are always using the access controls of the originating repository - guaranteeing that only authorized users can see the data.
With linked data, the creator of the information remains its owner. There is only one instance of that artifact, stored in the repository of the expert tool the owner is working with. Users working with other tools can simply use the link to see the latest version of that artifact. OSLC eliminates the need for copies and prevents uncontrolled variations.
Linking keeps the information where it was originally created. Linking allows the source repository to validate user permissions before sharing the data, thus respecting the audit and security requirements.
Use OSLC to connect your data and achieve the digital thread across domains, applications, and organizations. Our OSLC Connectors enable integration of Jira or Confluence with your OSLC-compatible tools for requirements, change, and test management, as well as modeling and implementation, for end-to-end traceability.
We are here to help. Reach out to us today with any questions you may have. We will be happy to help you learn more about how we, at SodiusWillert, can help you achieve your goals.