| Original Mission Statement from Campus Records | Clarified Mission Statement for Board Approval |
| Kentucky State University, building on its legacy of achievement as a historically black, liberal arts, and 1890 Land Grant University, affords access to and prepares a diverse population of traditional and non-traditional students to compete in a multifaceted, ever changing global society by providing student-centered learning while integrating teaching, research and service through high-quality undergraduate and select graduate programs. Kentucky State University is committed to keeping relevant in its legacy of service by proactively engaging the community in partnerships on civic projects driven by the objective of positively impacting the quality of life of the citizens of the commonwealth. | Kentucky State University is a public, comprehensive, historically black land-grant university committed to advancing the Commonwealth of Kentucky, enhancing society, and impacting individuals by providing quality teaching with a foundation in liberal studies, scholarly research, and public service to enable productive lives within the diverse global economy. |
| Kentucky State University, building on its legacy of achievement as a historically black, liberal arts, and 1890 Land Grant University, affords access to and prepares a diverse population of traditional and non-traditional students to compete in a multifaceted, ever changing global society by providing student-centered learning while integrating teaching, research and service through high-quality undergraduate and select graduate programs. Kentucky State University is committed to keeping relevant in its legacy of service by proactively engaging the community in partnerships on civic projects driven by the objective of positively impacting the quality of life of the citizens of the commonwealth. | Kentucky State University is a public, comprehensive, historically black land-grant university committed to advancing the Commonwealth of Kentucky, enhancing society, and impacting individuals by providing quality teaching with a foundation in liberal studies, scholarly research, and public service to enable productive lives within the diverse global economy. |
===== PAGE 16 =====
| Kentucky State University, building on its legacy of achievement as a historically black, liberal arts, and 1890 Land Grant University, affords access to and prepares a diverse population of traditional and non-traditional students to compete in a multifaceted, ever changing global society by providing student-centered learning while integrating teaching, research and service through high-quality undergraduate and select graduate programs. Kentucky State University is committed to keeping relevant in its legacy of service by proactively engaging the community in partnerships on civic projects driven by the objective of positively impacting the quality of life of the citizens of the commonwealth. | Kentucky State University is a public, comprehensive, historically black land-grant university committed to advancing the Commonwealth of Kentucky, enhancing society, and impacting individuals by providing quality teaching with a foundation in liberal studies, scholarly research, and public service to enable productive lives within the diverse global economy. |
| Kentucky State University, building on its legacy of achievement as a historically black, liberal arts, and 1890 Land Grant University, affords access to and prepares a diverse population of traditional and non-traditional students to compete in a multifaceted, ever changing global society by providing student-centered learning while integrating teaching, research and service through high-quality undergraduate and select graduate programs. Kentucky State University is committed to keeping relevant in its legacy of service by proactively engaging the community in partnerships on civic projects driven by the objective of positively impacting the quality of life of the citizens of the commonwealth. | Kentucky State University is a public, comprehensive, historically black land-grant university committed to advancing the Commonwealth of Kentucky, enhancing society, and impacting individuals by providing quality teaching with a foundation in liberal studies, scholarly research, and public service to enable productive lives within the diverse global economy. |
===== PAGE 17 =====
| Kentucky State University, building on its legacy of achievement as a historically black, liberal arts, and 1890 Land Grant University, affords access to and prepares a diverse population of traditional and non-traditional students to compete in a multifaceted, ever changing global society by providing student-centered learning while integrating teaching, research and service though high-quality undergraduate and select graduate programs. Kentucky State University is committed to keeping relevant in its legacy of service by proactively engaging the community in partnerships on civic projects driven by the objective of positively impacting the quality of life of the citizens of the commonwealth. | Kentucky State University is a public, comprehensive, historically black land-grant university committed to advancing the Commonwealth of Kentucky, enhancing society, and impacting individuals by providing quality teaching with a foundation in liberal studies, scholarly research, and public service to enable productive lives within the diverse global economy. |
| Kentucky State University, building on its legacy of achievement as a historically black, liberal arts, and 1890 Land Grant University, affords access to and prepares a diverse population of traditional and non-traditional students to compete in a multifaceted, ever changing global society by providing student-centered learning while integrating teaching, research and service though high-quality undergraduate and select graduate programs. Kentucky State University is committed to keeping relevant in its legacy of service by proactively engaging the community in partnerships on civic projects driven by the objective of positively impacting the quality of life of the citizens of the commonwealth. | Kentucky State University is a public, comprehensive, historically black land-grant university committed to advancing the Commonwealth of Kentucky, enhancing society, and impacting individuals by providing quality teaching with a foundation in liberal studies, scholarly research, and public service to enable productive lives within the diverse global economy. |
===== PAGE 18 =====
# KENTUCKY STATE UNIVERSITY Board of Regents
ATTENTION: This is not an order. Read all instructions, terms, and conditions carefully.
| Issue Date: | December 2nd, 2016 | IMPORTANT: PROPOSALS MUST BE RECEIVED BY: |
| Purchasing Officer: | Stephanie Sowders | Friday, January 20th, 2016 |
| Phone: | (859) 622-2246 | |
| Service: | External Auditing Services | |
| 1. | It is the intention of the Request for Proposal (RFP) to enter into competitive negotiation as authorized by KRS 45A.085. |
| 2. | Proposals for competitive negotiation shall not be subject to public inspection until negotiations between the purchasing agency and all Offerors have been concluded and a contract awarded to the responsible Offeror submitting the proposal determined in writing to be the most advantageous to the University. Price and the evaluation factors set forth in the advertisement and solicitations for proposals will be considered. |
| 3. | An award of contract may be made upon the basis of the initial written proposals received without written or oral discussions. |
| 4. | Contracts resulting from this RFP must be governed by and in accordance with the laws of the Commonwealth of Kentucky. |
| 5. | The University reserves the right to request proposal amendments or modifications after the proposal receiving date. |
| 6. | THE TERMS AND CONDITIONS OF THIS REQUEST FOR PROPOSAL INCLUDE ALL GENERAL CONDITIONS, AS SET FORTH BY EASTERN KENTUCKY UNIVERSITY PLUS ANY SPECIAL CONDITIONS ENUMERATED HEREIN. |
| NOTICE |
| 1. | Any agreement or collusion among Offerors or prospective Offerors, which restrains, tends to restrain, or is reasonably calculated to restrain competition by agreement to proposal at a fixed price or to refrain from offering, or otherwise, is prohibited. |
| 2. | Any person who violates any provisions of KRS 45A.325 shall be guilty of a class D felony and shall be punished by a fine of not less than five thousand dollars nor more than ten thousand dollars, or be imprisoned not less than one year nor more than five years, or both such fine and imprisonment. Any firm, corporation, or association who violates any of the provisions of KRS 45A.325 shall, upon conviction, be fined not less than ten thousand dollars or more than twenty thousand dollars. |
| AUTHENTICATION OF RFP AND STATEMENT OF NON-COLLUSION AND NON-CONFLICT OF INTEREST | | | |
| 1. | I hereby swear (or affirm) under the penalty for false swearing as provided by KRS 523.040:\nThat I am the Offeror (if the Offeror is an individual), a partner (if the Offeror is a partnership), or an Officer or employee of the bidding corporation having authority to sign on its behalf (if the Offeror is a corporation);\n2. | That the attached proposal has been arrived at by the Offeror independently and has been submitted without collusion with, and without any agreement, understanding or planned common course of action with, any other Contractor of materials, supplies, equipment or services described in the Request for Proposal, designed to limit independent offering or competition;\n3. | That the contents of the proposal have not been communicated by the Offeror or its employees or agents to any person not an employee or agent of the Offeror or its surety on any bond furnished with the proposal and will not be communicated to any such person prior to the official closing of the RFP:\n4. | That the Offeror is legally entitled to enter into contracts with the Eastern Kentucky University and is not in violation of any prohibited conflict of interest, including those prohibited by the provisions of KRS 45A.330 through KRS 45A.340 and KRS 164.390, and\n5. |
| SWORN STATEMENT OF COMPLIANCE WITH CAMPAIGN FINANCE LAWS | | | |
| In accordance with KRS45A.110(2), the undersigned hereby swears under penalty of perjury that he/she has not knowingly violated any provision of the campaign finance laws of the Commonwealth of Kentucky and that the award of a contract to an Offeror will not violate any provision of the campaign finance laws of the Commonwealth of Kentucky.\nOFFEROR REPORT OF PRIOR VIOLATIONS OF KRS CHAPTERS 136, 139, 141, 337, 338, 341 & 342 | | | |
| The Offeror by signing and submitting a proposal agrees as required by KRS 45A.485 to submit final determinations of any violations of the provisions of KRS Chapters 136, 139, 141, 337, 338, 341 and 342 that have occurred in the previous five (5) years prior to the award of a contract and agrees to remain in continuous compliance with the provisions of the statutes during the duration of any contract that may be established. Final determinations of violations of these statutes must be provided to the University by the successful Offeror prior to the award of a contract.\nCERTIFICATION OF NON-SEGREGATED FACILITIES | | | |
| The Offeror, by submitting a proposal, certifies that he/she is in compliance with the Code of Federal Regulations, 41 CFR 60-1.8 that prohibits the maintaining of segregated facilities.\nSMOKE FREE ZONE POLICY | | | |
| The Offeror, by signing and submitting a Proposal, agrees to comply with the University’s Smoke Free Zone Policy.\nhttp://policies.eku.edu/sites/policies.eku.edu/files/policies/tobacco-free_policy_bor_41414.pdf | | | |
| SUSTAINABILITY POLICY | | | |
| The University is committed to reducing the adverse environmental impact of its purchasing decisions; it is committed to buying goods and services from contractors who share its environmental concern and commitment. The University encourages bidders to include in their responses economical and environmentally friendly products and service options that serve to minimize waste, reduce excess packing, recycle, reduce, reuse, prevent pollution, and/or offer resource efficiency. It’s the University’s goal to maximize environmental responsibility on its campuses.\nCOMPETITIVE NEGOTIATION DETERMINATION | | | |
| In accordance with KRS 45A.085(1) the Purchasing Officer listed above has determined that the use of competitive sealed bidding is not practicable. This Request for Proposals shall indicate the relative importance of price and other evaluation criteria (KRS 45A.085(4)). | | | |
SIGNATURE REQUIRED: This proposal cannot be considered valid unless signed and dated by an authorized agent of the Offeror. Type or print the signatory's name, title, address, phone number and fax number in the spaces provided. Offers signed by an agent are to be accompanied by evidence of his/her authority unless such evidence has been previously furnished to the issuing office.
| EMAIL: adm.purchasing@eku.edu | Eastern Kentucky University\nCommonwealth 14th Floor #1411\n521 Lancaster Avenue\nRichmond, Kentucky 40475 |
| Phone # (859)622-2246\nPlease type or print legibly | VENDOR INFORMATION |
| Name of Firm * (Company or Individual) | Phone Number* | Make Checks Payable To* |
| Address* | Fax Number* | Payment Address* |
| Address | Web Site Address or E-mail | Payment Address |
| Address | Vendor Representative | Name on Invoice* |
| City* State* Zip* | Federal Tax ID Number** | Social Security Number** |
| Willing to accept ACH payments* Yes ☐ No ☐\nBank Name & Routing # ________ | Willing to accept credit card payments*\nYes ☐ No ☐ | Payment Terms* |
| Bank Account # ________ | | |
| * required fields\n**Federal Tax ID Number- This field must be completed if “Name of Firm” is a company name.\nSocial Security Number- This field must be completed if “Name of Firm” is an individual’s name. |
| *REGISTRATION\nAny foreign corporation (outside the State of Kentucky) must obtain a certificate of authority from the Secretary of State as is required by KRS 271B.15-010 & KRS/014A06/010\n• Certificate #: ________ (https://secure.kentucky.gov/sos/ftbr/Welcome.aspx)\n• Claimed exemption: ________ |
| Any “person” (business or individual) making retail sales in the state are to be registered to collect Kentucky sales and use tax. If the foreign individual (or business) is making retail sales they should be registered for Kentucky sales and use tax purposes by completing a Tax Registration Application (form 10A100), available at the link below. If they are under contract to perform services that do not include the sale of tangible personal property or digital property, or do not perform services subject to tax per KRS 139.200 (such as admissions, provision of telecommunication services, sewer services, and so on), then they are not required to register.KRS 139\n• Consumer Use Tax Account number: ________ (http://revenue.ky.gov/)\n• Sales Tax Account Number: ________ |
| CERTIFICATION\nUnder penalties of perjury. I certify that:\n1. The number shown on this form is my correct taxpayer identification number (or I am waiting for a number to be issued to me) and\n2. I am not subject to backup withholding because:(a) I am exempt from backup withholding, or (b) I have not been notified by the Internal Revenue Service (IRS) that I am subject to backup withholding as a result of a failure to report all interest or dividends, or (c) the IRS has notified me that I am no longer subject to backup withholding, and\n3. I am a U.S. person (including a U.S. resident alien).\nCertification instructions. You must cross out item 2 above if you have been notified by the IRS that you are currently subject to backup withholdings because you have failed to report all interest and dividends on your tax return. For real estate transactions, item 2 does not apply. For mortgage interest paid, acquisition or abandonment of secured property, cancellation of debt, contributions to an individual retirement arrangement (IRA), and generally, payments other than interest and dividends, you are not required to sign the certification, but you must provide your correct Taxpayer Identification Number.\nSignature of U.S. Person ________ Date ________ |
| *Business Classification Reference Links: www.ccr.gov/sizestandard.asp, https://eweb1.sba.gov/hubzone/internet/general/whoweare.cfm, and |
| Type of Ownership (Check Appropriate Box(es))*\n☐ (01) Individual/Sole Proprietorship ☐ (05) Non-Resident Alien ☐ (SM) Small Business ☐ (SD) Small Disadvantaged Business\n☐ (02) Partnership ☐ (06) Exempt from backup ☐ (LG) Large Business ☐ (GA) Government Agency\n☐ (03) Corporation-Incorporated in (State) ☐ Other: ________ | Business Classification (Check Appropriate Box(es))*\n☐ (SM) Small Business ☐ (SM) Small Disadvantaged Business\n☐ (LG) Large Business ☐ (LG) Small Disadvantaged Business\n☐ (CT) In County ☐ (CT) Non-Profit (N) (N) Minor Owned (N) (N) Minor Owned (N) (N) Minor Owned (N) (N) Minor Owned (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) (N) | |
Printed Name of Authorizing Official:
Prin*
Authorized Signature: ___
Date: _____
===== PAGE 89 =====
Solicitation #: ___
## REQUIRED AFFIDAVIT FOR BIDDERS, OFFERORS AND CONTRACTORS CLAIMING RESIDENT BIDDER STATUS
## FOR BIDS AND CONTRACTS IN GENERAL:
The bidder or offeror hereby swears and affirms under penalty of perjury that, in accordance with KRS 45A.494(2), the entity bidding is an individual, partnership, association, corporation, or other business entity that, on the date the contract is first advertised or announced as available for bidding:
1. Is authorized to transact business in the Commonwealth;
2. Has for one year prior to and through the date of advertisement
a. Filed Kentucky corporate income taxes;
b. Made payments to the Kentucky unemployment insurance fund established in KRS 341.49; and
c. Maintained a Kentucky workers' compensation policy in effect.
The BIDDING AGENCY reserves the right to request documentation supporting a bidder's claim of resident bidder status. Failure to provide such documentation upon request shall result in disqualification of the bidder or contract termination.
| Campuslabs Data Driven Innovation | Schedule A | Quote valid for 30 days) |
| Kentucky State University
400 E. Main Street
Frankfort, KY 40601 | Contact
Title
Phone
Email | Deneia Thomas. PhD
Asst. VP, Academic Affairs
502-597-5531
deneia.thomas@kysu.edu | Representative
Email
Phone | Andrew Lyle
alyle@campuslabs.com
716-270-0000 Ext. 7670
FTE
1,800
Ver. 15-12-M |
| Description | Price | Start | 2016
07/01/16-06/30/17 | 2017
07/01/17-06/30/18 | 2018
07/01/18-06/30/19 | | |
| Renewal | SACS Accreditation* | 4,155 | 2016 | 3,698 | 4,321 | 4,494 | | |
| New | Assessment Toolset, Course Evaluations with IDEA, Data Analytics Toolset, CollegiateLink | | 2016 | 111,899 | 116,375 | 121,030 | | |
| 1 day on-site training 4,000 | | | 4,000 | | | | |
| Annual Price | 119,597 | 120,696 | 125,524 | | | |
| Implementation | 20,633 | | | | | |
| Multi-Products Discount | (12,800) | (9,310) | (9,682) | | | |
| Net Annual Price | 127,430 | 111,386 | 115,842 | | | |
| Total Contract Price | | | 354,658 | | | |
| *Existing SACS Accreditation subscription renewal anniversary is August 10 each year. In order to shift that to align with the June 1 renewal date of newly added components, the 2016 amount is prorated to cover service from 08/10/16 - 06/30/17, or 89% of one year. |
| Campus Labs: | Accepted by | Date | 7/1/2016 | 6/30/2019 |
| Institution: | Kentucky State University | Date | Effective Date | Expiration Date |
| Accepted by | Date | | A
License Schedule |
Refer to Schedule B Addendum for license and product information
===== PAGE 119 =====
# Product and Licensing Information - Schedule B
Increase coordination in carrying out your academic mission, enhance your understanding of student success, and apply data to take purposeful action toward improvement.
Campus Labs offers a comprehensive academic affairs solution focused on student learning and inclusive of functionality for strategic planning, assessment collection, and outcomes reporting. Your institution can use the Campus Labs platform to more effectively measure learning and development, conduct program reviews, compile achievement reports, highlight faculty credentials, create curriculum maps, and conduct online course evaluations.
## Benefits and Features:
Set strategic directions by documenting goals, identifying action plans, and creating success criteria
Document the General Educational curriculum by cataloging outcomes, connecting course objectives to programs, and establishing appropriate learning measures
Manage resource allocations by apportioning funds for initiatives, assigning resources to strategic decisions, and tracking resource utilization over progress achieved
- Ensure accreditation progress by collecting narratives, uploading evidence, and managing submission workflow
- Collect course and program-level data from course evaluations, course-embedded assessments, and student assignments
Integrate student experience data including metrics from academic services, student perceptions of campus climate, and both student service hours and experiences
- Integrate student experience data including metrics from academic services, student perceptions of campus climate, and both student service hours and experiences
Measure learning outcomes using pre- and post-tests, student reflections, and rubrics
Determine effectiveness through employer and alumni assessments, job placement statistics, and internship or clinical experience data
• Conduct program review in order to determine program strengths, opportunities, quality, and impact
Foster institutional effectiveness by documenting departmental contributions toward the institution mission and tracking progress toward strategic goals and priorities
Create a comprehensive view of student learning inside and outside of the classroom with curricular and co-curricular data
- Create a comprehensive view of student learning inside and outside of the classroom with curricular and co-curricular data
Organize and report on faculty credentials including teaching assignments, research and service activities, qualifications, and professional development experiences
- Generate curriculum maps showing the connection between courses and learning outcomes in order to highlight gaps between the curriculum and course objectives
===== PAGE 120 =====
# Product and Licensing Information - Schedule B
Enhance your efforts to create a student experience that is engaging, supportive, and success-oriented by centralizing, organizing, and increasing student involvement opportunities.
Campus Labs offers a comprehensive student engagement solution that provides institutions with the ability to manage student co-curricular organizations, curriculums, programs, events, and services—all as a part of encouraging growth and development for students as they engage in these co-curricular activities. Your institution can also use the Campus Labs platform in areas across the entire institution in order to achieve a variety of needs related to the academic or co-curricular student experience.
## Benefits and Features:
Integrate with your student information system (SIS) or enterprise resource planning (ERP) system through secure file transfer protocol (SFTP) or application programming interface (API) methods designed to securely facilitate faculty and staff access to student and operational data
Empower students to manage and grow their organizations through online tools that allow them to customize their organization profiles, manage rosters, store files and photos, and integrate with common social media platforms
- Enhance administrative processes with tools for carrying out online organization registration, conducting campus-wide elections, or collecting budgets and allocating student activities fee monies
- Broadcast communications and messages to a wider audience using communication tools for mass e-mailing, text messaging, and posting to news tickers, message boards, and a virtual flyer-board
• Spread awareness of opportunities through organization-specific or campus-wide event calendars
• Track program participation by sending out invitations, monitoring RSVP status, and collecting attendance data using card-swipe or barcode readers—or upload data from external systems or paper sign-in sheets
Approve service hours completed by organization members and track the overall economic impact of student community engagement in your local area
- Automate the tracking of student progress across certification programs, curriculums, orientation task assignments, and other student affairs initiatives such as passport programs, first year experiences, and even campus-wide experience programs
Produce co-curricular transcripts that showcase students' areas of involvement, learning experiences, or overall outstanding achievements
Align involvement opportunities with institutional, divisional, or departmental learning outcomes
Export reports for reference and assessment related to organization membership, student participation, service hour completion, financial transactions, event listings, and more
===== PAGE 121 =====
| Engagement | High Level Tasks | Deliverables |
| Project Planning and Kickoff | Review the scope of service and Client tasks:Review service delivery expectations and outcomes;Assess viability of existing installed components for compatibility with Banner 9;Distribute Service Preparation Document ("SPD") to the Client and set a due date for the Client's team to return the SPD; andSchedule technical validation call. | Populated Client Collaboration Environment ("CCE")consisting of:■ Prerequisite documentation■ Project Task Log■ SPD |
| Technical Validation Call | Confirm information has been provided within the SPD to begin the implementation;Validate remote connectivity; andValidate service readiness by logging into the various servers and solutions as required for service delivery. | Engagement Report |
| Ethos Identity Installation, Baseline Configuration | Ellucian will deliver the following in 1 non-production and 1 production environment, where applicable:Ethos Identity installation with baseline configuration in a clustered (2-node) deployment with one primary user store connection (LDAPv3 compliant).Optional: If a method is not present to provision the Banner UDC Identifier ("UDCID") required for Banner Single Sign-On ("SSO"), a UDCID Attribute Store will be configured against Ethos Identity to retrieve the UDCID's from a materialized Banner database view through an encrypted JDBC connection. | Engagement Report |
===== PAGE 135 =====
| Engagement | High Level Tasks | Deliverables |
| For Clients with an existing installed and functional Identity Provider, refer to “Client Responsibilities – Existing Identity Provider” below.
Ethos Identity in a single node deployment is not recommended but can be accommodated within scope upon request. | |
| Banner 8 SSO with UDCID Assignment | Ellucian will install the following in 1 non-production and 1 production environment, where applicable:
■ Banner Enterprise Identity Services (“BEIS”) Utilities (singlenode);
■ UDCID Trigger (PL/SQL) package installation; and
■ BEIS SSO Manager (single node) and Banner 8 INB/SSB SSO configuration with Ethos Identity or identity provider meeting criteria herein.
Ellucian will install Apache Tomcat (single node) or Oracle WebLogic on up to one (1) application server in production to support the BEIS applications included herein. In non-production the BEIS applications included herein will reside on the Banner 9 Application Apache Tomcat server in the respective environment. | ■ Engagement Report |
| Ellucian Solution Manager Installation and Configuration | ■ Installation
0 ESM including Apache Tomcat;
■ Configuration
0 Configure the ESM environment for 2 non-production environments to be managed by ESM; and
0 Add the installed Apache Tomcat application server configurations to ESM to support the Banner 9 application deployment process.
■ Upgrade Banner using ESM in 2 non-production environments to the minimal required releases to support Banner 9 Administrative Pages | ■ Engagement Report |
| Banner 9 Administrative Pages Deployment | ● Install single node Apache Tomcat or Oracle WebLogic server on up to two (2) non-production servers
● Ellucian will deploy the following applications using ESM (onto) in up to 2 non-production environments:
0 Application Navigator
0 Banner 9 Administrative Pages | ■ Engagement Report |
| Banner 9 SSO:
Application Navigator & Banner 9 Administrative Pages Configuration | Ellucian will configure SSO for the following applications in up to two (2) non-production environments with CAS/SAML2 (Ethos Identity recommended):
■ Application Navigator
■ Banner 9 Administrative Pages | ■ Engagement Report |
| Turnover & Production Readiness | ■ Validate the environments configured herein by executing the Ellucian defined test plan, and document the installation and configuration for turnover engagement;
■ Provide turnover with the Client on the execution and configuration of services herein; and
■ Provide recommended readiness plan to allow for the Client to deploy into a production environment. | ■ Engagement Reports |
## Service Assumptions
Service requires Ellucian access the Client's environment via SecureLink;
■ Ethos Identity requires a Linux or Windows environment;
ESM requires a Linux environment;
The following applications require a Linux environment deployed onto Apache Tomcat as the web server:
===== PAGE 136 =====
O BEIS Utilities
O BEIS SSO Manager
0 Application Navigator
0 Banner 9 Administrative Pages (Deployment)
All prerequisites must be verified during the project planning and kickoff phase prior to implementation;
If Client is a member of a Banner consortium and that consortium will be managing software releases through ESM then the supporting infrastructure to manage the release process in ESM for consortia members must be in place prior to the Banner 9 Essentials Plus engagement, including:
0 The ‘master’ Consortia ESM instance has been installed; and
0 The 'master' Consortia ESM instance has been configured for consortia release management.
## Client Responsibilities
Enterprise Infrastructure:
0 Provision the Virtual Machines ("VM"), including Operating System for:
Ellucian Solution Manager: 1 VM
0 Note that one ESM server can support multiple environments and Banner instances
• Ellucian Ethos Identity: 2 or 4 VM's depending on deployment model
0 2-Node Cluster (recommended): Total of 4 VM's including 2 for non-production and 2 for production plus a load-balancer or proxy in a known working state.
0 Single-Node: Total of 2 VM's including 1 for non-production and 1 for production
BEIS (Utilities & SSO Manager): 1 VM
0 Total of 1 VM including 1 for production
Note that in non-production, the BEIS applications will reside on the same VM as the Banner 9 applications in the respective non-production environment
Banner 9 (Application Navigator & Banner Admin Pages): 2 VM's
0 Total of 2 VM's including one for each non-production environment
0 Ellucian Ethos Identity requires an Oracle or Microsoft SQL Server Database Instance in both non-production and production (cannot co-exist on the Banner Database Server).
O Request and install required SSL certificates from a trusted certificate authority for use in non-production and production environments.
0 Provide network administrative support for the configuring of firewalls, load balancer, and network devices as required.
Ellucian Ethos Identity:
The viability of clustering Ethos Identity (2-node) will be assessed during the planning phase. A load-balancer or proxy must be in place in a demonstrated working state. If determined that clustering will put the project at risk, a single node will be installed.
0 Provision constituent data into the primary user store for authentication. Note that if a non-production user store is not present, a container ("OU") in the production user store must be created for non-production accounts.
0 Provision the Banner UDCID's to the primary user store for authentication retrieval.
For Clients who cannot provision UDCIDs, UDCID Attribute Store Configuration must include:
0 Ellucian Ethos Identity (v2.0+) must be installed in non-production and production
O Banner must allow the ability for encrypted server requests (for JDBC connection with Ethos Identity) within the database server's “$ORACLE_HOME/network/admin/sqlnet.ora” file.
O User accounts exist within the client's primary user store; login ID's used for authentication (i.e., sAMAccountName or uid) must match the Banner gobtpac external user element.
Existing Identity Provider:
0 Ellucian will consider supporting SSO of the Banner applications in scope to an Identity Provider other than Ellucian Ethos Identity if certain requirements are met (below). The viability of this approach will be assessed during the planning phase and if it is determined that if using such approach will put the project at risk, Ellucian Ethos Identity will be installed.
One of the following Identity Providers are installed in a known working state with at least 1 service provider connection in both non-production and production:
• Ellucian Ethos Identity (version 2.0 +)
• Apero (JASIG) CAS (must support CAS v3.x protocol)
Active Directory Federation Services (ADFS)
===== PAGE 137 =====
• Shibboleth (version 2 or 3)
The Identity Provider be externally accessible, using a valid fully qualified domain name.
Client to provision the Banner UDCID's to the primary user store(s) for authentication.
The Client will be responsible for configuring their Identity Provider, including Ethos Identity if not installed as part of the services herein, to establish the required connection with the Banner applications in scope; Ellucian will only be responsible for configuring the Banner applications to support a CAS (v3.x) or SAML 2.0 connection.
Banner SSO:
O Banner UDCID's must exist within the primary user store in both non-production and production for authentication retrieval prior to SSO integration.
0 Provide 2 test user accounts in both non-production and production user stores
• Production Deployment:
0 Configure ESM for production Banner environment
0 Provision Application Navigator and Banner 9 Administrative Pages to the production environment
0 Configure the provisioned Application Navigator and Banner 9 Administrative Pages within production for SSO (CAS/SAML 2.0) integration with the production Ellucian Ethos Identity server (or other supported Identity Provider).
0 Configuration of production INB/SSB with BEISS SSO Manager
WebLogic:
The Banner 9 Essentials Plus services have been designed to rely on Tomcat for the deployment of the Banner components requiring an application server in order to keep the cost and total time of deployment as low as possible. In order to enhance project success, the installation of the required Tomcat servers has been included in the scope of service herein.
For Clients who prefer WebLogic administration, on request at the commencement of the service, Ellucian is able to install for and deploy compatible components, including Application Navigator, Administrative Pages. BEIS SSO Utilities and SSO manager if applicable in a WebLogic environment.
0 Installation of WebLogic includes a basic domain.
Client is responsible for WebLogic licensing.
## Out of Scope
Network, DNS, Load Balancer configuration and or testing;
2-node cluster configuration of BEIS Utilities, BEIS SSO Manager, Application Navigator or Banner 9 Administrative Pages;
- SSO integration, configuration, testing or troubleshooting of any service provider other than Banner 8 INB/SSB, Application Navigator, and Banner 9 Administrative Pages (deployment) listed within scope;
- Creation and/or installation of SSL certificates;
Migration or upgrades of existing Ellucian Ethos Identity instances;
• Branding Ethos Identity with Client's colors, logo, header or footer;
Advanced configurations of WebLogic including but not limited to clustering
2 or Multi Factor Authentication Configuration; and
Additional Ethos Identity Configuration including but not limited to Password Self-Service Reset/Change Functionality and Banner 9 Self-Service Configuration.
■ Deployment or configuration of JasperSoft.
## Banner 9 Adoption – Technical Workshop Scope of Work
## Overview
Ellucian will conduct a technical workshop designed to establish Client's readiness to execute on the prioritized technical requirements for Banner 9.
Ellucian will review the information gathered during the Banner 9 Adoption - Technical Workshop, will use it to plan for the implementation of Banner 9 within the Client's environment. The Client and Ellucian can then use the plan can to build a framework for the deployment of the Banner 9 infrastructure and the identified Banner 9 applications.
===== PAGE 138 =====
| 1. | Definitions. The defined terms in the Agreement will have the same meaning in this SOW unless the context clearly indicates otherwise. In addition to the defined terms in the Agreement, the following defined terms will apply to this SOW: |
| 1.1 | “Agreement” means the Agreement, Work Order or Amendment to which this SOW is attached. |
| 1.2 | “Application(s)” means the application software modules listed in the Application Inventory in Schedule A, that are purchased or licensed by Client (or provided by Ellucian for Client’s benefit) and installed on the Cloud Environment. |
| 1.3 | “Application Configuration Administration” means the setting and adjusting of Application global, system, class, and/or user-specific defined data elements that affect the functionality or display of the Application, and for those which are modifiable only through vendor-delivered Application entry screens, forms, processes or utilities, for the Applications supported under this SOW. |
| 1.4 | “Application Home” means the specific set of software code, or software code tree, used for the process of running a specific Application. |
| 1.5 | “Application Security Administration” means the granting and revoking of global, class, and/or user-specific data entry forms, processes, and reports, through baseline (i.e., general release without modification) and delivered Application screens and utilities, for that which are accessed or run by end users and/or used by the Applications supported under this SOW. |
| 1.6 | “Client System(s)” means the Applications and data, which are installed on or reside on the Cloud Environment. |
| 1.7 | “Cloud Environment” means the computing and networking resources (including servers, storage systems, backups systems, and network access components) provided or used by Ellucian. |
| 1.8 | “Core Component” means the Application(s) which provides the primary functionality which the majority of the user population interfaces with on a regular and ongoing basis. |
| 1.9 | “Database” means the physical data files tied to one or more Database Instances. |
| 1.10 | “Database Instance” means the logical set of resources and node-specific configuration files required to operate a Database. |
| 1.11 | “ERP” means enterprise resource planning. |
| 1.12 | “Full Time Equivalent” or “FTE” are determined based on the U.S. Department of Education Institute of Education Sciences National Center for Education Statistics Integrated Postsecondary Education Data System (“IPEDS”) annual figures for Student Population. |
| 1.13 | “Hosting Services” means the hosting services provided by Ellucian for the Applications, as described in this SOW. |
| 1.14 | “Hosting Services Term” means the term during which Ellucian will provide the Hosting Services, as otherwise provided for in the Agreement. |
===== PAGE 144 =====
1.15 “Production” means the specific Applications (as well as the Database Instances, Databases, and Cloud Environment running the Applications) which are exclusively used as the single authoritative and “live” system the Client interacts with for transactional processing. Production excludes any and all testing, training and/or other non-live Application or environment instances.
1.16 "Schedule A" means the Schedule attached to this SOW as Schedule A and labeled "Service Configuration and Systems Inventory."
1.17 “Schedule B” means the Schedule attached to this SOW as Schedule B and labeled “Service Level Agreement.” The Service Level Agreement is also referred to as the “SLA.”
1.18 "Schedule C" means the Schedule attached to this SOW as Schedule C and labeled "Standard Maintenance Windows."
1.19 "Schedule D" means the Schedule attached to this SOW as Schedule D and labeled "Information Security Addendum."
1.20 “Service Incident” means a disruption to normal service operations.
1.21 “Service Request” means a request by an authorized user for information, advice, access, role change or other inquiry that may facilitate a change to the current state of Client's System or Cloud Environment.
1.22 "Transition" or "Transition Services" means and refers to the process of planning, directing and coordinating the migration of IT knowledge, systems, processes, data and capabilities from the Client and/or other third parties to Ellucian for delivery of the Applications.
1.23 "VPN" means an encrypted, secure virtual private network pathway used for the purpose of remote connectivity.
#### 2. Delivery Environment.
2.1 Ellucian will deliver the Hosting Services from a Cloud Environment satisfying the requirements of the Applications hosted under this SOW, and address material performance degradation attributable to Cloud Environment managed by Ellucian. The Cloud Environment will align with the security controls and attributes set forth in the Information Security Addendum attached hereto as Schedule D.
2.2 Ellucian will be responsible for its own costs related to Ellucian's use of the Cloud Environment.
2.3 Ellucian will be responsible for supplying licenses and functionality, including upgrades and patches, for the following items in the Cloud Environment:
a. Backup
b. Disaster Recovery
c. Internet connectivity
d. Load balancing
e. Monitoring
f. Operating Systems
g. Security Scanning
===== PAGE 145 =====
3. Hosting Services Functional Requirements.
3.1 Ellucian will host all Production and non-Production environments identified in Schedule A and all associated Applications.
3.2 Ellucian will provide Client storage for all Applications and associated Databases.
3.3 Ellucian will provide a secure method for the Client to upload and download files necessary for the primary function of the Applications.
3.4 Ellucian uses a global delivery model in performing the Hosting Services, meaning that Ellucian personnel worldwide may be involved in delivery.
### 4. Information Security
Please refer to the Information Security Addendum attached hereto as Schedule D.
5. Transition Services. Ellucian will establish a team (the “Transition Team”) to be led by a Transition Manager. The Transition Team will plan, direct and coordinate the migration of IT knowledge, systems, processes, data and capabilities from the Client and/or third parties to Ellucian for the delivery of the Applications. The timeframe for any Transition Services will be based on the project scope/requirements and will be finalized and agreed upon by the parties during or promptly following the initial meeting between Ellucian and Client.
The Transition Manager will be Ellucian's primary Cloud point of contact during performance of the Transition Services as described herein. The Transition Manager will be responsible for:
a. Managing Transition deliverables, including the charter, schedule, and Client Care/portal site.
b. Overseeing communications and delivering according to a plan jointly developed and agreed upon by the parties.
c. Confirming all resources involved in the Transition Services have a common understanding of the needs of both businesses as well as the project deliverables.
d. Managing scope and delivery timetables to be consistent and complementary with the objectives of the Transition Services.
e. Monitoring progress and reporting the status of the Transition Services to all stakeholders.
6. Ellucian Communications with Client. During the Hosting Services Term, Ellucian will regularly communicate with Client regarding product adoption, upgrades and other projects pertaining to the Cloud Environment, change management, and problem resolution. In addition, Ellucian will identify a primary point of contact who will act as the point of escalation for any Hosting Services-related activities.
7. Operating System Administration Services. Ellucian will provide Operating System ("OS") Administration for the OS environments in the Cloud Environment. In this regard, Ellucian will be responsible for:
a. Installations and configurations of the OS environments for Application environments.
b. Maintaining access to and control of special user accounts used for OS administration (i.e. "ROOT" or "Administrator").
c. Installation of patches and updates from the applicable vendor(s) for OS environments.
d. Troubleshooting and resolving OS incidents.
===== PAGE 146 =====
8. Database and Application Administration Services. Ellucian will provide Database Administration ("DBA") Services and Application Administration Services for the Databases, Application Homes and Application environments as defined in Schedule A.
### 8.1 Ellucian will:
a. Install, configure, and update Applications as defined in Schedule A, and Database environments for vendor-specific systems.
b. Configure, as defined in Schedule A, baseline Application Home environments for vendor-specific systems.
c. Perform Database system level security administration for the Database environments.
d. Perform Database and Application Home clones, system refreshes or replications, for the Cloud Environment as agreed by the parties up to two (2) requests per month.
e. Exercise exclusive access and control of DBA privileged or super-user level passwords, to include those Application accounts requiring such access, to Databases, Database Instances and Applications.
f. Provide troubleshooting and diagnostic support for the Databases, Database Instances and Database Homes.
g. Provide troubleshooting and diagnostic support for the Applications, Application configurations and Application Homes.
h. Provide reasonable assistance with application maintenance issues requiring Database and Application administration knowledge and experience for designated Applications.
i. Perform tuning and adjusting of Database and Database Instance, and Application parameters and configurations based on the specific vendor's recommendations, input from users, and response time sampling based on Ellucian's standard practices for designated Applications.
j. Communicate with third party vendors or other Ellucian business units to resolve escalated issues as they arise for designated Applications.
### 8.2 Client will:
a. Appoint or provide a user liaison to coordinate and perform the Application Security Administration functions and duties as requested by the Client for the Applications.
b. Appoint or provide user liaison(s) to coordinate and perform the Application Configuration Administration functions and duties as requested by the Client for the Applications.
c. Appoint or provide a single named user liaison to coordinate ERP activities of patches and upgrades for the Applications.
d. Provide for programmers, analysts and user liaisons to research or review custom code, data level problems or data integrity issues for the Applications, and to develop and/or correct Client-developed customizations to Applications.
e. Maintain active software support contracts with Ellucian and third party vendors for all Applications such that the appropriate vendor will provide personnel to develop and/or correct code in the Applications as needed.
f. Provide functional, technical programming and user liaisons to provide troubleshooting of Application issues and to communicate with the applicable software vendor, including opening support contacts with the applicable software vendor.
g. Perform the function of the job and job stream management role, if applicable; and be responsible for creating, maintaining, and troubleshooting Application jobs and job streams submitted either through the Application or in a supported scheduling system.
h. Provide support for all user functions, management and other Applications not defined in this SOW.
i. Communicate any applicable Database or Application software standards and procedures for access to designated systems to participating students, faculty, staff and alumni.
j. Provide all end-user workstation and mobile device desktop and peripherals support for the Applications.
===== PAGE 147 =====
k. Provide support for all user reporting for applications (including those Applications defined in this SOW), including other ancillary third party systems.
9. Backups and Disaster Recovery. Ellucian will back up the Applications. Backups will adhere to Ellucian's internal backup controls. Ellucian will not be responsible for the accuracy of data in the Client's Databases and Applications, but will only be responsible for appropriately backing up the data in the Databases and Applications supported under this SOW.
9.1 Backups. Ellucian will conduct regular backup of all data and configuration files required for availability of Hosting Services. The retention of this data is separated into the following components:
• Database – backups will be retained for three (3) months
Point in Time-backups will be retained for one (1) week
These durations are provided as part of the standard Hosting Services. At the end of these durations, the oldest copies of files will be deleted.
Client may request copies of Database backups for archival purposes. Upon such request, Ellucian will make a copy of the database available to Client for secure download on a monthly basis. Each Database backup made available in this manner will replace the previously available file. It will be the Client's responsibility to retrieve those files in a timely manner.
9.2 Disaster Recovery. Ellucian will maintain a disaster recovery plan for the Production environments within the Hosting Services. If the primary Cloud Environment is damaged in whole or in part preventing Ellucian from securely delivering the Hosting Services, Ellucian will failover the primary Cloud Environment to Ellucian's disaster recovery environment. Ellucian's recovery time objective (RTO) is twenty-four (24) hours, measured from the time the Hosting Services are declared to have become unavailable until such services become available and operational in accordance with applicable service levels, as measured by Ellucian. Ellucian's recovery point objective (RPO) is two (2) hours, measured from the time the first transaction is lost or from the time the Hosting Services became unavailable. Ellucian will test its disaster recovery plan annually and will, upon Client's written request, provide Client with a summary of the most recent results. Note: Any Hosting Services downtime in excess of the aforementioned objectives will contribute towards the calculation of the SLA as defined in Schedule B.
10. Systems Monitoring. Ellucian will monitor the Cloud Environment on a 24x7x365 basis.
10.1 Ellucian will monitor the Application components and the Cloud Environment for availability.
10.2 Client will allow Ellucian-based remote services monitoring and security tools reasonable access to the Applications.
11. Standard External Interfaces for Integrations. Installation and operation of supported Applications may require installation of third-party applications, which may require connectivity to environments external to Ellucian or Client networks. Only the following defined integration paths, integrations and interfaces will be installed and supported under this SOW: (i) those defined baseline integration paths, integrations and interfaces listed in Section 11.2 below (the “Baseline Integrations”); and (ii) any additional integrations and interfaces specifically listed in Schedule A.
11.1 As it relates to any external interfaces/defined third party integration services as described herein, Ellucian will:
a. Open appropriate access to the Cloud Environment based on the requirements provided by Client. Access is provided via:
===== PAGE 148 =====
i. Public Internet Access – Used for Applications such as Portal and Self-Service.
ii. Site-to-Site VPN – A pair of VPN routers is configured, shipped, monitored, and maintained by Ellucian to provide encrypted access for administrative Application interfaces; as a network path for integrations to on-campus services; or for direct access to Database instances for Client programmers. The Site-to-Site VPN will be configured with industry standard encryption protocols.
b. Support administrative connectivity to the Cloud Environment from defined IP addresses or IP network subnets with the following protocols as appropriate: HTTP (for non-sensitive/non-protected data only); HTTPS; FTPS; SSH.
c. Maintain at least 1Gb/sec bi-directional datacenter connectivity to the Public Internet with diverse providers and physical entrances.
d. Maintain Internet firewalls to protect the Applications from unwanted and inappropriate access. Firewalls shall be configured with a default deny rule for inbound traffic.
11.2 Baseline Integrations – The following are included as part of the Hosting Services:
| Schedule A to Exhibit 1 |
| Service Configuration and System Inventory |
|
| Client Name: | Kentucky State University |
| Total FTE (IPEDS/ Intl Equiv.): | 1,627 |
| Application Inventory |
| Core ERP Application: | Production Instance | Non-Production Instance |
| Description | Count | Count |
| Banner BASE (Core ERP, Database, JobSub, INB, SSB, XE) | 1 | 1 |
| Additional Non-Production Instances | -- | 3 |
| Product Components: | Production Instance | Non-Production Instance |
| Description | Count | Count |
| Ellucian Mobile | 1 | 1 |
| Ellucian Ethos Identity (EIS) | 1 | 1 |
| Banner Event Publisher (BEP) | 1 | 1 |
| Banner Enterprise Identity Service (BEIS) | 1 | 1 |
| Ellucian Solution Manager (ESM) | 1 | 1 |
| Ellucian Ethos Integration | 1 | 1 |
| Business Intelligence (ODS/EDW) | 1 | 1 |
| Banner Enterprise Job Scheduler by Automatic (UC4) | 1 | 1 |
| Banner ePrint | 1 | 1 |
| Banner Integration for eLearning | 1 | 1 |
| Ellucian DegreeWorks | 1 | 1 |
| Ellucian DegreeWorks Transfer Equivalency | 1 | 1 |
| Evisions Argos | 1 | 1 |
| Evisions FormFusion | 1 | 1 |
| Evisions IntelleCheck | 1 | 1 |
| Baseline Integrations |
| Function | Path | Protocol |
| Upload or Download of data | Internet, Site to Site | Secure File |
| VPN | Transfer |
| System Printing from ERP | Site to Site VPN | UNIX Print |
| Directory Authentication* | Site to Site VPN | Secure LDAP |
| Internet, Site to Site | HTTP/Secure |
| Integrations through Ellucian standard web services APIs | VPN | HTTP |
| *Authentication is based on the Client's directory. |
===== PAGE 154 =====
| Validation of 3rd Party Licenses |
| Quantity | Description | Provided by |
| 10 | Oracle Database Enterprise Edition | Kentucky State University |
| 9 | Oracle iAS (Web Logic) | Kentucky State University |
| 2 | Oracle Internet Developer Suite (iDS) (perpetual license) | Kentucky State University |
| 2 | Oracle Programmer (perpetual license) | Kentucky State University |
| 2 | Fujitsu NetCOBOL Compiler License for Linux (1 Prod, 1 Non-Prod) | Kentucky State University |
| 1 | Secure Socket Layer (SSL) / Transport Layer Security (TLS) Certificate | Kentucky State University |
===== PAGE 155 =====
# Schedule B to Exhibit 1
## Service Level Agreement
### 1. Coverage and Terminology
This Service Level Agreement (the “SLA”) applies to the Production Applications supported under the SOW.
Availability: “Availability” means the percentage of a particular month (based on 24-hour days for the number of days in the subject month) that the Production Applications are available for remote access by Client as measured by Ellucian pursuant to the Service Level Objectives defined in the Service Level Objective section below.
Measurement: Availability is measured as the ratio of actual Availability to expected Availability resulting in an “Achieved Availability” percentage. Achieved Availability is determined by calculating the aggregate minutes, during the periods the Production Applications are scheduled to be available (“Scheduled Uptime”), that the Production Applications are unavailable for use by Client (“Unscheduled Outage”), divided by the total aggregate minutes of scheduled Availability for the month which is Scheduled Uptime minus the time the Production Applications are scheduled to be unavailable with Client agreement (“Scheduled Downtime”), and rounded to the nearest 10th (tenth) unless otherwise indicated in the specific SLA definition. The “Achieved Availability” calculation is expressed as:
## 1 – (Unscheduled Outage / (Scheduled Uptime - Scheduled Downtime))
For the avoidance of doubt, the unavailability of the Production Applications as a result of scheduled maintenance and emergency maintenance windows will not be considered a service outage and will not give rise to Service Level Credits.
#### 2. Service Level Objective.
Ellucian aims to achieve one hundred percent (100%) Availability for the Production Applications supported by the SOW. Subject to the terms in this SLA, Ellucian will provide ninety-nine and one half percent (99.5%) Availability for the Production Applications supported by the SOW.
A monthly Availability report will be made available within ten (10) business days following Client's written request.
#### 3. Service Level Credits.
Except under the conditions mentioned in the Conditions section below, if the Availability of the Production Applications is less than ninety-nine and one-half percent (99.5%), Ellucian will issue a credit (a "Service Level Credit") to Client according to the following tables.
| Engagement | High Level Tasks | Deliverables |
| Initiation | • Project initiation | • Project Planning session |
| Planning | • Project planning and resource management
• Initial Development of Project Charter or Scope Statement
• Project internal repository for project artifacts
• Ellucian internal project initiation meeting
• Client project planning session
• Introduction of delivery management team | • Project Charter or Scope Statement
• Project schedule with Ellucian resources
• Project Repository |
| Execution | • Quality assurance activities
• Issue tracking
• Changes to scope
• Schedule resources, and costs, project risk response plans
• Project financials (budgets, project reconciliation)
• Knowledge resources
• Delivery of solution artifacts | • Updated project documentation and solution delivery artifacts
• Status reports
• Change requests |
| Transition and Close | • Transition planning, delivery to contract and project scope with client acceptance
• Project closure | • Transition plan
• Client letter of acceptance |
## Client Responsibilities
- Client will provide information to Ellucian project team that will contribute to project activities and development of artifacts.
Client will provide approval on all project activities, artifacts, and outcomes based on the agreed sign-off criteria and Client acceptance period for approval.
- Client will attend and participate in project status meetings as defined by the Ellucian project manager and Client project leader.
Client will support and otherwise cooperate with Ellucian throughout all project activities, development of artifacts, and project outcomes.
Client will provide a full-time project leader or functional leader who will manage the project and work directly with the Ellucian project manager and provide the required input and work product to support project activities, artifacts, and outcomes.
• Client will assign Client resources to complete Client tasks required as part of the project's schedule.
• Client will provide timely approval of project change requests prior to the start of the project change.
===== PAGE 167 =====
## Service Description
| Engagement | High Level Tasks | Deliverables |
| Planning and Turnover | Technical kickoff, service preparation call, service readiness validation, and training for Ethos Integration and Ellucian ERP Middleware component installation. | • Planning Call
• Engagement Agenda
• Service Preparation Document
• Training Materials
• Engagement Report |
| Ethos Integration – Functional Integration | Configure the Ellucian ERP in preparation for the Ethos Integration implementation. Configure Ellucian Ethos Data Model mappings. | • Decision Workbook
• Configured Mappings |
| Ethos Integration – Technical Integration | Ellucian will:
• Deploy or upgrade the Ellucian Messaging Adapter to the latest supported version; and
• Configure the Ellucian ERP for the integration required for the Ethos Integration implementation. Ellucian will configure the Client Ethos Integration Tenant to the authoritative source (Ellucian ERP). | |
| Ethos Integration – Technical Validation | Ethos Integration message flow validation from Ethos Integration to the Ellucian ERP and validation from the Ellucian ERP to Ethos Integration. | • Validate 1 non-production environment
• Installation Report |
## Client Responsibilities
Provide a designated non-production environment representative of the intended production environment for deployment of the integration that is available for Ellucian to have access and required privileges for the duration of the engagement;
Provide the appropriate resource(s) to assist with deployment of integration components and execute the test plan in the same designated non-production environment, and provide timely system support as needed to maintain operation and availability of the designated non-production environment;
Develop and deliver test plan; and
Provide test data entered to the designated non-production environment per the test plan.
## Ellucian Ethos Integration Requirements
Banner Student API
Banner Integration API
Banner Common Database Upgrade
Banner Ethos API DB Upgrade
SSL configuration with a certificate from a well-known certificate authority for the Banner Student API
• Ellucian Messaging Service
Banner Events Publisher
## Banner Events Publisher Requirements
Tomcat 7.x with Java 7/Tomcat 8.x with Java 8 or WebLogic base domain with Oracle Database 11g (Java 7 or 12c with Java 7 or 8)
If you have Ellucian CRM Recruit, or planning to purchase Ellucian CRM Recruit note that BRIM requires WebLogic and is not supported on Tomcat as Tomcat does not support JMS
## Ellucian Messaging Service Requirements
BEP must be 100% functioning and tested in the production and the non-production environment
Banner Events Publisher
===== PAGE 168 =====
## Ethos Identity Tactical Planning Scope of Work
| Engagement | High Level Tasks | Deliverables |
| Project Initiation and Workshop Service Preparation | Project initiation meeting, identity tactical workshop planning service preparation, and preparation for onsite tactical planning workshop | |
| Tactical Planning Workshop | The purpose of the Identity Tactical Planning Service is to align the Client’s short-term tactical plan to the long-term vision by performing a tactical architecture and planning session, and to create an identity management implementation roadmap. This session will analyze the current state architecture and also educate the Client about the products, services and architecture surrounding the Banner ERP and Ellucian solutions. Based on the strategy, a future state architecture and a project plan to realize the identity goals will be developed. | • Engagement Agenda |
| Service Deliverable Preparation | Development of the tactical plan material and presentation | • Identity Management Implementation Roadmap |
| Service Deliverable Presentation and Follow Up | Delivery of the tactical plan outlining the Identity and Access Management (IAM) process flows and the IAM architecture. presentation to allow for Q&A. | • Client Presentation |
| Ongoing Follow-Up Support | Ongoing support and follow-up for topics regarding the Identity Tactical Planning sessions and deliverables. All ongoing follow-up sessions must be scheduled and allocated to an available Ellucian resource. | • Agenda and Engagement Report as applicable |
## Service Assumptions
- Deliver planning consultation
Document and deliver report templates including IAM Project Definition Document and IAM Project Schedule that documents the IAM architecture and plan for Client.
## Client Responsibilities
• Facilitate room logistics and invitation of participants
• Identify and schedule participants for service
- Circulate Ellucian materials in advance of the service.
Work with Ellucian to determine service expectations and timeline.
===== PAGE 169 =====
| Engagement | High Level Tasks | Deliverables |
| Software Installation | Ellucian will install the Degree Works application. | • Engagement Report |
| Introduction and Scribe Readiness Call | The purpose of the Degree Works introduction and Scribe Readiness Call is to give the project team an overview of the Degree Works implementation. Topics and documents reviewed will consist of:
• Degree Works implementation overview;
• Degree Works team roles and responsibilities;
• Catalog authentication (if needed);
• Which catalog year requirements to scribe; and
• Scribe kickoff worksheet. | • Degree Works Implementation Overview
• Degree Works Team Roles and Responsibilities
• Scribe Kickoff Worksheet |
| Decision Planning Visit | The purpose of the onsite engagement is threefold. The first day's emphasis is client focused. The Client's unique circumstances, goals, and concerns will be discussed in detail. On the second day, the emphasis is on introducing the Degree Works system and exploring its basic functionality. This understanding will serve as the basis for important configuration and implementation decisions that follow. The focus of the third day is on the implementation plan. Each component of the Degree Works implementation is discussed in detail with a particular emphasis on the Client's specific requirements and constraints.
Engagement objectives:
• Meet the Degree Works Core Team members and Ellucian;
• Understand the Degree Works features including web functionality;
• Identify the basic terminology of the Degree Works system;
• Describe the Degree Works process flow;
• Identify recommended practices in a Degree Works implementation;
• Identify the specific implementation approach for the Client; and
• Identify document implementation requirements and unique configuration/service considerations for the Client. | • Meeting Agenda |
| Scribe Services | The purpose of the Degree Works Scribe Service is to complete the initial coding of degree requirements for the Client's degree programs. The blocks of code are delivered into the Degree Works test database. If the scope of the engagement includes additional scribe services for past or future catalogs, this initial code, once verified by the Client, becomes the base for the building of additional scribing.
Ellucian will interact with participants who have been identified during the Degree Works Introduction and Scribe | • Engagement Report |
===== PAGE 171 =====
| Engagement | High Level Tasks | Deliverables |
| Readiness Call via email, conference calls, and WebEx sessions as needed to clarify degree requirements. All non-written interaction will be followed up with documentation for clear and efficient communication of discussion and decisions.
Engagement Objectives:
• Complete a comprehensive analysis of authenticated degree requirements
• Scribe requirements to test database
Breakdown of Scribe counts for the 2016-2017 Undergraduate catalog:
• Degrees: 7
• Majors: 48
• Minors: 40
• Certificate/Endorsement Programs: 4
• Options: 10
• Concentration: 13
• Tracks: 12
• General Education Blocks: 5
Breakdown of Scribe counts for the 2016-2017 Graduate catalog:
• Degrees: 5
• Majors: 8
• Options: 10
• Concentration: 2
• Specialization: 10 | |
 Technical Training | The purpose of the Degree Works technical training is to introduce and examine the Degree Works system and its technical components. This examination will consist of a demonstration of the Degree Works system. This training will also include a discussion of the setup, configuration, data extraction, and management of the Degree Works system. Finally, the examination will include a discussion of recommended practices, project management, and tools for the Degree Works implementation.
