43 lines
4.2 KiB
Markdown
43 lines
4.2 KiB
Markdown
# Project Specification: IT Asset & Service Management System
|
|
|
|
## 1. Project Overview
|
|
* The application is an IT asset management and helpdesk system designed to manage users, equipment, technical interventions, and annual maintenance.
|
|
* It will be utilized primarily by the 4 employees of the IT Department responsible for equipment administration and user support.
|
|
* The project will follow a modular architecture, featuring distinct applications for each major function: "Users", "Equipment", and "Interventions".
|
|
|
|
## 2. Technology Stack & Environment
|
|
* **Development & Deployment:** Built using Visual Studio Code, Git, and Docker. It will be deployed exclusively on the internal organizational network.
|
|
* **Backend:** Django web framework with a PostgreSQL database.
|
|
* **Frontend:** Bootstrap and HTMX.
|
|
|
|
## 3. Module Details
|
|
|
|
### 3.1. Users Module
|
|
* **Organizational Hierarchy:** The organizational structure is according to the attached "organigrama.pdf" document. Employees are in management or executive positions. The organization is composed as follows: the largest structure is called a „Direcție”, headed by an executive director, possibly also by a deputy executive director, they are directly assigned to the „Direcție”. The next structure is called a „Serviciu”, headed by a head of service. The smallest structure is called a „Compartiment”, which includes the executive staff. A „Compartiment” can be part of a „Serviciu”, or directly included in a „Direcție”.
|
|
* **Data Fields:** Name, User name, Function/role, Office number, Email address, and Observations.
|
|
* **Inventory Sheet:** The system must generate a user sheet detailing everything in their custody, which includes hardware as well as digital assets like qualified digital certificates (token/cloud) and print cards.
|
|
|
|
### 3.2. Equipment Module
|
|
This module manages three main categories: Computers/Laptops, Monitors, and Peripherals.
|
|
|
|
* **Unique Identification:** Every piece of equipment receives a permanent, unique code generated upon entry.
|
|
* The format is: `[Category Digit] + [YYMMDD] + [Daily Sequence Number]`.
|
|
* Category digits: `9` for Computers/Laptops, `8` for Monitors, `7` for Peripherals.
|
|
* Example: The first three computers registered on February 1, 2026, would be `92602011`, `92602012`, and `92602013`.
|
|
* **Computers / Laptops Data:** Equipment code, entry date, OEM name, motherboard, CPU, RAM, HDD/SSD, optical drive, GPU, network card MAC address, OS license, additional licenses, and observations.
|
|
* **Monitors Data:** Equipment code, entry date, name, serial number, screen diagonal, and observations.
|
|
* **Peripherals Data:** Equipment code, entry date, peripheral type (e.g., printer, UPS, scanner, copier, ethernet adapter, audio speakers, external HDD, webcam), name, and serial number.
|
|
* **Digital certificate:** each user has a qualified digital certificate. The following information is of interest: certificate type (cloud or usb token), issue date, expiration date, canceled (yes or no).
|
|
* **Lifecycle & Maintenance:**
|
|
* Equipment requires annual (or more frequent) maintenance, including cleaning, component checks, and upgrades.
|
|
* A dedicated maintenance sheet is required for each item, logging all maintenance operations and historical user assignments.
|
|
* At the end of its lifecycle (irreparable or obsolete), equipment is removed from inventory via a decommissioning (casare) operation.
|
|
|
|
## 4. Core Transactions & System Workflows
|
|
|
|
* **CRUD Operations:** All data categories must support Create, Read, Update, and Delete operations.
|
|
* **Audit Logging (Crucial):** Every action must be recorded in an audit log detailing who performed the action, the date, the operation type, and the state change (old value vs. new value for updates, or the deleted value).
|
|
* **User Relocation Workflow:** * Users can be transferred between Services or offices.
|
|
* During a move, they can either retain their current equipment or hand it over and receive new equipment at the new location.
|
|
* **Handover Protocol:** Equipment transfers must generate a formal handover-takeover document (proces verbal) that explicitly records the details of the person handing over the equipment, the person receiving it, and the IT staff member validating the transfer.
|