Severity Levels for information required from the system.

This is to define how important the information required is. 

Severity 1 (urgent)   A problem that severely impacts the system.

The situation halts your business operations and no procedural workaround exists.

Severity 2 (high) 

The situation is causing a high impact to portions of your business operations and no procedural workaround exists.

Severity 3 (medium)  

There is a medium-to-low impact on your business, but your business continues to function, including by using a procedural workaround.

Severity 4 (low)   

There is low-to-no impact on your business or the performance or functionality of your system. For development environments, there is a medium-to-low impact on your business, but your business continues to function, including by using a procedural workaround.

Also a single point of contact from the organization which needs the system built. 

Person assigned to coordinate so you are informed only when something is stuck and only your authority can be used to get it unstuck

Single point of contact from the buyer side ( of the project ) to ATRC for the project.

Single so they cannot expect anyone else to be the excuse and shift blame for not passing on the information. 

The SPC from the buyer side is to be appointed by the business owners. 

The PM from the supplier side ( ATRC ) shall be appointed by the top management of ATRC. 

ATRC shall appoint the project manager from the supplier side so the PM is responsible for informing and coordinating with everyone for the project.