Loren Data's SAM Daily™

FBO DAILY ISSUE OF JANUARY 14, 2005 FBO #1145
SOLICITATION NOTICE

D -- Universal Description, Discovery and Integration (UDDI) Registry COTS Product with Unlimited Licenses for NCES Usage

Notice Date

1/12/2005
 

Notice Type

Solicitation Notice
 

NAICS

541519 — Other Computer Related Services
 

Contracting Office

Defense Information Systems Agency, Procurement and Logistics, DITCO-Scott, P.O. Box 25857, Scott AFB, IL, 62225-5406
 

ZIP Code

62225-5406
 

Solicitation Number

HC104705R4011Amd1
 

Response Due

1/21/2005
 

Archive Date

2/5/2005
 

Description

Amendment 0001 is issued to HC104705R4011Reposting to answer questions received. The proposal due date is also extended to read 12:00 CT, 21 Jan 2005. Questions/Answers. 1. Q. Will an offer of these capabilities as an ASP (Application Service Provider) service be acceptable? A. Providing the capabilities that we requested through an Application Service Provider WOULD be an acceptable alternative. 2. Q. In section 3 of the required capabilities, reference is made to support for UDDI V3 capabilities to support categoryBag on bindingTemplates and keyedReferences, yet there is no requirement for UDDI V3 API's. Can you give us some background to the usage and scope of this requirement? A. Whereas we are not requiring total UDDI v3 compliancy, we do require some v3 capabilities. To allow us to categorize our services to the extent we desire, we do require categoryBag support for bindingTemplates and support for keyedReference groups. 3. Q. In Section 4 of the desired capabilities, reference is made to using Web services Security for authentication and an external authorization policy. Can you give us any information on the external providers that might be used? A. We don't generally target any vendor specific security service providers. We do require any security service vendor to be broadly compliant with current web service security specifications, including (but not limited to) W3C XML dsig, encryption specs and OASIS WSS, SAML and XACML specs. 4. Q. Can you give us some clarification to the scope and design intended by Section 8 of the desired capabilities referencing a globally load-balanced single point of presence? A. This is to say the product must support a robust and scalable deployment containing support for things such as a load balancer and clustered-deployment. 5. Q. Please explain the relationship and requirements for the UDDI registry with regards to the reference in CLIN0001 to the NCES Core Discovery Service. Can you please provide some detail on the NCES Core Discovery Service that is referenced? A. The NCES Service Discovery Service (SDS) is an abstraction layer fulfilling the Service Discovery needs. Currently it does so by discovering and publishing services in a UDDI registry. Using SOA protocols, the service requestor calls the SDS which, in turn, interfaces with the UDDI Registry and performs the requested operations. 6. Q. Do you require a point-by-point analysis of the product in compliance with the OSD Net-centric checklist, or basic UDDI compliance. A. No checklist for Net-Centricity is required. However, the product's compliance with both the required and desired technical capabilities, to include the required subset of UDDI v3 capabilities, must clearly be demonstrated. A checklist would certainly be an effective way to do this and facilitate the evaluation. With respect to v2 compliance, a statement of compliance which is clearly demonstrable by included documentation will be sufficient. 7. Q. Can you give us some estimates to the scope, deployment model/timeframe and support requirements for the registry over the life of the contract (# of sites, contacts, users). A. The SDS UDDI will support both SIPRNet and NIPRNet. The expected max number of users for each is 300K for SIPRNet and 5300K for NIPRNet. The number of sites and servers will be part of a deployment strategy that will evolve based on experience and a pilote implementation in the next year. 8. Q. Since Taxonomy API is not part of the UDDI specifications, are there any identified requirements for this API? A. Taxonomy management implies APIs to create, upload, update/edit, delete and download taxonomies for use in the UDDI registry. 9. Q. Does the request for ?unlimited licenses? mean that DISA is requesting the right to install the UDDI software on an unlimited number of computer servers? World-wide? Across all DoD computers? Or only those managed by DISA? And only within the DISA NCES Program? A. Only those managed by DISA and within the NCES program. 10. Q. Can you tell us what UDDI software is currently being used? What company supplies the current UDDI software? A. The UDDI software currently being used is the Systinet UDDI Registry 4.6. All other terms and conditions remain unchanged. 11. Q. Can we use the Online Representations and Certifications Application (ORCA) http://orca.bpn.gov for this proposal? A. Yes, please use ORCA to submit your reps and certs. Just indicate in your proposal that you submitted the reps and certs via ORCA and provide your DUNS number so the contracting officer can review. You must also acknowledge the basic solicitation and amendment 0001 in your proposal. All other terms and conditions of the original combined solicitation/synopsis remain unchanged. Email questions and proposals to DISA/DITCO, Linda.Goff@disa.mil.
 

Place of Performance

Address: 5275 Leesburg Pike, Falls Church VA

Zip Code: 22041

Country: USA
 

Record

SN00733451-W 20050114/050112211549 (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 |