User Tools

Site Tools


ddsf:public:guidebook:03_user:03_tms

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
ddsf:public:guidebook:03_user:03_tms [2021/07/14 15:55]
murphy ↷ Links adapted because of a move operation
ddsf:public:guidebook:03_user:03_tms [2021/09/02 19:43] (current)
mitza [Table]
Line 1: Line 1:
 ====== Use Case 2: Tactical Microgrid Standard (TMS) ====== ====== Use Case 2: Tactical Microgrid Standard (TMS) ======
 [[ddsf:​public:​guidebook:​03_user:​start| Return to User Experiences]] [[ddsf:​public:​guidebook:​03_user:​start| Return to User Experiences]]
- 
-  * **<color #​FF0000><​todo @char>​Please Review</​todo></​color>​** 
-  * **<color #​FF0000><​todo @DDSFmember>​Please Review</​todo></​color>​** 
- 
  
 ===== Details ===== ===== Details =====
  
-^ Author ​      ​| Daniel Herring | +^ Author ​       | Daniel Herring ​                                                                                                                                                            ​
-^ Title        | Associate Staff | +^ Title         ​| Associate Staff                                                                                                                                                            
-^ Organization | MIT Lincoln Laboratory | +^ Organization ​ | MIT Lincoln Laboratory ​                                                                                                                                                    ​
-^ Date         ​| 28 May 2020 | +^ Date          | 28 May 2020                                                                                                                                                                
-^ Time         ​| 31 Minutes | +^ Time          | 31 Minutes ​                                                                                                                                                                ​
-^ Presentation | [[https://​www.brighttalk.com/​webcast/​12231/​401676?​utm_campaign=channel-feed&​utm_source=brighttalk-portal&​utm_medium=web | Pactical ​Microgrid Standard - DDSF BrightTalk ]] | +^ Presentation ​ | [[https://​www.brighttalk.com/​webcast/​12231/​401676?​utm_campaign=channel-feed&​utm_source=brighttalk-portal&​utm_medium=web| ​Tactical ​Microgrid Standard - DDSF BrightTalk ]]  
-^ Document ​    ​| [[http://​public2.brighttalk.com/​resource/​core/​274119/​dds-foundation_tms-use-case-20200527_609918.pdf | Pactical ​Microgrid Standard ]] |+^ Document ​     | [[http://​public2.brighttalk.com/​resource/​core/​274119/​dds-foundation_tms-use-case-20200527_609918.pdf| ​Tactical ​Microgrid Standard ]]                                       ​|
  
 ===== Tactical Microgrid Standard (TMS) Using DDS for Secure Communications ===== ===== Tactical Microgrid Standard (TMS) Using DDS for Secure Communications =====
Line 165: Line 161:
   * **[[ddsf:​public:​guidebook:​06_append:​glossary:​c:​cntrgrid]]** locates all the generators in one location and then fans out all the power through a **Transmission Network** to all the tents that require power. The **Central Microgrid** combines the positive characteristics of the **Spot** and **Consolidated Generation** into a single architecture by providing some backup generation capabilities. For example, extra generator(s) can be located on the site providing redundancy to protect against generator fails by balancing the power production to the extra generator(s). Unfortunately,​ there is even more dependent on cables om the **Transmission Network**. ​ Another drawback is that **Central Microgrids** available in the market place today require one vendor for all generators at a site meaning that you can not mix and match across generators from different companies or even within product lines from  single company due to issues in communication control as well as other aspects of how the system function. There are some actual deployments available in the marketplace today, the [[https://​asc.army.mil/​web/​portfolio-item/​cs-css-advanced-medium-mobile-power-source-ammps/​ | Advanced Medium Mobile Power System (AMMPS)]] Microgrid is being deployed in the DoD inventory with a 2019 purchase another $0.5B worth of available equipment. ​   * **[[ddsf:​public:​guidebook:​06_append:​glossary:​c:​cntrgrid]]** locates all the generators in one location and then fans out all the power through a **Transmission Network** to all the tents that require power. The **Central Microgrid** combines the positive characteristics of the **Spot** and **Consolidated Generation** into a single architecture by providing some backup generation capabilities. For example, extra generator(s) can be located on the site providing redundancy to protect against generator fails by balancing the power production to the extra generator(s). Unfortunately,​ there is even more dependent on cables om the **Transmission Network**. ​ Another drawback is that **Central Microgrids** available in the market place today require one vendor for all generators at a site meaning that you can not mix and match across generators from different companies or even within product lines from  single company due to issues in communication control as well as other aspects of how the system function. There are some actual deployments available in the marketplace today, the [[https://​asc.army.mil/​web/​portfolio-item/​cs-css-advanced-medium-mobile-power-source-ammps/​ | Advanced Medium Mobile Power System (AMMPS)]] Microgrid is being deployed in the DoD inventory with a 2019 purchase another $0.5B worth of available equipment. ​
  
-  * **[[ddsf:​public:​guidebook:​06_append:​glossary:​d:​distgrid]]** is attractive because it has the efficiency of the **Central Microgrid** but also has redundant **Transmission Network** cabling. In a **Distributed Microgrid** each generator'​s load is independently adjustable resulting in a more complicated control problem. Consequently,​ __with existing technologies__,​ it is more complicated to setup and has more proprietary [[ddsf:private:​guidebook:​06_append:​glossary:​v:​vendorlockin|vendor lock-in]]. **Note:** in a **Central Microgrid**,​ all the generators must support an equal fraction of the load. +  * **[[ddsf:​public:​guidebook:​06_append:​glossary:​d:​distgrid]]** is attractive because it has the efficiency of the **Central Microgrid** but also has redundant **Transmission Network** cabling. In a **Distributed Microgrid** each generator'​s load is independently adjustable resulting in a more complicated control problem. Consequently,​ __with existing technologies__,​ it is more complicated to setup and has more proprietary [[ddsf:public:​guidebook:​06_append:​glossary:​v:​vendorlockin|vendor lock-in]]. **Note:** in a **Central Microgrid**,​ all the generators must support an equal fraction of the load. 
  
 In summary, Figure {{ref>​BeforTms}} graphicaly represents the Tactical Microgrid landscape before TMS.  In summary, Figure {{ref>​BeforTms}} graphicaly represents the Tactical Microgrid landscape before TMS. 
Line 316: Line 312:
     * Rich Quality of Service (QoS) allows for the tune it to support many different data flows.     * Rich Quality of Service (QoS) allows for the tune it to support many different data flows.
     * Portable [[ddsf:​public:​guidebook:​06_append:​glossary:​a:​api]]     * Portable [[ddsf:​public:​guidebook:​06_append:​glossary:​a:​api]]
-    * Interoperable [[ddsf:private:​guidebook:​06_append:​glossary:​w:​wireprotocol|wire protocol]]+    * Interoperable [[ddsf:public:​guidebook:​06_append:​glossary:​w:​wireprotocol|wire protocol]]
     * Security architecture provided a near term capability and an upgrade roadmap     * Security architecture provided a near term capability and an upgrade roadmap
  
Line 341: Line 337:
   * **[[ddsf:​public:​guidebook:​06_append:​glossary:​p:​pdf]]** providing some human readable documentation about TMS: what things are; and how things work    * **[[ddsf:​public:​guidebook:​06_append:​glossary:​p:​pdf]]** providing some human readable documentation about TMS: what things are; and how things work 
   * **[[ddsf:​public:​guidebook:​06_append:​glossary:​i:​idl]]** providing machine readable information about the [[ddsf:​public:​guidebook:​06_append:​glossary:​t:​topic]],​ [[ddsf:​public:​guidebook:​06_append:​glossary:​d:​datatype| datatypes]]   * **[[ddsf:​public:​guidebook:​06_append:​glossary:​i:​idl]]** providing machine readable information about the [[ddsf:​public:​guidebook:​06_append:​glossary:​t:​topic]],​ [[ddsf:​public:​guidebook:​06_append:​glossary:​d:​datatype| datatypes]]
-  * **[[ddsf:private:​guidebook:​06_append:​glossary:​x:​xml]]** providing machine readable information about QoS and system configuration. ​+  * **[[ddsf:public:​guidebook:​06_append:​glossary:​x:​xml]]** providing machine readable information about QoS and system configuration. ​
  
 **OMG** provides **DDS** and related products artifacts: **OMG** provides **DDS** and related products artifacts:
ddsf/public/guidebook/03_user/03_tms.1626292555.txt.gz · Last modified: 2021/07/14 15:55 by murphy