SPECIAL NOTICE
70 -- Global Visibility Request for Information
- Notice Date
- 6/28/2005
- Notice Type
- Special Notice
- NAICS
- 541511
— Custom Computer Programming Services
- Contracting Office
- Department of the Navy, Naval Supply Systems Command, FISC NORFOLK DETACHMENT PHILADELPHIA, 700 Robbins Avenue, Building 2B, Philadelphia, PA, 19111-5083
- ZIP Code
- 19111-5083
- Solicitation Number
- Reference-Number-Global-Visibility-RFI
- Response Due
- 7/29/2005
- Archive Date
- 8/13/2005
- Description
- U.S. Joint Forces Command (USJFCOM) has submitted a Request for Information (RFI) regarding information technologies that can be applied against the development of a global visibility capability as described below. This announcement constitutes an official Request for Information (RFI) as defined in FAR 15.201 (c). The intent of the RFI is to identify market interest and to solicit recommendations regarding the best way to produce the desired global visibility capability. This is neither a Request for Proposal (RFP) nor an Invitation for Bid (IFB), nor can there be any claims levied against the Government as a result of any information submitted by respondents. Responses to this notice are not offers and cannot be accepted by the Government to form a binding contract. Potential uses for the information received may include development of requirements packages and possible future solicitations, but knowledge of this cannot be construed in any way as a commitment by the government. The Joint Staff J8 (JS J8) and the Office of the Secretary of Defense, Personnel and Readiness (OSD-P&R) are co-leading a Functional Solutions Analysis for development of a Global Visibility Capability in support of USJFCOM as the primary conventional Joint Force Provider. The JFCOM J3/4 will be the primary customer for development of this capability. Accordingly, JFCOM is advertising this Request for Information (RFI) to all organizations, as part of its search for mature technologies that can provide either a single information technology tool or an integrated suite of tools that will meet the capability objectives listed in the Use Cases below. The Global Visibility capability is a critical enabler for JFCOM in its role as the conventional Joint Force Provider. JFCOM is pursuing a number of available options for the development of this capability. The results of our review of the responses to the RFI and the results of the JS J8 Functional Solutions Analysis will be briefed to the Force Management Functional Capabilities Board in the Fall of 2005, and will be used in the continuation of the effort to develop the a global visibility capability. This Market Research and RFI is for planning only, and shall not be considered an RFP or IFB, an obligation from the U.S. Government (USG) to acquire any products or services, or authorization to incur any cost in anticipation of such authorization. The USG does not intend to award a contract on the basis of this RFI or reimburse respondents for information solicited. This information is subject to change and in no way binds the USG to pursue any course of action described herein. If the USG chooses to issue an RFP at some future date, another notice will be published. Global Visibility Capability High Level Objectives The following Use Cases, when taken as a whole, describe the desired capability. The following Condition and Objective apply universally to all the Use Cases listed: Universal Condition: A SIPRNET and NIPRNET net-centric accessible application which accesses authoritative Joint, Service, and Agency data representing capabilities within Department of Defense (DOD) force structure regardless of classification. Authoritative data sources and force structure shall be tailorable and dynamic to allow for evolutionary changes. Universal Objective: Retrieve/input query results and export/import data into application in compliance with joint system of record (GCCS-J, JC2, other?) application standards (> 95% accuracy). Use Case A ? Force Structure Task: Provide comprehensive inventory of DOD force structure that represents capabilities required to meet emergent and rotational requirements. For Combat Forces, this inventory shall be inclusive of the smallest ?deployable entity? commonly used to meet RCC requirements. The GSORTS unit level code (ULC) field for Combat Forces provides an initial framework for meeting this requirement for each Service. For Combat Support/Combat Service Support (CS/CSS) Forces, this breakdown shall be down to the smallest ?deployable entity? (e.g., teams, dets, platoons, squads, troops, companies, elements, etc.); possibly down to the MOS/individual. Requires comprehensive analysis of all RFF?s/RFC?s generated since OIF build up to identify required levels of reporting/visibility. (Note: This analysis is currently underway; status of effort will be briefed at information exchange day.) For aggregation/ ?rollup? of capabilities (CSG?s, BDE?s etc.), GVT shall account for each individual units/ ?deployable entities? as they are tailored over time to meet requirements of requested aggregated/?rollup? capability. Standard: Provide JFP visibility of DOD Force/capabilities inventory. Required to establish units/?deployable entities? baseline to draw from to meet the requested force/capability. Forces For layout is insufficient to meet JFP requirements. Objective: Be able to identify and track (1) all DOD force structure elements (down to the smallest ?deployable entities? level) as defined in the ?task? section of this Use Case and (2) all ad hoc ?deployable entities? which are task organized to meet emergent mission requirements (examples are ETTs, ASTs, etc.). Use Case B ? Force Capabilities Identifier Task: Identify units/?deployable entities of units? (by name, UIC or other designator) that equate to the requested force or capability (RFF/RFC for contingency operations) and rotational requirements (for ongoing operations, e.g. OIF/OEF/SFOR, etc) and requirements to source contingency plan TPFDDs (OPLAN/CONPLAN/FUNCPLAN). Standard: Provide JFP a preliminary list of candidate units/?deployable entities? to meet the requested force/capability. This list of units/?deployable entities? shall represent the entire joint sourcing solution set for meeting each RCC requirement. Objective: Be able to identify (1) all DOD force structure elements (down to the smallest ?deployable entities? level) as defined in the ?task? section of the Force Structure Use Case and (2) any ad hoc force structure by capability. Use Case C ? Force Readiness Task: Provide measured readiness (current/project OPTES: Overall, Personnel, Training, Equipment, Supplies) at the appropriate level of reporting for the required capability/force across the joint sourcing solution set in common language/standards of measurement (C-rating, R-Y-G, other?). Standard: Provide JFP the visibility of measured readiness for candidate units/ ?deployable entities? to meet the requested force/capability. Readiness shall include traditional OPTES resource data as well as mission unique data requirements for units/?deployable entities? to meet each RCC requirement. Objective: Be able to identify current readiness levels as reported by the ?unit? commander within one day of status change against (1) all DOD force structure elements (down to the smallest ?deployable entities? level) as defined in the ?task? section of the Force Structure Use Case by capability and (2) ad hoc force structure. Use Case D ? Global Force Management Strategic Guidance Task: Identify red-line violations/considerations for candidate units/?deployable entities? IAW accepted GFM Strategic Guidance. Red-line considerations include (at a minimum): Mob history (Mobilizations, Demobilizations, Extensions, Re-mob, Mob Authority), Dwell, Transformation, Ops/Pers Tempo, Readiness (minimum standards for deployment), AC/RC/NG specific guidance and any others identified by OSD, Joint Staff or Services in the future. Standard: Provide JFP the strategic guidance required to prioritize/eliminate candidate units/?deployable entities? to meet the requested force/capability. Strategic guidance shall be dynamic and shall be updated by OSD, JS, and Services (as required) to ensure JFP visibility of recognized red-lines when recommending sourcing solutions to meet each RCC requirement. Objective: Incorporates all strategic guidance by OSD, Joint Staff and Services required to prioritize (1) all DOD force structure elements (down to the smallest ?deployable entities? level) as defined in the ?task? section of the Force Structure Use Case and (2) all ad hoc force structure elements. Use Case E ? Force Availability Task: Provide comprehensive and tailorable (by filter) overview (current, historic and future) of force availability for each of the candidate units/?deployable entities? identified. Required visibility includes (but is not limited to): deployments (operational, exercise, and experiments)/redeployments, PTDOs, Mobilization/Demobilization, Reconstitution/ Reset, Maintenance (include C-5 designations), Transformation, JSCP apportionment, COCOM assignment, OPCON/ADCON relationships, planned rotations (AEFPP, JPP, GNFPP, SSN global allocation, ISR allocation, other?), and Service identified considerations (?wildcard? entry for Service comments). Standard: Provide JFP the overview of units/?deployable entities? employment over time and is required to prioritize/eliminate candidate units/?deployable entities? to meet the requested force/capability. Force Availability data shall be dynamic and shall be updated (as required) by OSD, JS, COCOMs and Services to ensure JFP visibility of recognized red-lines/ considerations when recommending sourcing solutions to meet each RCC requirement. Objective: Provide historic (six year past), current, and future (six year forward) force availability for all DOD force structure elements (down to the smallest ?deployable entities? level) as defined in the ?task? section of the Force Structure Use Case. Use Case F ? Force Location Task: Provide integrated location information for each of the candidate units/?deployable entities? identified. Required location visibility (historic, current, future) includes but is not limited to CONUS (major city/state) and Intra- /Inter-Theater (major city/nation) movements for each of the candidate units/?deployable entities?. Standard: Provide JFP visibility required to prioritize/eliminate candidate units/?deployable entities? to meet the requested force/capability and to track units/ ?deployable entities throughout the pre-deployment (mobilization if required), deployment, redeployment and reconstitution cycle. Location information may be determining factor in transportation analysis in selecting one candidate over another or be used to confirm previous deployments/force availability considerations (e.g. BOG) for individual candidates (i.e. ?who can get there first??). Objective: Provide historic (six year), current, and future (three year) force locations for all DOD force structure elements (down to the smallest ?deployable entities? level) as defined in the ?task? section of the Force Structure Use Case. Provide historic, current, and future force locations for ad hoc force structure elements as they are identified. Use Case G ? Force Apportionment Task: Identify units/?deployable entities of units? (by name, UIC or other designator) apportionment to COCOM plan requirements (OPLAN, CONPLAN, FUNCPLAN). Standard: Provide JFP visibility required to identify units/?deployable entities? aligned to a given COCOM plan and their readiness/status/availability to meet requirements. In addition, require JFP to identify a substitute force/capability candidate if the apportioned unit/?deployable entity? is selected by JFP to meet other requirements or is otherwise engaged. Include capability to identify units to fill TPFDD plan requirements, flag dual/multiple taskings (identify conflicts) and find substitutes when conflicts exist. Objective: Be able to accurately track and report on the current apportionment process. Use Case H ? Common Operating Picture Task: Provide integrated common operating picture (COP) which has tailorable, exportable graphics and reports. Display features of COP shall be tailorable to display ad hoc and routine queries for requested force information but at a minimum allow the JFP to display/obtain information on the status and location of deploying, deployed and redeploying forces. The reporting module of COP shall provide user defined and standard reports in both textual and graphical presentations. Standard: COP must provide on demand and routine reporting capability to support the JFP requirement to supervise deployment of forces to meet UCP04 tasking. Objective: Retrieve/input query results and export/import data into application in compliance with joint system of record (GCCS-J, JC2, other?) application standards (> 95% accuracy). Use Case I ? Work In Progress Task: Save work-in-progress at end of day or in order to work another RFF/RFC or open previously saved work-in-progress and continue working. Standard: Provide ability to: save work-in-progress (working set of forces being considered for a complete or partial RFF/RFC); load saved work-in-progress and update qualifications of forces (readiness, etc.); identify saved works-in-progress associated with a complete or partial RFF/RFC; and transfer a saved work-in-progress to another analyst at the JFP location. Objective: Save work-in-progress in < 5 seconds; number of works-in-progress should be limited only by available storage capacity which must be expandable Instructions for Submission of Responses The disclaimers provided in the first section of this RFI apply to all submissions by respondents. The Government does not desire elaborate submissions and requests that RFI responses be limited to 30 total pages of information (single spaced using 12 pitch font). Responses should include 1) An executive summary outlining a high level overview of the substantive ideas presented in the response; 2) A short description of the mature technologies available to provide the desired capabilities; 3) A rough order of magnitude (ROM) estimate of vendor non-recurring development costs to adapt mature technologies to provide these specific capabilities to create a working prototype; 4) A rough order of magnitude timeline for development; 5) Any other information at vendor discretion, but limited to 30 total pages for the entire submission. Request respondents submit one (1) hard copy of their RFI response via mail to USJFCOM J33, 1562 Mitscher Ave, Suite 200, Norfolk, VA 23551-2488, Attention: LCDR Mike Fisher, JFCOM J33. In addition, submit an electronic version of RFI responses via e-mail to michael.fisher@jfcom.mil Email responses may not include any of the following types of files because the JFCOM email server currently blocks the following unclassified/XNet files from external sources: .JPG, .JPEG, .386, .EXE, .AD, .ADE, .ADP, .ASP, .BAS, .BAT, .CHM, .CMD, .COM, .CPL, .CRT, .HLP, .HTA, .INF, .INS, .ISP, .JS, .JSE, .LNK, .MDB, .MDE, .MSC, .MSI, .MSP, .MST, .PCD, .PIF, .REG, .SCR, .SCT, .SHB, .SHS, .URL, .VB, .VBE, .VBS, .VSS, .VST, .VSW, .WS, .WSC, .WSF, .WSH, .XSL, .ZIP. Information should be submitted no later than COB 29 July 2005. Direct questions concerning this RFI to LCDR Mike Fisher (michael.fisher@jfcom.mil).
- Record
- SN00838197-W 20050630/050628212531 (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 |