MODIFICATION
D -- Force Readiness Support Services
- Notice Date
- 8/2/2005
- Notice Type
- Modification
- NAICS
- 541519
— Other Computer Related Services
- Contracting Office
- Defense Information Systems Agency, Procurement and Logistics, DITCO-NCR, P.O. 4502, Arlington, VA, 22204-4502
- ZIP Code
- 22204-4502
- Solicitation Number
- Reference-Number-RFIForceReadinessSupportServices
- Response Due
- 8/29/2005
- Point of Contact
- Marina Atchison, Contract Specialist, Phone 703-681-0928, Fax 703-681-0346,
- E-Mail Address
-
Marina.Atchison@disa.mil
- Description
- The purpose of this modification to a previous notice is to address additional questions that have been submitted. The date for submission of responses is unchanged as a result of this information. Information regarding the network architecture topology is available as two Power Point documents separately uploaded to FedBizOpps. Question: In order to better understand and respond, could you please provide further detail into the following: network architecture topology; elaboration on the development environment (number of users, platforms, software and versions, etc.); and existing databases within the architecture to include: quantity within the network, vendor and database version for each location, primary application/functionality (financial, logistics, etc.), current and anticipated growth in size database size for each location, and current anticipated growth in users/queries for each location number of users for each location. Would the Government consider products other than Oracle 10g and Solaris that met and/or exceeded these requirements? Response: 1) Additional Overview comments: The Status of Resources and Training System (SORTS) is the central registry for all Operational Units in the Department of Defense. It is the single automated reporting system within DoD that provides the senior leadership with authoritative identification, location, assignment, personnel, and equipment data. It contains the condition and level of resources and training and the Commander's assessment of how the status of his/her resources and training levels affect the Unit's readiness status. Units report by exception with 24 hours of a change and submit validation reports if no changes occur within 30 days. 2) Network architecture topology: See two Power Point documents separately uploaded to FedBizOpps. 3) Elaboration on development environment: Force Readiness is split into three categories, as follows: the Readiness Assessment System Input Tool, the SORTS database, and the Readiness Assessment System Output Tool. Development activities are conducted at the current vendor's facility and the DISA Skyline laboratory, with testing occurring at the DISA Skyline laboratory and the Engineering/Integration suite at Northrop-Grumman. Currently, the Force Readiness architecture resides on Sun Fire V440 servers, hoping to move to Sun Fire V890 Servers. In February, SORTS released Version 4.0.2 and will be releasing Version 4.0.3 in October. 4) Quantity of databases within the network: The architecture contains two primary databases, the SORTS master database (containing current readiness data) and the Historical database (containing historical readiness data). The subcomponents of these databases are shown in the two Power Point documents separately uploaded to FedBizOpps. 5) Vendor and database version: The incumbent contractor has been previously identified in Modification 01. The Readiness Assessment System Input Tool and the SORTS database are on Version 4.0.3 and the Readiness Assessment Output Tool is on Version Global 4.0.1. 6) Primary application/functionality: described in overview statement above (statement 1). 7) Database location: The database serves the readiness reporting needs of Joint Staff, all Military Services (including Coast Guard), and all Combatant Commands. In performing this support, the SORTS master database is distributed by means of local GORAs (Global SORTS Oracle Client Database) to 39 locations worldwide. The User pool should remain relatively constant as we move into Block V. 8) Architecture Issues: Force Readiness is a "system within a system." It belongs to a family of command and control mission applications (to include COP, I3, SORTS, JOPES, etc.) based upon a Common Operational Environment established by the GCCS-J Systems Engineer. In order to stay consistent throughout the architecture, it is necessary for all mission applications to remain on the same architectural base - for NOTE: THIS NOTICE MAY HAVE POSTED ON WWW.FEDBIZOPPS.GOV ON THE DATE INDICATED IN THE NOTICE ITSELF (02-AUG-2005). IT ACTUALLY APPEARED OR REAPPEARED ON THE FEDBIZOPPS SYSTEM ON 19-SEP-2005, BUT REAPPEARED IN THE FTP FEED FOR THIS POSTING DATE. PLEASE CONTACT fbo.support@gsa.gov REGARDING THIS ISSUE.
- Web Link
-
Link to FedBizOpps document.
(http://www.eps.gov/spg/DISA/D4AD/DTN/Reference-Number-RFIForceReadinessSupportServices/listing.html)
- Place of Performance
- Address: Falls Church VA
- Zip Code: 22041
- Country: USA
- Zip Code: 22041
- Record
- SN00899068-F 20050921/050919213036 (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 |