DEFENSE PROCUREMENT AND ACQUISITION POLICY PROCURE-TO-PAY TRAINING SYMPOSIUM. Business Intelligence FPDS and DoD Procurement BI Service (PBIS):

Transcription

1 DEFENSE PROCUREMENT AND ACQUISITION POLICY PROCURE-TO-PAY TRAINING SYMPOSIUM Business Intelligence FPDS and DoD Procurement BI Service (PBIS): PDS Data in PBIS Presented by: Terry L. Ford Electronic Business Acquisition Specialist - DPAP PDI May 30 June 1, 2017 Hyatt Regency Orlando FL 1

2 What Is PDS? The Procurement Data Standard (PDS) is a system-agnostic data standard that is adopting 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. Further, the PDS will improve visibility of contract-related data, enabling senior DoD leadership to make better informed business decisions. And finally, this data standard will support future migration to enterprise and federal systems and processes where appropriate. For more information about PDS you can visit the Wednesday session PDS Schema Q&A 2017 Procure-to-Pay Training Symposium 2

3 Why Add PDS Data to PBIS? FPDS data is only summary level Does not include Line Item details Place of Performance and Product Service Code (PSC) information are only for the preponderance of money on the contract action PDS data provides Line Item level details and much more 2017 Procure-to-Pay Training Symposium 3

4 How Much Detail? 2017 Procure-to-Pay Training Symposium 4

5 PDS Ingestion Principles Store all of PDS, not just a subset Store PDS in schema-independent tables Data model should be optimized for querying 2017 Procure-to-Pay Training Symposium 5

6 PDS Ingestion Development Two step process First store PDS data in schema specific tables Then map from those tables to a data model that will support all versions ELT (Extract, Load, Transform) instead of ETL (Extract, Transform, Load) 2017 Procure-to-Pay Training Symposium 6

7 Completed Efforts Developed ingestion process for PDS versions 2.2.1, 2.3, 2.4, 2.5, and Loaded fourth quarter of FY 2016 PDS data for the purposes of testing Began loading FY 2017 data for use in PBIS 2017 Procure-to-Pay Training Symposium 7

8 Examples of Test Queries Contracts that are still using Standard Industry Classification (SIC) codes despite SIC being retired in 2000 and replaced with NAICS Contracts that have either a Manufacturer's CAGE or Manufacturer's Part Number Contract mods that deleted the Electronic Submission of Payment Requests and Receiving Reports clause ( ) Contracts that added and deleted the same clause without changing any clause information 2017 Procure-to-Pay Training Symposium 8

9 Results of Testing Determined inconsistencies with PDS data usage Deleting and adding of clauses where nothing changed Storing the entire Statement Of Work (SOW) in the field just meant to hold the document name (document itself would be an attachment which is allowed in PDS) 2017 Procure-to-Pay Training Symposium 9

10 Ongoing Efforts Load rest of 2017 data to date and start daily load process Load PDS data prior to 2017 Incorporate EDA Synopsis XML to use when PDS is not available Create a conformed data view that incorporates modification changes 2017 Procure-to-Pay Training Symposium 10

11 What Does This Mean for Me? Will be able to use PDS data to develop new reports Item Unique Identification (IUID) compliance Clause compliance Government Furnished Property (GFP) metrics Future plan to send copy of PDS database tables to the Procurement Integrated Enterprise Environment (PIEE) You can visit the Wednesday session "What is the Data Lake and PIEE? for more information about PIEE 2017 Procure-to-Pay Training Symposium 11

12 DEFENSE PROCUREMENT AND ACQUISITION POLICY PROCURE PAY TRAINING TO SYMPOSIUM May 30 June 1, 2017 Hyatt Regency Orlando FL 12