User:Shawndouglas/sandbox

System questionnaire

This questionnaire lists the extensive requirements of a laboratory informatics system, primarily of a LIMS, though these requirements could easily apply to other informatics systems. The intention of this document is 1. to assist labs with identifying their system needs and 2. to help labs better determine if a specific vendor/product meets their requirements in the form of a request for information (RFI).

This questionnaire is comprehensive and includes many items that do not apply to every lab. Additionally, some laboratories' requirements include a functionality item not common to other labs. Section 1.5 "Industry-specific questionnaire" contains a selection of those industry-specific requirements and will continue to be amended over time. The last section, 1.6 "Custom system functions questionnaire," is designed for the vendor to insert any additional functionality that doesn't fall under the categories provided.

When referencing a particular item for someone else, use the section number followed by the requirement letter, e.g. 1.4.2.f for "Does the system allow the system admin to create custom screens, apps, and reports?"

Requirement code and notes

In responding to each requirement, the vendor must select a requirement code from the following:

• Y: Meets requirement in commercial off-the-shelf solution as delivered/configured (or vendor provides service)
• YC: Meets requirement only with customization (additional code, using a third-party application, etc.)
• N: Does not meet requirement
• I: Informational response only, N/A

The vendor should ideally enter a requirement code and a response for each functionality question.

1.0 Vendor information

1.0 Vendor information Company name Physical address Website LIMSwiki web page Contact name and title Contact e-mail Contact phone and fax Years in business

1.1 Vendor services

1.1 Vendor services Request for information Requirement code Vendor response a. Does the vendor offer an online demonstration and/or an on-site demonstration? b. Does the vendor provide a detailed project approach and plan that includes the project team, timeline, deliverables, and risk and issue management procedures? c. Does the vendor explain their overall project approach, acknowledgement of the deliverables, time/schedule constraints, and any other criteria for the project? d. Does the vendor provide reliable cost estimates and pricing schedules, including all products and services in the scope of work? e. Can the vendor detail the amount of time and staff that purchaser will have to provide for the implementation process? f. Can the vendor explain the maintenance and support offered during and after implementation, including times and methods of availability, issue escalation and management, etc.? Give details. g. Does the vendor provide a support schedule for the implementation process, including optional support levels and their function and availability? Give details. h. Does the vendor provide support during the "go-live" period between system validation/operational deployment and final acceptance/beginning of maintenance and support agreements? i. Does the vendor provide a gap analysis after initial system installation, identifying the deliverables or tasks remaining? j. Does the vendor provide a table linking each deliverable to the corresponding user requirement specification it fulfills? k. Does the vendor use a consistent training methodology for training new users? Give details. l. Does the vendor supply LIMS-specific training program curricula? m. Does the vendor provide user, administrator, developer, installation, and reference manuals? Give details. n. Does the vendor provide design qualification documentation? o. Does the vendor provide installation qualification documentation? p. Does the vendor provide operation qualification documentation? q. Does the vendor provide performance qualification documentation during implementation? r. Does the vendor provide well-documented system upgrades that authorized users can independently install? s. Does the vendor provide source code for the system? t. Does the vendor provide an optional comprehensive set of test codes suitable for use by the purchasing facility?

1.2 Information technology

1.2 Information technology 1.2.1 General Request for information Requirement code Vendor response a. Does your system operate with a web-based interface (hosted on a server and accessed via a web browser) or on a more traditional client-server architecture? If web-based, what technology does it support? b. Does your system contain a single database that supports multiple laboratory sites and departments? c. Does your system's database conform to the Open Database Connectivity Standard (ODBC)? d. Did you design your system so upgrades to the back-end database do not require extensive reconfiguration or effectively cripple the system? Please describe. e. Did you design your system to not be impacted by multiple users or failover processes? Please describe. f. Does your system apply security features to all system files? g. Does your system apply login security to all servers and workstations accessing it? h. Does your system provide a workstation and server authentication mechanism? i. Does your system apply Secured Socket Layer (SSL) encryption on the web client interface? j. Does your system encrypt client passwords in a database with support for multi-case and special characters? k. Does your system provide all secured users access to its data via the Internet, LAN, or direct modem connection? l. Does your system use TCP/IP as its network transport? m. Does your system contain an archive utility that doesn't require off-line mode? n. Does your system provide local backup and restore capability without support intervention? o. Does your system maintain the transactional history of system administrators? 1.2.2 Hardware environment Request for information Requirement code Vendor response a. Does your system prove compatible with a variety of hardware environments? Please describe how. 1.2.3 Software environment Request for information Requirement code Vendor response a. Does your system utilize a non-proprietary database such as Oracle or Microsoft SQL Server? Please explain. b. Does your system prove compatible with a variety of software environments? Please describe how.

