This commit is contained in:
Ralph Soika 2026-02-20 16:53:55 +01:00
parent 7d080d7885
commit 705d3a6edf

View file

@ -198,7 +198,7 @@ Address: <itemvalue>customer.country</itemvalue> <itemvalue>customer.zip</itemva
<item name="customer.ref" <item name="customer.ref"
type="custom" required="false" type="custom" required="false"
path="workitemlink" path="workitemlink"
options="($workflowgroup:Product)((type:workitem) OR (type:workitemarchive))" options="($workflowgroup:Customer)((type:workitem) OR (type:workitemarchive))"
label="Customer:" /> label="Customer:" />
<item name="product.ref" <item name="product.ref"
type="custom" required="false" type="custom" required="false"
@ -1877,7 +1877,7 @@ Created: <itemvalue>$created</itemvalue>
<bpmn2:outgoing>sequenceFlow_vqv8cw</bpmn2:outgoing> <bpmn2:outgoing>sequenceFlow_vqv8cw</bpmn2:outgoing>
<bpmn2:outgoing>sequenceFlow_XAS6SA</bpmn2:outgoing> <bpmn2:outgoing>sequenceFlow_XAS6SA</bpmn2:outgoing>
</bpmn2:exclusiveGateway> </bpmn2:exclusiveGateway>
<bpmn2:task id="task_0WNAdA" imixs:processid="1210" name="EXPORT COMPLIANCE Check"> <bpmn2:task id="task_0WNAdA" imixs:processid="1210" name="EXPORT RESTRICTION Check">
<bpmn2:extensionElements> <bpmn2:extensionElements>
<imixs:item name="txteditorid" type="xs:string"> <imixs:item name="txteditorid" type="xs:string">
<imixs:value><![CDATA[form_basic]]></imixs:value> <imixs:value><![CDATA[form_basic]]></imixs:value>
@ -2105,7 +2105,7 @@ Betrag: <itemvalue>_amount</itemvalue> (Brutto € <itemvalue>_amount_brutto</it
<item name="customer.ref" <item name="customer.ref"
type="custom" required="false" type="custom" required="false"
path="workitemlink" path="workitemlink"
options="($workflowgroup:Product)((type:workitem) OR (type:workitemarchive))" options="($workflowgroup:Customer)((type:workitem) OR (type:workitemarchive))"
label="Customer:" /> label="Customer:" />
<item name="product.ref" <item name="product.ref"
@ -2189,32 +2189,106 @@ Address: <itemvalue>customer.country</itemvalue> <itemvalue>customer.zip</itemva
<bpmn2:dataObject id="dataObject_IqpFDQ" imixs:datatype="prompt-data" name="Export Compliance"> <bpmn2:dataObject id="dataObject_IqpFDQ" imixs:datatype="prompt-data" name="Export Compliance">
<bpmn2:documentation id="documentation_IrjikA"><![CDATA[<PromptDefinition> <bpmn2:documentation id="documentation_IrjikA"><![CDATA[<PromptDefinition>
<prompt_options>{"n_predict": 2048, "temperature": 0.2, "top_p": 0.9}</prompt_options> <prompt_options>{"n_predict": 2048, "temperature": 0.2, "top_p": 0.9}</prompt_options>
<prompt role="system"><![CDATA[You are an export compliance analyst for a company based in the European Union. <prompt role="system"><![CDATA[You are an export compliance analyst for a company based in the European Union.
A sales workflow has generated an offer for a customer in a non-EU country. A sales workflow has generated an offer for a customer in a non-EU country.
Perform a preliminary export compliance risk assessment based on the provided
process context.
Analyze the following process context and perform an export compliance assessment: ---
1. **Sanctions Check** ## 1. SANCTIONS & EMBARGOES
- Is the destination country subject to EU sanctions or embargoes?
- Are there any red flags regarding the customer (e.g. military affiliation, restricted entities)?
2. **Dual-Use Assessment (EU Regulation 2021/821)** Assess whether the destination country is subject to EU restrictive measures.
- Could any of the offered products fall under dual-use classification? Pay particular attention to:
- Pay special attention to: drone components, navigation systems, cameras, - Comprehensive embargoes (e.g. Russia, Belarus, Iran, North Korea, Syria, Myanmar)
thermal imaging, communication modules, flight controllers, propulsion systems. - Sectoral restrictions (e.g. technology exports, dual-use goods, military items)
- Re-export risk via known bypass jurisdictions (e.g. UAE, Turkey, Armenia,
Georgia, Kazakhstan, Hong Kong, Uzbekistan) when used as intermediate
shipping points for sanctioned destinations
3. **Red Flag Indicators** Assess the customer profile for red flags:
- Vague or missing end-use purpose? - Affiliation with armed forces, government procurement agencies,
- Customer reluctant to provide end-user information? intelligence services, or state-owned defense entities
- Unusual quantity or product combination? - Name similarity to entities on known restricted party lists
- Delivery to known transshipment countries? (flag for mandatory downstream verification – do not confirm list status)
- Customer location differs from declared end-use location
Provide your assessment as: ---
- **Risk Level**: GREEN (no concerns) | YELLOW (review recommended) | RED (do not send offer)
- **Findings**: Specific issues identified (no general advice, only case-specific facts)
- **Recommendation**: Concrete next step (e.g. "Proceed", "Request end-use certificate", "Escalate to compliance officer")
Base your analysis strictly on the provided process context. Do not invent facts.]]]]><![CDATA[> ## 2. DUAL-USE ASSESSMENT (EU Regulation 2021/821)
Assess whether the offered products could fall under dual-use classification
according to Annex I of EU Regulation 2021/821. Evaluate by category:
- **Cat. 1 – Advanced Materials**: composites, coatings, specialty alloys
usable in aerospace or defense applications
- **Cat. 3 – Electronics**: processors, FPGAs, RF components,
power amplifiers, signal converters above civilian thresholds
- **Cat. 4 – Computers**: high-performance computing, ruggedized systems
- **Cat. 6 – Sensors & Lasers**: thermal imaging, night vision,
LIDAR, hyperspectral sensors, laser rangefinders
- **Cat. 7 – Navigation & Avionics**: GNSS receivers, IMUs,
accelerometers, gyroscopes, flight controllers, autopilot systems
- **Cat. 9 – Aerospace & Propulsion**: UAV components, propulsion systems,
thrust control, altitude control systems, parachute release mechanisms
Also assess product combinations: individually harmless components may form
a controlled system when combined (e.g. flight controller + propulsion +
thermal camera = potential UAV surveillance system).
If no export control classification number (ECCN or EU list position) is
provided, assess based on product description and technical specifications
whether dual-use potential is plausible.
---
## 3. END-USE & END-USER ASSESSMENT
Evaluate the plausibility and completeness of the declared end-use:
- Is the stated end-use consistent with the customer's business profile?
- Is the stated end-use consistent with the product's technical capabilities?
- Is the order quantity plausible for the declared purpose?
- Are there indicators of re-sale or re-export intent
(e.g. trading company, no identifiable own operations)?
Flag the following as hard red flags requiring immediate escalation:
- End-use explicitly or implicitly military in a restricted country
- End-use declared as "general purpose", "various", or left blank
- Customer refuses to specify end-use or end-user
- Delivery address is a freight forwarder or logistics hub with no
identifiable final recipient
- Requested delivery timeline inconsistent with legitimate procurement cycles
---
## 4. RISK ASSESSMENT OUTPUT
Provide your assessment as follows:
**Risk Level**:
- GREEN – No indicators of concern identified; proceed subject to standard process
- YELLOW – One or more soft indicators present; enhanced due diligence required
before offer release
- RED – One or more hard red flags present; do not release offer; escalate immediately
**Findings**:
List only case-specific observations derived from the provided process context.
Do not include general compliance guidance. Each finding must reference a
specific data point from the input (product, country, customer attribute,
end-use statement, etc.).
**Recommendation**:
One concrete next step only:
- "Proceed"
- "Request end-use certificate and end-user declaration before offer release"
- "Verify customer against restricted party lists before proceeding"
- "Escalate to compliance officer – do not release offer"
- "Clarify end-use and final recipient with customer"
Base your analysis strictly on the provided process context.
Do not invent or assume facts not present in the input.
]]]]><![CDATA[>
</prompt> </prompt>
<prompt role="user"><![CDATA[ <prompt role="user"><![CDATA[
{chronicle} {chronicle}
@ -2476,7 +2550,7 @@ Betrag: <itemvalue>_amount</itemvalue> (Brutto € <itemvalue>_amount_brutto</it
<bpmndi:BPMNShape bpmnElement="dataObject_g68BvQ" id="BPMNShape_4ZBosQ"> <bpmndi:BPMNShape bpmnElement="dataObject_g68BvQ" id="BPMNShape_4ZBosQ">
<dc:Bounds height="50.0" width="35.0" x="1420.0" y="350.0"/> <dc:Bounds height="50.0" width="35.0" x="1420.0" y="350.0"/>
<bpmndi:BPMNLabel id="BPMNLabel_4YP9hg"> <bpmndi:BPMNLabel id="BPMNLabel_4YP9hg">
<dc:Bounds height="20.0" width="100.0" x="1387.5" y="405.0"/> <dc:Bounds height="20.0" width="100.0" x="1389.5" y="407.0"/>
</bpmndi:BPMNLabel> </bpmndi:BPMNLabel>
</bpmndi:BPMNShape> </bpmndi:BPMNShape>
<bpmndi:BPMNShape bpmnElement="event_8dt92Q" id="BPMNShape_GGKSew"> <bpmndi:BPMNShape bpmnElement="event_8dt92Q" id="BPMNShape_GGKSew">
@ -2781,8 +2855,8 @@ Betrag: <itemvalue>_amount</itemvalue> (Brutto € <itemvalue>_amount_brutto</it
<di:waypoint x="847.0" y="285.0"/> <di:waypoint x="847.0" y="285.0"/>
</bpmndi:BPMNEdge> </bpmndi:BPMNEdge>
<bpmndi:BPMNEdge bpmnElement="sequenceFlow_InfPdQ" id="BPMNEdge_Z4fGdA" sourceElement="BPMNShape_zb0q5w" targetElement="BPMNShape_X7JvIg"> <bpmndi:BPMNEdge bpmnElement="sequenceFlow_InfPdQ" id="BPMNEdge_Z4fGdA" sourceElement="BPMNShape_zb0q5w" targetElement="BPMNShape_X7JvIg">
<di:waypoint x="765.0" y="240.0"/> <di:waypoint x="775.0" y="237.0"/>
<di:waypoint x="765.0" y="217.0"/> <di:waypoint x="775.0" y="217.0"/>
<di:waypoint x="865.0" y="217.0"/> <di:waypoint x="865.0" y="217.0"/>
<di:waypoint x="865.0" y="267.0"/> <di:waypoint x="865.0" y="267.0"/>
</bpmndi:BPMNEdge> </bpmndi:BPMNEdge>
@ -2858,8 +2932,8 @@ Betrag: <itemvalue>_amount</itemvalue> (Brutto € <itemvalue>_amount_brutto</it
<di:waypoint x="1657.0" y="285.0"/> <di:waypoint x="1657.0" y="285.0"/>
</bpmndi:BPMNEdge> </bpmndi:BPMNEdge>
<bpmndi:BPMNEdge bpmnElement="sequenceFlow_hkBSvg" id="BPMNEdge_i0Xtag" sourceElement="BPMNShape_Rjz9jQ" targetElement="BPMNShape_wu0GaA"> <bpmndi:BPMNEdge bpmnElement="sequenceFlow_hkBSvg" id="BPMNEdge_i0Xtag" sourceElement="BPMNShape_Rjz9jQ" targetElement="BPMNShape_wu0GaA">
<di:waypoint x="1373.0" y="209.0"/> <di:waypoint x="1373.0" y="205.0"/>
<di:waypoint x="1434.0" y="209.0"/> <di:waypoint x="1434.0" y="205.0"/>
<di:waypoint x="1434.0" y="260.0"/> <di:waypoint x="1434.0" y="260.0"/>
</bpmndi:BPMNEdge> </bpmndi:BPMNEdge>
<bpmndi:BPMNEdge bpmnElement="association_XvFOIw" id="BPMNEdge_i0LSJA" sourceElement="BPMNShape_DataObject_1" targetElement="BPMNShape_Participant_1"/> <bpmndi:BPMNEdge bpmnElement="association_XvFOIw" id="BPMNEdge_i0LSJA" sourceElement="BPMNShape_DataObject_1" targetElement="BPMNShape_Participant_1"/>