| Title: | DEC Rdb against the World |
| Moderator: | HERON::GODFRIND |
| Created: | Fri Jun 12 1987 |
| Last Modified: | Thu Feb 23 1995 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 1348 |
| Total number of notes: | 5438 |
I just read a little snippet from an Rfp that came out from the US Air
Force/Army. This is the AAFES - Army Air Force Exchange Services -
basically, all the BX's PX's, Movie houses and other services at all
the bases worldwide. The Rfp is asking for an information system.
The Database and Operating System sections are REAL short (although the
Rfp itself is 3 inches thick!
Mandatory's include (and if you don't say "YES" to a mandatory, you are
disqualified...)
Mandatorys: Database: Oracle
SQL*FORMS
O/S: Unix System V
Interesting that the Rfp comes out with the software already chosen....
Cheers,
Gil
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 548.1 | Spec Wars II | PHLACT::QUINN | Thu Jan 25 1990 19:30 | 15 | |
Gil,
Have you tried....
"Mr. COTR, (contracting officer's trechnical representative) can I see
your waiver for this DOD contract software system, justifying your
decision to preclude the use of ADA, the MIL-STD 1815A required
programming language?"
"But sir, you must have a waiver, because mandating ORACLE/UNIX
precludes an ADA development."
It won't close the sale, but it will open the field for us.
thomas
| |||||
| 548.2 | CISM::MORAN | When Money Speaks The Truth is? | Thu Jan 25 1990 20:50 | 7 | |
Not only is oracle the database required on this proposal BUT it
was demoed on a VAX. From all appearances there are only two serious
players for this proposal - HP and DEC. FYI - the potential winner
could get up to 150MM over the next few years worldwide. Fred Roberts
of the Dallas office has been waiting close to 1.5 years for this
to finally be released. Hope we win. Another FYI - the system
integration for all of this is being performed by Coopers & Lybrand.
| |||||
| 548.3 | V&V contractor??? | PHLACT::QUINN | Mon Jan 29 1990 15:04 | 25 | |
Another idea, maybe...
Have they selected a V&V (verification and validation) contractor yet?
If they have, begin courting favor with same, if they haven't, find one
or two, court them and get one selected.
Once you have them selected, start playing the paperwork game. V&V guys
check the paperwork, file it, forward it, caress it lovingly, etc.
They're odd, but necessary. What you can do is help them find (and
understand) internal documentation inconsistencies in the spec. Things
like mutually exclusive requirements and clauses, etc.
What this gets you (sorry, but its a pain!) is the opportunity to sic
the document guys on the functional guys who specified ORACLE. You do
it by pointing out that function X described in section LL.MMM.NNN
excludes design element Y in section AA.BBB.CCC. So they file a
software problem report (or whatever) and the specification review board
MUST answer it in writing and then ORACLE must fess up and .....
The above assumes, of course, that you can find real reasons,
spec-wise, why they shouldn't be using ORACLE.
Lemme know about this one, I'm curious.
thomas
| |||||