How To Create A Financial Aid Independent Verification System At Hsu

Transcription

1 Humboldt State University Request for Quote # Imaging and Document Management Software Solution Addendum #1 The following changes, omissions and/or additions to the Request for Quote Documents shall apply to proposals made for and to the execution of the various parts of the work affected thereby and all other conditions shall remain the same. In case of conflict between Request for Proposal Documents and this Addendum, this Addendum shall govern. Section A.4 Schedule of Events: The deadline for contractor responses to RFQ has been extended to 5:00pm Monday, January 10, The overall timeline has been updated as follows; please note that the dates for invitations and on-campus product demonstrations are estimated. January 10, 2011, 5:00pm PST Deadline for contractor responses to RFQ (Note: The HSU Campus is closed from December 25, 2010 until January 3, 2011) January 24, 2011 (estimated) Invitations issued for product demonstrations February 7 11, 2011 (estimated) On-campus product demonstrations February 21, 2011 (estimated) Contract awarded Questions submitted by various prospective proposers: The University s response to each question is as follows: 1. What level of integration is HSU looking for between PeopleSoft and the desired Imaging system? Is HSU looking to only image enable PeopleSoft to perform search and retrieval within that application? Or does HSU require bi-directional database updating meaning that if a value within either the PeopleSoft database or the Imaging database should occur one or the other is automatically updated? Please describe the level of integration required Our preference is for the solution to provide as much integration as possible, affording us the greatest opportunity for process efficiency. Using the Financial Aid Independent Verification process referenced in the scope as an example, we would look for transactions received in the content management solution to update PeopleSoft and updates made in PeopleSoft to advise the content management system thus allowing the workflow to continue in as automated a process as possible. 2. Is there a backfile conversion component to the project? If so, would HSU consider a quote to convert those files as part of the project or independent to the Imaging system quote? HSU_Imaging RFQ Addendum 1.docxDecember 20, 2010 Page 1

