San Diego is a border metro. It is known for biotechnology and life sciences, for defense and the Navy, for wireless and telecommunications, and for manufacturing that crosses the line: a plant in Tijuana run by a company on the San Diego side is a common arrangement. This page begins with that arrangement, because it is where an engineer in Mexico who works in two languages matters most.
A plant on one side, the company on the other
A cross-border manufacturer usually keeps engineering, purchasing and its customers on the San Diego side and the production floor in Tijuana. Its documents follow the same split. Work instructions, quality records and shift reports tend to be written in Spanish. Specifications, customer complaints and management reports tend to be written in English. An AI system for that company has to read both, and it has to answer each person in the language of the question.
The closest published work is in Spanish and about plants. It is the platform of a lean manufacturing practice in Monterrey that works with food, metalworking and automotive plants: an open corpus, working tools for the floor, an assistant grounded in that corpus and an MCP server so that agents read the same material people read. Applied to a manufacturer's own documents, those pieces are what I describe under RAG and data platforms and internal tools with AI. A page in Spanish covers the same ground for the plant: AI engineer for companies in Tijuana.
One clock at the border, another in Monterrey
Tijuana follows the same Pacific time as San Diego, seasonal change included, so the plant and the company never disagree about the hour. Monterrey does not change its clocks. Both border cities are two hours behind Monterrey from early November to mid March, and one hour behind from mid March to early November. Eight in the morning at the border is ten in Monterrey in winter and nine in summer.
Biotechnology and life sciences
Life science companies keep protocols, batch records and submissions under document control, and they must show who changed what. They ask for search that respects that control. No case study on this site comes from biotechnology. What transfers is the method of answering only from approved documents, and the guide on agent auditability, which sets out what to record each time an agent acts.
Defense, the Navy and wireless
Defense work and the Navy are government, and no case study on this site comes from government. What transfers is narrow: a record of every action an agent takes, and a gateway that decides which tools a given agent may call. The MCP gateway case study describes the second.
Wireless and telecommunications companies have their data spread over many systems. For that the site shows an analytics platform and a data warehouse, both fed from operational systems and both written up as case studies.
Starting from either side
Whichever side owns the system sends the first email, in either language. I answer with a written proposal: what to build first, what access it takes and what I leave out. This page offers no one on the plant floor and no one in a meeting room in San Diego. The floor reaches me through its documents, and its people through a call.