Development of system design and software for ECU

Usługi doradcze w zakresie działalności gospodarczej, w tym usługi badawcze i eksperymentalno-rozwojowe

Tryb zamówienia	Zapytanie ofertowe
Rodzaj zamówienia	Usługi
Tytuł	Development of system design and software for ECU
Zamawiający	Dostępne dla zalogowanych
Miejsce realizacji	Bielany Wrocławskie
Data publikacji	2025-09-18
Data składania ofert	25/09/2025, Godzina 23:59
Dokumenty do pobrania	Dostępne dla zalogowanych
Kod CPV	731000003 Usługi badawcze i eksperymentalno-rozwojowe
Numer przetargu	6550541

<div>
 <h1>Development of system design and software for an Electronic Control Unit (ECU) intended for the electro-hydraulic steering system</h1>

<h2>Załączniki</h2>
 <ul>
 <li>Appendix no. 1 - Tender offer form</li>
 <li>Appendix no. 2 - Declaration confirming the fulfilment of the conditions of participation</li>
 <li>Request for quotation</li>
 </ul>
 
 <h2>Części zamówienia</h2>

<h3>Development of system design and software for ECU</h3>
 Przedmioty zamówienia
 The subject of the contract includes the development of system design and software for an Electronic Control Unit (ECU) intended for the electro-hydraulic steering system of mobile machinery particularly in the segment of agricultural machines (tractors, sprayers, combines), construction and road machines (wheel loaders, backhoe loaders, telescopic loaders), forestry, municipal, and special-purpose machines. 
The subject of the contract covers the full development cycle: from requirements gathering and safety analyses, through software architecture and ECU software implementation, up to validation. 
The subject of the contract does not include creating the end-user environment (scope of works carried out by the Contracting Authority). 
The subject of the contract shall comply with the conditions set out in this request for quotation if it meets the requirements specified below, either in a compliant or equivalent manner. It is the responsibility of the Tenderer to clarify the extent of equivalence of the proposed parameters. 
 
Task 1 – Collection and Analysis of Functional and Non-Functional Requirements for the ECU: 
Development stage: concept phase. 
Scope: The Contractor shall carry out the concept phase of the ECU development, focusing on requirements elicitation and definition, based on the input provided by the Contracting Authority. The activities will ensure that both functional safety and cybersecurity considerations are embedded in the system from the very beginning. 
Activities include: 
- Production of a comprehensive product concept, addressing all functional aspects as well as the integration of functional safety and cybersecurity requirements. 
- Execution of HARA (Hazard Analysis and Risk Assessment) and TARA (Threat Analysis and Risk Assessment) to identify safety and cybersecurity goals. 
- Development of a structured set of functional and non-functional requirements, including those related to functional safety and cybersecurity. 
Expected Input: Product definition, including a description of the electro-hydraulic steering system, technical details of the flow control principle, construction of the steering unit, operating conditions, and available interface specifications which will be provided by the Contracting Authority. 
Expected Output: 
- product concept, 
- documented safety goals, 
- documented cybersecurity goals, 
- functional and technical requirements specification. 
 
Task 2 – Development of the Software Architecture of the ECU and the Concept of Functional Control Blocks: 
Development stage: system level development. 
Scope: The Contractor shall develop the complete software architecture of the ECU, ensuring that functional safety and cybersecurity requirements are properly embedded and allocated. The task focuses on translating the defined requirements into a structured technical concept at system and software level. 
Activities include: 
- Derivation of detailed technical requirements, including those related to functional safety and cybersecurity together with the Contracting Authority. 
- Definition of hardware-software interfaces together with the Contracting Authority. 
- Development of the System and Software Architecture, including the definition of functional control blocks. 
- Allocation of requirements to hardware and software elements and linking them to the corresponding architecture components. 
Expected Input: Outputs from Task 1 and hardware architecture. 
Expected Output: 
- complete technical concept, including system (architecture) and software architecture level, 
- documented safety and cybersecurity technical requirements, 
- allocation matrix of requirements to hardware and software areas. 
 
