CQI Steering
Committee
President's
Address
Fall 2003
President's
Address
Fall 2002
President's
Address
Fall 2001
AQIP
Agendas
Discussion
Meetings
Minutes
Process
Improvement
Teams
Dr.
Yowell's
CQI e-mail
|
|
ITS
- Academic
Lab Deployment - Minutes
|
To address
needed computer lab design, enhancement, and implementation.
David
Johnson,
Jesse Parete,
Carol Gudorf,
Mona Walters,
Phil Lootens,
Janice Michael,
Shirley Moore,
Anna Hudelson,
Betsy Kondall,
Darlene Cardinal,
Shannon Miller and
Dennis Myers
CQI Process Mapping - ITS Computer Lab
Deployment
Existing Situation
-
There is no formal process
-
Requests have been largely driven by
Tech Team meetings
-
Other requests have been verbal
requests directed to the ITS department.
-
Most labs are redone to meet
unforeseen needs.
Consequences
-
Informal process is very detrimental
to ITS' productivity because it causes severe time management issues.
-
Continually dealing with symptoms
rather than having the time to properly troubleshoot the core problem.
-
Morale of ITS, students, and
instructors suffer
-
Students/customers and instructors
suffer due to malfunctioning labs
-
Stakeholders lose due to lost
productivity by ITS staff:
-
Students
-
Instructors
-
Student Services
-
ITS staff
-
Edison Community College's reputation
is destroyed by the community.
Benefits of CQI Lab Deployment
New Formal CQI Process should:
-
be well known and published
-
be broad based
-
be adaptable to different
instructional venues
-
be efficient
-
incorporate shared responsibilities;
everyone should be involved
-
acknowledge that the design is
primarily driven by the instructional material
-
enable all parties to produce and
achievable design. ITS should challenge non-workable issues.
Any debates will be settled via prototype testing.
-
Dictate that the prototype set up
will match the actual environment; this prototype system can then act as
a "hot spare" system in case of a total system malfunction in the new
lab.
CQI-New Computer Labs
-
List of software requirements to
ITS
Submit all software requirements to the department for evaluation. (If
new software or licenses are required, up to 2 weeks may be required to
procure them. ) Time required: 3 business days
-
Procure software
If new software or licenses are required, up to ten business days to
procure. Time required: 10 business days
-
ITS reviews request and required
hardware
ITS will determine if any required new equipment and provide the
specifications if new equipment is required, up to 2 months will be
required to procure. Time required: 20 business days
-
Prototype image created
The prototype installation will use the exact hardware as will be used
in the lab. Time required: 5 business days
-
Prototype image tested
The Prototype is to be thoroughly tested by ITS, Faculty and Adjuncts,
and student testers. Time required: 10 business days
-
Final adjustments
Once testing is complete, adjustments will be made to refine the image.
Any further testing should be completed at this stage as well.
Time required: 3 business days
-
Final testing
The Prototype with any new adjustments is to be thoroughly tested a
final time before deployment by ITS, Faculty and adjuncts, and student
teachers. Time required: 5 business days
-
Image deployment
The new lab image will be deployed in the lab. Time required:
3 business days (dependent upon lab availability)
-
Live
ITS and Faculty will continue to monitor the new deployment for any
errors in configuration. Time required: 5 business days
10.10.00
Agendas
|
Meetings
| Minutes
|
Flowcharts
|
|
