15 second delay in Initial setup of enforcer is confusing for users

The enforcer now gracefully copes with no DB and no zones, however there does seem to be a 15 second delay during initial set up from a clean system:

Dec 6 14:06:18 sara-ods ods-enforcerd: [engine] enforcer started
Dec 6 14:06:18 sara-ods ods-enforcerd: SQLITE3: no such table: Policy (1)
Dec 6 14:06:18 sara-ods ods-enforcerd: expected to be able to select from table: Policy
Dec 6 14:06:18 sara-ods ods-enforcerd: [autostart_cmd] Database is not set up yet. Not scheduling tasks.
Dec 6 14:06:18 sara-ods ods-enforcerd: [autostart_cmd] Run the 'ods-enforcer setup' command to create the database.
Dec 6 14:06:21 sara-ods ods-enforcerd: [enforce_task] unable to determine next schedule time
Dec 6 14:06:21 sara-ods ods-enforcerd: [enforce_task] retrying in 30 minutes
Dec 6 14:06:21 sara-ods ods-enforcerd: kasp loaded from /home/sara/jenkins/2.0_s/workspace/root/local-test/etc/opendnssec/kasp.xml
Dec 6 14:06:21 sara-ods ods-enforcerd: policy default found
Dec 6 14:06:21 sara-ods ods-enforcerd: kasp update complete
Dec 6 14:06:21 sara-ods ods-enforcerd: SoftHSM: C_GenerateKeyPair: Key pair generated
Dec 6 14:06:21 sara-ods ods-enforcerd: SoftHSM: C_GenerateKeyPair: Key pair generated
Dec 6 14:06:21 sara-ods ods-enforcerd: [enforce_task] transaction not started
Dec 6 14:06:21 sara-ods ods-enforcerd: [enforce_task] retrying in 15 seconds
Dec 6 14:06:36 sara-ods ods-enforcerd: [enforcer] update Zone: ods
Dec 6 14:06:36 sara-ods ods-enforcerd: Could not call signer engine

it would be nice if we could streamline this a bit for the initial setup.