CompressorScript is a Windows program

Use of the program requires the following:

1. The program installs locally, but requires an active internet connection to run. This is for licensing purposes only
2. The Ariel sizing program must be installed on the user's computer
3. Users must be adept at using the Ariel sizing program
4. Users need Excel and Word installed on their PC
5. Users must have a verified CompressorScript account for program access
6. The program login is always the user's Email address
7. The program subscription is for one user on one computer
8. The program is a valuable tool, but it does not replace user packaging expertise. The user should be familiar with compressor packaging

What the program does

1. Maintains a quote numbering/tracking system internally
2. Loads the information needed for packaging from the Ariel *.run file directly
3. For new runs, presents a selection for the package "Bias", for example Offshore-Onshore-High Spec-Low Spec
4. Creates an editable process design, for example, Piping, Bottles, PSV's, Scrubbers.. etc
5. Creates a pricing spreadsheet
6. Creates a proposal
7. The program produces its output quickly and efficently

Best Use

The program's best use is for quoting a wide variety of customer specified high-speed packages ranging in horsepower from 20 to 5000, electric motor driven, or gas engine driven

Ariel *.run Limitations

1. No compressor performance checks are made. For example, the program does not check rod load values against design limits. Checks like that are made completely within the Ariel program resources.
2. CompressorScript assumes the Ariel sizing conforms to Ariel requirements.
3. A Natural Gas, or Electric driver must be selected within the Ariel program.
4. Mulitple cases are evaluated with the program. If, for example, one case produces a 30" suction scrubber, and another case produces a 36" scrubber, the program will 3elect the 36" for sizing and pricing after analyzing all cases.
5. All cases must be consistent as to the total number of stages and services. For example, one case cannot be 4 stage, if another case is 3 stage.
6. If any case is "Blow-Thru" or has inconsistent stage/service arrangements between cases, program execution will halt. Some applications need a real human.