data-workflow.md

 # Data Workflow with Business Partners
 ## BVIS
 ### Contracting
-1. [in] [contract data](bvis/contracting/contract-data)
+~ 1. [in] event "receive new contract"  
    Capitol provides a REST API that accepts JSON data to start the process.  
-2. [out] [contract data](bvis/contracting/contract-data) (insurance benefits may have been added)
+   BVIS sends [contract data](bvis/contracting/contract-data).
+
+~ 2. [out] task "send contract to BVIS"  
    BVIS provides a REST endpoint that accepts JSON data.  
-3. [in] customer decision **TODO**
+   Capitol sends [contract data](bvis/contracting/contract-data). (insurance benefits may have been added)
+
+~ 3. [in] event "receive customer decisions regarding the contract"  
    Capitol provides a REST endpoint that accepts JSON data.  
+   BVIS sends the customer decision (see below). **TODO:inform BVIS**
+   
    * contract id
    * signing flag (indicates if the customer accepted the contract)
    * insurance benefits (see [contract data](bvis/contracting/contract-data)) (indicates which insurance benefits the customer accepted, may be empty)
 
 ### Accident
-1. [in] [accident data](bvis/accident/accident-data)
+~ 1. [in] event "receive information about accident and customer"  
    Capitol provides a REST endpoint that accepts JSON data to start the process.  
+   BVIS sends [accident data](bvis/accident/accident-data). (see below)
    
-   * Capitol contract id
-   
-   or
-   
-   * BVIS customer id 
-   * car
-   
-   to identify the contract and
-   
-   * process id
-   * date
+   * contract id (by Capitol)
+   * transaction key (generated by BVIS)
+   * accident date
    * damage description
    
-2. [out] contact BVIS if accident is a liability case [liability information](bvis/accident/liability-information)
+~ 2. [out] task "notify BVIS if accident is covered"  
    BVIS provides a REST endpoint that accepts JSON.  
+   Capitol sends [liability information](bvis/accident/liability-information). (see below)
    
    * transaction key
    * contract id
    * liability flag
 
-   **TODO** adopt workflow model
-
 ## Cars & Co
 ### Accident
-1. [out] contact Cars & Co if accident is liability case [data](bvis/accident/-data)
-
-   **@see** BVIS->Cars & Co
+~ 1. [out] task "contact Cars & Co"  
+   Cars & Co provides a REST endpoint that accepts JSON.  
+   Capitol sends [repair request](carsnco/accident/repair-request). (see below, equals BVIS' data flow)
    
-   * car
+   * [car](model/car)
    * damage description
-   * customer id (of Capitol for Cars & Co)
+   * customer id (id Cars & Co assigned to their customer Capitol)
 
-2. [in] receive [bill](bvis/accident/billing-data) 
+~ 2. [in] event "receive invoice from Cars & Co"  
    Capitol provides a REST endpoint that accepts JSON.  
+   Cars & Co sends a [bill](bvis/accident/billing-data). (see below)
    
    * kontoinhaber
    * iban
@@ -57,9 +56,10 @@
    * referenznummer
    * posten
 
-3. [out] pay Cars & Co [payment data](bvis/accident/payment-data)
-   This will simulate a payment transaction to Cars & Co via a bank.
+~ 3. [out] task "pay Cars & Co"  
      Cars & Co provides a REST endpoint that accepts JSON.  
+     This will simulate a payment transaction to Cars & Co via a bank.  
+     Capitol sends a [payment data](bvis/accident/payment-data) object. (see below)
    
    * iban
    * bic