Collaborative Development using Jama Connect

Author: Brian Kennedy

Date: 05/14/2025

Audience: Engineering Leadership. System Engineers

Products Applicable: Jama Connect®, Jama Connect Interchange™

Use Case

Collaborative Development using Jama Connect

Best Practice

Modern product development often involves managing requirements from multiple companies, each with unique perspectives and security concerns. Effective management of these diverse requirements is crucial for project success. This article explores the uses cases and recommended solutions for collaborating across multiple companies utilizing Jama Connect.

Implementation

Table of Use Cases

Jama Connect to Jama Connect Approaches

Companies collaborate on product design and development, with varying levels of integration. The following use cases describe these varying levels and, later in the article, best practices for implementing them are provided.

1. Shared Jama Connect

Companies share high-level requirements in the company’s Jama Connect system. All companies directly refine and update component-level requirements and design proposals in the single Jama SaaS environment.

2. Live Synchronized Data

Companies share high-level requirements via Technical Data Packages through a direct integration between their Jama Connect systems. Companies ingest data from each other into their workflows, refine it, and then deliver updated data back to the other company’s systems through a defined, integrated process.

3. File / ReqIF Exchange

Companies share high-level requirements for components via contract and specification documents. Using separate systems, Companies complete specifications and validation data independently, delivering contract deliverables to each other at set times instead of through continuous integration.

DETAILED SOLUTION APPROACHES

Shared Jama Connect Solution

All requirements and activities are managed in a single Jama Connect instance, ensuring maximum traceability with minimal effort. This approach supports complete versioning, approvals, and traceability for all project aspects, regardless of the source.

Best Practice Setup

1. Create separate user groups for each supplier to ensure proper access, government access restrictions, and IP protection. This facilitates auditing and compliance with regulations.
2. Create separate requirement types for the different companies collaborating to allow unique workflows and approval processes, and segregate data between them.

Benefits

• Comprehensive traceability for all project aspects.
• Complete record of requirements history.
• Unique workflows and tools for each company.
• Quick response to change requests and certification needs.
• Supports various PLM and ALM tools, creating a full Digital Thread.
• All data is included in a single instance.

Limitations

• Complete data isolation is limited because all data is in a single instance.
• Coordinated user creation and access.
• Companies must provide firewall access for data synchronization.

Live Synchronized Data Solution

The collaborative integrated solution manages requirements in multiple Jama Connect instances, integrated using the Planview Hub framework. Planview Hub connects Jama Connect to various software applications to streamline workflows and enhance productivity. It supports no-code integration, real-time data exchange, centralized visibility, and automated, flexible workflows. Companies can manage requirements in their Jama Connect instance, while Planview Hub synchronizes data between the instances, maintaining workflow continuity and the project's digital thread.

Best Practice Setup

1. Working together, all companies should identify core data and relationships to replicate for a complete system-level digital thread.
2. Individual companies need to determine the portion of data to share and synchronize back to the other participant companies and what data should remain private.
3. All participating companies must define a single Planview Hub Model to provide integration between their Jama Connect systems, resolving differences in item types and data.

Benefits

• Maximum data protection.
• Unique workflows and tools for suppliers.
• Complete record of requirements history in each instance.
• Comprehensive traceability for all project aspects.
• Quick response to change requests and certification needs across all companies.
• Supports various PLM and ALM tools, creating a full digital thread.

Limitations

• Higher setup complexity.
• Added complexity to business processes.
• The system-level digital thread won't include all the participants' data and history.
• Complete change history of other companies’ data is inaccessible from a single instance.
• Requires the use of a single Planview Hub for all companies.

File / ReqIF Exchange Solution

In the non-integrated solution, requirements are managed in the disconnected Jama Connect instances of each individual company. System-level requirements are supplied via technical data packages using ReqIF generated from the Jama Connect Interchange (JCI). Participating companies use JCI to import the provided ReqIF, then transfer needed requirements and validation/verification data back to the other participating companies using JCI generated ReqIF. JCI’s Conversation capability updates to existing content in the individual Jama Connect instances.

Best Practice Setup

1. All companies should identify core data and relationships to be sent supporting their development process. Companies can export data in ReqIF format using JCI at proper workflow points, allowing participating companies to ingest and manage the requirements in their own instances.
2. Individual companies need to identify the data to be delivered back to the other companies to support development and validation processes. After completing requirements workflows and validation activities, individual companies can export updated ReqIF files back to the other participants.
3. All companies should define the cadence and key milestones for data transfer together, ensuring full traceability of the project through JCI-generated ReqIF conversations.

Benefits

• Maximum Data Protection
• Unique workflows and tools for suppliers.
• A complete record of the requirements history is needed in each instance.
• Comprehensive traceability for all project aspects.

Limitations

• Does not support real-time collaboration
• Requires manual action to move data from one company instance to another and back.
• The primary digital thread will not include all data from other companies.
• The Complete change history of all company data is not accessible from other companies’ instances.

References

• Success Programs
• Success Catalog
• Datasheets
• Request a Solution Offering or Training from the Success Catalog

Please feel free to leave feedback in the comments below.