Inteli Project Partners

The aim of this project is to develop a computer game to solve a real problem in the context presented by the selected Market Partner.

APPLICATION EXAMPLES:

• Introductory financial education game with different types of financial products;
• Health promotion through a game, disseminating in a fun way how habits impact on health and can help prevent various types of cancer;
• Through a game, generate an understanding of technology courses and their possible careers, leading to an assertive choice according to each profile.

MANDATORY RESOURCES:

• Programming languages and technologies for the machine learning application, frontend, backend and cloud deployment: C, C++, Python, JavaScript, HTML, CSS and others that are relevant to the application developed;
• Access to a cloud platform with functionality for data engineering and machine learning pipelines;
• Version control system: Git with distribution and collaboration on the GitHub platform;
• Database: DynamoDB, SQLite, MySQL or PostgreSQL or Market Partner Database.

Partner commitment


For the partnership to be a success, the commitment of the partner is essential at all stages of the project. After registering and selecting the initiative, the partner selects a point of contact for the understanding and definition phase. A minimum of 20 hours is required over the course of the project, which will be distributed over 7 face-to-face meetings (each lasting between 1 and 2 hours) and remote moments for clarifying doubts if necessary.

Closing the scope


The Project Office team sends the partner the Inteli Project Opening Form (TAPI) for completion. The partner must fill in this document detailing the scope of the project and return it to the Project Office.
An alignment meeting will be scheduled between the Partner, the Academic Team and the Inteli Project Office. The aim of this meeting is to clarify any doubts about the Inteli Project Charter (TAPI), which contains a description of the problem, the timetable, the resources and technologies involved and the project's objectives.

7 face-to-face Inteli and Partner meetings:


During the projects the meetings held strengthen the relationship with the students and help give the best direction for successful deliveries.

• Executive Onboarding
• Kickoff
• Sprint validations: 4 meetings
• Final presentation of the prototypes

Kickoff meetings, sprint validations and prototype deliveries last approximately 2 hours and will take place on the Inteli campus. Meeting invitations to book agendas will be sent out by the Project Office after the initiatives have been selected.

The delivery to be made by the student groups consists of a prototype that incorporates the functionalities/requirements defined for the web application in question, in line with the learning content presented and agreed with the selected Market Partner via the Project Office. The prototypes developed are made available for use by the partner one month after the end of the module.

Check out the prototypes already made in this module.

The aim of this project is to design a high-performance algorithm whose modeling is carried out using graph structures and techniques to solve problems in the context presented by the selected market partner from sectors such as business, engineering, logistics, finance and others, improving efficiency, decision-making and optimization capacity in real-world scenarios.

APPLICATION EXAMPLES:

• Fleet Routing: Optimize the routing of delivery vehicles to minimize delivery time and transport costs.
• Supply Chain Optimization: Optimizing production and distribution in complex networks of suppliers and manufacturers.
• Smart Grids: Optimizing power flow and detecting faults in complex electrical networks.

MANDATORY INFRASTRUCTURE RESOURCES:

• Java language for backend
• Javascript, HTML and CSS languages for the frontend
• Database: graph-oriented noSQL
• Graph data visualization
• Version control system: GITHUB platform
• Integrated Development Environment- IDE

Partner commitment


For the partnership to be a success, the commitment of the partner is essential at all stages of the project. After registering and selecting the initiative, the partner selects a point of contact for the understanding and definition phase. A minimum of 20 hours is required over the course of the project, which will be distributed over 7 face-to-face meetings (each lasting between 1 and 2 hours) and remote moments for clarifying doubts if necessary.

Closing the scope


The Project Office team sends the partner the Inteli Project Opening Form (TAPI) for completion. The partner must fill in this document detailing the scope of the project and return it to the Project Office.
An alignment meeting will be scheduled between the Partner, the Academic Team and the Inteli Project Office. The aim of this meeting is to clarify any doubts about the Inteli Project Charter (TAPI), which contains a description of the problem, the timetable, the resources and technologies involved and the project's objectives.

7 face-to-face Inteli and Partner meetings:


During the projects the meetings held strengthen the relationship with the students and help give the best direction for successful deliveries.

• Executive Onboarding
• Kickoff
• Sprint validations: 4 meetings
• Final presentation of the prototypes

Kickoff meetings, sprint validations and prototype deliveries last approximately 2 hours and will take place on the Inteli campus. Meeting invitations to book agendas will be sent out by the Project Office after the initiatives have been selected.

The delivery to be made by the student groups consists of a prototype that incorporates the functionalities/requirements defined for the project in question, in line with the learning content presented and agreed with the selected Market Partner via the Project Office. The prototypes developed are made available for use by the partner after one month of the end of the module.

Check out the prototypes already made in this module.

The aim of this project is to develop an industrial automation system using robotic manipulators to solve problems involving production lines. Using a varied set of devices such as robots, sensors, process controllers and specialized software, this area allows complex systems to operate efficiently and precisely, minimizing the need for human intervention.

APPLICATION EXAMPLES:

• Process Control: Adjustment of reactor variables in the operation of oil refineries and chemical industries in general;
• Sorting and Packaging: Automated systems for sorting and filling products on a production line;
• Quality Control: Inspection for defects or contamination in the food and pharmaceutical industries.

MANDATORY RESOURCES:

• Presence of human operators to monitor the automated process;
• Communication network (Wifi or Bluetooth) at the installation site;
• At least one computer to support the operation of the automation system and the presentation of the human-machine interface;
• Serial-chain robotic manipulators (robotic arms);
• Sensors suitable for measuring the process in question (temperature, pressure, presence of volatile gases, distance, etc);
• Microcontrollers for processing sensor signals and interfacing with actuators;

Partner commitment


For the partnership to be a success, the commitment of the partner is essential at all stages of the project. After registering and selecting the initiative, the partner selects a point of contact for the understanding and definition phase. A minimum of 20 hours is required over the course of the project, which will be distributed over 7 face-to-face meetings (each lasting between 1 and 2 hours) and remote moments for clarifying doubts if necessary.

Closing the scope


The Project Office team sends the partner the Inteli Project Opening Form (TAPI) for completion. The partner must fill in this document detailing the scope of the project and return it to the Project Office.
An alignment meeting will be scheduled between the Partner, the Academic Team and the Inteli Project Office. The aim of this meeting is to clarify any doubts about the Inteli Project Charter (TAPI), which contains a description of the problem, the timetable, the resources and technologies involved and the project's objectives.

7 face-to-face Inteli and Partner meetings:


During the projects the meetings held strengthen the relationship with the students and help give the best direction for successful deliveries.

• Executive Onboarding
• Kickoff
• Sprint validations: 4 meetings
• Final presentation of the prototypes

Kickoff meetings, sprint validations and prototype deliveries last approximately 2 hours and will take place on the Inteli campus. Meeting invitations to book agendas will be sent out by the Project Office after the initiatives have been selected.

The delivery to be made by the student groups consists of a prototype that incorporates the functionalities/requirements defined for the project in question, in line with the learning content presented and agreed with the selected market partner through the project office. The prototypes developed are made available for use by the partner after one month of the end of the module.

Check out the prototypes already made in this module.

The aim of this project is to develop a Cloud Web Application that aims to reduce or eliminate its dependence on local network infrastructure, server and storage, to solve a real problem, in the context presented by the selected Market Partner.

APPLICATION EXAMPLES:

• Integration of legacy applications (API creation);
• Creating a new cloud application for the company (we recommend not working with a legacy system in this case);
• Creation of a data repository accessible via API.

MANDATORY RESOURCES:

• Programming languages and technologies for the machine learning application, frontend, backend and cloud deployment: C, C++, Python, JavaScript, HTML, CSS and others that are relevant to the application developed;
• Access to a cloud platform with functionality for data engineering and machine learning pipelines;
• Version control system: Git with distribution and collaboration on the GitHub platform;
• Database: DynamoDB, SQLite, MySQL or PostgreSQL or Market Partner Database.

Partner commitment


For the partnership to be a success, the commitment of the partner is essential at all stages of the project. After registering and selecting the initiative, the partner selects a point of contact for the understanding and definition phase. A minimum of 20 hours is required over the course of the project, which will be distributed over 7 face-to-face meetings (each lasting between 1 and 2 hours) and remote moments for clarifying doubts if necessary.

Closing the scope


The Project Office team sends the partner the Inteli Project Opening Form (TAPI) for completion. The partner must fill in this document detailing the scope of the project and return it to the Project Office.
An alignment meeting will be scheduled between the Partner, the Academic Team and the Inteli Project Office. The aim of this meeting is to clarify any doubts about the Inteli Project Charter (TAPI), which contains a description of the problem, the timetable, the resources and technologies involved and the project's objectives.

7 face-to-face Inteli and Partner meetings:


During the projects the meetings held strengthen the relationship with the students and help give the best direction for successful deliveries.

• Executive Onboarding
• Kickoff
• Sprint validations: 4 meetings
• Final presentation of the prototypes

Kickoff meetings, sprint validations and prototype deliveries last approximately 2 hours and will take place on the Inteli campus. Meeting invitations to book agendas will be sent out by the Project Office after the initiatives have been selected.

The delivery to be made by the student groups consists of a prototype that incorporates the functionalities/requirements defined for the project in question, in line with the learning content presented and agreed with the selected Market Partner via the Project Office. The prototypes developed are made available for use by the partner after one month of the end of the module.

Check out the prototypes already made in this module.

The aim of this project is to develop a Blockchain-based solution that makes it possible to track the sending and receiving of certain types of information over the internet. Pieces of code generated online that carry connected information - like blocks of data that form a chain.

APPLICATION EXAMPLES:

• Smart Contracts;
• Goods and/or parts traceability systems;
• Tokenization.

MANDATORY RESOURCES:

• Hyperledger (for private B2B);
• Ethereum Virtual Machine (for the public B2C case);
• Smart Contracts in Solidity (Ethereum) or Chaincode (Hyperledger);
• Ganache or similar testnet (Ethereum); or Fabric Test Network (Hyperledger);
• Web application in HTML, CSS, Javascript (Node.js);
• Web3.js or Ethers.js app-network communication library for the Ethereum network; otherwise Hyperledger Fabric SDK.

Partner commitment


For the partnership to be a success, the commitment of the partner is essential at all stages of the project. After registering and selecting the initiative, the partner selects a point of contact for the understanding and definition phase. A minimum of 20 hours is required over the course of the project, which will be distributed over 7 face-to-face meetings (each lasting between 1 and 2 hours) and remote moments for clarifying doubts if necessary.

Closing the scope


The Project Office team sends the partner the Inteli Project Opening Form (TAPI) for completion. The partner must fill in this document detailing the scope of the project and return it to the Project Office.
An alignment meeting will be scheduled between the Partner, the Academic Team and the Inteli Project Office. The aim of this meeting is to clarify any doubts about the Inteli Project Charter (TAPI), which contains a description of the problem, the timetable, the resources and technologies involved and the project's objectives.

7 face-to-face Inteli and Partner meetings:


During the projects the meetings held strengthen the relationship with the students and help give the best direction for successful deliveries.

• Executive Onboarding
• Kickoff
• Sprint validations: 4 meetings
• Final presentation of the prototypes

Kickoff meetings, sprint validations and prototype deliveries last approximately 2 hours and will take place on the Inteli campus. Meeting invitations to book agendas will be sent out by the Project Office after the initiatives have been selected.

The delivery to be made by the student groups consists of a prototype that incorporates the functionalities/requirements defined for the web application in question, in line with the learning content presented and agreed with the selected Market Partner via the Project Office. The prototypes developed are made available for use by the partner one month after the end of the module.

Check out the prototypes already made in this module.

The project aims to solve complex challenges in computer vision, using techniques such as image processing, segmentation, deep learning and transfer learning. The focus is on improving the accuracy and efficiency of image analysis, maximizing the use of limited resources and implementing advanced models efficiently.

APPLICATION EXAMPLES:

• In medicine: detecting cancer by analyzing images from medical examinations;
• In agriculture: counting fruit on trees to assess agricultural production;
• In banking institutions: Facial verification for identity authentication in financial transactions.

MANDATORY INFRASTRUCTURE RESOURCES:

• Python: Versatile, high-level programming language;
• TensorFlow: Open source deep learning framework;
• PyTorch: Deep learning framework with a focus on flexibility;
• OpenCV: Open source computer vision library;
• NumPy: Essential library for numerical computation in Python;
• Scikit-learn: Machine learning library in Python;
• GPUs: Graphics processing unit for computational acceleration;
• Clusters: Sets of interconnected computers for parallel processing;
• Cloud: Scalable computing platforms based in the cloud;
• Google Colab Pro Plus: cloud and collaborative development environment;
• Docker: Container technology for deploying applications;
• Git: Repository and version control tool.

