Loren Data's SAM Daily™

fbodaily.com
Home Today's SAM Search Archives Numbered Notes CBD Archives Subscribe
FBO DAILY - FEDBIZOPPS ISSUE OF MARCH 23, 2014 FBO #4502
SOURCES SOUGHT

D -- SOFTWARE USAGE MONITORING

Notice Date
3/21/2014
 
Notice Type
Sources Sought
 
NAICS
511210 — Software Publishers
 
Contracting Office
NASA Shared Services Center Procurement Division Building 1111 Stennis SpaceCenter, MS 39529-6000
 
ZIP Code
39529-6000
 
Solicitation Number
NNX14ZXD004L
 
Response Due
4/16/2014
 
Archive Date
3/21/2015
 
Point of Contact
Darryl A Smith, Program Analyst, Phone 228-813-6388, Fax 228-813-6493, Email darryl.a.smith@nasa.gov - Brad J Binder, Contract Specialist, Phone 228-813-6110, Fax 228-813-6493, Email brad.j.binder@nasa.gov
 
E-Mail Address
Darryl A Smith
(darryl.a.smith@nasa.gov)
 
Small Business Set-Aside
N/A
 
Description
This is a Request for Information (RFI) only and does not constitute a commitment, implied or otherwise, that the National Aeronautics and Space Administration (NASA) will take further action in this matter. Further, neither NASA, nor the Government, will be responsible for any costs incurred in furnishing this information. NASA is soliciting information to conduct market research regarding capabilities to monitor and efficiently report on software usage by individual user identification (ID) in a nonintrusive manner. Software to be monitored are standard engineering and design tools such as Autodesk, MatLab, National Instruments Labview, PTCs Creo, Cullimore and Rings Thermal Desktop and other offerings, and MSC suite of applications. The software is typically installed on dedicated and Virtual Machine (VM) servers at as many of the following NASA Centers and Associated Facilities located throughout the continental United States: Armstrong Flight Research Center (AFRC) formally Dryden Flight Research Center Dryden Aircraft Operation Facility (DAOF) Ames Research Center (ARC) Glenn Research Center Main Campus (GRC) GRC Plumbrook Facility Goddard Space Flight Center Main Campus (GSFC) GSFC Wallops Flight Facility (WFF) GSFC White Sands Complex (WSC) GSFC Independent Verification and Validation Facility (IV&V) GSFC Goddard Institute for Space Studies (GISS) Headquarters Main Campus (HQ) Johnson Space Center Main Campus (JSC) JSC White Sands Test Facility (WSTF) JSC El Paso Forward Operating Location JSC White Sands Space Harbor Kennedy Space Center Main Campus (KSC) KSC Vandenberg Air Force Base (VAFB) KSC Transoceanic Abort Landing (TAL) Sites Langley Research Center (LaRC) Marshall Space Flight Center Main Campus (MSFC) MSFC Michoud Assembly Facility (MAF) MSFC National Space Science & Technology Center (NSSTC) NASA Shared Services Center (NSSC) Stennis Space Center (SSC) There may be more than one instantiation of the software at a site. The usage monitoring tool must be able to distinguish and report individual user ID, host name, log on date, log off date, log on time, log off time, calculate duration, sum durations over time, quantity of software units used, software feature, identify site and organization location, and general user information such as phone number, location, project, and email address. Offerings should support secure data transmittal in autonomous manner to a remotely located central collection server. The respondent should describe the data collecting periodicity capability of their offerings. The desired collecting periodicity is from continuous to a minimum of once per hour. The capability to store usage data locally and transmit to a central server upon request is of interest. These offerings should provide sufficient documentation to allow installation and configuration with the minimum of offer support. Offerings should be capable of operating in an Amazon Cloud environment and support Windows, Linux, or comparable web services as described below: Notional Platform Hosting for Stored Data Generic execution environments capable of supporting multiple operating systems utilizing x86-64 instruction set architecture, including GNU/Linux distributions, Microsoft Windows Server, and Unix-like distributions that are accessible on-demand. Appropriate patch management and control that adhere to FedRAMP and NASA and Federal standards such as those published by NIST and required for FISMA, at various levels of certification and confidence. Network connectivity from execution environments to the public Internet at 1 Gbps. Network connectivity between execution environments at 1 Gbps. Flexible IP firewall rule sets with IP access groups with network access restrictions by IP and by access key. Integration with NASA Domain Name System (DNS) as needed. Notional Bandwidth Availability for Data Streaming Total bandwidth usage for streaming and non-streaming content to peak at up to 60 Gbps for short periods of time. Network capacity for content files size 1 Mb or less shall upload to the content-management tool in 7.5 seconds or less. Page load of 7.5 seconds or less for all content management tools pages as measured by a third party service such as Web metrics. Page load shall be measured over the course of a week where starting at 12:01 a.m. Eastern U.S. time Sunday through midnight Eastern U.S. time Saturday. The respondent should identify supported license managers. NASA also requests a rough order of magnitude (ROM and/or budgetary estimate) to be provide for planning purposes, only. The ROM should include a schedule of payment with associated milestones to implement the suggested solution within in the attached RFI response. PARTICIPATION POLICIES This RFI is seeking respondents with Commercial Off The Shelf (COTS) software offerings. INFORMATION REQUESTED RFI responses must include the following information: A. Name of Respondent; B. Respondents address; C. Name and contact information for primary Respondent Point of Contact (POC), including POCs name, title (or affiliation with Respondent entity), email address, and phone number; D. General description of Respondents capabilities and experience in the subject matter of this RFI; Describe your System architecture (including a data flow diagram) and how it addresses the following elements: - Support for Multi-OS client platform (Win, MAC and Linux) - Support web browsers as described in NASA-STD-2804 NASA TECHNICAL STANDARD: MINIMUM INTEROPERABILITY SOFTWARE SUITE (current revision) - Support for an enterprise-level licensing environment - Web-based reporting at the enterprise-level that addresses - Multi-Centers within the enterprise - Multi Organizations or Departments within each Center - Standard configured reports, including sample reports - Ability to customize reportsAbility to export reporting data into other formats or applicationsImportation of Lightweight Direct Access Protocol (LDAP) data - Aggregation of report data - Interactive and customizable web dashboards Describe your methodology for addressing the need for an enterprise solution to user authentication via pre-established protocols on a center-by-center basis to prevent the need for locally stored user accounts on an internal database. Provide details on installation and configuration options for your product. - Does your product use role-based administration? Please describe and provide details on roles and ability to customize roles - Alert notifications (software, host, and agent) - Report log rotation - Data retention and clean up Provide information about your Technical Support Model and if appropriate levels of support available with a description of each and expected turn-around on support issues Training available, both on-line and site specific Provide a list of license management/tracking and Engineering tools supported Identify supported license managers (e.g. Flex LM, FlexNet, LUM, LM-X, etc.) Identify data storage formats support (e.g. CSV (Comma-separated values), JSON (JavaScript Object Notation), XML (Extensible Markup Language), HDFS (Hadoop Digital File System), etc.) Identify data analysis tools supported (e.g. SPLUNK, Tableau, AWStat, Wakari, QlikView, MicroStrategy, etc.) List of current customers utilizing your product E. NASA also request a rough order of magnitude (ROM and/or budgetary estimate) to be provide for planning purposes. The ROM should align with the period of performance provided in the attached document. F. NASA request all responses to the RFI be provided by March 14, 2014. If you have any questions concerning the attached RFI, please contact Mr. Brad Binder or Dr. Darryl Smith at the contacts provided in the POC section. DISCLAIMER It is not NASAs intent to publicly disclose Respondents proprietary information obtained in response to this RFI. To the full extent that it is protected pursuant to the Freedom of Information Act and other laws and regulations, information identified by a Respondent as Proprietary or Confidential will be kept confidential. In accordance with FAR 15.201(e), the information being requested is for planning purposes only and is not intended to bind the Government. It is emphasized that this RFI is NOT a Request for Proposal, Quotation, or Invitation for Bid. This RFI is for information and planning purposes only, subject to FAR Clause 52.215-3 titled Solicitation for Information or Planning Purposes, and is NOT to be construed as a commitment by the Government to enter into a contractual agreement. The Government will not pay for information submitted in response to this RFI. No solicitation exists; therefore, do not request a copy of the solicitation. If a solicitation were released, it would be synopsized in the FedBizOpps or NASA Acquisition Internet Service website at http://prod.nais.nasa.gov/cgi-bin/eps/bizops.cgi?gr=D&pin=51. It is the responsibility of any potential offerors/bidders to monitor these sites for the release of any solicitation, synopsis, or related documents. As part of its assessment of industry responses, the NSSC may contact respondents to this Request for Information if clarifications or further information is needed. RESPONDING TO THIS RFI All final submissions shall be submitted via e-mail to both points of contact listed below no later than April 16, 2014. Two hardcopies of the final submission shall be sent to: NASA Shared Services Center (NSSC) Please reference NNX14ZXD004L-RFI in any response. Files may be submitted in MS Word, PDF, or RTF format. All responses shall be no more than ten (10) pages. A page is defined as one (1) sheet 8.5 x 11 inches using a minimum of 12-point font size for text. NO CLASSIFIED INFORMATION SHOULD BE INCLUDED IN THIS RFI RESPONSE. Respondents are highly encouraged to submit any questions via email regarding this RFI by April 1, 2014, to allow the Government time to develop responses prior to the due date for submissions. All questions and responses will be posted prior to the response date to the maximum extent practicable to assist all potential respondents. NASA Clause 1852.215-84, Ombudsman, is applicable. The Center Ombudsman for this acquisition can be found at http://prod.nais.nasa.gov/pub/p ub_library/Omb.html.
 
Web Link
FBO.gov Permalink
(https://www.fbo.gov/spg/NASA/NSSC/NSSC1/NNX14ZXD004L/listing.html)
 
Record
SN03316966-W 20140323/140321234751-d76a5b0caed118bb9b827b1106adddea (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 |
ECGrid: EDI VAN Interconnect ECGridOS: EDI Web Services Interconnect API Government Data Publications CBDDisk Subscribers
 Privacy Policy  Jenny in Wanderland!  © 1994-2024, Loren Data Corp.