2 A backfile conversion is not part of our initial project scope although expected in followon phases. Interested contractors are welcome to submit quotes, for informational purposes only, independent to the imaging system quote. 3. How many concurrent users are needed for the Financial Aid project? The Financial Aid office is currently staffed with 16 employees and 10+ student assistants, any of which could play a role in the verification process for this project though not necessarily all at the same time. We suggest vendors provide pricing on as many concurrent users as possible within the $150,000 project budget. 4. How many scan locations are needed for Financial Aid? We suggest vendors submit their recommendations on how many scan stations would be suitable to automate the Financial Aid Verification process. It may also be helpful to note upon what increased volume your solution would require or justify adding another scan station. 5. Does Humboldt State plan to host the server or are they planning to have the selected vendor host the server? As noted in the RFQ, we are interested in the details of any Software-as-a-service or hosted solutions (RFQ section C.2.2). Pricing should be presented in both hosted and locally installed environments (RFQ section E.1.1). 6. How many scan stations are needed? We suggest vendors submit their recommendations on how many scan stations would be suitable for the pilot project - automating the Financial Aid Independent Verification. It would also be helpful to note upon what increased volume your solution would require or justify adding another scan station. 7. What is the proposed annual scanning volume? Estimated annual volume for the Financial Aid Independent Verification pilot project is 12 15,000 pages. Please note that we hope to apply the experience gained from this pilot project to other projects on campus, including the Financial Aid Dependent Verification process with estimated annual volumes of 30-35,000 and Non-Verification document volumes of 22-27,000 annually. 8. How many users need access to the imaging and document management system? Vendors should provide details on the number and type of licensing that is possible within the $150,000 project budget. Campus-wide HSU has 726 staff and management and 577 faculty, not including student assistants. While we do not expect all of those users to require access simultaneously, given our long-term plans to deploy this solution campus-wide, the potential exists for that volume of access. We suggest vendors also include costs for additional blocks of licenses (see section E.1, Pricing HSU_Imaging RFQ Addendum 1.docxDecember 20, 2010 Page 2

3 Options, #8). Vendor recommendations, based on their experience as to the appropriate percentage of users that will require access on an ongoing basis, would also be useful. 9. The budget for this project is $150,000 yet the scope calls for an ECM Solution with Electronic Forms, Workflow, Integration with PeopleSoft and Records Management. How much flexibility is there in the initial project (Pilot) with this limited budget? Please refer to RFQ section A.2 Scope which notes that Pricing should be structured to illustrate what the contractor can provide within the $150,000 budget limit, as well as any additional costs for future expansion of additional users, departments and modules. The Financial Aid Independent Verification process has been identified as the pilot project for several reasons, including providing an opportunity to compare all vendor responses against the same pilot project. 10. How many concurrent users should the vendors price for the initial implementation? The Financial Aid office is currently staffed with 16 employees and 10+ student assistants, any of which could play a role in the verification process for this project though not necessarily all at the same time. We suggest vendors provide pricing on as many concurrent users as possible within the $150,000 project budget. 11. How is University planning on incorporating electronic signatures? While no specific current plans have been made for use of electronic signatures, HSU does have interest in implementing non-wet signatures within State and Federal guidelines. 12. Does the University own or prefer a particular reporting tool to create customized reports? HSU is in the process of deploying the Oracle Business Intelligence (OBI) reporting tool for reporting data from PeopleSoft, and we expect to allow reporting by that tool to other data sources in the future. There are certainly advantages to incorporating workflow, security and user activity data from the content management solution into a single reporting tool although though this is not an absolute requirement so long as reporting information (see section C.4.1 Highly Desirable Requirement #43) is available from within the content management solution itself. 13. What document types are the University planning on incorporating zonal OCR technology for index extraction? No specific document types have yet been identified. HSU is interested in a solution that will provide the best opportunity for automating the capture and storage of any document type. If there are limitations to the types of documents suitable for the OCR functionality being proposed, vendors should indicate such in their response. HSU_Imaging RFQ Addendum 1.docxDecember 20, 2010 Page 3

4 14. In regards to EDI, what index data does the University wish to extract? Where is the EDI being captured from? No specific EDI index data has yet been identified. HSU is interested in a solution that will provide the best opportunity for automated the capture and storage of any electronic documents or data. If there are limitations to the types of electronic documents or data suitable for the EDI functionality being proposed, vendors should indicate such in their response. 15. In regards to COLD-ERM, what type of report stream or print output is the University planning on capturing? Please refer to the RFQ Preferred Requirements section, # Would a vendor be considered even if they do not meet the specified DVBE requirements of 3%? Yes. Please see A.7 Evaluation Criteria, Cost section bullet point Would it be possible to get a list of previously used and/or preferred DVBE contractors for this type of commodity? HSU does not have a compiled list of previously used and/or preferred DVBE contractors for this type of commodity. Small Business and DVBE contractors may be found by searching online at What Oracle solutions is presently being utilizing at the University? As part of the California State University (CSU) system, HSU uses the Chancellor s Office supported Common Management System (CMS) baseline versions of PeopleSoft HCM for Human Resource and Campus Solution (student) records as well as the Common Financial System (CFS) version of Finance 9.0. We are currently on HCM version 8.9, on schedule to upgrade to HCM 9.0 in December HSU also has an Oracle based Data Warehouse using the Oracle Warehouse Builder 11 product to extract data from PeopleSoft HCM and Finance. We are currently transitioning the reporting front end for that Warehouse from Hyperion to OBI. 19. Some of the integration requirements may require customization of PeopleSoft screens. Does the University own PeopleTools and potential staff to perform the needed programmatic changes (on the PeopleSoft side) if required HSU has the access and staff experience in using PeopleTools. However, as noted in section C.3.2 Rapid and Flexible Integration, preference will be given to a solution that can be integrated without modifications. 20. The RFQ states a budget not to exceed $150,000 requesting vendors provide to HSU what they can provide within the budget amount. Would travel and living expenses associated with the project by the vendor be included within that $150,000 figure or budgeted separately? We bill only actual T&L expenses but would like to know if we must account for those likely costs or whether those HSU_Imaging RFQ Addendum 1.docxDecember 20, 2010 Page 4

5 costs will be managed separately by HSU. Of course expenses will be based upon HSU policy. Travel and living expenses must be included in the $150,000 pilot project budget. 21. How many licensed users would you expect to have? Please see response to question # Can you please provide detail on the type of integration required with PeopleSoft Our preference is for the solution to provide as much integration as possible, affording us the greatest opportunity for process efficiency. Using the Financial Aid Independent Verification process referenced in the scope as an example, we would look for transactions received in the content management solution to update PeopleSoft and updates made in PeopleSoft to advise the content management system thus allowing the workflow to continue in as automated a process as possible. 23. How many Document Management System users are anticipated for initial implementation within Financial Aid how many PeopleSoft licenses are these users utilizing? The Financial Aid office is currently staffed with 16 employees and 10+ student assistants, any of which could play a role in the verification process for this project though not necessarily all at the same time. We suggest vendors provide pricing on as many concurrent users as possible within the $150,000 project budget. Access to PeopleSoft is under an enterprise license. 24. Are there any scanners currently in use within the Financial Aid department? If so do you intend to continue using them? How many and what type of scanners are they? Financial Aid is currently using 4 Fujitsu fi-6240 scanners for an internal backfile scanning project. We suggest vendors submit their recommendations on how many scan stations would be suitable to automate the Financial Aid Verification process. It may also be helpful to note upon what increased volume your solution would require or justify adding another scan station. 25. Do you currently use PeopleSoft workflow for any of the steps documented in supplied process charts? No. 26. Please describe which steps within current process are paper based and which are electronic and automated. The current process is entirely paper based. 27. Are there any imaging/document management systems currently in use within the Humboldt enterprise? If so what systems and in what departments? Do you intend to continue using existing systems? HSU_Imaging RFQ Addendum 1.docxDecember 20, 2010 Page 5

6 While a few departments, such as Financial Aid and Financial Services, have internal backfile scanning projects for electronic storage of documents, there are no imaging/document management systems currently in use at HSU. 28. Does the new system need to interact or integrate with any existing imaging systems in anyway? If so please name system and describe interaction desired. No imaging systems exist at HSU today, although some electronic file storage does exist. Please see section C.4.1 Highly Desirable Requirements #10 for object types. 29. Is the proposed solution intended to replace an existing document management system or will it replace a paper based system? Replace a paper based system. 30. Are all Financial Aid staff located in a single physical office or are they dispersed? Financial Aid staff is located in a single physical office. 31. Is an ODBC connection to the imaging database acceptable? Please see section C.4.1 Highly Desirable Requirements # Would you like for vendors to include a feature and functionality matrix indicating functionality available in the various user clients offered (ActiveX, Citrix, etc.)? If available, yes that would be helpful. 33. Do you require communications with server to be SSL encrypted? The option for this is highly desired. Please see Highly Desirable Requirements # Should the chosen solution integrate directly with HSU s PeopleSoft system or via an indirect, screen-scraping tool? Our preference is for the solution to provide as much integration as possible, affording us the greatest opportunity for process efficiency. Using the Financial Aid Independent Verification process referenced in the scope as an example, we would look for transactions received in the content management solution to update PeopleSoft and updates made in PeopleSoft to advise the content management system thus allowing the workflow to continue in as automated a process as possible. 35. Is a nightly refresh of system data from the PS system to the imaging system acceptable? If no, how frequently would you like the imaging system to be refreshed. Given our interest in optimizing the level of integration and if workflows are dependent on data exchanged with PeopleSoft, we would prefer the data refresh be more often than nightly unless we find that to be cost or performance prohibitive. 36. Is real-time integration with PeopleSoft data a requirement? HSU_Imaging RFQ Addendum 1.docxDecember 20, 2010 Page 6

7 Given our interest in optimizing the level of integration and if workflows are dependent on data exchanged with PeopleSoft, we would prefer the data refresh be more often than nightly unless we find that to be cost or performance prohibitive. 37. Is the ECM vendor expected to take responsibility for data synchronization between the PeopleSoft and document management systems? We are unsure how you are defining take responsibility. We expect the solution to support data integration with PeopleSoft and other business applications. As identified in section C.4.1 Highly Desirable Requirements section contractor responses, including those relative to the Integration section beginning at #51, should note if the requirement can only be met with the purchase of additional hardware and/or software beyond the shipping version of the product. As identified in section C.3.4 Independence from Contractor, we are interested in a system that allows us to choose the entity performing the specific integration functions whether the contractor, their recommended provider or an unrelated contractor. 38. Will HSU staff perform any local installation of required ECM software and components on end-user machines? Yes, if local installations are required. HSU will expect the contractor to provide installation instructions. 39. If local software installation is the vendor's responsibility, should the respondent include professional service costs required to install ECM components on user machines? Can you estimate the number and location of end-user machines that will require access to the ECM system? Please see response to # Do all ECM system users need full-text search capability? If only certain users can you estimate the number of users that will need full-text search capability? Should appropriate licensing cost for full-text search be included in vendor s response? We do not expect that all users will require full-text search capability but the estimated number of users is unknown. Responses must include the type of license being proposed and the price for each type, including licensing costs for full-text search licenses. 41. Do all users require access to workflow functionality? If only certain users can you estimate the number of users that will need workflow access? We anticipate a limited number of users would have access to build or modify a workflow process however the number of users needing to participate in a workflow depends on how the workflow licensing is defined. Using our scope Financial Aid Independent Verification pilot project as an example, if scanning a document to satisfy a step in the process requires a workflow license and, assuming actual interaction by a Financial Aid counselor to update activities within the verification workflow that require it to move to the next step, then all Financial Aid staff would require workflow access though not necessarily all at the same time. If scanning does not require a HSU_Imaging RFQ Addendum 1.docxDecember 20, 2010 Page 7

8 workflow license, then we estimate the number of workflow participants to be 50-75% or users. 42. What types of browsers are in use at HSU, and which must the ECM system be compatible with? Must the system run natively on these browser(s) without need for client install? Please see section C.4.1 Highly Desirable Requirements, Client section beginning at #61 for the preferred browser compatibility. Please also see section C.2.2 Solution Specifications, #2 requesting vendors provide a detailed schedule of all desktop requirements including compatible web-browsers and operating systems. HSU would prefer that any solution run natively in modern browsers because our users are on heterogeneous platforms and are increasingly accessing systems from mobile devices that don t support client installs. That said, we reserve the right to evaluate proposals based on a best value analysis of all factors. 43. Should the ECM system offer full product functionality via the web browser? Preferred but not required. 44. How many end users and system administrators will require training by the vendor so that we can price training accurately? As regards end users for the pilot project, the Financial Aid office is currently staffed with 16 employees and 10+ student assistants, any of which could play a role in the verification process for this project though not necessarily all at the same time. The initial number of system administrators is estimated to be Should the ECM system run natively on portable devices such as the ipad? Preferred but not required. 46. Is there a need for document version control functionality within the document management product? If so should the vendor include this software functionality in the quoted software configuration? Yes. 47. How many people would be accessing the system? Please see response to question # We offer a 1, 2 and 3 year contract; do you have a preference for the term? No. 49. Has Humboldt State University had any prior communication with any of the vendors responding to this RFQ? HSU does not yet know who the responding vendors will be. This RFQ is a fully open and competitive request. Any official communication between HSU and potential responding vendors has been in writing and any clarifications are being addressed in this Amendment #1, which will be available to all potential responding vendors. HSU_Imaging RFQ Addendum 1.docxDecember 20, 2010 Page 8

9 50. In regard to sec. A7, how is the point system weighted (i.e., does ease of use receive more points than currently part of the delivered product )? We have not assigned specific weights in these areas. Please note at the end of section A.2 Scope: The award will be made on the a best value analysis at the sole discretion of HSU. 51. Does this project have funding? How did HSU derive the price of $150K? Were there any prior quotations submitted? Funding is available for the pilot project and was based in part on past research but not on prior quotations. 52. For the Workflows presenting in Appendix A, would you please provide associated volumes for some representative period of time. (Just ballpark estimates would be very helpful.) Estimated annual volume for the Financial Aid Independent Verification pilot project is 12 15,000 pages. Please note that we hope to apply the experience gained from this pilot project to other projects on campus, including the Financial Aid Dependent Verification process with estimated annual volumes of 30-35,000 and Non-Verification document volumes of 22-27,000 annually. 53. What is the current system used by Humboldt State University and/or the Financial Aid Department? As of February 2011, HSU will be using Google Mail (Gmail) campus-wide - staff, faculty and students. A number of these users will use Microsoft Outlook as their primary client via Gmail connector. 54. Would all staff participating in the Financial Aid Independent Verification workflows by located on the same campus or would some be remote users? If access to the Document Management repository and workflow process were through web access, would there be bandwidth issues? Financial Aid staff is located in a single physical office. 55. For the ISIR Import Process flow shown as the first workflow in Appendix A, does the verification process that is performed for 1/3 of the students involve access to the paper versions (or their XML representations) of their Free Application for Federal Student Aid (FAFSA) documents? What exactly is occurring during the verification process that would require access / search of the Imaging and Document Management system? This process was included as a piece of the entire Independent Verification process and does not necessarily require access/search of the Imaging and Document Management system as that is handled within the PeopleSoft automation. The FAFSA record is entirely electronic and stored within PeopleSoft; verification currently requires matching and looking at physical worksheets (the 8I) and tax returns as well as the electronic FAFSA record in PeopleSoft. HSU_Imaging RFQ Addendum 1.docxDecember 20, 2010 Page 9

10 56. For the PS Packaging workflow (the 2nd workflow in Appendix A), how are the Counselor and Prepackaging Reports currently made available for review? Exported into Microsoft Excel where data is sorted, etc. then distributed and worked. 57. In the checklist(s) update and validation process (in the 3rd workflow in Appendix A), what unstructured records (e.g., original FAFSA documents or tax records) actually follow the flow (if any)? If unstructured documents are stored, how are they currently managed and are they stored in paper format or in digital form? How are they currently organized and searched? (forwarded to FinAid) We are unsure how you defining unstructured records. All documents follow the workflow and are tracked using checklists and checklist items. All documents are currently stored in physical, paper files currently organized alphabetically by last name first, with color coded labels to designate the most recent active aid year. The tracking record of the document is first searched by looking up the student record in PeopleSoft, and then the physical file is pulled if necessary. 58. (Again, referencing the 3rd workflow) Are the checklist entries captured in digital form or are paper checklists filled out? If the latter, are the checklists filed in the students paper file? Checklists in this workflow are PeopleSoft electronic checklists. 59. What document types typically make up the student s paper folder? How many active files are in the file room? How many total files? What is the retention set (rules and time periods) applied to these student records? The pilot project does not include backfile scanning but rather automation and image of this process going forward. 60. In the financial aid verification process (5th workflow in Appendix A), is Form 81 printed and filled out manually, or is it filled out online? Same question for Form 38E. Is the signature referenced a wet signature? Are the Forms 81 and 38 stored in the student s file in the file room after verification? Both form 8I and 38E is available online but both must be submitted manually and with a wet signature. 61. The Financial Aid Package that is sent to Financial Aid is this a copy of the originals or does the original package get passed around during the review process? These are the original documents. 62. Do you have an estimate of the number of student files that would need to be imaged to support the Financial Aid Independent Verification process? Is the plan to digitize all student files or just to image them on a day-forward, plus referenced files basis? The pilot project does not include backfile scanning but rather automation and image of this process going forward. HSU_Imaging RFQ Addendum 1.docxDecember 20, 2010 Page 10

11 63. How many FA staff are involved in the Financial Aid Independent Verification process(es) that are to be included in the first implementation? How many counselors or others are involved? The Financial Aid office is currently staffed with 16 employees, 11 of which are counselors, and 10+ student assistants, any of which could play a role in the verification process for this project though not necessarily all at the same time. 64. What scanning environment currently exists? Is there a central scanning facility that will be available as part of the proposed solution? Please see response to question #24. While scanning of documents within the Financial Aid process is expected to be housed within the Financial Aid office, as we continue deployment campus-wide, the decision the need for a centralized scanning facility has not yet been determined. 65. What scanning software is currently used and what is its current configuration (in terms of workstations and servers)? Is the current scanning software planned to be used as part of the proposed system, and if so, what is the current volume level associated with the license held (e.g., Kofax Server products)? Pending response from FinAid as to what software, if any, they are using in their backfill scanning. We do not have any Kofax Server products licensed. Scanning within Financial Aid is performed using the Fujitsu software that came with the scanners (see also response to question #24) 66. Does the University have any established standards related to its approach to electronic signature solutions? Does the University have an implemented Suite B or PKI signature solution? While we have interest in deploying digital or electronic signatures where legally possible, HSU does not currently have any established approach to electronic signatures nor have we implemented Suite B or a PKI signature solution. 67. Has Humboldt implemented a Single Sign-on solution and if so what are they using? HSU currently synchronizes user accounts and passwords from a central Identity Management registry to Active Directory, OpenLDAP, and Kerberos, providing a single mechanism for password changes to all systems. HSU also operates a Shibboleth Identity Provider, backed by OpenLDAP, and is a member of the InCommon Federated Identity Management system. 68. In Section A.2 that discusses scope, conversion of existing images necessary for the first project implementation is included. In Section D.1 it states that While not part of the initial project scope, contractor should provide recommendations for conversion of existing system images and mass imaging of existing archive records. Could you please clarify so that there is no question about the scope that is being proposed? HSU_Imaging RFQ Addendum 1.docxDecember 20, 2010 Page 11

12 A backfile conversion is not part of our initial project scope although expected in followon phases. Interested contractors are welcome to submit quotes, for informational purposes only, independent to the imaging system quote. Conversion of existing images as part of the initial scope includes converting existing forms to online forms that can be used by the proposed solution. 69. How many initial instillations? Please refer to section A.2 Scope and Appendix A for details on the initial pilot project, automating the Financial Aid Independent Verification process. 70. What hours available for instillation on daily basis? Staff are scheduled to work 8 hour days although their installation activities will have to be shared with regular work duties. Please see section 8.1 Pricing Options, #6 for where responding contractors are expected to provide estimates of the workdays and type of services that HSU is expected to supply. 71. What are the qualifications of personnel assigned to assist in implementation? Please see section C.2.2 Solution Specifications, #6 where responding contractors are expected to provide information about personnel resource requirements for implementation of the project and #8 for ongoing administration. 72. Will remote training be accepted after initial training of key personnel? Remote training will be considered after the initial training. 73. Overall number of work stations/ servers will require search retrieval software to be installed? As noted in section A.2 Scope, the initial pilot project is for the Financial Aid Independent Verification process. The Financial Aid office is currently staffed with 16 employees, each with their own workstation and 10+ student assistants which share 5-7 workstations. If there are any existing servers requiring installation, we expect that will be driven by the proposed solution. 74. Will vendor be given rights to terminal server remotely? Yes, if required. Remote access will be provided via VPN. 75. Will HSU provide VPN access? Yes, if required. Remote access will be provided via VPN. 76. What form of licensing HSU will prefer Concurrent or C license? We are unclear what a C license is but we would definitely prefer concurrent licenses over named user licensing. 77. Will HSU accept implementation of hardware and software in less than 5 months? Yes, as identified in section A.4 Schedule of Events, the tentative implementation timeline is February June HSU_Imaging RFQ Addendum 1.docxDecember 20, 2010 Page 12

13 78. Is the proposed system to be designed initially for the Financial Aid office and expanded to other departments? The workflows given only seem to apply to Financial Aid. Is the proposed system design (i.e. workflows and document types) only to refer to the Financial Aid Department and the requisite integration with the Finance Department? Please refer to section A.2 Scope. 79. What is the total expected image volume of the proposed imaging system? (i.e. How many images in the system at any given time?) Estimated annual volume for the Financial Aid Independent Verification pilot project is 12 15,000 pages. Please note that we hope to apply the experience gained from this pilot project to other projects on campus, including the Financial Aid Dependent Verification process with estimated annual volumes of 30-35,000 and Non-Verification document volumes of 22-27,000 annually. 80. Is there a preferred image format (i.e. PDF, Tiff, ect.) Please see section C.4.1 Highly Desirable Requirements # Is a Kofax scanning solution (VRS, Kofax Capture, or otherwise) already installed at the University? What is the image volume of the system and how much is currently being used? A Kofax scanning solution is not installed at HSU. 82. Both large batch scanning and ad-hoc scanning are mentioned as desirable in the RPF. How many approximate users for each solution? Please see response to question # Does question # 75 refer to a proposed solution s ability to run natively on a Red Hat Server, share data with a Red Hat Server, or run on a Virtual Machine? Run natively on a RedHat Server. 84. Does question #35 refer to only eforms? In other words, does the system have to automatically recognize paper documents that are passing through the systems as well? Section c.4.1 Highly Desirable Requirement #35 Distinguish between document types (i.e., invoices versus transcripts) and identify variations within types (i.e., Company A invoice versus Company B invoice) applies to paper (current solution) and eforms (as developed). HSU_Imaging RFQ Addendum 1.docxDecember 20, 2010 Page 13

14 85. Will an organization be disqualified if it provides a compiled statement without an unqualified opinion from an accountant? The company I represent is smaller but it has been in the document imaging and content management business for thirty years. The company has great references and an outstanding reputation. No, providing compiled statements without an unqualified opinion from an accountant will not disqualify a response. 86. Does the PeopleSoft integration mentioned in Questions and 56 refer to data integration (via ODBC) or to PeopleSoft s security and access? Both section C.4.1 Highly Desirable Requirement questions (Integration) relate to the ability of the solution to integrate with PeopleSoft and question 56 (Security) relates to leveraging our existing security infrastructure for authentication within the content management solution. System to system ODBC access may be possible to establish, but only after heavy review at both the HSU and CSU levels as it would bypass much of the PeopleSoft security model. 87. In Question #63 of the preferred requirements; please define user-driven library. Section C.4.2 Preferred Requirements #63 user-driven form library refers to the ability of HSU (users) to create a collection of electronic forms. HSU_Imaging RFQ Addendum 1.docxDecember 20, 2010 Page 14