1. Architectural design

2. Cross Compliance Assessment Tool Requirements CCAT architecture End users > (able to run scenarios) > access to output of CCAT Modeling team members > access to total CCAT tool > able to define input / model rules > able to test own partial system

3. Cross Compliance Assessment Tool CCAT core architecture Internet GUI CCAT Tool EngineCCAT Modelers GUI CCAT Manager Preprocess CCAT Manager Scenario Run CCAT Manager Postprocess

4. Cross Compliance Assessment Tool CCAT Manager Scenario Run Compliance Preprocess MITERRA Nitrogen Preprocess CAPRI model MITERRA model BIODIVERSITY model EPIC meta model

5. Cross Compliance Assessment Tool Architectural philosophy for joint model building Bottom up simple modular approach Model run test at any architectural level Simple input/definition templates: xls sheets Entire running system >> batch driven Overall modeling environment for modelers

6. Cross Compliance Assessment Tool CCAT Manager Scenario Run: Tasks Receiving scenario information from GUI Translating scenario information for models to run Transporting information towards models Running models sequentially Translating information between models (if needed) Receiving output from models Translating output to GUI

7. Cross Compliance Assessment Tool CCAT Mgr Scenario Run Scenario data MITERRA Nitrogen Interaction data CAPRI Interaction data Output data MITERRA Interaction data RESULTS: Output data for GUI start Input data BIODIVERSITY Compliance preprocessor Input data Interaction data CCAT Manager scenario interactions Output data start

8. Cross Compliance Assessment Tool DEMO CCAT Tool PT I Wait and see …..