1. BEA 10.0 CCB Architecture Artifact Approval Brief Acquisition
3 December 2012
Department of Defense

2. BLUF
Recommend CCB approve BRD effort for Purchase Request Data Standard (PRDS) and Procurement Data Standard (PDS)
Requirements promoted by CFO and AT&L through the P2P Process Advocates Working Group - consideration given for impact to Financial, Personnel and Readiness, I&E, and Logistics Community
Focus is on data interoperability and transparency to support asset management, vendor and business partner integration to support warfighter readiness and audit readiness
Data Attribute Count:
Total: PDS: PRDS: 468 (see graphic in backup slides)
SFIS: 4 (removed from PDS/PRDS Enterprise Standard)

3. Interdependency Matrix
PDS & PRDS/All Stakeholders
Interdependency/Affected Parties
All DoD Stakeholders / Components must use PDS and PRDS as the Enterprise Standard for exchanging Purchase Request and Procurement Instrument information
Compliance aspect is for information exchange (IE), not how the data is stored in a system or database
Resolution Requirements/Usage Constraints
Requirements generating Systems that would produce an acceptable PR for contracting and Procurement Systems that map to “P2P” Operational Activities and/or Information Exchanges will be assessed for compliance or plan for compliance
Architecture Impact
PDS and PRDS will be mapped to Information Exchanges (IE) in the OV-3.
DIV-2 will be updated and new data attributes (definition/length/type/values) will be mapped to these IEs - data attributes will be made available for compliance in ACART
Level of effort required to incorporate the approved requirement into the BEA for both PRDS/PDS is 200 hours (25 days)
BEA integration and 15 hours for html visualization for the scope of the work
Standard Data Requirement
PDS and PRDS are the Enterprise Standard for exchanging Purchase Request and Procurement Instrument (Awards, orders, and modifications) information
Enables DoD data integration interoperability and common data exchange standards – outcome is transparency, audit readiness, procurement/finance integration

4. CCB Prioritization/Approval Recommendation
Proposed BEA CCB Criteria [Architecture Requirements]
Type of EA artifact is clearly understood
DIV-2 Logical Data Model
OV-3 (Information Exchanges)
ACART
AV-2 Integrated Dictionary
Enterprise Standards
BEA HTML changes for PDS and PRDS visualization
Business Requirement
Business Element
Business Strategy (Acquisition/Logistics)
Business Outcome
Business Mandate
Investment Management Process Support Element
Portfolio Management Support (e.g., binning and bucketing by Operational Activities, Capabilities, E2E, etc.)
EA Structure Element (common vocabularies, documentation methodologies, etc.)

5. CCB Prioritization/Approval Recommendation
Proposed BEA CCB Criteria [Architecture Requirements]
Identify your conformance with the below stated criteria
Impact of proposed change
Cost/impact of proposed change to BEA (i.e., how many systems/processes, architectures across DoD will be effected?) - PDS:
Impacts OV-3 Information Exchanges and DIV-2 Products; ACART for Compliance
Prioritization: CCB, in consultation with Functional Sponsor, assigned proposed priority High
PRDS/PDS moves DoD toward improved visibility, accuracy, and auditability of contract data
Create data integration or “handshakes” for linkage between budget and execution
Standardize and streamline the procure-to-pay business process
Reduce transactional failures and costs (improve electronic commerce/business)
Improve internal controls for financial auditability
Achieve transparency and data integrity to enable end-to-end (E2E) interoperability
Maturity of proposed EA approach
Clear “line of sight” from business requirement to proposed EA artifact(s)
Functional Sponsor has validated proposed EA artifact(s) will assist with achieving intended business requirement/strategy/outcome/mandate
EA artifact resource estimate complete hours (25 days)

6.
Department of Defense

7. P2P High Level Process Flow

9. Relationships Among Selected Standards & Forms