Quoting and Billing: Commercialization of Big Data Analytics Dr. Ingo Simonis BIDS’19, February 2019

Voluntary consensus standards organization 25th Anniversary International Research & Development

Product Implementations Prototype Implementations Requirements OGC Software Architecture Innovation Program Guides & Tools Gaps and Enhancements Engineering Reports Requirements Requirements Communications & Outreach Standards Program Adopted Standards Compliance Program Product Implementations Requirements 5

EO Applications in the Cloud: Challenge More and more applications are cloud-enabled. They are being deployed and executed close to the physical location of the data. In Testbed-13, we developed an architecture that allows an application developer to develop an application that contained al the information to run in a wokrflow. This is, packing it into a Docker container, create metadata with all necessary information to run the container (e.g. inputs, parameters). The application package could be registered with a WPS service. Application consumers can find the application on that server and subsequently execute the workflow. In Testbed-14, the challenge was how to register not one application but a workflow composed of various applications. In addition, moving away from the local machine into the cloud has the risk for the user that requested data processing causes enormous costs. Therefore, we needed a model that allows the application consumer to understand what a planned execution would cost.

EO Applications in the Cloud More and more applications are cloud-enabled. They are being deployed and executed close to the physical location of the data. In Testbed-13, we developed an architecture that allows an application developer to develop an application that contained al the information to run in a wokrflow. This is, packing it into a Docker container, create metadata with all necessary information to run the container (e.g. inputs, parameters). The application package could be registered with a WPS service. Application consumers can find the application on that server and subsequently execute the workflow. In Testbed-14, the challenge was how to register not one application but a workflow composed of various applications. In addition, moving away from the local machine into the cloud has the risk for the user that requested data processing causes enormous costs. Therefore, we needed a model that allows the application consumer to understand what a planned execution would cost.

EO Applications in the Cloud: Challenge More and more applications are cloud-enabled. They are being deployed and executed close to the physical location of the data. In Testbed-13, we developed an architecture that allows an application developer to develop an application that contained al the information to run in a wokrflow. This is, packing it into a Docker container, create metadata with all necessary information to run the container (e.g. inputs, parameters). The application package could be registered with a WPS service. Application consumers can find the application on that server and subsequently execute the workflow. In Testbed-14, the challenge was how to register not one application but a workflow composed of various applications. In addition, moving away from the local machine into the cloud has the risk for the user that requested data processing causes enormous costs. Therefore, we needed a model that allows the application consumer to understand what a planned execution would cost.

Application consumer

Application consumer

Application consumer Application developer

Application consumer Application developer

Computing cycles Storage capacity Value added services

Problem: complex ecosystem Platform: X platforms, Y implementers Infrastructure: Z suppliers App developer s Develop once Benefit from X * Y * Z explosion Not care about details

Building Blocks: AP, ADES, EMS Workflows integrated Quoting and Billing API & Model Implemented & Tested

Discovery of Apps Apps and their applicable data Integration with deployed processes

Next Steps Maturity Testing Real data Real services Real processes Real quoting and billing