Loren Data's SAM Daily™

FBO DAILY ISSUE OF FEBRUARY 05, 2009 FBO #2628
SOLICITATION NOTICE

58 -- Movement Tracking System - Request for Information

Notice Date

2/3/2009
 

Notice Type

Presolicitation
 

NAICS

334220 — Radio and Television Broadcasting and Wireless Communications Equipment Manufacturing
 

Contracting Office

ACA, ITEC4, Directorate of Contracting , 2461 Eisenhower Avenue, Alexandria, VA 22331-0700
 

ZIP Code

22331-0700
 

Solicitation Number

W91QUZ-09-RFI-0001
 

Response Due

3/6/2009
 

Archive Date

5/5/2009
 

Point of Contact

James Goodwin, 703-325-4374<br />
 

Small Business Set-Aside

N/A
 

Description

Movement Tracking System (MTS) Request for Information (RFI) 3 February 2009 1.0 RFI INFORMATION: 1.1 This is not a Request for Proposal (RFP). This is a Request for Information (RFI). Responses to this notice are not offers and cannot be accepted by the Government to form a binding contract. The RFP number W91QUZ-09-RFI-0001 was entered as a requirement to allow the posting of this RFI. Therefore, the use of W91QUZ-09-RFI-0001 is not an indication of future action, beyond this RFI. This is a request for information only, as defined in the Federal Acquisition Regulation (FAR) at 15.201e. It does not constitute a Request for Proposal (RFP) or a promise to issue an RFP in the future. Responses to this notice shall not be construed as offers and cannot be accepted by the Government to form a binding contract. The U.S. Government will not pay for any information or administrative cost incurred in response to this RFI. All costs associated with responding to this RFI will be solely at the interested partys expense. Not responding to this RFI will not preclude participation in any future RFP, if issued. This action seeks information for a potential follow-on to the current MTS contract that expires 12 July 2010. 1.2 The Program Executive Office, Enterprise Information Systems (PEO-EIS), the Product Manager Movement Tracking System (PdM MTS), and other Department of Defense (DoD) agencies seek information and comment regarding potential strategies for the design, development, installation and operation and maintaining of a follow-on to the current MTS contract involving GPS, commercial computer equipment, systems support software, installation kits (A-Kits), air time, integration, maintenance, and technical support and services to provide world-wide two-way data communications and geo-location capability between mobile units (Handheld Mobile Units (V1), and Vehicle Mounted Mobile Units (V2)) and designated control points (Control Stations). While the reengineering effort is not assured, the multi-service DoD team seeks to investigate potential solutions and architecture approaches that identify best practices, migration strategies, and technologies that will advance the MTS. PEO-EIS anticipates awarding an MTS follow-on contract before February 2010. 2.0 SUBMISSION INSTRUCTIONS: Responses to this RFI will be in the form of a White Paper, not to exceed fifteen (15) single-sided pages, in Times New Roman 12 pitch font, and supported by a Microsoft Power Point briefing, including notes, not to exceed ten (10) slides. Contractors are urged to limit marketing material in order to provide more substantive information in their response. Responses are to be submitted in Microsoft Word, 2003 compatible format, via e-mail to two addressees: Sharyn Timms at sharyn.timms@us.army.mil and Robert Straub at Robert.straub@us.army.mil, not later than 4:00pm EST on Fri, 6 March 2009. Please note-this deadline will not be extended. 3.0 MTS BACKGROUND: The MTS is a worldwide, data communications capability for locating and managing the movement of logistics and combat support vehicles. MTS will provide in-transit visibility and velocity management of logistics and other Army combat support assets anywhere from the sustaining base to the theater of operations. MTS will be used to support missions throughout the full range of military operations from peacetime to war. MTS will provide commanders with near real-time data for location and status of logistics and combat support movement. MTS will provide key capabilities to enable and enhance in-transit visibility and velocity management such as the ability to reroute supplies due to changing priorities, helping avoid hazards, and maintaining updated unit status. The MTS capability will improve the efficiency and the effectiveness of distribution of resources and assets. 3.1 The Information Technology and Electronic Commerce Commercial Contracting Center (ITEC4), Department of the Armys contracting office, competitively awarded the original MTS contract in June 1999, with a follow-on contract awarded in August 2007. The final option period on the current contract will expire on 12 July 2010. The FSC Code for the current contract is 5895. NAICS Code is 334220. 4.0 ADDITIONAL REFERENCE MATERIAL: The Government may make reference/reading material available. If reference/reading material is made available, an amendment to this notice will be issued with instructions. 5.0 ACQUISITION OBJECTIVES: 5.1 To the extent practical, the equipment shall represent state-of-the-art technology. The current system provides in-transit visibility and velocity management of logistics from the sustaining base to the theater of operations. MTS will support missions throughout the full range of military operations from peacetime to war. It is a critical logistics communications and tracking system that provides detailed In-Transit Visibility (ITV) from the vehicle-level and provides the logistics soldier with navigational aids and a means for text communications from anywhere in the battle space. The MTS satellite based architecture provides long-haul communications and tracking far beyond the capabilities of conventional line-of-sight technologies. The follow-on system will start where the current system ends. MTS fills the void that has historically existed and still exists today for logisticians. MTS allows the means for unity of command through central control and monitoring of dispersed fleet assets; increased velocity through the direction/re-direction of critical, limited assets; and near-real-time logistical situational awareness through ITV of assets on the battlefield. MTS enhances the capability of logistics distribution assets to survive and successfully complete their battlefield missions. MTS does not displace or replace any existing communications, tracking, or logistics system. Ordering for the current system ends in July 2010. 5.2 The newest version of MTS incorporates the latest vehicle-tracking technologies, and new Automatic Identification Technology (AIT) Radio Frequency Identification (RFID). AIT-RFID will allow systems to begin delivering near-real-time insight into materials being transported by and in close proximity to Army vehicles outfitted with MTS. The customer community for MTS is all common user logistics transport (CULT) and select command and control Combat Support and Combat Service Support tactical wheeled vehicles in the Army force structure. MTS will support military operations on a world-wide basis in peacetime, peacekeeping and wartime operations. MTS system components shall be capable of operating without the use of direct telephone (land line or cellular) connections or LAN/WAN/INTERNET direct connectivity. The primary acquisition objective of MTS is to obtain a solution that efficiently, effectively, and economically provides and maintains a standard Information technology infrastructure to support the Government in meeting the MTS missions. As such, the Government anticipates that some or all of the following objectives of this requirement will be as follows: a. Building on the current MTS solution (hardware, software, infrastructure) to provide a best-in-class, secure, interoperable, scalable, and upgradeable solution for MTS that focuses on a user-friendly interface. b. Ensure a seamless/transparent transition from the current MTS architecture to the proposed architecture and from the existing contract to this contract, improving current process standards and procedures. c. Under a performance-based arrangement, award to a contractor committed to delivering a highly reliable, user friendly, timely, and secure IT solution that meets or exceeds customer requirements and expectations. d. Provide evolutionary, robust and user-friendly enterprise portal Commercial Off-the-Shelf (COTS) toolsets capable of integrating best of breed in messaging, work flow, position reporting, ITV and other services, as required. e. Assure that MTS services are provided to any operational MTS user anywhere, at any time to include a network-challenged environment. The system must be responsive and reliable to users at the network edge. Provide responsive and competent user assistance available 24/7/365. f. Ensure security compliance/information assurance, including physical security, for MTS, its data, and users. Relevant guidelines include, but are not limited to, DoD 8500.1, 8500.2, AR 25-2, FIPS 140-2 and the Army Approved Information Assurance Products List (AIAAPL). g. Provide network architecture that is scalable to 100,000 users. h. Ensure MTS continues to operate at required levels of operational availability (including Business Continuity Plan and Disaster Recovery Plan (BCP and DRP) during any software or hardware changes, upgrades or disasters. i. Ensure new capabilities are adequately tested to prevent adverse impact to operations or the users experience during portal modifications and upgrades. Provide user training to increase awareness of MTS functionality. j. Provide market research and recommendations focused on continuous capability improvements. Provide a roadmap for future MTS improvements with an established and predictable release cycle. k. Provide Help Desk services for customer service and technical reporting purposes. Operations should be 24/7/365 and available to all MTS users. Offeror must propose performance standards applicable to this type of operation. 5.3. Consideration should be given to the following technical areas: (a) The vendor is invited to submit comments or plans on how the current/planned system computing environments will be leveraged to enhance vehicle availability, maintenance scheduling, or serve as a tool to aid in the remote repair of disabled platforms. Given the digital age that our current fleet operates in, the vendor should be able to explain how they will leverage this digital sensor rich environment and likewise how the company would plan to compensate for the analog legacy fleet. (b) The vendor is invited to submit comments as to how they plan to compensate for short term outage (blocked view to the satellite) and a methodology of providing 'mesh' coverage to non-satellite communications equipped platforms that belong to the same element or region or organization. The vendor should document this plan of multi-path connectivity and include it as an expandable feature that could be bought separately from the base satellite coverage of the program. This enhancement of multipath from a platform should also be looked at for bandwidth efficiencies, low priority traffic that could be stored for short terms and for short to intermediate distance (1KM - 5KM) coverage. This redundancy if enacted should be able to independently perform (satellite blocked), perform in concert with the satellite communications (priority based) or perform only as needed (standby). (c) The vendor is invited to submit comments or plans on the use of Joint Variable Message Format (JVMF) and informational products from the available and emerging battle command systems to provide the MTS user and control station operator an unclassified situational awareness (SA) for force protection. The products include overlays, symbology, geo-fencing and non-tracked unit/organization information. Any plan should include a methodology informational management of these products (e.g. - keeping the products versioned and updated across a wide area dispersed fleet that isn't always on the network, but still require the information once brought on line). 6.0 ACQUISITION STRATEGY ISSUES: Sources will be expected to provide hardware, software, installation, training, post-installation support, and satellite services worldwide. This support effort includes, but is not limited to: program management, requirements definition, technology insertion, systems development and procurement, systems integration, installation, fabrication, testing, evaluation, certification, studies and analysis, technical data management, configuration management, operations, maintenance and logistics support, training, site surveys, engineering studies and documentation, integration/interface impact studies, relocation of equipment, CONUS and OCONUS shipping, development of A-Kits for several different vehicle-types, demonstration support, and, briefing support. The Government is looking for the ability to fulfill the above requirements, plus incorporate existing fielded systems within the proposed architecture. 7.0 PERFORMANCE-BASED ACQUISITION (PBA): The MTS contract, if awarded, may use performance-based service contracting principles including use of a Statement of Objectives or a Performance Work Statement. 8.0 QUESTIONS FOR INDUSTRY RESPONSE: The Government is requesting comments on the above options, and is interested in obtaining the following information from industry to consider in determining its acquisition strategy and development of the RFP: 8.1 How difficult would it be to implement a solution in which the Government provides a limited set of equipment as GFE? In this event the Government would likely not be in a position to acquire or lease all equipment necessary for MTS to function. Rather, the contractor would be required to provide MTS as a service using its own resources. Please explain the advantages and disadvantages with this approach. 8.2 With regards to FAR Subpart 27, what other factors should be considered regarding software licenses and Configuration Management? How would you recommend handling software licenses issues and any software that might be developed/enhanced under this effort? 8.3 What specific detail or additional information beyond the information provided in the reading room is needed in order to bid on the complete requirement? 8.4 What contract type(s) would be most beneficial to both the Government and the contractor? 8.5 How long would it take to transition from the existing contract to the new contract? 8.6 What logical portions of work are suitable for small business (SB) participation on an effort of this size? What SB subcontracting goals have you achieved on similar efforts? 8.7 What contractual incentives would motivate outstanding performance? In what areas can performance most effectively be incentivized? 8.8 How would you monitor MTS service availability and quality? 8.9 With regards to future trends, what should the Government consider in assessing future capabilities? 8.10Does your organization have the resources and expertise available to perform the complex analysis of the MTS system needed to model system capacity and performance? Such analysis would include link budget analysis, interference analysis, network capacity modeling, identifying bottlenecks in the system, and determination of the best satellite bandwidth options for a given area. 9.0 VENDOR QUESTIONS: Any questions regarding this RFI should be submitted via e-mail to the addressees listed above NOT LATER THAN close of business on Thursday, 12 February 2009. If any questions are received, responses will be consolidated and posted as an amendment to this notice. Telephonic questions will not be accepted. End of RFI
 

Web Link

FedBizOpps Complete View
(https://www.fbo.gov/?s=opportunity&mode=form&id=605eb94dd45725625e0308506eafc41a&tab=core&_cview=1)
 

Place of Performance

Address: ACA, ITEC4 Directorate of Contracting , 2461 Eisenhower Avenue Alexandria VA<br />

Zip Code: 22331-0700<br />
 

Record

SN01742988-W 20090205/090203215510-605eb94dd45725625e0308506eafc41a (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 |