Procurement Systems Integration Integrating P-RAMS and other Procurement Applications in Operations Portal & Client Connection Marcelo Donolo Procurement Specialist, OPCPR Fiduciary Forum, March 2010
Objectives 1.Procurement applications in Ops Portal 2.Procurement applications in the Regions 3.Issues with system integration 4.Proposed functional approach to Integration 5.The P-RAMS Dashboard 6.Discussion, Q&A
Procurement Applications in Ops Portal
1. Bid Module Bid Creation & processing 2. Procurement Notices Publishing (Ads) 3. AML Check & Form-384 Prior Review 4. Contract Awards Publishing (Awards) 5. Post Review Supplement to PPR Report 6. Complaints Database Case Record/Monitor 7. P-RAMS Risk Management 8. Red Flags Tool F&C Due Diligence
Procurement Applications in Ops Portal 9. Red Flags (in development)
Procurement Applications in Ops Portal 9. Red Flags (in development)
Procurement Applications in the Regions
1. LCR: SEPA Procurement plan/mgt 2. AFR: PROCYS Bid processing/performance mgt 3. MNA: PPR System Post review report 4. EAP: Performance tracking tools 5. ECA: Performance tracking tools 6. SAR: Performance tracking tools Other Reference Systems: CRPD Database, Debarred Firms Web Site, Suspension Lists (TS, ETS), Procurement Reports
Issues with System Integration
1. Anchor Unit (OPCPR) - IT Development under OKSP; Ops Portal/CC - Lead time 8-12 months - Demands come from senior mgt & Regions 2. Regions - Business needs may lack alignment w/ OPCPR IT WP - Regional solutions not scalable to enterprise level - Maintenance costs burdensome 3. End users - Frustrated with yet another system…(which doesn’t necessarily meet TTL’s business needs)
Proposed Functional Approach to Integration
1. Integrate what can be integrated - Bank-wide applications talk to each other - Duplicate data entry minimized
Proposed Functional Approach to Integration 1. Integrate what can be integrated - Bank-wide applications talk to each other - Duplicate data entry minimized 2. Link what can be linked - Allow regional systems to talk to Ops Portal - Regional autonomy retained
Proposed Functional Approach to Integration 1. Integrate what can be integrated - Bank-wide applications talk to each other - Duplicate data entry minimized 2. Link what can be linked - Allow regional systems to talk to Ops Portal - Regional autonomy retained 3. Align future IT development with IL reform & OKSP - Dashboard concept (ORAF) - P-RAMS as a procurement dashboard - Improvement of Client Connection & Ops Portal Function
Proposed Functional Approach to Integration 1.Functional Improvements to Portals Procurement plan Procurement plan Recording performance time (business standards) Recording performance time (business standards) Electronic no-objection function Electronic no-objection function Automated Form-384 Automated Form-384 Integration of reference systems (CRPD, TS, ETS) Integration of reference systems (CRPD, TS, ETS) Connected to e-disbursements Connected to e-disbursements
Proposed Functional Approach to Integration 1.Functional Improvements to Portals Procurement plan Procurement plan Recording performance time (business standards) Recording performance time (business standards) Electronic no-objection function Electronic no-objection function Automated Form-384 Automated Form-384 Integration of reference systems (CRPD, TS, ETS) Integration of reference systems (CRPD, TS, ETS) Connected to e-disbursements Connected to e-disbursements 2.Technical Improvements (ISG) Faster speed Faster speed Improved reliability Improved reliability Documentum (IRIS replacement) Documentum (IRIS replacement)
The P-RAMS Dashboard
1. Main point of entry for procurement data - All procurement data accessible through P-RAMS - Integration and linkages across all modules in Portals 2. Main point of entry for monitoring & reporting - Procurement data extractable from P-RAMS - Substantiates IA capacity/feeds into risk assessment - Centralizes information - Aligns with OKSP
The P-RAMS Dashboard
Regional Systems
The P-RAMS Dashboard
Discussion, Q&A