Engagement objectives:
• Meet the Degree Works Project Team members and the Ellucian consultants;
• Understand the Degree Works features consisting of web functionality and the PC tools;
• Identify the basic terminology of the Degree Works system;
• Define the Degree Works implementation project management procedures;
• Describe the system architecture;
• Describe the Degree Works process flow;
• Define the extract process and describe how this process relates to the SIS configuration;
• Understand the configuration settings in the UCX tables; | • Training Agenda
• Training Materials (PDF format) |
===== PAGE 172 =====
| Engagement | High Level Tasks | Deliverables |
| • Set up staff ID files and extract staff data from the SIS into Degree Works;
• Extract sample student data from the SIS into Degree Works;
• Attempt a trial run of the student extract from SIS to Degree Works;
• Describe and discuss nightly SQL extract scripts;
• Identify web design requirements of Degree Works web pages;
• Define and set up Degree Works authentication paths;
• Describe how access to services is handled in Degree Works;
• Describe system management requirements including the setup of nightly cron job requirements and the description of log files;
• Describe and explain troubleshooting techniques
• Identify recommended practices in a Degree Works implementation; and
• Identify the Degree Works implementation tools. | • Training Agenda
• Training Materials (PDF format) |
| Functional Training I | The purpose of the Degree Works Functional Training I is to:
• Understand the Degree Works System, Data Structures, Functional Applications and Student Records System, and Data Requirements;
• Focus on administrative tools: Scribe, Sure Code and Transit; emphasizing navigation, functionality, and features;
• Introduce the Degree Works Web Audit worksheets, emphasizing Student View, Student Data Report, and What If audit; and
• Learn to use these products and functionality through full hands on training and prepare for Scribe Block Review and Functional Web Review.
This session is designed to enable the participants to demonstrate, through hands-on exercises, the knowledge and understanding of the Degree Works system functional applications and data requirements. This will consist of using pc applications and the internet. Participants will receive full hands on training during this visit.
The lecture and hands-on workshop(s) will cover the following:
• Demonstrated ability to navigate in Scribe and to scribe basic and semi-complex requirements, and update existing requirement blocks;
• Demonstrated awareness of how to troubleshoot student data issues, using Student Data View, and understand their application to course requirements on the Web;
• Demonstrated ability to use Sure Code to edit, delete or add codes and flags to UCX tables;
• Demonstrated ability to use What If and Student View Audits to look at the display of scribed logic and wording; | • Training Agenda
• Training Materials (PDF format) |
===== PAGE 173 =====
| Engagement | High Level Tasks | Deliverables |
| • Demonstrated ability to run administrative scripts via Transit; and
• Demonstrated ability to use Ellucian Degree Works documentation. | |
| Functional Training II | This session is designed to introduce additional functionality on the Web, begin building the localization roadmap and requirements of the Degree Works system. A strong focus will be placed on an in-depth understanding of SIS data and its relationships to Degree Works and the placement of courses in the Degree Audits.
The purpose of the Degree Works Functional Training II consists of:
• Defining web design changes, exception processing and Other functionality of the Web, Continuation of Web and Scribe Review; and
• Focusing on PC Tool: Transit; emphasizing navigation, functionality, and features.
Engagement objectives:
• Demonstrated ability to troubleshoot student data issues and their application to course requirements on the Web;
• Demonstrated ability to place Exceptions on student record; and
• Demonstrated ability to run extracts, and bulk audits via Transit. | • Training Agenda
• Training Materials (PDF format) |
| Web Design Service | The purpose of this engagement is to provide the Client with site-specific web design changes to alter the look-and-feel of the web application and audit worksheets. We will work with the Client to create a list of requested changes, which will be prioritized and completed by Ellucian. The service also consists of testing of the web changes. | • Engagement Report |
| Functional Training III | This session is designed to enable participants to set up user access permissions, conduct a go-live checklist evaluation, and make sure the staff is ready to proceed to rolling out Degree Works to the campus community. Web design changes and user roles set-up will be finalized, sample end to end scenarios will be tested with different user logons, and the cut-over plan of moving from implementation to an installed client will be reviewed.
Engagement Objectives:
• All users will have appropriate permissions;
• Demonstrated ability to manage the Planner and Templates functionality;
• The “go-live” checklist will indicate the status of all critical components;
• Software cut-over plan will be evaluated; and
• Internal training plan for each user class will be evaluated. | • Training Agenda
• Training Materials (PDF format)
• Go-live checklist |
===== PAGE 174 =====
| Engagement | High Level Tasks | Deliverables |
| Student Educational Planner Training | The purpose of the Degree Works Student Educational Planner session is to:
• Understand the Degree Works Student Educational Planner (SEP) System, Data Structures, Functional Applications and Student Records System, and Data Requirements;
• Focus on Web tools for building Plans and Templates for Program Plans. Consists of working with multiple applications within Degree Management;
• Learn to use these products and functionality through full hands on training; and
• Define new business processes where needed. This will encourage accurate data entry. By having accurate data entry in Plans and Templates, curriculum planning reporting can be used as desired.
The purpose of this training session is to develop competence working with the Student Educational Plan application and its related tables. It is our goal that the Client will roll out the application to selected departments or campus-wide within a reasonable amount of time after the consulting session has completed. | • Training Agenda
• Training Materials (PDF format) |
| Functional Training IV | This session is designed to enable participants to conduct a go-live checklist evaluation, and make sure the staff is ready to proceed to rolling out Degree Works to the campus community. The cut-over plan of moving from implementation to an installed client will be reviewed.
Engagement Objectives:
• All users will have appropriate permissions
• The “go-live” checklist will indicate the status of all critical components
• Software Cut-Over plan will be evaluated
Internal Training plan for each user class will be evaluated | • Training Agenda
• Training Materials (PDF format)
• Go -live Checklist |
| Technical Training | The purpose of this engagement is to provide the Client with a review of key technical topics familiarity with which will be essential to support a successful go-live.
These topics consist of:
• Degree Works architecture
• Tuning
• User access/authorization
• Degree Works environment management
• Reapplying web design changes after an upgrade
• Go-live checklist
• (Possibly CPA reporting)
Engagement objectives:
• Demonstrated understanding of key technical topics;
• Completion of go-live checklist; and
• Client confidence in the ability to manage the Degree Works technical environment in support of and following go-live. | • Training Agenda
• Go-live Checklist |
===== PAGE 175 =====
| Engagement | High Level Tasks | Deliverables |
| Software Installation | Ellucian will install the Degree Works Transfer Equivalency system on Client’s computer system, located at Client’s site. | |
| Introduction and Prep Call | The purpose of the introduction and prep call is to give the potential project team members to an overview of the Degree Works Transfer Equivalency implementation. This will consist of walking through several documents and templates provided by Ellucian to assist in the implementation.
Topics and documents reviewed to consist of:
• Degree Works Transfer Equivalency Implementation Overview; and
• Team roles and responsibilities. | • Degree Works Transfer Equivalency Implementation Overview
• Team Roles and Responsibilities |
| Transfer Equivalency Self Service Configuration | The purpose of the engagement is to introduce and examine the Degree Works Transfer Equivalency system and its components. This examination will consist of a demonstration of the Degree Works system. This training will also contain discussion of the setup, configuration, data extraction, and management of the Degree Works Transfer Equivalency system.
Engagement objectives contain the following:
• Meeting the Project Team members and the Ellucian Degree Works functional consultant;
• Understanding the Degree Works Transfer Equivalency features including web functionality;
• Identifying the basic terminology of the Degree Works Transfer Equivalency system;
• Defining the articulation mapping extract process and describe how this process relates to the Self-Service configuration; | • Training Agenda
• Training Materials (PDF format) |
===== PAGE 177 =====
| Engagement | High Level Tasks | Deliverables |
| • Understanding the configuration settings in the UCX tables; and
• Extracting articulation mapping data from the SIS into Degree Works. | |
| Transfer Equivalency Self Service User Interface Training | This session is designed to introduce participants to the Transfer Equivalency Self-Service web interface, including basic navigation and sign-in options.
Engagement objectives include the following:
• Demonstrated ability to navigate the Transfer Equivalency Self-Service web application. | • Training Agenda
• Training Materials (PDF format) |
| Engagement Report | Engagement Report, provided after the conclusion of the Transfer Equivalency service, summarizing the objectives and accomplishments of the sessions, relevant issues to be addressed, and tasks to be completed. | • Engagement Report |
## Service Assumptions
• Transfer articulation mapping records are complete, correct, and reside in the Client's SIS.
Client has licensed the following Ellucian Baseline Component Systems: Degree Works and Transfer Equivalency Admin.
## Client Responsibilities
- Provide the infrastructure to support the software (e.g., servers, personal computers and network, Oracle database);
- Provide appropriate campus resources as outlined in the Degree Works Campus Team Roles and Responsibilities document;
Client's expert teams will participate in all training and consulting sessions. Client's expert teams will review existing policies and procedures and begin to develop new procedures as appropriate. Each member of the team will review the information contained in the training documentation and the supplied training materials which explains the functionality of the Baseline Transfer Equivalency Admin Component System. These teams must complete all testing, validation, rule, and process development required for production system operations in their respective areas of specialization;
Provide any changes to the look-and-feel of the Self-Service application;
- Client will be responsible for taking the Baseline Transfer Equivalency Self-Service Component System into a live production environment and, in this regard, will make the determination as to the appropriate time frame for this undertaking;
Process any required business practice changes; and
Test the Degree Works Transfer Equivalency system for accuracy.
===== PAGE 178 =====
## Overview
The Ellucian Mobile Foundation Services are designed to provide a Client branded version of Ellucian Mobile within the Client's non-production and production environment, as well as a published application the Apple App Store, and Google Play.
Service Description
| Engagement | High Level Tasks | Deliverables |
| Project Initiation | Review project and expectations (technical and functional consultant both attend 1-hour call with Project Manager) | • Engagement Agenda
• Engagement Agenda
• Decision Workbook
• Engagement Report |
| Ellucian Mobile Discovery and Planning | • Partner with the Client to determine an Ellucian Mobile implementation strategy by reviewing Ellucian Mobile capabilities and functionalities and aligning them with the Client’s goals and objectives.
• Develop a strategy for the implementation of security roles and permissions of each Ellucian Mobile Module.
• Tailor the Ellucian Mobile Design branding, menu configuration, layout of content and navigation.
Specific objectives consist of:
• Project goals & objectives;
• System Education (review functionality and related decision points);
• Discovery (Decision Workbook documentation); and
• Design Planning (information design, menu configuration, mobile app navigation). | • Engagement Agenda
• Decision Workbook
• Engagement Report |
| Ellucian Mobile Readiness Review and Planning Service | Ellucian will provide Client with a remote readiness review and planning session to provide information about Ellucian’s Ellucian Mobile, Ellucian Mobile Services, and implementation and deployment of Ellucian Mobile.
Ellucian will provide Client with a Service Preparation Document (“SPD”); a checklist to ensure the Client’s environment is meets the requirements of Ellucian Mobile and provides valuable information to Ellucian delivering the services. | • SPD
• Mobile configuration
• Installation checklist
• Installation checklist documentation
• Engagement Report |
| Ellucian Mobile Installation and Configuration Service | Services consist of:
• 1 Ellucian Mobile server components into the non-production environment; and
• 1 Ellucian Mobile server components into the production environment.
Ellucian will pre-configure Ellucian Mobile on Client’s behalf with the Client’s branding. This consists of:
• Applying appropriately scaled image of Client’s logo (or Client’s image of choosing) as the Ellucian Mobile application logo, for iPhone this includes updating the splash/load screen. For both Android and iPhone this includes applying Client’s provided icon images; | • Mobile configuration
• Installation checklist
• Installation checklist documentation
• Engagement Report |
===== PAGE 179 =====
| Engagement | High Level Tasks | Deliverables |
| • Configuring the Ellucian Mobile application institution selection to be hardcoded directly against the Client's cloud configuration;
• Deploying a test application to the Client's internal environment; and
• Deploying the Client's branded production ready application in the Apple App Store, and Google Play.
Ellucian will provide the initial configuration of Ellucian Mobile Cloud for the Client. This includes setting up the following cloud configuration sections:
• Getting Started section (Mobile Server Key, and Mobile Server URL)
• General section (Database Configuration)
• Appearance/About sections (Colors/Splash Logo/About) | |
| Ellucian Mobile Training | The Ellucian Mobile Foundation Service includes an installation overview of Ellucian Mobile components as well as an overview on the cloud configuration utility. | |
| Ellucian Mobile Application Configuration | Review and document modifications to the design and configure Ellucian Mobile per agreed upon specifications as defined during the Ellucian Mobile discovery and planning engagement.
Specific objectives consist of:
• Documenting and review design modifications; and
• Configuring Ellucian Mobile as per agreed upon specifications. | • Configured Mobile Application
• Updated Decision Workbook |
| Ellucian Mobile Go-live Planning | Design and document a go-live adoption strategy including how to market Ellucian Mobile and teach end users the ease of use along with the benefits of Ellucian Mobile to optimize high number of end user adoption. The goal of this engagement is to create a roll-out plan that will ensuring a high level of downloads, regular use, student engagement and retention.
Review integration features with analytic tools such as Google analytics to review the metrics which confirm the ability to monitor key ROI metrics.
Specific objectives consist of:
• Creating a go-live adoption plan (marketing and support);
• Planning for engagement and retention; and
• Determining analytics metrics. | • Engagement Report |
## Service Assumptions
• Ellucian Mobile authentication will be configured via the Student Information System (SIS) native authentication method and can be configured via LDAP/AD as part of the standard service offering.
## Client Responsibilities
- Prior to the commencement of Ellucian Mobile Foundation Services, Client must obtain (or have obtained) a valid license for Ellucian Mobile Foundation edition from Ellucian to use Ellucian Mobile.
For Single Sign On authentication via federation, Ethos Identity will be required in non-production and production for Ellucian to perform configuration.
Client will provide remote access to Ellucian to the non-production and production server environment designated for the Ellucian Mobile Service activities, including system administrative privileges.
===== PAGE 180 =====
Client is responsible to confirm that the prerequisites described below are satisfied for Ellucian to be able to perform its services obligations hereunder.
Environment meets specifications for the deployment of the Ellucian Mobile Software.
Client facilitates logistics and invitation of Client's participants for each of the training services described herein
Coordinate with Ellucian to determine expectations and timeline.
• Client will provide properly scaled images as outlined in the SPD;
• Client will provide hexadecimal Red Green Blue ("RGB") color values for the application as outlined in the SPD.
Client will provide a compatible non-production and production environment.
• Services do not include applying Banner required pre-requisite releases, Client will ensure compliance.
The Banner Student API 9.4+ along with Banner Student 8.9.3+ are required for Registration via the Ellucian Mobile application
## Out of Scope
Single Sign On configuration is out of scope. Additional services can be purchased to integrate Ethos Identity with Ellucian Mobile for Single Sign On.
Banner MEP Clients
Ellucian will only provide Ellucian Mobile server components installations on Tomcat, which is currently the only supported application server.
Ellucian will use its development keys for the deployment of the application to the Apple App Store and Google Play. Optionally, we will utilize Client's keys by request.
Ellucian will install the mobile components. It is up to the Client to test and validate Mobile and the ERP to make use of the mobile features such as registration.
| Engagement | High Level Tasks | Deliverables |
| Initiation | • Project initiation | • Project Planning session |
| Planning | • Project planning and resource management
• Initial Development of Project Charter or Scope Statement
• Project internal repository for project artifacts
• Ellucian internal project initiation meeting
• Client project planning session
• Introduction of delivery management team | • Project Charter or Scope Statement
• Project schedule with Ellucian resources
• Project Repository |
| Execution | • Quality assurance activities
• Issue tracking
• Changes to scope
• Schedule resources, and costs, project risk response plans
• Project financials (budgets, project reconciliation)
• Knowledge resources
• Delivery of solution artifacts | • Updated project documentation and solution delivery artifacts
• Status reports
• Change requests |
| Transition and Close | • Transition planning, delivery to contract and project scope with client acceptance
• Project closure | • Transition plan
• Client letter of acceptance |
## Client Responsibilities
Client will provide information to Ellucian project team that will contribute to project activities and development of artifacts.
- Client will provide approval on all project activities, artifacts, and outcomes based on the agreed sign-off criteria and Client acceptance period for approval.
- Client will attend and participate in project status meetings as defined by the Ellucian project manager and Client project leader.
Client will support and otherwise cooperate with Ellucian throughout all project activities, development of artifacts, and project outcomes.
Client will provide a full-time project leader or functional leader who will manage the project and work directly with the Ellucian project manager and provide the required input and work product to support project activities, artifacts, and outcomes.
• Client will assign Client resources to complete Client tasks required as part of the project's schedule
Client will provide timely approval of project change requests prior to the start of the project change
===== PAGE 190 =====
