System Design Review

A post-contract system design review (SDR) is necessary because it is seldom, if ever, possible to finalize all details of the design and related project documents in the contract, let alone in the proposal documents.

You need to invest significant time and preparation for the System Design Review (also known as Customer Design Review or Final Design Review). Typically held at your location, the purpose of this meeting (or, in cases of complex projects, series of meetings) is to lock in the design/project plan and enable the vendor internal procurement efforts – production of equipment, purchasing third party devices, signing up subcontractors.

The System Design Review can deliver more than its name implies. For instance, it is a good opportunity to revisit and finalize a number of additional important documents. While every project is an iterative process, there should be very few questions unanswered about project implementation after the SDR is finished.

The following technical documentation is a high level view – you should expect and demand more detailed information from your vendor.

Technical design documentation

  • System architecture
  • Detailed site drawings (RF, dispatch and backhaul equipment configuration, antenna system design, power system design, wiring, grounding, alarms, site improvements or new site details)
  • Detailed list of purchased items including sufficiently described software features and associated licenses

Implementation plan

  • Detailed statement of work identifying resources and assigning responsibilities to the vendor or to the buyer
  • Timeline – typically a detailed Gantt chart with dependencies, resources and critical path identified

Regulatory review – all applicable licenses and permits

  • FCC
  • FAA
  • Environmental
  • Health and Safety
  • Other

Acceptance test plans

  • Factory Acceptance Test Plan (may be more than one, if an elaborate microwave network is being procured with the radio system)
  • Functional Field Test Plan (to verify system functionality after it has been installed)
  • Coverage Acceptance Test Plan/s (may vary by technology, geography, coverage requirements)
  • Burn-in test definitions (if applicable)

Training plans

  • User training
  • Technical training
  • Administrative training

Click "NEXT" to learn about Cutover Plans or select a topic from the menu below.

Implementing your P25 System: Articles

Leave a Reply

Your email address will not be published. Required fields are marked *

Tait Communications

Cookies

This site uses both functional cookies and tracking cookies to help us understand how users interact with the site.

You can choose to disable non-functional cookies if you wish, however we will need to set a functional cookie to respect your choice.

If you do not wish to accept any cookies, you will not be able to continue using this website.

Analytics and tracking

We use trusted third-party analytics providers to help us improve your experience on this website.

Privacy Policy
Privacy settings