SEA Agreements with Partners Tracking

Learning > Record Pages > SEA Agreements with Partners Tracking

Background

The SEA Agreements with Partners Tracking record enables Project Managers to identify agreements early in the project delivery process. Having a record to track agreements prevents projects from moving forward without formal agreements in place. Agreements documented in the record need to be finalized and signed before AD to prevent any issues should the agreements fall through and to not delay the project AD date.

Note: For more detailed information that is not specific to PMWeb, please visit the SEA Document Web Page and the SEA Information Web Page.

Access: This record is located in the Records module of PMWeb under "Custom Forms".

Job Aids

The following job aids and reference guides are relevant to the SEA Agreements with Partners Tracking record:

To request additional training or documentation, please submit a Help Request in PMWeb.

Record Guidance

Record Information Header

In the Record Information header section, PMs select the Project for which to track SEA Agreements. After saving, PMWeb will autopopulate the other fields.

Agreements Table

In the Agreements table, PMs add agreement information to give the ITS Lead an understanding of proposed and existing agreements on the project. When the ITS Lead reviews the Agreement table, they can notify the PM of contracts that may be needed but are not currently planned.

If an agreement exists, PMs must attach supporting documentation in the Attachments tab. The record will be returned to the submitter in Workflow if attachments are missing.

Report Guidance

The SEA Agreements with Partners Tracking report is available in "BI Reporting".

Workflow Guidance

Once the submitter sends the record to Workflow, PMWeb will check to see if the Concept of Operations sub-tab in the SEA Design, Testing, and Validation record has been approved.

If the Concept of Ops has been completed and approved, PMWeb sends the SEA Agreements with Partners Tracking record to the ITS Lead to review and final approve.
If the Concept of Ops has not been completed and approved, PMWeb returns the record to the submitter.

The ITS Lead reviews the record.

If the record is complete, the ITS Lead selects "Final Approve" to approve the record. The Workflow is now complete.
If additional clarification or changes to the record are needed, the ITS Lead selects "Return" and notes the reasoning in the comments field.

The ITS SEA Lead will not be able to "Final Approve" the record until all agreements listed in the Agreements table have a status of "Existing". If there are outstanding agreements that are still "Proposed", the record cannot be completed.

Integration and Trigger Guidance

The following documents must be submitted in the below sequential order, with each document needing to be approved by the ITS Lead prior to the next document being submitted:

Technology/SEA Assessment record
Alternative Analysis (SEA DTV record)
Concept of Operations (SEA DTV record)
System Function Requirement and the High Level System Design can be submitted together (SEA DTV record)
Detailed Level System Design (SEA DTV record)
Testing and Integration (SEA DTV record)
Validation Plan (SEA DTV record)

The following documents can be submitted any time after the Concept of Operations is approved, but must be approved prior to the Validation Plan being submitted:

SEA Maintenance Plan record
SEA Agreements with Partners Tracking record
SEA Standard Operating Procedures (SOP) record

SEA Process Flowchart

The diagram below shows the PM's path to complete the SEA documentation in PMWeb:

FAQs

There are currently no FAQs.

Page updated

Report abuse