Check the
documentation
Ask the
Community
Take a look
at
Academy
Cognite
Status
Page
Contact
Cognite Support
We've added two new capabilities to the GAP connector that address common challenges Petroleum Engineers face when working with GAP simulation models in production environments.
Information Model Extraction
The GAP connector now can automatically extract detailed information models from simulator model revisions, making flowsheet data accessible for analysis without requiring direct simulator access. When you upload a GAP model revision, the connector can parse the complete flowsheet hierarchy, capturing all functional blocks such as wells, pumps, valves, pipes, and tanks along with their operating parameters, physical properties, and configuration settings. The system also extracts connection relationships between equipment and graphical positioning information for visualization processes.
This extraction is configurable through a modelparsing.config.yml file where you define which properties to extract from different equipment types. You can specify common properties that apply to all equipment (like oil rates, water rates, and gas rates from solver results) as well as equipment-specific properties (such as well model types, pipeline correlations, or valve characteristics). Each property definition includes the data type, units, and the GAP address suffix used to retrieve the value from the model.
The parsing process activates automatically when a new model revision is created or when you reparse an existing revision, provided a valid configuration file exists. The connector loads the GAP model, discovers all equipment instances, extracts the configured properties along with unit information, analyzes equipment connections to generate material flow relationships, and stores the complete information model in CDF alongside the simulator model revision.
The parsing adds some processing time during model validation, with the duration depending on model complexity. If property extraction fails for individual items (due to invalid addresses, incorrect unit quantities, or wrong value types), the connector logs the errors and continues processing rather than failing the entire operation.
For configuration instructions and examples, see the public documentation.
External Dependencies Support
The GAP connector now supports a new external dependencies mode that changes how you manage simulation model components. Traditional GAP workflows require packaging everything into single .gar archive files, which can get quite large for big networks. Any change to individual components like well models or VLP tables necessitates repackaging and re-uploading the entire bundle, creating storage overhead and making frequent updates impractical.
The external dependencies mode allows you to upload .zip files containing only the GAP network files (production and injection networks) while mapping individual node dependencies like .OUT, .VLP as separate CDF files. When creating a model revision, the user provides a mapping structure that links each external dependency file to its proper location in the GAP model using the simulator's address notation. For example, you can map a PROSPER .OUT file to GAP.MOD[{PROD}].WELL[{A1}].File and a .VLP file to GAP.MOD[{PROD}].WELL[{A1}].VLPFile.
This approach enables to update individual well models, VLP tables, or other components without rebuilding entire model bundles. Different team members can work on different components independently, and you avoid duplicating unchanged files across model revisions, significantly reducing storage costs. The connector handles the complexity by downloading the network files, processing the external dependencies mapping, downloading each referenced CDF file separately, resolving file paths using the provided arguments, and assembling everything into a complete simulation model.
For complete setup instructions covering both the new external dependencies mode and the single bundle mode, refer to the the public documentation.
These features are currently in beta and subject to change based on user feedback. Access the parsed information through the existing simulator model revision endpoints, and configure external dependencies through the standard model revision creation process.
