What the plugin does in the whole system | Mingcedar Studio

<div class="manual-doc-article manual-doc-article-section"><h2 id="foundation">Basics: What the plugin does in the whole system</h2>

Mingcedar Studio is the authoring side. It creates screens and exports runtime assets; Mingcedar runs them.

<div class="doc-card-list">

<article class="doc-card">

<h3 id="foundation-item-1">Position in the architecture</h3>

<p>Mingcedar Studio creates and exports screens, and Mingcedar hosts runtime configuration, permissions, licensing, menus, alarms, trends, and scripts. Mingcedar Scan is a separate tool for projects that need TIA / PLC DB point preparation.</p>

</article>

<article class="doc-card">

<h3 id="foundation-item-2">What belongs in PowerPoint</h3>

<p>Layout, components, text, colors, animations, popup behavior, navigation behavior, and template parameters belong in the PowerPoint authoring workflow.</p>

</article>

<article class="doc-card">

<h3 id="foundation-item-3">What belongs in Mingcedar</h3>

<p>Devices, tags, users, permissions, menus, published screen files, license state, alarm history, trend history, APIs, and scripts belong in Mingcedar.</p>

</article>

</div>

</div>