Smart Construction Challenge

1. Smart Construction Challenge Contacts: Alexy Khrabrov: Alexy@trusted-iot.org Eleonora Faini eleonora.faini@bosch-si.com

2. Evaluation Criteria Business How well does the proposal support the outlined use cases, provide value add for end-customers, and deliver innovation? Technology How well does the proposal describe how it will ensure scalability and realistic rollout in an enterprise environment? Proof of Concepts will be given bonus consideration Community Contribution How well have the contributors supported the Smart Construction Challenge events reflected in the timeline? Submission deadline: May 5th

3. Use this PowerPoint template to submit your proposed concept for the challenge • Fill out each slide from the following, using the appendix for additional material • Optional • Video • Highly recommended • Should provide insights into the work you did for the challenge (not simply product advertisement) • Please attach or embed this into this PPT • Code / PoC (proof of concept) Results • Optional, but highly desirable • Include high-level overview in PPT, with link to your repo Challenge Submission Please use the following slides to make your submission to the challenge

4. About your Company OR Challenge Team Please submit on this slide • Company name(s) • Submitter name(s) and e-mail addresses • Link(s) to company home page(s) • Who is representing which part of this submission (if it is a joint submission)

5. Contributions to the Construction Challenge • Please describe the contributions your team has made to building the smart construction community, e.g. by participating in challenge-related hackathons, attending or organizing challenge-related workshops, promoting the challenge actively via social media or presentations, helping to advance the TIOTA framework, etc.

6. Solution Design: Business Perspective • Describe your proposed solution from a business/end-user perspective (e.g., how would the solution - when fully deployed - create value for participants in the ecosystem including planning and construction companies, sub-contractors, certification and insurance companies, construction equipment providers and operators, etc.

7. Solution Design: GTM Perspective If the GTM for your solutions involves multiple stakeholder from the challenge ecosystem (e.g. your team, and/or some of the sponsors), please describe: • Describe the business model which would allow the ecosystem participants to jointly benefit from the solution • For example: How will we deal with IP which is created in the ecosystems • Potential legal form and organization: How will the solution be developed, sold and supported

8. Solution Design: Differentiation • Differentiation -- how would your proposed solution differentiate itself from others in the market?

9. Solution Design: Architecture • Please provide an overview of the proposed solution architecture • Optional • For IIoT: Please use an IIC architecture pattern (e.g. 3-Tier IIoT architecture) as the “canvas” • For DLT-centric solutions with IoT, please use the TIOTA Reference Architecture on the next slide as a “canvas” and map the main elements of you solution onto it

10. Solution Design: Technology • Describe your proposed solution from a technology perspective. In your description, please describe how IoT and/or blockchain/distributed ledger-based technology will be used in your solution.

11. Solution Design: Scale • Scaling up on the technical level: At what scale do you expect the solution to work, e.g. number of clients, throughput, transaction times, etc. • Scaling up on the business and operational level: How would you ensure this?

12. Potential Issues/Challenges • What issues/challenges might you encounter when creating your solution? Challenges might be related to the underlying technology, integrations, platform development, etc.

13. Tentative Timeline • Provide a tentative pilot timeline: • Key milestone dates • Proposed date when you believe your PoC will be live

14. Appendix • Attach any supporting materials to this appendix

15. Optional (for DLT-centric solution proposals): Mapping against TIOTA Reference Architecture Field • Asset Layer • Examples: Truck, Train, Machine • Includes local and remote communication and processing (on asset, fog) • Can include local blockchain clients Asset  Gateway WAN IoT Cloud  • IoT Cloud Layer • Asset connectivity & FOTA • Digital Twin, Asset-related data, event management • Enterprise Application Integration Application Logic Blockchain Cloud Enterprise Applications (ERP, Legacy, etc)  Blockchain Cloud Layer • Asset-related ledger entries • Peer-to-Peer Middleware for management of BCs • Network of compute nodes for BC   BC Middleware  BC Network Backend • Application Logic • Distributed across the different layers, e.g. apps + HMI on the asset; digital twin-based apps in the IoT Cloud; or smart contracts in the blockchain cloud

16. Optional: Architecture Canvas for your Solution Proposal Field Please use this slide as a canvas for your solution proposal. This will help us to compare the different proposals, and to build up a library of re-usable design patterns. If you feel there are elements missing of the structure is not right, please feel free to change it as you see fit. Asset Gateway WAN IoT Cloud Application Logic Blockchain Cloud BC Middleware BC Network Backend

17. Optional: Identity and Trusted Lifecycle Trusted IoT Lifecycle Phases Provisioning Tracing - Chain of Custody - Usage Tracing - External Events - Structural Changes Decommissioning IoT Identity Assets Users Lifecycle If applicable: Please explain how your solution is using DLTs etc. to enable identity management for the IoT. How is your solution supporting the trusted IoT lifecycle, in the context of the reference architecture?

18. Optional: Key/Certificate Lifecycle Management Key/Certificate Lifecycle Management • Secure generation of keys and certificates • Root of Trust: Keys and certificates injection at chip wafer level • Tamper resistance to ensure protection of keys in the supply chain and in the field (e.g. via TPM) • Secure key management and forward security: key negotiation, key wrapping, key regeneration, … If applicable: Please explain how your solution is supporting the lifecycle management of keys in a distributed environment (again, using the TIOTA reference architecture)

19. Join us now! Submit your application before May 5th 2019 by filling the Submission ppt Template Contacts: Alexy Khrabrov: Alexy@trusted-iot.org Eleonora Faini eleonora.faini@bosch-si.com