Best practices with MS Project Importing

[JR Laprime]

We are looking for guidance on best practices for importing Microsoft Project files into ServiceNow. Specifically, we are interested in:

• Individual project importing best practices
• Batch MS Project file importing via MS Project Server and/or Project Online
• Scheduled import process for all active projects

While I recognize ServiceNow has significantly improved the usability and end-user experience with the new Project Workspace, our organization will be relying on MS Project for detailed project schedules due to advanced schedule analysis requirements (such as Monte Carlo simulations, SRA Schedule Risk Analysis, and DCMA 14-point schedule assessments) and ServiceNow user licensing limitations.

However, we want to leverage the new Resource Assignments functionality to project WBS/tasks records to improve our resource forecasting abilities as compared to legacy Resource Management.  Therefore, synchronizing schedules between MS Project and ServiceNow SPM will be key.

Additional Context:

• We are not yet using the new Project Workspace in ServiceNow.
• We are interested in implementing a standard MS Project import process to synchronize project schedules between MS Project and ServiceNow improving resource forecasting based on new features with Resource Assignments.
• We have advanced schedule analysis requirements, such as Monte Carlo simulations, SRA Schedule Risk Analysis, and DCMA 14-point schedule assessment.

Any insights or guidance from the community on best practices with MS Project Importing would be greatly appreciated!

[StephanieN]

I would be interested as well. Especially with MS Project Professional and Planner roadmap for Microsoft is changing.