IT Project Management

The AIS Project Management Processes have evolved for 3 key reasons. First, through listening to customer and internal stakeholders to address a series of pain points, with similar roots, our organizational structure and responsibilities, based on many conversations over the last year and patterns identified among them. Second, to facilitate significant company growth, by increasing top-line capacity, increasing the bottom-line through efficiency, with the ability to scale head count internally. Third, to encourage personal growth and employee retention through additional roles and paths to leadership at AIS.

Example Project Plan

  • Verify All Requirements Are Provided
    • Return Completed List Of Requirements To AIS
  • Kickoff Call
    • Review SOW
    • Client Contacts And Change Management Process
    • Client Environment Details
    • Project Timeline
    • Identify Next Steps
  • Access Control Requirements
    • Identify Customer Restrictions On Network Admin Console Authentication Method (i E Local Password, RADIUS, Etc)
  • Discovery
    • Discover And Document IT Environment Details And Credentials Related To This Project
    • Determine Regular Maintenance Window For Device Outages Resulting From Moves/adds/changes/upgrades
    • Document Related Environment Details And Existing Equipment Configuration
    • Identify Key Risk Factors
    • Assessment And Discovery The Project Team Will Perform A Review Of Existing Environment Identified In The Customer Designated Locations
    • Identify Other Configuration Parameters As Necessitated By The Environment And As Dictated By Seller Best Practices
    • Identify Affected Entities Including, But Not Limited To Virtual Hosts, Virtual Machines (w/ OS), Servers (w/ OS), Server Switching, Virtual Networking, Microsoft And Other Related Software Licensing Details, Switches/Routers/Firewalls And Network Topology
  • Provide All Necessary Access Credentials
  • Project Management
    • Coordinates And Facilitates Kickoff, Status And Close Out Calls
    • Creates And Distributes Escalation And Contact Lists And All Necessary Information Needed Per The Scope Of Work
    • Facilitates Any Necessary Change Processes And Administrative Tasks
    • Leads Scheduling And Logistics Planning
    • Oversees Project Documentation
  • Preparation
    • Confirm Physical Installation Locations Of Equipment At Designated Locations
    • Identify Customer And Third Party Managed Systems Impacted By Implementation
    • Review Implementation And Test Plans With Customer, Adjust As Necessary
    • Define Notification And Escalation Procedures
    • Identify Cutover Windows For Critical Milestones
  • Update Environment Documentation
  • Cutover
    • Confirm All License And Support Agreements And Entitlements Are Properly Applied To Customer’s Account Provided By Manufacturers
    • Remotely Configure And Test New Environment According To Accepted Implementation Plan
    • Schedule Engineers For Implementation And Cutover To New Configuration
    • Update Software On All Related Servers If Available And To Test Operation Prior To Cutover
    • Implement New Configuration Including, But Not Limited To Configuration Of Active Directory, VLANs, Physical Network Interfaces, Network Addressing, Secure Access, And Network Management Parameters Based On The Design Phase Of The Project
    • Decommission Legacy Equipment Settings As Needed Per Design Phase
    • Engineer To Perform Customer Approved Test Plan At Each Of The Customer Locations
    • Resolve Configuration Issues As Needed
    • Conduct And Confirm Final Functionality Testing With Customer
  • Submit Ad Hoc Support Requests
  • Complete Testing Plan
    • Test Data Flow And Access To All Relevant Data Identified In The Testing Plan

Last modified October 4, 2021