10.07.2015 Views

department of defense handbook guidance for acquisition ... - NAVAIR

department of defense handbook guidance for acquisition ... - NAVAIR

department of defense handbook guidance for acquisition ... - NAVAIR

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

MIL-HDBK-29612-1APre-RFP/RFQACTIVITIESRFP/RFQ RELEASECONTRACTORPROPOSALAcquisition PlanningData Call ConductedCDRL DevelopedGCO DevelopedData Deliverables andTypesUsersUse <strong>of</strong> DataSupport InfrastructureDelivery Modes/Format/MediaSpecifications/StandardsCITIS PROPOSAL (if CITISrequired)Bidder Suggestion <strong>for</strong> MoreEffective In<strong>for</strong>mationInterchangePROPOSALEVALUATIONSNEGOTIATIONCONTRACT AWARDImplement EvaluationPlanModification to GCOModification to Contractor'sApproachCDRL ModificationsUpgrade Infrastructure, ifRequiredFIGURE 3. The CALS GCO in the contracting process.C.4.2.1 Pre-RFP activities and RFP release. The GCO planning process should start asearly in the <strong>acquisition</strong> process as possible. The process <strong>for</strong> gathering the GCO in<strong>for</strong>mationshould simply be part <strong>of</strong> the overall data call during the pre-RFP activities. A GCO should bedistributed to the functional organizations along with the normal data call in<strong>for</strong>mation.Development <strong>of</strong> a GCO will help ensure that the Government receives the correct version and<strong>for</strong>mats <strong>of</strong> digital data needed to acquire and support a training program. A flow diagram <strong>of</strong> theentire process is shown in Figure 4. The suggested methodology to determine the data<strong>acquisition</strong> requirements as diagrammed in Figure 4 is contained in paragraph C.5.1. During theGCO development process, the following will be determined and documented:a. The hardware and s<strong>of</strong>tware systems the Government has, or is developing, to manage anduse the data.b. Data users, types <strong>of</strong> data, frequency <strong>of</strong> use, and timeliness <strong>of</strong> data access or delivery toeach user.c. Data use and the review and/or approval processes to support life cycle functions.d. Users' locations and their primary functions in support <strong>of</strong> the <strong>defense</strong> system.e. Data interchange requirements including <strong>for</strong>mat, media, applicable standards, andexisting telecommunications capabilities.71

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!