SOLICITATION NOTICE
70 -- Bi-Directional Interface between Comprizon and PD2 using the ETI Tool.
- Notice Date
- 8/25/2005
- Notice Type
- Solicitation Notice
- Contracting Office
- ACA, ITEC4, Directorate of Contracting , 2461 Eisenhower Avenue, Alexandria, VA 22331-0700
- ZIP Code
- 22331-0700
- Solicitation Number
- S5108A-05-R-0004
- Response Due
- 9/12/2005
- Archive Date
- 11/11/2005
- Small Business Set-Aside
- N/A
- Description
- This is a combined synopsis/solicitation for commercial items prepared in accordance with the format in Subpart 12.6, 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. Proposals should be on a firm-fixed price basis, including performance based metrics, quality assurance plans, as quality assurance surveillance plans. A draft project plan shall also be included for review. A data migration guide is available upon request . The requirements are listed below. Statement of Work Department of Defense Education Activity Integration Support 11 August 2005 Section 1 Scope This statement of work (SOW) delineates software integration support required by the Program Executive Office (PEO) Enterprise Information Systems (EIS) Standard Procurement System (SPS) Joint Program Management Office (JPMO). Specifically, this support is for the creation of a Procurement Desktop Defense (PD2) integration between the Department of Defense Education Activitys (DoDEA) purchase request application Comprizon.Request and the SPS utilizing the JPMOs centralized Integrated Development Environme nt (IDE), currently hosted by Evolutionary Technologies, Inc (ETI). Section 2 Background The SPS JPMO is in the process of developing and fielding a commercially based application to support the automation of contracting offices throughout the Department of Defense (DoD). In support of this mission, the SPS Program uses a XML-based WebMethods PD2 Adapter to facilitate integrations with other systems. Additionally, the JPMO uses the ETI Solution? Version 5 tool along with WebMethods as part of a standard process for rapidly developing and documenting integration efforts. The DoDEA provides education to DoD military and civilian dependents from preschool through grade 12. DoDEA operates over 200 public schools in 15 districts located in 13 foreign countries, seven states, Guam and Puerto Rico. DoDEA has four procurement off ices. The location of these offices is as follows: Headquarters (HQ), Arlington, VA; 30 contract specialists and over 100 requisitioners DoDEA Europe Procurement Office (DEPO), Wiesbaden, Germany; 25 contract specialists DoDEA Pacific Procurement Office (DPPO), Okinawa, Japan; 18 contract specialists DoDEA Domestic Dependent Elementary and Secondary Schools (DDESS), Atlanta, GA; 3 requisitioner/contract specialist users. The DoDEA has used CACI developed contract writing solutions for over 14 years, including legacy versions branded as SACONS and Comprizon.Buy. DoDEA is currently using Comprizon.Suite, a web based procurement system hosted at DoDEA HQ in Arlington, VA. Com prizon.Suite has both requisitioning and procurement modules Comprizon.Request and Comprizon.Award. The requisitioning module is only used in HQ and DDESS at the current time. Section 3 Objectives DoDEA intends to retain Comprizon.Request as the agency wide requisitioning module and transition to SPS as its contract management solution. DoDEA requires an integration between the Comprizon.Request solution (internet accessible) and SPS PD2 Increment 2 . The following functionality is required: The Comprizon.Request submit function shall trigger the formal passing of an action from the Comprizon solution into the PD2 solution. The Comprizon.Request requisition will be taken into PD2 as an approved, funded Purchase Request. Data fields in PD2 shall be populated with all the information from the purchase request in Comprizon.Request. See the attached data element listing. The requisition number shall remain the same between the two systems. Support documents shall pull forward from Comprizon.Request to PD2. Support documents may be .doc, .xls, .pdf, cad files, etc. The status of the PD2 document shall be available and real time viewable by users in the Comprizon.Request appl ication. The objective of this SOW is to build a bi-directional interface between the SPS and the DoDEA Comprizon.Request to allow the deployment of the newest version of PD2 in a way that facilitates the DoDEA end to end logistics and contracting process. Metadata relating to the new integration will be captured in the Governments ETI Solution? metastore repository. Integration code will be developed using the ETI Solution? code generator and incorporated in the PD2 Adapter/WebMethods environment. Respondents are required to demonstrate that they possess the following capabilities: Ability to effectively and efficiently use the ETI Solution? Version 5 toolset. webMethods 6.x development expertise and ability to integrate ETI Solution? generated code into a webMethods environment. Ability to host the ETI Solution? metastore and development environment in support of this project. Ability to utilize the Evolutionary Technologies methodology for data integration management. Understanding of the Standard Procurement System and PD2 Adapter business rules and DoD contracting in general. Respondents that do not directly address the above items in their proposal will be disqualified. Section 4 Tasks The contractor will accomplish the following tasks: Task 1 Develop the bi-directional integration of PD2 and the DoDEA Comprizon.Request. The contractor will participate in discussions with DoDEA PD2 and Comprizon.Request subject matter experts (SMEs) as required to understand and document the business requirements of the integration. The contractor will develop a DoDEA Comprizon.Request translator using the PD2 Adapter, version 2.2, related PD2 Document Type Definitions and appropriate ETI Solution? tools. The contractor will develop and provide test scripts and sample files required for testing, and will support testing of the integration code at the Government Test Facility as well as onsite at the DoDEA Headquarters in Arlington, VA. The contractor will provide all code and documentation generated by the ETI tool as a result of this development effort. The contractor will provide all functional and technical documentation required to sufficiently document the integrations business process as well as all installation and configuration issues for the PD2 Adapter and/or WebMethods environment. Successful execution of these tasks will be demonstrated by the contractors ability to transform the files received from Comprizon.Request into the format required by the PD2 Adapter, and those produced by the PD2 Adapter into the specified file format re quired by Comprizon.Request. Success will be demonstrated by system testing conducted by DoDEA Comprizon.Request representatives. Section 5 Contract Deliverables All deliverables related to this effort will be provided to the SPS JPMO. The deliverables will include: Deliverable Due Project Plan outlining tasks, resources, and schedule to complete DUE 5 - Days After Contract Award Functional requirements document describing the CONOPS for the PD2 Comprizon.Request Integration (including Final ETI Solution? Conversion Report) DRAFT DUE - 15 days After Contract Award FINAL DUE - Upon Final Delivery All test artifacts (i.e., test scripts, sample files and production files). DUE Prior to Government SAT Technical Installation/Configuration Documentation DUE Upon Final Delivery All Code / Code Documentation / Copy of Final ETI Solution? Metastore DUE Upon Final Delivery All reports will be delivered in Microsoft Office products and format. Each deliverable will be determined acceptable or unacceptable to the government within ten calendar days of receipt. Section 6 Government Furnished Facilities and Services The contractor may be required to attend meetings in government facilities. The government will provide access to DoD functional and technical experts as well as additional co ntractor resources for integration support as required. Documentation and reports relating to specific tasks in the SOW will be provided by the Contracting Officers Representative (COR), Amy Taylor (703-460-1081) when and as required. Section 7 Period of Performance The period of performance for this delivery order is 60 days from initiation of the contract. Section 8 - Place of Performance The work to be performed under this order will be conducted primarily in local government facilities. Work may also be performed at the contractors facility or at other facilities, as designated and approved by the COR. Access to government facilities req uired for completion of the above tasks will be coordinated by the SPS JPMO. Section 9 - Security Requirements Work under this order will be unclassified. Contract personnel visiting any government facility in conjunction with this order shall be subject to the Standards of Conduct applicable to government employees. Site specific approval regarding access, issue o f badges, etc, will be coordinated, as required. The below cited data elements reflect specific information found in Comprizon"Suite (Comprizon.Request) functionality. DoDEA requires these data elements be captured in an SPS PD2 PURCHASE REQUEST document. ?1 OBJECT_ID Internal identification number ?2 DOCUMENT_NBR Requisition number ?3 CRE Creator of the Requisition ?4 PURPOSE Text statement of purpose, up to 2000 characters, entered by creator ?5 REQUESTED_BY Requestor's name as entered on the Requisition ?6 DELIVERY_DT Delivery date cited within the Requisition ?7 POC_NM Point of Contact Information entered within the Requisition ?8 LI_ACC_CNT Number of Account Codes ?9 ACC_BASE_AMT Total base cost of the line items associated with account information in the Requisition ?10 ACC_TOTAL_COST Total cost of the line items associated with account information in the Requisition ?11 ACC_OPTION_AMT Total option cost of the line items associated with account information in the Requisition ?12 ACC_DFLT_NUM Number of default account codes ?13 ACC_DFLT_PCT Total percentage of cost associated with the default account code(s) ?14 ACC_NUM_LI Number of line items with an account code assigned ?15 LI_NUM_LI Number of line items in the Requisition ?16 LI_TOTAL_COST Total cost of the line items in the Requisition ?17 LI_OPTION_AMT Total option cost of the line items in the Requisition ?18 LI_BASE_AMT Total base cost of the line items in the Requisition As an example, the below cited data elements are found in the Comprizon"Suite (Comprizon.AWARD) functionality. It is anticiapted that the SPS PD2 PURCHASE REQUEST document will contact all or most of these data elements populated from the Comprizon.Reques t document: ?19 OBJECT_ID Internal identification number ?20 DOCUMENT_NBR Purchase Request Number ?21 CRE Creator of the Purchase Request ?22 PURPOSE Text statement of purpose, up to 2000 characters, entered by creator ?23 REQUESTED_BY Requestor's name as entered on the Purchase Request ?24 DELIVERY_DT Delivery date cited in the Purchase Request ?25 POC_NM Point of Contact Information entered within the Purchase Request ?26 LI_ACC_CT Number of Account Codes ?27 ACC_BASE_AMT Total base cost of the line items associated with account information in the Purchase Request ?28 ACC_TOTAL_COST Total cost of the line items associated with account information in the Purchase Request ?29 ACC_OPTION_AMT Total option cost of the line items associated with account information in the Purchase Request ?30 ACC_DFLT_NUM Number of default account codes ?31 ACC_DFLT_PCT Total percentage of cost associated with the default account code(s) ?32 ACC_NUM_LI Number of line items with an account code assigned ?33 LI_NUM_LI Number of line items in the Purchase Request ?34 L I_TOTAL_COST Total cost of the line items in the Purchase Request ?35 LI_OPT_AMT Total option cost of the line items in the Purchase Request ?36 LI_BASE_AMT Total base cost of the line items in the Purchase Request
- Place of Performance
- Address: SPS JPMO 4114 Legato Rd. Fairfax VA
- Zip Code: 22033
- Country: US
- Zip Code: 22033
- Record
- SN00879510-W 20050827/050825212356 (fbodaily.com)
- Source
-
FedBizOpps.gov Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |