Orsatmax

User Tools

Site Tools

Trace:
start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
start [2025/12/24 17:16]
172.71.167.124 old revision restored (2025/09/24 03:21) 		start [2026/01/14 21:32] (current)
172.69.65.175 old revision restored (2025/10/16 04:02)
Line 27: Line 27:
 The output format for data generated by the analytical data system must adhere to a specific ASCII text format to enable MAX to be able to correctly interpret and store the data.  Orsat has generated output formats for both the Totalchrom and EZChrom data systems.  The user will not only need this format for the output but will need their analytical method to adhere to specific requirements such as target names, response factor format and calibration units.  Orsat can assist by supplying methods for each analytical and help the user to implement any necessary changes that might be required.  The output format for data generated by the analytical data system must adhere to a specific ASCII text format to enable MAX to be able to correctly interpret and store the data.  Orsat has generated output formats for both the Totalchrom and EZChrom data systems.  The user will not only need this format for the output but will need their analytical method to adhere to specific requirements such as target names, response factor format and calibration units.  Orsat can assist by supplying methods for each analytical and help the user to implement any necessary changes that might be required. 
    
 +  **Required Input from Analytical System**
 +
     * Instrument Name - (Format "SITE-//x//")     * Instrument Name - (Format "SITE-//x//")
     * Filename - specific format (see File Naming)     * Filename - specific format (see File Naming)
Line 43: Line 45:
 MAX was designed to identify the QC control samples by using a specific file naming paradigm.  Thus filenames must be specific to the sample type.  Filenames are generated using a sequence generator which assigns filenames and schedules the necessary QC samples in the analytical system.  This requires specific automation not generally provided as part of the original manufacturers product.  Orsat offers the necessary hardware and software to generate not only the sequences with descriptive filenames but also the hardware to automate the introduction of the necessary QC samples for both the PerkinElmer and Agilent systems. MAX was designed to identify the QC control samples by using a specific file naming paradigm.  Thus filenames must be specific to the sample type.  Filenames are generated using a sequence generator which assigns filenames and schedules the necessary QC samples in the analytical system.  This requires specific automation not generally provided as part of the original manufacturers product.  Orsat offers the necessary hardware and software to generate not only the sequences with descriptive filenames but also the hardware to automate the introduction of the necessary QC samples for both the PerkinElmer and Agilent systems.
  
-//FilenameStructure 1.png +Filename structure.png
-FIlenameStructure 2.png//+
  
-    +      
  
  
Line 61: Line 62:
   - Total Blank Maximum value   - Total Blank Maximum value
   - List of Target Compounds by Channel   - List of Target Compounds by Channel
-  - List of Target Compounds in each of the required QC samples (LCS, CVS, RTS, Blank and MDL) including required control limits+  - List of Target Compounds in each of the required QC samples (LCS, CVS, RTS, Blank and MDL by channel including required limits or thresholds
   - List of applicable Null, Qualifier and Inform Flags available for use in AQS files.   - List of applicable Null, Qualifier and Inform Flags available for use in AQS files.
  
-Each Site also has unique information to identify it in the database.  In addition to a unique site name other information is required to generate a site-specific AQS data file which will be submitted to the EPA AQS Database.+Each Site also has unique information to identify it in the database.  In addition to a  specific 
  
 === Information Required for Site Configuration === === Information Required for Site Configuration ===
Line 81: Line 82:
   - CAMS code (if available)   - CAMS code (if available)
   - Interval, units code and method codes required for AQS file generation    - Interval, units code and method codes required for AQS file generation 
- 
-==== Site Permissions ==== 
-MAX allows for user-defined permissions for each user based on the users role.  These roles define the activities available to that user.  Users can be designated as Administrators, Validators, Operators or Guests.  Each designated role provides different levels of permissions. 
-=== Roles === 
-  * **Guest** - viewing access only, no access to raw TX0 data, Screening tools, Generation of CSV output, AQS Files. 
-  * **Operators** - Same as Guest. Additional access to view TX0 data, generate CSV output and the ability to add or edit Certificates of Analysis, QA/QC table updates, and Site Information 
-  * Validators - Same as Operators with added ability to add or edit all features.  Limited ability to delete items in the AQS List, Sample Types, Networks, TX0 data and Sites. 
-  * Admin - full access to all functions 
- 
-  
- 
  
  
start.1766596592.txt.gz · Last modified: 2025/12/24 17:16 by 172.71.167.124

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki