Airports & Ground Transit Addendum
Sector-specific terms for airport, seaport, rail, bus, and ground-transit operators. Attaches to and modifies the MSA where the deploying Authority operates a transportation facility.
1. Applicable regulatory regime
Deployments in U.S. airports are subject to Transportation Security Administration ("TSA") regulations and, where the Coverage Area falls within the airside operational area or within an airport operations area, to Federal Aviation Administration ("FAA") regulations. Rail deployments are subject to Federal Railroad Administration ("FRA") regulations. Public-transit deployments are subject to Federal Transit Administration ("FTA") requirements. International deployments are subject to ICAO Annex 17 (aviation) and IMO ISPS Code (maritime) as applicable, together with the requirements of the local aviation or maritime authority.
2. Complementary, not substitute, screening
The Platform is deployed as a complement to the primary screening operation, not as a substitute for TSA, contract-security, or airport-authority screening. Notifications are advisory to the Authority's security operators; response to a Notification is subject to the Authority's Security Program.
3. TSA and airport-authority coordination
The Authority is responsible for coordinating with the TSA Federal Security Director and, where applicable, with the airport authority security office regarding deployment of the Platform in areas adjacent to or interacting with primary screening. WCE shall reasonably assist in that coordination and will provide the categorical Capability Statement to the coordinating authorities under NDA.
4. Sensitive Security Information
Materials designated Sensitive Security Information ("SSI") under 49 C.F.R. Part 1520 shall be handled by both Parties in accordance with that Part. WCE shall not receive SSI unless expressly required for the Purpose; where received, SSI shall be marked, handled, and destroyed as required.
5. Airside restrictions
Deployment of Edge Devices within an airport airside area requires the prior written approval of the airport authority and, where required, of the FAA. WCE will not install airside Edge Devices without that approval.
6. Passenger flow and non-discrimination
Deployment shall not create a bottleneck that materially impairs the flow of passengers, and shall not be operated in a manner that produces Notifications correlated with a Protected Characteristic (see the AUP). Where the Authority publishes performance data derived from the Platform, that data shall be reported at a categorical level, without disaggregation that would permit inference of proprietary methods or of Protected Characteristics.
7. Chain-of-Custody for interdictions
Where a Notification precedes an interdiction, the Authority is responsible for maintaining its own record of the interdiction; the WCE Chain-of-Custody Record documents only the Notification itself. Where custodian testimony is required, WCE will provide it consistent with the Chain-of-Custody Rider.
8. Data-flow to law enforcement
Sharing of Notifications with airport police, TSA, or federal law-enforcement partners shall be through the Authority as Controller under its DPA, and shall be consistent with applicable law. WCE shall not disclose Notifications to law enforcement absent Authority direction or valid legal process.
9. Multi-modal deployments
Where a deployment spans aviation, rail, or maritime modes on a common campus, each mode's regulatory regime applies within its jurisdiction, and the Order Form shall identify the responsible authority for each Coverage Area.
10. Order of precedence
In the event of a conflict with the body of the MSA, this Addendum governs to the extent required by aviation, maritime, or surface-transit regulation.
This Addendum attaches to the MSA and is effective concurrently with it.