Skip to main content

Standardize the Platform, Not the Solution -- Assimilation is Futile

Many organizations are plagued by incompatible software solutions that proliferate in multiple departments.  These solutions are expensive to support because they may require different skills from developers and system administrators. The quality of data also suffers because records are updated in one department and not another. The result is a search for a single system that will rule them all.

If this sounds familiar, it is because the desire for a monolithic and comprehensive software solution is timeless and universal.    The problem is that this quest is futile, and has been shown repeatedly to fail by large and small organizations.

Politics is usually the reason that a universal solution fails, not technology.   Individual departments know their data much better than anyone else, and are justifiably reluctant to give up control.

Change is also the archenemy of the monolithic solution.  It takes time to document and implement requirements, and these business needs are subject to change.  A fast cycle for implementing changes is a valuable asset for any organization.

Does the quixotic nature of universal solutions mean that no standardization can succeed?  No, it turns out that some standards can help you save time in procurement, development, testing and training.  The most important standard is to set a technology platform to encourage compatible solutions for your departments.

The best items to standardize are:
  1. The database. The database is the heart of most solutions. Supporting multiple databases will drive up software and integration costs.  
  2. Workflow engine. If an enterprise can standardize on workflows across departments, many headaches are eliminated.
  3. Services layer for user interfaces. Multiple interfaces are required, especially for mobile apps, so a standardized approach will save time. The Model View Controller (MVC) architecture decouples the user interface from the data and business rules for better performance and flexibility.
This standardized approach will require less expensive integration efforts, allowing more resources to be spent on customizing the workflows and user experience for your unique business needs.

Popular posts from this blog

The DATA Act Driving Grant Management Automation

The Digital Accountability and Transparency Act enacted in May 2014 calls for making spending data available in open, standardized formats to be published online.  It is a continuation of transparency initiatives and lessons learned with experiences such as grants.gov, the 2009 economic stimulus under the Recovery Act and the spending site USASpending.gov.

Government grantees will have significant new administrative responsibilities.  Many organizations that were tracking grants in spreadsheets or documents will have to adopt more sophisticated automated grant management systems such as Microsoft Grants Manager to keep up with reporting rules.

For profit companies will lose some privacy as a result of this law.  Grant recipients will be required to disclose information including officer salaries.

Continued improvements to publishing grant opportunities such as grants.gov may make it easier to find grants. These reforms together are designed to improve the effectiveness of grant prog…

Key Concepts for Microsoft Dynamics 365: Entities and Attributes

To understand Microsoft Dynamics 365 (formerly Dynamics CRM and Dynamics 365 Customer Engagement), you need to learn some new terms and concepts that may be a bit different from what you know from databases and solutions that are hosted on premises. This is the second post in a series, and covers entities and attributes.

Entities are the most fundamental part of Dynamics 365 in terms of storing your business data.  They are similar in concept to database tables, and the relate to one another like tables in a relational database. For instance, Dynamics 365 has an entity called Contacts that stores data such as name, address, and email address of people that you track.   Accounts is a related entity that describes the organizations to which Contacts may belong.

Although they are similar to database tables, Dynamics entities allow you to do some customizations that are not possible in a standard database table.  Field labels, for instance, are part of an entity, and they may differ from …

Dynamics 365 for Auditing Activities

Many government and commercial organizations are responsible for conducting audits of financial and other performance in order to ensure compliance with regulations.

Microsoft Dynamics 365 offers a rich platform for automating auditing activities.  Here are some of the key functions that Dynamics 365 and Office 365 can perform for auditors:


Schedule visits. The Field Service app for Dynamics 365 includes a dispatcher console, and a module to assign auditors and schedule their visits or inspections.  It can also track other resources such as equipment which is used for field audits. Manage documents.  Dynamics 365 is integrated with SharePoint and also Azure Blob Storage.  This means that files may be associated with audit records, and searched using Microsoft search technologies which index full text and metadata. Generate notifications. Alerts via email or other communication channels (such as text messages) may be generated with Dynamics 365 automated workflows.  The messages are bas…