The College of Engineering IT team manages most software installations to ensure secure, reliable, and well-supported computing for our community. This page explains what software is installed by IT, how to request new software, and when you can install applications yourself.

IT-Managed Software

COE IT installs and maintains standard engineering software for shared use across our systems, including:

  • 3D CAD tools

  • Computational fluid dynamics and modeling tools

  • Compilers and programming languages

Some software is simple to install, while others require customization and ongoing updates for security. All general-access software must be reviewed and approved by IT to confirm it can be supported.

Requesting Software for General Access

To be considered for installation across shared systems, software must:

  • Run on the current release of Red Hat Enterprise Linux or Windows

  • Support a network license model, or be free for research/instructional use

  • Support x86 architecture (ARM processor support is planned)

  • Be actively maintained and supported by the vendor or developer

  • Provide a clear benefit to multiple users

  • Be compatible with OSU/COE computing environments

Not supported: Software that requires its own dedicated website, database, or other permanent service

Lead time: Please allow at least 14 days for review and installation.

To request software installation, submit a ServiceNow ticket.

User-Installed Software on Unix Systems

You may install your own software when:

  • A custom installation location is supported

  • The software runs on the current release of Red Hat Enterprise Linux or in a containerized environment

Additional Considerations

  • Student licensed software will not be installed. These packages are only for use on personal devices owned by the student

  • Demo software installs need to be discussed with COE IT

  • Export-controlled or restricted software: Requires COE IT involvement

  • HPC systems: Not ideal for GUI-based or web front-end applications

  • Security best practices:

    • Verify the source of your software and its contributors

    • Be cautious with data sources to avoid “scientific phishing.”

Need Help?

If you’re not sure whether your software qualifies, or if you need assistance with installation:

Contact us at coe.support@oregonstate.edu.