Skip to main content
B
bkontham12-Amethyst
12-Amethyst
March 16, 2017
Solved

Integration of Integrity Modules

  • March 16, 2017
  • 2 replies
  • 4057 views

Hi All,

There are different components in Integrity like Integrity Lifecycle Manager, Modeler, Requirements connecter and Process Director. Are these Standalone installations? or Can we integrate them with each other? If so, How can these components Integrated and how they work ?

Best answer by llambert

Lifecycle Manager allows for bi-directional synchronization of Documents (commonly Requirements) between itself and Modeler through functionality in Modeler.  The integration must be selected during installation of Modeler and there is some setup on the ILM side to create fields to store the integration metadata on the ILM side.  All of this is documented in Modeler.  The use case is commonly to pull Requirements managed in ILM into Modeler for further functional and structural decomposition via SysML and UML paradigms.  Conversely, Model elements can be "surrogated" inside of ILM for traceability, and the traces can be sync'ed as appropriate. 

Requirements connector does not have any out of box integrations with other Integrity products; however, all the tools have API's or web service interfaces so an integration is possible.  Requirements connector by design is a standalone tool that connects to ILM and Doors to bidirectionally push data between those two systems or conversely can be used between two doors systems or two ILM systems or any system that supports the REQIF format. 

Each tool is a standalone installation. 

2 replies

L
llambert12-AmethystAnswer
12-Amethyst
March 16, 2017

Lifecycle Manager allows for bi-directional synchronization of Documents (commonly Requirements) between itself and Modeler through functionality in Modeler.  The integration must be selected during installation of Modeler and there is some setup on the ILM side to create fields to store the integration metadata on the ILM side.  All of this is documented in Modeler.  The use case is commonly to pull Requirements managed in ILM into Modeler for further functional and structural decomposition via SysML and UML paradigms.  Conversely, Model elements can be "surrogated" inside of ILM for traceability, and the traces can be sync'ed as appropriate. 

Requirements connector does not have any out of box integrations with other Integrity products; however, all the tools have API's or web service interfaces so an integration is possible.  Requirements connector by design is a standalone tool that connects to ILM and Doors to bidirectionally push data between those two systems or conversely can be used between two doors systems or two ILM systems or any system that supports the REQIF format. 

Each tool is a standalone installation. 

    P
    PatrickOllerton16-Pearl
    16-Pearl
    March 17, 2017

    In addition to the information Lance provided, Process Director is also standalone. It only has basic levels of integration with the other tools, specifically the ability to define URL links to data outside of Process Director.

    regards,

    Patrick

      B
      bkontham12-AmethystAuthor
      12-Amethyst
      March 24, 2017

      Hi Patrick Ollerton‌

      I looked into the Integrity Modeler and Windchill Integration overview and use cases document presented by you. It has a wonderful information.

      Is there any overview and use case document for Integrity Lifecycle Manager and Windchill Integration? If so, Can you please provide the links to it.

      Thanks,

      Bhagirath

      P
      PatrickOllerton16-Pearl
      16-Pearl
      March 25, 2017

      Hi Bhagirath,

      Pleased the information is useful.

      I'm unsure if there is a similar document for the ILM integration with Windchill. In general though, both Manage Traces apps were designed to have consistent behavior where possible. So the concepts of viewing/creating/deleting trace links and suspecting are the same, the main difference being what is linked to the Windchill Part (either a Modeler block or an ILM requirement).

      For the benefit of others, here is a summary of integrations:

      • Modeler integration with ILM
        • Lance Lambert mentioned the synchronizer tool. The Modeler Help also has lots more information including use cases. I don’t believe we have a datasheet for this specifically.
        • In the next release of Modeler (July) we also plan to have a “trace linking” capability in addition to the synch.
      • Modeler Integration with WC
      • Modeler Integration with Asset Library
        • A close integration exists  – info here and in the Modeler Help (Asset Library Integration topic).
      • Modeler Integration with Process Director
        • Integration using URL hyperlinks from PD to Modeler. More info attached.
      • ILM Integration with Windchill
        • Trace linking capability using PTC Navigate Manage Traces (ILM). Some info here, the ILM team can maybe provide more.


      regards,

      Patrick

        Terms & ConditionsCookie settingsAccessibility statement