Administration Solutions

This integration is a system that uses the files generated by the onboarding and parses them into a directory list. ⮝

This integration is a system that uses the files generated by the onboarding and parses them into a CSV file and imports them into LucidCharts to produce the graphics. ⮝

Software used for organizations' operations often needs to provide solutions or strategies to link with other systems. Interoperability among the system requires API, apps, and other solutions to increase functionality or allow information sharing among systems. An example is creating a script that generates a time stamp to copy it into logs or files when it does not allow a log system. However, it does contain a place for notes where we can automize dates.

During my years of service, these types of needs were essential to finish tasks that required the integration of information among websites, intranets, and databases, among others.

I have deployed solutions managing Application Programming Interfaces (API), Microsoft Open Database Connectivity (ODBC), and importing CSV to connect the different system to do specific tasks.

I have created interfaces to align data from the Active Directory and produce other files like a directory list, organizational charts, inventory requests, purchase orders.

These applications help staff members from different offices to work together and interchange data to finish sharable processes.

This image shows the GUI process of the form OSD 25 from the state that uses a CSV file to create an HTML document that can be printed or saved. ⮝

Surplus and E-waste are always challenging since they involve storage, inventory, reporting, security, and proper disposal.

At DPPC, I created a GUI with a script that was able to take a CSV file from the inventory, and with a scanner, we were able to collect asset tags and create the format that the state requires for reporting.

This process uses a static HTML file to produce the list for the pickup and for the state to process the paperwork for disposal.

This script server receives all the HR information to create the CSV files to push the information into different systems. ⮝

This image is the documentation of the onboarding procedure for DPPC that I designed with scripts to set up computers, push information to the different devices, and create the paperwork needed for the training required as new staff members. ⮝

During onboarding, the scripts designed for the deployment generate barcodes to make deployment easier. Since we have to deploy iPads and iPhones, I created barcodes to use after the MDM sets up the devices so we can add the user's information. All these procedures became a white glove deployment will all the accounts set up. ⮝

I have designed different onboarding procedures.

I always start assessing the systems to search for conditions to accept CSV files or use APIs to make them communicate with the main processes.

I have several meetings with HR to see their requirements and information needed for their operations.

After we have all the analysis of the different stages of creating accounts up to finish setting computers ready for the various task staff members have to perform, I make all the scripting to do the automatization.

During this process, I include scripts to setup images to the computers, setup repositories for the installation, create labels with databases, add the devices to the inventory, create barcodes to facilitate pushing the information that needs to be manual setup and finished with the presentation for the training.

During this process, we include signs for doors, keycards, and automatization with adobe to send the paperwork that needs signature by the new users.

Scripts using CSV files from Active Directory and another database to compare users' names to clean databases. ⮝

One of the most challenging processes is the off-boarding procedure. Mainly because many systems nowadays have methods to bulk users into the system. Still, few offer a bulk deleting process to ensure we have clear users' credentials that left the organizations.

I created a procedure during off-boarding which allows comparing two databases. The first will be the master list, and the other systems will provide the second one to match current users.

The active directory database provides the master list, and the script will compare those and will indicate which users are present and which ones are not.

After that, the system will produce a list of users that need to be deleted.