Loren Data's SAM Daily™

FBO DAILY - FEDBIZOPPS ISSUE OF JANUARY 28, 2017 FBO #5545
MODIFICATION

D -- System Log Correlation Software and Support Services

Notice Date

1/26/2017
 

Notice Type

Modification/Amendment
 

NAICS

541511 — Custom Computer Programming Services
 

Contracting Office

Department of Health and Human Services, National Institutes of Health, National Library of Medicine, 6707 Democracy Blvd., Suite 105, Bethesda, Maryland, 20894, United States
 

ZIP Code

20894
 

Solicitation Number

NIHLM2017935MAH
 

Archive Date

2/25/2017
 

Point of Contact

Mario Henriquez, Phone: 301-827-7629, Sally Boakye, Phone: 301-496-6546
 

E-Mail Address

mario.henriquez@nih.gov, boakyes@mail.nih.gov
(mario.henriquez@nih.gov, boakyes@mail.nih.gov)
 

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. This solicitation is being issued as Request for Quotations (RFQ) NIHLM2017935MAH. The resultant order will be a firm-fixed price contract. In accordance with FAR Parts 12 and 13, the National Institutes of Health (NIH) intends to procure System Log Correlation Software and Support Services for NIH's Business System (NBS). This acquisition is Full and Open. The North American Industry Classification System (NAICS) Code is 541511 - Custom Computer Programming Services. Background Information The National Institutes of Health (NIH) is comprised of the Office of the Director (OD) and 27 Institutes and Centers. The OD is the central office at NIH. The OD is responsible for setting policy for NIH and for planning, managing, and coordinating the programs and activities of all the NIH components. The NIH Business System (NBS) Program is committed to fostering NIH's mission through the following provisions: • Secure, accurate, and timely business transaction capabilities that enable the NIH scientific community and supporting organizations to acquire needed assets, goods and services; • Accurate source information that facilitates knowledgeable decision making by the NIH management community regarding budgets, finance, acquisitions, supply/replenishment, property, grants, and travel; and • Improving transparency and accountability of all NBS accounting data. The NBS software applications are currently comprised of the following: • Oracle e-Business Suite (Federal Administrator, General Ledger, Payables, i-Procurement, Purchasing, Receivables, Order Management, Warehouse Management, Inventory, i-Supplier (internal and external facing), and Project Accounting (Costing and Billing); • Oracle Governance, Risk and Compliance (GRC) suite which includes the Access Application Controls Governor (AACG), Configuration Controls Governor (CCG), Preventative Controls Governor (PCG), Transaction Controls Governor (TCG), and GRC Manager and Intelligence for NIH-wide Enterprise Risk Assessment; • Kofax invoice document management application; • Sunflower Asset Management application; • Compusearch PRISM contract management module; • GSA e-Travel System - Concur (CGE) Web-Based Travel Manager application; • NIH Patient Travel Module; • SmartPay II Purchase Card Module; • Inter/Intra Agency Agreements and Reimbursable Agreements; • Interfaces, including Web interfaces that enable sharing or exchange of data with other business systems; and • Rapid eSuite. The NBS also includes special purpose peripheral devices employed for data capture or output, such as hand-held scanners and wireless printers, and supporting tools and modules that facilitate operations, maintenance and support, such as AppWorx production operations scheduler. The scope of the NBS Program includes the following: • Operations support and maintenance of the following NBS components: Federal Administrator, Finance, Acquisitions, Supply, Property, Travel (employee, patient and sponsored travel), i-Supplier, Project Accounting, Grants Integration, and other NBS Web interfaces, Foreign and Federal Grants, Fellowship Pay, Animal Procurement, and Service and Supply Fund; • Enhancement or upgrade of NBS functionality in response to demands that arise from Congressional, Office of Management and Budget (OMB), DHHS initiatives/requirements, mandatory policies, the user community, from findings during ongoing operations, from the software contractors, and other authorities which require system and data security and privacy; • Compliance with the DHHS Enterprise Performance Life Cycle (EPLC) Framework and NBS specific tailoring of EPLC project activities and documentation as approved by the NBS Contracting Officer's Technical Representative (COTR) for NBS O&M Projects; • Business consulting, communication, job aids and training to NIH Institutes and Centers with respect to NBS functionality, i.e., acquisition, logistics, budget, finance, and travel; • Operations support and maintenance of community portals on the NIH intranet that are designed to communicate with various segments of the NBS user community; and • Coordination and compliance with NIH Enterprise Architecture requirements. Contractor Requirements Independently, and not as an agent of the Government, the Contractor shall furnish all necessary labor, materials, supplies, equipment, and services necessary to provide all work and deliverables stated in the attached Statement of Work (SOW). All work performed under this procurement shall be monitored by the Contracting Officer's Representative (COR). Contractor Tasks TASK 1 - Tenable Log Correlation Engine Licensing The Contractor shall provide the government one (1) commercial off-the-shelf perpetual application Security Information and Event Management (SIEM) known as Tenable Log Correlation Engine license and services the following: Quantity Description 1 LCE - On Premise - 1TB - Perpetual Licenses TASK 2 - Annual Maintenance Service The Contractor shall provide annual maintenance and support services as follows: Quantity Description 1 LCE - On Premise - 1TB Annual Maintenance Support Services • Provide Major product and technology releases • Provide updates, fixes, security alerts, data fixes, and critical patch updates during the contract term with immediate download passwords • Provide software license replacement for accidently damaged or malfunctioning hardware keys (Not including lost keys) • Provide certification that licenses are capable with most new COTS application products • Provide 24x7 Technical Support TASK 3 - Requirements Analysis The Contractor shall conduct activities including, but not limited to, performing detailed Requirements Analysis to determine complete scope and solution to implement the Tenable Log Correlation Engine application within the NBS enterprise infrastructure and provide all of the reports, alerts, and enhancements for the security events listed in Table 1. Each of the security events shall be included in a daily report for NBS security team, and optionally, a real-time alert. There shall be a mechanism for recording acknowledgement of the report by any of several methods. The acknowledgment shall include the date, time, ID of the user, and a pointer to the report. Acceptable methods include a hypertext link, SharePoint workflow, reply email to a central account, or other similar. The deliverable of this phase shall be a detailed Requirements Document. TASK 4 - Implementation, Deployment, and Integration Upon approval of the Requirements Document, the Contractor shall provide the services to implement, deploy, and integrate the resulting reports, alerts and enhancements. 1. Custom reports/alerts/enhancements to the Log Correlation Engine Application - Provide consulting services onsite for the following: a. LCE Project Schedule - The Contractor shall provide a proposed Project schedule for implementations. The schedule shall include the following: i) Estimated time range for Implementation, Deployment, and Integration; and ii) Pricing and payment terms for yearly maintenance. b. LCE General Architecture - the Contractor shall provide a general architecture document that shall include monitoring of all NBS desktops, servers, databases, major applications, and existent security platforms. The architecture shall include forwarding logs to NIH Incident Response Team (IRT) and HHS. The architecture shall consider disaster recovery capabilities, local storage for 30 days of correlated events for on-demand queries, as well as secured network storage for long term storage of logs (i.e. minimum 12 months). c. The integrated product requires collecting, analyzing, and monitoring specific events on the internal NIH Business system network. The events listed in Table 1 shall be collected, analyzed, monitored, and stored. d. Integration of LCE - the Contractor shall work with CIT Server hosting Group and CIT Desktop Support Group to deploy Tenable LCE Clients on all NBS' endpoints (i.e. desktops and servers). The Contractor shall collaborate with CIT Networking Group to direct and allow traffic through internal firewalls from all NBS endpoints to the LCE. e. Configure - All Services, efforts, functionality, and documentation shall be deemed to be "Solution Support Materials": The Contractor shall ensure that initial configuration eliminates or reduces the level of false positives alerts generated by LCE. The Contractor shall ensure the configuration integrates with other existent security platforms including endpoint security, vulnerability scanning tools, and firewalls. The initial configuration shall be comprised by enabling default rules and policies as well as custom rules and policies based on NBS-specific requirements. f. Provide Installation Scripts - The Contractor shall provide NBS with installation scripts and instructions on how to execute the scripts to install the enhancements into NIH's existing enterprise system environment. g. Provide Initial Installation Support - The Contractor shall provide NIH with remote support for NIH's execution of the Installation Scripts in an initial Tenable LCE test environment. This remote support shall be provided on a single day. h. NBS Testing Support - The Contractor shall conduct User Acceptance Testing. The user testing may last up to 30 days, after the conclusion of the execution of the installation scripts in the initial Tenable LCE test environment. The contractor must remediate any testing failure with the 30 days' requirement. i. Migration Support - The Contractor shall provide remote support for NBS's migrations (after the installation of Tenable LCE application into the NBS infrastructure test environment) for up to two (2) additional environments (Initial Test to Stage, Stage to Production) over one (1) day per environment. The Migration support shall be provided in the same timeframe as the NIH Testing Support. j. Go-Live Support - The Contractor shall provide remote support for the initial use of the enhancements outlined herein in a production environment at NIH. This remote support shall be provided for up to five (5) business days immediately following the migrating of the enhancements into the Production environment. The Contractor shall provide 508 compliant documentations such as design document, requirements traceability matrix, system codes, configuration management, user and operation and maintenance documentation. Documentation - The contractor must provide the government with knowledge transfer and standard operation documentation 14 days after deployment. k. The Contractor shall provide a Stabilization Period of 30 days from Go-Live date. TASK 5 - System Configuration Activities The Contractor shall perform all activities as describe in the Tenable Log Correlation Engine 4.4 Administration and User Guide as follows: • LCE Agents install for servers and Desktops (Unix, Linux, Solaris and Windows) • Basic Configuration • Storage Configuration • IDS Configuration • Load Balancing Configuration • Configuring the Primary LCE Server • Advanced Configuration Options Storage • LCE Web Server • Sensor Names • Clients • User Tracking • Host Discovery and Vulnerabilities • Statistical Alerts • Resource Usage and Performance • DNS Caching • Data Forwarding • Sending Syslog Messages to Other Hosts • Syslog Compliant Messages • Content of Forwarded syslog Messages • Checksum Forwarding • TCP Syslog • Correlation • TASL and Plugins • Excluding TASL Files • Excluding PRM Files • TASL Parameters • Event Rules • Email Syntax • Syslog Syntax • Custom Command Syntax • LCE Rule Filters • LCE Shell Command Options • Email/Alerting/Execution • Debugging • Debug Mode • Storing All Logs with "save-all" • Different File System • Multiple Plugin Matches per Log File "multiple-matches" • Quick Example • SSH Keys • Service Control • Feed Settings • Feed Registration • Plugin Update • Updating Plugins (PRM Files) and TASL Scripts • Automatic Plugin (PRM Files) and TASL Updates • Updating Individual PRM Files • Offline Updates • Web Proxy • Open required port for Solaris servers syslogs to audit logging TASK 6 - Log Correlation Engine audit Logging REPORTS The Contractor shall ensure that the following report categories can be generated from software application: Categories • Accounts, Authentication & Password Audits • Advanced Persistent Threats & Malicious Software • Botnets • Center for Internet Security • Configuration & Patch Auditing • Data Leakage & File Sharing • Exploits & Attack Paths • File Integrity Monitoring • FISMA/NIST SP800-53 Rev4 or most current version at time of the deployment. • Logging, Monitoring, & Intrusion Detection • Mobile Devices, USB Devices & Wireless • Nessus Scan Monitoring • Network Monitoring • SANS • Software & IT Technology • Vulnerability Metrics • Vulnerability Reporting • Web Application Security TASK 7 - Auditable Events The Contractor shall create scripts for the following auditable events. NIH Security Event Logging Policy AU: Audit Logging Events Each information system shall generate audit records for the following events: Account Logon Events: • Logon Success • Logon Failure (Failed User Authentication - Unknown user name or bad password; Multiple Login Attempts / Logon Failures: Account Locked Out) • Logoff Account Management: • Account Created • Account Deleted • Account Disabled • Account Expired • Password Changed Directory Service: • Object (user, machine, etc.) Added to Domain / Directory • Object Removed from Domain / Directory • Domain Policy Change • Filesystem Events: • Directory Created • Directory Deleted • Directory Read • Directory Write • Directory Permissions Changed • File Created • File Deleted • File Read • File Write • File Permissions Changed • Object Access Logging Event: • Event Log Full • Event Log Overwritten Network Events: • ACL Changed • Traffic Blocked at Firewall Policy Change • All Privilege Use:  Privilege Escalation (i.e., Sudo)  Privileged Object or Service Called  Object Accessed by Privileged Account Process Tracking: • Process Executed • Process Terminated • Scheduled Event Executed • Scheduled Event Failed System Events: • Service Started • Service Stopped • System Startup • System Shutting Down • Session Disconnected FISCAM AUDITABLE EVENTS • Privileged Use Events Note: Database Layer monitoring refers to all Oracle and Microsoft databases managed by NBS. Application Layer refers to all major applications managed by NBS including but not limited to Oracle EBusiness Suite (EBS), Prism, Sunflower, Markview, CAPS, etc. FISCAM Auditable Events HHS OCIO, Policy for Information Systems Security and Privacy Handbook, which adopted NIST SP 800-53 Revision 4, Recommended Security Controls for Federal Information Systems, specifically: AU-2 Auditable Events Control: The organization: a. Determines, that the information system is capable of auditing the following events: • Server alerts and error messages • User log-on and log-off (successful or unsuccessful) • System administration activities; • Modification of privileges and access • Start up and shut down • Modifications to the application • Application alerts and error messages • Configuration changes • Account creation, modification, or deletion • (Moderate and High only) Read access to sensitive information • (Moderate and High only) Modification to sensitive information • (Moderate and High only) Printing sensitive information • Coordinates the security audit function with other organizational entities requiring audit related information to enhance mutual support and to help guide the selection of auditable events; • Provides a rationale for why the list of auditable events are deemed to be adequate to support after-the-fact investigations of security incidents; and • Determines, that the following events are to be audited within the information system at least weekly: • Unsuccessful log-on attempts that result in a locked account/node; • Attempts to Access the Database at Unusual Hours • Attempts to Access the Database with Non-Existent Users • Check for Users Sharing Database Accounts • Failed and Successful Logon Attempts • Multiple Access Attempts for Different Users from the Same Terminal • People Accessing APPS/MARKVIEW/LOFTWARE Schema in the Last 24 Hours • Check for individuals Logging in as SYSADMIN or SYSDBA • Unauthorized Database Table changes • Unauthorized FileConfig changes • Configuration changes; • Application alerts and error messages; • System administration activities; • Modification of privileges and access; and • Account creation, modification, or deletion. TASK 8 - TRAINING Tenable LCE and Security Information and Event Management (SIEM) Training - The Contractor shall provide a hands-on, instructor-led course on Tenable LCE and Security Information and Event Management (SIEM) which shall cover the operational use of the Log Correlation Engine (LCE) integration with SecurityCenter. Participants shall learn about the deployment strategies for LCEs, the Installation and configuration of LCEs, and LCE clients. The course shall be for up to five (5) attendees. Attendees shall also gain knowledge of LCE performance parameters, analysis of event data, and reporting. Each student shall have access to individual systems in order to complete the lab materials. The course shall cover the following additional topics: • Introduction to Log Correlation Engine (LCE) • LCE Architecture • LCE Server Installation Configuration and connecting to SecurityCenter • LCE Clients Installation Types • LCE Server Performance Parameters • LCE Server Maintenance • Event Analysis • Vulnerability Analysis • SecurityCenter Reports • SecurityCenter Dashboard • SecurityCenter Alerts and Ticketing Targeted IDS - Incident Response Optional Contractor Tasks All optional tasks shall only be implemented by express written authority of the Contracting Officer. ENHANCEMENTS OF THE Log Correlation Engine Application - Provide additional consulting services (Yearly Maintenance). Services may be provided remotely or onsite. Additional licenses - Due to unknown and changing variables, additional licenses may be required to meet the NBS requirements. Deliverables and Delivery Schedule The Contractor shall provide the following enhancement deliverables for review and acceptance by the COR: DELIVERABLE SECTION TIMEFRAME FOR DELIVERY Provide license for the Tenable LCE product Within 15 days after award. Install and configure the LCE product for the NBS Environment and perform unit and integrated tests to ensure proper functioning of the tool. Within 15 days after award. Requirements Document for Task 3 30 days after award Software Products for Task 4 90 days after award Training 90 days after award. Quality Assurance Plan a. Submitted with the Technical Proposal. b. Ten (10) days after updates are finalized. Final Contract Transition Plan Six (6) months before the end of the contract Status Reports Weekly until completion of installation and training. Other documentation, meeting minutes, presentation materials, scripts, and source code Varies As required by the COR and/or the Federal Project Manager(s)/Lead(s) EPLC Stage Gate Review Documentation As required by the NBS Project Management Officer Documentation required for NBS Initiatives Legend: (P) = Preliminary; (FD) = Final Draft; (F) = Final Initiation: • Business Needs Statement (F) Concept: • Project Charter (F) • Project Mgmt. Plan w/ components (P) • Design Document (P) • Functional Specification (P) • Technical Specification (P) Planning: • Enterprise Architecture (EA) Assessment (F) • Project Mgmt. Plan w/ components (F) • Privacy Impact Assessment (F) • Project Process Agreement (F) • Kick-off Meeting Requirements Analysis: • Requirements Doc w/ components (F) • Functional Specification (F) • Data Conversion Analysis (F) • Capacity Planning Analysis (FD) • Stakeholder Analysis (F) • Business Process Analysis (F) • Organizational Risk Assessment (F) • Leadership Strategy (F) • Workforce Impact Assessment (F) Design: • Capacity Planning Analysis (F) • Technical Specification with components (Architectural & detailed elements) (F) • Computer Match Agreement (F) • Test Plan (FD) • Design Document (F) • Contingency/Disaster Recovery (FD) • System of Record Notice (FD) Development: • Test Plan (F) • Operation & Maintenance Manual (FD) • Systems Security Plan (FD) • Training Plan (FD) • Training Materials (FD) • Training Delivery (FD) • Security Risk Assessment (FD) • User Manual (FD) • Business Product (FD) Test: • Implementation Plan (F) • Test Reports (F) • Capacity Planning Analysis (F) • Go/No-Go Decision (F) Implementation: • Authority to Operate w/ components (F) • System of Record Notice (F) • Operations & Maintenance Manual (F) • Systems Security Plan (F) • Training Plan (F) • Training Materials (F) • Training Delivery (F) • Security Risk Assessment (F) • User Manual (F) • Business Product (F) • Project Completion Report (F) • Contingency/Disaster Recovery (F) • Business Process Control (F) • Finalize Business Process Policy and Procedure Documentation (F) • Knowledge Management Transfer to NBS O&M (F) Operations & Maintenance: • Annual Operational Assessment (F) • Disposition Plan (F) Disposition: • Project Archives (F) As determined by the approved dates included in the governing documentation (i.e., Project Management Plan) by COTR and/or the Federal Project Manager(s)/Lead(s) Other documentation, meeting minutes, presentation materials, scripts, and source code As required by the COTR and/or the Federal Project Manager(s)/Lead(s) Period of Performance One (1) Base Year (12-months) with Four (4) 12-month Option Years PROMOTING EFFICIENT GOVERNMENT SPENDING On September 21, 2011, the Office of Management and Budget issued Memorandum M-11-35, entitled, "Eliminating Conference Spending and Promoting Efficiency in Government," emphasizing the President's priority to ensure that the Government operates with the utmost efficiency and eliminates unnecessary or wasteful spending. This was followed by the Executive Order on Delivering an Efficient, Effective, and Accountable Government (EO 13576 ) and the Executive Order on Promoting Efficient Spending ( EO 13589 ). On January 3, 2012, the Department of Health and Human Services (DHHS) issued the memorandum "HHS Policy on Promoting Efficient Spending: Use of Appropriated Funds for Conferences and Meetings, Food, Promotional Items, and Printing, and Publications" (See http://www.hhs.gov/asfr/ogapa/acquisition/effspendpol_memo.html ). In support of these administrative directives, the NIH issued a January 30, 2012 Memorandum entitled "NIH Guidance Related to the HHS Policies on Promoting Efficient Spending: Use of Appropriated Funds for Conferences, Conference Grants and Meetings, Food, Promotional Items, and Printing and Publications." (See http://oamp.od.nih.gov/ ) Any contract awarded as a result of this solicitation will: • Specifically prohibit the use of contract funds for the provision of food for meals, light refreshments and beverages for any NIH funded meeting or conference; and • Limit the procurement of meeting space, promotional items, printing, and publications. TECHNICAL EVALUATION CRITERIA (Total Points - 100) Factor 1 - Service Level of Quality - 50 The Offeror shall be evaluated on how well the proposal meets the NBS project objectives, stated tasks, considerations, and constraints, and complies with NIH IT standards and guidelines, as well as industry's best practices. This factor includes the following items: 1. Turn-around time in providing maintenance. - 10 points 2. Ability to identify, diagnose and repair software defects - 10 points 3. Ability to provide software patching - 10 points 4. Terms of maintenance services - 10 points 5. Ability to guarantee services - 10 points Factor 2 - Technical experience - 30 Technical Qualifications, Knowledge, Skills, and Certifications The Offeror will be evaluated on its ability to demonstrate it will implement, for this requirement, a team of personnel and facilitators with a minimum of three (3) years of experience working in the Federal Government, or organizations of similar size and scope, supporting design, analysis configuration and, implementation activities necessary to perform the work as described within the SOW. Factor 3 - Past Performance - 20 Points The evaluation of this factor will provide an indication of the Offeror's ability to staff and manage activities similar in function, scope and complexity to the NBS requirements, and will indicate the likelihood of the Offeror's success. This factor will be evaluated on the basis of: 1. Past Performance and Experience: The relevant past performance and working experience of the Offeror and any proposed teaming partners will be evaluated to assess the Offeror's approach to and retaining a fully qualified workforce, while minimizing turnover. The evaluation of this factor will include an evaluation of the quality of the Offeror's past products and services, its timeliness of performance, success in controlling costs, and the experience of its personnel. The Government prefers an Offeror who shows a trend of successful past performance and experience in: (1) managing service support activities. The evaluation shall include an assessment of the Offeror's ability to successfully manage complex, time sensitive operations; and (2) the likelihood the Offeror will be successful in executing the NBS requirement. Offerors shall provide relevant current or past performance (within the last three years) information sufficient for the Government to assess. 2. Customer Satisfaction: A determination of customer satisfaction based upon information received from the Offeror's past customers on work performed during the last 3 years. The Government shall review and assess relevant customer satisfaction using the Past Performance Information Retrieval System (PPIRS), other Federal databases, and/or by contacting current or previous customers. FEDERAL ACQUISITION REGULATION (FAR) CLAUSES The following provisions and clauses apply to this acquisition and are incorporated by reference. Full text may be found at https://www.acquisition.gov/Far FAR 52.212-1 Instructions to Offerors-Commercial Items FAR 52.212-2 Evaluation-Commercial Items FAR 52.212-3 Offeror Representations and Certifications-Commercial Items FAR 52.212-4 Contract Terms and Conditions-Commercial Items FAR 52.212-5 Contract Terms and Conditions Required to Implement Statutes and Executive orders FAR 52.227-19 Commercial Computer Software Licensesince Proposal Instructions All interested parties shall submit electronic responses to Mario Henriquez at Mario.henriquez@nih.gov and Sally Boakye at boakyes@mail.nih.gov. Responses must be received no later than 2:00 P.M. EST on Friday, January 27, 2017 and shall not exceed 20 single-sided pages in length, exclusive of the cover page and letter, table of contents, appendices, and resumes. Please reference solicitation number NIHLM2017935MAH on all correspondence to this notice. Inquiries regarding this notice shall be submitted electronically to Mario.henriquez@nih.gov and boakyes@mail.nih.gov by no later than 10:00 A.M. EST on Tuesday, January 17, 2017. The proposal submitted in response to this RFQ shall be prepared in two (2) parts and be clearly identified as a "Technical Proposal" and "Business Proposal." Proposals shall be in sufficient detail to permit proper evaluation, negotiation and/or acceptance thereof. The technical proposal must not contain reference to price; however, resource information (such as data concerning labor hours and categories, materials, subcontracts, etc.) must be contained in the technical proposal so that the Contractor's understanding of the Statement of Work may be evaluated. In order to receive an award, Contractors must have valid registration and certification in the Central Contractor Registration (CCR) and the Online Representations and Certifications Application (ORCA) through the System of Award Management (SAM) www.sam.gov.
 

Web Link

FBO.gov Permalink
(https://www.fbo.gov/spg/HHS/NIH/OAM/NIHLM2017935MAH/listing.html)
 

Place of Performance

Address: 6707 Democracy Boulevard, Bethesda, Maryland, 20892, United States

Zip Code: 20892
 

Record

SN04382620-W 20170128/170126234538-e4b1b6e79bb8b897d51aee1547c916c0 (fbodaily.com)
 

Source

FedBizOpps Link to This Notice
(may not be valid after Archive Date)

---

| FSG Index  |  This Issue's Index  |  Today's FBO Daily Index Page |