Understanding Copyright and Information Usage at AECOM – Siltalin8

Overview As a global leader in infrastructure, AECOM produces and consumes a vast amount of intellectual property. Protecting our firm and our clients means adhering to strict copyright laws and licensing agreements. This guide helps you navigate how to use, cite, and share information safely.

What is a "Notice of Copyright"? When you receive a notice from our team, it is typically an advisory regarding:

External Articles: Ensuring we aren't redistributing paid journal articles or standards internally without the correct license.
Image Usage: Confirming that photos or diagrams in client presentations are either owned by AECOM or properly licensed for commercial use.
Project Documentation: Guidelines on how to reference proprietary data from previous projects without breaching non-disclosure agreements (NDAs).

Your Compliance Checklist

Check the License: Before copying a technical standard into a report, check if our license allows for "External Distribution" or "Internal Use Only."
Attribute Correctly: Always credit the source. If you found a document through our library services, use the standard AECOM citation format.
Avoid "Copy-Paste" from the Web: Just because an image or article is on Google doesn't mean it’s free to use in a multi-million dollar bid.
Ask the Librarian: If you receive a "Copyright Notice" or a "Take-down Request," do not ignore it. Contact us immediately for a resolution.

Common Scenarios

"Can I share this PDF with a sub-consultant?" Generally, no. Most of our database subscriptions are for AECOM employees only. We can help you check the specific contract terms.
"I found a great diagram in an old project file." Ensure the previous client doesn't own the "Work Product." When in doubt, our team can help trace the ownership.

Librarian’s Note: Compliance isn't about being the "Information Police." It's about protecting the integrity of your hard work and AECOM’s reputation. If you’re unsure about a source, send it our way—we’d much rather vet it now than fix it later!