My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Agenda Packet_2025-08-05
Clerk
>
Agenda Packets / Staff Reports
>
City Council (2004 - Present)
>
2025
>
08/05/2025 Regular
>
Agenda Packet_2025-08-05
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
7/30/2025 5:11:00 PM
Creation date
7/30/2025 5:07:38 PM
Metadata
Fields
Template:
City Clerk
Doc Type
Agenda Packet
Agency
Clerk of the Council
Date
8/5/2025
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
595
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
I <br />3. Standard Setup Ta sks: Configuration and Branding Application <br />The purpose of this task is to configu re and test the Meridian LMS software application based <br />upon the completed and approved Requirements Document as defined in task 8.2 above. <br />MERIDI AN Deliverables CLIENT Deliverables <br />Comp lete the setup of all agreed upon <br />softwa re application configurations. <br />Setup One (1) branded Merid ian LMS <br />CLIENT specific skin. <br />Graphics per branding checklist <br />specifications. <br />Assumptions Accep tance Criteria <br />Application Branding -MERIDIAN will <br />deliver one ( 1) round of final pre-production <br />skin mock up to the CLIENT for review and <br />approval prior to setup in the Meridian LMS <br />CLIENT Stage environment. <br />Application Branding -MERIDIAN will <br />deliver one (1) round of final pre-production <br />sk in review and changes upon applying to <br />the Meridian LMS CLIENT Stage <br />environment. <br />MERIDIAN will conduct and support five (5) <br />days of Customer Acceptance Testing for <br />all tasks defined in section B herein. <br />4. Standard Setup Tasks: System Integration <br />Configurations completed and tested per <br />the Requirements specified in task 8.2 <br />above. <br />Meridian LMS application CLIENT Branded <br />skin configured and tested , per the <br />Requirements specified in task 8.2 above. <br />The purpose of the following task is to setup the inbound to Meridian LMS HRIS Integration. The <br />HRIS inbound feed transmits employee detail from CLIENT's HR sys tem to MERIDIAN (e.g . <br />Employee Name, Organization, and Job Title). <br />CLIENT will provide three (3) fl at files to MERID IAN, in MERIDIAN 's format, for the inbound <br />processing and loading of HRIS data (Organiza tions, Job Titles, User data). The HRIS/DAIL Y <br />FEED data (flat files) must follow the specifications designated in MERIDIAN 's HRI S templates. <br />Any extension of the file schema's and/or processing/va lidation requirements may result in an <br />expansion of scope for this task and may require additional funding. Meridian's tool to process the <br />aforementioned flat files performs the appropriate inserts and updates of Organization Data, Job <br />Titles , then Users, processing all data through the native APl's of Merid ian LMS. <br />Saas Agreement: Multi-Tenant meridianks.com <br /> <br />City Council 14 – 30 8/5/2025
The URL can be used to link to this page
Your browser does not support the video tag.