Difference between revisions of "Non-continuance-payment-policy"

From HPC Guide
Jump to navigation Jump to search
orig>Wiki admin
(Created page with "'''The Policy in case of non-continuance payment for services''' See in the table below our policy in case a PI stops his budget transfers to the computation center for one o...")
 
m (4 revisions imported)
 
(3 intermediate revisions by one other user not shown)
Line 1: Line 1:
'''The Policy in case of non-continuance payment for services'''
+
'''See the table below our policy in case of non-continuance payment for services'''
 
 
See in the table below our policy in case a PI stops his budget transfers to the computation center for one of the HPC team Services.
 
  
 
{| class="wikitable"
 
{| class="wikitable"
|+ Caption text
+
|+ The HPC team policy in case a PI stops his budget transfers to the computation center for one of the HPC team Services
 
|-
 
|-
 
! Service Type !! Issue !! Policy
 
! Service Type !! Issue !! Policy
 
|-
 
|-
| Power || empty budget || the HPC team will stop their supporting service within a month
+
| Power cluster || empty budget || the HPC team will stop their supporting service within a month
 +
|-
 +
| Power cluster || blocked budget || the HPC team will stop their supporting service within a month
 +
|-
 +
| Power cluster || budget incompatibility || the HPC team will stop their supporting service within a month
 +
|-
 +
| Stand alone cluster in our DC || empty budget || the HPC team will stop their supporting service within a month, the cluster will be disconnected and returned to owner within two months of none payment
 +
|-
 +
| Stand alone cluster in our DC || blocked budget || the HPC team will stop their supporting service within a month, the cluster will be disconnected and returned to owner within two months of none payment
 +
|-
 +
| Stand alone cluster in our DC || budget incompatibility || the HPC team will stop their supporting service within a month, the cluster will be disconnected and returned to owner within two months of none payment
 +
|-
 +
| Minimal service in our DC || empty budget || the cluster will be disconnected within a month and returned to it's owner within two months of none payment
 +
|-
 +
| Minimal service in our DC || blocked budget || the cluster will be disconnected within a month and returned to it's owner within two months of none payment
 +
|-
 +
| Minimal service in our DC || budget incompatibility || the cluster will be disconnected within a month and returned to it's owner within two months of none payment
 +
|-
 +
| Remote Stand alone cluster || empty budget || the HPC team will stop their supporting service within a month
 +
|-
 +
| Remote Stand alone cluster || blocked budget || the HPC team will stop their supporting service within a month
 +
|-
 +
| Remote Stand alone cluster || budget incompatibility || the HPC team will stop their supporting service within a month
 +
|-
 +
| Remote Stand alone workstation || empty budget || the HPC team will stop their supporting service within a month
 
|-
 
|-
| Power || blocked budget || the HPC team will stop their supporting service within a month
+
| Remote Stand alone workstation || blocked budget || the HPC team will stop their supporting service within a month
 
|-
 
|-
| Power || budget incompatibility || the HPC team will stop their supporting service within a month
+
| Remote Stand alone workstation  || budget incompatibility || the HPC team will stop their supporting service within a month
 
|}
 
|}

Latest revision as of 08:33, 5 April 2022

See the table below our policy in case of non-continuance payment for services

The HPC team policy in case a PI stops his budget transfers to the computation center for one of the HPC team Services
Service Type Issue Policy
Power cluster empty budget the HPC team will stop their supporting service within a month
Power cluster blocked budget the HPC team will stop their supporting service within a month
Power cluster budget incompatibility the HPC team will stop their supporting service within a month
Stand alone cluster in our DC empty budget the HPC team will stop their supporting service within a month, the cluster will be disconnected and returned to owner within two months of none payment
Stand alone cluster in our DC blocked budget the HPC team will stop their supporting service within a month, the cluster will be disconnected and returned to owner within two months of none payment
Stand alone cluster in our DC budget incompatibility the HPC team will stop their supporting service within a month, the cluster will be disconnected and returned to owner within two months of none payment
Minimal service in our DC empty budget the cluster will be disconnected within a month and returned to it's owner within two months of none payment
Minimal service in our DC blocked budget the cluster will be disconnected within a month and returned to it's owner within two months of none payment
Minimal service in our DC budget incompatibility the cluster will be disconnected within a month and returned to it's owner within two months of none payment
Remote Stand alone cluster empty budget the HPC team will stop their supporting service within a month
Remote Stand alone cluster blocked budget the HPC team will stop their supporting service within a month
Remote Stand alone cluster budget incompatibility the HPC team will stop their supporting service within a month
Remote Stand alone workstation empty budget the HPC team will stop their supporting service within a month
Remote Stand alone workstation blocked budget the HPC team will stop their supporting service within a month
Remote Stand alone workstation budget incompatibility the HPC team will stop their supporting service within a month