Loren Data's SAM Daily™

fbodaily.com
Home Today's SAM Search Archives Numbered Notes CBD Archives Subscribe
FBO DAILY ISSUE OF JUNE 02, 2005 FBO #1284
SOURCES SOUGHT

A -- DELIBERATE AND CRISIS ACTION PLANNING AND EXECUTION SEGMENTS (DCAPES) INCREMENT 2B FOLLOW-ON ACQUISITION

Notice Date
5/31/2005
 
Notice Type
Sources Sought
 
Contracting Office
HQ OSSG/KA, Attn: Mr. Harry Bryan, 490 East Moore Dr., Bldg. 888, Room 2051, Maxwell AFB - Gunter Annex, AL 36114
 
ZIP Code
36114
 
Solicitation Number
OSSG-05-01
 
Response Due
6/17/2005
 
Archive Date
6/30/2005
 
Small Business Set-Aside
N/A
 
Description
Any information submitted is strictly voluntary and will not be returned to the vendor. The Government will neither award a contract solely on the basis of this notice, nor pay for any information that is submitted by respondents to the Sources Sought. This Sources Sought Synopsis is being released by the Department of the Air Force, Headquarters Operations Sustainment Support (HQ OSSG), Deployment System Branch, Program Office, Maxwell AFB, Gunter Annex, AL. HQ OSSG is seeking potential sources interested in providing maintenance, sustainment, and modernization services for Deliberate and Crisis Action Planning and Execution Segments (DCAPES) Increment 2b. DCAPES Increment 2a will be referred to in this document as DCAPES. This sources sought synopsis is not restricted. All interested vendors are encouraged to respond. DCAPES is a set of software applications providing capabilities the Air Force requires to support their planners and commanders in performing tasks for contingency operations and military operations. It provides HQ USAF, Major Command (MAJCOM), Numbered Air Force (NAF)/Air Component, Field Operating Agency (FOA), Direct Reporting Unit (DRU), Air Force reserve component, and wing/base planners support to plan, source, mobilize, deploy, sustain, redeploy, and reconstitute forces supporting contingency and crisis operations inside joint and warfighting commanders' projected decision cycles. DCAPES INCREMENT 2B will be both in-garrison and deployable; it will be an integral part of the Global Command and Control System- Air Force (GCCS-AF) and use the GCCS communications infrastructure. Air Force Command, Control, Intelligence, Surveillance, and Reconnaissance Center (AFC2ISRC) is the sponsoring command for DCAPES INCREMENT 2B requirements. Current systems have not kept pace with recent changes to planning and execution functional processes. These systems are slow in response, inaccurate, inflexible, non-interoperable, and are unable to assimilate necessary data to support activities. Approved, Final Multi-Command Mission Need Statement CAF-AMC-AFMC-AETC-AFSPC-AFSOC 616-94 for DCAPES applies. DCAPES also supports the AFC2ISRC Integrated Command and Control (IC2) Capability Mission Needs Statement (MNS) 04-98, 22 Sep 99 which identifies the need to field Command and Control (C2) capabilities to support the full spectrum of air and space operations. In concert with these goals, DCAPES integrates previously developed and fielded deployment management systems to exchange information and function in a more efficient and logical manner. Integration is achieved by implementing refined architectures and standards and migrating current and/or new systems to comply with the Global Information Grid-enterprise (GIG) system. Successful integration will result in required levels of interoperability and information exchange with appropriate agencies and C2&ISR systems as expressed in the DCAPES 2b draft Capability Development Document (CDD). DCAPES supports deliberate and crisis action planning by providing users the capability to receive and analyze taskings; develop, compare, and prioritize alternative Courses of Action (COAs); and prepare documents which support Joint Strategic Capabilities Plan (JSCP), Unified Command, and Air Force requirements and taskings. Specifically, DCAPES INCREMENT 2B will help planners to electronically access USAF planning and execution data; create and maintain War and Mobilization Plan (WMP)-3/4/5 data; exchange data with other command and control systems; create and manage Unit Type Codes (UTCs); produce Time-Phased Force and Deployment Data (TPFDD); compare planning data in different databases; perform feasibility and capability analysis in support of logistics, manpower, personnel, and transportation requirements; and develop planning and execution documents. DCAPES supports the preparation and dissemination of alert, warning, mobilization, execution, and operation orders. It assists with Air Force reserve component activation tasks. DCAPES INCREMENT 2B will support deployment operations by providing users the capability to electronically direct, monitor, and document authorized movement of forces and materiel to areas of operations, and manage changes to established movement schedules. It will support the planning and execution of sustainment/replenishment operations. It will also support termination/redeployment operations with the same capabilities used for deployment operations. Lastly, DCAPES INCREMENT 2B will produce standard and ad hoc reports, and process feedback reports for input into the Joint Uniform Lessons Learned System (JULLS). DCAPES requires extensive use of external system resources and information to be effective. A secure on-demand communications infrastructure with sufficient capacity is required for all operations. This infrastructure is increasingly critical as operations are distributed and the volume of priority information increases. Intelligence, Surveillance, and Reconnaissance (ISR) systems provide most of the information that DCAPES uses to perform its war/deployment planning and execution mission. Information operations support is required to protect networks and communications infrastructure and provide the freedom to operate. GIG enterprise services must mature and be fully implemented across the DoD to capitalize on the investment that the Air Force will make in Interworking & Interoperability (I&I) using GIG enterprise services. DCAPES INCREMENT 2B will use the modernization efforts of disparate systems to integrate applications and tools and extend the interoperability of these systems. As Joint Command and Control (JC2) mature and is fielded, DCAPES INCREMENT 2B, as part of GCCS-AF, will migrate to and help GCCS-AF become the Force Employment-Air and Space Operations Mission Capability Package (MCP) of JC2. Proposed Approach: DCAPES, as part of the C2 and ISR systems that support Monitor, Analyze, Plan, and Execute (MAPE), will be integrated Machine to Machine (M2M) with C2 processes and automation tools to execute effects-based operations in a Net-Centric environment that meet time and effectiveness criteria. DCAPES INCREMENT 2B will use an integrated, interoperable, common, standard, open-system architecture GIG enterprise service to provide global integrated C2 horizontally and vertically at all levels of operations. DCAPES INCREMENT 2B will use common and consistent functional and technical capabilities across mission boundaries and eliminate duplication in functionality, support requirements, acquisition management, and integration. DCAPES INCREMENT 2B integrates automated decision support applications and information exchange capabilities. In doing so, as part of GCCS-AF, it will position itself to fold into JC2 as an integral MCP through design. The approach is to transition current systems to a fully I&I single application-titled Force Employment-Air and Space MCP as a section of JC2. Key to the transition is integration and increased interoperability with the ten Air Force C2 application sets (DCAPES, WMP, ECSS, LOGMOD, LOGCAT, LOGFAC, MANPER-B, AEF Libraries, ASPEN and HAF-MDS) that currently support the Air and Space mission. This is an evolving assimilation of current capabilities into an interoperable suite to enable greater efficiencies and reduce operator workload through enhanced software utility. Initially, the most significant and measurable increase in capability will be in information sharing, followed by collaborative planning, shared awareness, and finally self-synchronization. DCAPES INCREMENT 2B will be maintained by a combination of Air Force and contractor personnel. Organization and depot levels of maintenance are planned. System instructions, operating procedures, and information presentations will be standardized across the commands. Training will be required for system administrators, database administrators, functional users, maintenance personnel, and systems, network and security managers. The system will process UNCLASSIFIED through SECRET level data with an objective of TOP SECRET processing. It will meet the Department of Defense (DOD) Technical Architecture Framework for Information Management (TAFIM) interoperability requirements. DCAPES INCREMENT 2B must be interoperable with DOD's Secure Internet Protocol Router Network (SIPRNET), the Air Force Command and Control Network (AFC2N), and Air Force open systems architecture command and control systems. DCAPES INCREMENT 2B will be implemented at HQ USAF, MAJCOM, NAF/Air Component, FOA, DRU, Air Force reserve component, and wing/base designated locations. HQ USAF will declare Air Force-wide system Initial Operational Capability based on MAJCOM commander inputs. Once DCAPES is fully operational at all participating locations, HQ USAF will declare Full Operational Capability for the Air Force-wide system. DCAPES INCREMENT 2B will allow seamless integration of new capabilities to meet time constraints and footprint objectives and accomplish robust and efficient information processing, storage, transport, and dissemination management with guaranteed information assurance. The system is in full compliance with the Joint Command and Control (JC2) Operational Requirements Document (ORD) 22 August 03 as a transition step to an Air and Space Mission Capability Package (MCP). JC2 MCPs are sets of Service/agency-provided software applications supporting joint mission capabilities: Force Projection, Force Readiness, Intelligence, Situational Awareness, Force Employment-Air/Space Operations, Force Employment-Joint Fires/Maneuver, and Force Protection. Vendors responding to this synopsis are encouraged to provide answers to the following questions. (1). Are the desired capabilities understandable? If not, identify your concerns; (2).Is the development schedule of 2 major and 2 minor releases per FY realistic? If not, suggest an alternative schedule; (3). Does your product offer other alternatives? If so, describe; (4). Are there any COTS solutions available? If so, identify; (5).Describe your experience with operational maintenance; (6). Describe your experience in maintaining a system of over 600,000 lines of code; (7). Describe your experience/ability to produce a full staff with experience in Oracle 8i and/or higher, Tcl-Tk, DBMS, SQL, Java, XML, HTML, J2EE, JSP, and Struts NET 8 TCP/IP, SQL Plus, Oracle Objects, on Sun Solaris platforms; (8) Describe your experience/ability to maintain a mission essential 24/7 system; (9). Describe your experience/ability to develop and/or maintain Computer Based Training (CBT) software. The resultant contractor will be required to author and maintain training documentation and to perform/facilitate on-site user training on an as required basis; (10) Is your company CMMI certified? If so, at what level? If not, will your company receive certification (when and at what level)? (11) Does your company have experience in the development and maintenance of interfaces between contractor/government and government/government systems? If so, describe; (12) Does your company have experience in maintaining multiple interfaces across multiple Department of Defense organizations? If so, describe; (13). Has your company developed applications compliant with GCCS Common Operating Environment (COE)? If so, describe; (14). Has your company developed applications using Client Server Architecture? If so, describe; (15) Does your company have experience converting Client Server Architecture to Web Services? If so, describe. (16) Describe your experience in developing a Java n-tier application utilizing the J2EE and Struts frameworks. All responses should be 25 pages or less in Times New Roman 12 font with one-inch margins (MS Word Document). The page limitation does not include the cover letter Contractors responding to this synopsis should submit the information to Mr. Harry Bryan. You may contact Mr. Bryan at (334) 416-47652 or via email: harry.bryan@gunter.af.mil. Interested Firms should indicate whether they are a Large Business, U.S. or Foreign owned, Small Business, Very Small Business, Small Disadvantaged Business, 8(a) Program Small Business, Women-owned Small Business, HUB Zone Small Business, Veteran-owned Small Business, Service-disabled Veteran-owned Small Business and/or a Native American Small Business capable of performing this effort. Responses must be submitted no later than 17 June 2005. The Air Force may contact interested vendors for follow-on fact-finding sessions. Therefore, vendors should clearly identify the telephone number, e-mail address and name of their points of contacts. See Note 26.
 
Web Link
ESC Business Opportunities Web Page
(http://www.herbb.hanscom.af.mil)
 
Place of Performance
Address: N/A
Zip Code: N/A
Country: N/A
 
Record
SN00818381-W 20050602/050531211907 (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 |
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.