SOURCES SOUGHT
D -- Global Storage Capability
- Notice Date
- 5/31/2005
- Notice Type
- Sources Sought
- NAICS
- 541519
— Other Computer Related Services
- Contracting Office
- Department of the Air Force, Air Mobility Command, 375th Contracting Squadron, 201 East Winters Street Building 50, Scott AFB, IL, 62225-5015
- ZIP Code
- 62225-5015
- Solicitation Number
- Reference-Number-AFCA11005200
- Response Due
- 6/30/2005
- Archive Date
- 7/15/2005
- Description
- DESC: This announcement constitutes a Request for Information (RFI) synopsis. Information obtained as a result of this synopsis is for planning purposes only. It does not constitute an invitation for sealed bid or request for proposal (RFP), nor is it to be construed as a commitment by the government. The government is currently conducting a market survey and analysis of government-off-the shelf and commercial-off-the shelf products that can meet the requirements for the Air Force Enterprise Information Technology Service (AF EITS) Storage initiative. The DESIRED END STATE is a Global Air Force Storage Capability that is in alignment with the end state described in the AF EITS Strategy, Version 1.0, 25 March 2005 as follows: A protected storage environment that supports day-to-day and long-term data and information. Access, archiving, retrieval, staging, and delivery of on-demand information to support AF and joint information requirements. Build upon and fully leverage the existing computing and transmission layer information technology. Leverage the power now resident in storage management software functionality that the USAF has already invested in. Complement existing IT with tools that allow AF IT professionals to remotely monitor and manage storage as an enterprise asset. The end state shall be in accordance with Information Life-cycle policies and procedures (AF Information Management/Data Management Policy, DoD Net-centric Data Strategy etc.). Furthermore, the software/hardware to provide the capability to meet the desired end state must satisfy all mandatory NCES, GIG requirements and be compliant with DISR-Online. Our current initiative calls for: Consolidation of core (Web, E-mail, File, & Print) services and mission critical applications at the regional level Consolidate local/Base level data into a MAJCOM centric storage nodes Development of ILM policies and procedures Standardized Record Management practices Indexing coupled with discovery services Centrally managed, physically distributed storage Tactical storage infrastructure (based on warfighter requirements) Content delivery networks Tiered Storage (HSM, data mobility / migration) Inclusion of other existing components such as Air Force Knowledge System (AFKS) and Enterprise Information Management (EIM) storage infrastructure Metadata storage Federation with NCES storage service Utilization of DISA DECC Distribution/Centralization of Storage as a web service Storage Management Software to support remote monitoring and management Continuity of Operation Shared Spaces to support COIs Day to Day & Long-term data storage (structured, unstructured, multimedia, file systems) Service Oriented Architecture (SOA) enabled Authoritative data sources Service level Agreements Secured Interfaces with other AF EITS services & legacy environments Mechanisms supported Time stamping Replication Controlled Duplication if necessary Concurrent access Caching etc. At a minimum the vendor?s RFI submissions should answer the following questions: 1. How does the vendor?s capability/concept support the AF EITS end-state? 2. Does the proposed capability/concept rely on any proprietary standards to meet any of the Air Force?s or Department of Defense?s requirements? This is a major interoperability concern; in our future enterprise storage solution all data must be available regardless of hardware vendor or operating systems. 3. Does the proposed capability/concept allow for storage virtualization, including Storing and recalling data regardless of file system, operating system, data format, storage hardware vendor or physical location. Rapid availability of data to all levels of command. 4. Is the capability easy to deploy, maintain, learn and use? What kind of training is available for the maintainers? On-line/CBTs, classroom, on/off-site, etc.? 5. Can your concept be remotely administered? 6. How does the proposed concept manage/support disaster recovery? Can the solution/concept support Full, Differential and Incremental back-ups directly to an off-site location? ?on-site location? Can the solution/concept support a real-time remote hot site? Can the solution/concept support automated client/server back-ups? 7. What fault tolerance measures are utilized/supported by the proposed solution? RAID levels, redundant power supplies, etc. 8. Security What ports and protocols does the proposed solution/concept use? What measures/mechanisms are used to ensure data is accessible to authorized individuals/systems? 9. What file systems are used/supported by the proposed solution? 10. What operating systems are used/supported by the proposed solution? 11. Can the solution/concept manage virtualization, archiving, clusters, volumes and replication? locally and at remote locations? How? 12. What type of connectivity (media, protocols, etc.) is supported/required between the enclaves, LAN/MANs, etc.? Data rates? 13. What other vendors are partnered with and support the proposed solution. 14. What level of policy/schedule management is available to reduce administrator?s workload and ensure that data is protected? 15. What features, whether listed above or not, are in development and will be available in future releases. Describe in detail. What standards are the features based on? Is the proposed technology proprietary? Vendors responding to this RFI who currently can make products available to the Air Force are requested to provide descriptions of concepts by close of business on 30 June, 2005. Potential vendors may express interest, make comments and ask questions via electronic mail or fax comments or questions to the Air Force Communications Agency, Service Platform Profile Development at AFCA.EACO@scott.af.mil, FAX (618) 229-5339. Vendors that meet Air Force requirements will be asked to demonstrate, at no cost to the government, capabilities and provide software/concepts for Air Force testing/review. All comments and questions must be in writing and must identify the company source, contact person, e-mail address and telephone number. EMAILADD: AFCA.EACO@scott.af.mil EMAILDESC: Air Force Communications Agency, Service Platform Profile Development, Scott AFB IL
- Place of Performance
- Address: AFCA/EAC, 203 W. Losey Street, Room 1100, Scott Air Force Base IL
- Zip Code: 62225-5200
- Country: United States
- Zip Code: 62225-5200
- Record
- SN00818459-W 20050602/050531212035 (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 |