Libre Services: From concept to reality

Figure 3: From concept to reality

 

Figure 3 provides an overview of the major stages of development needed to establish Libre Services as a reality, and the principal deliverables needed at each stage. The major requirements are:

• Conceptual definition. The first requirement is a clear definition and explication of the concept. The necessary intellectual work must be done to define the concept fully, and written materials created to communicate it to others.

  The principal required deliverable is the Libre Services Manifesto, a comprehensive description of the Libre Services model.

• Collaborative framework. The next requirement is a framework for collaborative engineering development. Open-source software development does not take place in a vacuum--it requires a proper framework to proceed effectively. This framework must include a central software repository, and automated mechanisms to allow developers to retrieve software components from the repository, then resubmit modified software back into the repository. The framework must also define the policies and procedures to be followed for orderly collaboration, and provide various other resources for developers.

  The required deliverable is LibreServices.org, a website and forum providing all the necessary resources and functionality.

• Engineering development. Next it is necessary to do the engineering work to create Libre Services software. This is done by the open-source development community within the industry at large.

  The required deliverables are a set of software components and Libre Service Engines.

• Deployment and delivery. Finally it is necessary to deploy and deliver services to individual subscribers. This is done by service providers within the industry at large.

  The required deliverables are a set of deployed, usable, first-generation Libre Services.

Transformation of software into services

Figure 4: Transformation of free software into Libre Services

 

Figure 4 provides an overview of the technical processes required to transform free software components into a working service for delivery to users.

In addition to free software components, two other important elements are required to create a service: an integration portal, and LSIP. These three elements are integrated together to create a Libre Service Engine.

The Libre Service Engine is a key technological component of the Libre Services model. It is a complete, fully integrated package of service features and capabilities, ready for deployment and delivery by a service provider. It is part of the definition of a Libre Service that such an engine exist, ready for deployment without requiring any further software integration work.

It is the responsibility of a service provider to create a deployed service based on the service engine. This includes binding the service to a specific Internet domain, branding the service with the provider's trade name, and providing the technical and business structures required to deliver the service and support users.

The vertical line in Figure 4 represents an important conceptual point of demarcation in the Libre Services model. It is the division between industry-general engineering activity, and provider-specific deployment activity. Engineering development is a collective activity, undertaken by the industry as a whole. The resulting assets are industry-generic, available for use by all industry participants. Deployment and delivery, on the other hand, is undertaken by a commercial or non-commercial service provider. The resulting deployed service is associated with and carries the brand name of a specific provider.

Thus LSIP and all service engines are industry-generic resources. ByName, a deployed service, is associated with a specific service provider, in this case Neda.

In the Libre Services model any engineering development, taking place at any point within the industry, becomes immediately available to the entire industry. This means that differentiation and competition among service providers no longer takes place on the basis of service functionality. Instead it must now take place purely on the basis of deployment and delivery characteristics such as service cost, reliability, and customer service.