We Are Not The World: Database Design II
First step in designing the architecture for your proposal databases is to understand where you are in the eco-system of data. Proposal data and CRM is pretty far downstream.
Though our purpose is critical to the survival of the organization, our data needs are second or third tier. You see, others dictate the requirements for the upstream databases. Payroll and accounting must satisfy the appetite of regulators at the SEC and agencies like the IRS. Sarbanes Oxley is keeping your CFO up at night, so stay out of their way.
Second, our data needs are historical not real time. HR, payroll and accounts payable must be realtime. A week or month delay in relaying data to your system is not really a problem.
So, do not try to change the existing database environment in other departments to suit your new database nor software. This is unnecessary.
Document the systems in use, and ask whether they anticipate any major changes in their system. Keep your plug-in points simple. Don’t plan any upstream data change.
Reader (RSS)
Email