New Search
Award SummaryPage 21 of 33 <br />for highly granular report refinement <br /> <br />- The seven levels of hierarchy is attached to each transaction for reporting <br /> <br />purposes. <br /> <br />- Enhanced Data Capture Tied to Card <br /> <br />- 5 Vehicle-Specific User Code Fields (can be used to capture vehicle class, GVW, <br /> <br />On/Off Road designation, garage location, etc.) <br /> <br />- 5 Card-Specific User Code Fields (can be used to capture accounting strings, GL <br /> <br />codes, temporarily assigned project codes, etc.) <br /> <br />- 5 Driver-Specific User Code Fields (can be used to capture vehicle class, GVW, <br /> <br />On/Off Road designation, garage location, etc.) <br /> <br />- All the User Code Fields are attached to each transaction for reporting purposes. <br /> <br /> <br />5.5 Advances in Electronic Controls <br /> <br /> <br />Contractor will assist the Participant in establishing appropriate spending controls based <br /> <br />on best practices and program objectives. These controls can be set for daily transaction <br /> <br />limits, monthly transaction limits and monthly dollar limits. Any new features will be <br /> <br />introduced on an iterative basis, enabling new functionality to become available as soon as <br /> <br />possible. <br /> <br /> <br />The Participant can set controls at the individual card or region level based upon the <br /> <br />cardholders' unique spending needs. Participants can customize daily and monthly spending <br /> <br />limits on a card-by-card basis. Contractor will work closely with the State and <br /> <br />Participants to create appropriate driver or vehicle-type spending levels on their Voyager <br /> <br />accounts. <br /> <br /> <br />Contractors comprehensive reporting packages will allow Participant Administrators to <br /> <br />monitor cardholder spending for cardholder compliance as identified by the State or <br /> <br />Participant. <br /> <br /> <br />5.6 Reconciliation Software <br /> <br /> <br />The Contractor transaction management system shall assign two separate date stamps to each <br /> <br />transaction: Transaction Posting Date, and Transaction Date. The Transaction Posting Date <br /> <br />corresponds to the actual date that the transaction was submitted to Contractor for <br /> <br />billing. The Transaction Date corresponds to the actual date the transaction occurred. <br /> <br /> <br />The Contractor's system must account for both Transaction Posting Date and actual <br /> <br />Transaction Date. The Fleet Commander Online system shall also allow users to run queries <br /> <br />by both dates. <br /> <br /> <br />Contractor shall have the ability to tie accounting codes by product code when sending <br /> <br />electronic billings. <br /> <br /> <br />5.7 Point of Sale Information <br /> <br /> <br />Any merchant accepting Contractor's card must provide 100% Level III data. Contractor <br /> <br />shall work closely with the oil companies and independent merchant processors to continue <br /> <br />to enhance the merchants' ability to provide Level III data. Following is a list of all <br /> <br />data elements that can be captured and tied to a single transaction within Contractor's <br /> <br />system: <br /> <br /> <br /> <br />- Account Number <br /> <br />- Date <br /> <br />- Time <br /> <br />- Driver Number <br /> <br />- Driver Name <br /> <br />- Vendor <br /> <br />- Location Name <br /> <br />- Address <br /> <br />- City <br /> <br />- State <br /> <br />- ZIP <br /> <br />- Transaction ID <br /> <br />- Card ID <br /> <br />- Vehicle Number <br /> <br />- Vehicle Description <br /> <br />- License <br /> <br />- VIN <br /> <br />- Odometer <br /> <br />- Product <br /> <br />- Units <br />https://orpin.oregon.gov/open.dll/showDocSummary?sessionID=1921160&disID=985529&docTy...6/10/2008 <br /> <br />