Partner commitment


For the partnership to be a success, the commitment of the partner is essential at all stages of the project. After registering and selecting the initiative, the partner selects a point of contact for the understanding and definition phase. A minimum of 20 hours is required over the course of the project, which will be distributed over 7 face-to-face meetings (each lasting between 1 and 2 hours) and remote moments for clarifying doubts if necessary.

Closing the scope


The Project Office team sends the partner the Inteli Project Opening Form (TAPI) for completion. The partner must fill in this document detailing the scope of the project and return it to the Project Office.
An alignment meeting will be scheduled between the Partner, the Academic Team and the Inteli Project Office. The aim of this meeting is to clarify any doubts about the Inteli Project Charter (TAPI), which contains a description of the problem, the timetable, the resources and technologies involved and the project's objectives.

7 face-to-face Inteli and Partner meetings:


During the projects the meetings held strengthen the relationship with the students and help give the best direction for successful deliveries.

• Executive Onboarding
• Kickoff
• Sprint validations: 4 meetings
• Final presentation of the prototypes

Kickoff meetings, sprint validations and prototype deliveries last approximately 2 hours and will take place on the Inteli campus. Meeting invitations to book agendas will be sent out by the Project Office after the initiatives have been selected.

The delivery to be made by the student groups consists of a prototype that incorporates the functionalities/requirements defined for the project in question, in line with the learning content presented and agreed with the selected Market Partner via the Project Office. The prototypes developed are made available for use by the partner after one month of the end of the module.

Check out the prototypes already made in this module.

The aim of this project is to carry out software testing and quality control processes. In this sense, the project envisages the construction of a system of reduced size to be used as a basis for the development of various types of tests (black box, integration, unit, load and so on), considering the definition of procedures and the development of code for test automation. Taking into account the definition of procedures, the project should consider working with the definition of quality metrics (number of defects, test coverage, requirements tested, etc.), (automated) protocols for code quality analysis and communication and management mechanisms such as the presentation of infographics and monitoring dashboards.

APPLICATION EXAMPLES:

• Building a testing and quality control system for an electronic medical records (EHR) solution. This includes the automation of black box tests, unit tests, load tests and integration tests to ensure the interoperability of healthcare systems and the validation of critical data for patient safety;
• Building a testing and quality control system for an online banking application. This includes security tests to protect financial information, performance tests to ensure fast transactions and code quality analysis to maintain the stability of the application;
• Building a testing and quality control system for a hotel and travel booking platform. This includes usability tests, integration tests with payment systems and quality metrics to measure customer satisfaction.

MANDATORY INFRASTRUCTURE RESOURCES:

