System Architecture

This project for a governmental agency managed environmental upgrades to constituents’ properties. Examples would be furnace/AC upgrades, windows, wall insulation and roofing. This system involved custom designed applications and APIs as well as off-the-shelf software (such as Salesforce.)

These system diagrams included application architecture, interfaces, and integration. This document included the IT data extraction process and key process flows.

Process Flows

This project displays the processing of applications and vouchers. Incidents could be experienced at any point in the process. It also discussed maintenance and patching on the network and configuration of the network was also provided.

It also contained architectural deployment related to:

• Network security groups (NSGs) to allow access for administrators to RDC into boxes.
• A jump box letting developers access databases and file shares.
• Firewalls configured at each virtual machine whitelisting specific ports and IPs which can access it.

Decision Maps

This project involved the warehousing and movement of goods into, through and out of the warehouse.

Information on warehouse setup was provided to work with the barcoding system. Each unit (palette, barrel, etc.) was identified with a bar code. Locations within the warehouse also were barcoded.

When move instructions were received, the lift operator scanned the location and unit to be moved. The unit was moved and the location was again scanned with the new location.

This helped to manage FIFO, overage and product expiration.

Technology Overview

This project provided an overview of an IOT home automation system and interaction with the cloud. It discussed the Cloud Services such as core services, the user portal, user and device interfaces and OEM. It also included information on security types, common concepts, as well as communications and application security. Various communication paths were also illustrated and explained.

This information was shared with clients and was also used as a ramp for new developers.

API Guides

This document provided an overview of system architecture, interfaces, and integration. It discussed APIs, batch files, and other methods of integrating Sightline Tracking data with the third-party systems used. Additionally, it included troubleshooting and steps for resolving data issues.

Developer Manuals

This manual was a reference tool supporting application development by creating smaller databases using a subset of data in the original database.
It was designed for experienced C language software developers with a solid foundation in these languages, features, and constructs.

The document provided a reference section that included structures, functions, callbacks and error listings. It included discussions on data extraction, route corridor extractions, and continuous map extraction.

Administrator Guides

This guide was used when converting OEM motorcycle model information into a format that could be imported and referenced by the client’s repair shops.

The process included viewing the information in different ways to make the necessary edits. In addition to ordering parts, labor charges were included.

User Guides

This guide was for users who were new to navigation devices. It discussed the interface and using maps to create a route. It also provided options for voice maneuvers to help the user reach their destination. Topics included detailed setup procedures, Bluetooth use, security features and points of interest (POIs).

Due Diligence

This document was created by a startup company that wanted to either sell itself or secure venture capital. This company’s products were cutting edge and used the most up-to-date software, system design considerations, and AI to create their best in show products.

Wiki Design and Development

This site was created for use by the Reservations group in an international hotel and resort company. Information gathered in a Sharepoint site was reviewed, organized and the most current information was presented in the wiki.

The Home page offered a centralized location to find department information. As the company acquired more motels and chains, the group had to create applets, APIs, or applications to transfer data between the hotel and home office systems. Each individual page included host information to help support staff quickly troubleshoot and resolve any issues that came up. It also documented system algorithms used to generate hotel availability and pricing for each offered room type.