Sample Environment - How to Create a Knowledge Network Using Drupal

Transcription

1 Request for Proposals Drupal - Knowledge Network Commission for Environmental Cooperation

2 RFP - Knowledge Network 1.0 Background The Commission for Environmental Cooperation (CEC) is an international organization created by Canada, Mexico and the United States under the North American Agreement on Environmental Cooperation (NAAEC). The CEC was established to address regional environmental concerns, help prevent potential trade and environmental conflicts, and to promote the effective enforcement of environmental law. The Agreement complements the environmental provisions of the North American Free Trade Agreement (NAFTA). The proposed CEC Knowledge Network is part of an ongoing process to utilize the web for publishing purposes. 1.1 Objective of the Project The main objective of the CEC Knowledge Network is to create an infrastructure that will allow us to publish content from our publications and other program deliverables outside of the book publication model, where we can create linkages between CEC program work and make content from this work shareable among our own sites and those interested in our work. An important outcome of the project is to create a framework where sites can be created and added to the network by CEC staff, without relying on a third-party vendor. 1.2 Rationale for the Project The CEC has published many documents over the course of its life, and these usually have taken the form of reports, books and other publications. There has also been the creation and/or maintenance of multiple datasets that exist either on their own or in conjunction with a publication. The publishing model has largely been to create PDFs of the documents and uploading them on to the website, where they sit until someone downloads them. There have been some moves to make information more accessible through such initiatives as the North American Environmental Atlas and the Taking Stock database of searchable PRTR data. This project will take the information out of static book-style publications and make them consumable over the Web using a flexible technical infrastructure where adding sites and sharing content between sites is done quickly and easily. 2.0 Tasks and Expected Output and Deliverables The project has four identified tasks, which will result in a final deliverable of a scalable website infrastructure, with identified content areas, templates and themes. Descriptions of the tasks follow: Task 1: Technical Framework This task is to create a technical framework for the Knowledge Network. Drupal has been identified as the system most suitable for this project. However, the system would need to communicate with some Windows-based applications that the CEC has in production (Website CMS, searchable databases, etc) See Task 1A for more on this. Much of the discussion in this task is based on the following high level site map: 2

3 Note: This is all theoretical and meant for discussion purposes only and does not match any defined sites or content inside of these sites. The home page at the top is the main knowledge network home page, which will contain content mostly pulled from sub sites The three sample sites (NAMPAN, Data, Taking Stock) are sub sites that are selfcontained but still are related to each other in that they can share sections or content with other sites or the Network home. In this map, the Species section of the NAMPAN site is shared with the Network home page, as is the Monarch page. An example of content that can be shared between sub sites is Power Plant Emission data, which can be shared between the Data website and the Power Plant Emissions area of the Taking Stock website. The emphasis is on granular content that can be shared. Task 1A: Integration with Windows Applications The CEC has in production two Windows applications that will need to have some interaction with the Knowledge Network. One is a searchable database of Pollutant Release and Transfer (PRTR) data. The other is the content management system for our corporate website. For the PRTR database in particular, there is a need to explore whether technical integration is required or just a re-skinning of the interface. This task is to identify how the Drupal system will work with our Windows applications and implement that solution. The applications are run using Windows Server 2003 and SQL Server 2005, both Standard Edition. Task 2: Library of Themes and Modules As previously mentioned, an expected outcome of this project is the ability for CEC staff to add sites and content without the need for third-party assistance. To achieve this, a series of themes need to be created with CEC branding, which can be selected when adding a site to the network. The first part of this task is to create a series of three-to five themes that we can work with that can act as the skins for the network. There is a need to present the CEC brand with a bold visual design. 3

4 The second part of this task is, once the macro requirements are identified, to create or configure and make available in the system, a series of approved modules that CEC staff have the option to include on an individual site. Task 3: Content Disaggregation and Taxonomy Creating a series of sites can have the potential to be messy if rules are not built into the system about how content is constructed and managed. Without knowing the structure of content chunks, they are difficult to share. Going hand-in-hand with the technical framework and theme development, this task focuses on developing rules for such things as content granularity and defining the levels of content disaggregation, rules for tagging (creating taxonomy), etc. The expected outcome will be a documented system for creating and editing content that can be built into the technical framework. Task 4: Guidebook for future sites This task is to create a guidebook for CEC staff to reference when creating sites or adding content. It will describe: The expected structure of the content (Task 3) How to add a site How to add or change a theme How to update Drupal How to work with modules How to push content onto multiple sites in the network A basic primer on how to use Drupal 3.0 Mandatory Requirements The system, including all modules, must be fully trilingual. The back-end administrative interface can be English only, but anything public-facing must be trilingual. All included modules must be as future-proofed as possible. The system must contain modules to manage video, flash, and other related media. 4.0 Proposal Submission Proposals should include the following: A description of your company s experience developing websites with Drupal, including several examples. A description of your company s visual design experience, including examples. If you work with another company or sub-contractor for these purposes, please include several samples from them. A description of your company s approach to project development using Drupal, with emphasis on the tasks indicated in this RFP. A description of your company s policies on updating Drupal, how your company approaches updating the system, including your policy on updating modules that conflict with Drupal updates. Suggested modifications, if any, to the Knowledge Network project, and the reasons for such modifications. Résumés of Key Personnel who would be involved in the project, including subcontractors or third-party vendors, if applicable. 4

