1. SPS Spotlight Series October 2014
PDS Punch-Out v1.0
SPS Spotlight Series
October 2014
This guide will provide additional information for PDS.

2. This information was originally created for The SPS Spotlight Series project, which ran from November 2013 through November Updates to the original content may be incorporated to ensure accuracy. If you have any questions about this information, please contact the SPS Help Desk at

3. Definition Procurement Data Standard (PDS)
The Procurement Data Standard (PDS) is a system-agnostic data standard that is intended to be adopted and implemented DoD-wide for creation, translation, processing, and sharing of procurement actions. It defines the minimum requirements for contract writing system output to improve visibility and accuracy of contract-related data, to support interoperability of DoD acquisition systems and to standardize and streamline the procure-to-pay business process.
For more information see the PDS Home Page
d.html
These are common phrases used with PDS. Examples of the PDS Event Subscriptions will be shown later in this presentation.

4. Background information
Currently, some SPS contracts are being completed in a manner that does not pass validation edits for the Procurement Data Standard (PDS).
The PDS Punch-Out will provide the ability for users to send a document to the PDS system for validation prior to release.
A standard approval template name will be recognized as a trigger for the PDS Punch-Out Utility to translate the SPS XML to the PDS XML format and send the document to the PDS validation service. Upon receipt of the PDS validation service response, a sticky note containing the validation result (valid or invalid) and a single alert informing the user of the completion of the PDS validation process will be created in PD². If the validation result is invalid, an attachment will be inserted to view validation details.
Services/sites will need to update their agreements and set-up their channel with DLA/GEX in order to use this new functionality.

5. Installation of PDS Punch-Out
Pre-Requisites to Installation
PDS package should be installed and properly configured
Site needs to be on PD² SR14/SR14a or SR15
Download and Install the PDSValidation.zip Package
Create a File Polling Port on Integration Server page
Create PDS Validation Template in PD²
Update PD2 Database Trigger for PDS Validation
Configure PDS Validation Service Communication
Add PDS Punch-Out Configurations to AMSCommonProperties.prop file

6. PDS Validation Template
The “PDS Validation” approval template is used by functional users to flag procurement documents for submission to the PDS Validation Service.
The PDS Validation Template is created via a script that is run against the PD² database.
This script will be found in the newly installed PDSValidation package folder on the PD² Adapter server.

7. Update PD2 Database Trigger for PDS Validation
A standard PD2 Database Trigger must be updated to capture the new PDS Validation events.
The Database Trigger updates are to be ran against the PD² database.
These scripts will be found in the newly installed PDSValidation package folder on the PD² Adapter server.

8. Configure PDS Validation Service Communication
The primary purpose of PDS Punch-Out is to communicate with the PDS Validation Service. PDS Punch-Out can synchronously or asynchronously exchange information with the PDS Validation Service. The default configuration will use asynchronous communication
Synchronous configuration features:
Submits it to the PDS Validation Service via an HTTPS connection
Keeps the HTTPS open until results are received
Appropriate for sites that produce small, less complicated PDS documents, and have low network latency.
Asynchronous configuration features:
Writes the PDS document to the file system
An external process periodically submits the PDS documents to the PDS Validation Service
Appropriate for most sites. These sites are either producing many large or a few very large PDS documents or have bandwidth limitations.

9. Configure PDS Validation Service Communication cont’d - Asynchronous
PDS Validation creates new events in the PD² Event Subscription table in the PD² database.
Adding Asynchronous Event Subscriptions is done via a script. This script will be found in the newly installed PDSValidation package folder on the PD² Adapter server.
The Asynchronous configuration writes outbound files to a configured local directory and picks up response files from a configured local directory. It is each site’s responsibility to transmit the files to and from the PDS Validation Service. This is typically done by an SFTP batch process, but the method of transmission may vary from site to site.

10. Asynchronous Event Subscriptions

11. Configure PDS Validation Service Communication cont’d - Synchronous
PDS Validation creates new events in the PD² Event Subscription table in the PD² database.
Adding Synchronous Event Subscriptions is done via a script. This script will be found in the newly installed PDSValidation package folder on the PD² Adapter server.
The Synchronous configuration requires the creation of a TN Trading Partner in MWS (Administration > Integration > B2B > Partner Administration > Partner Profiles )
The Delivery Method values (Host, Port, Location, User Name and Password) will be provide by GEX.
In the AMSCommonProperties.prop file the caci.pdsval.synchProfileDuns value should match the DUNS value of the PDS Validation TN Partner profile.

12. Synchronous Event Subscriptions

13. Add PDS Punch-Out Configurations
Adding the PDS Punch-Out configurations to the PD2 Adapter’s configuration file involves running a batch file that inserts additional rows to the AMSCommonProperties.prop file.
Values that need to be updated within the AMSCommonProperties.prop file include:
the caci.pdsval.asynchOutDir - represents the directory that will store outbound PDS documents.
the caci.pdsval.monitorDir - represents the directory where the responses from the PDS Validation Service will be picked up by the webMethods Integration Server.
the caci.pdsval.synchProfileDuns value should match the DUNS value of the PDS Validation TN Partner profile.

14. Create a File Polling Port
A file polling port periodically polls the monitoring directory for the arrival of files and then performs special processing on them.
Adding a file polling port is done on the Integration Server page under Security > Ports link.
The value in the Monitoring Directory text box should match the value of the caci.pdsval.monitorDir configured in the AMSCommonProperties.prop file.

15. Create a File Polling Port continued

16. Selecting Document for Validation
Only documents that are valid for translation into the PDS format will be transmitted for validation.
Users will not be required by the system to submit a document to the PDS Punch-out or to pass all PDS validations prior to releasing a document.
To select a document to submit to PDS Punch-Out, users must apply the PDS Validation approval template. From the menu bar, select Procurement --> Approvals.
From the list of Approval Templates, select the PDS Validation approval template.

17. Selecting Document for Validation continued

18. Validation Info
Upon completion of processing of the validation, an alert informing the user of the completion of the PDS validation process will be created in PD2. A Sticky Note will be placed on the document with the validation status and attachment information, if applicable.
If there were any validation messages, a PDS Validation attachment containing the messages will be placed in the same container as the document being validated. Double-clicking the attachment will open MS Word and display the messages.
To resubmit a document for PDS Validation after updates or corrections have been made, repeat the process of adding a PDS Validation Approval Sheet. Any messages associated with a resubmitted validation will be contained in a new attachment.

19. Passed Validation Sticky Note

20. Failed Validation Sticky Note

21. PDS Validation attachment

22. PDS Validation attachment continued