Task 3 – Implementation and Integration of ECU Software According to the Defined Architecture: 
Development stage: software level development and integration. 
Scope: This task focuses exclusively on the implementation of ECU software and its integration according to the architecture defined in Task 2. No hardware implementation is included at this stage. The Contractor shall develop the ECU software and integrate it with the ECU hardware platform. 
Activities include: 
- ECU software development (without OS, excluding hardware-level drivers), covering: 
- co-development of QM software, 
- integration and activation of functional safety and cybersecurity functions, 
- implementation of OTA (Over-the-Air) update mechanisms, 
- parametrization and dynamic configuration, 
- development or integration of diagnostic functions. 
- Software integration testing to verify the correct operation of the ECU software within the defined architecture. 
Expected Input: Outputs from Task 2. 
Expected Output: 
- detailed software architecture documentation, 
- SBOM, 
- test plan and executed test reports, 
- complete software source code with technical documentation, 
- complete binary images of software. 
 
Task 4 – Functional and Integration Testing of the ECU in a Laboratory Environment: 
Development stage: system level development. 
Scope: The Contractor shall perform system-level functional and integration testing of the ECU in a controlled laboratory environment together with the Contracting Authority. The purpose of this task is to verify that the ECU software, hardware platform, and user environment operate correctly as a complete system, in line with defined requirements for functionality, safety, and cybersecurity, using both simulated input signals and real components such as sensors (for steering angle, pressure, speed), solenoid valves, communication buses (CAN). 
The tests shall include verification of compliance with functional and non-functional requirements, and preliminary analysis of compliance with standards: 
- ISO 13849 (PL d), 
- ISO 25119 (AgPLd), 
- IEC 62443 or ISO/SAE21434. 
Activities include: Execution of system integration testing, covering ECU functions, communication protocols, diagnostics, and safety/security mechanisms. 
Expected Input: Outputs from Task 2 and Task 3. 
Expected Output: 
- system integration test plan, 
- executed test cases and corresponding test reports confirming system functionality and compliance, 
- the ECU model should achieve the following parameters: 
- compliance with functional safety at SIL2/PLd level, 
- measurement of system response time confirming SAE safety level, time from the application of the control signal to achieving pressure at output (actuator). Separately for: 
analog input (0–10 V): approximately 100ms, 
current input (4–20 mA): approximately 100ms, 
CAN command (ID, control data, message type): 100ms, 
- integration tests with physical components: 
reading data from steering, position, and pressure sensors and their correct interpretation in ECU logic: verification of measurement accuracy with a tolerance of 3% in the range 0-10V, 4-20mA, 
verification of correct reception of CAN frames Standard ID and Extended ID (sent frame matches the received one). 
 
Final result of works 
- Documentation to support configuration management, certification, and end-user operation of the ECU: 
- internal documentation of the system and software baseline environment, 
- end-user manual and guidelines to support safe and secure ECU use, 
- documentation suitable for certification and long-term system maintenance, 
- materials (and mandatory instruction sessions) for engineers on safe modification of the existing system. 
Documentation must reflect the developed system and software baseline and provide clear instructions for integration and operation. 
- Complete software source code. 
- Complete binary images of software. 
 
Safety and reliability requirements 
- The system and software shall enable achievement of PL d/SIL 2. 
- The system shall provide robustness against failures and allow detection and handling of fault states. 
 
Standards and directives 
The system design and software shall comply with the following standards and directives: 
- ISO 13849 (PL d), 
- EN 16590 (SIL 2, AgPL d, SRL 3), 
- ISO 19014, 
- EMC Directive 2004/108/EC, 2009/64/EC, 
- CE marking requirements, 
- ISO 21434 or IEC62443, 
- ISO 24089, CRA, 
- SPICE, IATF 16949, 
- ISO 25119 (AgPLd), 
- MISRA.

