Laserfiche WebLink
• <br /> • <br /> ATTACHMENT 7 <br /> MEMORANDUM OF AGREEMENT <br /> The U-PASS Agreement sets forth six specific issues that must be resolved prior to the University of Washington <br /> transitioning the U-PASS to the ORCA platform. These issues are identified in Section 11.12 of the U-PASS <br /> Agreement. <br /> In accordance with Section 11.12, the undersigned have executed this Memorandum of Agreement to document <br /> the agreed-upon solutions to five of the six issues, and the conditions associated with each. <br /> Section 11.12 (a), Implementation of RFI-448, E-Purse Block. This system change was implemented in <br /> Maintenance Release 9 (MR 9). The ORCA Cards issued under the U-PASS agreement for University or Cascadia <br /> Community College use, will have the e-purse functionality blocked at time of issuance. The e-purse block is not <br /> reversible at the present time. The Parties agree to explore solutions to the policy barriers preventing <br /> implementation of e-purse at the University and the College. If the Parties come to an agreement to implement e- <br /> purse, functionality to reverse the blocked e-purses shall be investigated. The University has no expectation that <br /> the e-purse block functionality would be available to the College if the College separates from the U-PASS <br /> Agreement and enters an ORCA Business Account Agreement. The University agrees to communicate this <br /> understanding with the College. <br /> Section 11.12 (b), Implementation of RFI-523,XML File Upload. This system change is being implemented in <br /> two phases. Phase 1, XML file upload validation and error notification,was implemented in accordance with RFI <br /> 523.1 in Maintenance Release 14(MR 14). Phase 2, reporting of expiring actionlist items associated with card <br /> group movement is defined in RFI 523.3, and will be implemented in Maintenance Release 15 (MR 15). <br /> Section 11.12 (c),Renewing Expired Actionlist Items and Card Management Process. Renewal of actionlist <br /> items to move cards between groups was implemented in Maintenance Release 11 (MR 11). Final resolution on <br /> the proposed card management process is being defined in RFI 623 and RFI 523. <br /> Section 11.12 (d),Automatic Upload of XML File; and Section 11.12(e), Card Blocking. The University is <br /> hereby granted permission to develop and run macro programs on a twice daily basis to upload XML files to the <br /> ORCA system and perform card blocks, both via the Business Account website, subject to the following conditions <br /> and the information provided in RFI 440: <br /> a. The macro programs will mimic the user interactions on the Business Account website, and as such, will <br /> use the public user interface designed for this purpose. <br /> b. The macro programs shall only be run between the hours of 11:00 p.m. and 5:00 a.m and between noon <br /> to 1:00 pm, or at other times agreed upon by the Parties. <br /> c. The macro programs shall not damage, disrupt or interfere with the proper functioning of the Business <br /> Account website, nor shall they bypass the account login page or contain programs that directly access or <br /> attempt to access the backend of the ORCA system. In the event the macro programs cause a disruption <br /> to the ORCA system which affects system performance or completion of normal system tasks, the UW will <br /> disengage the programs immediately upon notice by the ORCA agencies. <br /> d. The Business Account website may be modified from time to time and the University shall be solely <br /> responsible for making any revisions to its macro programs as needed to interact with the modified website. <br /> The Lead Agency will provide notification of impending modifications to fields, forms, pages, URLs, html, <br /> and processes that the macro will interact with when uploading a XML file or performing a card block, <br /> including but not limited to the business account log in and log out, order summary, create/maintain card <br /> groups, upload card group file(both submission of files and response page of a submitted file), at least <br /> fourteen(14) days prior to changes in the Business Account website being implemented. <br /> e. The agencies will not be held responsible in the event CD is delayed or there is a failure of the macro <br /> programs. <br /> U-PASS Agreement 94 Final, October 2011 <br /> Attachment 7, Memorandum of Agreement Page 43 of 44 <br />