Solicitation Attachment.doc
DOC document 96 KB Posted
- Attached to
- Chart of Accounts Conversion Tool Federal contract opportunity
- Solicitation number
- H94002-09-Q-0022
- Issued by
- Defense Health Agency
About this file
Attachment 1
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| H94002-09-Q-0022.doc | DOC document |
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Attachment I
Chart of Accounts Conversion Tool
Specification and Evaluation Criteria Response Worksheet
| Requirement Description |
| Evaluation |
(Government Use Only)
Meets = 1
Does Not Meet = 0 Offeror Response
Must begin with “yes” or “no”, followed by description.
| 2. Functional Specification for Chart of Accounts Conversion Tool: The COTS Chart of Accounts Conversion tool must meet the following functional specifications. All of the Sections 2 and 3 requirements are criteria that must be met by the offeror’s proposed product solution, and must be provided in the offeror’s proposal in order to be considered for this acquisition. Using Attachment I, the offeror must describe how the Chart of Accounts Conversion Tool software meets each requirement laid out in this section. |
| No Evaluation or Response Here |
2.1. Operating Systems Support: Client-side software must be able to run on Windows XP Professional Service Pack 2 (SP2) and Windows Server v2003 Service Pack 2 (SP2) platforms.
2.2. Application Support: Must be able to convert Chart of Accounts on Oracle E-Business Suite release 11i.
2.3. Application: Must be able to replace existing code combinations IDs (CCIDs) with new code combinations IDs (CCIDs) based on mapping rules to carry the change throughout the existing Oracle 10g database.
2.4. Mapping management tool: Must include a utility/tool to map existing Chart of Account segments to new Chart of Account segments for one-to-one, one-to-many, many-to-one, and many-to-many mappings.
2.5. Model and error checking: Must have ability to model changes to chart of accounts and automatically check for errors that identify exceptions and alerts user.
2.6. Stand-alone: Must be available as stand-alone software, with no additional consulting or services fees required.
2.7. Reporting: Must be able to generate reports detailing mapping choices, exceptions and changes.
2.8. Change Functions: Must be able to: add Chart of Account segments, remove Chart of Account segments and values, change Chart of Account segment lengths, and consolidate two or more Chart of Accounts segments.
| 3. Maintenance and Support: Offeror must provide in the proposal one year of annual maintenance and support (one 12-month Base Period) to ensure system maintainability. Using Attachment I, the offeror must describe the details of the maintenance and support policy and response commitments. |
| No Evaluation or Response Here |
3.1. Annual Maintenance. Maintenance that includes updates and upgrades must be provided for the Migration Tool. The offeror must describe how the maintenance shall provide for product and license updates and upgrades to each component.
3.2. Annual Support: Technical support must be provided for the Migration Tool. The offeror must describe the method(s) (e.g. web or telephony based) the Government is to obtain technical support for the Migration Tool.
3.2.1. The offeror must describe how the support packages will provide a response to a Government technical support request within 24 hours, assuming a 9am to 5pm, Monday through Friday business week.
| Requirement Description |
| Evaluation |
(Government Use Only)
(See Definitions in table below) Offeror Response
Must begin with “yes” or “no”, followed by description.
| 4. Additional Requirement: The requirements in Section 4 will be rated on a three value Risk Level scale where Exceptional (3) = Very Low Risk, Acceptable (2) = Moderate Risk, and Unacceptable (1) = Very High Risk. Using Attachment I, The offeror shall describe in detail how the Migration Tool meets the following additional requirements. |
| No Evaluation or Response Here |
4.1. The offeror shall describe the user-friendliness of the graphical user interface (GUI) and the nature and level of training required to use the product.
4.2. The offeror shall describe how the tool delivers new Chart of Account structures, values, and code combination IDs (CCIDs) throughout the existing Oracle applications data.
4.3. The offeror shall describe how this Chart of Accounts Conversion Tool will transition to an Internet Protocol Version Six (IPv6) capable network in the future.
4.4. The offeror shall describe how all of their proposed client-side software will provide support for Windows Vista Business Service Pack 1 (SP1), or Windows 7.
4.5. The offeror shall describe how all of their proposed client-side software will provide support for Windows Server 2008 Service Pack 2 (SP2).
4.6. The offeror shall describe how the Chart of Accounts Conversion Tool supports Security Provisions for ensuring proper level of developer and user security. The Chart of Accounts Conversion Tool shall have the ability to execute in a PKI-enabled (Public Key Infrastructure) environment as required by Department of Defense Information Assurance Certification and Accreditation Process (DIACAP) Certification & Accreditation (C&A) process.
4.7. The offeror shall describe, in detail, all known limitations of all of their proposed software when executing in, or against, a server-side virtualized environment(s) as compared to non-virtualized environment(s.)
4.8. The offeror shall describe all known limitations of all of their proposed software when executing against Oracle E-Business Suite Release 11i and 10g Database instances running on UNIX Solaris 10 platform.
4.9. Where available, offeror shall provide Section 508 Voluntary Product Accessibility Template (VPAT) datasheet documentation.
4.10. The offeror's Chart of Accounts Conversion Tool must pass a Defense Information Systems Agency (DISA) Information Assurance (IA) security risk assessment review in order to be approved for use on the DISA network. In order to assist in this review, the offeror shall describe how they will provide documentation during the security risk assessment review.
Total Score Evaluation for Section 4
(Max Score/Lowest Risk = 30)
No Response Here
Evaluation Definitions for above Section 4
| Evaluation Rating |
| Definition and Criteria |
| Exceptional (3 Points) |
| The proposal has exceptional merit and reflects an excellent approach which should clearly result in the superior attainment of all requirements and objectives. The proposed approach includes numerous substantial advantages, and essentially no disadvantages, and can be expected to result in outstanding performance. The solutions proposed are considered very low risk in that they are exceptionally clear and precise, fully supported, and demonstrate a complete understanding of the requirements. |
Risk Level: Very Low Risk
| Acceptable (2 Points) |
| The proposal demonstrates an approach which is capable of meeting all requirements and objectives. The approach may have both advantages and disadvantages, however any disadvantages do not outweigh the advantages and the approach can be expected to result in satisfactory performance. The solutions proposed are considered to reflect moderate risk in that they are for the most part clear, precise, and supported, and demonstrate a general understanding of all the requirements. |
Risk Level: Moderate Risk
| Unacceptable (1 Point) |
| The proposal demonstrates an approach which will very likely not be capable of meeting all requirements and objectives. This approach has one or more substantial disadvantages or contains a deficiency. Collectively, the advantages and disadvantages are not likely to result in satisfactory performance. The solutions proposed are considered to reflect very high risk in that they lack any clarity or precision, are unsupported, or indicate a lack of understanding of the requirement. |
Risk Level: Very High Risk
File details come from the government source that posted it. Updated .