Private 15
Internal Enterprise Asset & Inventory Management App Act as a senior full-stack engineer designing and implementing an i
Los osos están cargando la página…
Comunidad de reseñas de IA de XiuZon · dos osos batallando
Private 15
Modelo de IA
Private 15
Internal Enterprise Asset & Inventory Management App Act as a senior full-stack engineer designing and implementing an i
Grok 4.3
Internal Enterprise Asset & Inventory Management App Act as a senior full-stack engineer designing and implementing an i
Internal Enterprise Asset & Inventory Management App Act as a senior full-stack engineer designing and implementing an internal enterprise asset and inventory management system for a construction/industrial company with multiple branches. Goal Build a secure, self-hosted web application that tracks all company assets (construction machines, vehicles, equipment and tools), their current branch/location, and all related documentation (licenses, registrations, insurance, inspections, contracts), including document expiry alerts and asset movement history. Architecture & stack Backend: Node.js 22 with NestJS, PostgreSQL, Prisma ORM. Frontend: Next.js 16, React, Tailwind CSS (and optionally shadcn/ui for components). Auth: JWT-based authentication with role- and branch-based authorization. Background jobs: Redis-backed job queue (e.g., BullMQ) for scheduled tasks like document expiry checks and notifications. Storage: Object storage (e.g., MinIO/S3 or NAS) for document files; store file paths/URLs in the DB. Deployment: Docker-based (Docker Compose) suitable for running on Ubuntu/Proxmox behind Traefik/Nginx with HTTPS. Core data model Implement at least the following entities: Asset: represents a machine, vehicle, or other equipment item. Fields: id (UUID), asset_code, asset_type (enum: MACHINE, VEHICLE, TOOL, IT_EQUIPMENT, OTHER), status (ACTIVE, IN_MAINTENANCE, RETIRED, DISPOSED), current_branch_id, current_location_detail (string), serial_number, manufacturer, model, year, tag_type (BARCODE, RFID), tag_value (string), created_at, updated_at. Branch: company branch/site. Fields: id, name, code, address, timezone, is_active, created_at, updated_at. AssetMovement: movement events for assets between branches. Fields: id, asset_id, from_branch_id (nullable), to_branch_id, planned_start_date (nullable), planned_end_date (nullable), actual_start_date, actual_end_date (nullable for open-ended assignments), reason (string), created_by_user_id, created_at. Rule: current branch/location for an asset must be derived from the latest movement where actual_end_date is null. Document: any file related to an asset (license, registration, insurance, inspection report, contract, warranty). Fields: id, asset_id, branch_id (nullable), document_type (enum: LICENSE, REGISTRATION, INSURANCE, INSPECTION, CONTRACT, WARRANTY, OTHER), issue_date (nullable), expiry_date (nullable), file_url, file_hash, status (VALID, EXPIRING_SOON, EXPIRED), created_at, updated_at. MaintenanceEvent (optional initial implementation, but design schema): Fields: id, asset_id, event_type (MAINTENANCE, INSPECTION, REPAIR, OTHER), date, description, cost (numeric), performed_by, created_at. User and Role: User fields: id, name, email, password_hash, role (SUPER_ADMIN, HQ_ADMIN, BRANCH_MANAGER, BRANCH_USER), branch_scope (one or many branches or ALL), created_at. AuditLog: Fields: id, user_id, entity_type (ASSET, BRANCH, DOCUMENT, MOVEMENT, MAINTENANCE, USER), entity_id, action (CREATE, UPDATE, DELETE, MOVE, UPLOAD_DOC), timestamp, diff (JSON with before/after). Enforce relational integrity with foreign keys and indexes on commonly queried fields (asset_code, serial_number, plate_number for vehicles, branch_id, document_type, expiry_date). Key features to implement Authentication & authorization Login with JWT tokens. Middleware/guards enforcing roles and branch-based permissions for each API route. SUPER_ADMIN/HQ_ADMIN: full global access. BRANCH_MANAGER: full access within their branch; limited visibility to assets moving to/from their branch. BRANCH_USER: read-only to most data, can create requests or upload some docs subject to rules. Asset management Create, view, update, and (soft) delete assets. Unique asset_code generation and validation. Input validation and required fields; no asset can be ACTIVE without assigned branch. Support barcode/RFID tags stored on assets; expose endpoints and UI fields for tag_type/tag_value. Branch & location tracking CRUD for branches. Asset list filtered by branch and asset_type. Asset detail page showing current branch, current location detail, and full movement history. Movement creation flow: Select asset, from_branch, to_branch, planned dates (optional). Set actual_start_date when movement is confirmed. Close movement by setting actual_end_date when asset returns or moves again. Backend: derive and persist current_branch_id and current_location_detail from movements. Documents & expiry Upload documents per asset, categorize by type, and specify issue/expiry dates. Store files in object storage; save file_url and file_hash in DB. Implement a scheduled job: Runs daily. For each document with expiry_date, computes status: VALID: expiry_date > now + threshold. EXPIRING_SOON: expiry_date between now and now + threshold (e.g., 30 days). EXPIRED: expiry_date <= now. Threshold should be configurable. Provide API and UI views: Documents expiring soon per branch. Expired documents needing action. Search, filters, dashboards Global asset search by asset_code, serial_number, plate_number (vehicles), tag_value. Filters: branch, asset_type, status, document_status (valid, expiring_soon, expired). Dashboard cards: Assets by branch and type. Count of assets currently away from their home branch. Count of documents expiring soon and expired, per branch. Bulk operations CSV/Excel import for assets and optionally documents. Validate data, report errors, and apply bulk create/update. Bulk edit actions for selected assets (e.g., change branch, status, category) with proper audit logging. Audit logging For all create/update/delete/move operations, write an AuditLog entry. Expose a simple audit log viewer in admin UI for Super Admin/HQ Admin. API & integration Provide REST endpoints (or GraphQL) for assets, branches, movements, documents, and maintenance events. Prepare hooks/webhooks/events for future integration with ERP or maintenance systems (e.g., emit events when an asset moves or a document expires). Frontend requirements Build a responsive admin dashboard (Next.js) with: Login page. Branch management pages. Asset list and detailed view with movement history and documents. Document expiry overview pages (expiring soon, expired). Forms designed for fast data entry (dropdowns, date pickers, validation messages). Ensure good UX for branch managers to quickly see: Which machines/cars are at their branch. Which assets are loaned out or incoming. Which documents need renewal. Quality & best practices Use TypeScript across backend and frontend. Follow clean architecture: separate domain logic from controllers and persistence. Implement unit tests for core domain logic (e.g., deriving current branch from movements, computing document statuses). Enforce consistent naming conventions and validation on required fields. Make all destructive operations soft-delete where proper, with audit logs. Deliver the project as a Dockerized application with clear documentation explaining: System architecture. Environment variables. DB migrations and seed data. How to run background jobs. How to configure expiry thresholds and branches/roles.
Create an interactive analytics dashboard for Question Bank aimed at Perticipates that wants to understand which more fr
Create an interactive analytics dashboard for Question Bank aimed at Perticipates that wants to understand which more frequently asked question in the show. Include KPI summary cards with trend indicators, a mix of line, bar, and donut charts with hover tooltips and smooth transitions, a sortable and filterable data table, and date-range and segment filters that update every view live. Use a clean, modern visual style with clear layout hierarchy and a dark mode toggle, generate realistic sample data so every chart feels alive, and make it fully responsive.
Create an interactive analytics dashboard for Whole bank view focusing on future pipeline but also looking retrospective
Create an interactive analytics dashboard for Whole bank view focusing on future pipeline but also looking retrospectively at recent large movements aimed at CEO. Include KPI summary cards with trend indicators, a mix of line, bar, and donut charts with hover tooltips and smooth transitions, a sortable and filterable data table, and date-range and segment filters that update every view live. Use a clean, modern visual style with clear layout hierarchy and a dark mode toggle, generate realistic sample data so every chart feels alive, and make it fully responsive.
создай планер на 31 дней Август 2026 (чтобы можно было отмечать в квадратиках прогресс изучения английского в день). Пун
создай планер на 31 дней Август 2026 (чтобы можно было отмечать в квадратиках прогресс изучения английского в день). Пункты: 2ч изучения слов. 2ч просмотр видео, 30 мин теории, 30 мин аудирования, 30 чтения