In general that's true. But the question was how to progam it.
V-Nav uses info from the Performance page which is loaded on
the ground. It requests info via dashes and boxes which have to
or may be filled. The FMC needs info like, ZFM, cruise alt, cost index,reserve fuel etc. It calculates the most economic climb speed for the loaded data.
In the legs page of the FMC you can enter restrictions. Like at the
first point during climb you want to be above 2000' whith a
max speed of 230 Kts. This would look like this on the legs page:
Dayne 230/2000A
Or for example Dayne 230/2000B
Which implies that a/c will level off at 2000' until you have
passed Dayne with a max speed of 230 Kts.
This speed/Alt data may be entered manually or may already
be in the database. Departures are in the database
under the dep/arr page.
This also goes for descent. You can enter a restriction as
mentioned by Localiser Green to be at Dayne at Fl70. It will
be entered like this on the legs page:
Dayne ..../070
Or if you want to be above Fl70:
Dayne ..../070A etc. You get the point.
As you see I left the speed in dots. Because of the cost index
which was loaded before the flight the FMC will calculate a
best econ des speed. Which would be something like .79/290 Kts.
( Just a rough figure). The FMC will, as already stated,
make a V-Nav path all the way back to you cruising level and
calculate the descent point to reach Dayne at this level.
Does this answer your question?
Rgds