842572309 - DISA Mobility Device Migration RFI.docx

REQUEST FOR INFORMATION

Defense Information Systems Agency (DISA)/Emerging Technology Directorate/ Procurement Services Directorate is seeking information from industry to assist with the development and planning of a potential new requirement.

THIS IS A REQUEST FOR INFORMATION (RFI) NOTICE ONLY. THIS IS NOT A REQUEST FOR PROPOSALS (RFP). NO SOLICITATION IS AVAILABLE AT THIS TIME.

1. Overview/Purpose/ Description of Procurement

DISA manages and operates the Department of Defense (DoD) Mobility Unclassified Capability (DMUC) to enable mobile access to DoD Enterprise resources, capabilities and services for decisionmakers, warfighters, and coalition partners. The DoD Mobility Program Management Office mission is to extend enterprise services to unclassified mobile devices in order to deliver a fully operational secure Mobility Enterprise Service to DoD. Over the past five years, DoD started moving toward leveraging Office 365 (O365) and Microsoft Intune to provide a comprehensive solution for managing and securing mobile devices. Our objective is to enable DoD personnel to access sensitive information and applications from anywhere, while ensuring the security and integrity of DoD's mobile ecosystem and achieving significant cost efficiencies through reduced infrastructure and management costs, improved resource utilization, and streamlined IT operations.

As the DoD continues to evolve its mobility capabilities, it recognizes the need to migrate from its legacy Mobile Device Management (MDM) platform, Ivanti. The Government is seeking recommendations from vendors on innovative strategies for migrating mobile devices securely to the Intune MDM platform, while ensuring compliance with mobility regulations, data retention requirements, policies and enabling future operational efficiencies. The desired outcome is a seamless and cost-effective transition that enhances the effectiveness, efficiency and security of the DoD's mobile enterprise service.

2. Scope of Effort

The scope of effort for the migration of mobile devices from the legacy Ivanti MDM platform to the new MDM, Intune environment encompasses a comprehensive and complex series of tasks. The primary objective is to automate, as much as possible, the migration of approximately 35,000 mobile devices, comprising both Android and iOS devices, currently managed by Ivanti MDM. This includes about 31,500 iOS devices and 3,500 Android devices, all of which are distributed across various locations within the Continental United States and Outside the Continental United States, including but not limited to, key sites at Ft. Meade, San Antonio, Columbus, Ogden, Mechanicsburg, and St. Louis, as well as numerous locations of DoD 4th Estate Agencies.

Key Components of the Scope of Effort:

1. Pre-Migration Assessment: Conducting a thorough assessment of the current Ivanti MDM setup, including device configurations, policies, and security settings to understand the baseline from which the migration will occur.

1. Solution Development: Identifying, designing, or developing an automated tool or service capable of migrating devices from the legacy Ivanti MDM to the new MDM environment.

1. Over-the-Air (OTA) Migration Capability: The preferred method of migration is Over-the-Air, minimizing the need for physical access to devices and reducing downtime.

1. On-Site Migration Support: For devices that cannot be migrated via OTA due to technical limitations or other constraints, the solution must include provisions for on-site support at the specified DISA and 4th Estate Agency locations.

1. Device Data Integrity and Security: The migration process must maintain the integrity of all device data, ensuring that no data is lost, corrupted, or compromised during the transition.

1. Device Enrollment and Configuration: Post-migration, all devices must be properly enrolled in the new MDM Intune environment with appropriate configurations, including supervision for iOS devices and Work Profile setup for Android devices to maintain device security and management capabilities.

1. Project Management and Reporting: Effective project management is crucial to ensure migration stays on track.

1. Training and Documentation: Providing comprehensive documentation of the migration process.

1. Post-Migration Support: Offering support post-migration to address any issues that may arise, ensuring that all devices are functioning as expected within the new MDM Intune environment.

3. Technical Characteristics

The technical requirement for migrating managed mobile endpoints from one MDM solution to another, specifically from Ivanti Endpoint Manager Mobile (EPMM) to Intune, involves several key considerations. Firstly, Apple devices, which are enrolled through Apple Business Manager's Device Enrollment Portal (ABM DEP), must retain supervision on the MDM profile post-migration. This ensures continuous management and security oversight. For Android devices, migration must enroll them as Corporate Owned Personally Enabled (COPE) Work Profile, ensuring a clear distinction between personal and corporate data and applications. A critical aspect of this migration is maintaining device data integrity. If possible, migration must occur without requiring a factory reset, but if a reset is unavoidable, an automated backup of all device data to a government-managed source must be performed. During the transition, devices must be locked down, with all non-essential apps disabled or hidden from users to prevent unauthorized use. Furthermore, once devices are migrated to the new MDM, the devices must be configured in a way that prevents devices from leaving management, either by wiping the device or removing the MDM profile. To ensure visibility and control over the process, tracking the progress of all mobile devices through migration, with status reporting via a dashboard or similar tool, is essential. This comprehensive approach is designed to ensure a secure, efficient, and data-preserving transition of managed mobile endpoints to the new MDM solution.

4. Requested Information The following requirements need to be addressed to meet DISA’s objectives. The vendor shall provide a detailed response on how each requirement is addressed.

a. General

i. Describe your company’s years of experience in migrating mobile devices from Ivanti MDM platform to Intune.

ii. Describe your company’s years of experience in migrating mobile devices from any MDM to Intune.

iii. Explain the level of end user interaction is required during the migration.

