MODIFICATION
70 -- Amendment to provide answers to questions received. The due date is extended to 2/18/05 at 1700 hours
- Notice Date
- 2/4/2005
- Notice Type
- Modification
- Contracting Office
- ACA, ITEC4, Directorate of Contracting , 2461 Eisenhower Avenue, Alexandria, VA 22331-0700
- ZIP Code
- 22331-0700
- Solicitation Number
- S5108A-05-R-0001
- Response Due
- 2/18/2005
- Archive Date
- 4/19/2005
- Small Business Set-Aside
- N/A
- Description
- Answers to questions received For #1 - should we provide the Interface Requirement Spec - Spec is available upon request. 1. The initial integration will consist of a DMLSS PR inbound to PD2 and a contract award outbound to DMLSS. The PR and Award will be created in XML and are expected conform to existing PD2 DTDs. This will be confirmed during the requirements identification phase of the project. 2. These two transactions represent the initial transaction set for this integration. It is anticipated that additional transactions will be required in the future and that these will require the application of unique business rules to ensure correct processing. These initial transactions are being designed with a translator to ensure consistency in the current and future design of this integration. In addition - the use of the ETI Solution tool is required for documenting requirements as well as for required development. 3. The contractor will be expected to host and use the JPMO's licensed copy of the ETI Solution Toolset to complete this integration. 4. Incoming PRs will be received from and outgoing Awards will be routed through the DAASC DEBX. DAASC POC is Stuart Scott, sscott@daas.dla.mil, 937-656-3705. QUESTIONS: 1. Based on Conference Calls that XXXXXXXX participated in with DMLLS, it's our understanding that DMLSS provides PRs in an XML file that conforms to the PD2 xProcurement and xCommon DTDs that define the PD2 Adapter Standards. In addition, it's our understanding that DMLLS can accept Awards in an XML format conforming to the PD2 Adapter DTDs. Please confirm this. 2. If Number 1 is confirmed, please clarify the need for a translator as referenced in the SOW. If DMLSS and PD2 generate and accept XML files conforming to the PD2 Adapter DTDs, there is no requirement for a translator since the file formats are the same. 3. If a translator is required for this effort, the SOW requires the translator to be built using the ETI Solution Version 5 Toolset. In addition, the SOW requires delivery of the ETI Solution Metastore upon project completion. The JPMO currently has a leased version of the ETI Solution Version 5 Toolset and a Metastore that contains data related to the existing integrations utilizing the ETI Solution Version 5 Toolset. Therefore, it seems likely that the JPMO will allow the contractor awarded this effort to utilize the JPMO leased version of the ETI Solution Version 5 Toolset to ensure that information for this integration is contained with the JPMO's existing Metastore. Please clarify if the JPMO leased version of the ETI Solution Version 5 Toolset can be utilized by the contractor awarded this project. 4. Based on Conference Calls that XXXXXX participated in with DMLLS, it's our understanding that the DAASC-DEBX supports this integration by routing files between PD2 and DMLLS. Please confirm that DAASC-DEBX has a role in this integration. In addition, if available, please provide a DAASC-DEBX POC that XXXXXX can work with to determine the technical architecture or options for a technical solution to support this integration effort. The DMLSS Interface Requirements Spec is available upon request. Please contact the PCO via e-mail for a copy.
- Place of Performance
- Address: SPS JPMO 4114 Legato Rd. Fairfax VA
- Zip Code: 22033
- Country: US
- Zip Code: 22033
- Record
- SN00746014-W 20050206/050204212119 (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 |