Those of you who read my blog closely may have noticed that I have edited yesterday's post on Bibliocommons. I wrote that post at the San Francisco Airport at 6AM, and when I went back and read it after a good night's sleep I did not feel comfortable with my comments about the relationship between Bibliocommons and Innovative Interfaces, particularly since PVLD has not yet formalized a relationship with Bibliocommons and has not had any direct discussions with Innovative about our potential use of Bibliocommons...although I'm hopeful that both of these activities are not too far off!
I also realized that what really has been bugging me is not whether two particular pieces of software will work together, but what I see as a growing gap between an old business model and a new one. The old one was the model of proprietary and closed systems. In my personal experience it was best exemplified by my very first major software implementation project - the implementation of the SAP integrated business system into an aluminum smelting business in Australia back in the late 80s and early 90s. The SAP system had its roots in what used to be called "mainframe computing" and was intended to provide an integrated automated solution for all of a corporation’s business processes from manufacturing and inventory control to accounting to human resources....
The idea was that you would purchase this monolithic software from the vendor, and if it didn't quite meet your needs in a particular business area you would either modfiy the software yourself (which had both short and long-term cost and maintenance implications) or work with the vendor and other users of the software to have modfications included into a later release of the software (which could take a long time). Where customers demanded new functionality the vendor would develop and sell additional modules. The software resided on computers owned by the customer. Proprietary software code and standards made it difficult if not impossible to purchase a different product for a particular business need and integrate it into the overall system architecture, and the sizeable investment in the software and implementation made changing to a different product very costly.
The advantages to this model include the tight integration of data and work flows across and between business processes, the ease of maintenance afforded by dealing with a single product from a single vendor, and the control afforded by having the software and data residing on your computers.
The disadvantages include lack of flexibility to meet specific, unique, or changing business needs, relatively slow development timetables, and the sizable investment of time and money required to implement such a system (including the need to invest in the hardware infrastructure).
This model worked pretty well in the 20th century, but the world has changed. Some of the things that are becoming “standard” include – hosted software where the software resides on servers owned by the software/service provider and is made available via the web; “open source” software that is typically free and for which applications and new functionality are developed by and shared within the user community (PVLD is using open source software for our staff Intranet and new website; and “open application interfaces” which allow anyone to create new applications to add on to existing services (an example is all of the little add-ons for Facebook). In this environment organizations pick and choose the “best of breed” applications that best meet their business needs, and expect that those applications will work together…and they expect to be able to get these at a reasonable cost, or even for free!
The worry that has been at the back of my mind for some time is that major Integrated Library Systems were developed under the old model. While there are some moves towards developing new open source ILS solutions, and while some vendors have been more willing than others to enable their core products to work with other 3rd party solutions, the most common ILS products are built on the old, monolithic model…and the Innovative Interfaces business model seems to be more wedded to this old model than many others. Where changing expectations have led to demands for new functionality - like "federated search" or a more "social" catalog" - the response has been to develop these products in-house, and make it difficult for customers to integrate products from other vendors with the core ILS offerings. These ILS vendor-developed offerings are often expensive, and not often the best or most innovative solutions available.
This is going to be a challenge for PVLD as we strive to get better and faster at modifying our service offerings to meet changing customer applications. We want to be able to quickly and easily implement new service models like those offered by Bibliocommons, Aquabrowser, LibraryThing and others…and to easily integrate these with our ILS and each other. I hope Innovative understands this need and will work with us. If not, I fear for their long-term future…..
Recent Comments