MODIFICATION
70 -- Remote LAN Trace Tool
- Notice Date
- 6/30/2003
- Notice Type
- Modification
- Contracting Office
- Social Security Administration, Deputy Commissioner for Finance, Assessment and Management, Office of Acquisition and Grants, 1710 Gwynn Oak Avenue, Baltimore, MD, 21207-5279
- ZIP Code
- 21207-5279
- Solicitation Number
- ssa-rfi-ap-0001
- Response Due
- 7/18/2003
- Archive Date
- 8/2/2003
- Point of Contact
- Amy Pasciak, Contract Specialist, Phone 410-965-9549, Fax 410-966-5982,
- E-Mail Address
-
amy.pasciak@ssa.gov
- Description
- Thie Modification changes the due date from August 20, 2003 to July 18, 2003. This is a REQUEST FOR INFORMATION. Reference ?Remote LAN Trace Tool? when responding to this announcement. The Social Security Administration (SSA) is attempting to identify vendors that are capable of providing a software application for remote LAN tracing that does not require its own hardware. The Agency is seeking sources that produce a software package and/or solution that will meet the following requirements: 1) remote packet captures: The product must be able to remotely gather network layer data [layers 1, 2, and 3 of the Open Systems Interconnect (OSI) model] for real-time analysis and be able to transport that data to a central site to be saved for future analysis, 2) unattended format: The tool must be able to operate in an environment devoid of user intervention. That means that an engineer or user at HQ or another site must be able to initiate a capture remotely, without anyone at the user site providing assistance, 3) No third party initiation tool [Microsoft System Management Server (SMS), remote control, etc.]: Once the tool is installed, no 3rd tool may be required to initiate the trace or download (e.g.? NT scheduler may not be used to initiate a trace). SMS or a 3rd party tool MAY be used for initial install. Initiation, use of the tool must not require a remote take over/ remote control of the target machine. We want the ability to interact with the software remotely without having to use another piece of software to control the tracing. Also we want to be able to use a third tool like SMS to install it remotely so that we do not have to install it on each of the 100,000+ workstations in the network one by one manually, 4) Integrated conversion tool (.enc format): The tool must be capable of saving the trace files into required formats on its own. No 3rd party tool may be required for saving data in the formats specified elsewhere within this document. The minimum required format is NAI .ENC format, 5) the product must be capable of the full 7 layer OSI model decode. Product must decode, at a minimum, the following networking protocols; TCP/IP ? all IP protocol ? icmp, tcp, udp, etc, http, SNA, DLC, 6) Generated reports must be capable of saving in several common formats ? Microsoft Word .doc format, text file format, RTF, HTML, .PDF, 7) Pre and Post filtering (Mac address, IP address, protocol, sender, designation), 8) Product must allow user to specify search criteria before capture is initiated that will narrow down the search results (and decrease the file size) (pattern matching), 9) Product must also allow user to specify criteria that will narrow the search results AFTER the capture is completed and transferred to the user, 10) Frame slicing ? product must be able to capture only the specified portion of a frame, 11) Product licensing: Product must be licensed on an enterprise basis. This means that pricing may not be incremental based on number of machines under the product umbrella, 12) View the real time status of the decode and trace (bytes, frames, buffer, etc.), 13) Provide trace analysis: Product must provide an expert analysis of the trace upon receipt of the completed trace. This should present itself in both executive type reports as well as data level decodes of the trace data. Expert suggestions about root cause analysis should be available as well, 14) Merge traces: Product must be able to merge two or more separate trace files together into one for analysis, 15) No preset limit on trace file size, 16) Runs on all Unix and Windows platforms: This includes but is not limited to, specifically, Windows 2000, XP, NT, and Solaris, 17) Licensing sharing: Product licensing must have the capability to be centrally managed, 18) Security: Must integrate with Windows security, 19) the product must be delivered in CDROM format, 20) provide documentation both in printed format and on CDROM, 21) provide both email and telephone support during normal business hours, with additional non-prime time options available, and 22) Compliancy with Section 508. Interested vendors must be able to provide verifiable proof by submitting information in sufficient detail to demonstrate their ability to meet the Agency?s requirement. Vendors responding should indicate whether their services are available on the GSA Federal Supply Schedules or any other Government Wide Agency Contract (GWAC). This is not a request for proposal and the Government does not intend to pay for information submitted. 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. Responses to this notice should be submitted electronically by August 20, 2003. No Faxed responses. Requests for copies of a solicitation will not be honored or acknowledged. NO FORMAL SOLICITATION IS BEING ISSUED AT THIS TIME. ELECTRONIC RESPONSES ONLY, to the POC identified above.
- Record
- SN00360437-W 20030702/030630213657 (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 |