MOBILE DEVICE MANAGEMENT (MDM)/MOBILE APPLICATION STORE (MAS) REVIEW OF DRAFT DOCUMENTS

This posting is a replacement to the MDM-MAS-DRAFT-DOCUMENTS posting originally made on 31 Jul 2012. This new posting is necessary in order to provide a corrected version of the Statement of Work (SOW). The original SOW incorrectly contained a FOUO legend in the Header and Footer. All other information and attachments in this posting are the same as the information and attachments provided on 31 Jul 2012. Notice of intent to issue copies of the draft documents for Mobile Device Management (MDM)/Mobile Application Stores (MAS). The Defense Information Systems Agency (DISA), Defense Information Technology Contracting Organization (DITCO) is requesting review and comments on the draft documents identified below for incorporation into a Request for Proposal (RFP), planned for release in the 4th quarter FY 2012. The purpose of the review of these draft documents is to enable the Department of Defense (DOD) to obtain feedback from industry to support a core set of MDM/MAS user needs and user-selectable enhancements. This information will be fundamental to shaping the future acquistion of MDM/MAS. The Mobile Device Management (MDM) capability should provide the application and user level "traffic cop," to enforce policy for network and end devices. The MDM institutes the policy, security and permissions that define the functions the user is enabled to conduct on the mobile device. This capability ensures the security of the entire user community is not compromised by an incorrectly configured device. A unified MDM architecture secures, monitors, manages, and supports accredited mobile devices across a range of DoD environments. This allows for malware detection and policy control of the devices. MDM also supports over-the-air electronic software distribution (ESD) of applications, remote data-wipe capabilities, remote device configuration management, and asset/property management capabilities protect against key and data compromise. The Mobile Application Store (MAS) capability is an online digital electronic software distribution (ESD) system often part of the MDM. Obtaining user application permission rights from the MDM, the MAS can deliver, update and delete applications on the mobile device without the mobile device user having to return the device for service. The MAS operates in conjunction with the MDM system. The objective of an Enterprise MAS is to optimize the functionality and distribution of mobile applications to Mobile Devices while minimizing replication, cost, and downtime. The MAS depends upon the MDM for identification of new, removed, or changed mobile devices to support the PMO Mobility function. Certification and Accreditation of mobile applications will use a distributed process to facilitate entry into the storefront. The following draft documents are provided, with interested parties are requested to provide comments following their review of the draft documents: Draft Statement of Work (SOW) - Attachment A. Draft Section B - Pricing Table. In your review of this document, venders are asked to provide information on your business models. Suggestions are also requested on any revisions to the proposed section B. - Attachment B Draft Special Instructions (Section H) - Attachment C. Draft Instructions to Offerors (Section L) - Attachment D. Draft Evaluation Factors for Award (Section M) - Attachment E. Question/Comment Matrix - Attachment F. This announcement is issued solely for information and planning purposes and does not constitute a solicitation. From the questions/comments received from the review of the draft documents, a summary of the responses will be provided with the release of the RFP. Whatever information is provided in response to this review of the draft documents will be used to assess how to proceed in the acquisition process for a MDM/MAS solution. In accordance with FAR 15.201(e), responses to this review of the draft documents are not offers and cannot be accepted by the Government to form a binding contract. All interested contractors (both large and small) are requested to provide written comments in responses to the draft documents. This Synopsis is requesting responses from both large and small businesses under the North American Industry Classification System (NAICS) Codes 541512 (Computer Design Services/$25.5M). In addition to Small Businesses, this Synopsis is encouraging responses from interested Service Disabled-Veteran Owned Small Businesses, Veteran-Owned Small Businesses, Women-owned Small Businesses, HUBZone Small Businesses, Small Disadvantaged Small Businesses and 8(a). A single award is anticipated with a one-year period of performance and two one-year option periods. A decision has not been made on whether this MDM/MAS acquistion will be set-aside for small business concerns. Comments are to be submitted on the spreadsheet provided as Attachment F to this notice. With each comment indicate the applicable document and respective section(s) from that document that pertain to the specific inquiry. All comments and suggested changes must be submitted no later than 21 August 2012, 1500 hours Central Daylight Savings Time. Submit comments on the spreadsheet provided as Attachment F to: Arthur L. Kruse, Contracting Officer, Phone 618-229-9773, e-mail arthur.l.kruse.civ@mail.mil and Kathryn Koerkenmeier, Contract Specialist, Phone 618-229-9513, e-mail, kathryn.v.koerkenmeier.civ@mail.mil DISCLAIMER: THE GOVERNMENT DOES NOT INTEND TO AWARD A CONTRACT ON THE BASIS OF THIS SYNOPSIS OR OTHERWISE PAY FOR INFORMATION RECEIVED IN RESPONSES TO THE SYNOPSIS. This synopsis is issued for information and planning purposes only and does not constitute a solicitation. Proprietary information and trade secrets, if any, must be clearly marked on all materials. All information received that is marked Proprietary will be safeguarded in accordance with the applicable Government regulations. Please be advised that all submissions become Government property and will not be returned. The Government shall not be liable for or suffer any consequential damages for any proprietary information not properly identified. All government and contractor personal reviewing RFI responses will have signed non-disclosure agreements and understand their responsibility for proper use and protection from unauthorized disclosure of proprietary information as described 41 USC 423.