DRAFT
InCommon and Internet2 invite the community to respond to our request for proposal entitled: [TITLE HERE]
RFP Schedule
April 15, 2013 - Release and distribution of RFP
April 17, 2013 - Community Webinar on RFP
(Do we need written questions included - April XX 2013 - Deadline for vendors to submit questions for which they would like written answers
(MayXX, 2013 - Questions with written answers provided to all interested vendors
May 15, 2013, 9:00 am EST - deadline for submitting proposals
June 1, 2013 - Finalists interviewed, if necessary
June 15, 2013 - Vendor selected
Project Phasing
There are 5 key phases to this development Project.
- Delivery of design and architecture## Discussion: Detailed design and architecture review
- Delivery of code## Discussion: Detailed code review outlining how the final code differs from the Design presented earlier.
- Community testing and bug fixing
- Acceptance of code
- Optional post-project support
Project Requirements
The software requirements for this RFP can be found at XXXXXX.
Communication and Documentation Requirements
The organization awarded the project will have the following communication and documentation requirements:
- Weekly communications with InCommon staff and/or designated community collaborators during the project.
- Delivery of documentation including: Design and Architecture document, Java document, wiki page outlining configuration and logging options,
Proposal Content Requirements
Proposals should include the information outlined in this section; our ability to interpret and apply your proposal to these questions will factor into our decisions.
- Describe in detail the organization's proposal to address the requirements outlined in this RFP, including details such as technologies to be used. Include your approach to unit testing.
- Provide a timeline for the completion of this proposal, including start and finish dates and project phases.
- Describe the fee structure and how Internet2 will be charged.
- Provide a brief history and profile of the organization and your experience supporting Higher Education. Provide a list of the organization's Higher Education clients; include contact name, telephone number, website location, services provided and length of service.
- Provide evidence of the organization's experience and work with Shibboleth software.
- Describe the project process and methodology including sample deliverables from past projects of similar size and scope. Document examples of the organization's experience in designing/developing each of the project requirements.
- List the project team and short biographies of each team member. If using freelancers or outside resources please indicate them as such; we reserve the right to approve/disapprove of selected resources. Indicate how many full time staff are employed by your organization.
- Please provide an unsigned copy of your standard service contract for our review and any additional stipulations of which we should be aware.
- As an optional component, include a proposal of how the software will be supported after it is delivered to Internet2. If you plan to offer support to campus adopters directly, please include your terms and rates.
Assessment Criteria
A team of community reviewers will be assembled to review the proposal, using the following criteria:
- Degree of experience working with and knowledge of the Shibboleth software.
- Degree of experience working with the Higher Education community and InCommon.
- Level of cost effectiveness of the proposal and timely delivery of software.
- Level of confidence in the ability to deliver the software as described in the RFP and in the organization's proposal.
- Qualifications of the staff identified to work on the project.
- Level of communications between InCommon and the organization.
- Amount of negotiation necessary to align contract with Internet2 legal parameters.