PDS Procurement Data Standard SPS Spotlight Series October

PDS- Procurement Data Standard SPS Spotlight Series October 2014 INFORMATION DEPLOYED. SOLUTIONS ADVANCED. MISSIONS ACCOMPLISHED.

This information was originally created for The SPS Spotlight Series project, which ran from November 2013 through November 2015. 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 sps. helpdesk@caci. com. 2 | CACI Information Solutions and Services | October 2014 | CACI Proprietary Information

Overview § § § § § 3 | Introduction to PDS Definitions Architecture Deployment Supplementary PDS Configuration Configuring PDS to Route Documents via TN (optional) web. Methods server log Examples of PDS Validation errors FAQs CACI Information Solutions and Services | October 2014 | CACI Proprietary Information

Introduction to PDS § What is the Procurement Data Standard (PDS)? • • • § A Do. D-wide system-independent procurement data standard. Carries all contract data in a single format for distribution from contract writing systems. Captures FAR and DFARS rules for contract type, line item structure, etc. Validation capability at GEX / DLA Transaction Services enforces rules before sending to EDA converts awards in PDS XML format into physical contract representation. What does PDS mean to the SPS User? • • • Need for greater attention to quality of data in contracts. Ability, in EDA, to see conformed copy. Ability to measure, trace, and diagnose contract quality problems. For more information, see the PDS Home Page. − http: //www. acq. osd. mil/dpap/pdi/eb/procurement_data_standard. html 4 | CACI Information Solutions and Services | October 2014 | CACI Proprietary Information

Definitions 5 § PDS Event Subscriptions • The PD² Adapter’s outbound transactions are event based. • As an action is taken within the PD² database, the substance of the action is converted into an event for the PD² Adapter’s consumption. • Event subscriptions allow an SA to configure which events the PD² Adapter should process. § Extraction Parameters • Extraction parameters are a sub-component of event subscriptions. • They allow an SA to specify which XML sections are produced for a specific event subscription. • The flexibility provided by extraction parameters is useful for sites that create complex documents with large numbers of included clauses and multiple large attachments, but do not need that information passed on to integration partners. Many production sites, remove extraction parameters to improve performance by reducing the amount of data sent to integrations. | CACI Information Solutions and Services | October 2014 | CACI Proprietary Information

What’s happening to the SPS Data 6 | CACI Information Solutions and Services | October 2014 | CACI Proprietary Information

SPS/PDS Architecture §SPS DB §PD 2 Adapter §w. Ms Message Broker §PDS IC §w. Ms Server Log 7 | CACI Information Solutions and Services | October 2014 | CACI Proprietary Information §PDS XML Files

SPS/PDS Architecture (continued) § 8 | PDS Integration Component (IC) § Contains the PDS package § Applies selection criteria; Issues status message if document is ignored § Maps data from SPS XML structure to the PDS XML structure § Performs Validation § Validates PDS XML against PDS Business Rules § Validates PDS XML against PDS Schema § All status and validation messages recorded only in web. Methods Server Log § PDS XML is written to file system CACI Information Solutions and Services | October 2014 | CACI Proprietary Information § 8

Deployment 9 | § Installation • A single web. Methods Package (PDS) • Event Subscriptions • SQL script provided to identify common subscriptions that could be used • SQL script provided to update common subscriptions with “id” extraction parameter • SQL script provided to insert new custom PDS subscriptions § Properties • Batch file provided to add PDS specific properties to AMSCommon. Services’ common properties file § Documentation • Installation Guide • Operations Guide CACI Information Solutions and Services | October 2014 | CACI Proprietary Information

Supplementary PDS Configuration. § In prior releases of the PDS Extract Utility, sites experienced issues with the Broker Server's storage files filling up. Due to this issue, a supplementary configuration path is now included with the PDS Extract Utility Release 1 and greater. The goal of the supplementary configuration is to significantly reduce the size of each message published to the message Broker. This is accomplished by not including the complete XML document in the message. The new message will consist only of procurement document metadata. The metadata will be flexible and allow the Integration Component (IC) to determine if the document should be processed by PDS. If it should, the PDS IC will request the already produced PD² Adapter XML document from a data store and continue with the PDS translation. § The Supplemental configuration consists of the following: • • 10 | Installing of the CACISps. Integ. Common package. Deleting All Legacy PDS Specific Events Adding Metadata PDS Specific Events Configuring new Events (TN Sender, TN Receiver, etc. ) CACI Information Solutions and Services | October 2014 | CACI Proprietary Information

