Help:Contracts

From Navigates Help

This help page will guide you through the process of creating contracts. The procedure consists of four required steps: Entering General information, Entering Rights, Submitting the Contract and Clearing Messages, and Executing the Contract.

[edit] Step 1: Enter General Information

(Fig. 1.1: Blank contract form)

(Fig. 1.2: Contract general info)

Select Customer Activities -> Contracts -> Contract. You will be directed to the Contract screen.
Click at the top of the screen. A blank contract form will come up. (Fig. 1.1) You also have an option of copying an existing contract. To do so, retrieve the contract you wish to copy, click and proceed with updating the fields, as necessary.
Enter the following required information (when available, you may click on the ellipsis to bring up the lookup fields):
- Service Requester (name of the customer associated with the contract).
- Service (type of service that the contract covers).
- Begin Date (begin date for the contract).
- End Date (end date for the contract).
- Requested by Name (customer contact name).
- Requested by Phone (contract phone number).
Click to save your contract. The systems will assign a unique identifier, also known as Contract Number (displayed in the Svc Req K field).(Fig. 1.2)

[edit] Step 2: Enter Rights

The Rights Input screen will change depending on the service you have selected. Please refer to the appropriate instructions when entering rights.
When you are done entering rights for your contract, select Screen Function >> RunRightsConfigurator.

