PRRIP Request for Proposals Draft (5)

Home Browse Search

PRRIP - ED OFFICE DRAFT 11/03/2008 45 46 The System will be developed and managed by an independent contractor for the Program. The 47 contractor will work with the Governance Committee, Program staff, and several Program 48 Advisory Committees to develop the System. Program staff will periodically evaluate the System 49 to ensure it is performing to expectations and operating within budget. Periodic evaluations will 50 also allow the contractor to further develop and enhance the System to keep it efficient, "user- 51 friendly" and up-to-date with the current technology (i.e. software enhancements). 52 53 The System will be web-based and supported by common and tested database software (such 54 MySQLTM, OracleTM, or IBM's DB2TM). Data will be available to be viewed by web browser, 55 and texts will be available in Portable Document Format (PDF) that can be viewed with a PDF 56 reader (e.g., Adobe Acrobat ReaderTM). Individual user accounts with permissions will ensure 57 that only authorized users can submit data and reports, only the System Administrator can review 58 and approve uploaded data, and that in general all users have read/write access only to the 59 appropriate technical and administrative information. Public and non-Program groups will be 60 able view Program news and reports and download data from the web site. 61 62 A web-based System will allow real-time updates to the database and will ensure that all 63 Program participants have access to the System at their assigned level of security through the 64 Internet. Another benefit of the web-based system is the accessibility of the Program 65 information to the public. The only hardware and software that will be necessary to submit, 66 access, and retrieve information from the System is a computer with an internet connection. As 67 mentioned previously, the database will be created and managed using proven software such as 68 MySQLTM, OracleTM, or IBM's DB2TM. The database software will be chosen based on cost, 69 flexibility, reliability, and the perceived life of the software. 70 71 System component design needs and guidance follow, with examples of how each component 72 will be used by Program participants or the general public. 73 74 Hardware and Securitv 75 The System will be stand-alone in that it will be separate from other contractor servers and all 76 components will be licensed to or owned by the Program. This will add a degree of portability to 77 the System, providing the Program with the ability to move physical locations or change 78 contractors if necessary. The System will also include an off-site backup protocol. Depending on 79 the backup approach, that hardware may not need to be owned by the Program. 80 81 Permission to access information inside the System will depend on the type of user, and 82 participants with security clearance (granted during a provisioning process) will use login names 83 and passwords to access Program participant-only information. For example, the general public 84 will be able to enter the database through the web site, requiring no login name or password, but 85 access will be limited to completed work products ready for distribution to the public. A 86 Program participant will be able to enter any portion of the database (i.e. protocols, raw data, 87 administrative information, etc.) with read-only access unless given editing permission. This 88 will allow users to view text and data and query and retrieve data for analysis while preventing Page 2 of 10