| Project Sponsor UARK Email |
Only UARK email addresses are accepted in this form field. See Project Sponsor for more details. |
username@uark.edu |
| Project Sponsor |
The person who has the authority to make decisions on the project on behalf of their department. Ultimately, the Project Sponsor is responsible for coordinating and approving project funding, deliverables, timelines, and signing off on completions. |
[Auto-populated from Project Sponsor UARK Email] |
| Department |
The Project Sponsor’s department. If the Sponsor belongs to multiple departments, the department listed here should be the one that is funding the project. |
[Auto-populated from Project Sponsor UARK Email but can be edited in the Projects app on TDWorkManagement] |
| Primary Project Manager UARK Email |
Only UARK email addresses are accepted in this form field. See Project Manager for more details. |
username@uark.edu |
| Primary Project Manager |
The person who is responsible for managing and updating the project on TDWorkManagement platform. This person must have the security role of Project Manager (PM) on TeamDynamix Users Portal. |
[Auto-populated from Primary Project Manager UARK Email] |
| Project Manager Department |
The Project Manager’s department. If the Project Manager belongs to multiple departments, the department listed here should be the one that is funding the project. |
[Auto-populated from Primary Project Manager UARK Email, but can be edited in the Projects app on TDWorkManagement] |
| Project Name |
A unique, brief title for the Project that makes it easy to discern from other projects.
A good naming convention would be: [DEPT/Team] – [System / Process] – [Main Goal of the Project]
|
UITS-IT Training-Develop AI Training Curriculum for Staff |
| Requested Start Date |
This is the date the project started (past) or will start (future). |
08/01/2026 |
| Requested End Date |
This is the date that the project is expected to be completed by. |
08/31/2026 |
| Project Description |
Summary of who, what, when, where, why, and how of a project.
Project description should briefly describe the project, including any existing issues or problems that will be solved, opportunities that will be reached, or benefits that will be gained. Explain how this project is necessary to achieve these goals.”
If you’d like a template: [Department] is implementing [solution/change] between [start date] and [end date]. The project involves [stakeholders]. Currently, [problem/opportunity]. This project will [expected outcome/benefits] by [high-level approach]. The effort is necessary because [business need/strategic goal].
|
The Human Resources department is implementing an automated employee onboarding solution to replace several manual processes currently managed through email, spreadsheets, and paper forms. The project will be completed between September 2026 and January 2027 and will involve Human Resources, IT Services, and hiring departments across campus. Currently, onboarding activities require significant manual effort, resulting in delays, duplicate data entry, and inconsistent communication with new employees. The new solution will automate onboarding workflows, standardize required tasks, and improve visibility into onboarding progress. |
| Current Status |
- New – Has not been started yet.
- In Process – Has already been worked on or initiated
|
- New is used for future projects
- In Process is used for current or backdated Start Date projects.
|
| Data Types |
Data types are based on University Data Classification policy.
- Public – Information to which the general public may be granted.
- Sensitive (Internal) – Information not intended to be shared with the public, absent a FOIA request.
- Highly Sensitive – Information, if compromised, could result in serious personal, financial, or reputational harm to individuals or to the university in whole or in part.
- Restricted – Information regulated by federal, state, or local statutes, regulations, industry standards, or contractual obligations.
|
If you work with multiple types of data, always use the highest security classification.
- Public used for anything already published on a public website
- Sensitive used for information on university operations, contracts, legal matters, audits, internal memos, emails, reports, infrastructure diagrams or data, business partner information
- Highly Sensitive used for personal identifiable information (PII) - outside of public directory information, Tax information, Donor records, Financial records, Research prior to publication
- Restricted used for data governed by HIPAA, FERPA, GDPR, GLBA, PCI-DSS, etc.
|
| Project Impacts: Area or Department Benefiting from the Project |
Four letter department code of the department most benefiting from the completion of this project. |
UITS |
| Project Impacts: Systems Affected |
These are systems that are affected upstream or downstream of the project completion.
- Enterprise Resource Planning (ERP) – When a project impacts the university's ERP
- Hardware – When a project impacts hardware usage on campus
- Network - When a project impacts network or infrastructure usage on campus
- No Systems Affected - When a project does not impact any system
- Software - When a project impacts software availability or usage on campus
- Unknown- When a project impacts are unknown
|
- Enterprise Resource Planning (ERP) used for anything related to Workday
- Hardware used for upgrading computer to implement Windows 11
- Network used for upgrading/adding AP
- No Systems Affected used for no system is affected
- Software used for when a new software is implemented
- Unknown used for when it is unknown if the project will impact a system
|
| Project Impacts: Processes Affected |
These are process that are affected upstream or downstream of the project completion.
- Business – An activity or set of activities that accomplish a specific organizational goal
- No Related Processes – No process affected by the project completion
- Operational – An activity or set of activities that allow a team/dept to render services
- Technical –An activity or set of activities that requires technical steps that computers, systems, applications, or IT staff perform to make a service work
- Unknown – Used when at the moment of form creation there is no known process affected
|
- Business used for HECVAT/VPAT software approval process
- No Related Processes used for when there are not processes affected
- Operational used for when a team is being onboarded to TeamDynamix for their service management needs
- Technical used for the automated workflow for change enablement process on TeamDynamix
- Unknown used for currently unknown
|
| Is a vendor involved as an active participant in the project? |
Yes- the vendor is involved in regular updates and a collaborator of the project.
No – the vendor is only a resources not an active collaborator or not a participant at all. |
- Yes used for when the vendor is a collaborator. Example Microsoft for Cloud infrastructure implementation.
- No used for when LinkedIn Learning representative is used as a resource for answering Admin questions.
|
| Notes and additional details |
Any supplemental information that might be valuable information to know. |
This project is a product of the IT Staff SWOT analysis for increasing collaboration, transparency, and communication. |