Skip to main content
Office of Research and Innovation
Enterprise Research Administration (ERA)

Progress

The graphic below shows the progress of each module's implementation, which can be broken into seven phases.

Module Development Phases

100 - Go Live Continuous Improvement
0 - Requirements Gathering and Business Process Mapping
0 - Requirements Gathering and Business Process Mapping
100 - Go Live Continuous Improvement
100 - Go Live Continuous Improvement
15 - Onsite Module Overview and Business Process Mapping
100 - Go Live Continuous Improvement
0 - Requirements Gathering and Business Process Mapping
  1. 1
  2. 2
  3. 3
  4. 4
  5. 5
  6. 6
  7. 7

  1. Requirements Gathering and Business Process Mapping

  2. Onsite Module Overview and Business Process Mapping

  3. Prototype Build, Training, and Review

  4. Revision Cycle and Project Team Testing

  5. User Acceptance Testing and Data Conversion

  6. Training and Go Live Preparation

  7. Go Live Continuous Improvement

Module Development Phases Explained

During this phase, subject matter experts work with InfoEd to ensure workflows are created accurately, based on current business processes, and that the vendor is made aware of the requirements — and improvements — desired of the new system. InfoEd then uses this information to begin configuring its existing software to meet NC State’s unique needs.

During this phase, InfoEd representatives present and begin to demonstrate the preliminary module iteration to both subject matter and IT experts, who then have their first opportunity to evaluate and provide feedback on the software. Following these demonstrations, select users will continue to interact with the early version of the software, to further evaluate it and get a better understanding of how it operates.

During this phase, OIT and InfoEd use the feedback received thus far to finalize the module prototype. After a number of workshop meetings, InfoEd representatives perform in-depth demonstrations with an emphasis on ensuring the users involved at this point are familiar with every aspect of the system’s functionality. At this point in the process, there is still ample opportunity for feedback and subsequent revision prior to go-live.

During this phase, the module will undergo a series of iterative revisions as the remaining members of the project team who have yet to interact with and provide feedback on the system become involved.

During this phase, end-users ensure the system performs as intended in real-world scenarios and then provide feedback. This is when a larger number of affected users will begin to interact with the software. Meanwhile, data conversion will also begin to take place.

During this phase, affected users will begin to be trained to use the new system. Other important aspects of go-live preparation include validation of data conversation — and making any last-minute tweaks that may be required.

During this phase, the module being implemented will launch — and affected users will begin to make the switch to the new system. Keep in mind, however, that the system will be continually updated and improved.