A Closer Look at Open Platforms

A Closer Look at Open Platforms

By Jeane Chen

Open source, open platform, open technology. With so many variations of the word, how are associations and not-for-profits supposed to understand? This article provides an overview of the various terms, what they mean, and what it means for associations and not-for-profits.

According to the Open Source Initiative (OSI), a California public benefit corporation with 501(c)3 status and the community-recognized body for reviewing and approving licenses as OSD-conformant, open source is "a development method for software that harnesses the power of distributed peer review and transparency of process." The OSI, which maintains the definition of open source for the community, contends that, in order to be open source, not only must the source code be openly available, but it must also be free to redistribute.

An open platform, as defined by Wikipedia, is a way to describe a software system that has published external programming interfaces. External programming interfaces are often called Application Programming Interfaces, or APIs. The published APIs enable a third-party to integrate with the software system. Many vendors have created open platforms with APIs to allow third-party integrations with the software and to also enable developers to add features and functionality to the system. Open platforms provide two main benefits-the ability to develop unique functionality and combat data silos.

Another term often used is "open technology." The term is extremely general and can be used to refer to open platforms, open source, or a combination of the two. Usually, after further reading, the true essence of the open technology will be revealed. Companies offering open source or an open platform may refer to open technology, but will divulge whether it is open source or an open platform. The main difference between open source and open technology is the availability of the source code and its free distribution, while an open platform provides the programming interface but not necessarily the code.

As constituents continue to demand more integration between various technologies, the number of software providers with open platforms has increased exponentially. This transformation was driven by the desire of organizations to combat data silos and create the cohesive experience that constituents have come to expect. For example, in the consumer arena, technology providers have joined forces to provide Internet access from mobile phones.

Generally, there is no single application that meets all the needs of an association or not-for-profit. Oftentimes, programs are specialized to meet a particular need. Accounting applications are chosen to manage money in and out of the organization. Website management solutions are used to design and maintain the organization's online presence. Another system may be used to track donations received through direct mail campaigns or personal appeals. This level of distinction isn't likely to change drastically in the near future. As the technology industry has matured, technology vendors and companies have focused their products for unique markets or to address specific needs.

Because open platforms enable software developers to add functionality or features, associations and other not-for-profits will be able to adjust and/or modify their existing software solutions to better meet their requirements. To illustrate, consider a common application like Microsoft Excel. Many avid and experienced users of Excel are familiar with the application's limitations. While it can do a lot, it can't do everything; there are times when all of us have thought "if it could only" or "if I could just." If Microsoft had an open platform, developers could view the APIs and add the functionality to address their "if it could only" concerns.

Adding features and functionality are not the only benefits of open platforms. Open platforms also help associations and not-for-profits combat data silos. Many organizations have data stored in multiple applications, within certain departments, or even with particular individuals. When member or donor information is spread throughout various departments, organizations cannot get a complete understanding of a constituent's relationship with the organization. In some not-for-profits, for example, those who donate online are often stored in one application, while those who send a check can be kept in another system. It is not uncommon for some donors to donate both online and offline. Having this type of information stored separately can lead the organization to misinterpret the true affinity or commitment of the donor. APIs, because they enable third-party integrations, help decrease this challenge.

Open platforms can unlock the door to solutions that better meet organizational needs. They enable the development of additional functionality and features and can effectively combat data silos.

 





Jeane Chen is executive vice president of engineering for Blackbaud, Kintera division, 9605 Scranton Rd., Suite 240, San Diego, CA 92121; 858-795-3000; www.blackbaud.com/is.