Okres gwarancji: -
 
 <h2>Kryteria oceny</h2>
 1)	Fulfilment of the conditions for participation in the procedure set out in point 5 of the request for quotation. 
2)	Submission of a tender offer by the deadline. 
Failure to fulfill the above criteria will result in the rejection of the tender offer. Criterion no. 1 may be supplemented.
 Preparation of a tender offer in accordance with the requirements set out in point 2 of the request for quotation. 
Failure to fulfil the above criterion will result in the rejection of the tender offer, however, it is possible to supplement the tender offer.
 Submission of all required appendices to the request for quotation set out in point 2.2 of the request for quotation. 
Failure to fulfil the above criterion will result in the rejection of the tender offer, however, it is possible to supplement the tender offer.
 The offered scope of the contract complies with the specified requirements. 
Failure to fulfil the above criterion will result in the rejection of the tender offer, however, it is possible to supplement the tender offer.
 Net price 
Total net price 
Weight: 100% 
Methodology for awarding points: (price of the tender offer with the lowest net price among the evaluated tender offers / price indicated in the evaluated tender offer) x 100 points x 100%.
 
 <h2>Warunki zmiany umowy</h2>

The Contracting Authority provides for the possibility of amending the provisions of the concluded conditional contract in relation to the content of the tender offer on the basis of which the Contractor was selected, in the following scope: 
1)	The necessity to introduce amendments shall result from amendments to contracts between the Contracting Authority and a party other than the Contractor, including another contractor or institution supervising the performance of the project under which the Contract is executed, while the amendment may concern only those provisions of the conditional contract that shall be directly affected by the modifications, and the amendments shall not lead to an increase in the Contractor&#039;s remuneration. 
2)	Due to a prolonged procedure for the selection of the Contractor in the procedure for the award of this conditional contract, or due to other circumstances that could not have been foreseen beforehand, preventing the proper execution of the subject of the contract, it shall become necessary to amend the completion dates specified in the request for quotation or the conditional contract. 
3)	Amendments to the contract completion date shall be acceptable in cases of: 
a)	force majeure events preventing the execution of the subject of the contract, 
b)	circumstances that could not have been foreseen by the contracting parties despite the exercise of due diligence or reasons of formal and legal obstacles beyond the control of the contracting parties, 
c)	changes to the planned project are necessary and require acceptance by the Intermediary Institution (in such cases, the contract completion date may be extended by the period corresponding to the time from the submission of the request for changes to the planned project by the Contracting Authority until the acceptance of the changes by the Intermediary Institution), 
d)	delays at earlier stages of the project, 
e)	delays in or changes to administrative or other institutions&#039; decisions (decisions by public authorities, changes to the applicable provisions of law, awaiting previously unforeseen but necessary expert assessments, court rulings, etc.), beyond the control of the Contracting Authority and the Contractor, which the contracting parties were unable to foresee despite exercising due diligence, 
f)	performing the subject of the contract before the contract completion date and obtaining the funds to pay the Contractor’s remuneration at an earlier date by the Contracting Authority, 
g)	a need to perform additional deliveries, services, or construction works from the existing Contractor, not covered by the basic order, may arise during the performance of the subject of the contract, provided that they have become necessary, and all of the following conditions are fulfilled: 
- the change of the current Contractor cannot be made for economic or technical reasons, in particular concerning the interchangeability or interoperability of equipment, services or installations ordered under the basic order, and 
- the change of the current Contractor would cause significant inconvenience or a significant increase in costs for the Contracting Authority, and 
- the value of the amendment does not exceed 50% of the order value specified originally in the conditional contract signed with the selected Contractor. 
All changes to the provisions of the conditional contract shall be made in writing otherwise shall be null and void. The occurrence of any of the circumstances mentioned above to the extent that they affect the performance of the conditional contract may result in extending/amending the contract completion date accordingly by the time required to properly complete the execution of the subject of the contract. Any delays/changes must be documented by relevant protocols signed by the Contractor and the Contracting Authority, based on which the parties shall agree upon new deadlines.
 </div>