Service Registry and Repository Solution

General Information

Contracting Office Address

Social Security Administration, Deputy Commissioner, Budget, Finance and Maintenance, Office of Acquisition and Grants, 7111 Security Boulevard, Baltimore, MD, 21244.

Description

This is a REQUEST FOR INFORMATION. Please Reference Number-SSA-RFI-10-1009 when responding to this announcement.  The Social Security Administration is seeking sources sought to identify responsible vendors capable of providing an Enterprise -wide Service Registry and Repository (SRR) solution.  The objective of this action to identify, evaluate prospective Service Registry and Repository providers and their solutions relative to the Agency's strategy and requirements. The agency will evaluate responses based on functional, technical and commercial merit. 

Background information:

•Ø  The Social Security Administration is utilizing three IBM z990 2084 and three IBM z10 2094 mainframe systems at the National Computer Center in Baltimore, Maryland.  The mainframe operating system will be z/OS 1.9 or higher.  The Service Registry and Repository must be able to interact with this processing environment.

•Ø  The majority of the agency's Web Applications are running on IBM's WebSphere Application server 6.1 for z/OS.  There are also Web Applications running under IBM's WebSphere Application server 6.1 for SOLARIS.

•Ø  The agency has a large amount of legacy application running using CICS on the z/OS platform.

•Ø  The target platform the ESB will be installed on has yet to be determined. Potential platforms are; Sun Solaris (UNIX) or mainframe operating system z/OS 1.9 or higher.

•Ø  SSA has a vast customer base (56 million beneficiaries, as of July 2006) and the tool must have the ability to handle large volumes of data coupled with a huge (more than 75 million) number of transactions per day.

The tool should support the following scenarios:

•·         Web services (COBOL, true and restful) are hosted on WAS in a z/OS or Solaris environment. Users must be able to access the service and it's supporting artifacts through the Service registry and repository tool.

In addition to the above scenarios, the tool must satisfy the following minimal requirements.

General features:

• Custom lifecycle management
• Custom service categorization
• Automatic artifacts indexing
• Service dependency modeling
• Configurable change notification
• Publish and search facilities including design time search
• Endpoint and deployment metadata management
• Support multiple service-level agreements
• Strong querying abilities including the saving of queries for reuse
• Reference external locations/systems - Requirements management systems Project/Lifecycle management systems, etc.
• Support multiple environments (development, validation, integration and production)
• Support access to code to include or invoke the service

Governance:

• Policy management at artifact, service, and instance levels
• Registry monitoring for Governance
• Reverse look up for service consumption data
• Management console for stakeholders
• Performance monitoring, response time, and error logging
• Reporting abilities to include the types of reports and exporting to other tools
• Conflict resolution capabilities including the automatic identification of discrepancies between artifacts

Administration:

• Ability to store service configurations, i.e., version control
• Ability to capture and store multiple data types - unstructured content and images
• Audit trail capabilities while applying authorizations to asset descriptions
• Support different security configurations for various user roles

Federation:

• Federation with existing repositories
• Federation with other design tools and catalogs including the ability to move or exchange metadata from the repository to other tools or repositories

• Integration with Enterprise Service Bus, Business Rules Engine, and other SOA platforms
• Integration with version control tools

Operations:

• Support replication and synchronization
• Repository server clustering
• Load balancing support

Platform Architecture:

•·         Operating Systems: Windows XP, Windows Vista, z/OS, Solaris

•·         Languages: COBOL, CICS, J2EE, JDBC, ODBC, HTTP, SOAP

•·         Databases: Oracle, DB2 Version 9

•·         Web services support

•·         Java and .NET Classes support

•·         WebSphere Application Server (WAS)

•·         Hardware: IBM /Z (Mainframe), SUN/Solaris

•·         Java Enterprise Edition Application Server support

•·         Security Gateway: DataPower

Vendors having the capability to meet the above requirements are invited to submit complete details.  The responses must clearly state how their product provides the ability to meet the above requirements.  Interested parties must respond to this notice within 7 calendar days from the date of this publication.  Vendors responding should indicate whether their products are available on the GSA schedule.  Pricing data may be submitted.  This is not a request for proposal and the government does not intend to pay for information submitted.  The solution shall be compliant with Section 508 Electronic and Information Technology (EIT) Accessibility Standards.  Interested vendors must provide verifiable proof in sufficient detail to demonstrate their ability to meet the SSA's requirement, see URL site    http://www.ssa.gov/oag/acq/oagacq_508.htm.  Respondents will not be notified of the results of the evaluation of the data received. No contract award will be made on the basis of responses received; however, this information will be used in SSA's assessment of capable sources. No Faxed responses. Requests for copies of a solicitation will not be honored or acknowledged. No formal solicitation is being issued at this time. Please submit electronic responses only to the contract specialist identified herein. NOTE: There is a size limit for e-mail: No submission shall be greater than 5 MB.

Original Point of Contact

Aminta Freeman, Contract Specialist, Email [email protected]