Redesign
- Added Blog page
- Deleted Use Case page
Signed-off-by: Siwara Schmitt <siwara.schmitt@iese.fraunhofer.de>
diff --git a/config.toml b/config.toml
index 66527fa..40ae5f4 100644
--- a/config.toml
+++ b/config.toml
@@ -42,8 +42,8 @@
# weight = 20
[[menu.main]]
- name = "Success Stories"
- url = "/success story/"
+ name = "Reference Projects"
+ url = "https://wiki.eclipse.org/BaSyx_/_Reference_Projects"
weight = 25
#[[menu.main]]
@@ -106,8 +106,8 @@
[params]
viewMorePostLink = "/blog/"
author = "Admin"
- defaultKeywords = ["industrie 4.0", "iot", "basys 4.0", "basyx", "smart production", "digitalization", "cyber physical systems"]
- defaultDescription = "Eclipse BaSyx community website"
+ defaultKeywords = ["industrie 4.0", "iot", "basys 4.0", "basys 4.2", "basyx", "smart production", "digitalization", "cyber physical systems", "ecosystem", "BaSyx offers", "Digital Twin", "Asset Administration Shell"]
+ defaultDescription = "Eclipse BaSyx Community Website"
# Google Maps API key (if not set will default to not passing a key.)
#googleMapsApiKey = "AIzaSyCFhtWLJcE30xOAjcbSFi-0fnoVmQZPb1Y"
@@ -130,7 +130,7 @@
# Enable the contact form by entering your Formspree.io email
email = ""
- #copyright = "Copyright © 2019 The Eclipse Foundation. All Rights Reserved."
+ #copyright = "Copyright © 2020 The Eclipse Foundation. All Rights Reserved."
# Format dates with Go's time formatting
date_format = "January 2, 2006"
@@ -169,7 +169,7 @@
[params.carousel]
enable = true
- # All carroussel items are defined in their own files. You can find example items
+ # All carousel items are defined in their own files. You can find example items
# at 'exampleSite/data/carousel'.
# For more information take a look at the README.
diff --git a/content/about/index.md b/content/about/index.md
index 5bc2c52..ed358d2 100644
--- a/content/about/index.md
+++ b/content/about/index.md
@@ -41,7 +41,7 @@
</p>
<p class="lead">
- The Project is actively supported by the German <a href="https://www.basys40.de" target="_blank" rel="noopener">BaSys 4.0 research project</a>, which focuses on research and specification of key Industrie 4.0 concepts, participates in standardization activities, and integrates existing standards and technologies into an Industrie 4.0 middleware project.
+ The Project is actively supported by the German <a href="https://www.basys40.de" target="_blank" rel="noopener">BaSys 4.2 research project</a>, which focuses on research and specification of key Industrie 4.0 concepts, participates in standardization activities, and integrates existing standards and technologies into an Industrie 4.0 middleware project.
</p>
</div>
diff --git a/content/blog/ece1018ese1218.md b/content/blog/ece1018ese1218.md
new file mode 100644
index 0000000..d71698f
--- /dev/null
+++ b/content/blog/ece1018ese1218.md
@@ -0,0 +1,15 @@
+---
+title: "EclipseCon Europe and ESE Kongress events"
+date: 2018-10-22T12:13:28+02:00
+#tags: ["ece18"]
+#categories: ["dissemination"]
+banner: "img/banners/banner-8.jpg"
+---
+
+## EclipseCon France 2018
+
+Eclipse Kuksa and its latest development activities will be presented along with the talk [Automotive meets IoT: Innovating your Future Vehicle](https://www.eclipsecon.org/europe2018/sessions/automotive-meets-iot-innovating-your-future-vehicle) at **EclipseCon Europe** 2018 in Ludwigsburg, Germany.
+
+## Embedded Software Engineering Kongress 2018
+
+In addition to the EclipseCon Europe event, you can join us at the **ESE Kongress** in Sindelfingen, Germany, on December, 6th. The talk [Überwindung der Silos –
Revolution für vernetzte Fahrzeuge](https://www.ese-kongress.de/paper/presentation/id/78), that means 'Overcoming the Silos - Revolution for Connected Vehicles', will be held at 16:45 o'clock (4:45pm) and will cover both a generic as well as detailed descriptions of the three Eclipse Kuksa platforms (a) In-Vehicle, (b) IDE, and ( c) Cloud.
\ No newline at end of file
diff --git a/content/blog/ecf2018-interview.md b/content/blog/ecf2018-interview.md
new file mode 100644
index 0000000..a812550
--- /dev/null
+++ b/content/blog/ecf2018-interview.md
@@ -0,0 +1,16 @@
++++
+title = "EclipseCon France 2018 - Robert Höttger interview"
+date = "2018-09-18T13:07:31+02:00"
+#tags = ["ecf18"]
+#categories = ["dissemination"]
+banner = "img/banners/banner-7.jpg"
++++
+
+Interview with Robert Höttger (Fachhochschule Dortmund - University of Applied Science and Arts). Robert presented the recent news about the APPSTACLE project.
+
+<!-- There is currently a bug in Eclipse API:
+This URL is not recognized as a youtube URL
+-->
+<!-- a class="eclipsefdn-video" href="https://youtu.be/qCyBjZnGK2E"></a -->
+
+<a class="eclipsefdn-video" href="https://www.youtube.com/watch?v=qCyBjZnGK2E"></a>
diff --git a/content/blog/ecf2018.md b/content/blog/ecf2018.md
new file mode 100644
index 0000000..42de00d
--- /dev/null
+++ b/content/blog/ecf2018.md
@@ -0,0 +1,14 @@
++++
+title = "EclipseCon France participation"
+date = "2018-06-18T13:07:31+02:00"
+#tags = ["ecf18"]
+#categories = ["dissemination"]
+banner = "img/banners/banner-5.jpg"
++++
+
+## EclipseCon France 2018
+Eclipse Kuksa was presented at EclipseCon France 2018 along with the research booth, the research community's pitch session, a regular talk hold by Tobias Rawald and Robert Hoettger, and an interview about the motivation, goals, and the current state of Eclipse Kuksa.
+
+{{< tweet 1007266197820329984 >}}
+{{< tweet 1006833646119018496 >}}
+{{< tweet 1006835234669842432 >}}
diff --git a/content/blog/hack0818.md b/content/blog/hack0818.md
new file mode 100644
index 0000000..454806b
--- /dev/null
+++ b/content/blog/hack0818.md
@@ -0,0 +1,34 @@
++++
+title = "Eclipse Kuksa Hackathon 08.2018"
+date = "2018-08-30T13:47:08+02:00"
+#tags = ["Appstore"]
+#categories = ["Implementation"]
+banner = "img/banners/banner-hack.jpeg"
++++
+
+
+## Hacking 3 Days @ IDiAL, FH-Dortmund, for Eclipse Kuksa Features
+
+13 Hackers met in Dortmund on August, 28th until 30th of August to work on an end-to-end use case scenario along with new Eclipse Kuksa technologies.
+**20 CQs, 2 major GitHub pull-requests, and 21035 LOCs** were the results. Of course, the LOCs also contain content from work prior to the Hackathon.
+
+More precisely, the **Eclipse Kuksa Appstore** was migrated to an Eclipse HawkBit Server, that transmits applications wirelessly to an Eclipse HawkBit client running on a device (Raspberry Pi) that runs the Kuksa adapted AGL (Automotive Grade Linux + Kuksa technologies). After successfully downloading the image, an **installer** unpacks and installs the downloaded image, such that the application, downloaded from the Kuksa Appstore, is executed on the target device.
+Transmissions are thereby accompanied by certificates and tokens to ensure a **secure and authenticated** data transmission and management.
+
+Implementations are not yet merged into the Kuksa GitHub repositories since used third party content is not yet fully IP checked. As soon as this is finished, you will be able to access the new technologies available at our [Kuksa GitHub repositories](https://github.com/eclipse?utf8=✓&q=kuksa).
+
+Here are two screenshots:
+
+<p style="text-align:center;">
+ <a href="/kuksa/blog/images/scsh1.png">
+ <img src="/kuksa/blog/images/scsh1.png" width="60%" alt="KUKSA Appstore Apps"/>
+ </a>
+</p>
+
+<p style="text-align:center;">
+ <a href="/kuksa/blog/images/scsh2.png">
+ <img src="/kuksa/blog/images/scsh2.png" alt="KUKSA Appstore Login" width="60%">
+ </a>
+</p>
+
+More information regarding the Eclipse HawkBit / Hono integration will follow soon: Stay tuned!
\ No newline at end of file
diff --git a/content/blog/images/scsh1.png b/content/blog/images/scsh1.png
new file mode 100644
index 0000000..6ec9d5f
--- /dev/null
+++ b/content/blog/images/scsh1.png
Binary files differ
diff --git a/content/blog/images/scsh2.png b/content/blog/images/scsh2.png
new file mode 100644
index 0000000..769c7ee
--- /dev/null
+++ b/content/blog/images/scsh2.png
Binary files differ
diff --git a/content/blog/initialContribution.md b/content/blog/initialContribution.md
new file mode 100644
index 0000000..689bdd7
--- /dev/null
+++ b/content/blog/initialContribution.md
@@ -0,0 +1,18 @@
++++
+title = "Initial Contributions"
+date = "2018-06-05T21:49:20+02:00"
+#tags = ["Implementation"]
+#categories = ["Implementation"]
+banner = "img/banners/banner-6.png"
++++
+
+Eclipse Kuksa's initial contribution was successfully submitted to the [GitHub repositories](https://github.com/eclipse?utf8=✓&q=kuksa&type=&language=). We are working on a roadmap to present planned activities for upcoming contributions. Apart from the three major Kuksa parts, i.e.,
+
+* [kuksa.invehicle](https://github.com/eclipse/kuksa.invehicle)
+* [kuksa.cloud](https://github.com/eclipse/kuksa.cloud)
+* [kuksa.ide](https://github.com/eclipse/kuksa.ide)
+
+additional repositories will cover specific use-cases, builds, tests, and other features within:
+
+* [kuksa.apps](https://github.com/eclipse/kuksa.apps)
+* [kuksa.integration](https://github.com/eclipse/kuksa.integration)
diff --git a/content/blog/oulanka.md b/content/blog/oulanka.md
new file mode 100644
index 0000000..f0f428a
--- /dev/null
+++ b/content/blog/oulanka.md
@@ -0,0 +1,13 @@
++++
+title = "Oulanka Project Meeting"
+date = "2017-10-26T13:39:46+02:00"
+#tags = ["Oulanka"]
+#categories = ["dissemination"]
+banner = "img/banners/banner-3.jpg"
++++
+
+## Project Meeting in Oulanka
+
+At the project meeting in Oulanka, Finnland, the APPSTACLE consortium collected and coordinated a variety of topics to work on in the upcoming time.
+Use-case scenarios, in-vehicle development activities, network protocols, cloud infrastructure, security demands, dissemination and exploitation and other topics were in focus for the project partners.
+The various discussions, cooperations, ideas, and further activities were defined in order to set the basis to reach the goals of APPSTACLE and form Eclipse Kuksa, i.e. the code based and results of the APPSTACLE project.
diff --git a/content/blog/plans.md b/content/blog/plans.md
new file mode 100644
index 0000000..1bf960b
--- /dev/null
+++ b/content/blog/plans.md
@@ -0,0 +1,14 @@
++++
+title = "Eclipse Kuksa @ IoT WG"
+date = "2018-01-17T13:47:08+02:00"
+#tags = ["IoT"]
+#categories = ["Introduction"]
+banner = "img/banners/banner-2.jpg"
++++
+
+
+## Introduction to Eclipse Kuksa
+
+The slides below were part of the introduction of Eclipse Kuksa to the Eclipse IoT community.
+
+Presentation is available [here](https://owncloud.idial.institute/s/WPtAYX6r8weKgWT).
diff --git a/content/blog/roverv03.md b/content/blog/roverv03.md
new file mode 100644
index 0000000..f8c1131
--- /dev/null
+++ b/content/blog/roverv03.md
@@ -0,0 +1,16 @@
++++
+title = "Rover V03"
+date = "2018-05-31T21:49:20+02:00"
+#tags = ["rover"]
+#categories = ["rover"]
+banner = "img/banners/banner-4.jpg"
++++
+
+The Rover (SW: [Rover Software](https://app4mc-rover.github.io/rover-docs/), HW: [Rover Hardware](https://wiki.eclipse.org/APP4MC/Rover)) has been updated to version V03. This includes several migrations of tasks to AGL services and applications, as well major improvements to the Rover's chassis, that provides a more modular structure since components can be flexibly clipped to different positions without the need of screws.
+The following implementations are though on our roadmap for the next release:
+
+* ACC
+* Parking
+* Marker recognition (using OpenCV)
+* Rover-follow application
+* ....
diff --git a/content/use case/BigDataAnalytics.md b/content/use case/BigDataAnalytics.md
deleted file mode 100644
index 39be69a..0000000
--- a/content/use case/BigDataAnalytics.md
+++ /dev/null
@@ -1,24 +0,0 @@
----
-title: "Enabler Of Big Data Analytics"
-#date: 2019-03-13
-tags: ["Big Data Analytics"]
-#banner: "img/banners/banner-8.jpg"
-
----
-<p class="lead">
-Every factory device creates a continuous stream of data. Data analytics can provide valuable insights into production processes:
-<ul class="lead">
- <li>Which variables have impacts on production cost and quality?</li>
- <li>How can we predict production performance?</li>
- <li>Where is hidden potential for optimization in my manufacturing processes?</li>
-</ul>
-<p/>
-<p class="lead">
-Data analytics requires the combination of data from different sources, i.e. production devices, as well as IT servers. The ability of Eclipse BaSyx to structure machine and product data in Asset Administration Shells, enriching both with semantic information, then combining them, is the enabler for big data analysis. System architects can freely choose which cloud optionally preprocessed data is transferred. This ensures that data ownership remains with product and machine owners.
-<p/>
-<p style="text-align:center;">
- <a href="/basyx/use case/images/BigDataAnalytics.jpg">
- <img style="border:1px solid black" src="/basyx/use case/images/BigDataAnalytics.jpg" border="2" width="100%" alt=""/>
- </a>
-</p>
-</br></br>
\ No newline at end of file
diff --git a/content/use case/ChangeableProduction.md b/content/use case/ChangeableProduction.md
deleted file mode 100644
index 9a63b55..0000000
--- a/content/use case/ChangeableProduction.md
+++ /dev/null
@@ -1,18 +0,0 @@
----
-title: "Changeable Production To Enable Profitable Lot Size 1"
-#date: 2019-03-13
-tags: ["changeable production", "lot size 1"]
-#banner: "img/banners/banner-8.jpg"
----
-<p class="lead">
-Current production industry is designed for large lot sizes. Due to the shorter product lifecycles, manufacturing industry needs to shift its focus. Rapidly changing market requirements demand efficient changeable production processes. Furthermore, customers are increasingly attracted to tailored products that yield a much higher value creation than mass-produced goods. A major challenge for process changes is the necessary reprogramming of Programmable Logic Controllers (PLC). PLCs implement automation programs that execute pre-programmed sequences, optionally supporting a pre-defined amount of flexibility. The lack of a defined process model causes side-effects when PLC programs are changed, causing expensive down times for testing and fixing.
-<p/>
-<p class="lead">
-Eclipse BaSyx introduces service oriented programming for devices. PLC controllers implement real-time production services, an orchestrator controls service invocation, e.g. based on a recipe. This explicit process modeling enables rapid changes and removes side effects. BaSyx introduces the required interoperability and abstraction with the concept of the Asset Administration Shell and service interfaces. Through the standardization inherent in the Asset Administration Shell, devices may be replaced by another device with equal service interfaces, without having to change the plant application.
-<p/>
-<p style="text-align:center;">
- <a href="/basyx/use case/images/ChangableProduction.jpg">
- <img style="border:1px solid black" src="/basyx/use case/images/ChangableProduction.jpg" border="2" width="100%" alt=""/>
- </a>
-</p>
-</br></br>
\ No newline at end of file
diff --git a/content/use case/ConnectingITWithProductionDevices.md b/content/use case/ConnectingITWithProductionDevices.md
deleted file mode 100644
index cbe23cf..0000000
--- a/content/use case/ConnectingITWithProductionDevices.md
+++ /dev/null
@@ -1,18 +0,0 @@
----
-title: "Connecting IT And Production Devices On The Shop-Floor"
-#date: 2019-03-13
-tags: ["Dashboards", "Monitoring", "from Office-Floor to Shop-Floor"]
-#banner:"img/banners/banner-8.jpg"
----
-<p class="lead">
-Walking around the shop-floor to manually query machine states is inefficient and prevents operators from efficiently obtaining a holistic view on the complete production process. Streaming of live production data to IT on the office-floor remains a challenge that prevents efficient monitoring and understanding of production processes.
-<p/>
-<p class="lead">
-The BaSyx Virtual Automation Bus (VAB) enables machine to machine communication across the layers of the automation pyramid; shop-floor devices can directly interact with enterprise resource planning (ERP) systems, even if they use different protocols. Dashboards show focused process views and enable live monitoring of products and production processes. They enable workers and operators to monitor production processes, understand them, evaluate potential optimization, and to understand the impact of every production station on organizational success. Customers may access live production data to monitor the progress of their orders. Logistics may be dispatched on the spot to save storage space.
-<p/>
-<p style="text-align:center;">
- <a href="/basyx/use case/images/ConnectingITandDevices.jpg">
- <img style="border:1px solid black" src="/basyx/use case/images/ConnectingITandDevices.jpg" border="2" width="100%" alt=""/>
- </a>
-</p>
-</br></br>
\ No newline at end of file
diff --git a/content/use case/NewBusinessModels.md b/content/use case/NewBusinessModels.md
deleted file mode 100644
index 9fc3de2..0000000
--- a/content/use case/NewBusinessModels.md
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title: "Enabler For New Business Models"
-#date: 2019-03-13
-tags: ["New Business Models"]
-#banner: "img/banners/banner-8.jpg"
----
-<p class="lead">
-Industrie 4.0 is about more efficient mass-production processes, and mass-customization, the efficient and inexpensive production of small lot sizes. Industrie 4.0 is also the end-to-end digitalization of manufacturing and enables new business models. The following exemplary Industrie 4.0 business models can be implemented with Eclipse BaSyx.
-<ol type="a" class="lead">
- <li><b>Data Brokering</b></br>Data produced in manufacturing processes is extremely valuable for equipment manufacturers and other third-party businesses since it enables prediction and optimization of manufacturing processes and product quality. Prediction models based on the combination of data from different sources will yield business advantages for companies, but they require a large data pool for their creation. Brokering of data, the ability to provide anonymized data that is compliant with the privacy of data providers, but that is a valuable source for data users, will be a key business after the fourth industrial revolution. </li></br>
- <li><b>Virtual Prototyping & Continuous Engineering</b></br>The integration of new devices and new device programs requires a significant amount of time during a change to production. Digital device twins may reduce this required time by providing, for example interaction models that enable engineers to adjust device-to-device communication and to validate service calls, call parameter, and potential side-effects without having to stop the production line. Asset Administration Shells provide the ability to store these simulation models in sub models, and to deliver them before the physical device is delivered. Ideally, production systems can communicate with a digital twin without knowing whether the communication partner is a virtual prototype or the real asset. This significantly reduces downtimes when integrating new devices, or when changing critical processes.</li></br>
- <li><b>Production as a Service</b></br>Production-as-a-Service changes the business model of manufacturers from selling produced goods to becoming the sole operator of a plant. Production is on a contract basis that guarantees access to manufacturing machines and resource availability. Manufacturing companies can focus on their core business: the manufacturing of goods. Customers can save time and costs, as well as react quickly to changing lot sizes. For smaller production companies there is an opportunity to sell selected machines via production-as-a-service models to compensate unused times. Companies that produce similar goods may implement production-as-a service as load-balancing to compensate periods with fewer requests and, at the same time, enable handling of requests that would be too large for their own machines. </li>
-</ol>
-<p/>
-<p style="text-align:center;">
- <a href="/basyx/use case/images/NewBusinessModels.jpg">
- <img style="border:1px solid black" src="/basyx/use case/images/NewBusinessModels.jpg" border="2" width="100%" alt=""/>
- </a>
-</p>
-</br></br>
\ No newline at end of file
diff --git a/content/use case/PredictiveMaintenance.md b/content/use case/PredictiveMaintenance.md
deleted file mode 100644
index c20f54a..0000000
--- a/content/use case/PredictiveMaintenance.md
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title: "Predictive Maintenance"
-#date: 2019-03-13
-tags: ["Predictive Maintenance"]
-#banner:"img/banners/banner-8.jpg"
----
-<p class="lead">
-Repairing a device once it’s ‘broken’ can lead to unpredictable and expensive downtime. Scheduled maintenance improves the situation, but a static maintenance schedule can cause unnecessary interruptions. In the worst case, required parts need to be ordered, extending downtimes significantly. Predictive maintenance solves these issues:
-<ol class="lead">
- <li>Combining live sensor data and past experience enables prediction of necessary maintenance activities and schedules. Production processes can then be adapted to synchronize and integrate maintenance activities with the least possible impact.</li> </br>
- <li>Predictive maintenance data can be live information regarding the product quality that the devices produce. Maintenance for devices that produce lower quality batches may be delayed in this scenario, as long as the device output is still satisfactory.</li> </br>
- <li>Required spare parts may be ordered just in time, saving storage space and minimizing down times.</li>
-</ol>
-<p/>
-<p style="text-align:center;">
- <a href="/basyx/use case/images/PredictiveMaintenance.jpg">
- <img style="border:1px solid black" src="/basyx/use case/images/PredictiveMaintenance.jpg" width="100%" height="100%" alt=""/>
- </a>
-</p>
-</br></br>
\ No newline at end of file
diff --git a/content/use case/images/BigDataAnalytics.jpg b/content/use case/images/BigDataAnalytics.jpg
deleted file mode 100644
index a684fe3..0000000
--- a/content/use case/images/BigDataAnalytics.jpg
+++ /dev/null
Binary files differ
diff --git a/content/use case/images/ChangableProduction.jpg b/content/use case/images/ChangableProduction.jpg
deleted file mode 100644
index 3a91c6b..0000000
--- a/content/use case/images/ChangableProduction.jpg
+++ /dev/null
Binary files differ
diff --git a/content/use case/images/ConnectingITandDevices.jpg b/content/use case/images/ConnectingITandDevices.jpg
deleted file mode 100644
index 9455d97..0000000
--- a/content/use case/images/ConnectingITandDevices.jpg
+++ /dev/null
Binary files differ
diff --git a/content/use case/images/NewBusinessModels.jpg b/content/use case/images/NewBusinessModels.jpg
deleted file mode 100644
index 394ab91..0000000
--- a/content/use case/images/NewBusinessModels.jpg
+++ /dev/null
Binary files differ
diff --git a/content/use case/images/PredictiveMaintenance.jpg b/content/use case/images/PredictiveMaintenance.jpg
deleted file mode 100644
index 67d7510..0000000
--- a/content/use case/images/PredictiveMaintenance.jpg
+++ /dev/null
Binary files differ
diff --git a/layouts/index.html b/layouts/index.html
index 38b7c61..141d69c 100644
--- a/layouts/index.html
+++ b/layouts/index.html
@@ -25,7 +25,7 @@
{{ partial "see_more.html" . }}
- <!--{{ partial "recent_posts.html" . }}-->
+ {{ partial "recent_posts.html" . }}
{{ partial "clients.html" . }}
diff --git a/layouts/partials/sidebar.html b/layouts/partials/sidebar.html
index 2f8715d..a3b5620 100755
--- a/layouts/partials/sidebar.html
+++ b/layouts/partials/sidebar.html
@@ -1,6 +1,7 @@
-<!--{{ partial "widgets/search.html" . }}-->
-{{ partial "widgets/usecases.html" . }}
+{{ partial "widgets/search.html" . }}
+
+<!--{{ partial "widgets/usecases.html" . }}-->
<!--{{ partial "widgets/categories.html" . }}-->
-<!--{{ partial "widgets/tags.html" . }}-->
+{{ partial "widgets/tags.html" . }}
