Page 325 - Tech handbook 2019 rev 6 whyperlinks

Contract Management

Newly Signed LTSA

- Agreement is negotiated and fully executed by VP of Product Support through Sales
Support Engineer.
- Signed LTSA and cost calculation files are forwarded to Contract Manager &
Administrative Coordinator.
- HITLIST

____ Folder is created on SharePoint in Corresponding Branches site.

____ Location: “NES & WES Product Support - NES [WES] Contracts\LTSAs\LTSA
NAME”.
____ Fully signed agreement is named: “! ! FINAL Signed LTSA NAME 091616”.
____ Cost calculation files filed here as well.

____ Determine whether the assets are running, if not acquire projected commissioning
date from Product Support or Engineering.

____ Notify branch and initiate invoicing with Product Support Administrator.

____ Schedule LTSA Review meeting, with agenda.
____ Send Welcome Email to any known contacts. Per procedure:
 Attached NES or WES Contact List.
 Confirm that there is a Billing Account set up in the system with credit
terms for Hours Invoicing, if not include credit app.
 Introduce Product Support Administrator as billing contact for credit
application processing (if applicable) and PO collection.
 If commissioned running, begin invoicing OPH immediately
 If awaiting Commissioning await TOE and invoice OPH (per the term
section of the agreement) once received from Commissioning Manager

____ Create D365 Billing Account, Service Location, Assets. This should be created
prior to commissioning if possible to associate commissioning activities with the
asset history. Per procedure:

____ Create Billing Summary as soon as possible after LTSA execution. This should be
no later than engine acquiring 1000 hours. Uploaded to SharePoint for branch
access upon completion. Per Procedure:
 Location: “NES & WES Product Support – NES [WES]
Contracts\LTSAs\LTSA NAME”
 Naming Format: LTSA NAME Maintenance Billing Summary 091616
 Read/Review entire LTSA agreement.