This is the Body:

<ul>
  <li><emphasize><strong>Key figures</strong></emphasize>
    <ul>
      <li><strong>Machine parameters</strong> - Name, location, age, intended purposes, operation energy range, plant layout (rough)</li>
      <li><strong>Control system parameters</strong>
        <ul>
          <li>(<emphasize>key characteristics</emphasize> - to be defined)</li>
        </ul>
      </li>
    </ul>
  </li>
  <li><emphasize><strong>Architecture</strong></emphasize>
    <ul>
      <li><strong>Type</strong> - multi-tier?, distributed?, database-centric?, module-based</li>
      <li><strong>Extensions and variations</strong> - deviations from a basic type, e.g. subsystems not fitting into one of the main tiers</li>
      <li><strong>Configurability and flexibility</strong> - possibility to work also with a significantly different number of devices controlled (front-end) or devices involved with the control system (infrastructure)</li>
    </ul>
  </li>
  <li><strong><emphasize>Design and Implementation</emphasize></strong>
    <ul>
      <li><strong>System size</strong>
        <ul>
          <li><emphasize>Scope</emphasize> - What functionality is part of the CS? To which other systems does it interface?</li>
          <li><emphasize>Type and number of front-end devices</emphasize> - Which devices are being controlled and what is their multiplicity?</li>
          <li><emphasize>IT Infrastructure</emphasize> - What is the &quot;grounding&quot; of the control system? How many and type of machines for servers and clients? Which networking infrastructures are deployed?</li>
        </ul>
      </li>
      <li><strong>Hardware</strong>
        <ul>
          <li><emphasize>Requirements</emphasize>
            <ul>
              <li>Functional - Which control tasks are performed in hardware? What capabilities does the hardware meet (PLC, embedded processors, servers, workstations, their processing and interfacing/communication capabilities)</li>
              <li>Non-functional - Timing (required mean and worst case values), Safety (required reliability and redundancy) and Legal (required standards)</li>
            </ul>
          </li>
          <li><emphasize>COTS</emphasize> - As detailed as possible: vendors, products</li>
          <li><emphasize>In-house developed</emphasize>
            <ul>
              <li>Development cost - Budget, time, number of dedicated people: to allow comparison with COTS solutions</li>
              <li>Schedule in the context of the plant construction - To check compatibility with the MedAustron schedule</li>
            </ul>
          </li>
        </ul>
      </li>
      <li><strong>Software</strong>
        <ul>
          <li><emphasize>Requirements</emphasize>
            <ul>
              <li>Functional - Which control tasks are performed in software? What capabilities does the software need to meet (supervisory control, real-time paths)</li>
              <li>Non-functional - Timing (required mean and worst case values), Safety (required reliability and redundancy) and Legal (required standards)</li>
            </ul>
          </li>
          <li><emphasize>Standards</emphasize> - Architecture, Programming Language, Operating System, Communication</li>
          <li><emphasize>COTS</emphasize> - As detailed as possible: vendors, products</li>
          <li><emphasize>In-house developed</emphasize>
            <ul>
              <li>Development cost - Budget, time, number of dedicated people: to allow comparison with COTS solutions</li>
              <li>Schedule in the context of the plant construction - To check compatibility with the MedAustron schedule</li>
            </ul>
          </li>
        </ul>
      </li>
      <li><strong>Process applied</strong>
        <ul>
          <li><emphasize>Standard, deviations from standard or in-house </emphasize>- This should allow to point out correlations between the process applied and the general success and quality of the results</li>
          <li><emphasize>Certification</emphasize> - This should allow to point out parallels to the certification that will be needed at MedAustron and how to achieve it.</li>
        </ul>
      </li>
    </ul>
  </li>
  <li><strong><emphasize>Safety</emphasize></strong>
    <ul>
      <li><strong>General</strong>
        <ul>
          <li><emphasize>Standards applied</emphasize> - Names all safety-related standards that have been met and as far as possible summarizes their content and links to the full documentation</li>
          <li><emphasize>Government rules and regulations</emphasize> - Lists all legal constraints, explains their influence and possibly compares to similar regulations relevant in Austria</li>
          <li><emphasize>Certifications obtained </emphasize>- Lists the name and subject of the certificates, how they were obtained what implications they have for the CS</li>
        </ul>
      </li>
      <li><strong>Specific</strong> - What specific safety measures were taken to protect the …
        <ul>
          <li><emphasize>Personnel</emphasize></li>
          <li><emphasize>Patients</emphasize></li>
          <li><emphasize>Machine</emphasize></li>
          <li><emphasize>Environment</emphasize></li>
        </ul>
      </li>
    </ul>
  </li>
  <li><strong><emphasize>Project management</emphasize></strong>
    <ul>
      <li><strong>Timeline</strong></li>
      <li><strong>Cost</strong> - Can the overall cost be identified? How high is it?</li>
      <li><strong>Problems encountered</strong> - Were they solved or avoided? Are there remaining problems?</li>
      <li><strong>Degree of success</strong>
        <ul>
          <li><emphasize>Schedule met</emphasize></li>
          <li><emphasize>Client &amp; user satisfaction</emphasize> - Is there feedback from operating or medical personnel?</li>
          <li><emphasize>Feature exploitation</emphasize> - Is the provided system adequate for the actual needs? </li>
        </ul>
      </li>
    </ul>
  </li>
</ul>

This is after the list.