Federal Procurement Data System – Next Generation (FPDS-NG) Agency Information Day

1. Federal Procurement Data System – Next Generation (FPDS-NG)Agency Information Day July 21, 2003

2. Morning Agenda • Welcome (Pat Brooks/Teresa Sorrenti) • FY03 Completion (Jerry Olson) • FPDS-NG Overview/Status (Pat Brooks) • New Information (John Cochran) • Reports Available in October • Agency Admin Responsibilities • FAR PIID Coverage • Data Dictionary Alterations/Corrections • Change Control Board Procedures • CCR Data Integration (Frequency and Schedule) • Demo Direct Key Entry System (GCE) • Status of Development • Demonstration • Q&A

3. Afternoon Agenda • Welcome Back (Pat Brooks) • Change Management (GCE) • Early Adopters – Up to September 15 • Integration Testing for Agency Systems • Technical Exchange on Actual System Integrations (GCE) • Before and After Look • Technology Characteristics • Integration Method • Duration of Integration • Demonstration • Q&A • Wrap-up and Thanks (Pat Brooks)

4. Agency Admin Responsibilities • Agencies expected to have core administration role In FPDS • No longer an error correction clerk • Can authorize a hierarchy of “sub” administrators

5. Agency Admin Responsibilities(Cont’d) • Authorize Government users/systems • Systems that submit procurement data • People with FPDS login rights • People who request free public-cost reports • Disable users/systems no longer authorized • Ensure users receive instruction • Maintain agency tables • Contracting offices • Funding offices • Agency major programs • Offset officer

6. Agency Admin Responsibilities(Cont’d) • Quality Assurance • Monitor reporting (assure reporting) • Resolve anomalies • Request exceptions to validation rules • Use Monitoring Tools • Weekly error status e-mail • Reporting Status Report • High Dollars Report • Socio-economics Reports

7. Procurement Instrument ID • Anticipated FAR Language Will Require: • Alpha characters in the first positions to indicate the agency, followed by alphanumeric characters identifying bureau, offices, or other administrative subdivisions. • Last portion of the PIID to be numbered sequentially. • May include other elements, as appropriate, such as fiscal year. • When the basic reference contract is available for multi-agency use (GWAC, Federal Supply Schedule contract, etc.), an ordering agency shall use the same delivery orders, task orders, and call numbers as it uses for its contractual instruments. • OFPP Expected To Issue Instructions Immediately After DAR Council Approves The Change

8. FAR PIID Examples (Cont’d)

9. Data Dictionary Alterations/Corrections • Specification unchanged except as noted below: • Two bundling elements combined • Bundled Requirement (Y/N) eliminated • New value added to Bundled Contract Exception • Screen label is Bundled Requirement • Fee for use of service for DO • The requirement to report the fee paid was inappropriately eliminated…it is required. The Use Case Matrix is correct. • EPA clauses for BPA Call • Use Case Matrix is wrong • EPA Designated Products is the required element • Recovered Materials Clause is not required

10. Data DictionaryUpdates • Screen labels will be added to DD • Possible changes (identified but not changed) • Add “STTR” as Competition possibility • Move “SDB Participating Program” from Competition to separate element • Federal data element naming conventions will be incorporated

11. Change Control Board Procedures • An Interagency Board of 8 to 10 Contracting Officers and technical staff • Policy decisions elevated to FAC or a FAC subcommittee • Will accommodate Agency data needs • Invitation for nominations go to FAC

12. CCR Data Integration • CCR provides a data update every morning • FPDS will process the update every morning • Civilian use of CCR may not be mandatory by October 1. • How to handle delay & foreign vendors is under discussion