Budget: 25000 UAH Deadline: 1 day
I will do my best - and I can be quite effective as I have created my own operating system for AI development telegram bibamon.
We are developing a platform for optimizing and assessing the investment efficiency of solar generation (PV) projects and energy storage systems (BESS).
The system uses hourly data (8760), MILP optimization for calculating battery dispatch, and a financial model (NPV/IRR) for project evaluation.
Budget: 25000 UAH Deadline: 1 day
I will do my best - and I can be quite effective as I have created my own operating system for AI development telegram bibamon.
Budget: 25000 UAH Deadline: 14 days
Hello. I can take the MILP model for BESS optimization. I will formalize the constraints, implement the model in Python, and prepare a clear run scenario with result checks.
I see this as a one time engineering task where we should first align input data, objective function, battery and grid constraints, and output format. I have a strong Python profile on FreelanceHunt and can quickly turn the specification into a reliable implementation plan.
Next step: let us clarify the input files, planning horizon, solver requirements, and acceptance criteria here on FreelanceHunt.
Budget: 25000 UAH Deadline: 21 days
Hello!
I have experience with MILP optimization in Python (PuLP/Pyomo), working with time series and Pandas/NumPy. I understand how to model SOC through linear constraints and prevent simultaneous charge/discharge using binary variables.
I am ready to complete a test task for confirmation.
Budget: 25000 UAH Deadline: 10 days
Hello, I can take on the MILP model for optimizing the operation of the storage system.
I will build the model using 8760 hours of data with charge/discharge dispatching, battery constraints, and consideration of solar generation. The financial part can be presented separately: cash flows, NPV, IRR, and scenario comparisons.
In the end, there will be a clear model that can be tested with the original data and parameters can be changed without rewriting the logic.
Budget: 25000 UAH Deadline: 17 days
Hello! Ready to collaborate. I offer quality and fast work. Write to me on the site)
Budget: 27000 UAH Deadline: 3 days
Good day. I am ready to complete this project and have extensive experience in developing various applications.
Budget: 27000 UAH Deadline: 30 days
Good day! I represent a software development team, please message me privately to discuss in more detail.
Budget: 27000 UAH Deadline: 5 days
Hello! I understand that you are developing a MILP model for optimizing the operation of energy storage systems and solar generation. The task is complex and involves processing large volumes of data as well as financial calculations. Optimizing battery operation through MILP and creating an evaluation model will require time and a precise approach.
For implementation, I plan to: analyze the input data (8760 hourly), adjust the MILP parameters to achieve the best result in battery distribution, and develop a financial model to assess the NPV and IRR of the project. This will not only optimize the operation of BESS but also provide a detailed understanding of investment efficiency.
However, it is important to clarify a few points: do you already have prepared data for calculations? What specific criteria do you intend to use for evaluating efficiency? Are there any time constraints for completing the project? Please ensure that the data we will use is current and complete, otherwise it may complicate the work.
If you are interested, let's discuss the project details further and collaboratively create a plan. I would be happy to help!
Budget: 25000 UAH Deadline: 1 day
Good day, I have experience working with Python as well as Telegram bots, I can complete everything quickly and efficiently, write to me and we will discuss the details.
Budget: 25000 UAH Deadline: 3 days
Hello! Your project looks very interesting. I am ready to start working immediately and ensure high quality.
Budget: 25000 UAH Deadline: 1 day
Good day, I am writing on behalf of the company Devoxen. We specialize in your task. We have extensive experience in developing complex analytical platforms, optimization models, and high-load backend solutions. We can implement a system for evaluating the effectiveness of PV/BESS projects with processing hourly data for 8760 hours, MILP optimization of battery dispatch logic, as well as a full financial model with NPV/IRR calculations and scenario analysis. We can also implement a user-friendly interface, API integrations, and a scalable architecture for further development of the platform.
We can do this without unnecessary questions and time delays. We also provide a guarantee and support if desired. We can start working on your project immediately after discussing the technical specifications.
I suggest moving to private messages for a more detailed dialogue.
Budget: 27000 UAH Deadline: 27 days
My expertise is focused specifically on optimization systems where mathematical formulation, operational constraints and financial logic must work together correctly. This is critical for PV + BESS projects because even small mistakes in SOC dynamics, dispatch constraints or tariff logic can produce inaccurate NPV, IRR and investment evaluations.
I am not a generic backend developer attempting to approximate optimization with simple if/else logic. I have real experience building mathematical optimization models using Python, time series processing and solver based architectures. The system will include a properly formulated MILP optimization engine with SOC constraints, charge/discharge limits, efficiency losses, grid interaction logic and prevention of simultaneous charging and discharging through binary variables and constraint formulation. The optimization objective will be designed to maximize real economic benefit while maintaining model stability and explainability.
Special attention will be given to scalability, solver performance and clean modular architecture. The project structure will be separated into independent modules including optimizer, financial engine, data processing and reporting layers. This approach allows future expansion into additional tariff structures, energy market logic or alternative BESS configurations without rewriting the optimization core. The final result will not only provide dispatch outputs, but also transparent proof of economics suitable for investment decision support.
Plan of work:
Analysis of MVP requirements and hourly input datasets
Design of MILP mathematical model and constraints
Implementation of PV, Grid, Load and BESS energy balance logic
Development of SOC dynamics and operational constraint handling
Implementation of optimization objective for economic benefit maximization
Integration of NPV, IRR and Payback calculations
Optimization of model performance on 8760 hourly datasets
Modularization of optimizer, finance and data processing layers
Testing of solver stability and dispatch correctness
Preparation of final outputs including SOC profiles and savings analysis.
Привет
Я хотел бы уточнить некоторые моменты.
По данным
- В каком формате будут входные данные: CSV, Excel, API, другое?
LoadиPV— этоkWилиkWh за час?- Есть ли пропуски в
8760, переходы времени, timezone?- Данные всегда за один год или может быть несколько лет?
По тарифам
- Есть ли отдельные цены покупки и продажи?
- Разрешен ли экспорт в сеть?
- Есть ли лимит экспорта?
- Есть ли demand charge — плата за максимальную мощность?
- Есть ли net metering?
- Можно ли заряжать батарею из сети?
По батарее
- SOC начальный и конечный должны быть одинаковыми?
- Нужно ли учитывать degradation?
- Есть ли ограничение на cycles per day/year?
- Можно ли батарее продавать энергию в сеть?
- Нужно ли учитывать inverter limit отдельно от battery power?
По PV
- Что делать с surplus PV: экспорт, curtailment или заряд батареи?
- Есть ли ограничение inverter AC capacity?
- Нужно ли моделировать PV degradation по годам?
По финансам (простая модель или полноценная инвестиционная)
- Какая валюта?
- Какой discount rate?
- Project lifetime: 5, 10, 15, 20, 25 лет?
- CAPEX задается отдельно для PV и BESS?
- Есть ли OPEX?
- Нужно ли учитывать замену батареи?
- Нужны ли налоги, субсидии, кредитное финансирование?
По результатам
- Нужен API, Excel export, dashboard или всё вместе?
- Какие таблицы нужны на выходе?
- Нужны ли графики SOC / dispatch / savings?
- Нужно ли сравнение сценариев: без батареи, с батареей, разные емкости?
- Нужно ли оптимизировать размер батареи или только dispatch для заданной батареи?
И еще по поводу оптимизатора - ориентироваться на бесплатный HiGHS или сразу на коммерческий Gurobi?
Жду ваших ответов, чтобы сделать предложение
Спасибо, очень хороший список вопросов — отвечаю, фиксируем scope MVP:
🔹 Данные
Формат: Excel (основной), CSV допустимо
Load и PV: kWh за час
Данные: 8760 часов, 1 год
Пропуски: предполагаем чистые данные (без дыр)
Timezone: фиксированный, без усложнений
🔹 Тарифы
Есть:
import tariff (покупка)
export tariff (продажа)
Экспорт:
разрешён
без сложных лимитов (в MVP)
❌ Нет в MVP:
demand charge
net metering
сложные тарифные конструкции
Заряд от сети:
да, разрешён
🔹 Батарея (BESS)
SOC:
есть min/max
SOC_start = SOC_end (важно)
Ограничения:
мощность charge/discharge
efficiency
запрет одновременного charge/discharge (binary variables)
Деградация:
да, учитываем как линейную стоимость €/kWh discharge
без сложных моделей
❌ Нет в MVP:
cycle limits
сложная деградация
Разряд в сеть:
да, разрешён
🔹 PV
Surplus PV:
приоритет:
load
BESS
export
curtailment
❌ Не учитываем в MVP:
PV degradation
inverter AC limit (пока можно игнорировать)
🔹 Финансовая модель
Валюта: любая (параметр)
Discount rate: входной параметр
Lifetime: 10–15 лет (задаётся)
CAPEX:
отдельно PV и BESS
OPEX:
да (упрощённо)
Замена батареи:
можно упростить или отложить (не критично для MVP)
Не нужно сейчас, можно следующим этапом :
налоги
субсидии
кредитное финансирование
🔹 Результаты
Нужно:
таблицы:
dispatch (8760)
SOC
grid import/export
PV allocation
финансы:
annual savings
NPV
IRR
Payback
графики:
SOC
dispatch
тариф vs поведение батареи
сравнение:
с батареей vs без батареи (обязательно)
🔹 Оптимизация
На MVP:
фиксированный размер батареи
оптимизируем только dispatch
Оптимизация размера — позже
🔹 Solver
Основной: HiGHS (open-source)
Gurobi — не требуется на MVP
🔹 Важно (контекст задачи)
Это MVP / prototype, не production.
Цель:
проверить корректность связки
dispatch → экономический эффект → NPVНе требуется:
API
сложная архитектура
multi-user система
Спасибо, очень хороший список вопросов — отвечаю, фиксируем scope MVP:
🔹 Данные
Формат: Excel (основной), CSV допустимо
Load и PV: kWh за час
Данные: 8760 часов, 1 год
Пропуски: предполагаем чистые данные (без дыр)
Timezone: фиксированный, без усложнений
🔹 Тарифы
Есть:
import tariff (покупка)
export tariff (продажа)
Экспорт:
разрешён
без сложных лимитов (в MVP)
❌ Нет в MVP:
demand charge
net metering
сложные тарифные конструкции
Заряд от сети:
да, разрешён
🔹 Батарея (BESS)
SOC:
есть min/max
SOC_start = SOC_end (важно)
Ограничения:
мощность charge/discharge
efficiency
запрет одновременного charge/discharge (binary variables)
Деградация:
да, учитываем как линейную стоимость €/kWh discharge
без сложных моделей
❌ Нет в MVP:
cycle limits
сложная деградация
Разряд в сеть:
да, разрешён
🔹 PV
Surplus PV:
приоритет:
load
BESS
export
curtailment
❌ Не учитываем в MVP:
PV degradation
inverter AC limit (пока можно игнорировать)
🔹 Финансовая модель
Валюта: любая (параметр)
Discount rate: входной параметр
Lifetime: 10–15 лет (задаётся)
CAPEX:
отдельно PV и BESS
OPEX:
да (упрощённо)
Замена батареи:
можно упростить или отложить (не критично для MVP)
Не нужно сейчас, можно следующим этапом :
налоги
субсидии
кредитное финансирование
🔹 Результаты
Нужно:
таблицы:
dispatch (8760)
SOC
grid import/export
PV allocation
финансы:
annual savings
NPV
IRR
Payback
графики:
SOC
dispatch
тариф vs поведение батареи
сравнение:
с батареей vs без батареи (обязательно)
🔹 Оптимизация
На MVP:
фиксированный размер батареи
оптимизируем только dispatch
Оптимизация размера — позже
🔹 Solver
Основной: HiGHS (open-source)
Gurobi — не требуется на MVP
🔹 Важно (контекст задачи)
Это MVP / prototype, не production.
Цель:
проверить корректность связки
dispatch → экономический эффект → NPVНе требуется:
API
сложная архитектура
multi-user система
Как бы вы сформулировали objective function для этой задачи, если цель — максимизация экономического эффекта проекта?
Инна, добрый вечер
Спасибо за ваши ответы
Может мы перейдем в личный канал переписки, так как уже начинается обсуждение важных вопросов, которые не совсем хотелось бы освещать в открытом форуме
Спасибо за понимание
Начинаю готовить предложение
На ваш вопрос:Для MVP я бы формулировал objective не как “максимизировать NPV” напрямую, а как:
на уровне MILP: max annual operational benefit на уровне finance: annual operational benefit → cash flow → NPV / IRR / PaybackТо есть MILP оптимизирует 8760-часовую эксплуатацию, а NPV считается уже после оптимизации.
здесь нельзя передавать личную инфу
вы можете создать персональный проект на Freelancehunt и отправить мне приглашение. После этого я приму проект, и мы продолжим работу в личном кабинете или можете найти меня где угодно по фи
Project: YOKA ASSIST — intelligent diagnostic and training system for mining equipment Project Description It is required to develop the YOKA ASSIST intelligent system based on a Telegram bot using artificial intelligence. The main task of the project is to create a digital assistant for electricians, mechanics, operators, and engineering and technical personnel, which will assist in diagnosing faults, training employees, and storing a technical knowledge base. The first stage of the project is focused on mining equipment (EKG excavators, SBSh drilling rigs, and other equipment), but the architecture should be universal and easily scalable. Main Functionality Telegram Bot - Modern interface. - Menu with buttons. - User authorization. - Access rights separation (user, administrator, chief administrator). Artificial Intelligence Knowledge Base A knowledge storage system needs to be created. Support: - PDF; - Word; - Excel; - photographs; - diagrams; - videos; - instructions; - equipment passports; - technical documents. After information is added by the administrator, the AI should use it in responses without changing the program code. Equipment Diagnostics Search support: - by error code; - by protection name; - by cabinet; - by unit; - by equipment; - by symptoms. For each fault, it is desirable to provide: - description; - possible causes; - sequence of checks; - photographs; - diagrams; - video materials; - links to related documents. Dynamic Buttons Buttons should be generated automatically depending on the situation. For example: - Check cabinet. - View diagram. - View video. - Next stage of diagnostics. - Go back. Administrative Panel The chief administrator should be able to: - add equipment; - create new errors; - add documents; - upload photographs; - upload videos; - edit the knowledge base; - manage users; - assign administrators of individual departments. QR System Each cabinet, unit, or equipment can have its own QR code. After scanning, the user immediately enters the corresponding section of the Telegram bot. Repair Log A log of completed work needs to be implemented. Functions: - who performed the repair; - date and time; - equipment; - description of completed work; - materials used; - comments; - repair history. Analytics It is desirable to implement: - most common faults; - repair statistics; - time to resolve faults; - reports on equipment; - reports on employees. Scalability The architecture should allow for adding new types of equipment, new enterprises, new departments, and new knowledge bases without rewriting the project. Technologies Desirable: - Python; - Telegram Bot API; - PostgreSQL or SQLite (SQLite is allowed in the first stage); - integration with AI via API; - modular architecture; - possibility of further connecting a web panel. What is expected from the contractor - Development of a fully functional project. - Clean and understandable code. - Documented project structure. - Possibility of further development without complete redesign. - Assistance with initial deployment and setup of the project. The project is long-term. After successful completion of the first stage, further improvements and development of the system are possible.
I'm looking for an experienced Python developer who can conduct a full audit of the existing project, fix errors, and bring it to fully stable operation. If necessary, a complete redesign of the project architecture or writing a new implementation while preserving all necessary functionality is allowed. What I will provide The source code of the current bot. A video demonstrating how the bot should work. A complete technical specification with the logic of operation. Main task The goal is to restore the stable operation of the bot and ensure the execution of the full scenario without failures. If the current architecture cannot be effectively fixed, a complete redesign of the project is allowed. The main objective is not to preserve the existing code but to obtain a fully functional, stable, and maintainable product. What needs to be done 1. Conduct a project audit Before starting work, it is necessary to: study the existing code; identify the reasons why the bot stopped working; assess what can be fixed and what is more reasonable to rewrite. 2. Restore all functionality After the work is completed, the bot should correctly execute the entire scenario: registration of a new account; confirmation of login via code from email; authorization; execution of the scenario according to the technical specification; completion of work; transition to the next account. All stages must work automatically without manual intervention. 3. Fix existing errors It is necessary to eliminate any errors related to: authorization; receiving the confirmation code; unstable operation; freezing; unexpected program termination; errors after website updates; incorrect exception handling. 4. Make the project resilient The bot must: correctly handle errors; not enter infinite loops; automatically terminate unsuccessful scenarios; correctly continue operation after non-critical errors; maintain clear logs. 5. Control panel It is necessary to preserve or redesign the control panel. It should allow: to start and stop operation; to change necessary settings; to view the current status; to view the log of operations and errors. The interface should be clear and stable. 6. Code Code requirements: clear project structure; separation of logic into modules; possibility of further support. 7. Compatibility The project must run on a modern version of Python. The contractor must provide a complete list of dependencies and instructions for running. 8. Result verification Before handing over the project, the contractor must demonstrate a fully working scenario on video: project launch; completion of the full cycle; absence of errors; correct operation of all functions. What to provide after completion source code; all modified files; instructions for running; list of dependencies; video demonstration of operation; brief description of the changes made. Important The work is considered completed only after all functionality described in the technical specification and demonstration video works stably without critical errors. If during the audit it turns out that the current project cannot be effectively fixed, a complete redesign is allowed while preserving all necessary functionality. When responding, please indicate immediately: experience with Python; experience in browser automation (Playwright, Selenium, or similar tools); experience with REST API; cost of work; estimated completion time.
We are looking for a highly skilled AI application engineer and full-stack backend developer to build a production-ready AI-powered document validation, refinement, and approval workflow. This is not a simple prompt engineering role. We need someone who can design and implement a real AI application with strong backend architecture, Claude API integration, structured validation logic, audit trails, secure data handling, and human-in-the-loop review workflows. The system will act as an intelligent quality assurance layer for submitted reports and documents. It should review completed submissions, identify issues, improve content quality, apply business rules, protect sensitive information, and either approve the document automatically or route it for human review. The developer will be responsible for building a workflow that can: Pull completed documents, reports, or submissions from an external platform via API Analyze the full document, including structured answers, ratings, selections, narratives, comments, and free-text fields Perform semantic audits to detect logical conflicts, contradictions, missing information, vague statements, unsupported claims, or incomplete sections Validate that structured responses and written content are consistent with each other Apply custom validation rules, editorial guidelines, formatting standards, tone requirements, and business logic Detect, tokenize, mask, or securely handle PII, confidential data, and sensitive security-related information before AI processing where required Rewrite and enhance narratives, comments, and document sections for grammar, clarity, professionalism, consistency, and readability Preserve the original meaning, observations, and intent while improving the final output Standardize writing style across documents without making every report sound generic or over-normalized Flag content that appears inconsistent, fabricated, vague, incomplete, sensitive, or requiring human review Generate specific validation notes explaining why a document failed review and what needs to be corrected Automatically generate clarification or revision requests when more information is needed Support approval workflows where documents are: Automatically approved when confidence thresholds are met Routed to a human editor or validator for review Returned to the original submitter for revision or clarification Maintain a complete audit trail showing: Original submission Tokenized or masked sensitive data events AI findings and recommendations AI-rewritten content Human edits Approval or rejection decisions Final approved version Write approved and validated content back to the source platform through API integration The role also requires building an editor and final-decision workflow. Human reviewers should be able to inspect the AI’s findings, compare original and revised content, make edits, approve changes, reject recommendations, and finalize the document before it is sent downstream. Ideal experience includes: Strong Claude API / Anthropic API integration experience Experience building AI-powered document review, validation, editing, or compliance workflows Strong backend architecture skills Full-stack development ability Experience with API integrations, webhooks, queues, job processing, and database design Ability to design structured AI outputs, confidence scoring, rule-based validation, and human-in-the-loop review Experience with PII detection, tokenization, masking, encryption, access control, and secure AI data handling Experience building secure audit trails and approval systems Strong understanding of prompt design, but also the engineering skills to turn prompts into a reliable production system We are looking for someone who has already built serious AI applications, not someone who only writes prompts. The right person should be able to design the architecture, integrate with external APIs, manage document processing logic, protect sensitive data, build the review interface, and deliver a reliable workflow that can be used in production.
We are looking for a 3D GenAI Engineer / AI 3D Pipeline Developer It is necessary to create a solution that can qualitatively generate 3D models from a single image or multiple images. It is important that this is not just a ready-made demo, but a clear and reproducible process: from the input image to a full-fledged 3D asset with mesh, geometry, textures, and the possibility of further use. What needs to be done: - test modern image-to-3D models and approaches; - determine which option is best suited for our task; - use Trellis, Hunyuan3D, or similar solutions; - if necessary, use Gaussian Splatting in the 3D pipeline; - configure the conversion of Gaussian Splat / splat representation into 3D mesh; - obtain usable geometry; - generate high-quality textures; - bring the result to a usable 3D asset state; - find the optimal balance between quality, generation speed, and pipeline complexity; - build a clear process that can be repeated for different images; - perform fine-tuning, LoRA, or other model adaptations for specific types of objects.
It is necessary to connect the application form on the landing page to keycrm. I will provide all necessary access. Please write how much time and cost this task will take.