My WebLink
|
Help
|
About
|
Sign Out
Home
8F Consent 2020 0903
CityHall
>
City Clerk
>
City Council
>
Agenda Packets
>
2020
>
Packet 2020 0908
>
8F Consent 2020 0903
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
9/2/2020 7:11:20 PM
Creation date
9/2/2020 7:10:40 PM
Metadata
Fields
Template:
CM City Clerk-City Council
CM City Clerk-City Council - Document Type
Agenda
Document Date (6)
9/8/2020
Retention
PERM
Document Relationships
Reso 2020-109 903 CSA Ethosoft Inc for Laboratory Information Mgmt System
(Approved by)
Path:
\City Clerk\City Council\Resolutions\2020
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
103
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).
Download electronic document
View images
View plain text
Attachment F- Functionality Matrix <br /> <br />Proposer Instructions <br /> <br />The proposer must use the response index given below for each requirement listed to indicate <br />how each requirement will be met, with an optional explanation in the comments column to <br />provide more detail. <br /> <br />Response Index <br /> <br />1. Requirement met by an out-of-the-box proposed software package. Configuration, data, or <br />setting changes may be necessary, but the base software remains unchanged. The cost for <br />configuration for the specific functional requirement is included in the solution proposed by <br />the Vendor. <br /> <br />2. Requirement will be met by a Third Party Software product that is not licensed by the <br />Vendor. Identify the Third Party Software product with a description in the Comments <br />column. This is to indicate additional software licenses that the District would be required to <br />obtain in addition to the licenses provided by the Vendor. <br /> <br />3. Requirement will be met by custom programming that modifies the source code of the base <br />software. Describe the level of effort required to provide this functionality in the comments <br />column. <br /> <br />4. Requirement cannot be met by Vendor. <br /> <br />5. Separate narrative attached. <br /> <br />1. Sample Planning and Scheduling <br /> <br />ID # Description <br />Vendor <br />Response <br />(see Index) <br />Comment <br />1.1 LIMS shall include a calendar-based scheduler to <br />automatically pre-schedule routine samples. <br /> <br />1.2 <br />LIMS shall be able to store sample collection locations <br />and the frequency that various routine sample types are <br />to be collected from each location. <br /> <br />1.3 <br />LIMS shall include the capability to use bar code readers <br />and label printers to generate barcodes and user-defined <br />labels. Proposers should include a list of compatible <br />bar code readers and label printers. The Label <br />generator shall have the following capabilities: <br />1.3.1 Print labels for scheduled samples prior to <br />collection. <br />1.3.2 Print labels for ad-hoc samples prior to collection. <br />1.3.3 Print small labels that can be transferred to paper <br />worksheets. <br />1.3.4 Barcode reader can read container vendor codes to <br />identify container ID and type. <br />1.3.5 Label format shall have multiple fields to allow the <br />user to configure any number of parameters associated <br />with the sample, including printing barcodes on labels. <br /> <br />2298
The URL can be used to link to this page
Your browser does not support the video tag.