An additional scenario this flow might need to consider is when a new employee comes on and the supervisor indicates no machine is needed, but only because they still have a working machine from a previous employee. If that is allowed, the form might handle adjustment to the inventory or otherwise needs to direct the staff on any need to and how to hand in a device for re-imaging, and whether all that has to happen rather than simultaneously getting a new or an already re-imaged machine. Policy is needed here on the accounting and IGPVs and the potential to provide computing “services” vs retaining the precise machine ownership. DOIT ought to be able to swap machines as equal if of similar specs and within some closeness of warranty.

At Centralized PC/Laptop Procurement meeting today Kurt suggested this flow should be updated to include the ability to request a laptop/PC along with network access. This will have to navigate any difference between temp vs. full time staff and between loaner and dedicated deployment and will need to ensure clarity about how this path for requesting a machine replaces or integrates with any current (email helpdesk) or planned (simpliGov flow) express deployment process.

from soft-roll out with LTCs:

new link in production at DoIT Forms – NJ DEP | Division of Information Technology (state.nj.us)

Knute to follow-up with Holly on who gets notice in programs of new employees. These folks need to be set in the SimpliGov “Department” that defines who has access to the flow, or we need to allow anyone. Consider a supervisor approval stage where user doing entry is NOT the supervisor. This could allow for anyone to make entry, confirmed by the supervisor before being implemented.

Add in a notice to LTCs of the new employees IT access rights to systems and email groups intended to serve as potential oversight for any needed IT training.