1.3 Regulatory compliance and security

1.3 Regulatory compliance and security 1.3.1 Regulatory compliance Request for information Requirement code Vendor response a. Does your system support 21 CFR Part 11 and 40 CFR Part 3 requirements, including login security, settable automatic logouts, periodic requirements for mandatory password changes, limits on reusability of passwords, and full electronic signature? Please explain in detail. b. Does your system support ISO/IEC 17025 requirements? Please explain how. c. Does your system support HIPAA requirements? Please explain how. d. Does your system support GALP and/or GAMP standards? Please explain how. e. Does your system support the standards The NELAC Institute? Please explain how. f. Does your system meet government requirements for handling classified information and documents? g. Does your system maintain audit and specification violation trails of all data manipulation — such as result and header information changes — as consistent with all applicable regulations and standards? Provide details. h. Does your system's audit log retain all data, prohibit any deletions, and allows user comments? i. Does your system provide additional persistent auditing capabilities? If so, what? j. Does your system provide user-selectable NELAP-compliant internal chain of custody that tracks all samples and associated containers from the time they are collected until disposed of? Please explain how. k. Does your system provide the ability to insert/manage secure electronic and/or digital signatures? l. Does your system incorporate automatic date and time stamping of additions, changes, etc.? 1.3.2 Security Request for information Requirement code Vendor response a. Does your system allow system administrators and managers to configure multiple levels of user rights and security by site location, department, role, and/or specific function? Please explain the depth of this security. b. Does your system allow administrators to reset user passwords? c. Does your system enforce rules concerning password complexity, reuse, and expiration? If so, how? d. Does your system provide automatic logout based on keyboard or mouse inactivity? e. Does your system prompt users for a reason for database record changes? f. Does your system allow administrators to modify records, while also maintaining an audit trail of such actions? g. Does your system allow authorized personnel to review audit logs at will? h. Does your system allow supervisors to override chain of custody? i. Does your system provide email notification of lockout, security access, and improper workstation access?

1.4 General system functions