• Programming languages and technologies normally used for frontend, backend and cloud deployment: C#, Node.js, JavaScript, HTML, CSS and others that are relevant to the application developed;
• Access to any services through the partnership's controlled access interfaces in the form of APIs;
• Version control system (required for Inteli): GITHUB platform;
• Commonly used Integrated Development Environment (IDE): VSCode;
• Modeling Tool for UML: Several;
• Process modeling tool: Various;
• Services from cloud technology partners: AWS (Inteli's current partner).

Partner commitment


For the partnership to be a success, the commitment of the partner is essential at all stages of the project. After registering and selecting the initiative, the partner selects a point of contact for the understanding and definition phase. A minimum of 20 hours is required over the course of the project, which will be distributed over 7 face-to-face meetings (each lasting between 1 and 2 hours) and remote moments for clarifying doubts if necessary.

Closing the scope


The Project Office team sends the partner the Inteli Project Opening Form (TAPI) for completion. The partner must fill in this document detailing the scope of the project and return it to the Project Office.
An alignment meeting will be scheduled between the Partner, the Academic Team and the Inteli Project Office. The aim of this meeting is to clarify any doubts about the Inteli Project Charter (TAPI), which contains a description of the problem, the timetable, the resources and technologies involved and the project's objectives.

7 face-to-face Inteli and Partner meetings:


During the projects the meetings held strengthen the relationship with the students and help give the best direction for successful deliveries.

• Executive Onboarding
• Kickoff
• Sprint validations: 4 meetings
• Final presentation of the prototypes

Kickoff meetings, sprint validations and prototype deliveries last approximately 2 hours and will take place on the Inteli campus. Meeting invitations to book agendas will be sent out by the Project Office after the initiatives have been selected.

The delivery to be made by the student groups consists of a prototype that incorporates the functionalities/requirements defined for the project in question, in line with the learning content presented and agreed with the market partner selected through the project office. The prototypes developed are made available for use by the partner one month after the end of the module.

Check out the prototypes already made in this module.

The overall objective of the project is:

More information about this module will be available soon.

APPLICATION EXAMPLES:

More information about this module will be available soon.

MANDATORY INFRASTRUCTURE RESOURCES:

More information about this module will be available soon.

Partner commitment

For the partnership to be a success, the commitment of the partner is essential at all stages of the project. After registering and selecting the initiative, the partner selects a point of contact for the understanding and definition phase. A minimum of 20 hours is required over the course of the project, which will be distributed over 7 face-to-face meetings (each lasting between 1 and 2 hours) and remote moments to clarify any doubts.

Closing the scope

The Project Office team sends the Inteli Project Initiation Agreement (TAPI) to the partner for completion. The partner must complete this document with details regarding the project scope and return it to the Project Office.
An alignment meeting will be scheduled between the Partner, the Academic Team, and Inteli’s Project Office. The purpose of this meeting is to address any questions regarding the Inteli Project Initiation Agreement (TAPI), which includes a description of the problem, the timeline, the resources and technologies involved, and the project objectives.

7 face-to-face meetings Inteli and Partner:

During the projects, the meetings held strengthen the relationship with the students and help provide the best guidance for successful deliveries.

• Executive Onboarding
• Kickoff
• Sprint validations: 4 meetings
• Final presentation of the prototypes

Kickoff meetings, sprint validations and prototype deliveries last approximately 2 hours and will take place on the Inteli campus. Meeting invitations to book agendas will be sent out by the Project Office after the initiatives have been selected.

The delivery to be made by the student groups consists of a prototype that incorporates the functionalities/requirements defined for the web application in question, in line with the learning content presented and agreed with the selected Market Partner via the Project Office. The prototypes developed are made available for use by the partner one month after the end of the module.

The overall aim of the project is to develop a robust and scalable software architecture to support the infrastructure needed for secure applications in smart cities. The main challenge is to manage the massive volume of data coming from edge devices, which includes a wide range of smart devices such as traffic sensors, weather stations and surveillance systems. Using efficient protocols such as MQTT for communication and tools such as Kafka for processing data streams, the architecture seeks not only to accommodate this intense flow, but also to guarantee optimum security and performance.

APPLICATION EXAMPLES:

• Waste collection service: monitoring collection points and helping to create optimized waste collection routes;
• Public transport monitoring: monitoring not only the position of transport elements, but also their capacity, bringing not only position information to the population, but also the occupancy level of each one.

MANDATORY RESOURCES:

• Version control system: Git with distribution and collaboration on the GitHub platform;
• All documentation will be delivered on the GitHub platform, using a documentation tool defined in the module, such as https://docusaurus.io/ or https://docsify.js.org/#/;
• Use of MQTT and HiveMQ protocols for communication between IoT devices;
• Using Kafka as a tool for streaming messages in the system;
• Information storage using solutions that prioritize storage in large quantities, with an open standard and that are economical over time;
• Using MongoDB for data storage;
• Construction of a platform for data visualization.

Partner commitment


For the partnership to be a success, the commitment of the partner is essential at all stages of the project. After registering and selecting the initiative, the partner selects a point of contact for the understanding and definition phase. A minimum of 20 hours is required over the course of the project, which will be distributed over 7 face-to-face meetings (each lasting between 1 and 2 hours) and remote moments for clarifying doubts if necessary.

Closing the scope


The Project Office team sends the partner the Inteli Project Opening Form (TAPI) for completion. The partner must fill in this document detailing the scope of the project and return it to the Project Office.
An alignment meeting will be scheduled between the Partner, the Academic Team and the Inteli Project Office. The aim of this meeting is to clarify any doubts about the Inteli Project Charter (TAPI), which contains a description of the problem, the timetable, the resources and technologies involved and the project's objectives.

7 face-to-face Inteli and Partner meetings:


During the projects the meetings held strengthen the relationship with the students and help give the best direction for successful deliveries.

• Executive Onboarding
• Kickoff
• Sprint validations: 4 meetings
• Final presentation of the prototypes

Kickoff meetings, sprint validations and prototype deliveries last approximately 2 hours and will take place on the Inteli campus. Meeting invitations to book agendas will be sent out by the Project Office after the initiatives have been selected.

The delivery to be made by the student groups consists of a prototype that incorporates the functionalities/requirements defined for the project in question, in line with the learning content presented and agreed with the selected Market Partner via the Project Office. The prototypes developed are made available for use by the partner one month after the end of the module.

Check out the prototypes already made in this module.

The aim of the project is to develop technological solutions that improve HR management. The creation of reports and dashboards will be explored, with the purpose of visualizing specific HR information, promoting more effective management and data-based decision-making. The ultimate goal is to provide significant value to the HR sector and the organization as a whole.

MANDATORY RESOURCES:

A complex relational database should be provided, covering remuneration indicators, KPIs, turnover and others relevant to the HR sector, with data going back more than 5 years, ideally 10 years.

Partner commitment


For the partnership to be a success, the commitment of the partner is essential at all stages of the project. After registering and selecting the initiative, the partner selects a point of contact for the understanding and definition phase. A minimum of 20 hours is required over the course of the project, which will be distributed over 7 face-to-face meetings (each lasting between 1 and 2 hours) and remote moments for clarifying doubts if necessary.

Closing the scope


The Project Office team sends the partner the Inteli Project Opening Form (TAPI) for completion. The partner must fill in this document detailing the scope of the project and return it to the Project Office.
An alignment meeting will be scheduled between the Partner, the Academic Team and the Inteli Project Office. The aim of this meeting is to clarify any doubts about the Inteli Project Charter (TAPI), which contains a description of the problem, the timetable, the resources and technologies involved and the project's objectives.

7 face-to-face Inteli and Partner meetings:


During the projects the meetings held strengthen the relationship with the students and help give the best direction for successful deliveries.

• Executive Onboarding
• Kickoff
• Sprint validations: 4 meetings
• Final presentation of the prototypes

Kickoff meetings, sprint validations and prototype deliveries last approximately 2 hours and will take place on the Inteli campus. Meeting invitations to book agendas will be sent out by the Project Office after the initiatives have been selected.

The delivery to be made by the student groups consists of a prototype that incorporates the functionalities/requirements defined for the project in question, in line with the learning content presented and agreed with the market partner selected through the project office. The prototypes developed are made available for use by the partner one month after the end of the module.

Check out the prototypes already made in this module.

The overall objective of the project is:

• Develop automated and integrated financial models (using spreadsheets and Python) to project long-term revenues, costs, and financial statements in detail.
• Conduct in-depth business valuation analyses using the Discounted Cash Flow (DCF) and market multiples methodologies.
• Develop sensitivity analyses and scenario modeling (optimistic, base-case, and pessimistic) to assess operational and financial risks under conditions of uncertainty.
• To deliver an evidence-based decision-making ecosystem, supported by strategic analyses and high-impact, professional executive reports.

APPLICATION EXAMPLES:

• Company Valuation for M&A and Investment Rounds: Determining the fair value (valuation) of startups, SMEs, or large companies to support mergers, acquisitions, and capital contributions.
• Financial Planning and Long-Term Projections: Preparing structured future financial statements (Income Statement, Balance Sheet, and Cash Flow Statement) for time horizons ranging from 3 to 10 years.
• Introductory Financial Automation: Creating Python scripts to transform raw, unstructured sales or cost data into modeled cash flows, thereby reducing manual errors.

MANDATORY INFRASTRUCTURE RESOURCES:

• Provision of minimum historical financial data (such as income statements and balance sheets for the past 5 years), with permission to anonymize the data if necessary.
• Access to detailed strategic information about the company's business model, cost structures, revenues, investments, and data on market comparables.
• Availability of financial and business experts from the partner organization for biweekly meetings to align on and validate assumptions.
• Software infrastructure for modeling, including Microsoft Excel or Google Sheets, a Python runtime environment, and calculation tools for financial metrics such as WACC, IRR, and NPV.

Partner commitment

For the partnership to be a success, the commitment of the partner is essential at all stages of the project. After registering and selecting the initiative, the partner selects a point of contact for the understanding and definition phase. A minimum of 20 hours is required over the course of the project, which will be distributed over 7 face-to-face meetings (each lasting between 1 and 2 hours) and remote moments to clarify any doubts.

Closing the scope

The Project Office team sends the Inteli Project Initiation Agreement (TAPI) to the partner for completion. The partner must complete this document with details regarding the project scope and return it to the Project Office.
An alignment meeting will be scheduled between the Partner, the Academic Team, and Inteli’s Project Office. The purpose of this meeting is to address any questions regarding the Inteli Project Initiation Agreement (TAPI), which includes a description of the problem, the timeline, the resources and technologies involved, and the project objectives.

7 face-to-face meetings Inteli and Partner:

During the projects, the meetings held strengthen the relationship with the students and help provide the best guidance for successful deliveries.

• Executive Onboarding
• Kickoff
• Sprint validations: 4 meetings
• Final presentation of the prototypes

Kickoff meetings, sprint validations and prototype deliveries last approximately 2 hours and will take place on the Inteli campus. Meeting invitations to book agendas will be sent out by the Project Office after the initiatives have been selected.

The delivery to be made by the student groups consists of a prototype that incorporates the functionalities/requirements defined for the web application in question, in line with the learning content presented and agreed with the selected Market Partner via the Project Office. The prototypes developed are made available for use by the partner one month after the end of the module.

The aim of this project is to develop a Web Application to solve a real problem in the context presented by the selected Market Partner.

APPLICATION EXAMPLES:

• A web application to find job vacancies in the technology sector that match the professional profile of women, taking into account their technical and non-technical skills;
• A web application of Banco Pan's data catalog that collaborates with the business areas to find information according to specific demands;
• A web-based solution for engaging small Natura producers to collect and process data, helping the company's researchers.

MANDATORY INFRASTRUCTURE RESOURCES:

• Javascript language;
• HTML and CSS languages for the front-end;
• Database: SQLite;
• Back-end execution environment: Node.js;
• Version control system and project documentation: Github;
• Integrated Development Environment - IDE: Visual Studio Code;
• Deployment platform (application publishing): CodeSandbox or similar;
• Prototyping environment: Figma or similar;
• Communication environment: Slack;
• Various file storage environments: Google Drive (internal Inteli).

Partner commitment


For the partnership to be a success, the commitment of the partner is essential at all stages of the project. After registering and selecting the initiative, the partner selects a point of contact for the understanding and definition phase. A minimum of 20 hours is required over the course of the project, which will be distributed over 7 face-to-face meetings (each lasting between 1 and 2 hours) and remote moments for clarifying doubts if necessary.

Closing the scope


The Project Office team sends the partner the Inteli Project Opening Form (TAPI) for completion. The partner must fill in this document detailing the scope of the project and return it to the Project Office.
An alignment meeting will be scheduled between the Partner, the Academic Team and the Inteli Project Office. The aim of this meeting is to clarify any doubts about the Inteli Project Charter (TAPI), which contains a description of the problem, the timetable, the resources and technologies involved and the project's objectives.

7 face-to-face Inteli and Partner meetings:


During the projects the meetings held strengthen the relationship with the students and help give the best direction for successful deliveries.

• Executive Onboarding
• Kickoff
• Sprint validations: 4 meetings
• Final presentation of the prototypes

Kickoff meetings, sprint validations and prototype deliveries last approximately 2 hours and will take place on the Inteli campus. Meeting invitations to book agendas will be sent out by the Project Office after the initiatives have been selected.

The delivery to be made by the student groups consists of a prototype that incorporates the functionalities/requirements defined for the web application in question, in line with the learning content presented and agreed with the market partner selected through the project office. The prototypes developed are made available for use by the partner after one month of the end of the module.

Check out the prototypes already made in this module.

More information soon.

The aim of this project is to model and design algorithms to solve optimization problems, whether it's operations research with linear programming problems, integer programming or combinatorial optimization. This type of problem meets a very wide range of business needs in order to maximize profits (or reduce costs) or make optimal use of scarce resources.

APPLICATION EXAMPLES:

• Finance - Portfolio Analysis: Optimize asset allocation in investment portfolios to maximize return and manage risk;
• Warehouses and capacity - Location of warehouses: Minimizing delivery time, minimizing inventory costs.
• Reducing waste (cutting problems): Problems in which, in addition to minimizing waste, there are additional restrictions, such as the need to cut parts to specific sizes, the use of different types of material or compliance with environmental regulations.

MANDATORY INFRASTRUCTURE RESOURCES:

• Java language for the backend.
• Javascript, HTML and CSS languages for the frontend.
• Data visualization with a graphic library suitable for the project.
• Version control system: GitHub platform.
• Internet access.

Partner commitment


For the partnership to be a success, the commitment of the partner is essential at all stages of the project. After registering and selecting the initiative, the partner selects a point of contact for the understanding and definition phase. A minimum of 20 hours is required over the course of the project, which will be distributed over 7 face-to-face meetings (each lasting between 1 and 2 hours) and remote moments for clarifying doubts if necessary.

Closing the scope


The Project Office team sends the partner the Inteli Project Opening Form (TAPI) for completion. The partner must fill in this document detailing the scope of the project and return it to the Project Office.
An alignment meeting will be scheduled between the Partner, the Academic Team and the Inteli Project Office. The aim of this meeting is to clarify any doubts about the Inteli Project Charter (TAPI), which contains a description of the problem, the timetable, the resources and technologies involved and the project's objectives.

7 face-to-face Inteli and Partner meetings:


During the projects the meetings held strengthen the relationship with the students and help give the best direction for successful deliveries.

• Executive Onboarding
• Kickoff
• Sprint validations: 4 meetings
• Final presentation of the prototypes

Kickoff meetings, sprint validations and prototype deliveries last approximately 2 hours and will take place on the Inteli campus. Meeting invitations to book agendas will be sent out by the Project Office after the initiatives have been selected.

The delivery to be made by the student groups consists of a prototype that incorporates the functionalities/requirements defined for the web application in question, in line with the learning content presented and agreed with the market partner selected through the Project Office. The prototypes developed are made available for use by the partner one month after the end of the module.

Check out the prototypes already made in this module.

The project addresses the development of a system integrating remotely controlled mobile robots and computer vision with real applications. These robots are controlled remotely by human operators, allowing them to perform a variety of functions without putting lives at risk.

APPLICATION EXAMPLES:

• Industrial inspection and maintenance: these robots are used to inspect hard-to-reach areas such as pipes, storage tanks and elevated structures. They can carry out maintenance tasks such as cleaning, painting and repairs without exposing workers to risk;
• Rescue and emergency operations: in situations of natural disasters or accidents, these robots are used to carry out searches and rescues in dangerous or inaccessible areas. They can navigate through rubble, detect signs of life and provide assistance to victims, reducing the risks for rescuers;
• Scientific research: in hard-to-reach environments, such as the ocean floor or hard-to-reach areas, teleoperated mobile robots are valuable tools for collecting data and samples, allowing scientists to study ecosystems, geology and other phenomena without being physically present.

MANDATORY INFRASTRUCTURE RESOURCES:

• Programming languages (mainly Python, C++ and Javascript, but not necessarily limited to these);
• Relational databases;
• Mobile robotic platform;
• Operating system for robotics;
• Code versioning system;
• Various cameras and sensors;
• Scaled track to simulate the environment to be navigated;
• Human-machine interface device (e.g. Joystick) for teleoperation of the robot.

Partner commitment


For the partnership to be a success, the commitment of the partner is essential at all stages of the project. After registering and selecting the initiative, the partner selects a point of contact for the understanding and definition phase. A minimum of 20 hours is required over the course of the project, which will be distributed over 7 face-to-face meetings (each lasting between 1 and 2 hours) and remote moments for clarifying doubts if necessary.

Closing the scope


The Project Office team sends the partner the Inteli Project Opening Form (TAPI) for completion. The partner must fill in this document detailing the scope of the project and return it to the Project Office.
An alignment meeting will be scheduled between the Partner, the Academic Team and the Inteli Project Office. The aim of this meeting is to clarify any doubts about the Inteli Project Charter (TAPI), which contains a description of the problem, the timetable, the resources and technologies involved and the project's objectives.

7 face-to-face Inteli and Partner meetings:


During the projects the meetings held strengthen the relationship with the students and help give the best direction for successful deliveries.

• Executive Onboarding
• Kickoff
• Sprint validations: 4 meetings
• Final presentation of the prototypes

Kickoff meetings, sprint validations and prototype deliveries last approximately 2 hours and will take place on the Inteli campus. Meeting invitations to book agendas will be sent out by the Project Office after the initiatives have been selected.

The delivery to be made by the student groups consists of a prototype that incorporates the functionalities/requirements defined for the web application in question, in line with the learning content presented and agreed with the selected Market Partner via the Project Office. The prototypes developed are made available for use by the partner one month after the end of the module.

Check out the prototypes already made in this module.

The aim of this module is to develop a solution whose demands require the use of a service-oriented architecture as the basis for the design of recommendation systems for use on mobile devices within the "Mobile First" concept.

The "Mobile First" concept addresses mobile devices first and then adapts to the web and other platforms. The development and hosting of the application also considers deployment using cloud computing.

MANDATORY INFRASTRUCTURE RESOURCES:

• Commonly used languages (varies with each module): Python, Node.js;
• Commonly used frontend mobile development languages: React Native, Dart, Flutter;
• Commonly used databases: Dynamo DB, SQLite, MySQL and PostgreSQL;
• Version control system (required for Inteli): GITHUB platform;
• Commonly used Integrated Development Environment (IDE): VSCode;
• Modeling Tool for UML: Several;
• Process modeling tool: Various;
• Services from cloud technology partners.

Partner commitment


For the partnership to be a success, the commitment of the partner is essential at all stages of the project. After registering and selecting the initiative, the partner selects a point of contact for the understanding and definition phase. A minimum of 20 hours is required over the course of the project, which will be distributed over 7 face-to-face meetings (each lasting between 1 and 2 hours) and remote moments for clarifying doubts if necessary.

Closing the scope


The Project Office team sends the partner the Inteli Project Opening Form (TAPI) for completion. The partner must fill in this document detailing the scope of the project and return it to the Project Office.
An alignment meeting will be scheduled between the Partner, the Academic Team and the Inteli Project Office. The aim of this meeting is to clarify any doubts about the Inteli Project Charter (TAPI), which contains a description of the problem, the timetable, the resources and technologies involved and the project's objectives.

7 face-to-face Inteli and Partner meetings:


During the projects the meetings held strengthen the relationship with the students and help give the best direction for successful deliveries.

• Executive Onboarding
• Kickoff
• Sprint validations: 4 meetings
• Final presentation of the prototypes

Kickoff meetings, sprint validations and prototype deliveries last approximately 2 hours and will take place on the Inteli campus. Meeting invitations to book agendas will be sent out by the Project Office after the initiatives have been selected.

The delivery to be made by the student groups consists of a prototype that incorporates the functionalities/requirements defined for the project in question, in line with the learning content presented and agreed with the selected market partner through the project office. The prototypes developed are made available for use by the partner after one month of the end of the module.

Check out the prototypes already made in this module.

The aim of this project is to model and design algorithms to solve Natural Language Processing (NLP) problems, i.e. to develop solutions for computers to understand and generate natural language. NLP is an area of Artificial Intelligence that focuses on making computers understand and process human language efficiently and accurately, in order to analyze large amounts of data (which are in text format) and extract valuable information for decision-making in various sectors, such as health, finance, e-commerce and others.

NLP (Natural Language Processing) is an area of Artificial Intelligence that focuses on teaching computers to understand and process human language naturally and efficiently. Basically, it's the ability to make machines understand what people are saying or writing, and be able to respond appropriately. It is a constantly evolving field and has many practical applications in areas such as virtual assistants, sentiment analysis on social media and machine translation. In short, NLP is the bridge between people and machines, making communication more efficient and natural.

APPLICATION EXAMPLES:

• Sentiment analysis for Descriptive Analysis: sent iment analysis can be used to analyze customer opinions and comments about your company and services, which can help improve customer satisfaction;
• Sentiment analysis to solve a larger classification or decision-making problem: Companies can analyze customer ratings and comments to predict the likelihood of churn, i.e. the possibility that a customer will cancel or switch to a competitor.

MANDATORY INFRASTRUCTURE RESOURCES:

• Languages: Python, node.js, html, css and javascript;
• Database: MySQL (relational) and MongoDB (non-relational);
• Version control: GitHub (required);
• IDE for development: Visual Code;
• UML modeling tool: Draw.io;
• Cloud: AWS, Google or Azure;
• Set of valid data containing some natural language input field, i.e. texts from customers, users, etc;
• Database with Label/Target of the task to be achieved. E.g. Churn/No Churn, Positive/Negative/Neutral, Low Risk/High Risk etc;
• Sensitive information must be anonymized before it is given to the students, at which stage the teacher can help the company.

Partner commitment


For the partnership to be a success, the commitment of the partner is essential at all stages of the project. After registering and selecting the initiative, the partner selects a point of contact for the understanding and definition phase. A minimum of 20 hours is required over the course of the project, which will be distributed over 7 face-to-face meetings (each lasting between 1 and 2 hours) and remote moments for clarifying doubts if necessary.

Closing the scope


The Project Office team sends the partner the Inteli Project Opening Form (TAPI) for completion. The partner must fill in this document detailing the scope of the project and return it to the Project Office.
An alignment meeting will be scheduled between the Partner, the Academic Team and the Inteli Project Office. The aim of this meeting is to clarify any doubts about the Inteli Project Charter (TAPI), which contains a description of the problem, the timetable, the resources and technologies involved and the project's objectives.

7 face-to-face Inteli and Partner meetings:


During the projects the meetings held strengthen the relationship with the students and help give the best direction for successful deliveries.

• Executive Onboarding
• Kickoff
• Sprint validations: 4 meetings
• Final presentation of the prototypes

Kickoff meetings, sprint validations and prototype deliveries last approximately 2 hours and will take place on the Inteli campus. Meeting invitations to book agendas will be sent out by the Project Office after the initiatives have been selected.

The delivery to be made by the student groups consists of a prototype that incorporates the functionalities/requirements defined for the web application in question, in line with the learning content presented and agreed with the selected Market Partner via the Project Office. The prototypes developed are made available for use by the partner after one month of the end of the module.

Check out the prototypes already made in this module.

The aim of this project is to develop and implement an efficient and reliable continuous delivery system for a specific software application. Continuous delivery is a software development approach that aims to automate and simplify the process of deploying code into production environments quickly and consistently. By means of continuous application integration and deployment pipelines, supported by configuration control and quality control automation, new required functionalities are delivered to users continuously, in short cycles (sprints), without the need for service interruptions.

APPLICATION EXAMPLES:

Organizations in the technology area, as well as the technology areas of organizations that need to work with this issue, improving the provision of internal services by reducing release cycle times, increasing operational efficiency, reducing risks and improving software quality.

MANDATORY INFRASTRUCTURE RESOURCES:

• Commonly used languages (varies with each module): Python, Node.js;
• Commonly used frontend development languages: React, Node.js;
• Commonly used databases: Dynamo DB, SQLite, MySQL and PostgreSQL;
• Version control system (required for Inteli): GITHUB platform;
• Commonly used Integrated Development Environment (IDE): VSCode;
• Modeling Tool for UML: Several;
• Process modeling tool: Various;
• Services from cloud technology partners.

Partner commitment


For the partnership to be a success, the commitment of the partner is essential at all stages of the project. After registering and selecting the initiative, the partner selects a point of contact for the understanding and definition phase. A minimum of 20 hours is required over the course of the project, which will be distributed over 7 face-to-face meetings (each lasting between 1 and 2 hours) and remote moments for clarifying doubts if necessary.

Closing the scope


The Project Office team sends the partner the Inteli Project Opening Form (TAPI) for completion. The partner must fill in this document detailing the scope of the project and return it to the Project Office.
An alignment meeting will be scheduled between the Partner, the Academic Team and the Inteli Project Office. The aim of this meeting is to clarify any doubts about the Inteli Project Charter (TAPI), which contains a description of the problem, the timetable, the resources and technologies involved and the project's objectives.

7 face-to-face Inteli and Partner meetings:


During the projects the meetings held strengthen the relationship with the students and help give the best direction for successful deliveries.

• Executive Onboarding
• Kickoff
• Sprint validations: 4 meetings
• Final presentation of the prototypes

Kickoff meetings, sprint validations and prototype deliveries last approximately 2 hours and will take place on the Inteli campus. Meeting invitations to book agendas will be sent out by the Project Office after the initiatives have been selected.

The delivery to be made by the student groups consists of a prototype that incorporates the functionalities/requirements defined for the project in question, in line with the learning content presented and agreed with the selected market partner through the project office. The prototypes developed are made available for use by the partner after one month of the end of the module.

Check out the prototypes already made in this module.

The project aims to understand and model user behavior in digital interfaces, using techniques such as Monte Carlo simulation and A/B testing to predict and analyze different usage scenarios. This includes developing skills in programming, simulation, and statistical analysis to improve the customer experience on websites and apps.

APPLICATION EXAMPLES:

• E-commerce optimization: Using Monte Carlo simulation and A/B testing to analyze user behavior on an e-commerce platform, identifying patterns that influence the purchasing decision.
• Optimizing Lead Capture on Digital Platforms: Implement advanced behavioral analysis techniques to understand and optimize the user journey on digital platforms in order to maximize lead capture.

MANDATORY INFRASTRUCTURE RESOURCES:

• Algorithm developed in the Python language;
• HTML and CSS languages for the front-end;
• PostgreSQL Database;
• Back-end execution environment: Node.js;
• Version control system and project documentation: Github;
• Deployment platform (application publishing): CodeSandbox or similar;
• Prototyping environment: Figma or similar
• Communication environment: Slack
• Miscellaneous file storage environment: Google Drive (Internal Inteli)

Partner commitment


For the partnership to be a success, the commitment of the partner is essential at all stages of the project. After registering and selecting the initiative, the partner selects a point of contact for the understanding and definition phase. A minimum of 20 hours is required over the course of the project, which will be distributed over 7 face-to-face meetings (each lasting between 1 and 2 hours) and remote moments for clarifying doubts if necessary.

Closing the scope


The Project Office team sends the partner the Inteli Project Opening Form (TAPI) for completion. The partner must fill in this document detailing the scope of the project and return it to the Project Office.
An alignment meeting will be scheduled between the Partner, the Academic Team and the Inteli Project Office. The aim of this meeting is to clarify any doubts about the Inteli Project Charter (TAPI), which contains a description of the problem, the timetable, the resources and technologies involved and the project's objectives.

7 face-to-face Inteli and Partner meetings:


During the projects the meetings held strengthen the relationship with the students and help give the best direction for successful deliveries.

• Executive Onboarding
• Kickoff
• Sprint validations: 4 meetings
• Final presentation of the prototypes

Kickoff meetings, sprint validations and prototype deliveries last approximately 2 hours and will take place on the Inteli campus. Meeting invitations to book agendas will be sent out by the Project Office after the initiatives have been selected.

The delivery to be made by the student groups consists of a prototype that incorporates the functionalities/requirements defined for the project in question, in line with the learning content presented and agreed with the selected Market Partner via the Project Office. The prototypes developed are made available for use by the partner after one month of the end of the module.

Check out the prototypes already made in this module.

The aim of this project is to solve problems involving sequential decision-making under uncertainty by building agents that learn by reinforcement. Problems of this nature involve situations in which an agent (be it a human, an organization or a computer program) needs to make a series of decisions over time, and each decision can influence the future options available and the possible outcomes.

APPLICATION EXAMPLES:

• Financial investment: an investor who needs to decide which stock to buy, when to buy it, sell it, and so on;
• Route planning: an autonomous vehicle must decide where to move at any given moment, and each movement can open up or close off different future paths;
• Logistics: design of a decision-making agent for inventory control in a retail environment, where product demand is uncertain and the agent needs to optimize its inventory replenishment decisions over time.

MANDATORY INFRASTRUCTURE RESOURCES:

• Cloud environment and services;
• Deep Racer from AWS;
• Python language;
• Data visualization with a graphic library suitable for the project;
• Version control system: GitHub platform.

Partner commitment


For the partnership to be a success, the commitment of the partner is essential at all stages of the project. After registering and selecting the initiative, the partner selects a point of contact for the understanding and definition phase. A minimum of 20 hours is required over the course of the project, which will be distributed over 7 face-to-face meetings (each lasting between 1 and 2 hours) and remote moments for clarifying doubts if necessary.

Closing the scope


The Project Office team sends the partner the Inteli Project Opening Form (TAPI) for completion. The partner must fill in this document detailing the scope of the project and return it to the Project Office.
An alignment meeting will be scheduled between the Partner, the Academic Team and the Inteli Project Office. The aim of this meeting is to clarify any doubts about the Inteli Project Charter (TAPI), which contains a description of the problem, the timetable, the resources and technologies involved and the project's objectives.

7 face-to-face Inteli and Partner meetings:


During the projects the meetings held strengthen the relationship with the students and help give the best direction for successful deliveries.

• Executive Onboarding
• Kickoff
• Sprint validations: 4 meetings
• Final presentation of the prototypes

Kickoff meetings, sprint validations and prototype deliveries last approximately 2 hours and will take place on the Inteli campus. Meeting invitations to book agendas will be sent out by the Project Office after the initiatives have been selected.

The delivery to be made by the student groups consists of a prototype that incorporates the functionalities/requirements defined for the project in question, in line with the learning content presented and agreed with the selected Market Partner via the Project Office. The prototypes developed are made available for use by the partner one month after the end of the module.

Check out the prototypes already made in this module.

The overall objective of the project is:

More information about this module will be available soon.

APPLICATION EXAMPLES:

More information about this module will be available soon.

MANDATORY INFRASTRUCTURE RESOURCES:

More information about this module will be available soon.

Partner commitment

For the partnership to be a success, the commitment of the partner is essential at all stages of the project. After registering and selecting the initiative, the partner selects a point of contact for the understanding and definition phase. A minimum of 20 hours is required over the course of the project, which will be distributed over 7 face-to-face meetings (each lasting between 1 and 2 hours) and remote moments to clarify any doubts.

Closing the scope

The Project Office team sends the Inteli Project Initiation Agreement (TAPI) to the partner for completion. The partner must complete this document with details regarding the project scope and return it to the Project Office.
An alignment meeting will be scheduled between the Partner, the Academic Team, and Inteli’s Project Office. The purpose of this meeting is to address any questions regarding the Inteli Project Initiation Agreement (TAPI), which includes a description of the problem, the timeline, the resources and technologies involved, and the project objectives.

7 face-to-face meetings Inteli and Partner:

During the projects, the meetings held strengthen the relationship with the students and help provide the best guidance for successful deliveries.

• Executive Onboarding
• Kickoff
• Sprint validations: 4 meetings
• Final presentation of the prototypes

Kickoff meetings, sprint validations and prototype deliveries last approximately 2 hours and will take place on the Inteli campus. Meeting invitations to book agendas will be sent out by the Project Office after the initiatives have been selected.

The delivery to be made by the student groups consists of a prototype that incorporates the functionalities/requirements defined for the web application in question, in line with the learning content presented and agreed with the selected Market Partner via the Project Office. The prototypes developed are made available for use by the partner one month after the end of the module.

The overall objective of the project is:

• Structure organizational decision-making processes based on data intelligence, mitigating cognitive biases and purely intuitive judgments.
• Develop a comprehensive scenario and decision simulator capable of generating multi-criteria evaluation matrices.
• Apply Business Intelligence (BI) tools and stochastic modeling (such as Monte Carlo simulations) to collect, process, and visually analyze risks.
• Build interactive dashboards and structured executive reports using sound data storytelling techniques.

APPLICATION EXAMPLES:

• Market Expansion and Product Launches: Developing BI tools to assess the feasibility of new initiatives and simulate multiple future scenarios.
• Investment Prioritization and Resource Allocation: Development of analytical models based on historical data and indicators to optimize corporate decisions.
• Performance and Risk Management: Creating decision-support dashboards that consolidate KPIs from different business units to eliminate information silos.

MANDATORY INFRASTRUCTURE RESOURCES:

• Preliminary mapping of decision-making processes and strategic alignment with subject matter experts (SMEs) provided by the partner company.
• Guaranteed access to the company's original data assets and sources, with sufficient sampling and volume to ensure statistical significance.
• Data infrastructure structured in editable formats (spreadsheets, databases, or APIs) and fully compliant with LGPD guidelines.
• Use of development tools and technologies such as Python (Pandas, NumPy), BI platforms (Power BI, Tableau, or Metabase), and wireframing tools (Figma/Miro).

Partner commitment

For the partnership to be a success, the commitment of the partner is essential at all stages of the project. After registering and selecting the initiative, the partner selects a point of contact for the understanding and definition phase. A minimum of 20 hours is required over the course of the project, which will be distributed over 7 face-to-face meetings (each lasting between 1 and 2 hours) and remote moments to clarify any doubts.

Closing the scope

The Project Office team sends the Inteli Project Initiation Agreement (TAPI) to the partner for completion. The partner must complete this document with details regarding the project scope and return it to the Project Office.
An alignment meeting will be scheduled between the Partner, the Academic Team, and Inteli’s Project Office. The purpose of this meeting is to address any questions regarding the Inteli Project Initiation Agreement (TAPI), which includes a description of the problem, the timeline, the resources and technologies involved, and the project objectives.

7 face-to-face meetings Inteli and Partner:

During the projects, the meetings held strengthen the relationship with the students and help provide the best guidance for successful deliveries.

• Executive Onboarding
• Kickoff
• Sprint validations: 4 meetings
• Final presentation of the prototypes

Kickoff meetings, sprint validations and prototype deliveries last approximately 2 hours and will take place on the Inteli campus. Meeting invitations to book agendas will be sent out by the Project Office after the initiatives have been selected.

The delivery to be made by the student groups consists of a prototype that incorporates the functionalities/requirements defined for the web application in question, in line with the learning content presented and agreed with the selected Market Partner via the Project Office. The prototypes developed are made available for use by the partner one month after the end of the module.

Development of hyperscalable applications, focusing mainly on the programming of scalable services and the development of hybrid applications, to interact with the services created by different modes of user use, such as web applications and native applications for mobile devices. The concepts of synchronous and asynchronous systems will be explored. Different load testing tools will be presented, making it possible to verify the behavior of the developed system, creating performance reports that make it possible to make targeted technical and strategic decisions for a solution.

APPLICATION EXAMPLES:

• Order management system (similar to iFood, Uber);
• Document validation system (application sending the document to the backend for validation).

MANDATORY RESOURCES:

• Javascript, Dart, Flutter, Go and/or Python;
• Database: PostgreSQL (relational) and MongoDB (non-relational);
• Version control system: Git and Github platform;
• Integrated Development Environment- IDE: VS Code (editor) and Android Studio;
• Services from cloud technology partners (e.g. AWS, Google Cloud, Azure), within the Cloud Free Tier, just to demonstrate the application.

Partner commitment


For the partnership to be a success, the commitment of the partner is essential at all stages of the project. After registering and selecting the initiative, the partner selects a point of contact for the understanding and definition phase. A minimum of 20 hours is required over the course of the project, which will be distributed over 7 face-to-face meetings (each lasting between 1 and 2 hours) and remote moments for clarifying doubts if necessary.

Closing the scope


The Project Office team sends the partner the Inteli Project Opening Form (TAPI) for completion. The partner must fill in this document detailing the scope of the project and return it to the Project Office.
An alignment meeting will be scheduled between the Partner, the Academic Team and the Inteli Project Office. The aim of this meeting is to clarify any doubts about the Inteli Project Charter (TAPI), which contains a description of the problem, the timetable, the resources and technologies involved and the project's objectives.

7 face-to-face Inteli and Partner meetings:


During the projects the meetings held strengthen the relationship with the students and help give the best direction for successful deliveries.

• Executive Onboarding
• Kickoff
• Sprint validations: 4 meetings
• Final presentation of the prototypes

Kickoff meetings, sprint validations and prototype deliveries last approximately 2 hours and will take place on the Inteli campus. Meeting invitations to book agendas will be sent out by the Project Office after the initiatives have been selected.

The delivery to be made by the student groups consists of a prototype that incorporates the functionalities/requirements defined for the project in question, in line with the learning content presented and agreed with the selected market partner through the project office. The prototypes developed are made available for use by the partner after one month of the end of the module.

Check out the prototypes already made in this module.

Creating a business management system - ERP (Enterprise Resource Planning) - aims to improve operational and decision-making processes in organizations. An ERP system enables the integration and automation of business processes, working in various areas such as finance, accounting, human resources, production, stock, sales and marketing. By implementing an ERP system, the organization can have integrated, real-time access to all its information, which allows for better analysis, performance monitoring and faster identification of problems and opportunities.

APPLICATION EXAMPLES:

• Lack of integration between systems: Many organizations use different systems to manage their business areas, which can lead to integration problems and difficulties in analyzing data;
• Difficulty in inventory management: An ERP system can help organizations manage their inventories more efficiently, allowing more precise control over inventory, reducing the risk of errors and improving decision-making on purchases and sales;
• Lack of process standardization: When each area of the organization works with its own processes, there can be a lack of standardization and difficulties in keeping information consistent. An ERP system can help standardize processes and ensure that all areas work to the same standard.

MANDATORY INFRASTRUCTURE RESOURCES:

• Prior mapping of the client's areas that will be integrated by the ERP system and prior provision of the master databases;
• Provide a technical support team for Inteli students throughout the ERP system implementation life cycle, on a 12 x 5 basis. This support will be on a remote / face-to-face basis on demand or prior planning;
• Infrastructure resources must be provided by the Partner, such as servers, licenses, manuals and other technical documents, in line with the production of the TAPI.

COMPLETION AND DELIVERY OF THE PROJECT

All the prototypes generated during the project are delivered at the end of the 10th week.

Partner commitment


For the partnership to be a success, the commitment of the partner is essential at all stages of the project. After registering and selecting the initiative, the partner selects a point of contact for the understanding and definition phase. A minimum of 20 hours is required over the course of the project, which will be distributed over 7 face-to-face meetings (each lasting between 1 and 2 hours) and remote moments for clarifying doubts if necessary.

Closing the scope


The Project Office team sends the partner the Inteli Project Opening Form (TAPI) for completion. The partner must fill in this document detailing the scope of the project and return it to the Project Office.
An alignment meeting will be scheduled between the Partner, the Academic Team and the Inteli Project Office. The aim of this meeting is to clarify any doubts about the Inteli Project Charter (TAPI), which contains a description of the problem, the timetable, the resources and technologies involved and the project's objectives.

7 face-to-face Inteli and Partner meetings:


During the projects the meetings held strengthen the relationship with the students and help give the best direction for successful deliveries.

• Executive Onboarding
• Kickoff
• Sprint validations: 4 meetings
• Final presentation of the prototypes

Kickoff meetings, sprint validations and prototype deliveries last approximately 2 hours and will take place on the Inteli campus. Meeting invitations to book agendas will be sent out by the Project Office after the initiatives have been selected.

The delivery to be made by the student groups consists of a prototype that incorporates the functionalities/requirements defined for the project in question, in line with the learning content presented and agreed with the selected market partner through the project office. The prototypes developed are made available for use by the partner after one month of the end of the module.

Check out the prototypes already made in this module.

The aim of this project is to delve into the principles of deep learning, from fundamentals to advanced applications, focusing on fraud detection. The application of deep learning in fraud detection is pertinent in various industries due to its ability to identify complex patterns in extensive volumes of data.

APPLICATION EXAMPLES:

• E-commerce fraud prevention: On e-commerce platforms, fraud such as purchases made with stolen credit cards or compromised user accounts is common. Deep learning models can be employed to analyze purchase and login behavior, learning to identify activities that are inconsistent with the user's usual pattern.
• Fraud Detection in Banking Transactions: Using deep learning models, it is possible to analyze patterns in banking transactions to identify suspicious activity that could indicate fraud. For example, the system can learn to recognize unauthorized transfers or abnormal withdrawals of large amounts of money. By processing large volumes of data, the model can detect deviations from a customer's usual transaction patterns, such as transactions at atypical times or locations.
• Insurance Fraud Prevention: In the insurance sector, deep learning models can be applied to identify fraudulent claims. By analyzing claim histories and claim patterns, these models can highlight cases that deviate from statistical norms, such as excessively frequent claims or significantly high value claims that do not align with the customer's risk profile. This allows insurers to investigate and validate suspicious claims more efficiently.

COMPLETION AND DELIVERY OF THE PROJECT:

All the prototypes generated during the project are delivered at the end of the 10th week.

Partner commitment


For the partnership to be a success, the commitment of the partner is essential at all stages of the project. After registering and selecting the initiative, the partner selects a point of contact for the understanding and definition phase. A minimum of 20 hours is required over the course of the project, which will be distributed over 7 face-to-face meetings (each lasting between 1 and 2 hours) and remote moments for clarifying doubts if necessary.

Closing the scope


The Project Office team sends the partner the Inteli Project Opening Form (TAPI) for completion. The partner must fill in this document detailing the scope of the project and return it to the Project Office.
An alignment meeting will be scheduled between the Partner, the Academic Team and the Inteli Project Office. The aim of this meeting is to clarify any doubts about the Inteli Project Charter (TAPI), which contains a description of the problem, the timetable, the resources and technologies involved and the project's objectives.

7 face-to-face Inteli and Partner meetings:


During the projects the meetings held strengthen the relationship with the students and help give the best direction for successful deliveries.

• Executive Onboarding
• Kickoff
• Sprint validations: 4 meetings
• Final presentation of the prototypes

Kickoff meetings, sprint validations and prototype deliveries last approximately 2 hours and will take place on the Inteli campus. Meeting invitations to book agendas will be sent out by the Project Office after the initiatives have been selected.

The delivery to be made by the student groups consists of a prototype that incorporates the functionalities/requirements defined for the project in question, in line with the learning content presented and agreed with the selected Market Partner via the Project Office. The prototypes developed are made available for use by the partner after one month of the end of the module.

Check out the prototypes already made in this module.

The aim of this project is to develop a predictive model to solve a real problem in the area of Data Science and Machine Learning, in the context presented by the selected Market Partner.

APPLICATION EXAMPLES:

• Prediction of churn and turnover in consumer or employee retention contexts;
• Predicting the success/failure of new products in consolidated markets;
• Recommending products according to consumption patterns.

MANDATORY INFRASTRUCTURE RESOURCES:

• Python programming language, Numpy, Pandas and Scikit-learn libraries;
• Classic Machine Learning models: kNN, k-Means, Naive Bayes, Random Forest, Decision Tree, Linear Regression, Logistic Regression, SVM, among others. Neural networks and deep learning techniques will not be used;
• Database: anonymized CSV or Excel files provided by the partner (with target columns filled in, in the case of supervised learning);
• Version control system: GITHUB platform;
• System for developing predictive models and analyzing results: Google Collaboratory.

COMPLETION AND DELIVERY OF THE PROJECT:

All the prototypes generated during the project are delivered at the end of the 10th week.

Partner commitment


For the partnership to be a success, the commitment of the partner is essential at all stages of the project. After registering and selecting the initiative, the partner selects a point of contact for the understanding and definition phase. A minimum of 20 hours is required over the course of the project, which will be distributed over 7 face-to-face meetings (each lasting between 1 and 2 hours) and remote moments for clarifying doubts if necessary.

Closing the scope


The Project Office team sends the partner the Inteli Project Opening Form (TAPI) for completion. The partner must fill in this document detailing the scope of the project and return it to the Project Office.
An alignment meeting will be scheduled between the Partner, the Academic Team and the Inteli Project Office. The aim of this meeting is to clarify any doubts about the Inteli Project Charter (TAPI), which contains a description of the problem, the timetable, the resources and technologies involved and the project's objectives.

7 face-to-face Inteli and Partner meetings:


During the projects the meetings held strengthen the relationship with the students and help give the best direction for successful deliveries.

• Executive Onboarding
• Kickoff
• Sprint validations: 4 meetings
• Final presentation of the prototypes

Kickoff meetings, sprint validations and prototype deliveries last approximately 2 hours and will take place on the Inteli campus. Meeting invitations to book agendas will be sent out by the Project Office after the initiatives have been selected.

The delivery to be made by the student groups consists of a prototype that incorporates the functionalities/requirements defined for the project in question, in line with the learning content presented and agreed with the selected Market Partner via the Project Office. The prototypes developed are made available for use by the partner after one month of the end of the module.

Check out the prototypes already made in this module.

The aim of this project is to develop a highly scalable, available, distributed system based on microservices. A system deployed in the cloud must be able to handle a large number of simultaneous requests and be easily scaled to handle more requests as traffic increases. The product is developed and deployed using containers, container managers, serverless technologies and messaging systems.

APPLICATION EXAMPLES:

• Personal finance management app: Financial technology companies (fintechs) can develop a scalable app that allows users to manage their personal finances, track spending, make budgets, receive bill alerts and carry out banking transactions securely.
• Video streaming platform: Entertainment companies can develop a scalable application that allows users to watch videos, movies, series and content on demand, guaranteeing high-quality streaming and supporting a large number of simultaneous users.
• Online gaming platform: Gaming companies can develop a scalable application that supports online multiplayer games, allowing players to connect, interact and compete in real time, regardless of the number of connected users.

MANDATORY INFRASTRUCTURE RESOURCES:

• Java language for the backend.
• Javascript, HTML and CSS languages for the frontend.
• Data visualization with a graphic library suitable for the project.
• Version control system: GitHub platform.
• Internet access.

COMPLETION AND DELIVERY OF THE PROJECT:

All the prototypes generated during the project are delivered at the end of the 10th week.

Partner commitment


For the partnership to be a success, the commitment of the partner is essential at all stages of the project. After registering and selecting the initiative, the partner selects a point of contact for the understanding and definition phase. A minimum of 20 hours is required over the course of the project, which will be distributed over 7 face-to-face meetings (each lasting between 1 and 2 hours) and remote moments for clarifying doubts if necessary.

Closing the scope


The Project Office team sends the partner the Inteli Project Opening Form (TAPI) for completion. The partner must fill in this document detailing the scope of the project and return it to the Project Office.
An alignment meeting will be scheduled between the Partner, the Academic Team and the Inteli Project Office. The aim of this meeting is to clarify any doubts about the Inteli Project Charter (TAPI), which contains a description of the problem, the timetable, the resources and technologies involved and the project's objectives.

7 face-to-face Inteli and Partner meetings:


During the projects the meetings held strengthen the relationship with the students and help give the best direction for successful deliveries.

• Executive Onboarding
• Kickoff
• Sprint validations: 4 meetings
• Final presentation of the prototypes

Kickoff meetings, sprint validations and prototype deliveries last approximately 2 hours and will take place on the Inteli campus. Meeting invitations to book agendas will be sent out by the Project Office after the initiatives have been selected.

The delivery to be made by the student groups consists of a prototype that incorporates the functionalities/requirements defined for the project in question, in line with the learning content presented and agreed with the market partner selected through the project office.

The prototypes developed are made available for use by the partner after one month of the module.

Check out the prototypes already made in this module.

The aim of this project is to build a predictive maintenance support system using machine learning and artificial intelligence techniques. Throughout the project, a system will be designed and implemented to load the partner's data and build, train and deploy the artificial intelligence model. An interface will also be built to enable system users to consult and feed the model used, as well as visualizing the data with a dashboard.

APPLICATION EXAMPLES:

• Predictive maintenance system in hospitals: Machines such as MRI and CT scanners are essential for treating patients, predictive maintenance uses data and sensors to detect wear and schedule maintenance, preventing unexpected failures. This saves resources and extends the life of medical equipment;
• Predictive maintenance systems for card machines: Predictive maintenance for payment devices, such as card machines ("maquininha" or PDQ), uses sensors and machine learning algorithms to detect signs of wear and predict when maintenance is required;
• Predictive maintenance system for productive machines: Predictive maintenance on industrial equipment helps reduce costs and prevent equipment failures by analyzing sensor data and using machine learning algorithms to predict when maintenance is required.

MANDATORY INFRASTRUCTURE RESOURCES:

• Programming languages and technologies for the machine learning application, frontend, backend and cloud deployment: C, C++, Python, JavaScript, HTML, CSS and others that are relevant to the application developed;
• Access to a cloud platform with functionality for data engineering and machine learning pipelines;
• Version control system: Git with distribution and collaboration on the Github platform;
• The proof of concept must necessarily have a backend, frontend and a data engineering pipeline with the application of machine learning;
• Frameworks, libraries and/or software for implementing data visualization systems in dashboard format;
• Access to a dataset with annotations and of a size suitable for training machine learning models for the application in question.

COMPLETION AND DELIVERY OF THE PROJECT:

All the prototypes generated during the project are delivered at the end of the 10th week.

Partner commitment


For the partnership to be a success, the commitment of the partner is essential at all stages of the project. After registering and selecting the initiative, the partner selects a point of contact for the understanding and definition phase. A minimum of 20 hours is required over the course of the project, which will be distributed over 7 face-to-face meetings (each lasting between 1 and 2 hours) and remote moments for clarifying doubts if necessary.

Closing the scope


The Project Office team sends the partner the Inteli Project Opening Form (TAPI) for completion. The partner must fill in this document detailing the scope of the project and return it to the Project Office.
An alignment meeting will be scheduled between the Partner, the Academic Team and the Inteli Project Office. The aim of this meeting is to clarify any doubts about the Inteli Project Charter (TAPI), which contains a description of the problem, the timetable, the resources and technologies involved and the project's objectives.

7 face-to-face Inteli and Partner meetings:


During the projects the meetings held strengthen the relationship with the students and help give the best direction for successful deliveries.

• Executive Onboarding
• Kickoff
• Sprint validations: 4 meetings
• Final presentation of the prototypes

Kickoff meetings, sprint validations and prototype deliveries last approximately 2 hours and will take place on the Inteli campus. Meeting invitations to book agendas will be sent out by the Project Office after the initiatives have been selected.

The delivery to be made by the student groups consists of a prototype that incorporates the functionalities/requirements defined for the project in question, in line with the learning content presented and agreed with the selected Market Partner via the Project Office. The prototypes developed are made available for use by the partner after one month of the end of the module.

Check out the prototypes already made in this module.

The aim of this project is to develop a proof of concept for a system with edge computing architecture, so as to enable the implementation of a system with artificial intelligence without overloading the central server. The project focuses on each of the layers of the architecture, with the main objectives being the implementation of:

• Training and fine tuning robust deep learning models on high-performance computers;
• Inference systems for artificial intelligence models in embedded devices;
• Nodes for queuing and pre-processing data sent by embedded devices;
• Cloud server architecture, capable of storing the data received in high-performance databases and feeding business intelligence/dashboard systems;
• A simplified dashboard proposal for visualizing the data collected.

Application examples

• Smart Traffic Monitoring: In smart cities, camera systems and sensors installed at traffic lights and intersections can process data in real time to optimize traffic flows. By analyzing the images and traffic data locally, the system can adjust traffic signals in real time to reduce congestion and improve road safety;
• Remote Medical Assistance: Edge computing devices can be used for remote patient monitoring, allowing real-time analysis of health data such as vital signs. This enables a faster response in critical situations and reduces the load on centralized healthcare systems.

MANDATORY INFRASTRUCTURE RESOURCES:

In order to carry out the proposed proof of concept, hardware, software and data resources are required. The hardware resources required are:

• High-performance computers with high video memory capacity for training deep learning models;
• Embedded devices with microprocessor-compatible SoCs (e.g. raspberry pi);
• Embedded devices with microcontrollers with high performance constraints; and
• Sensors for measuring the relevant data (e.g. cameras for computer vision, microphones for speech recognition).

The software resources required are:

• Cloud server system (e.g. Microsoft Azure, AWS, GCP);
• Libraries for training artificial intelligence models (e.g. Torch);
• Libraries for inference of artificial intelligence models compatible with embedded devices (e.g. TinyML);
• NoSQL database system compatible with mutable objects (e.g. MongoDB);
• System for scalable orchestration of edge device processing nodes (e.g. KubeEdge);
• System for processing complex events with high throughput (e.g. Apache Nifi, Apache Kafka, Redis); and
• Tools for building dashboards (e.g. Kibana, Grafana)

The data resources required are:

• Previously processed and cleaned dataset for training/fine tuning the artificial intelligence models that will be implemented at the edge.

COMPLETION AND DELIVERY OF THE PROJECT:

All the prototypes generated during the project are delivered at the end of the 10th week.

Partner commitment


For the partnership to be a success, the commitment of the partner is essential at all stages of the project. After registering and selecting the initiative, the partner selects a point of contact for the understanding and definition phase. A minimum of 20 hours is required over the course of the project, which will be distributed over 7 face-to-face meetings (each lasting between 1 and 2 hours) and remote moments for clarifying doubts if necessary.

Closing the scope


The Project Office team sends the partner the Inteli Project Opening Form (TAPI) for completion. The partner must fill in this document detailing the scope of the project and return it to the Project Office.
An alignment meeting will be scheduled between the Partner, the Academic Team and the Inteli Project Office. The aim of this meeting is to clarify any doubts about the Inteli Project Charter (TAPI), which contains a description of the problem, the timetable, the resources and technologies involved and the project's objectives.

7 face-to-face Inteli and Partner meetings:


During the projects the meetings held strengthen the relationship with the students and help give the best direction for successful deliveries.

• Executive Onboarding
• Kickoff
• Sprint validations: 4 meetings
• Final presentation of the prototypes

Kickoff meetings, sprint validations and prototype deliveries last approximately 2 hours and will take place on the Inteli campus. Meeting invitations to book agendas will be sent out by the Project Office after the initiatives have been selected.

The delivery to be made by the student groups consists of a prototype that incorporates the functionalities/requirements defined for the project in question, in line with the learning content presented and agreed with the market partner selected through the project office. The prototypes developed are made available for use by the partner one month after the end of the module.

Check out the prototypes already made in this module.

The project aims to train students to develop advanced solutions in natural language processing (NLP) and generative artificial intelligence (AI). These solutions aim to solve complex problems in organizations where it is crucial that computer systems understand, interpret, and manage human language naturally and effectively.

APPLICATION EXAMPLES:

• Customer Service and Support (Chatbots and Virtual Assistants): Development of automatic response systems that can understand and respond to customer queries in natural language (text), providing efficient customer service and reducing waiting times.
• CV Analysis and Talent Matching: Automated tools to analyze CVs, evaluate skills and experience in textual format, and suggest candidates for job vacancies and facilitate the generation of personalized CVs, optimizing the recruitment process.

Mandatory infrastructure resources:

1. Python: Versatile, high-level programming language.
2. TensorFlow: Open source deep learning framework.
3. PyTorch: Deep learning framework with a focus on flexibility.
4. NumPy: Essential library for numerical computation in Python.
5. Scikit-learn: Machine learning library in Python.
6. GPUs: Graphics processing unit for computational acceleration.
7. Clusters: Sets of interconnected computers for parallel processing.
8. Cloud: Scalable computing platforms based in the cloud.
9. Google Colab Pro Plus: cloud and collaborative development environment.
10. Git: Repository and version control tool.
11. Flask: API development tool in Python.
12. Ngrok: Tunneling tool for agile experimentation with endpoints (e.g. tunneling to quickly make an API running locally available).
13. Hugging Face: Open LLM model platform available with API access.
14. Langchain: Agent development tool based on LLM models.
15. Ollama: Tool for local execution of open LLM models.

Partner commitment


For the partnership to be a success, the commitment of the partner is essential at all stages of the project. After registering and selecting the initiative, the partner selects a point of contact for the understanding and definition phase. A minimum of 20 hours is required over the course of the project, which will be distributed over 7 face-to-face meetings (each lasting between 1 and 2 hours) and remote moments for clarifying doubts if necessary.

Closing the scope


The Project Office team sends the partner the Inteli Project Opening Form (TAPI) for completion. The partner must fill in this document detailing the scope of the project and return it to the Project Office.
An alignment meeting will be scheduled between the Partner, the Academic Team and the Inteli Project Office. The aim of this meeting is to clarify any doubts about the Inteli Project Charter (TAPI), which contains a description of the problem, the timetable, the resources and technologies involved and the project's objectives.

7 face-to-face Inteli and Partner meetings:


During the projects the meetings held strengthen the relationship with the students and help give the best direction for successful deliveries.

• Executive Onboarding
• Kickoff
• Sprint validations: 4 meetings
• Final presentation of the prototypes

Kickoff meetings, sprint validations and prototype deliveries last approximately 2 hours and will take place on the Inteli campus. Meeting invitations to book agendas will be sent out by the Project Office after the initiatives have been selected.

The delivery to be made by the student groups consists of a prototype that incorporates the functionalities/requirements defined for the project in question, in line with the learning content presented and agreed with the selected Market Partner via the Project Office. The prototypes developed are made available for use by the partner after one month of the end of the module.

Check out the prototypes already made in this module.

The aim of this project is a complete immersion in the development of an advanced data app, aimed at improving corporate governance and supporting strategic decisions in organizations. It will use advanced algorithms to clean, categorize and structure this data, making it ready for in-depth analysis. The importance of the user interface will be explored, developing intuitive dashboards that highlight key performance indicators (KPIs) essential for corporate governance. Interactive functionalities will be implemented to allow users to customize their data visualizations and perform in-depth exploratory analyses. Strict security and compliance protocols will be introduced, guaranteeing the protection of sensitive data and compliance with internal and external regulations and policies.

APPLICATION EXAMPLES:

• Implementation of advanced algorithms for processing unstructured data, such as corporate e-mails, transaction records and documents, in order to guarantee compliance with privacy and data security regulations, as well as ensuring the integrity and quality of the data used for strategic decision-making.
• Development of intuitive user interfaces, with dynamic dashboards that highlight specific KPIs related to data governance, such as regulatory compliance metrics, data quality and the effectiveness of security controls, providing a clear and objective view of the current state of data in the organization.

Mandatory Infrastructure Resources:

Virtual machines for applications, cloud database server (such as Amazon RDS, Google Cloud SQL or Microsoft Azure SQL Database) for secure and scalable data storage, data visualization applications (such as Tableau, Power BI or Qlik Sense) to assist in the visual representation and analysis of the proposed data architecture. In addition, data integration tools (e.g. Apache Kafka, Talend or Informatica) will be required to facilitate the smooth integration of data from multiple business sources. Natural language processing and text analysis algorithms will also be required to handle unstructured data efficiently and extract insights relevant to data governance. Finally, advanced security systems with encryption and role-based access control will be indispensable to ensure data protection and compliance.

COMPLETION AND DELIVERY OF THE PROJECT:

All the prototypes generated during the project are delivered at the end of the 10th week.

Partner commitment


For the partnership to be a success, the commitment of the partner is essential at all stages of the project. After registering and selecting the initiative, the partner selects a point of contact for the understanding and definition phase. A minimum of 20 hours is required over the course of the project, which will be distributed over 7 face-to-face meetings (each lasting between 1 and 2 hours) and remote moments for clarifying doubts if necessary.

Closing the scope


The Project Office team sends the partner the Inteli Project Opening Form (TAPI) for completion. The partner must fill in this document detailing the scope of the project and return it to the Project Office.
An alignment meeting will be scheduled between the Partner, the Academic Team and the Inteli Project Office. The aim of this meeting is to clarify any doubts about the Inteli Project Charter (TAPI), which contains a description of the problem, the timetable, the resources and technologies involved and the project's objectives.

7 face-to-face Inteli and Partner meetings:


During the projects the meetings held strengthen the relationship with the students and help give the best direction for successful deliveries.

• Executive Onboarding
• Kickoff
• Sprint validations: 4 meetings
• Final presentation of the prototypes

Kickoff meetings, sprint validations and prototype deliveries last approximately 2 hours and will take place on the Inteli campus. Meeting invitations to book agendas will be sent out by the Project Office after the initiatives have been selected.

The delivery to be made by the student groups consists of a prototype that incorporates the functionalities/requirements defined for the project in question, in line with the learning content presented and agreed with the selected market partner through the project office. The prototypes developed are made available for use by the partner after one month of the end of the module.

Check out the prototypes already made in this module.

The aim is to automate with audio recognition. The solution includes the construction of a system that converts voice to text, the intention classification system given the user's text, using artificial intelligence techniques, contemplated in the area of natural language processing. In addition, this system will be designed to integrate with commercial IoT devices, such as smart light bulbs, humidifiers, heaters, among other actuators, which have an open communication interface via a local network and the Internet. Finally, the students will version the documents using the Git tool and make the complete solution available on GitHub.

To support this system, students will have to design it using the concepts of scalability, load balancing, fault tolerance, service-oriented architecture, management and development methodologies, to solve a real problem in the context presented by the selected market partner.

APPLICATION EXAMPLES:

• Voice recognition in hands-free scenarios (situations in which the user has a preference for hands-free interactions, such as access control after shopping in a market, while driving a car, while cooking at home);
• Personalized chatbots (adaptive responses according to the user's feelings);
• Voice recognition and conversational interfaces for accessibility applications.

MANDATORY INFRASTRUCTURE RESOURCES:

• Programming languages and technologies for the machine learning application, frontend, backend and cloud deployment: C, C++, Python, JavaScript, HTML, CSS and others that are relevant to the application developed;
• Access to a cloud platform with functionality for data engineering and machine learning pipelines;
• Version control system: Git with distribution and collaboration on the GitHub platform;
• Database: DynamoDB, SQLite, MySQL or PostgreSQL or Market Partner Database;
• Integrated Development Environment- IDE (VSCode);
• Services from cloud technology partners;
• Frameworks, libraries and/or software for integration with the IoT system provided by the institution;
• Access to a data set with annotations and of a size consistent with the training of machine learning models for the application in question (e.g., examples of sentences categorized with intentions, expected responses and/or expected actions).

COMPLETION AND DELIVERY OF THE PROJECT:

All the prototypes generated during the project are delivered at the end of the 10th week.

Partner commitment


For the partnership to be a success, the commitment of the partner is essential at all stages of the project. After registering and selecting the initiative, the partner selects a point of contact for the understanding and definition phase. A minimum of 20 hours is required over the course of the project, which will be distributed over 7 face-to-face meetings (each lasting between 1 and 2 hours) and remote moments for clarifying doubts if necessary.

Closing the scope


The Project Office team sends the partner the Inteli Project Opening Form (TAPI) for completion. The partner must fill in this document detailing the scope of the project and return it to the Project Office.
An alignment meeting will be scheduled between the Partner, the Academic Team and the Inteli Project Office. The aim of this meeting is to clarify any doubts about the Inteli Project Charter (TAPI), which contains a description of the problem, the timetable, the resources and technologies involved and the project's objectives.

7 face-to-face Inteli and Partner meetings:


During the projects the meetings held strengthen the relationship with the students and help give the best direction for successful deliveries.

• Executive Onboarding
• Kickoff
• Sprint validations: 4 meetings
• Final presentation of the prototypes

Kickoff meetings, sprint validations and prototype deliveries last approximately 2 hours and will take place on the Inteli campus. Meeting invitations to book agendas will be sent out by the Project Office after the initiatives have been selected.

The delivery to be made by the student groups consists of a prototype that incorporates the functionalities/requirements defined for the web application in question, in line with the learning content presented and agreed with the selected Market Partner via the Project Office. The prototypes developed are made available for use by the partner one month after the end of the module.

Check out the prototypes already made in this module.

The overall objective of the project is:

• To equip students with the skills to structure real-world financial asset tokenization transactions as an alternative mechanism for raising capital and increasing liquidity for companies.
• Map out the capital structure and model the technical, financial, and regulatory architecture for the issuance of digital assets.
• Understand and apply the fundamentals of blockchain networks, smart contracts, and token standards to reduce intermediaries and fractionalize capital.
• Develop technical documentation for the operation and a functional prototype on a token issuance and management platform.

APPLICATION EXAMPLES:

• Advance Payment of Receivables and Future Revenue: A technological framework for converting expected cash flows into tokens to raise funds immediately.
• Tokenization of Real Assets: The transformation of illiquid physical assets (such as corporate real estate or machinery) into tradable digital shares.
• Corporate Debt and Credit Funds: Automated issuance of debt tokens as an alternative to debentures or CCBs, as well as the structuring of tokenized FIDCs.
• Equity Financing: Issuance of equity tokens for growth rounds, ensuring full transparency and auditability on the blockchain.

MANDATORY INFRASTRUCTURE RESOURCES:

• Provision of structured financial data from the partner company, including financial statements, cash flow statements, and accounts receivable.
• Involvement of the company’s legal and financial departments to ensure structural compliance and regulatory compliance (CVM and Bacen).
• The existence of a tangible asset or identifiable receivable with predictable cash flow or verifiable value that serves as collateral for the transaction.
• Use of technology stacks and modeling frameworks suitable for blockchain, smart contracts (ERC-20, ERC-1400 standards), and tokenomics analysis.

Partner commitment

For the partnership to be a success, the commitment of the partner is essential at all stages of the project. After registering and selecting the initiative, the partner selects a point of contact for the understanding and definition phase. A minimum of 20 hours is required over the course of the project, which will be distributed over 7 face-to-face meetings (each lasting between 1 and 2 hours) and remote moments to clarify any doubts.

Closing the scope

The Project Office team sends the Inteli Project Initiation Agreement (TAPI) to the partner for completion. The partner must complete this document with details regarding the project scope and return it to the Project Office.
An alignment meeting will be scheduled between the Partner, the Academic Team, and Inteli’s Project Office. The purpose of this meeting is to address any questions regarding the Inteli Project Initiation Agreement (TAPI), which includes a description of the problem, the timeline, the resources and technologies involved, and the project objectives.

7 face-to-face meetings Inteli and Partner:

During the projects, the meetings held strengthen the relationship with the students and help provide the best guidance for successful deliveries.

• Executive Onboarding
• Kickoff
• Sprint validations: 4 meetings
• Final presentation of the prototypes

Kickoff meetings, sprint validations and prototype deliveries last approximately 2 hours and will take place on the Inteli campus. Meeting invitations to book agendas will be sent out by the Project Office after the initiatives have been selected.

The delivery to be made by the student groups consists of a prototype that incorporates the functionalities/requirements defined for the web application in question, in line with the learning content presented and agreed with the selected Market Partner via the Project Office. The prototypes developed are made available for use by the partner one month after the end of the module.

The overall objective of the project is:

More information about this module will be available soon.

APPLICATION EXAMPLES:

More information about this module will be available soon.

MANDATORY INFRASTRUCTURE RESOURCES:

More information about this module will be available soon.

Partner commitment

For the partnership to be a success, the commitment of the partner is essential at all stages of the project. After registering and selecting the initiative, the partner selects a point of contact for the understanding and definition phase. A minimum of 20 hours is required over the course of the project, which will be distributed over 7 face-to-face meetings (each lasting between 1 and 2 hours) and remote moments to clarify any doubts.

Closing the scope

The Project Office team sends the Inteli Project Initiation Agreement (TAPI) to the partner for completion. The partner must complete this document with details regarding the project scope and return it to the Project Office.
An alignment meeting will be scheduled between the Partner, the Academic Team, and Inteli’s Project Office. The purpose of this meeting is to address any questions regarding the Inteli Project Initiation Agreement (TAPI), which includes a description of the problem, the timeline, the resources and technologies involved, and the project objectives.

7 face-to-face meetings Inteli and Partner:

During the projects, the meetings held strengthen the relationship with the students and help provide the best guidance for successful deliveries.

• Executive Onboarding
• Kickoff
• Sprint validations: 4 meetings
• Final presentation of the prototypes

Kickoff meetings, sprint validations and prototype deliveries last approximately 2 hours and will take place on the Inteli campus. Meeting invitations to book agendas will be sent out by the Project Office after the initiatives have been selected.

The delivery to be made by the student groups consists of a prototype that incorporates the functionalities/requirements defined for the web application in question, in line with the learning content presented and agreed with the selected Market Partner via the Project Office. The prototypes developed are made available for use by the partner one month after the end of the module.

The aim of this project is to develop an IoT project to solve a real problem in the context presented by the Partner.

APPLICATION EXAMPLES:

• Monitoring in condominiums: water tank level, garden irrigation, lighting or presence of people in common areas, parking spaces in garages;
• Current and voltage sensors in homes, hospitals and hotels;
• Agribusiness: soil moisture, wind speed, atmospheric temperature, phosphorus, potassium and nitrogen levels. Remote control of livestock and poultry, weight and feed and water consumption.

COMPLETION AND DELIVERY OF THE PROJECT:

All the prototypes generated during the project are delivered at the end of the 10th week.

Partner commitment


For the partnership to be a success, the commitment of the partner is essential at all stages of the project. After registering and selecting the initiative, the partner selects a point of contact for the understanding and definition phase. A minimum of 20 hours is required over the course of the project, which will be distributed over 7 face-to-face meetings (each lasting between 1 and 2 hours) and remote moments for clarifying doubts if necessary.

Closing the scope


The Project Office team sends the partner the Inteli Project Opening Form (TAPI) for completion. The partner must fill in this document detailing the scope of the project and return it to the Project Office.
An alignment meeting will be scheduled between the Partner, the Academic Team and the Inteli Project Office. The aim of this meeting is to clarify any doubts about the Inteli Project Charter (TAPI), which contains a description of the problem, the timetable, the resources and technologies involved and the project's objectives.

7 face-to-face Inteli and Partner meetings:


During the projects the meetings held strengthen the relationship with the students and help give the best direction for successful deliveries.

• Executive Onboarding
• Kickoff
• Sprint validations: 4 meetings
• Final presentation of the prototypes

Kickoff meetings, sprint validations and prototype deliveries last approximately 2 hours and will take place on the Inteli campus. Meeting invitations to book agendas will be sent out by the Project Office after the initiatives have been selected.

The delivery to be made by the student groups consists of a prototype that incorporates the functionalities/requirements defined for the project in question, in line with the learning content presented and agreed with the selected market partner through the project office. The prototypes developed are made available for use by the partner after one month of the end of the module.

Check out the prototypes already made in this module.

The aim of this project is to create a Big Data pipeline based on AWS (Amazon Web Services) resources or on premise, to carry out descriptive statistical analysis on data stored in a data lake or data warehouse. In addition, the aim is to create an infographic based on the results of the statistical study, in a generic way for the best delivery of value to the customer.

APPLICATION EXAMPLES:

• Identification of patterns and trends in the data;
• Discovery of relevant insights for decision-making;
• Comparative analysis between different data sets.

MANDATORY INFRASTRUCTURE RESOURCES:

• A data set with a minimum volume of 1 gigabyte in total must be provided for use in the Big Data pipeline, which can be logs via streaming or batches via different protocols to be analyzed;
• The data set should preferably be of unstructured origin;
• The results obtained from the statistical analysis of the data will be validated with the client before the infographic is created.

COMPLETION AND DELIVERY OF THE PROJECT

All the prototypes generated during the project are delivered at the end of the 10th week.

Partner commitment


For the partnership to be a success, the commitment of the partner is essential at all stages of the project. After registering and selecting the initiative, the partner selects a point of contact for the understanding and definition phase. A minimum of 20 hours is required over the course of the project, which will be distributed over 7 face-to-face meetings (each lasting between 1 and 2 hours) and remote moments for clarifying doubts if necessary.

Closing the scope


The Project Office team sends the partner the Inteli Project Opening Form (TAPI) for completion. The partner must fill in this document detailing the scope of the project and return it to the Project Office.
An alignment meeting will be scheduled between the Partner, the Academic Team and the Inteli Project Office. The aim of this meeting is to clarify any doubts about the Inteli Project Charter (TAPI), which contains a description of the problem, the timetable, the resources and technologies involved and the project's objectives.

7 face-to-face Inteli and Partner meetings:


During the projects the meetings held strengthen the relationship with the students and help give the best direction for successful deliveries.

• Executive Onboarding
• Kickoff
• Sprint validations: 4 meetings
• Final presentation of the prototypes

Kickoff meetings, sprint validations and prototype deliveries last approximately 2 hours and will take place on the Inteli campus. Meeting invitations to book agendas will be sent out by the Project Office after the initiatives have been selected.

The delivery to be made by the student groups consists of a prototype that incorporates the functionalities/requirements defined for the project in question, in line with the learning content presented and agreed with the selected Market Partner via the Project Office. The prototypes developed are made available for use by the partner after one month of the end of the module.

Check out the prototypes already made in this module.

The aim of this project is to analyze and design a software architecture, as a fundamental structure that defines the organization, behavior and interaction of the components of a system. The main aspects of a system will be addressed, such as its different parts, responsibilities, interfaces and design decisions that guide its construction. The system's scalability, maintainability, security and performance will also be considered, as well as an overview of the system to facilitate communication between members of the development team and stakeholders.

APPLICATION EXAMPLES:

• Improve the security of system transactions by focusing on integrity (fraud);
• Improving the security of transactions and information by focusing on the LGPD (privacy, and purpose in accordance with the consent form);
• Improve the capacity and scale of the system in terms of transactions and daily customers (by 1000%).

MANDATORY INFRASTRUCTURE RESOURCES:

• Programming languages and technologies for the machine learning application, frontend, backend and cloud deployment: C, C++, Python, JavaScript, HTML, CSS and others that are relevant to the application developed;
• Access to any services through the partnership's controlled access interfaces in the form of APIs;
• Access to a cloud platform with functionality for data engineering and machine learning pipelines;
• Version control system: Git with distribution and collaboration on the GitHub platform;
• Database: DynamoDB, SQLite, MySQL or PostgreSQL or Market Partner Database;
• Integrated Development Environment- IDE (VSCode);
• Services from cloud technology partners;
• Frameworks, libraries and/or software for integration with the IoT system provided by the institution;
• Access to a data set for possible use in the simulation and training of machine learning models.

COMPLETION AND DELIVERY OF THE PROJECT

All the prototypes generated during the project are delivered at the end of the 10th week.

Partner commitment


For the partnership to be a success, the commitment of the partner is essential at all stages of the project. After registering and selecting the initiative, the partner selects a point of contact for the understanding and definition phase. A minimum of 20 hours is required over the course of the project, which will be distributed over 7 face-to-face meetings (each lasting between 1 and 2 hours) and remote moments for clarifying doubts if necessary.

Closing the scope


The Project Office team sends the partner the Inteli Project Opening Form (TAPI) for completion. The partner must fill in this document detailing the scope of the project and return it to the Project Office.
An alignment meeting will be scheduled between the Partner, the Academic Team and the Inteli Project Office. The aim of this meeting is to clarify any doubts about the Inteli Project Charter (TAPI), which contains a description of the problem, the timetable, the resources and technologies involved and the project's objectives.

7 face-to-face Inteli and Partner meetings:


During the projects the meetings held strengthen the relationship with the students and help give the best direction for successful deliveries.

• Executive Onboarding
• Kickoff
• Sprint validations: 4 meetings
• Final presentation of the prototypes

Kickoff meetings, sprint validations and prototype deliveries last approximately 2 hours and will take place on the Inteli campus. Meeting invitations to book agendas will be sent out by the Project Office after the initiatives have been selected.

The delivery to be made by the student groups consists of a prototype that incorporates the functionalities/requirements defined for the project in question, in line with the learning content presented and agreed with the selected market partner through the project office. The prototypes developed are made available for use by the partner after one month of the end of the module.

Check out the prototypes already made in this module.

The overall aim of the project is to implement a service robot from a mobile robotic base. To this end, the specific objectives are:

• Development and integration of a mapping and navigation system in closed environments with controlled movement of people;
• Development and integration of a chatbot capable of interacting with people in the controlled environment;
• Development and integration of systems for interaction with human beings using natural language. To do this, it will be necessary to find solutions for both audio-to-text and text-to-audio conversion (speech synthesis).

APPLICATION EXAMPLES:

• Robot butlers/waiters/customer service in general;
• Personal assistant for the elderly;
• Concierge service for events and/or offices.

MANDATORY INFRASTRUCTURE RESOURCES:

• Programming languages and technologies for the machine learning application, frontend, backend and cloud deployment: C, C++, Python, JavaScript, HTML, CSS and others that are relevant to the application developed;
• Meta-operating system for developing robotics applications (ROS 2 Humble);
• Version control system: Git with distribution and collaboration on the Github platform.

COMPLETION AND DELIVERY OF THE PROJECT:

All the prototypes generated during the project are delivered at the end of the 10th week.

Partner commitment


For the partnership to be a success, the commitment of the partner is essential at all stages of the project. After registering and selecting the initiative, the partner selects a point of contact for the understanding and definition phase. A minimum of 20 hours is required over the course of the project, which will be distributed over 7 face-to-face meetings (each lasting between 1 and 2 hours) and remote moments for clarifying doubts if necessary.

Closing the scope


The Project Office team sends the partner the Inteli Project Opening Form (TAPI) for completion. The partner must fill in this document detailing the scope of the project and return it to the Project Office.
An alignment meeting will be scheduled between the Partner, the Academic Team and the Inteli Project Office. The aim of this meeting is to clarify any doubts about the Inteli Project Charter (TAPI), which contains a description of the problem, the timetable, the resources and technologies involved and the project's objectives.

7 face-to-face Inteli and Partner meetings:


During the projects the meetings held strengthen the relationship with the students and help give the best direction for successful deliveries.

• Executive Onboarding
• Kickoff
• Sprint validations: 4 meetings
• Final presentation of the prototypes

Kickoff meetings, sprint validations and prototype deliveries last approximately 2 hours and will take place on the Inteli campus. Meeting invitations to book agendas will be sent out by the Project Office after the initiatives have been selected.

The delivery to be made by the student groups consists of a prototype that incorporates the functionalities/requirements defined for the project in question, in line with the learning content presented and agreed with the selected market partner through the project office. The prototypes developed are made available for use by the partner after one month of the end of the module.

Check out the prototypes already made in this module.

The aim of this project is to develop a system that has an interface or IDE (Integrated Development Environment) for programming occupational therapy activities using a sensory mat connected to the physical device, the Greg Maker. A user interface will be created that provides access to the device's functionalities and takes into account the limitations of the system's resources, the process of building the compiler or interpreter that drives the hardware, proper integration with other parts of the system, such as business logic and hardware controllers, is also crucial to the success of the interface. In the end, the system needs to propose alternatives for building/programming activities related to occupational therapy using the sensory mat.

APPLICATION EXAMPLES:

• Development of a sensory mat that offers a variety of programmable tactile, visual and sound stimuli to help manage stress, anxiety and sensory sensitivity in children and adults with Autism Spectrum Disorder (ASD);
• Intuitive programming interface for therapists and patients;
• Development of therapeutic games in assistive technology.

MANDATORY INFRASTRUCTURE RESOURCES:

• Sensory mat;
• Greg Maker;
• Python or C language for the backend;
• Javascript, HTML and CSS languages for the frontend;
• Data visualization with a graphic library suitable for the project;
• Version control system: GitHub platform;
• Internet access.

PROJECT COMPLETION AND DELIVERY

All the prototypes generated during the project are delivered at the end of the 10th week.

Partner commitment


For the partnership to be a success, the commitment of the partner is essential at all stages of the project. After registering and selecting the initiative, the partner selects a point of contact for the understanding and definition phase. A minimum of 20 hours is required over the course of the project, which will be distributed over 7 face-to-face meetings (each lasting between 1 and 2 hours) and remote moments for clarifying doubts if necessary.

Closing the scope


The Project Office team sends the partner the Inteli Project Opening Form (TAPI) for completion. The partner must fill in this document detailing the scope of the project and return it to the Project Office.
An alignment meeting will be scheduled between the Partner, the Academic Team and the Inteli Project Office. The aim of this meeting is to clarify any doubts about the Inteli Project Charter (TAPI), which contains a description of the problem, the timetable, the resources and technologies involved and the project's objectives.

7 face-to-face Inteli and Partner meetings:


During the projects the meetings held strengthen the relationship with the students and help give the best direction for successful deliveries.

• Executive Onboarding
• Kickoff
• Sprint validations: 4 meetings
• Final presentation of the prototypes

Kickoff meetings, sprint validations and prototype deliveries last approximately 2 hours and will take place on the Inteli campus. Meeting invitations to book agendas will be sent out by the Project Office after the initiatives have been selected.

The delivery to be made by the student groups consists of a prototype that incorporates the functionalities/requirements defined for the project in question, in line with the learning content presented and agreed with the selected market partner through the project office. The prototypes developed are made available for use by the partner after one month of the end of the module.

Check out the prototypes already made in this module.

The overall objective of the project is:

• To enable students to analyze investment scenarios and construct optimized investment portfolios using Modern Portfolio Theory and Markowitz’s Efficient Frontier.
• Quantify risk and return by calculating variance, standard deviation, and historical/expected returns for individual assets and portfolios.
• Evaluate portfolio performance using established metrics such as the Sharpe Ratio, the Treynor Ratio, Jensen's Alpha, and the Security Market Line (SML).
• Develop a quantitative simulation tool that allows users to enter assets and obtain a dynamic calculation of the expected return.

APPLICATION EXAMPLES:

• Corporate Treasury and Pension Fund Management: Structuring portfolios to intelligently allocate the company’s excess cash, balancing liquidity and security.
• Portfolio Rebalancing and Protection (Wealth Management): Development of asset allocation and capital protection (hedging) strategies using negative correlation matrices in stress scenarios.
• Quantitative Analysis and Equity Research: Development of interactive simulators and performance reports to support strategic recommendations for buying or selling assets.

MANDATORY INFRASTRUCTURE RESOURCES:

• Active involvement of the partner company's financial managers in setting risk tolerance limits and measurable return targets.
• Provision of time series of market data (price history, returns, and indicators such as the Selic, IPCA, and CDI) for analyzable fixed-income or equity assets.
• Access to and use of computational modeling tools and databases, such as Excel (Solver), Python (Pandas, NumPy, SciPy), Yahoo Finance, or Bloomberg.

Partner commitment

For the partnership to be a success, the commitment of the partner is essential at all stages of the project. After registering and selecting the initiative, the partner selects a point of contact for the understanding and definition phase. A minimum of 20 hours is required over the course of the project, which will be distributed over 7 face-to-face meetings (each lasting between 1 and 2 hours) and remote moments to clarify any doubts.

Closing the scope

The Project Office team sends the Inteli Project Initiation Agreement (TAPI) to the partner for completion. The partner must complete this document with details regarding the project scope and return it to the Project Office.
An alignment meeting will be scheduled between the Partner, the Academic Team, and Inteli’s Project Office. The purpose of this meeting is to address any questions regarding the Inteli Project Initiation Agreement (TAPI), which includes a description of the problem, the timeline, the resources and technologies involved, and the project objectives.

7 face-to-face meetings Inteli and Partner:

During the projects, the meetings held strengthen the relationship with the students and help provide the best guidance for successful deliveries.

• Executive Onboarding
• Kickoff
• Sprint validations: 4 meetings
• Final presentation of the prototypes

Kickoff meetings, sprint validations and prototype deliveries last approximately 2 hours and will take place on the Inteli campus. Meeting invitations to book agendas will be sent out by the Project Office after the initiatives have been selected.

The delivery to be made by the student groups consists of a prototype that incorporates the functionalities/requirements defined for the web application in question, in line with the learning content presented and agreed with the selected Market Partner via the Project Office. The prototypes developed are made available for use by the partner one month after the end of the module.