5 Availability of Key Personnel Three (3) reference contacts. Detailed cost breakdown, including labour costs of Key Personnel and other personnel, direct and indirect costs, travel costs and applicable taxes; and Description of any other relevant experience. Potential consultants are encouraged to submit any additional information that they believe will assist the CEC Secretariat in the evaluation of their proposal. However, the proposal should not exceed 12 pages. (This 12-page limit does not include CVs of individuals or corporate brochures.) 5.0. Type of Contract to be Used for These Services The CEC Secretariat intends to use its standard time-based contract for these services. A sample is available upon request. If the contract is negotiated with a consortium, the CEC will offer the consultants the option to have separate contracts between each consultant and the CEC. All work within the contract must be completed by end of December Selection Procedure to be Used The Consultant will be selected in accordance with the CEC Consultant Services Procurement Manual (Provisional, October 1996), Section 2.3: Basis of Selecting Consultants. Proposals that the CEC Secretariat determines to be complete will be evaluated according to the procedure described here. Prospective consultants who submit proposals determined by the CEC Secretariat to be incomplete will be so notified in writing. Each complete proposal that is submitted will be evaluated by the CEC Secretariat according to the following criteria, with a point rating assigned for each: Evaluation Criteria Maximum Point Rating Understanding of project requirements, adequacy of proposal 30 Experience, qualifications and competence 30 Quality of previous work 25 Cost 15 Total 100 A minimum score of 80 will be required for the prospective consultant's proposal to be eligible for further consideration. Prospective consultants whose proposals score less than 80 will be so notified in writing, together with the reasons for the score. Cost efficiency and value-for-money will be taken into account in evaluating proposals. The proposals will be evaluated in accordance with the CEC Consultant Services Procurement Manual, Appendix B "Proposal Evaluation Criteria and Consultant Selection Process: Guidelines and Standard Evaluation Format" available through the CEC web site < A summary of the process is given below. Proposals in response to this request will be evaluated by the CEC Manager of Information Services, Communications Manager and Program Manager for Environmental Information. Each 5

6 member of the Evaluation Committee shall receive a copy of the proposals and will be asked to rate each proposal using the evaluation criteria and maximum point ratings given above. The CEC Program Manager will arrange for meeting among the members of the Evaluation Committee to discuss the ratings, arrive at final scores, and, subsequently, a ranking of all proposals. The strengths and weaknesses of each proposal, in terms of the evaluation criteria, will be noted and summarized and a shortlist will be created. We will then arrange for a meeting/conference call with each of the shortlisted proposals. Feedback will be provided to each prospective consultant once the selection has been made. The prospective consultant s ranking will be provided to them if requested, however, neither the evaluations nor the scores of other bidders will be provided. 7.0 Estimated Level of Resources Required The Consultant may prepare the estimate in either C$, P$ or US$. If a currency other than US$ is used, the Consultant should indicate the total cost of the professional services in US$ as well as the currency of choice, for comparison purposes. 8.0 Basis of Payment Required Payment shall be made only for bona fide consultant fees and legitimate expenses incurred in accordance with the contract for professional services, and only upon receipt and documented acceptance by the Secretariat of statement(s) of account/invoice(s) from the Consultant. Settlement of invoices that are acceptable for payment will normally be made 30 days from the date of receipt by the Commission. 9.0 Financial and Other Confidential Information For this proposal, the CEC Secretariat will not require the submission of any confidential information nor will the CEC Secretariat require information regarding insurance, financial status, or company ownership Deadlines for Proposal Submission and Decision The proposal, including all relevant attachments, must be received by the CEC Secretariat offices by 17:00 on Friday, February 5, Proposals submitted after this deadline will not be considered. Proposals must be submitted via electronic mail to kpowell@cec.org. Proposal format may be in Microsoft Word or Adobe PDF format. Once the proposal has been submitted electronically the CEC will confirm proposal receipt within three business days. If receipt of electronic submission is not received by within this time, applicants must contact the CEC to confirm receipt. Upon completion of electronic submission, a signed copy of the proposal with authorized signatures is also required and should be postmarked no later than Friday, February 5, 2010.Three copies of the proposal should be sent by overnight courier to: Keith Powell Manager, Information Services Commission for Environmental Cooperation 393, rue St-Jacques Ouest, bureau 200 Montreal, QC Canada H2Y 1N9 tel: fax:

7 The CEC Secretariat intends to select the Consultant within fourteen (14) working days following the date of proposal submission. Notification of selections will be made on or about February 19,