Project handover and maintenance records | Mingcedar

<div class="manual-doc-article manual-doc-article-section"><h2 id="delivery">User guide: Project handover and maintenance records</h2>

Hand over access endpoints, configuration, maintenance information and recovery steps.

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

<article class="doc-card">

<h3 id="delivery-item-1">Runtime information</h3>

<p>Record information matching the delivered project version.</p>

<ol>

<li>List the release, operating system, architecture, protocol drivers, Python and dependency versions.</li>

<li>Record Portal and Screen endpoints, site relationships, Device and Tag codes, screen menus and runtime services.</li>

<li>Document role responsibilities and account handover; transfer credentials separately through a controlled channel.</li>

</ol>

</article>

<article class="doc-card">

<h3 id="delivery-item-2">Operations and maintenance windows</h3>

<p>Document daily monitoring, incident handling and maintenance timing.</p>

<ol>

<li>Retain key Tag verification results and operating procedures for alarm acknowledgement, trends, script triggers and API access.</li>

<li>Identify owners and schedules for configuration changes, restarts and device maintenance.</li>

<li>Record capacity and retention policies, including routine disk, archive and service checks.</li>

</ol>

</article>

<article class="doc-card">

<h3 id="delivery-item-3">Backup and recovery information</h3>

<p>Provide usable backup locations and restoration steps.</p>

<ol>

<li>Document backup contents, frequency, location and matching versions.</li>

<li>Record restoration results for licensing, screens, data and site relationships.</li>

<li>Provide maintenance contacts and upgrade instructions, plus known limitations and their handling.</li>

</ol>

</article>

</div></div>