Canon global

The cutting-edge imageRUNNER ADVANCE (iR-ADV) series of multifunction office systems was developed by reviewing the product concept from the foundation up and determining its specifications from scratch. First, please tell us about this.

Kitozaki

We first recognized that we had to be even more user centric (customer oriented) than we had been in the past. Along with discussing desired features with the staff involved with product planning and design, we held a series of meetings with domestic and overseas sales staff. These in-depth discussions, our first efforts for the multifunction office system, resulted in the creation of a four-pillar concept. The first pillar is that the system must be easier to use and more comfortable for the user. This doesn't mean just for the workplace, but also for each individual in the workplace. The second pillar is that it must be able to work in conjunction with PCs and other multifunction office systems in an office, and increase work efficiency. The third pillar is that the system must have strong security features and be worry-free. The fourth pillar is that it must be environmentally friendly, conserve energy, and reduce running costs. We set high targets based on these concepts, but we couldn't reach those targets with just an extension of our existing devices. This is why we decided to begin development from scratch.

When did this take place?

Kitozaki

In 2005. At that time, we presented a mock-up and product concept for the new generation of multifunction office systems, in other words, the iR-ADV, at product exhibition that Canon held in New York, Paris, and Tokyo. To progress from this point until the first pre-production model could output its first sheet, it took close to twice as long as previous pre-production models.

I see. I can imagine how high your targets were. Wasn't development actually rather difficult?

Nakagaki

When I saw the mock-up, I thought, "How in the world are we going to make this?!" (Laughs) [We had to] put all exhaust vents on the back, significantly improve maintenance ease, and put areas that more frequently need maintenance work in the front. On top of that, [we had to] make it smaller, faster, and realize better image quality. From a mechanical-design standpoint, it was outrageous. We held discussions between the mechanical, electrical and hardware, and process design teams regarding the design of the internal structure.

Asahara

I worked on the application platform. The software architecture for the iR-ADV was very complex and large. When operations become concentrated, the system becomes overloaded and decreases in speed, making the experience less pleasant for the user. Because of that, we really wracked our brains over the software, trying to decide what should operate and when.

Nishiyama

I mainly handled software development for the user interface (UI). The iR-ADV has many new functions. We worked to develop a UI that would be easy for anyone to understand so that the large number of functions wouldn't become stressful for the user. We thoroughly reviewed the existing function display and remade it into a new UI, but we really struggled with understanding what it means to be "easy to understand" and what would make it easy to understand. We even held repeated meetings within the team.

It sounds like this was a multifunction office system development project that required you to think outside of the box. How big was the development structure?

Kitozaki

Including hardware and software, there were more than twice as many people as is usual for a new development project.

What was your feeling when you began working on development?

Asahara

I'm the youngest of the four of us, and actually, at the beginning of the development process, I wondered if it was okay for somebody young like me to be involved in reconsidering and adjusting the specifications of the entire system. But, my supervisor got me all fired up (laughs) and I remember deciding to hit it hard, specifically because it was such a big project.