What's New¶
The 2022 R1 version of Cost Insight Connect (also known as aP Connect) provides these enhancements.
Support for ENOVIA® PLM Systems¶
Automate component costing and data reporting by integrating your ENOVIA® PLM system with Cost Insight Connect.
Organizations that use an ENOVIA® PLM system can take advantage of the automation provided by the Cost Insight Generate solution by installing a new version of the Cost Insight Connect Agent.
To integrate ENOVIA 2019x with Cost Insight Connect,install a 2.2.0 or later version of the Cost Insight Connect Agent. To integrate ENOVIA 2015x.with Cost Insight Connect,install a 2.2.1 or later version of the Cost Insight Connect Agent.
For information on installing the new Agent and configuring a Cost Insight Connect connector for an ENOVIA® PLM system, see the 2022 R1 versions of the Cost Insight Connect Agent Installation Guide and the Cost Insight Connect System Administration Guide.
Support for Native Assemblies¶
Automatically analyze multi-file assemblies returned from your integrated system.
You can use Cost Insight Generate 2022 R1 to analyze native, multi-file assemblies. All the components (child parts and assemblies in an assembly) that meet the query criteria or specified in the request body of a REST request will be included in automated analysis.
The DTC Component Summary Report (renamed from DTC Part Summary Report), DFM Multiple Components Summary Report (renamed from DFM Multiple Parts Summary Report), Part Cost Spreadsheet Report, and DFM Part Summary email notification have all been extended to support assemblies. The results captured in these reports, as well as in the Cost Insight Connect Job Details view in the Job History page, reflect the aggregate results for an assembly, including both the cost of assembly operations and the rolled-up costs of its components. To generate assembly scenario results that consider all available assembly children, either:
- Submit an assembly and its children in the same Cost Insight Connect job
- Serialize the job containing an assembly to execute after the jobs that cost and publish the scenarios for all the children that you want to include in the assembly scenario costing results.
Unlike Cost Insight Design, in which users are responsible for selecting the desired scenarios for the children of an assembly, Cost Insight Generate applies logic at the time of assembly costing to optimize the completeness of children associations by applying this order of precedence:
- Assembly child included in the same job as the assembly scenario
- Assembly child in public workspace with matching scenario name to assembly
- Assembly child in public workspace with non-matching scenario name to assembly
- Missing scenario as placeholder for assembly child
If Cost Insight Generate is not able to find one or more of the children of an assembly because they were neither submitted in the job nor previously costed and published, a missing scenario is created as a placeholder for each relevant child, and the status for the costing of the assembly scenario is designated as Incomplete.
Limitations
Monolithic assemblies, assemblies referencing family table components, and the Assembly Molding Process Group are not supported in Cost Insight Connect 2022 R1 release. For more information, see Known Issues and Workarounds
Cost Insight Connect Agent REST API Extension¶
Submit part IDs, inputs, and CAD models for analysis via REST request.
The Cost Insight Connect Agent REST API runPartList endpoint replaces an agent query against the target system by allowing components to be submitted for analysis programmatically. The runPartList endpoint allows you to push parts that are ready for analysis from your system, for example - as a step in your existing PLM workflows. This endpoint alternatively allows you to separate the triggering system that invokes analysis from the source system from which data is retrieved. Additionally, the runPartList endpoint allows CAD files to be submitted via relative CAD file path or any standard aPriori inputs that are available in Cost Insight Connect Connector setup, including user-defined attributes, to be specified in the REST request at the component level. When using this endpoint, reference the supported standard attributes, which are included in this table by their internalName in the request body:
| Display Name | internalName | Category | Type |
|---|---|---|---|
| Annual Volume | annualVolume | Production Inputs | INTEGER |
| Batch Size | batchSize | Production Inputs | INTEGER |
| CAD File Name | cadFileName | PLM System | STRING |
| Check In User Email | checkInUserEmail | PLM System | STRING |
| Description | description | Admin Info | STRING |
| Digital Factory | vpeName | Production Inputs | STRING |
| Material | materialName | Production Inputs | STRING |
| Process Group | processGroupName | Production Inputs | STRING |
| Production Life | productionLife | Production Inputs | DATETIME |
| Scenario Name | scenarioName | Costing Inputs | STRING |
Any inputs provided in the runPartList REST request will be used in analysis as the highest order of precedence. This means if a CAD file path or input value is specified via REST request, it will be used over any mapped attribute on the associated part object, workflow constant, PMI attribute value, Costing Service Settings default value, or digital factory default. For more information on order of input precedence, see the “Attribute Value Precedence” section in the Cost Insight Connect System Admin Guide.