Difference between revisions of "User:Shawndouglas/sandbox"
From LIMSWiki
Jump to navigationJump to searchShawndouglas (talk | contribs) (Saved.) |
Shawndouglas (talk | contribs) (Updated content.) |
||
Line 7: | Line 7: | ||
==Sandbox begins below== | ==Sandbox begins below== | ||
{| | {| | ||
Line 112: | Line 105: | ||
! style="color:brown; background-color:#ffffee; width:700px;"| Notes | ! style="color:brown; background-color:#ffffee; width:700px;"| Notes | ||
|- | |- | ||
| style="padding:5px; width:500px;" |'''a.''' | | style="padding:5px; width:500px;" |'''a.''' System contains single database that supports multiple laboratory sites and laboratory departments | ||
| style="background-color:white; padding:5px;" | | | style="background-color:white; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
|- | |- | ||
| style="padding:5px; width:500px;" |'''b.''' | | style="padding:5px; width:500px;" |'''b.''' System encrypts client passwords in database with support for multi-case and special characters | ||
| style="background-color:white; padding:5px;" | | | style="background-color:white; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
|- | |- | ||
| style="padding:5px; width:500px;" |'''c.''' | | style="padding:5px; width:500px;" |'''c.''' System uses secured Socket Layer (SSL) encryption on web client interface | ||
| style="background-color:white; padding:5px;" | | | style="background-color:white; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
Line 132: | Line 125: | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
|- | |- | ||
| style="padding:5px; width:500px;" |'''f.''' | | style="padding:5px; width:500px;" |'''f.''' System database conforms to [[ODBC|Open Database Connectivity Standard]] (ODBC) | ||
| style="background-color:white; padding:5px;" | | | style="background-color:white; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
|- | |- | ||
| style="padding:5px; width:500px;" |'''g.''' | | style="padding:5px; width:500px;" |'''g.''' System can apply security to all system files | ||
| style="background-color:white; padding:5px;" | | | style="background-color:white; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
|- | |- | ||
| style="padding:5px; width:500px;" |'''h.''' | | style="padding:5px; width:500px;" |'''h.''' System provides login security to all servers and workstations accessing it | ||
| style="background-color:white; padding:5px;" | | | style="background-color:white; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
|- | |- | ||
| style="padding:5px; width:500px;" |'''i.''' | | style="padding:5px; width:500px;" |'''i.''' System able to use TCP/IP as its network transport | ||
| style="background-color:white; padding:5px;" | | | style="background-color:white; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
|- | |- | ||
| style="padding:5px; width:500px;" |'''j.''' | | style="padding:5px; width:500px;" |'''j.''' System designed to not be impacted by multiple users or failover processes | ||
| style="background-color:white; padding:5px;" | | | style="background-color:white; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
|- | |- | ||
| style="padding:5px; width:500px;" |'''k.''' | | style="padding:5px; width:500px;" |'''k.''' System supplies archive utility without off-line | ||
| style="background-color:white; padding:5px;" | | | style="background-color:white; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
Line 164: | Line 157: | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
|- | |- | ||
| style="padding:5px; width:500px;" |'''n.''' System | | style="padding:5px; width:500px;" |'''n.''' System interfaces with database using ASP/ASP.net | ||
| style="background-color:white; padding:5px;" | | | style="background-color:white; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
Line 205: | Line 198: | ||
! style="color:brown; background-color:#ffffee; width:700px;"| Notes | ! style="color:brown; background-color:#ffffee; width:700px;"| Notes | ||
|- | |- | ||
| style="padding:5px; width:500px;" |'''a.''' | | style="padding:5px; width:500px;" |'''a.''' System has security consistent with [[21 CFR Part 11]] and [[40 CFR Part 3]], including login security, settable automatic logouts, periodic requirements for mandatory password changes, limits on reusability of passwords, and full electronic signature | ||
| style="background-color:white; padding:5px;" | | | style="background-color:white; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
|- | |- | ||
| style="padding:5px; width:500px;" |'''b.''' [[ | | style="padding:5px; width:500px;" |'''b.''' System maintains [[audit trail]] and specifications violation trails, including result changes and header information changes, as well as the user, date/time, and a required reason for the changes as a standard part of the application | ||
| style="background-color:white; padding:5px;" | | | style="background-color:white; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
Line 292: | Line 285: | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
|- | |- | ||
| style="padding:5px; width:500px;" |'''f.''' | | style="padding:5px; width:500px;" |'''f.''' System includes administrator ability to reset user passwords | ||
| style="background-color:white; padding:5px;" | | | style="background-color:white; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
|- | |- | ||
| style="padding:5px; width:500px;" |'''g.''' | | style="padding:5px; width:500px;" |'''g.''' System can interface with or import existing data | ||
| style="background-color:white; padding:5px;" | | | style="background-color:white; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
|- | |- | ||
| style="padding:5px; width:500px;" |'''h.''' | | style="padding:5px; width:500px;" |'''h.''' System can be configured to meet the characteristics of the laboratory | ||
| style="background-color:white; padding:5px;" | | | style="background-color:white; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
Line 312: | Line 305: | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
|- | |- | ||
| style="padding:5px; width:500px;" |'''k.''' | | style="padding:5px; width:500px;" |'''k.''' System allows user to store object files such as pictures from microscopes, GCMS scans of peaks, or even raw data files from instrument runs for later processing | ||
| style="background-color:white; padding:5px;" | | | style="background-color:white; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
|- | |- | ||
| style="padding:5px; width:500px;" |'''l.''' | | style="padding:5px; width:500px;" |'''l.''' System provides non-LIMS trained personnel access to the LIMS data via a simple Windows-type browser interface which permits the display of data from sample points, projects, or user-defined queries | ||
| style="background-color:white; padding:5px;" | | | style="background-color:white; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
Line 376: | Line 369: | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
|- | |- | ||
| style="padding:5px; width:500px;" |'''aa.''' | | style="padding:5px; width:500px;" |'''aa.''' System able to print chain of custody for items, cases, projects, and batches | ||
| style="background-color:white; padding:5px;" | | | style="background-color:white; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
|- | |- | ||
| style="padding:5px; width:500px;" |'''ab.''' System has inter-lab transfer function | | style="padding:5px; width:500px;" |'''ab.''' System has an inter-lab transfer function | ||
| style="background-color:white; padding:5px;" | | | style="background-color:white; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
Line 388: | Line 381: | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
|- | |- | ||
| style="padding:5px; width:500px;" |'''ad.''' | | style="padding:5px; width:500px;" |'''ad.''' System audit log retains all data, prohibits any deletions, and allows user comments | ||
| style="background-color:white; padding:5px;" | | | style="background-color:white; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
Line 476: | Line 469: | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
|- | |- | ||
| style="padding:5px; width:500px;" |'''az.''' | | style="padding:5px; width:500px;" |'''az.''' System cleanly converts migrated data to allow for reporting of historical sample collection | ||
| style="background-color:white; padding:5px;" | | | style="background-color:white; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
Line 486: | Line 479: | ||
! style="color:brown; background-color:#ffffee; width:700px;"| Notes | ! style="color:brown; background-color:#ffffee; width:700px;"| Notes | ||
|- | |- | ||
| style="padding:5px; width:500px;" |'''a.''' | | style="padding:5px; width:500px;" |'''a.''' System allows user to independently add fields without requiring reconfiguration of the system after routine upgrades and maintenance | ||
| style="background-color:white; padding:5px;" | | | style="background-color:white; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
Line 532: | Line 525: | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
|- | |- | ||
| style="padding:5px; width:500px;" |'''b.''' | | style="padding:5px; width:500px;" |'''b.''' System supports electronic accession records with digital picture and document uploads in standard formats | ||
| style="background-color:white; padding:5px;" | | | style="background-color:white; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
Line 556: | Line 549: | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
|- | |- | ||
| style="padding:5px; width:500px;" |'''h.''' | | style="padding:5px; width:500px;" |'''h.''' System supports the modification of sample or sample batch information prior to actual multi-sample login | ||
| style="background-color:white; padding:5px;" | | | style="background-color:white; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
|- | |- | ||
| style="padding:5px; width:500px;" |'''i.''' | | style="padding:5px; width:500px;" |'''i.''' supports ad-hoc samples not predefined in the sample point list during multi-sample login | ||
| style="background-color:white; padding:5px;" | | | style="background-color:white; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
Line 1,073: | Line 1,066: | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
|- | |- | ||
| style="padding:5px; width:500px;" |'''b.''' | | style="padding:5px; width:500px;" |'''b.''' System makes report output available online for external and internal web viewing | ||
1 | | style="background-color:white; padding:5px;" | | ||
a. | | style="background-color:white;" | | ||
|- | |||
| style="padding:5px; width:500px;" |'''c.''' System permits manual override of allowable test/species combinations for circumstances outside the norm | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
! colspan="3" style="color:DarkSlateGray; text-align:left; padding-left:40px;"| 1.5.2 '''Forensics: functional requirements''' | |||
|- | |||
! style="color:brown; background-color:#ffffee; width:500px;"| Functional requirement | |||
! style="color:brown; background-color:#ffffee; width:100px;"| Requirement code | |||
! style="color:brown; background-color:#ffffee; width:700px;"| Notes | |||
|- | |||
| style="padding:5px; width:500px;" |'''a.''' System uses barcode technology to identify and track property/evidence | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''b.''' System provides functionality for each discipline, including latent prints, crime scene unit, multi-media lab, evidence control, ballistics, polygraph, forensic chemistry, and DNA | |||
a. | | style="background-color:white; padding:5px;" | | ||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''c.''' System internally manages case workflow, including case assignment, case forwarding, and notification | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''d.''' System tracks court testimony | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''e.''' System supports additional segmentation of evidence | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''f.''' System provides a record locate function by name, agency, ORI, etc. | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''g.''' System records transaction date/time/persons associated with movement of lab evidence | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''h.''' System meets [[The American Society of Crime Laboratory Directors/Laboratory Accreditation Board|ASCLD]] standards for certified lab evidence transfers | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''i.''' System implements security functions such as password, PIN, etc. in evidence transfer | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''j.''' System supports [[ASTM International|ASTM]] standards, including evidence handling and numbering | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
3 | | style="padding:5px; width:500px;" |'''k.''' System supports open field numbering to create evidence packets | ||
a. | | style="background-color:white; padding:5px;" | | ||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''l.''' System provides evidence inventory with report capability | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''m.''' System sets automatic flags and processing for evidence return | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''n.''' System supports a statewide single case number | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''o.''' System provides a "search for prior submission" function | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''p.''' System requires case notes, data, and reports to be previewed before approval | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''q.''' System provides report templates with variable fields for things such as case, item results, and conclusion | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''r.''' System allows customer case status checking without staff intervention | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''s.''' System makes objects associated with a case or submission accessible only from within the application | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''t.''' System manages inventory of chemical, ammo, supplies, etc. | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''u.''' System permits authorized users to define analytical parameters based on case and standard operation procedure (SOP) | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''v.''' System permits supervisor or assignee to review all pending cases before assignment to staff | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''w.''' System lists evidence currently or recently checked out by analyst | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''x.''' System allows authorized users to configure case reports for location | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''y.''' System links system and lab case numbers or Z (database) numbers | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''aa.''' System displays individual examiner workload/productivity in a consolidated view, with ability to drill down to more detailed data | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''ab.''' System facilitates sharing of information with federal, state, and local law enforcement agencies | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''ac.''' System provides complete, accurate, and timely processing and tracking of evidence, reports, and statistical information | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''ad.''' System supports submission of requests for forensic examination electronically via e-mail, the FDL intranet, or FTP server | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''ae.''' System provides automated, limited remote access to database for case status inquiries and to view case reports | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''af.''' System supports analysis of document and fingerprint evidence | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''ag.''' System provides automated chain of custody for all items of evidence | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''ah.''' System supports documentation of expert witness testimony in courts of law and other judicial proceedings | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''ai.''' System permits analysis of evidence in support of intelligence activities, including dissemination of document intelligence, document analysis, and other technical information to the law enforcement community | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''aj.''' System supports data collection on meeting forensic case requester and case return deadlines | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
! colspan="3" style="color:DarkSlateGray; text-align:left; padding-left:40px;"| 1.5.3 '''Medical and health: functional requirements''' | |||
|- | |||
! style="color:brown; background-color:#ffffee; width:500px;"| Functional requirement | |||
! style="color:brown; background-color:#ffffee; width:100px;"| Requirement code | |||
! style="color:brown; background-color:#ffffee; width:700px;"| Notes | |||
|- | |||
| style="padding:5px; width:500px;" |'''a.''' System can automatically report any diagnostic test results deemed "suspect" or "positive" for reportable diseases | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
! colspan="3" style="color:DarkSlateGray; text-align:left; padding-left:40px;"| 1.5.4 '''Environmental, water, and wastewater: functional requirements''' | |||
|- | |||
! style="color:brown; background-color:#ffffee; width:500px;"| Functional requirement | |||
! style="color:brown; background-color:#ffffee; width:100px;"| Requirement code | |||
! style="color:brown; background-color:#ffffee; width:700px;"| Notes | |||
|- | |||
| style="padding:5px; width:500px;" |'''a.''' System provides 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 | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''b.''' System can calculate surcharge fees for each industry | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''c.''' System compiles cost data for each industry in the database | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''d.''' System stores permits for each industry | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''e.''' System links permit criteria with significantly non-compliant criteria | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''f.''' System generates notices of violation according to permit criteria and local limits | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''g.''' System stores standard operating procedures (SOPs) for all pretreatment procedures | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''h.''' System links all lab results with the correct reporting test method | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''i.''' System generates correspondence letters for permit renewals and new permits | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''j.''' System generates permit, permit application, directions for the application, and semi-annual report templates with fields like "name of industry," "mailing address," "SIC code," "permit number," and "contact name" | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''k.''' System generates documentation for filing charges | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''l.''' System generates reminder notices for citation dates | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''m.''' System able to index all industries/companies by Standard Industrial Classification (SIC) codes | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''n.''' System able to 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 | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''o.''' System contains an address book for all programs in environmental compliance that indexes alphabetically, by industry, by address, etc. | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''p.''' System indexes and compiles lists of industries that are in non-compliance/violation | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''q.''' System can calculate surcharge from chain of custodies and data results | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''r.''' System permits entering matrix duplicates for oil and grease samples | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''s.''' System can determine violation by either combined waste stream formula or local limits | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''t.''' System generates a report that determines if an industry is in significant non-compliance (SNC) | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''u.''' System generates sampling cost reports for each industry, which includes the number of visits, analysis, calculated administrative cost, tubing cost, and duplicate sample cost, etc. | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''v.''' System generates a biochemical oxygen demand (BOD) and total suspended solids (TSS) result report for industries | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''w.''' System generates and prints industrial reports, sampling, inspections, fact sheets, citations, formal charges, correspondence letters, and industrial permits | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''x.''' System generates a special report for HAZMAT incidents, storm water violations, spills/slugs, and local limit violators | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''y.''' System complies with the Cross Media Electronic Reporting Rule (CROMERR) of [[40 CFR Part 3|Title 40 CFR Part 3]] | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''z.''' System generates corresponding letters/templates for special and routine cases (e.g. industrial waste, permit renewals, semi-annual reports) | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
|} | |||
{| class="wikitable collapsible" border="1" cellpadding="10" cellspacing="0" | |||
|- | |||
! colspan="3" style="text-align:left; padding-left:20px; padding-top:10px; padding-bottom:10px;"| 1.6 '''Custom functional requirements''' | |||
|- | |||
! style="color:brown; background-color:#ffffee; width:500px;"| Functional requirement | |||
! style="color:brown; background-color:#ffffee; width:100px;"| Requirement code | |||
! style="color:brown; background-color:#ffffee; width:700px;"| Notes | |||
|- | |||
| style="padding:5px; width:500px;" |'''a.''' Enter your own unique requirement here | |||
| style="background-color:white; padding:5px;" | | | style="background-color:white; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | |
Revision as of 18:31, 17 September 2013
This is my sandbox, where I play with features and test MediaWiki code. If you wish to leave a comment for me, please see my discussion page instead. |
Sandbox begins below
|