140 likes | 304 Views
OPA RFP Presentation to Software Development Vendors. November 21, 2011. INDEX. Instructions to the Consultant Special Condition of Contract Proposals: Technical & Financial Term of Reference Further. A. INSTRUCTIONS TO THE CONSULTANT.
E N D
OPA RFP Presentationto Software Development Vendors November 21, 2011
INDEX • Instructions to the Consultant • Special Condition of Contract • Proposals: Technical & Financial • Term of Reference • Further
A. INSTRUCTIONS TO THE CONSULTANT • Bid Submission Last Date: 12:30 PM Monday, Nov 28, 2011 • Opening 2:30 PM Monday, Nov 28, 2011 • Selection Method :Quality & Cost based. • Project Duration: 6 months development, 2 months data migration, 1 month training of Master trainers = 9 months • Warranty Period: 12 months • Estimated Project Start Date: Jan 16, 2012 • Tech proposal shall not include any financial details.
Submission Details • Proposal must contain • Technical Proposal • One Original (Printed) & • Softcopy (pdf) of Original in a read only CD : “Technical Proposal for OPA up gradation” “Vendor’s Name” • Two copies (printed) • Financial Proposal • Bid Security • Nu. 30,000
B. SPECIAL CONDITION OF CONTRACT • Penalty: 1% of the total amount per week for every delayed week up to maximum of 10% of the total amount • Performance Security (PS): 10 % of the contract price • Payments • Mobilization Fund: 10% after PS deposit • Development Cost: 20% after SRS • Development Cost: 60% after UAT • Development Cost: 10% after Warranty Expires
C. PROPOSALS: TECHNICAL & FINANCIAL • Technical Proposal: Describe at least two outsourced software development projects successfully completed by your company (projects that resemble the target assignment {if any} would be ideal ) • Financial Proposal: Self explanatory standard forms
D. TERM OF REFERENCE • Software Requirement: • Platform: JAVA/ PostgresSQL/ MySQL • System Architecture & Hosting Environment • SDV must propose Technical solutions to ensure data privacy and reliability of inter agency letter communications in an environment where application servers are centrally hosted. • SDV must propose technical architecture to provide high availability, Performance, Security, Scalability and Manageability • Concurrency, Browser Compatibility • It has to render in a standard format in all versions of Microsoft Internet Explorer, Mozilla Firefox, Safari, Google Chrome, Opera and Netscape (W3C Compliant). • The system including the database must provide the capability of at least 500 concurrent connections and have a flexible architecture to scale to more concurrent users if required by adding servers and without needing to replace existing servers. • Development Methodology: Scrum
Ownership of Source Code and IPs will be DITT & any other agencies designated by DITT. • Collaboration, Partnerships with Foreign Firms & Subcontracting: Subcontracting is not allowed • Minimum Requirement for the Bidder • Valid License • Adequate Technical Man Power • Full time project Manager • 2 Sr. System Analyst (1 National) • 2 Sr. Developers • Min 3 National Programmer/Developers • Comply with Min Req S/w Dev Lab
Process flow and requirements • Normal User Requirements • Creating letter • Signed by Individual • Signed by Authority: Approval • Draft on / on behalf of Officiating • Multiple Signing: Note sheet [new] • Draft for correction [new] • Letters for Dispatch [new] • Response to the received Letter [new] • Receiving letter • Normal Letters • Approval Letters will be in flagged with incoming letters. • Tracking Letter • Notifications for every action taken to the letter. Notifications receiving options [on/off] • Letter transaction histories must be shown in an hierarchal and graphical representations. • Status: Dispatched, received, read, sent, filed, deleted,
Letter Filing • Auto filing of Office Copy • Forwarding the filed Letters. • Account Setting • Manage Name, password, number of letters to display per page in incoming for action page etc., • First time login: option for changing password and uploading Visual Signature • Dispatcher’s Requirements • Recording Physical letter • Registrar • Letter Received for Dispatch • Letter Received from other implementing agencies. • Administrator’s Requirements • Creating Agency, User & File • Auto Increment for New File • Auto-increment Dispatch Number irrespective of file number used • Set Officiating • Either user or administrator can set officiating user from any department within a duration specified (auto-expiry)
Management Dashboard – for Organization Admins [new] • View active number of users at a given point of time. • Error reports encountered by users. • Track User Access Information such as location, time and duration. • General Requirements • Drafting Letter • Advance Rich Text Editor, table insert and National Unicode supported features • Drafting on behalf, for correction and approval will not be possible across different implementing agencies. • Session Timeout and Auto-save features [new] [INCLUDE] • Attachments Upload optimization • Letter transaction among different implementing Agencies • Letters bound to other implementing agencies will need to send either to the Dispatcher of that agency or to the individuals • Dispatcher records incoming letter then forwards to the addressee.
Letter Non-repudiation • SDV must propose practical solution for letter non-repudiation. • SDV should be able to explain the security aspects of the proposed solution to govt agencies responsible for policy, finance and legal matters. • Identifying Letters & Notifications • Every folder must indicate number of letters pending for action by total number of letters • Read and unread letters has to be identified with different colour-coding • New pop-up with number of new notifications has to appear whenever action has been taken to the individual’s official letter by the trailing recipients • Letter Archival (Filing) • Administrator should be able to send the whole file with letters to the specific user of the same ministry, for a period of time specified by the administrator • Bulk filing. • System GUI • New OPA should retain the look and feel of previous OPA in overall GUI design
E. FURTHER COMMENTS Q&A tchojay@dit.gov.bt jtenzing@dit.gov.bt dtshering@dit.gov.bt