iv. Describe if the migration can be performed remotely (ex. Over the Air). If so, explain the migration process.

v. Explain what types of reporting and auditing features are included in your migration tool.

vi. Provide your company’s pre-migration assessments or readiness list checks.

vii. Describe if your company’s solution is able to support devices enrolled via Apple Automated Device Enrollment (ADE).

b. Technical

i. Provide your company’s migration support for both Android Enterprise and Apple iOS devices. Provide details on the differences in the migration approach for each platform limitation.

ii. Explain how your migration solution automates any part of the unenrollment and re-enrollment process.

1. Describe your company’s solution/tool data retention for original mobile device and how it can handle the following: preservation of user settings, app reinstallation, certificates, profiles and security policies

iii. Describe your company’s approach to data privacy and security during the migration process. Explain how your tool ensure security and provide oversight migrating from one MDM to another.

iv. Describe your company’s approach to planning and migrating Android and iOS devices (mobile and tablet) from DMUC MDM Ivanti to an Intune MDM solution. Provide details on the supported versions and any limitations.

v. Explain how your company’s tools and services move managed mobile endpoints (iOS and Android) from one MDM to another (ex. Ivanti EPMM to Intune).

vi. Describe how your company approaches migrating Apple devices that must maintain supervision on the MDM profile after migration.

vii. Apple devices are enrolled via ABM DEP

viii. Describe how your company migrates Android devices that must be enrolled as COPE Work Profile.

ix. Discuss how your company’s migration tool maintains device data integrity and minimal disruption to end-users during the migration process. Provide how your company’s tool migrates devices without a factory reset. If a factory reset is required, explain your approach how to perform backup to all device data needed to be performed in an automated fashion to a government managed source.

x. Explain how your company’s migrate Devices that must be locked down while not managed, all apps not required for the migration should be disabled/hidden from the user to prevent use.

xi. Explain how your company migrate Devices that should not be able to leave management, either through wiping or removing MDM profile, once migrated to the new MDM.

xii. Provide how your company tracks the progress of all mobile devices through migration and provide status reporting (e.g. dashboard).

c. Cost and Licensing

i. Describe your pricing model (e.g., per device, per migration, subscription-based).

ii. Explain the estimated costs for migrating per device (up to 35k listed above scope).

iii. Describe the separate costs for the following efforts: Licensing the migration tool, Professional services, Training and support.

iv. Identify any volume discounts or government/enterprise pricing models.

v. Explain any recurring costs for post-migration.

d. Schedule and Support

i. Explain the estimated timeline to migrate up to 35K devices (How long per device)

ii. Describe your typical lead times to begin a migration project.

iii. Explain how your tools and services accommodate phased or staged migrations.

iv. Describe your company’s support model (e.g., 24/7 support, dedicated account manager).

v. Discuss your company’s training or knowledge transfer to internal IT teams prior or during migration.

e. References and Case Studies

i. Provide examples of past migration projects of similar scope and complexity.

ii. Share customer references, especially for migrations involving the MDMs we are transitioning between.

iii. Attach any case studies, whitepapers, or documentation that support your expertise.

RESPONSE GUIDELINES:

Interested parties are requested to respond to this RFI with a white paper. Submissions cannot exceed 10 pages, single spaced, 12-point type with at least one-inch margins on 8 1/2” X 11” page size. The response should not exceed a 5 MB e-mail limit for all items associated with the RFI response. Responses must specifically describe the contractor’s capability to meet the requirements outlined in this RFI. Oral communications are not permissible. SAM.gov will be the sole repository for all information related to this RFI.

Companies who wish to respond to this RFI should send responses via email no later than May 14, 2025 at 12:00pm Eastern to angela.k.zang.civ@mail.mil and kari.r.wuebbles.civ@mail.mil

INDUSTRY DISCUSSIONS:

DISA representatives may choose to meet with potential offerors and hold one-on-one discussions. Such discussions would only be intended to obtain further clarification of potential capability to meet the requirements, including any development and certification risks.

QUESTIONS:

Questions regarding this announcement shall be submitted in writing by e-mail to angela.k.zang.civ@mail.mil and kari.r.wuebbles.civ@mail.mil. Verbal questions will NOT be accepted. Answers to questions will be posted to SAM.gov. The Government does not guarantee that questions received after May 12th at 8am Eastern will be answered. The Government will not reimburse companies for any costs associated with the submissions of their responses

DISCLAIMER:

This RFI is not a Request for Proposal (RFP) and is not to be construed as a commitment by the Government to issue a solicitation or ultimately award a contract. Responses will not be considered as proposals nor will any award be made as a result of this synopsis.

All information contained in the RFI is preliminary as well as subject to modification and is in no way binding on the Government. FAR clause 52.215-3, “Request for Information or Solicitation for Planning Purposes”, is incorporated by reference in this RFI. The Government does not intend to pay for information received in response to this RFI. Responders to this invitation are solely responsible for all expenses associated with responding to this RFI. This RFI will be the basis for collecting information on capabilities available. This RFI is issued solely for information and planning purposes. Proprietary information and trade secrets, if any, must be clearly marked on all materials. All information received in this RFI that is marked “Proprietary” will be handled accordingly. Please be advised that all submissions become Government property and will not be returned nor will receipt be confirmed. In accordance with FAR 15.201(e), responses to this RFI are not offers and cannot be accepted by the Government to form a binding contract.