API Connections
Use the Gocious Open API for scoped data exchange, directly or through your integration platform. Access and mappings are defined for your use case.
Product planning integrations
Connect Strategic Planning to Execution with Integrations
How do product plans stay current when delivery happens in other systems?
Gocious supports the product portfolio planning lifecycle from new product initiatives (NPIs) through decision, monitoring, and adjustment. Configured integrations send approved decisions and plans to execution systems and return supported status and change updates to planning.
GociousUnapproved and approved NPIs, roadmap decisions, alternatives, and portfolio context
↓ Approved decisions and plans to execution
↑ Supported status and change updates to planning
Execution and engineering systemsDetailed delivery plans, active work, product configuration, and design records
ERPSelected business inputs
CRMSelected customer context
Clear ownership across the planning lifecycle
What Gocious Holds and What Stays in Other Systems
Gocious: Product Portfolio Planning
Unapproved NPIs: Keep new product initiatives and plans together so leaders can compare them, prioritize them, and decide where to invest.
Approved NPIs: Maintain approved initiatives on the roadmap. Receive supported execution status and change updates to monitor progress, adapt the roadmap, and inform the next set of NPIs.
Alternatives: Keep alternatives to current NPIs so leaders can compare the current roadmap with alternative initiatives and roadmap options.
Other Systems: Execution and Product Detail
Execution systems hold detailed delivery plans, work items, assignments, and progress for initiatives that are being executed.
PLM and engineering systems retain product and module configuration, design details, and formal engineering records.
Connected lifecycle: New product initiatives → Decide → Monitor → Adjust. Gocious sends approved decisions to execution and receives supported status and change updates to complete the planning cycle.
From New Product Initiative to the Next Portfolio Decision
How do decisions and execution feedback complete the product portfolio planning lifecycle?
-
New Initiatives
Bring unapproved NPIs and alternatives into Gocious to compare priorities, assumptions, and investment choices.
-
Decide
Approve and fund the selected initiatives, place them on the roadmap, and send the decision to the execution system.
-
Monitor
Manage detailed delivery in execution systems and return supported status and change updates to the approved roadmap in Gocious.
-
Adjust
Use execution feedback to adapt the roadmap, compare alternatives, and inform the next set of NPIs.
Choose the right implementation path
Integration Options for Your Environment
The platform supports different connection methods. We assess the system, workflow, and security requirements before recommending an approach.
Batch and File Transfers
Exchange agreed data through scheduled batches or files when that approach fits your systems. Format, validation, and transfer timing are scoped together.
Available Connectors
An out-of-the-box Jira Cloud integration is available. We assess its fit and configuration; other systems may require a bespoke connection.
What Your Integration Implementation Includes
What needs to be agreed before the connection goes live? We define the workflow, assess your systems—including legacy systems where feasible—and scope implementation with you.
- Workflow and dataDefine the planning process and records that need to connect.
- Mappings and update directionAgree fields, data direction, update timing, and exception handling.
- System ownershipConfirm which system owns each record and where changes are made.
- Security and accessDefine authentication, permissions, and your security requirements.
- Testing and supportScope configuration or development, validation, rollout, and ongoing support.
Integration Use Cases
Planning-to-execution is the primary connection. Additional use cases are evaluated against your data, systems, and implementation requirements.
Project Management and Execution Systems
Connect approved and funded plans with delivery work and return supported milestone or status updates. Detailed task management stays in the execution system.
Customer and CRM Systems
Bring selected customer requests, service signals, or sales context into demand planning through a scoped connection.
ERP and Business Systems
Bring selected cost, revenue, availability, or business assumptions into planning. Operational and financial records stay in the underlying system.
PLM and Engineering Systems
Exchange selected planning context with engineering systems. Detailed engineering records and formal change control stay in those systems.
Frequently Asked Questions
What integrations does Gocious support?
Gocious supports scoped integrations through APIs, batch or file transfers, and available connectors, including an out-of-the-box Jira Cloud integration. We work with you to assess requirements and implement an approach suited to your systems and workflow.
How do Gocious integrations connect planning with execution?
Gocious holds unapproved NPIs for comparison and investment decisions, approved NPIs on the roadmap, and alternatives to the current plan. Approved decisions can connect with the execution system where teams manage detailed work. Supported status and change updates can then return to Gocious to support monitoring, roadmap adjustment, and the next set of product decisions.
Which system remains the source of truth?
Gocious maintains the product portfolio plan, including unapproved and approved NPIs, roadmap decisions, alternatives, and related planning context. Execution systems manage detailed delivery for active work. PLM and engineering systems retain product and module configuration, design details, and formal engineering records. Field ownership, mappings, and update rules are agreed during implementation.
Does Gocious work only with Jira?
No. Jira Cloud is an available out-of-the-box option. Other systems can be evaluated for API, batch, file-based, or bespoke integration based on the workflow, data access, and technical environment.
How does the Jira Cloud integration work?
Product and portfolio teams maintain planning context in Gocious while development teams manage detailed work in Jira Cloud. Supported Gocious planning items can be connected with corresponding Jira work, and supported execution status can inform the Gocious planning view. Exact mapping and synchronization behavior depend on configuration.
Has Gocious connected with PMA, Polarion, or Inspire Planner?
Yes. Gocious has previously been integrated with PMA from Cataligent, Siemens Polarion, and Inspire Planner, a Salesforce-native project-management application. The Inspire Planner connection was implemented through MuleSoft. These are prior customer-specific examples, not a promise of an out-of-the-box connector for each system.
What information moves between Gocious and another system?
For execution systems, an integration may send approved and funded decisions or plans from Gocious to the relevant delivery work and return supported status and change updates. Those updates help product leaders monitor the approved roadmap, compare alternatives, and inform the next set of NPIs. Exact objects, fields, mappings, update behavior, and configuration depend on the implementation.
Does Gocious provide an Open API?
Yes. Gocious provides an Open API for scoped data exchange and customer-specific integrations. Each implementation depends on the target system, workflow, data requirements, security, technical feasibility, and implementation requirements.
Is the Open API the same as a prebuilt connector?
No. A prebuilt connector is an existing integration designed for repeatable use. An Open API implementation may require discovery, mapping, middleware or development work, testing, security review, and ongoing support planning.
Can Gocious connect to PLM, ERP, or CRM systems?
Scoped connections may exchange selected data with these systems. We evaluate the use case, data access, direction, security, and technical feasibility before defining implementation. This does not imply a packaged connector for every system.
Does Gocious replace project execution, PLM, or ERP systems?
No. Execution systems manage detailed delivery, PLM manages detailed engineering and product records, and ERP manages operational and financial processes. Gocious provides the strategic product portfolio planning layer alongside those systems.
Why are integrations important for complex manufacturers?
Complex manufacturers plan across physical products, software, capabilities, modules, platforms, regions, long lifecycles, dependencies, and changing assumptions. Integrations help keep supported development progress connected to that broader planning context.
Can Gocious support batch or file-based integrations?
Yes. Batch or file-based exchange can be used when it fits the implementation. We agree the records, format, validation, transfer method, and update schedule for the connection.
Can Gocious work with legacy systems?
Legacy systems can be assessed for integration. The available data access, export methods, security requirements, and technical constraints determine whether an API, file transfer, or bespoke approach is feasible.
Let’s map the connection
Connect Planning and Execution Without Replacing Your Stack
Bring the systems you use and one workflow you want to connect. We’ll discuss the data, implementation approach, and scope with you.