Baseline PDS Event Subscription Table 11 | CACI Information Solutions and Services | October 2014 | CACI Proprietary Information

PDS Event Subscription Table with Supplemental PDS Configurations Applied 12 | CACI Information Solutions and Services | October 2014 | CACI Proprietary Information

Verification of Versions 13 | CACI Information Solutions and Services | October 2014 | CACI Proprietary Information

Verification of Versions (continued) 14 | CACI Information Solutions and Services | October 2014 | CACI Proprietary Information

Supplementary PDS Configuration 15 | CACI Information Solutions and Services | October 2014 | CACI Proprietary Information

Supplementary PDS Configuration (continued) 16 | CACI Information Solutions and Services | October 2014 | CACI Proprietary Information

Configuring PDS to Route Documents via TN In releases prior to PDS v 3. 4, all PDS documents were written to the file system. It was then the responsibility of the SA to get the translated documents from the file system to GEX and any additional third parties. As of PDS v 3. 4, it is now possible to automatically route the PDS documents to trading partners. § Creation of a new TN Partner with unique DUNS (ex: PDSXML) § The tn_receiver value in the PDS events must be updated with the new DUNS value (tn_receiver = PDSXML). § AMSCommon. Properties. prop file must be updated with this DUNS value. § Allows faster processing of the final PDS transmission, to lessen lag time between when the contract is signed and when PDS posts to EDA (Note: this can impact the EDA Scorecard results. ) Note: When making this decision, it is first important to contact your DLA Transaction Services or GEX POC to coordinate the change in transmission methods. 17 | CACI Information Solutions and Services | October 2014 | CACI Proprietary Information

Configuring PDS to Route Documents via TN (continued) 18 | CACI Information Solutions and Services | October 2014 | CACI Proprietary Information

Configuring PDS to Route Documents via TN - PDS TN Partner Profile 19 | CACI Information Solutions and Services | October 2014 | CACI Proprietary Information

Configuring PDS to Route Documents via TN – Results in MWS Transactions 20 | CACI Information Solutions and Services | October 2014 | CACI Proprietary Information

web. Methods Server Log § 2014 -02 -28 06: 19: 09 EST [ISP. 0090. 0004 C] ~PDSPROCESSOR -- [INITIALIZATION] Document ignored because caci. pds. trigger. Condition is pds and document type is PD 2_Award • Means that a documents was not processed by the PDS IC. • Could be that the document is not a valid doc type for PDS to process. § 2014 -02 -28 12: 35: 45 EST [ISP. 0090. 0004 C] ~PDSPROCESSOR -- [XXXXXX-14 -G-00090001] Building PDS XML § 2014 -02 -28 12: 35: 53 EST [ISP. 0090. 0004 C] ~PDSPROCESSOR -- [XXXXXX-14 -G-00090001] PDS XML document complete § 2014 -02 -28 12: 35: 53 EST [ISP. 0090. 0004 C] ~PDSPROCESSOR -- [XXXXXX-14 -G-00090001] Validating PDS XML against PDS Schema § 2014 -02 -28 12: 35: 53 EST [ISP. 0090. 0004 C] ~PDSPROCESSOR -- [XXXXXX-14 -G-00090001] PDS XML passed validation 21 | CACI Information Solutions and Services | October 2014 | CACI Proprietary Information

Examples of PDS Validation Errors § PDS_V_F_23: <Unit. Of. Measure> is required when <Quantity> is provided. • § PDS_F_F_18: The value '. 00' is not a valid entry for <Obligated. Amount>. It must be greater than zero. • § | The Extraction Parameters for PDS data elements are “id, wli, lidff”. If other parameters are used, the error may occur. For more information and a detailed list of PDS Validation message please see the below document: • 22 A common mistake when creating Not Separately Priced line items is to use the cost constraint No Charge. However, No Charge is not allowable in this circumstance. PDS_G_F_02: <Clause. Full. Text> was provided as an empty tag. It must be populated or removed. • § Occurs if an obligated amount of zero is left on an NSP line item. PDS_F_W_54: The value 'No Charge' should not be used for <Unit. Price. Basis>. It was disallowed per DFARS PGI 204. 7103(b). • § Occurs when a unit of measure is not placed on a line item. https: //spssite. caci. com/document_display. cfm? id=19887 CACI Information Solutions and Services | October 2014 | CACI Proprietary Information