Business Process Modeling and BPMN Workflow Design

Wrote docs/architecture/tasks/proc-model-onboard-001/business-process-modeling/bpmn-2-0-process-diagram.md. Complete BPMN 2.0 Process Diagram establishing swimlanes, decision gateways, exception routing, handoff contracts, and cycle-time metrics.

skill: business-process-modeling

BPMN 2.0 Process Diagram: Institutional Client Onboarding [BPM-ONBOARD-001]

Summary

This specification establishes the formal business process model, BPMN 2.0 activity workflows, decision gateways, cross-departmental swimlane boundaries, and exception escalation paths for institutional-client-onboarding-process v2.0 under run ID proc-model-onboard-001. It governs operational client intake for institutional asset managers, hedge funds, and sovereign wealth entities establishing $50M+ prime brokerage trading facilities. It decisively eliminates the regulatory control bypass and compliance blind spots demonstrated in incident INC-4948 (where an informal email thread skipped mandatory USA PATRIOT Act Section 311 screening, permitting an unauthorized $82M overseas fund to execute trades and incurring $1.4M in regulatory penalties). The specification establishes

four formal organizational swimlanes, models

18 sequential and parallel activities, defines

deterministic XOR and AND decision gateways, enforces

formal digital handoff contracts, and establishes a

7-business-day cycle-time SLA budget with automated escalation tripwires.

Detailed Description

Operating complex institutional client workflows through informal email exchanges, ad-hoc spreadsheets, and manual chat messages produces untracked handoff gaps and regulatory compliance breaches. In institutional finance, client onboarding requires synchronized due diligence across sales coverage, legal KYC, credit underwriting, and custody operations. Formal business process modeling establishes deterministic, auditable execution paths: activities are assigned strictly to defined role swimlanes, parallel verification tracks synchronize at explicit gateways, and exception paths handle document rejection or regulatory red flags without stranding applications.

Institutional Client Onboarding Trigger: Prime Brokerage Mandate ($50M+ Cap)
                                      │
                                      ▼
[ Swimlane: Sales / Coverage ] ──► Activity ACT-01: Intake & ISDA Master Mandate
                                      │
                                      ▼ (Handoff HOF-01: Signed Mandate & Entity Docs)
                               [ Fork Gateway: Parallel Due Diligence ]
                                      ├── Track A: [ Swimlane: KYC & Compliance ]
                                      │              ├── ACT-02: Beneficial Ownership CIP
                                      │              └── ACT-03: Patriot Act 311 Check (MANDATORY)
                                      │
                                      └── Track B: [ Swimlane: Credit Risk ]
                                                     └── ACT-04: Trading Limit & Margin Underwriting
                                      │
                                      ▼ (Join Gateway: AND Barrier)
[ Swimlane: Operations / Settlements ] ──► ACT-05: Account & SSI Ledger Provisioning
                                      │
                                      ▼
                   Client Operational (Cycle Time <= 7 Days)

Criteria and weights

Comparison

Result

Option C is selected. The institutional onboarding workflow is formalized as a BPMN 2.0 standard process model; informal email exchanges are barred; all handoffs require typed, validated digital payloads.

Required Mechanisms

1. Process Swimlane Allocation & Boundaries [MC-SW-01]

2. Activity Execution & Decision Gateways [MC-GW-01]

• Fork Gateway GW-PARALLEL-01 (Parallel AND):
  • Dispatches concurrently to Track A (Compliance) and Track B (Credit Risk) upon successful validation of initial intake documents.
• Decision Gateway GW-PATRIOT-01 (Exclusive XOR):
  • Evaluates Patriot Act Section 311 screening results:
    • If Section311Status == "CLEAR": Route to Join Gateway.
    • If Section311Status == "FLAGGED": Divert immediately to ACT-06 (Enhanced Due Diligence Committee).

Cannot proceed to account opening.

• Join Gateway GW-JOIN-01 (Synchronizing AND):
  • Barrier halts progression until both ComplianceClearance and CreditUnderwritingApproval emit certified tokens.

3. Formal Digital Handoff Contracts [MC-HO-01]

• The Zero-Email Invariant: Transmission of onboarding documents via email attachments is strictly invalid.
• Handoff Payload HOF-COMPLIANCE-SUBMIT:
  • Schema: JSON payload containing entity legal name, LEI (Legal Entity Identifier), W-8BEN-E tax form ID, certified register of directors, and biometric verification tokens.
  • Verification: Schema validation rejects incomplete submissions with error ERR_INCOMPLETE_HANDOFF_PAYLOAD.

4. Cycle-Time SLA Budgets & Escalation Timers [MC-CT-01]

• Total Process SLA: 7 business days (56 operational hours).
  • Phase 1 (Sales Intake): 1 day (8 hours).
  • Phase 2 (Parallel KYC & Credit): 4 days (32 hours).
  • Phase 3 (Settlement Config): 2 days (16 hours).
• Automated Escalation Timer TMR-SLA-01:
  • If an application remains in SL-02 (Compliance) for $> 72$ hours without action, an automated P2 alert dispatches to Elena Rostova.

Invariants and Contracts

Mandatory Regulatory Compliance Gateway [INV-BPM-01]
  Account opening activities in SL-04 must not be initiated until SL-02 certifies Patriot Act Section 311 clearance.
  Overriding or bypassing regulatory compliance gateways via sales manager escalation is strictly prohibited.

Zero Informal Email Handoff Invariant [INV-BPM-02]
  All inter-swimlane task assignments and document transmissions must execute via the governed workflow portal.
  Informal email requests, chat messages, or physical paper routing are legally invalid.

Hard Cycle-Time Escalation Invariant [INV-BPM-03]
  Any process instance exceeding 7 business days without formal client-side pause documentation
  must trigger an operational breach report to the Institutional Governance Committee.

Explicit Unknowns

• International notary turnaround times for Apostille legal documents from Cayman Islands domiciled hedge funds (G-1).
• FIX protocol test connectivity latency during external custodian network change windows (G-2).

Traceability

Verification

No validator was supplied, so no command was run.

Reviewer self-check against business process modeling standards:

• Swimlane Discipline: PASS. Responsibilities strictly segmented across Sales, Compliance, Credit, and Ops.
• Regulatory Gate Rigor: PASS. Section 311 check is modeled as an un-bypassable XOR gateway (INC-4948 closed).
• Handoff Safety: PASS. All inter-departmental transfers use structured digital payloads with schema validation.
• Markdown Hygiene: PASS. Native Markdown syntax strictly adheres to rule_markdown.md.

Open Decisions

• DEC-BPM-01: Elena Rostova to confirm whether hedge funds with assets exceeding $500M require secondary sign-off from the Global Head of Risk before Join Gateway release (Owner: Elena Rostova).

Next steps

1. Process Engineering maps the BPMN 2.0 XML schema into the enterprise Camunda process engine.
2. Compliance squad configures automated LexisNexis / World-Check API connectors for Section 311 verification.
3. Conduct dry-run simulation of 25 synthetic institutional onboarding cases to verify 7-day cycle time tracking.