SOURCES SOUGHT
70 -- Request for Information - To procure software for the purposes of the the automation of data entry across proprietary, legacy, and contemporary data systems.
- Notice Date
- 7/30/2012
- Notice Type
- Sources Sought
- NAICS
- 511210
— Software Publishers
- Contracting Office
- N62583 SPECIALTY CENTER ACQUISITIONS NAVFAC 1100 23rd Ave Bldg 1100 Port Hueneme, CA
- ZIP Code
- 00000
- Solicitation Number
- N6258312RFIKD
- Response Due
- 8/21/2012
- Archive Date
- 8/31/2012
- Point of Contact
- Klein Dadacay (Technical POC): 805-982-3873
- E-Mail Address
-
Klein.dadacay@navy.mil
(Klein.dadacay@navy.mil)
- Small Business Set-Aside
- N/A
- Description
- This Request for Information (RFI) is for information and planning purposes only and shall not be construed as a Request for Proposal (RFP), Request for Quote (RFQ) or as an obligation on the part of the Government. The Government does not intend to award a contract on the basis of this request or otherwise pay for the requested information. No reimbursement will be made for any costs associated with providing information in response to this announcement or any follow-up information request. NAVFAC Information Technology Center (NITC) is requesting information to procure software for the purposes of the automation of data entry across proprietary, legacy and contemporary data systems. NITC currently utilizes vendor supplied software for the automation of data entry across three NAVFAC business systems. The business systems ieFACMAN (a custom developed application based off Java and Oracle 10G R2 databases), SPS (a commercially available product using a Sybase 15.5 database and with a PowerBuilder based GUI), and FIS (based off an IBM mainframe) communicate in real time. The communication between the three systems is to exchange various data elements. Initial data entry occurs on ieFACMAN screens. That data is saved to tables on an Oracle database. Data is then pushed to and pulled from SPS and/or FIS; this sequence of events is triggered by a user saving data to ieFACMAN Oracle database via a save button on the ieFACMAN GUI. The data is currently saved to 17 different Oracle tables; the data in each table represents a unique transaction type. This accepts business rules to determine what data (transaction type) is sent to which system. All transactions are transparent to users. NITC seeks a solution that provides real time communication between the three above systems based on the following technical requirements. Technical Requirements: 1.The proposed solution shall interface with our current and future versions of the following technologies, when applicable. oSPS SR 11a (currently PowerBuilder 12 and Sybase 15.5 database) oOracle database (10g r2) oJava (1.6) oDatacom/DB dbms (12) oCICS (4.1) oCA IDEAL (11) 2.Technology currently in possession of the requesting organization includes oServers running Window 2003 and 2008 OS oServers running Solaris 10/11 Unix servers OS oServers running Oracle 10g/11g database oServers running Microsoft SQL server database oServers running Oracle Application Suite/Oracle Fusion Middleware Potential solutions must be hosted at the requesting organization s site. 3.Solution should be based on a COTS software product and require minimal custom coding to support the end solution. 4.Proposed solutions will be based on up to date technology that will be supported into the next 7 years. 5.Process transactions in real time and on demand. 6.Support handling at minimum 10,000 transactions per day. 7.Average run time on each transaction shall not exceed 1 minute. Solutions with shorter run times will also receive additional consideration in this case. 8.Perform transactions in a manner which is transparent to the users, meaning that the data transfer should be initiated as soon as data is saved to ieFACMAN Oracle database table. 9.The solution shall initially support 17 transaction types and be scalable to manage increase or decrease of transaction types as the needs of the customer change. oThere is one Oracle database table per transaction type in the ieFACMAN system. The solution shall have the ability to read from each table and determine the appropriate data flow. The solution shall support the addition of more transaction types. 10.Each record normally is associated with 10 or less child records. Some records may have several hundred child records that need to be processed. While the average runtime may exceed established thresholds for these special cases, the data flow needs to be seamless and transparent to the user in all cases. 11.On the SPS system, there are multiple active SPS instances and any number of them may process transactions at any given time. The solution shall be able to communicate between any of those instances and the Oracle/Java system and the mainframe system. The current system has 13 SPS instances, but the solution should be easily scalable to support more or less. 12.When transactions fail, error messages shall be delivered to an ieFACMAN database and developers shall be notified via email potentially for the purpose of debugging. The user should also receive and error message appropriate for their level of technical expertise. 13.Debugging and other general logging information should be readily available. 14.Needs to comply with all Department of Defense/Department of Navy guidelines for the secure access and secure transmission of information, specifically: oSecured HTTPS across multiple B1 boundaries. oCompliant with the Application Security and Development, and the Application Services Security Technical Implementation Guidelines (STIG). Interested sources must submit any information relating to this announcement in writing, Portable Document Format (PDF), ten (10) pages limit, 12 point font, English text via-email to Klein.dadacay@navy.mil (Contracts POC) and Tammy.hwang@navy.mil (Technical POC). The deadline for receiving responses is 2:00PM PST, 21 August 2012. Responses received after this deadline may not be considered. Since this is a Request for Information announcement, no evaluation letters will be issued to the participants. The Government recognizes that proprietary data may be a part of your submittal. If so, clearly mark such restricted or propriety data and present it as an addendum to the non-restricted/non propriety information. All submittals received will be reviewed for informational purposes. SCAN and NITC reserves the right to independently verify all information submitted.
- Web Link
-
FBO.gov Permalink
(https://www.fbo.gov/spg/DON/NAVFAC/N47408/N6258312RFIKD/listing.html)
- Record
- SN02819388-W 20120801/120730234722-78885710443c9e9a83353606c0c39599 (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 |