Loading...
 



Government procurement is a major marketplace.

Worldwide it accounts for around 12% of the global GDP.
This huge size calls for a transparent, fair and accessible tendering system.




Open source business model is inherently different from proprietary

1. Open source licenses are not negotiable


Open source belongs to an individual but all those contibutors who added their parts. Therfore its impossible to grant licnese rights to any agency without asking permissions from all.


2. Proprietary and open source's subscription cost entails different things


The subscription cost for proprietary software includes license cost and after support services. The subscription cost for open source software incldues "code support and maintenance, security updates, error correction, and patch updates. Where it differs from a proprietary support agreement is that it includes new features and new version releases. In the proprietary model new features are only available if license fees are paid. In either case it's worth purchasing support as this delivers transparent business value."


3. Open source providers can't provide contractual indemnity


"Procurement rules usually ask for substantial penalties to be associated with promises that the software doesn’t contain any misappropriated copyright, abuses no trademarks, and does not knowingly infringe any patents. The reason you need contractual indemnity when you procure proprietary software is you have no other way to attempt to protect yourself against careless or malicious infringement of the rights you or others can reasonably expect to be protected."





We believe that promoting Open Source can incite innovation, growth and business opportunities

Help us and get involved by joining our Community




We Recommend

1. Divide the Procurement System into two parallel processes

Divide the Procurement System into two parallel processes; one for open source software and the other for proprietary solutions. The selection criteria will naturally vary for both solutions depending on the type of license, support available etc.

source : opensource.com


2. Use Score or Qualitative Value

Place a Score or Qualitative Value "on issues such as vendor lock-in, exit costs, speed of the development and release process, number of contributing coders/companies in relation to your risk exposure, ability to keep the code and support of interoperability standards. These are valuable attributes often over-looked by the purchaser.”

source : opensource.com


3. Consider Total Cost of Ownership

Total Cost of Ownership should be taken into account before in preferring one solution over the other. TCO includes cost of: servers, storage to run the software, implementing, configuring and running the software, data migration, license, any customization required, upgrade and patches and training.


4. Best Value for Money as an optimum choice

Best Value for Money “shall be understood as the optimization of the total cost of ownership and quality needed to meet the user’s requirements, while taking into consideration potential risk factors and resources available. The Best Value for Money solution may not necessarily offer the lowest cost.” This could be best done by ensuring “that all costs are considered within the total cost of ownership, including transportation costs, installation costs, operating costs, maintenance costs, disposal costs, etc.”

Source: United nations procurement manual 2020 REF. NO.: DOS/2020.9 30 JUNE 2020


5. Retirement Cost

Retirement Cost is the one which agencies incur once the project is retired or finished. They still need to have the system running for several years 1) for reference 2) for compliance and 3) it has all the data which is yet to be migrated to the new system. This automatically reduces TCO less for the legacy system.

Source: /www.cio.com

Gary's feedback:

  • The meaning of the page name is ambiguous. Seeing it in the menu, we don't know if it means cause as in "cause and effect" or cause as in "a social cause". When we see the page itself, the meaning of "a social cause" seems to be the right one, but the reason for the page name still isn't clear, IMO.
  • I'm not too keen on the photograph. I don't think an image of people demonstrating in the street sets the right tone, really. Also the photo should go the full page width if it's a static image; maybe the idea is to have a carousel here. And the text needs better positioning over the image (more centered vertically).
  • I'll leave it to the Open Source marketing experts to evaluate the page content, but one thing I can say is that HTML headings should not be used just to make large text. Headings are semantic page section markers that should be used in a logical hierarchy and be used to introduce text and other content. Non-heading text can be made large by giving it a "font-size: 2.5rem" property, for example, or a Bootstrap display class as is used in other parts of the page.
  • I'm thinking it might not be a good idea to have links leading away from the site at the middle and bottom of the page. Maybe better, have the "Join us' button at the bottom (either only there or repeated from the top), to give the visitor a call to action that involves the site rather than links to other sites.

Edit this section and replace the brackets and the text they contain with the actual information for the page
Page description* [Short sentence between 130 and 170 characters that tells what the page is about, such as seen in search engine results.]
Main audience [Should be selected from the list of all planned-for site visitors/visitor categories.]
Very brief content outline:

[For example:

  • Main point(s) of the page
    • Information A supporting the main point(s), etc.
    • Information B supporting the main point(s), etc.

(so if something isn't covered by this outline, maybe it doesn't belong on this page).]

Call to action (CTA) [What call to action or other decisive step does the page visitor take to indicate the visit was a success from the standpoint of the website? (For example: Register for an event, navigate to a linked-to page, download an information package, etc.]
Search intent (reference)* [The user's motivation for/purpose of the search that leads to this page. ]
Keywords* [Words (single words and short multiple-word terms) that indicate the content of this page, which are also the terms that people enter in search engines to find this page. ]
Design notes [Any details about the page design as it contributes to communicating the page's message.]

  • This form is to help focus the selection of information to be presented on this page, and to help demonstrate how this page fits into the overall information hierarchy of the website.
  • Some of the items here, as indicated by an asterisk(*), can be used by the live site for SEO purposes.
  • When the website goes live, this box can be displayed to site admins/editors only, or removed if no longer needed.