combinedsynopsisforFMF-IMET Revised.rtf
RTF text file 343 KB Posted
- Solicitation number
- HQ0013-10-R-0001
- Issued by
-
Defense Security Cooperation Agency
Text of this file
This is a combined synopsis/solicitation for commercial services prepared in accordance with the format in the Federal Acquisition Regulation (FAR) Subpart 12.6 in conjunction with FAR 13.106, as applicable, and as supplemented with additional information included in this notice. This announcement constitutes the only solicitation; proposals are being requested and a written solicitation will not be issued. The solicitation number for this requirement is HQ0013-10-R-0001 is issued as a request for proposal (RFP). This solicitation and incorporated provisions and clauses are those in effect through Federal Acquisition Circular, FAC 2005-37. This requirement is issued as unrestricted under North American Industrial Classification System (NAICS) code 541511.
ITEM NO
SUPPLIES/SERVICES
QUANTITY
UNIT
UNIT PRICE
AMOUNT
FMF/IMET Budget Web Tool Months
FFP
Contractor shall provide all labor and material necessary to perform services outlined in the Performance Work Statement (PWS) entilted, “Information Technology Support for the Foreign Military Financing/International Military Education and Training (FMF/IMET) Budget Web Tool”
FMF/IMET Budget Web Tool Each
Transition Period. Contractor shall provide all labor and material necessary to perform services outlined in paragraph 3 of the Performance Work Statement (PWS) entilted, "“Information Technology Support for the Foreign Military Financing/International Military Education and Training (FMF/IMET) Budget Web Tool”
OPTION
Contractor shall provide all labor and material necessary to perform services outlined in the Performance Work Statement (PWS) entilted, “Information Technology Support for the Foreign Military Financing/International Military Education and Training (FMF/IMET) Budget Web Tool”
Contractor shall provide all labor and material necessary to perform services outlined in the Performance Work Statement (PWS) entilted, "“Information Technology Support for the Foreign Military Financing/International Military Education and Training (FMF/IMET) Budget Web Tool”
FMF/IMET Budget
Contractor shall provide all labor and material necessary to perform services outlined in the Performance Work Statement (PWS) entilted, "“Information Technology Support for the Foreign Military Financing/International Military Education and Training (FMF/IMET) Budget Web Tool”
ITEM NO
SUPPLIES/SERVICES
QUANTITY
UNIT
UNIT PRICE
AMOUNT
Contractor shall provide all labor and material necessary to perform services outlined in the Performance Work Statement (PWS) entilted, "“Information Technology Support for the Foreign Military Financing/International Military Education and Training (FMF/IMET) Budget Web Tool”
Performance Work Statement for Information Technology Support for the Foreign Military Financing/International Military Education and Training (FMF/IMET) Budget Web Tool Introduction The Defense Security Cooperation Agency (DSCA) leads, directs, and manages security cooperation programs and resources to support U.S. national security objectives that build relationships that promote U.S. interests; build allied and partner capacities for self-defense and coalition operations; and promote peacetime and contingency access for U.S. forces.
As the responsible organization for managing the budgeting process for the Department of Defense annual FMF and IMET funding recommendations to the State Department, DSCA had a need to automate the budget formulation and submission process, which was largely a manual process generating, collating, assessing, and summarizing disparate input from over 200 separate organizations. DSCA needed a mechanism to capture, submit, and report on budgetary data in a standardized and streamlined process.
In the fall of 2000, DSCA began developing a new approach to formulating and submitting the yearly FMF and IMET budgets in response to legislation and policy, to better justify and track requirements, and to address concerns from stakeholders about process transparency and data visibility. The FMF/IMET Budget Web Tool was developed to provide this capability. The intent of this acquisition is to maintain the existing web tool to continue to meet the goals for which it was originally developed and enhance the tool to meet ever changing legislative and policy requirements that impact the budgetary process as we strive to build partner nation capacity through FMF and IMET resourcing.
Objective DSCA requires Information Technology (IT) services to maintain the existing web tool to continue to meet the goals for which it was originally developed and enhance the tool to meet ever changing legislative and policy requirements that impact the budgetary process as we strive to build partner nation capacity through FMF and IMET resourcing.
The outcome of this procurement will be the ability to continue to effectively and timely formulate, submit and report on the annual FMF and IMET budget preparation using the web-based tool.
Approach The FMF/IMET Budget Web Tool is an application that, while ever evolving, has been operational for over 8 years and has a set of existing management and operational processes and procedures in place. In general, software and report development and maintenance requirements are tracked in a module of the web tool, prioritized by the Government Program Manager, scoped by the contractor, further definitized prior to coding, and bundled into a release of manageable size based on mutual agreement by the Government and contractor. This is an iterative process.
While it is desirable on the part of the Government to maintain continuity and consistency in management of web tool requirements, it is a dynamic environment in which the budget work, supported by the tool, is accomplished. The offeror’s proposals should, at a minimum, detail its concept of operations, design and development methodology, configuration and control management methodology, quality control methodology, and document management approach.
In addition and specifically related to the web hosting requirement, the offeror should detail its continuity of operations approach. Also, the offeror should detail in its proposal the specific web hosting configuration, services and support it will provide.
The offeror shall prepare and submit a Transition Plan as part of its proposal. The plan should include, at a minimum, the process, procedures, and timeline the offeror will use for re-hosting the web tool within its hosting facility with minimal downtime and without a loss of data or degradation in support.
Scope of Work The general IT services required are for database management; software development and maintenance; and web hosting of the application. The effort consists of the execution of 7 primary tasks as outlined below.
Software Development and Maintenance to include troubleshooting, coding, and testing
Metadata Modeling and Report Development and Maintenance to include maintaining and enhancing the integration of Cognos BI 8.0 with a complex database design and building/maintaining metadata models and complex reports in this type of environment
| Database Management to include tasks such as: database backup, database design, optimization, and performance; software installation and update; hardware and software configuration; archiving; testing; security; and data storage and retrieval efficiencies. |
| Creation and maintenance of online help, user manuals, and technical and administrative documents and manuals |
Application and maintenance of DIACAP for MAC III Sensitive web applications to maintain the web tools IA accreditation and certification
| Program Management to include software design and development; configuration and change control; quality control; and risk management |
| Web Hosting at a facility operated by the contractor, providing at a minimum, a development, testing, and production environment. The service shall provide, at a minimum a VM environment that provides load balancing, multiple processors, and clustered databases with automatic failover; 24/7 support; scheduled data backup; continuity of operations; industry standard security measures, and DS3 connections. A Service Level Agreement (SLA) shall be provided by the contractor for negotiation, acceptance, and incorporated into the contract after award. |
The following performance objectives/tasks, standards, measures, and monitoring methods will be used in the administration of this requirement.
Task 1: Software Development and Maintenance Outcome: Contractor support for the FMF/IMET Budget Web Tool results in the Government’s ability to continue to effectively and timely formulate, submit, and report on the annual FMF and IMET budget build using the web-based tool.
Performance Objective/Subtask Performance Standard Performance Measure Monitoring Method
4.1.1 The contractor shall assess requirements, develop, and deploy the necessary software/solutions to meet the Government need to include conducting requirement review meetings.
Assessment of requirements and development of software/solutions will be in accordance with methodologies in the Project Plan and process directions and requirements data approved by the Government COR in writing. COR. Requirements will be met following the approved project schedule.
Actual requirements completion will not deviate more than 10% from the project plan schedule unless approved by the Government COR in writing. The percentage of completed requirements shall not deviate by more than 10% from the planned work outlined in the project plan schedule unless approved by the Government COR in writing.
Actual Time to Complete vs. Planned Time to Complete per the Project Plan Schedule
Actual % of Work Completed vs. Planned Work in the Project Plan Schedule
100 % inspection by COR.
4.1.2 The contractor shall produce, update and maintain Use Cases for each requirement.
Use Cases will be accurate and reflect an effective requirement solution, process steps, and functional program actions.
Draft versions will be provided no less than 90% error free.
Final versions will be provided no less than 99% error free.
% of final deliverables without errors.
100% inspection by COR
4.1.3 The contractor shall produce, update, and maintain Test Scripts for each Use Case
Test Scripts will accurately reflect the functionality to be tested and the necessary scope to include related functionality. Test Scripts will be clearly written and easy to follow.
Draft versions will be provided no less than 90% error free.
Final versions will be provided at least 99% error free.
% of final deliverables without errors.
100% Inspection by COR
4.1.4 The contractor shall unit and regression test software/solutions prior to release Software/solutions will be released for Government testing with an error rate not to exceed 5% and meet the functionality requirements at no lower than a 95% success rate.
Software/solutions will be released fully operational and not introduce errors into the production environment at a rate not to exceed 2%.
Rate of error
Rate at which functionality requirements are met 100% inspection by COR
4.1.5 The contractor shall create, update, and maintain release notes for each software release.
Release notes shall be posted no later than 2 business days after the production release at least 90% of the time and at least 95% error free.
% of time
% of final deliverables without errors 100% inspection by COR
4.1.6 The contractor shall create, update, and maintain online help in conjunction with software development requirements Online help will be accurate and reflective of the requirements functionality.
Test versions will be provided at least 90% error free.
Final versions will be released at least 99% error free.
% of final deliverables without errors.
100% inspection by COR
4.1.7 The contractor shall create, update and maintain a General User and Tool Administrator Manual Manuals will be accurate and reflective of web tool functionality.
Draft versions will be provided at least 90% error free within 60 days of contract award.
Final versions will be provided at least 99% error free no more than 15 days after USG comment.
Subsequent changes will be accomplished in conjunction with software/solution development and be provided at the start of the Government testing phase and be no less than 99% error free when released into production.
% of deliverable milestones met.
% of final deliverables without errors.
100% inspection by COR of any draft and first release.
Periodic inspection by COR of any subsequent updates.
4.2 Task 2: Metadata Modeling and Report Development and Maintenance using Cognos BI 8.0
Outcome: Contractor support for the FMF/IMET Budget Web Tool provides effective metadata model, views, and reports that result in accurate, timely, and efficient reporting of data to support the FMF/IMET Budget process.
Performance Objective/Subtask Performance Standard Performance Measure Monitoring Method
4.2.1 The contractor shall create and maintain efficient and effective metadata models and views Metadata models and views must be able to report on all required data through released reports or the ad hoc reporting mechanism.
Metadata models and/or view should not result in the failure to support a reporting requirement, for that fact alone, of more than 5% Failure Rate of supporting reporting requirements 100% inspection by COR
4.2.2 The contractor shall create, update, and maintain reports for the accurate, timely, and efficient reporting of web tool data Assessment of requirements and development of software/solutions will be in accordance with methodologies in the Project Plan and process directions and requirements data approved by the COR. Requirements will be met following the approved project schedule.
Actual requirements completion will not deviate more than 10% from the original schedule unless approved by the COR. The percentage of completed requirements shall not deviate by more than 10% from the planned work outlined in the project schedule unless approved by the COR.
Time to complete vs planned
% completed vs planned
% inspection by COR.
4.3 Task 3: Database Management
Outcome: Contractor support for the FMF/IMET Budget Web Tool results in the effective, efficient, safe, and reliable processing, access, and storage of data.
Performance Objective/Subtask Performance Standard Performance Measure Monitoring Method
4.3.1 The contractor shall maintain optimized database performance through indexing, SQL Server caching and other agreed to database efficiency methods Database anomalies will be tracked through database performance monitoring and approved efficiencies applied.
Application will result in at least a 20% efficiency gain Rate of efficiency gained Random inspection by COR and through Monthly Status Report data
4.3.2 The contractor shall perform requisite software installation and updates to include those related to security Software installations and updates will be performed as required based on industry standards and vendor recommendations.
Installations and updates will be completed 95% of the time within recommended timeframes.
Timeliness of compliance Random inspection by COR and through Monthly Status Report data
4.3.3 The contractor shall perform required configuration changes and ensure the optimal hardware and software architecture is utilized Needed configuration changes are applied timely to support the web tool application. Hardware and software architecture is used that results in an efficient and responsive web tool.
Configuration changes are applied 95% of the time within requested timeframes.
Architecture changes will increase data efficiency, responsiveness, and /or failover capability by at least 20% Timeliness of compliance
Rate of efficiency, responsiveness, failover capability gained Inspection by COR through Monthly Status Report data
4.3.4 The contractor shall monitor tool response times to include bandwidth throughput, correct anomalies, and recommend improvements
Inspection by COR through Monthly Status Report data
4.3.5 The contractor shall perform all required backups
Both incremental and full Database and Web Server backups will be performed on development and production environments as outlined in the Continuity of Operations document.
Backups will be in compliance with the schedule no less than 98% of the time.
% of compliance with backup schedule Random inspection by COR and through Monthly Status Report data
4.4 Task 4: Documentation
Outcome: Contractor support for the FMF/IMET Budget Web Tool will result in well documented processes, procedures, management, and status to support the program manager and end users in the effective use, operation, and management of the web tool and associated contract.
Performance Objective/Subtask Performance Standard Performance Measure Monitoring Method
4.4.1 The contractor shall create, update, and maintain the necessary documentation for the effective and efficient operation and management of the web tool as outlined in the PWS Documents will be delivered, according to schedule that is comprehensive, accurate and clearly written.
Delivery milestones will be met no less than 95% of the time.
Final versions of documents will be provided no less than 99% error free.
Refer to specific documentation performance objectives/subtasks in other Task sections for any deviations from this general standard.
% of deliverable milestones met.
% of final deliverables without errors.
Refer to specific documentation performance objectives/subtasks in other Task sections for any deviations from this general standard.
100% inspection by COR of any draft and first release.
Periodic inspection by COR of any subsequent updates.
4.5 Task 5: MAC III Sensitive DIACAP Application and Maintenance of the FMF/IMET Budget Web Tool
Outcome: Contractor support for the FMF/IMET Budget Web Tool will result in annual compliance with DIACAP controls that retain the tools accreditation and certification.
Performance Objective/Subtask Performance Standard Performance Measure Monitoring Method
4.5.1 The contractor shall support the annual DIACAP review and assessment process through a review of Information Assurance (IA) controls Web Tool and associated process and practices will be 100% compliant for applicable controls unless waived by the Government COR in writing % of compliance with applicable DIACAP controls 100% inspection by COR through DIACAP Assessment process
4.5.2 The contractor shall create and submit an annual DIACAP Assessment/Compliance Report Web Tool and associated process and practices will be 100% compliant for applicable controls unless waived by the Government COR in writing % of compliance with applicable DIACAP controls 100% inspection by COR through DIACAP Assessment process
4.5.3 The contractor shall comply with all IA controls indicated in the contractual documentation Web Tool and associated process and practices will be 100% compliant for applicable controls unless waived by the Government COR in writing % of compliance with applicable DIACAP controls 100% inspection by COR through DIACAP Assessment process
4.6 Task 6: Program Management
Outcome: Contractor support for the FMF/IMET Budget Web Tool results in the Government’s ability to continue to effectively and timely manage the IT resources used in development of the annual FMF and IMET budget development process.
Performance Objective/Subtask Performance Standard Performance Measure Monitoring Method
4.6.1 The contractor shall create, update, maintain and provide a Project Plan
Project Plan is provided that thoroughly addresses the functional areas in the PWS by the delivery date. Updates, as required, are made through posted revisions to the online, electronic document.
A technically sound, well organized draft with no more than a 5% error rate is submitted within 30 days of contract award.
A technically sound, well organized first release with no errors within 5 business days of receipt of Government comment on draft.
Deliverable milestones met.
% of final deliverables without errors.
100% inspection by COR of any draft and first release.
Periodic inspection by COR of any subsequent updates.
4.6.2 The contractor shall create, update, maintain, and provide a Operations, Administration, and Maintenance (OAM) Manual OAM Manual provided that thoroughly addresses installation, configuration, start up, shut down, backup, recovery, upgrade deployment, diagnostic, and other support procedures for the software environment, application components, and subsystems of the project. Updates, as required, are made through posted revisions to the online, electronic document.
A technically sound, well organized draft with no more than a 5% error rate is submitted within 30 days of contract award.
A technically sound, well organized first release with no errors within 5 business days of receipt of Government comment on draft.
% of deliverable milestones met.
% of final deliverables without errors.
100% inspection by COR of any draft and first release.
Periodic inspection by COR of any subsequent updates.
4.6.3 The contractor shall create and provide a Weekly Status Report to include a Project Schedule Weekly Status Report will be provided by email every Friday accompanied by a project schedule that accurately reflects milestones and progress and discusses schedule slippages.
Delivery milestones will be met no less than 95% of the time.
Final versions of documents will be provided no less than 99% error free.
Deliverable milestones met.
% of deliverables without errors.
100% inspection by COR
4.6.4 The contractor shall prepare for, attend, and conduct a Monthly Status Review (MSR) meeting Meeting is scheduled by the last week of the month for no later than 10 business days into the next month.
Meetings will be scheduled and conducted within the standard no less than 90% of the time.
% of meetings scheduled and conducted within standard
100% inspection by COR
4.6.5 The contractor shall provide an action item summary resulting from the MSR meeting and provide status Action item summary is provided at least 95% of the time within 1 business day of MSR meeting completion indicating estimated resolution dates. Status will be provided in the Weekly Status Report until completed.
% of deliverable milestones met.
100% inspection by COR.
4.6.6 The contractor shall create and provide a Monthly Status report Monthly Status Report will be provided at the MSR 100% of the time and will, at a minimum outline reporting period work performed; planned work for the next reporting period; reconciliation of work planned in the reporting period not completed; database management information; resource expenditures; and deliverable to date.
Work not accomplished in the report period will not exceed an additional 30 calendar days of not being completed from the time it is reported and will not represent more than 10% of the overall work scheduled for completion in the current period unless the Government recognizes extenuating circumstances.
% of deliverable milestones met.
Length of time and % of work that remains not accomplished.
100% inspection by COR.
4.6.7 The contractor shall prepare and provide a monthly invoice and DD Form 250 Invoice and DD Form 250 will be provided at the MSR no less than 90% of the time and will be free of errors no less than 90% of the time.
% of deliverable milestones met.
% of deliverables without errors.
100% inspection by COR
4.6.8 The contractor shall provide appropriate oversight and guidance so the project is effectively and efficiently resourced, quality products are produced, and all deadlines are met.
Program milestones will be met no less than 95% of the time and final deliverables will be provided with no more than a 1% error rate.
% of milestones met.
% of deliverables without errors.
100% inspection by COR
4.7 Task 7: Web Hosting
Outcome: Contractor support for the FMF/IMET Budget Web Tool results in providing Government users with responsive and secure connectivity for the timely formulation, reporting, and submission of annual FMF and IMET budgets using the web-based tool.
Performance Objective/Subtask Performance Standard Performance Measure Monitoring Method
4.7.1 The contractor shall provide web hosting services that are reliable and responsive Services will be provided at a level no less than that contained in the Service Level Agreement.
Web and Application connectivity and access will be available no less than 95% of the time during the core time of Monday – Friday, 6am – 9pm ET.
Tool response time will not deviate negatively from the average by more than 20% for more than 30 minutes for those conditions causing the degradation that is under the direct control of the contractor.
Reported issues will be actively worked within 15 minutes of report time.
Reported issues will be resolved on average within 60 minutes of being reported for conditions causing the issue that are under the direct control of the contractor.
% of availability
% and length of time tool response time deviates from average response time
Average time for Issue Response
Average time for Issue Resolution
User reporting and periodic inspection by COR.
4.7.2 The contractor shall create, update, maintain, and provide a Continuity of Operations Plan Continuity of Operation Plan provided that thoroughly addresses backup processes, security (system, facility, personnel), disaster recovery/alternate site operations, and associated IA controls. Updates, as required, are made through posted revisions to the online, electronic document.
A technically sound, well organized draft with no more than a 5% error rate is submitted within 30 days of contract award.
A technically sound, well organized first release with no errors within 5 business days of receipt of Government comment on draft.
% of deliverable milestones met.
% of final deliverables without errors.
100% Inspection by COR of any draft and first release.
Periodic inspection by COR of any subsequent updates.
4.7.3 The contractor shall exercise the Continuity of Operations Plan as required Web tool and associated support is functional 90% of the time within the timeframes established in the Continuity of Operations document % of time restoration of operations is within established timeframes 100% inspection by COR
4.7.4 The contractor shall provide a Service Level Agreement for Web Hosting SLA is provided that thoroughly addresses the requirements in the PWS and any other non-cost negotiated requirements by the delivery milestone.
A technically sound, well organized draft with no more than a 5% error rate is submitted within 30 days of contract award.
A technically sound, well organized first release with no errors within 15 business days of receipt of Government comment on draft.
Deliverable milestones met.
% of final deliverables without errors.
100% Inspection by COR.
Personnel Skills Demonstrated technical capabilities and competencies of the contractor, as well as professional experience and qualifications of assigned contractor staff, are of the utmost importance in this acquisition. The contractor shall provide personnel experienced in managing and supporting a program of the scope and complexity of the FMF/IMET Budget Web Tool.
The Foreign Military Financing (FMF) and International Military Education and Training (IMET) Budget Web Tool is a zero foot print, layered architecture, web-based application that automates the preparation and submission of over 250 FMF and IMET budgets annually from approximately 260 active users within the Department of Defense and Department of State. It provides an on-line repository of tiered budgetary data in a dynamic, transaction-oriented application with a robust back end database and reporting center. The current tool has roughly 50,000 Lines of C# code, whose complexity is derived in the number of "thought points" that the code expresses. The tool implements roughly 225 different use cases, where each individual can be traced to a unique requirement. These 225 requirements are grouped into roughly 25 different areas of application development to include: User Administration, Permission/Role-base Security, Table Value Administration, Geography Administration, Email Management and Processing, Online Help Administration, Budget Call Management, Budget Entry and Submission, Allocation and Apportionment, Budget Targets, Funding Adjustment, Budget Prioritization, Executive Summary and Attachments, Fund Balance Management, Budget Cut Line Management, Import and Export of Data, Documentation and Announcement Posting, Issue Management, and Reporting. The large number of requirements, in addition to the advanced application architecture, makes the code base complex.
The application is currently hosted in a data center utilizing ITIL processes and is subject to periodic internal audits and 3rd party BITS assessments. The application operates in a VM Ware load-balanced web farm using multiple processors and a clustered SQL Server database environment both with an automatic failover configuration providing 24 hour/7 day support and connectivity exclusive of scheduled downtime. Full MS SQL Server database administration and scheduled data backup services are provided. The data center operates using DS3 connections.
The tool is DoD Information Assurance certified and accredited.
Additionally, since this an existing application, the following specific skills shall be provided in order to maintain, support, and enhance the application:
Knowledge and use of the following Software/Language: Microsoft SQL Server 2005, Microsoft Office, Windows Server 2003 (IIS, DNS, Active Directory, SMTP Virtual Server, and Group Policy), Microsoft Visual SourceSafe, Microsoft Remote Desktop, Microsoft .NET 3.5 Framework, Microsoft .NET Web Services Enhancement 3.0, XML Web Services, JavaScript, Ajax, HTML/DHTML, ASP.NET, ASP/VBS, T-SQL, C#, XML, SOAP, and XSL
Metadata modeling and complex report development using Cognos 8.0 BI.
Applying and maintaining DIACAP to MAC III Sensitive web applications
5.4 A general understanding of the FMF/IMET budget business process is highly desirable.
Personnel Requirements Due to the nature of the business and the data contained in the FMF/IMET Budget Web Tool, all contractor personnel working on this engagement shall be citizens of the United States of America. Non-US citizens or personnel with dual citizenship are not permitted. Records, data, and information to which the contractor has access may be highly sensitive and considered proprietary in nature. The contractor shall not divulge any information about the files, data, data processing activities or functions, user IDs, passwords, or any other knowledge that may be gained as a result of these tasks to anyone who is not authorized to have such information.
Key Personnel Key personnel are those that contribute substantially and measurably to the project. The offeror shall submit the resumes of all key personnel who it plans to assign to the tasks contained in the PWS. The contractor shall notify the COR 15 days prior to replacing key personnel and provide the resumes of proposed key personnel replacement with an equal or better qualified person for review and approval by the Government.
Place of Performance The work shall be performed at the contractor’s facility. Contractor facilities in the National Capitol Region are desirable, but not required, to facilitate 12 monthly status meetings and up to 12 requirements based meetings during the annual period of performance. The Government will not reimburse the contractor for costs associated with attending meetings at the Government work site.
Period of Performance
| Transition Period | Date of Contract Award – 28 Feb 2010 | |
| Base Year | 1 Mar 2010 – 28 Feb 2011 | |
| Option Year 1 | 1 Mar 2011 – 29 Feb 2012 | |
| Option Year 2 | 1 Mar 2012 – 28 Feb 2013 | |
| Option Year 3 | 1 Mar2013 – 28 Feb 2014 | |
| Option Year 4 | 1 Mar2014 – 28 Feb 2015 |
Exercising each option year is contingent on an acceptable level of contractor performance and the availability of funding.
Government Furnished Resources Government furnished resources include domain name rights, software licenses and security certificates for certain software components used in the operation of the FMF/IMET Budget Web Tool. All existing custom code and developed software, as well as existing software previously purchased by the Government or that which is produced or purchased as a result of this contract, is the property of the Government.
Deliverables All deliverables shall meet professional standards and requirements set forth in contractual documentation. The Contractor shall be responsible for delivering all items specified. The following items are deliverables which fall within the scope of the PWS. The Government reserves the right to modify the deliverable list as necessary to meet changing requirements/priorities. The contractor shall exercise due diligence in quality control of deliverables, to minimize the number of deliverable review cycles.
Unless otherwise stated, all deliverables, other than software, shall be submitted in draft form to the COR. The contractor shall incorporate COR comments and deliver a new version of a previously submitted deliverable in accordance with standards provided in Appendix A (Performance Requirements) of the PWS (or by the date agreed upon by the COR and contractor, as applicable). Acceptance of deliverables shall be provided by the COR through official email channels. The deliverables shall be provided as follows:
Deliverable Title Performance Objective/Task # Due Date Deliverable Instructions Project Plan (to include, but not limited to: Software Design and Development; Testing ; Configuration and Change Management; Quality Control; Documentation Management; Hardware Configuration; and Risk Management Methodology) 4.6 30 Days after Contract Award; maintained real-time Electronic Continuity of Operations Plan 4.7 30 Days after Contract Award; maintained real-time Electronic Operations, Administration, and Maintenance Manual 4.6 30 Days after Contract Award; maintained real-time Electronic Web Hosting Service Level Agreement 4.7 30 Days after Contract Award Electronic Annual DIACAP Report 4.5 Annually, when requested Electronic Weekly Status Report (to include Project Schedule) 4.6 Weekly, every Friday Electronic Monthly Status Report 4.6 Monthly; within first 10 business days of the month No Draft - 1 Hard Copy/Electronic Invoice/DD 250 4.6 Monthly; within first 10 business days of the month No Draft - 1 Hard Copy/Electronic Monthly Status Meeting Summary 4.6 Monthly; no later than 1 business day after Monthly Status Meeting No Draft; E-mail Use Cases 4.4 Per release schedule/cycle Electronic Test Scripts 4.4 Per release schedule cycle Electronic Software to include Reports and Online Help 4.1, 4.2, 4.4 Per release schedule/cycle Production Environment Release Release Notes 4.4 Per release schedule/cycle Electronic User Manual 4.4 60 days after Contract Award and then per release schedule/cycle Electronic Tool Administrator Manual 4.4 60 days after Contract Award and then per release schedule/cycle Electronic
Continuity of Services Any resulting contract from this solicitation will contain a FAR 52.237-3 Continuity of Services clause.
Information Assurance (IA) Compliance In order to protect DoD information in the service provider’s operating environment, the contractor shall outline the security roles and responsibilities of the web hosting service down to the IA control level in the web hosting service level agreement, along with any other performance and service-level parameters that the DoD deems appropriate and by which the DoD shall measure the IA profile of the outsourced IT-based process for the purpose of certification and accreditation. The following IA controls shall, be addressed, at a minimum as outlined in DODI 8500.2: COBR-1, CODB-1, CODP-1, COMS-1, COPS-1, COSP-1, COSW-1, COTR-1, DCCS-1, DCCT-1, DCFA-1, DCHW-1, DCMC-1, DCPD-1, DCPR-1, DCSL-1, DCSS-1, DCSW-1, EBRP-1, EBRU-1, EBVC-1, ECAN-1, ECAR-2, ECAT-1, ECCD-1, ECCT-1, ECLO-1, ECLP-1, ECND-1, ECNK-1, ECPA-1, ECPC-1, ECRC-1, ECRG-1, ECRR-1, ECSC-1, ECSD-1, ECTM-1, ECTP-1, ECVP-1, IAAC-1, IAGA-1, IAIA-1, IATS-1, PECF-1, PEDI-1, PEEL-1, PEFD-1, PEFI-1, PEFS-1, PEHC-1, PEMS-1, PEPF-1, PEPS-1, PESL-1, PESP-1, PESS-1, PETC-1, PETN-1, PEVC-1, PEVR-1, PRAS-1, PRMP-1, PRNK-1, and PRRB-1.
14. Payment Schedule
Monthly invoices will be allowed and will be paid within 30 days of receipt. Invoices will be submitted to the COR for approval and certification prior to submission to DFAS. The COR is responsible for submitting a DD 250 certifying each invoice. Invoices should be mailed to the COR at the below address:
Defense Security Cooperation Agency (DSCA) Business Operations/Comptroller ATTN: Brad Bittinger 201 12th Street South, Suite 203 Arlington VA 22202-5408
The invoice document shall include as a minimum, the following information in order to ensure proper payment:
Name and address of contractor (legal and doing business as)
Cage Code number
Invoice number and date
Contract number and/or Task Order Number
Contract line item number(s) and service rendered
Period of performance covered by invoice
Name, title, and telephone number of person to be notified in the case of defective invoices.
INSTRUCTION FOR PAYMENT OFFICE:
Do not prorate payments on this contract. Invoices are to be paid per specific contract line item number (CLIN) and accounting classification reference number (ACRN) in order of allocation as cited by the Contractor. A copy of the final paid invoice should be forwarded to the Contracting Officer and COR as designated in the PWS or the contract.
15. Contract Type
This is a best value procurement, price and other factors considered. The Government intends to award a firm-fixed price contract to the responsible Offeror whose proposal conforming to this synopsis/solicitation is most advantageous to the Government, price and other factors considered.
16. Contract Management
The Contracting Officer’s Representative (COR) will provide oversight for the task outlined in the PWS.
17. Clauses and Provisions
The following FAR clauses and provisions apply to this requirement: 52.204-4, Printed or Copied Double-Sided on Recycled Paper (Aug 2000); 52.204-7, Central Contractor Registration (Apr 2008); 52.212-1, Instructions to Offerors - Commercial Items (Jun 2008); 52.212-3 Offeror Representations and Certifications - Commercial Items (Feb 2009); 52.212-4 Contract Terms and Conditions – Commercial Items (Mar 2009); 52.212-5 Contract Terms and Conditions Required to Implement Statutes or Executive Orders - Commercial Items (Apr 2009) with the following checked subparagraphs (b), (1), (7), (9), (11), (20), (21), (22), (23), (24), (25), (26), (38) and subparagraphs (c) (1), (2), (3); 52.217-9; 52.252-2 Clauses Incorporate By Reference (Feb 1998) with the following insert www.farsite.gov and www.arnet.gov/far. Clauses and provisions contained herein are those in effect at the time of the solicitation issue date.
52.212-2 EVALUATION--COMMERCIAL ITEMS (JAN 1999)
(a) The Government will award a contract resulting from this solicitation to the responsible offeror whose offer conforming to the solicitation will be most advantageous to the Government, price and other factors considered. The Government will determine the most advantageous offer by evaluating the following factors and sub factors.
Factors 1, 2 and 3 are listed in descending order of importance. The sub-factors under each factor are of equal importance. Of the non-price factors, Technical is more important than Professional Qualifications and Experience and Past Performance. The non-price factors when combined are more important than Price. The importance of price in the evaluation for award will increase based on the degree of equality of the proposals. The Government will evaluate offers for award purposes by adding the total for all options to the total price for the basic requirement.
Factor 1.0 Technical Capability:
1.1 General Understanding of the Scope and Complexity of the Work
1.2 Software Development and Maintenance
1.3 Cognos BI 8.0 Metadata Modeling and Report Development and Maintenance
1.4 Program Management
1.5 Web Hosting
1.6 DIACAP application for MAC III Sensitive Web
Factor 2.0 Professional Qualifications and Experience:
| Software and Programming Language Requirement Competency |
| Cognos BI 8.0 Metadata Modeling and Report Development and Maintenance Competency |
Program Management Competency DIACAP Application Competency
1.5 FMF/IMET Budgeting Business Process Competency
Factor 3.0 The Past Performance
3.1 Quality of Service
3.2 Timeliness of Performance
3.3 Effectiveness of Communications
3.4 Customer Satisfaction
3.5 Subcontractor Management (as applicable)
3.6 Compliance with goals for Small Business Concerns
Factor 4.0 Price
(b) Options. The Government will evaluate offers for award purposes by adding the total price for all options to the total price for the basic requirement. The Government may determine that an offer is unacceptable if the option prices are significantly unbalanced. Evaluation of options shall not obligate the Government to exercise the option(s).
(c) A written notice of award or acceptance of an offer, mailed or otherwise furnished to the successful offeror within the time for acceptance specified in the offer, shall result in a binding contract without further action by either party. Before the offer's specified expiration time, the Government may accept an offer (or part of an offer), whether or not there are negotiations after its receipt, unless a written notice of withdrawal is received before award.
(End of provision)
52.217-9 OPTION TO EXTEND THE TERM OF THE CONTRACT (MAR 2000)
(a) The Government may extend the term of this contract by written notice to the Contractor within 30 days before the contract expires; provided that the Government gives the Contractor a preliminary written notice of its intent to extend at least 60 days before the contract expires. The preliminary notice does not commit the Government to an extension.
(b) If the Government exercises this option, the extended contract shall be considered to include this option clause.
(c) The total duration of this contract, including the exercise of any options under this clause, shall not exceed 66 months.
(End of clause)
52.232-18 AVAILABILITY OF FUNDS (APR 1984)
Funds are not presently available for this contract. The Government's obligation under this contract is contingent upon the availability of appropriated funds from which payment for contract purposes can be made. No legal liability on the part of the Government for any payment may arise until funds are made available to the Contracting Officer for this contract and until the Contractor receives notice of such availability, to be confirmed in writing by the Contracting Officer.
(End of clause)
17.0 Instructions to Offerors
All responsible sources may submit a proposal, which, if timely received, may be considered by the Government. Subject solicitation will close December 2, 2009, 2:00 p.m. EST. Offerors should submit an original and two copies of the Proposal by the closing date to the Defense Security Cooperation Agency, 201 12th Street, South, Suite 402, Arlington VA 22202-5408, Attn: Ms. Carrodena Johnson . All offerors are also required to submit an electronic copy of the Proposal to carrodena.johnson@dsca.mil. The coversheet to the proposal shall have the offeror’s information. The proposal shall only have the solicitation number. The offeror’s information SHALL NOT appear anywhere in the proposal.
Questions pertaining to the solicitation may be submitted via email. Please include the solicitation number on all correspondence. Telephone calls will not be accepted. All questions must be in writing and must be received by November 18, 2009. A consolidated question and answer (Q&A) will be posted on website http://www.fbo.gov on or around November 23, 2009.
PAST PERFORMANCE QUESTIONNAIRE (PPQ) – Offerors with relevant past performance information shall complete Section 1 of the attached Past Performance Questionnaire and submit to their designated past performance reference. The past performance reference shall complete Section 2 of the past performance questionnaire and submit directly to the Contracting Officer upon completion. The Government will consider past or current contracts (including Federal, State, local Government and commercial) for efforts similar to the Government requirement. The Government will also consider information provided by offerors on problems encountered on the identified contracts and associated corrective actions. The Government may also consider information obtained from any other sources when evaluating past performance.
Completed past performance questionnaires shall be sent to the following individual via email or facsimile:
Ms. Carrodena Johnson Contracting Officer Email: carrodena.johnson@dsca.mil Fax: 703-601-2451 Tel: 703-604-1002
Questionnaires shall be received by the contracting officer prior to the closing date and time of the solicitation. Any past performance questionnaire received after the closing date and time of the solicitation may not be considered as part of the offeror’s past performance proposal. It is recommended offerors keep track of those questionnaires sent to references to ensure the questionnaires are returned to the contracting officer prior to the solicitation closing date/time. The Government shall not consider past performance information submitted by an offeror unless it is supported by a past performance questionnaire or a CPARS rating. The Government may review the Contractor Performance Assessment Reporting System (CPARS) ratings and other existing past performance ratings on relevant contracts. The Government may also review other relevant past performance information contained in either local or other DSCA office’s files, or from other Government sources, as deemed necessary.
If an offeror has no record of past performance and states this fact in its proposal, the offeror will be given a “neutral” rating. However, failure of the offeror to affirmatively state that it has no record of past performance will result in an “unsatisfactory” rating.
Trends in a contractor’s performance may also be considered as long as a minimum of one year of performance has been completed as of the closing date of this solicitation. Offerors who present similar contracts/orders should provide a detailed explanation demonstrating the relevance of the contract/order to the requirements of the solicitation. Relevance is defined as the similarity of services provided, i.e. similar size/dollar value, magnitude and degree of administrative, managerial, and technical difficulty. The Government reserves the right to determine the relevancy of such information and to verify statements and representations made in an offeror’s proposal. Any information provided must be in sufficient detail with completed past performance questionnaires to enable the Government to conduct an evaluation. Summary lists of contracts or incomplete data may not be considered. In addition, the offeror may submit explanatory information of any substandard or poor performance and the corrective actions taken to prevent a recurrence.
In order to be considered for an award of a federal contract all contractors must be registered in the Central Contractor Registration (CCR). For information regarding registration, contact the CCR website at http://www.ccr.gov .
FAR, subpart 4.1200 requires that prospective contractors complete electronic annual representations and certifications in conjunction with their required registration in the CCR database. These Annual Representations and Certifications are submitted via the Online Representations and Certifications Application (ORCA) at http://orca.bpn.gov.
Other files
| File | Type | Posted |
|---|---|---|
| combinedsynopsisforFMF-IMET Revised 11-23-09 | — | |
| combinedsynopsisforFMF-IMET Revised 11-23-09.rtf | RTF text file | |
| Responses to Questions.doc | DOC document | |
| Use Case Example.doc | DOC document | |
| combinedsynopsisforFMF-IMET Revised.rtf | RTF text file | |
| PPQ 10-R-0001 FMF-IMET Budget Web Tool.doc | DOC document |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
File details come from the government source that posted it. Updated .