Thank you both so much! Truly appreciate the "2 cents". First plan is to look into the colocation. We actually have an idea of amount of slippage, so no worries there. And yes, no need to compete with HFTs, just need to get filled at specific prices 



We have run into major slippage issues, and the system is running on SPY. All orders are placed via ARCA and BATS, 500-1000 share lots. We want to receive the rebates for providing liquidity, or at the very least, not be charged for removing liquidity.
You're talking about slippage experienced while adding liquidity in a .05%-spread security that trades massive volume. I think that such slippage is inevitable, unless you're one of three parties: 1) a broker/dealer with lots of customer orders to internalize (trade against); 2) a "wholesaler" with enough scale to get a deal to buy customer order flow; or 3) an HFT with a large budget and the know-how to colocate at all the relevant exchanges; in the case of SPY, that also means including the CME at Aurora, IL and the relevant NY-Chicago link.
You can mitigate this somewhat, but nowhere near entirely, by following some of the latency-reducing advice that's already been given.
Unfortunately, the market is not as straightforward as the NBBO would seem to indicate. It is fragmented, and routing decisions are driven largely by brokers who often put their own interests above the interests of their customers. The HFT and wholesaler business models are very expensive, and that expense shows up in the slippage paid by all the rest of us.
On top of that, you also need to consider complex order types, and both how you use them and how other people are using them.
If the slippage overwhelms your strategy's profit, you might consider whether it's still profitable when taking liquidity instead.
