Tuesday, March 5, 2013
DATE: March 5, 2013
TO: All Certified Procurement Officers
SUBJECT: E-Procurement Frequently Asked Questions - Volume III
All State CPOs,
When submitting an RFP/ITB to OMES for processing and posting, all documentation must be submitted to the OMES ISD buyer for procuring. Once the solicitation is completed and the RFP/ITB is to be posted, the agency must make any supplemental documents; e.g. tables, appendices, maps, configurations, plans, reports, etc; available on the agency’s website and then provide a link(s) to those documents to OMES ISD Procurement. It will be the agency’s responsibility to ensure all documents for that RFP/ITB are in compliance with the State of Oklahoma IT Accessibility Standards and publicly viewable.
We appreciate your assistance with this. Approver Email Notification:
If you are suddenly not being notified via email of an approved/dispatched po, look in your junk email to see if the notifications are being sent to your “Junk” box. If so right click and request that the sender always be displayed in your in-box.
Request to Solicit In-House $50K to $100K
Request to Solicit In-House over $100K
OMES ISD Procurement Nondisclosure Form – CP-019SA1
OMES Form 004ISD – Certification for Competitive Bid
OMES Form 076ISD – Responding Bidder Information
OMES Form 109ISD – Statewide Contract Exception Request
ITAG IT Government (Interagency)
ITAO IT Authority Orders
ITEL IT Equipment Leases
ITEX IT Exempt from ISD
ITGS IT GSA
ITPB IT Prof Service Biddable
ITPO IT Purchases
ITPR IT Prof Serv-Title18 Non Bid
ITRL IT Release Against SW Contract
References to the 115 processes for Plan Approval Process in the December 23, 2011 announcement and the Business Justification on the Form 115 in the February 10, 2012 announcement should be replaced with the new ePro process for submission of plan reviews. Agencies should look to the online training guide for updated processes.
References to the Electronic Storage of Documents in PeopleSoft in the July 25, 2012 announcement should also include that proprietary or confidential data should be cleansed or stored outside of PeopleSoft. If they are stored outside of PeopleSoft make a notation in PeopleSoft so it is clear where to locate the files in the event they are needed.
Manual Update Highlights:
If you have any questions please contact the OMES Helpdesk at: email@example.com