## Any feasible APPs<font color="red"> ( Here for possible APPs )</font>
* e.g. Professor mentioned Multi-edge data inventory, or displaying real-time manufacturing data on a dashboard ( but quite common... )
* 中小企業自動化碳盤查系統
* 供應鏈碳盤查整合系統
* 工廠現場狀態影像
* 機台運作狀態（healthy/broken)

### 2023/08/11

* Our proposed scenario -- construction case
* Professor thought that Taiwan has fewer super large-scale construction scenes, so the focus is still on smart factories.
* Professor thought the scenario should concentrate on multi-factory case.
* An APP is fancy but lacks sync property
* VR for remote repairing requires real-time but not heavily related to synchronization.
* Other potential applications, but quite common.
* Supervisors can observe real-time production data, or place orders from different factories at other places
* Multi-edge data inventory
* The app needs to have the following properties in order to convince others of the necessity of our architecture
- [ ] <font color="red">Syncronization -> For Infrastructure
- [ ] Afraid of SPF -> For Infrastructure
- [ ] Fancy -> For Demo</font>
### 2023/08/07
* The case professor mentioned:
* Problem:
* Currently factory result of synchronization data is to create and save data on cloud server. However, in that case, the data is not secured because the cloud server might be provided by China company and we also have no idea if cloud server provider may do to our data (liking selling or leak the data or metadata).
* In short, data need to control by the factory company itself
* Solution:
* If the factory use our infrastructure, they don't need to use cloud server provided by other company. For demo, we can show that the CEO of the factory can see video(CCTV) from any one of the factories
* What we need to think
* What more application can support on this infrastructure?
* Need to point out the problem and solution like previous page
* Solution cannot be too common
* Our demo need to show our advantage
* Fancy demo
* See from factory/judge/cloud perspective to find some real case scenario problem and our advantages are really advantage

### 2023/08/03
* I would like to update the meeting note for today's discussion.
1. Our architecture goal is to securely connect multiple sides of the 5G private network.
2. The current issues to address in the research proposal are single-point failures and traffic congestion. These problems exist in the current centralized architecture.
3. We need to think more about the real-world applications and functions that the architecture can support --> we will update it in next Monday's meeting.
### 碳盤查 -- 資料來源日期 2022.11.17
* 碳盤查的各個範疇
* **範疇一**：直接造成的碳排，包括工廠發電機、車輛或機台
* **範疇二**：使用電力或其他能源造成的碳排
* **範疇三**：主要是供應鏈的上下游碳排，即產品生命周期所產生的排放。
* 選題優勢
* 台灣上周開放碳權交易，此方向貼合潮流；評審應該也對這類主題感興趣
* 動機
* 現今碳盤查瓶頸
- [ ] 問題
* 據經濟部統計，**全台登記的中小企業有154萬家，其中約19萬家可能被供應鏈要求或外銷歐盟必須做碳盤查**，涵蓋電子、紡織、運輸、食品、鋼鐵、金屬製品等行業。**但許多中小企業，對碳盤查、歐盟碳邊境調整機制等議題仍一頭霧水，不知該從何下手**
* **僅有22％的企業有自動化的碳盤查計算流程**，高達86％企業仍在使用試算表手動記錄和揭露排放，不僅耗工費時，也無法及早制訂決策。
* **30~40**%的企業估算有錯
* https://www.youtube.com/watch?v=T4FfLsQ_vZk&t=495s
- [ ] <font color="red">解方：中小企業自動化碳盤查系統(**focuse on 範疇一二**)</font>
- [ ] 問題
* 僅有9％企業能做到完整的碳盤查 -> **掌握範疇三的碳排是最大困難點**，「 你可以把自己盤的很好，但是你盤不到上下游供應鏈， 」
* 計算碳排牽涉營運資料的機密性，是許多企業的擔憂。像是蘋果（Apple）在供應鏈管理上高度重視保密度，「**供應商會擔心，提供營運資料給計算碳排的團隊，是否會觸犯與客戶的保密合約**？」劉北辰表示 -> 使用營運資料，**過程會牽涉到審批流程，需要去識別化處理** 。
* **範疇三的準確性與必要性**
* 以華碩為例，統計超過9成總體排放量是來自範疇三的供應鏈碳排放，成為未來推動減碳的關鍵。
* **範疇三牽涉到供應鏈之間的企業協同計算，企業間沒有統一的算法，或是沒有整合的平台是當前常見的問題。**
* **臺灣目前要求上市櫃公司揭露碳盤查資訊，僅限於範疇一、範疇二，並不包含範疇三**。但國際科技大廠在過去兩、三年也陸續自主揭露範疇三，所以**揭露範疇三是國際趨勢**。
- [ ] <font color="red">解方：供應鏈碳盤查整合系統(**focuse on 範疇三**)</font>

* 可能提出的應用
1. 中小企業自動化碳盤查系統(範疇一二)
* 單一客戶的多個智慧工廠連接到我們的APP，
3. 供應鏈碳盤查整合系統(範疇三)
* 供應鏈各廠連接到我們的APP，上游的相關生產資料地送到系統後會進行去識別化處理，再轉送到下游企業。
* **我們的系統要提供去識別化處理，以保證客戶的資料隱私**
* **供應鏈之企業使用相同平台運算便無須擔心碳排算法不一的問題。**

* 使用到INFRA的特性
* 應用1和2 -> 系統要避免SPF，**使用到distribution特性**
* 應用2 -> 供應鏈的智慧工廠要串聯，並使用同一套碳盤查系統，**使用到synchronization特性**