So am I talking about a SOA here?
For a government contract we will be proposing to build a traffic monitoring architecture.  We will have the following components:

 - Video camera's set up around the area of interest. The cameras will be aware of their location and orientation and viewing parameters.
 - A GIS map server which can be queried for streets, building, etc.
 - An algorithm the takes in raw video and street location information and outputs car locations.
 - Another algorithm takes in car locations and very low level street information and provides information about which cars are driving anomalously.
 - Another database takes in information about car locations and anomaly reports over time and  can be queried for this later.
 - A proxy (or perhaps more accurately, a facade) is set up over the archive database and the real-time algorithms in order to provide a unified interface to the information.
 - A client attaches to the proxy and to the street server and paints various representations of the traffic situation on the screen.

I'm just now learning what an SOA is.  Is this an ideal candidate of a Service Oriented Architecture SOA?  I had heard that SOA services should be stateless (or is that only RESTful services?)  I had also heard that it was inadvisable to pipe one service to the next to the next because it increases hidden complexity, and that there was something you should do to make this situation better (an "orchestration"?).  The services above do appear to be modular and reusable.  For instance, there will be plenty of cameras, various types of vehicle detection and anomaly algorithms, distributed databases, and plenty of clients.

If this isn't ideally implemented by a SOA, then where else should I be looking.  If this is ideal for a SOA, then where should I start when designing this? (And I'm starting basically from having read Wikipedia's SOA page.)
So am I talking about a SOA here?
===

For a government contract we will be proposing to build a traffic monitoring architecture.  We will have the following components:

 - Video camera's set up around the area of interest. The cameras will be aware of their location and orientation and viewing parameters.
 - A GIS map server which can be queried for streets, building, etc.
 - An algorithm the takes in raw video and street location information and outputs car locations.
 - Another algorithm takes in car locations and very low level street information and provides information about which cars are driving anomalously.
 - Another database takes in information about car locations and anomaly reports over time and  can be queried for this later.
 - A proxy (or perhaps more accurately, a facade) is set up over the archive database and the real-time algorithms in order to provide a unified interface to the information.
 - A client attaches to the proxy and to the street server and paints various representations of the traffic situation on the screen.

I'm just now learning what an SOA is.  Is this an ideal candidate of a Service Oriented Architecture SOA?  I had heard that SOA services should be stateless (or is that only RESTful services?)  I had also heard that it was inadvisable to pipe one service to the next to the next because it increases hidden complexity, and that there was something you should do to make this situation better (an "orchestration"?).  The services above do appear to be modular and reusable.  For instance, there will be plenty of cameras, various types of vehicle detection and anomaly algorithms, distributed databases, and plenty of clients.

If this isn't ideally implemented by a SOA, then where else should I be looking.  If this is ideal for a SOA, then where should I start when designing this? (And I'm starting basically from having read Wikipedia's SOA page.)