AT-engine ready

I think, it is wrong in OAT application to wait for basic at-ready indication (+WIND:3). ADL part of application already checks at state before starting main application function and issue some at-commands. More of this, +WIND:3 actually pass before application startup and can’t be detected.
So if i want to perform some basic setup (without any SIM-based commands), no need for me to wait, commands can be sended at any time.
Am i right?

At the time of performing some basic setup i guess you need not wait for the the +wind:3 indication in your application.In fact it would be better if you wait for the +wind:4 indication that suggests that the product is ready to process all AT commands.