Mingcedar capabilities and runtime model | Mingcedar

<div class="manual-doc-article manual-doc-article-section"><h2 id="what-can-do">User guide: Mingcedar capabilities and runtime model</h2>

Learn the roles of runtime services, Admin, runtime pages and Settings.

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

<article class="doc-card">

<h3 id="what-can-do-item-1">Runtime services</h3>

<p>Web/App provides browser access; IO collects device data; Alarm, Trend and Script handle alarms, history and project logic. Check services and data infrastructure in System Status.</p>

</article>

<article class="doc-card">

<h3 id="what-can-do-item-2">Administration</h3>

<p>Configure Devices, Tags, calculated Tags, screen files, menus, popups, sites, access, languages and integrations. Entries depend on account permissions and installed modules.</p>

</article>

<article class="doc-card">

<h3 id="what-can-do-item-3">Runtime pages</h3>

<p>Open project screens, alarms and trends through runtime menus. Reading, alarm acknowledgement and device writes follow their respective access and action permissions.</p>

</article>

<article class="doc-card">

<h3 id="what-can-do-item-4">Settings</h3>

<p>Manage display and operation, collection, Python, site connections and video. Preferences, alarm categories and collection policies save independently; other fields apply as indicated.</p>

</article>

</div>

</div>