All Lone Star College technology-related projects and purchases require pre-approval by the Office of Technology Services (OTS) to ensure what is being implemented or purchased not only meets customer needs, but also aligns with Lone Star Collegeís strategic objectives, connects to our network, etc.
OTS provides a user-friendly online Project Proposal Form to apply for approval of all technology-related projects. After the form is submitted, an OTS staff member is assigned to work with the requestor to further define the project in terms of cost, scope, the number of people needed, etc. Once this information is collected and the projectís cost/benefit is more fully explored, the proposal is given to one of three governance groups for consideration.
To submit a Project Request, visit Service Now > Service Catalog > IT Project Request > Project Request to access the online Project Proposal Form.
All projects being worked on by The Office of Technology Services are managed and tracked in our Service Management Suite, Service Now (also known as SNOW). The Service Now site can be accessed internally by faculty and staff members so they can track the status of their technology-related project requests as well as see all of projects being done across the system to enhance our network and keep our services innovative and at the forefront of higher education technology.
For a real-time snapshot of OTS projects, go to the SNOW Public Report.
The Office of Technology Services (OTS) categorizes IT projects for governance (decision-making) purposes. There are four categories, and each is explained more fully below. In terms of decision-making, Enterprise Applications projects categorized as Enhancements are reviewed and recommended for funding by a Governance Group comprised of senior-level decision-makers at LSCS during the annual budget planning process. Technical Services and Campus Services projects categorized as Enhancements are reviewed and recommended for funding by the Leadership Technology Advisory Council (L-TAC) during the annual budget planning process and throughout the year.
Projects categorized as Compliance, EC/Board, or Daily Operations, regardless of their area (EA, TS or CS) are prioritized by L-TAC and OTS managers. When submitting a project request, the governance category selected for a project is important for both decision-making and reporting purposes. As a requestor, if you have any doubts when submitting your request, ask your Campus Director for guidance.
Compliance ("We must do these")
Initiatives required by state or federal law or the Texas Higher Education Coordinating Board (THECB), initiatives that are necessary to keep systems current, and initiatives related to information technology security. Examples: Tax updates; PeopleSoft bundles; Exchange upgrade.
EC/Board ("We were told to do these")
Initiatives the Executive Council or Board of Trustees has directed us to do. Examples: Texas Completes/LSCS Success; Jakarta; ID Badging.
Daily Operations ("We do these to keep things running")
Initiatives necessary to ongoing IT operations. The key difference between Daily Operations and Compliance projects is the level of urgency because it determines priority. For instance, replacing end-of-life domain controllers is part of regular IT maintenance or daily operations. But upgrading our phone system is a "must-do" because it is required to keep communications up and running for the college.
Enhancements ("If we have the money and the people, we should do these")
Initiatives that are optional due to funding and resource limitations. If we have the money, the time and the people, we do them. If we donít, we donít. We involve others in selecting and prioritizing these initiatives (see Governance above). Examples: Mediated classrooms; VDI; Portal Redesign.
Campus-specific project titles begin with the college location and may be further classified based on whether the project is at a center or which team at the campus is involved. System-wide project titles start with a 2 or 3 letter classification designating the area of OTS involved in the project and further classified by team. And last, the title is given a user-friendly short description so they are easy to understand. The basic naming convention is:
"Campus OR Area+ Team+ User-friendly short description"
Example = NH GC Active Classroom Maintenance for Fall (The project is a North Harris college project at LSC-Greenspoint to perform maintenance on active classroom equipment in preparation for the Fall term.)
Example = EA HCM Ė Update eProfile Management functionality (The project is an Enterprise Applications initiative upgrading eProfile Management functionality in the HCM module)
Health Professions Building
Kingwood Campus CH
Montgomery Campus CL
CoLocation Data Center
North Harris Campus CO
System Office FB
Tomball Campus FS
University Park GC
EA = Enterprise Application projects (the iStar, myLoneStar & PeopleSoft systems)
|CS|| Campus Solutions
(Student Information Systems modules)
|DBA||Database Administration||TAM|| Talent Acquisition Management |
(Job Application module)
|HCM|| Human Capital Management
|POR||Portal (myLoneStar system)||OTHR||Other Applications|
TS = Technical Services projects
Service Unit CO
Nework Services DC
OTS = General OTS projects
SD = Service Desk projects