The purpose of this is to incorporate new process for movement of DoD-to-DoD direct cite MIPRs through a Workflow from Requesting Activity to Servicing Activity, using GEX for mediation.

PIEE will provide a single MIPR document for workflow processing. MIPR documents within PIEE will be based upon the Purchase Request Data Standard:

• Attachment capability
• Use all data elements capable of being transmitted via the PRDS XML.
• MIPRs may be originated either within an external System or manually via the PIEE web interface.
• Electronic Transactions will be transmitted via Purchase Request Data Standard XML schema.

MIPR user registration will leverage the PIEE Group Structure with a unique tree structure for the following MIPR roles:

• PR Administrator - MIPR user administration
• PR Initiator – Government or Government Support Contractor
• PR Submitter – Government role
• PR Financial Manager Reviewer - Government or Government Support Contractor
• PR Financial Manager - Government role
• PR Submission Approver – Government role
• PR Acceptor Reviewer - Government or Government Support Contractor
• PR Acceptor - Government role
• PR View Only - Government or Government Support Contractor

NOTE: PR roles will be prompted to register with appropriate EDA MIPR role

PIEE will also provide for the creation of a MIPR Electronically or via the web interface:

Requesting Office will be able to initiate MIPRs using previously submitted / processed MIPRs from their agency (Template).

• Requesting Office will be able to resubmit MIPRs as a complete overwrite. System will implement the MIPR amendment number as a “one up” from the source document.
• The system will forward a notification to the Servicing Activity that a MIPR was submitted to them.

MIPR Workflow Incorporation into the Procurement Integrated Enterprise Environment Demos:

The purpose of this is to update eMIPR to use the PRDS 2.0 Schema. There will be no backwards compatibility with PRDS 1.1.

Purchase Request Description will be defaulted to ‘Requesting Agency Order Number’ for eMIPR create.

Line Item numbering will utilize the DFARS element.

For external submission, the Purchase Request will be rejected if:

• There are multiple iterations of Purchase Request Identifier.
• Purchase Request Description is not ‘Requesting Agency Order Number’.
• Enterprise Identifier, Serial Number, and Purchase Request Revision Number are blank.
• LOA or SLOA elements are used instead of the Blob element for accounting.

The purpose of this is to provide the following eMIPR enhancements:

Total Price Calculation:

Populate Item Committed Amount with the product of that Item’s Quantity and Unit Price from Section B. The user may edit the Item Committed Amount in Section G.

Submission Notifications:

Additional workflow email notifications have been created that will include the MIPR Number and Action Taken.

Submission Help/Field Definitions:

A new ‘Info’ option has been added to the top menu.

This Information page will include links to a Data Dictionary and Documentation on external submission, acceptance and accounting.

Signature Visibility:

The Sign and Submit button will yield a popup when clicked. The user selects the signing certificate or if PKI Exempt, the user’s password is entered.

The History section of the eMIPR has been updated to include ‘Title” and ‘Signed By’ columns. The eMIPR will be signed by the Submitter, Submission Approver, Financial Manager and Acceptor.

The PDF has also been updated to include role, name, title and signature date.