1.4 General system functions 1.4.1 General Request for information Requirement code Vendor response a. Does your system offer non-LIMS trained personnel the ability to easily access system data via an intuitive, user-friendly Windows-type graphical user interface (GUI) which permits the display of data from sample points, projects, and user-defined queries, and can be configured to language, character set, and time zone needs? b. Does your system permit remote access for users, system admins, and support agents? c. Does your system utilize role-based presentation of menus and functions? d. Does your system allow for the use of navigation keys to freely move from field to field? e. Does your system allow data tables to be sorted? f. Does your system have a screen print function? g. Does your system provide single data entry, automatically populate other data fields, and remember pertinent and relevant data so it doesn't need to be re-entered, selected, or searched for? h. Does your system support multiple users entering data simultaneously? i. Does your system eliminate (or significantly reduce) redundant data entry and paper trails? If so, how? j. Does your system contain one or more spell-check dictionaries that allow authorized users to add, edit, or remove entries? k. Does your system provide full database keyword and field search capability? l. Does your system's search engine permit multiple search criteria? m. Does your system include the ability to search multiple databases, including those containing legacy data? n. Does your system interface with or import existing data from other systems and/or databases? o. Does you system cleanly convert migrated data to allow for reporting of historical sample collections? If so, how? p. Does your system provide data archival and retention functionality? q. Does your system manage archived, paper-based laboratory records? r. Does your system allow users to associate and store non-sample-related objects such as pictures from microscopes, GCMS scans of peaks, or even raw data files from instrument runs for later processing? s. Does your system allow users to associate and store sample-related objects such as pictures, spreadsheets, PDF files, etc., including any instrument-generated format outputs from equipment? t. Does your system store more non-traditional information and objects like project- or sample-specific special information fields, user-defined fields, scanned chain of custodies and digital photos of such items as sample events, bitmaps, movies, and .wav audio files? u. Does your system's numbering scheme allow for sub-numbering while maintaining parent-child relationships? v. Does your system efficiently utilize standardized data input points and enhanced individual workload tracking? w. Does your system capture data from all laboratory processes, ensuring uniformity of statistical reporting and other electronic data shared with designated users of the data? x. Does your system track status and workflow of the accession throughout the laboratory lifecycle, from submission to final analysis, including receiving, diagnostic testing, diagnostic test result reporting, and billing? y. Does your system support barcoded specimen labeling and tracking? z. Does your system have an inter-lab transfer function? aa. Does your system support the definition and maintenance of edit tables and lists? ab. Does your system issue sequential numbers for chain of custody? ac. Does your system allow authorized users to query and print chain of custody for items, cases, projects, and batches? ad. Does your system allow entry, maintenance, and administration of customers, suppliers, and other outside entities? ae. Does your system support multiple customer payment sources (e.g. grants}? Please explain the extent. af. Does your system link or embed standard operation procedures (SOPs) to/in other objects like analysis requests and test results? ag. Does your system allow multiple users to connect simultaneously to a contract lab? ah. Does your system provide read-only access to contract laboratory results? ai. Does your system notify users of events like the scheduling, receipt, and completion of tasks? aj. Does yout system include the ability to set up alerts via email? ak. Does your system maintain an analyst communication log? 1.4.2 Configuration and customization Request for information Requirement code Vendor response a. Can your system can be configured to meet the workflow of a laboratory without additional programming? Please explain how. b. Can your system easily and efficiently be modified to meet lab growth and changing business needs? Please explain how. c. Does your system include an application programming interface (API)? If so, what kind? If web, does it use Simple Object Access Protocol (SOAP) or representational state transfer (REST)? d. Can your system expand to accommodate a new discipline? If so, how? e. Can your system support customized screens with user-definable information specific to a customer, department, analysis, etc.? f. Does your system allow the administrator to create custom screens, applications, and reports? Please give details. g. Does the system allow a user to independently add fields without requiring reconfiguration of the system, even after routine upgrades and maintenance? h. Does your system allow a user to independently add universal fields on all samples logged into the system at any time during or after implementation, while neither voiding the warranty nor requiring vendor review at a later date? i. Does your system dynamically change captions (labels) on system fields? j. Does your system have dynamically configurable limit periods and notification hierarchy? k. Does your system allow for the integration of additional printers and scanners both locally and externally? 1.4.3 Receiving and scheduling Request for information Requirement code Vendor response a. Does your system create and maintain a unique electronic accession record for each accession received? b. Does your system support standard-format digital picture and document upload and attachment to electronic accession records? c. Does your system support a user-configurable, spreadsheet-style, templated multi-sample (batch) login without requiring additional programming? d. Does your system support the modification of sample or sample batch information prior to actual multi-sample (batch) login? e. Does your system support ad-hoc samples not predefined in the sample point list during multi-sample (batch) login? f. Does your system create, save, and recall pre-login groups for routine samples to simplify recurring logins? g. Does your system streamline the login of recurring sampling projects? h. Does your system automatically generate labels for recurring samples and sample groups? i. Does your system allow authorized users to generate user-definable chain of custodies, worksheets, routing sheets, and custom labels upon sample login? j. Does your system provide a comprehensive view of all samples and projects in the system using a color-coded status view of the current and scheduled samples via user-configurable templates, all without requiring additional programming? k. Does your system prevent a sample from being placed in a report queue until approved? l. Does your system include comprehensive sample scheduling, tracking, and sample flow management? m. Does your system allow authorized users to schedule routine samples on an hourly, daily, weekly, or monthly basis, allowing them to be enabled and disabled as a group? n. Does your system generate an hourly, daily, weekly, or monthly sampling schedule from a schedule database? o. Does your system schedule and assign tasks based on available inventory and personnel? p. Does your system support automatic assignment and scheduling of analysis requests? q. Can your system receive accession/analysis request information from web-enabled forms? r. Can your system process automated uploading of field-derived sample collection data? s. Does your system allows users to handle billable and non-billable tests on the same accession? t. Does your system support tracking of shipping and receiving? 1.4.4 Analysis and data entry Request for information Requirement code Vendor response a. Does your system support a variety of test protocols, each capable of storing test comments, test required, and special information like GCMS conditions or special objects associated with the test? Please give details. b. Does your system provide normal data range values for diagnostic tests? c. Does your system includes default input values for diagnostic tests? d. Does your system provide for a single test code requiring multiple analytes as targets? e. Does your system limit test code authorization to only qualified personnel and maintain their certification(s) to run assigned tests? f. Does your system support and qualify text-based tests? g. Does your system support single-component tests such as pH, BOD, CD, etc.? h. Does your system allow users to specify a single-component, multi-component, or narrative text test or group of tests, which represent all tests required? i. Does your system permit user-generated and modifiable calculations (based on a formulaic language) to be applied to all tests? j. Does your system distinguish between routine and duplicate analysis? k. Does your system provide an overview of all outstanding tests/analyses for better coordination of work schedules? l. Does your system electronically transfer an item during testing from one functional area to another? m. Does your system's user interface display visual indicators such as status icons to indicate a sample's status in the workflow? n. Does your system update sample/item status when tests are completed? o. Does your system read results from previously entered tests to calculate a final result and immediately display the calculated result? p. Does your system notify analysts of applicable safety hazards associated with a sample, reagent, or test before testing begins? q. Does your system allow authorized users to review all analytical results, including pricing, spec violations, history or trend analysis by analyte, and comments? r. Does your system allow on-screen review of the stored test result, diluted result with corrected method detection limits (MDLs), and qualifiers after running samples for multiple dilutions as in gas chromatography–mass spectrometry (GC-MS)? s. Does your system display the standard operating procedure (SOP) associated with each test result to ensure proper techniques were used? t. Does your system store test-related analysis comments with the test? u. Does your system provide for high-volume multi-component transfers of test results, with the ability to automatically match samples to data files in either a backlog mode or a designated file mode, to parse the data, and to review and commit the sample data? v. Does your system's results validation process access all information about a sample or group of samples, including comments or special information about the sample? w. Does your system's results validation process check each result against its individual sample location specifications (both warning and specification limits)? x. Does your system support validation at the analysis and sample level, while also prohibiting sample validation when analysis validation is incomplete? y. Does your system use a menu-driven process for results validation? z. Does your system provide secure electronic peer review of results? aa. Can your system clearly differentiate released preliminary data from fully validated results? ab. Does your system validate/approve data prior to being moved to the main database? ac. Does your system fully manage all aspects of laboratory quality control, including the reporting and charting of all quality control data captured in the lab? Please explain how. ad. Does your system provide a base for a quality assurance program, including proficiency testing, scheduled maintenance of equipment, etc.? Please explain how. ae. Does your system distinguish QA/QC duplicates from normal samples? af. Does your system allow QA/QC tests to be easily created and associated with the primary analytical test? ag. Does your system calculate monthly QA/QC percentages for testing? ah. Does your system automatically flag out-of-range quality control limits? ai. Does your system check data files for specification and corrects them for specific reporting and analyte limits and qualifiers like dilution factor, automatically assigning qualifiers based on project analyte limiting? aj. Does your system allow file transfer of data from instrument or user-generated files, with full on-screen review prior to database commitment? ak. Does your system permit manual data entry into an electronic worksheet of test measurements and results? al. Does your system allow incorrectly inputted data to be manually corrected? am. Does your system provide colored visual indication of previously entered data as well as new data associated with a single sample when a result is entered, with the indicator changing color if the value is out of specification? an. Does your system permit result entry via intelligent instrument interfaces or multi-sample/multi-test ASCII files? ao. Does your system allow automated or semi-automated data insertion? ap. Does your system provide auto-commenting for common laboratory result comments? aq. Does your system store non-narrative textual results in searchable fields? 1.4.5 Instruments Request for information Requirement code Vendor response a. Does your system bilaterally interface with instruments and related software? If so, please provide details. b. Can your system download data directly from laboratory instruments? c. Does your system permit the defining and exporting of sequences to instruments? d. Does your system track and report on laboratory equipment usage? e. Does your system allow automatic or manual reservation/scheduling of laboratory instruments? f. Does your system automatically (or manually allow an authorized user to) remove an instrument from potential use when it falls out of tolerance limit or requires scheduled calibration? g. Does your system provide a database of preventative maintenance, calibration, and repair records for laboratory equipment, preferably supported by standardized reporting? h. Can your system schedule calibration/verification tasks in the worksheets or work flow process? 1.4.6 External system interfaces Request for information Requirement code Vendor response a. Does your system support a library of common and/or basic electronic data deliverable (EDD) formats? If so, which? b. Can your system transfer data to and from another record management system? If so, how? c. Does your system integrate with Microsoft Exchange services? d. Can your system import data from and export data to Microsoft Word, Excel, and/or Access? e. Can your system interface with non-Microsoft programs? If so, which? f. Can your system interface with external billing systems? If so, how? g. Can your system interface with enterprise resource planning (ERP) systems? If so, how? h. Can your system interface with contract laboratories to electronically retrieve datasheets, sample analysis, and other related information? i. Can your system exchange data with National Identification System (NAIS) tracking systems? j. Can your system generate and exchange data with other systems using Health Level 7 (HL7) standards? k. Can your system leverage the application programming interface (API) of other systems to establish integration between systems? l. Can your system transmit status changes of samples, inventory, equipment, etc. to an external system? m. Can your system direct output from ad-hoc queries to a computer file for subsequent analysis by other software? n. Does your system support dockable mobile devices and handle information exchange between them and the system? 1.4.7 Reporting Request for information Requirement code Vendor response a. Does your system include a versatile report writer and forms generator? If so, please provide details. b. Does your system include a custom graphic generator for forms? c. Does your system interface with third-party reporting application? d. Does your system allow development of specific templates for different types of reports? e. Does your system maintain template versions and renditions, allowing management and tracking of the template over time? f. Can your system generate template letters for semi-annual reports? g. Can your system generate reports from any data in tables? h. Does your system support report queries by fields/keys, status, completion, or other variables? i. Does your system use Microsoft Office tools for formatting reports? j. Does your system support multiple web browsers for viewing online reports? If so, list which ones. k. Does your system permit sample progress reports to be viewed locally or remotely based on security application limits and/or sample ownership? l. Can your system generate, store, reproduce, and display laboratory, statistical, and inventory reports on demand, including narrative? m. Does your system include several standard reports and query routines to access all samples with the pending status through a backlog report that includes the following criteria: all laboratory, department, analysis, submittal date, collection date, prep test complete, location, project, sample delivery group, and other user-selectable options? n. Can your system generate management and turn-around time reports and graphs? o. Can your system generate customized final reports? p. Can your system automatically generate laboratory reports of findings and other written documents? q. Can your system automatically generate individual and aggregate workload and productivity reports on all operational and administrative activities? r. Can your system automatically generate and transmit exception trails and exception reports for all entered and/or stored out-of-specification data? s. Can your system generate a read-only progress report that allows for printed reports of sample status and data collected to date? t. Does your system provide an ad-hoc web reporting interface to report on user-selected criteria? u. Can your system automatically generate and update control charts? v. Can your system generate QA/QC charts for all recovery, precision, and lab control samples via a full statistics package? w. Does your system display history of previous results for an analyte's sample point in a tabular report, graphic trend chart, and statistical summary? x. Can your system automatically generate and post periodic static summary reports on an internal web server? y. Does your system transmit results in a variety of ways including fax, e-mail, print, and website in formats like RTF, PDF, HTML, XML, DOC, XLS, and TXT? z. Does your system prohibit issuing reports outside of qualified areas? If so, how? aa. Does your system electronically transmit results via final report only when all case reviews have been completed by the case coordinator? ab. Can your system send on-screen output to a printer or file? If so, does it contradict view-only statuses? ac. Does your system allow database access using user-friendly report writing and inquiry tools? 1.4.8 Laboratory management Request for information Requirement code Vendor response a. Does your system allow the creation, modification, and duplication of user profiles? b. Does your system allow the management of information workflow, including notifications for requests and exigencies? c. Does your system allow the management of documents like SOPs, MSDS, etc. to better ensure they are current and traceable? d. Does your system allow the management and monitoring of resources by analyst, priority, analysis, and instrument? e. Does your system allow authorized persons to select and assign tasks by analysts, work group, instrument, test, sample, and priority? f. Does your system allow authorized persons to review unassigned work by discipline and by lab? g. Does your system allow authorized persons to review pending work by analyst prior to assigning additional work? h. Does your system manage and report on reference samples, reagents, and other inventory? If so, to what extent? i. Does your system allow authorized users to monitor and report on reference and reagent creation, use, and expiration? j. Does your system allow authorized users to search invoice information by invoice number, account number, accession, payment types, client, or requested diagnostic test(s)? k. Does your system include performance assessment tracking? l. Does your system monitor proficiency test assignment, completion, and casework qualification for analytical staff? m. Does your system provide analysis tools for laboratory operations to better support resource planning, productivity projections, workload distribution, and work scheduling? n. Does your system calculate administrative and lab costs? o. Does your system track number of visits per specific industry?

