I'm glad to hear that.
This whole procurement thing is quite interesting to me. I've been researching this quite a bit and I have some questions that relate to the statements of requirements that the air force, if I can call it the air force, and the land service have been moving to, which would streamline the process so that we basically get rid of these 1,700-page documents on technical requirements and get down to capabilities requirements and then put it out to industry a lot quicker, speeding up the process. But when the folks from the navy were here this morning they basically were talking differently, from the perspective of still basically designing those technical specifications.
From an overall procurement perspective, when you talk about the integration of the three different services or three different elements of the Canadian Forces and how you're dependent upon the navy and how you're dependent upon the air force to project forces and to sustain operations domestically or in foreign territory, how do you see the fact that we are going to design-build with the navy, to off-the-shelf with the air force, and off-the-shelf maybe with the army component? Is that going to pose any problems?
There's going to be significant lag time, if we go to design-build in the navy, compared to off-the-shelf with air force and army. I'm wondering how that affects your defence capabilities planning and your strategic planning in the future.