[edit] FTS
Input Type: Contract Information Expanded (Fig. 2.1) Click at the top of the Contract Information Expanded matrix. Enter the following required information: Eff Begin Date. Eff End Date (the dates must span the entire contract period). MDCQ (total contract quantity). Reg ROFR. Contract ROFR. Click .	(Fig. 2.1: FTS Rights. Input Type: Contract Information Expanded)
Input Type: Point (Fig. 2.2) Click at the top of the Point matrix. Enter the following required information: Loc Code (you must have a valid point pair (Rct and Del) on the transport contract). Dir of Flow (must match the point's direction of flow). Prim/Sec Identifier (you must have one primary receipt and one primary delivery point). Point MDO Volume High (total receipt and total delivery quantities must equal the contract MDCQ unless you set Volume Match to No). Click .	(Fig. 2.2: FTS Rights. Input Type: Point)
[edit] FSS
Input Type: Contract Information Storage (Fig. 2.3) Click at the top of the Contract Information Storage matrix. Enter the following required information: Eff Begin Date. Eff End Date (the dates must span the entire contract period). Reg ROFR. Contract ROFR. Click .	(Fig. 2.3: FSS Rights. Input Type: Contract Information Storage)
Input Type: Inventory FSS (Fig. 2.4) Click at the top of the Inventory FSS matrix. Enter the following required information: Eff Begin Date. Eff End Date (the dates must span the entire contract period). Capacity (MSQ). Deliverability (MDSQ). Click .	(Fig. 2.4: FSS Rights. Input Type: Inventory FSS)
[edit] IPP
Input Type: Contract Information (Fig. 2.5) Click at the top of the Contract Information matrix. Enter the following required information: Eff Begin Date. Eff End Date (the dates must span the entire contract period). MDCQ (enter 999,999,999). Click .	(Fig. 2.5: IPP Rights. Input Type: Contract Information)
Input Type: Point Interruptible (Fig. 2.6) Click at the top of the Point Interruptible. Enter the following required information: Loc Code (You must enter the pooling points. TCO contracts will have one P10 pool; CGT contracts will have P20, P30 and P40 pools. For TCO pools, the contract point code should consist of P10 + contract number -- 4 or 5 digits. For 6 digit contracts, use the last 5 digits. For CGT pools, the contract code should consist of P20 (mainline), P30 (onshore), P40 (offshore) + contract number. Do not enter any physical points). Dir of Flow (Pooling points are Delivery only). Eff Begin Date. Eff End Date (the dates must span the entire contract period). Click .	(Fig. IPP Rights. Input Type: Contract Information)
[edit] ITS
Input Type: Contract Information (Fig. 2.7) Click at the top of the Contract Information matrix. Enter the following required information: Eff Begin Date. Eff End Date (the dates must span the entire contract period). MDCQ. Click .	(Fig. 2.7: ITS Rights. Input Type: Contract Information)
[edit] PAL
Input Type: Contract Information PAL (Fig. 2.8) Click at the top of the Contract Information PAL matrix. Enter the following required information: Eff Begin Date. Eff End Date (the dates must span the entire contract period). Click .	(Fig. 2.8: PAL Rights. Input Type: Contract Information PAL)
[edit] GTS
Input Type: Inventory GTS (Fig. 2.9) Click at the top of the Inventory GTS matrix. Enter the following required information: Eff Begin Date. Eff End Date (the dates must span the entire contract period). Capacity (MSQ). Click .	(Fig. 2.9: GTS Rights. Input Type: Inventory GTS)
Input Type: Contract Information GTS (Fig. 2.9) Click at the top of the Contract Information GTS matrix. Enter the following required information: Eff Begin Date. Eff End Date (the dates must span the entire contract period). MDCQ. ACQ. Reg ROFR. Contract ROFR. Click .	(Fig. 2.9: GTS Rights. Input Type: Contract Information GTS)
Input Type: Point (Fig. 2.10) Click at the top of the Point matrix. Enter the following required information: Loc Code (you must have a valid point pair (Rct and Del) on the transport contract). Dir of Flow (must match the point's direction of flow). Prim/Sec Identifier (you must have one primary receipt and one primary delivery point). Point MDO Volume High (total receipt and total delivery quantities must equal the contract MDCQ unless you set Volume Match to No). Click .	(Fig. 2.10: GTS Rights. Input Type: Point)
[edit] NTS
Input Type: Contract Information Expanded (Fig. 2.11) Click at the top of the Contract Information Expanded matrix. Enter the following required information: Eff Begin Date. Eff End Date (the dates must span the entire contract period). MDCQ (total contract quantity). Reg ROFR. Contract ROFR. Click .	(Fig. 2.11: NTS Rights. Input Type: Contract Information Expanded)
Input Type: Point (Fig. 2.12) Click at the top of the Point matrix. Enter the following required information: Loc Code (you must have a valid point pair (Rct and Del) on the transport contract). Dir of Flow (must match the point's direction of flow). Prim/Sec Identifier (you must have one primary receipt and one primary delivery point). Point MDO Volume High (total receipt and total delivery quantities must equal the contract MDCQ unless you set Volume Match to No). Click .	(Fig. 2.12: NTS Rights. Input Type: Point)
[edit] SIT
Input Type: Contract Information Conforming (Fig. 2.13) Click at the top of the Contract Information Conforming matrix. Enter the following required information: Eff Begin Date. Eff End Date (the dates must span the entire contract period). Click .	(Fig. 2.13: SIT Rights. Input Type: Contract Information Conforming)
Input Type: Inventory SIT (Fig. 2.14) Click at the top of the Inventory SIT matrix. Enter the following required information: Eff Begin Date. Eff End Date (the dates must span the entire contract period). Space (MBQ). Click .	(Fig. 2.14: SIT Rights. Input Type: Inventory SIT)
[edit] SST
Input Type: Contract Information Expanded (Fig. 2.15) Click at the top of the Contract Information Expanded matrix. Enter the following required information: Eff Begin Date. Eff End Date (the dates must span the entire contract period). MDCQ (total contract quantity). Reg ROFR. Contract ROFR. Specify seasonality in the RecStart and RecEnd fields (enter 4/1 - 9/30 for the summer season and 10/1 - 3/31 for the winter season). Click .	(Fig. 2.15: SST Rights. Input Type: Contract Information Expanded)
Input Type: Point (Fig. 2.16) Click at the top of the Point matrix. Enter the following required information: Loc Code (you must have a valid point pair (Rct and Del) on the transport contract). Dir of Flow (must match the point's direction of flow). Prim/Sec Identifier (you must have one primary receipt and one primary delivery point). Point MDO Volume High (total receipt and total delivery quantities must equal the contract MDCQ for the specified date range/season unless you set Volume Match to No). Specify the season in the RecStart and RecEnd fields. You will have two entries for each point. Click .	(Fig. 2.16: SST Rights. Input Type: Point)

[edit] Step 3: Submit

(Fig. 3.1: Contract Submission Successful)

(Fig. 3.2: Contract Submission Successful. Warning messages displayed)

(Fig. 3.3: Contract Submission Failed. Error messages displayed)

Select Screen Functions -> Submit Contract in order to submit contract. Note that after you do so, you will not be able to change General Information or Rights through the contract screen. Such updates will be permitted only through the Amendment process.
After the contract is submitted, you will see a confirmation message at the bottom of the screen.
If the message states that Contract Submission was successful, you may proceed to Executing the contract in step 4 (Fig. 3.1).
If the message states that Contract Submission was successful but has warnings, you will need to clear the messages before proceeding with execution (Fig. 3.2).
If the message states that contract Submission failed, you will need to correct the errors before re-submitting the contract (Fig. 3.3).

[edit] Warning Messages

(Fig. 3.4: Warning message cleared and saved.)

Switch to the Messages tab to view warning messages. While the cause did not prevent you from submitting the contract, you must acknowledge the presence of the issue by checking the Cleared checkbox before you can execute the contract (Fig. 3.4). Save when done.

[edit] Error Messages

If the contract submission failed, you can review the reason(s) on the Messages tab. You will have to address the issues marked as Error before you can re-submit the contract. Clearing the messages by checking the Cleared checkbox will not make the problem go away.
Below is the list of common error messages and solutions.

Error Message	Cause	Solution
Multiple errors related to points & quantities	RightConfigurator was not run	Select Screen Functions -> RunRightsConfigurator
Execution error in workflow Submissions Validations	RightConfigurator was not run	Select Screen Functions -> RunRightsConfigurator
There must be at least one primary receipt and delivery point	Either receipt or delivery point is missing, or both	Enter the proper point pair on the Rights Input screen
Contract quantity right must exist	Contract quantity was not specified	Enter the contract quantity on the Rights Input screen
The first quantity begin date must equal to agreement primary term begin date	Contract quantity Eff Beg Dt is not the same as the contract Begin Date	Either change the contract begin date on the Main Tab or the quantity Eff Begin Date on the Rights Input screen so that the two match
Contract quantities must span entire contract period	Contract quantity dates do not match the contract dates	Update either pair so that they match
Service Requester is not valid for the period	BA either expired or is not associated with the asset	Update the expiration date on the Data Administration >> Business Associate screen or add a proper Asset/BA relationship
The contacts for the GM role do not span the entire agreement period	General Mailing contact missing or does not cover the entire duration of contract	Add the contact or update the dates of an existing GM contact either on the External Contacts screen or on the Data Administration >> Contacts screen
The contacts for the B1 role do not span the entire agreement period	Billing-1 contact missing or does not cover the entire duration of contract	Add the contact or update the dates of an existing B1 contact either on the External Contacts screen or on the Data Administration >> Contacts screen

NOTE: If you change anything on the Rights Input screen, you MUST re-run RightsConfigurator.

[edit] Step 4: Execute

(Fig. 4.1: Approval Tab)

(Fig. 4.2: Approval status changed)

(Fig. 4.3: Contract is executed)

Complete the following steps to execute the contract.

Switch to the Approval tab.
Change the status of each approval from Not Yet Reviewed to Approved.
Click .
Repeat the change of status for all entries in the list. When you are done, the Status fields will turn gray and the contract status will change to Executed.

[edit] Step 5: Additional Screens

There are several screens available for entering additional information related to the contract. These screens are optional and may be filled out for a contract in any status other than Terminated or Withdrawn.

Screen	Function	Usage Instructions
[edit] Additional Info	Allows you to update information about the contract usage and ownership.	Update data as needed for the fields located in the upper part of the screen or click the [New] button at the top of Service Requester History or Contract Use Type to update the matrices. Save.
[edit] Related Contract	Allows you to create relationships between contracts.	Click the [New] button at the top of the Forward Relationships matrix, fill out required fields and save.
[edit] Agency	Allows you to add a contract agent.	Click the [New] button, fill out required fields and save.
[edit] Internal Contacts	Allows you to add internal contacts.	Click the [New] button, fill out required fields and save.
[edit] External Contacts	Allows you to add external contacts. Note that each contract has to have Billing-1 and General Mailing contacts before it can be submitted.	Click the [New] button, fill out required fields, or update an existing record. Save.
[edit] Contract Footnotes	Allows you to add contract footnotes.	Click the [New] button, enter footnote in the Comment Text field and save.
[edit] Customer Service Comments	Allows you to add contract comments.	Click the [New] button, specify comment visibility, enter comment in the Comment Text field and save.
[edit] Price Inputs	Allows you to add price discounts to certain services.	Click the [New] button at the top of the appropriate matrix and specify your discounts, then save. *Select Screen Functions -> RunPriceConfigurator* when finished.**
[edit] Price Comments	Allows you to add contract pricing comments.	Click the [New] button, specify comment visibility, enter comment in the Comment Text field and save.