1.5 Industry-specific

1.5 Industry-specific 1.5.1 Agriculture industry functions Request for information Requirement code Vendor response a. Does your system permit input and query of information such as (but not limited to) client ID numbers, animal species, animal breed, animal sex, animal diagnostic test performed, animal diagnostic test result, client or bill to zip code, program or funding codes, date ranges, lab department, case coordinator, and lab technician? Please provide details. b. Does your system make report output available online for external and internal web viewing? c. Does your system permit manual override of allowable test/species combinations for circumstances outside the norm? If so, to what extent? 1.5.2 Forensics functions Request for information Requirement code Vendor response a. Does your system provide functionality for each discipline, including latent prints, crime scene unit, multi-media lab, evidence control, ballistics, polygraph, forensic chemistry, and DNA? b. Does your system provide complete, accurate, and timely processing and tracking of evidence, reports, and statistical information? c. Does your system support open field numbering to create evidence packets? d. Does your system use barcode or radio frequency (RFID) technology to identify and track property/evidence? e. Does your system support additional segmentation of evidence? f. Does your system maintain evidence inventory and include the ability to make a report from it? g. Does your system record transaction date/time/persons associated with the movement of lab evidence? h. Does your system implement security functions such as password, PIN, etc. for evidence transfers? i. Does your system meet ASCLD standards for certified lab evidence transfers? j. Does your system list evidence currently or recently checked out by an analyst? k. Does your system initiate automatic flags and processing for evidence return? l. Does your system provide automated chain of custody for all items of evidence? m. Does your system permit analysis of evidence in support of intelligence activities, including dissemination of document intelligence, document analysis, and other technical information to the law enforcement community? n. Does your system support the analysis of document and fingerprint evidence? o. Does your system support the documentation of expert witness and other court testimony in courts of law and other judicial proceedings? p. Does your system internally manage case workflow, including case assignment, case forwarding, and notification? q. Does your system support a statewide single case number? r. Does your system link system and lab case numbers or Z (database) numbers? s. Does your system make objects associated with a case or submission accessible only from within the application? t. Does your system provide automated, limited remote access to the database for case status inquiries and to view case reports? u. Does your system allow authorized users to configure case reports for location? v. Does your system require case notes, data, and reports to be previewed before approval? w. Does your system permit a supervisor or assignee to review all pending cases before assignment to staff? x. Does your system allow customer case status checking without staff intervention? y. Does your system facilitate sharing of information with federal, state, and local law enforcement agencies? Please explain how. z. Does your system support ASTM standards, including evidence handling and numbering? aa. Does your system support submission of requests for forensic examination electronically via e-mail, the FDL intranet, or FTP server? ab. Does your system permit authorized users to define analytical parameters based on case and standard operation procedure (SOP)? ac. Does your system collect data on and report on meeting forensic case requester and case return deadlines? ad. Does your system provide report templates with variable fields for things such as case, item results, and conclusion? ae. Does your system display individual examiner workload/productivity in a consolidated view, with the ability to drill down to more detailed data? af. Does your system provide a record locate function by name, agency, ORI, etc.? ag. Does your system manage inventory of chemical, ammo, supplies, etc.? 1.5.3 Medical, health, and public health functions Request for information Requirement code Vendor response a. Does your system automatically report any diagnostic test results deemed "suspect" or "positive" for reportable diseases? b. Can your system differentiate among clinical, environmental, and other types of samples and their associated test requests? c. Can your system accept and process third-party epidemiology data associated with test requests? d. Can your system create documentation for and route samples to the Centers for Disease Control and Prevention (CDC) and other contract laboratories? 1.5.4 Environmental, water, and wastewater industry functions Request for information Requirement code Vendor response a. Does your system provide a flexible procedure for assigning location codes or sample types for each default sample point, including tests required, report types, invoice information, maximum holding time, project accounts, and location description; each location code has an upper and lower warning limit, target specification for every analyte assigned, and stored defaults for all user-defined universal fields, special project fields, and sample comments? b. Does your system link all lab results with the correct reporting test method? c. Does your ystem comply with the Cross Media Electronic Reporting Rule (CROMERR) of Title 40 CFR Part 3? d. Can your system generate and print industrial reports, sampling reports, inspection reports, fact sheets, citations, formal charges, correspondence letters, and industrial permits? e. Can your system generate and print corresponding letters/templates for special and routine cases (e.g. industrial waste, permit renewals, semi-annual reports)? f. Can your system generate and print sampling cost reports for each industry, including the number of visits, types of analyses, calculated administrative cost, tubing cost, and duplicate sample cost, etc.? g. Can your system generate and print a biochemical oxygen demand (BOD) and total suspended solids (TSS) result report for industries? h. Can your system generate and print a special report for HAZMAT incidents, storm water violations, spills/slugs, and local limit violators? i. Can your system generate and print a report that determines if an industry is in significant non-compliance (SNC)? j. Does your system index and compile lists of businesses and industries that are in non-compliance/violation? k. Can your system generate notices of violation according to permit criteria and local limits? l. Does your system determine violation by either combined waste stream formula or local limits? If so, explain. m. Can your system generate documentation for filing charges? n. Can your system generate reminder notices for citation dates? o. Can your system generate permits, permit applications, directions for the application, and semi-annual report templates with fields like "name of industry," "mailing address," "SIC code," "permit number," and "contact name"? p. Can your system link permit criteria with significantly non-compliant criteria? q. Can your system generate correspondence letters for permit renewals and new permits? r. Does your system store permits for each industry? s. Does your system calculate surcharge fees for each industry? t. Does your system calculate surcharge from chain of custodies and data results? u. Can your system compile cost data for each industry? v. Does your system index all industries/companies by Standard Industrial Classification (SIC) code? w. Does your system index all industries/companies by: categorical and non-categorical, exempt and non-exempt, alphabetical order, permit number, bar code, permit due dates, as well as daily, weekly, biweekly, monthly, quarterly, bi-annual, and annual? x. Does your system contain an address book for all industries and programs in environmental compliance that indexes alphabetically, by industry, by address, etc.? y. Does your system store standard operating procedures (SOPs) for all pretreatment procedures? z. Does your system permit entering matrix duplicates for oil and grease samples?

1.6 Custom functions

1.6 Custom functions Request for information Requirement code Vendor response a. Enter your own unique function here