DMS has different options that can be enabled to reflect different deployment methodologies. Before starting a project decisions need to be made regarding the deployment methodology.

• What is the total number of deployments. How long is the project expected to take.
• How will deployments be grouped to make the process more efficient (by floor/building/business unit)
• How and when will deployments take place and be scheduled
• Will you have users who frequently change their place of work?
• What is the maximum number of concurrent deployments for a group
• Will Asset Tracking (chain of custody compliance) be used?
• What is the Asset Recovery process?
• Where will computers be built? (Central Country Location, Central Building Location, at Users Desk)
• Who is responsible for assigning new computers to a deployment and when?
• Will the user verify the data before a deployment (individuals, or a group administrator)
• Will the user self-serve deployment dates, hardware or software
• Will the customer want email communication to users about their deployments
• What are the toll-gate tasks that need to be completed before deployments can take place
• Are there extra fields that need to be stored in DMS
• Will Build Sheets be used, what data needs to be on them. Will they be used as sign off for completed build. Will they need a bar code and of what.
• What data/rules must be complete before a deployment can take place
• What additional reports will be needed
• Will emails, User Portal or Validation Portal be multi lingual
• What fail codes will the project use, which ones will be available to Engineers and which ones will incur charges to the customer
• What password policy does the customer have
• Will the DMS service be able to run from the cloud, or will an on-site instance be needed
• Who will be responsible for providing the data that is imported into DMS, at what points will this data be ready
• Who will be using the DMS console, and have they had the necessary training