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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

MIL-HDBK-29612-1AFIGURE 5. GCO Example - Continued.2.3 Implementation planning. Key to the success <strong>of</strong> the SDD implementation ef<strong>for</strong>t is thedevelopment and implementation <strong>of</strong> programs and plans to support the seamless transfer <strong>of</strong> systemsand configuration management responsibility to the program manager and supporting activities. It isincumbent upon each XYZ training program manager to conduct SDD implementationplanning not only to support the goals and objectives <strong>of</strong> their individual programs, but also tosupport the goals, objectives and concept <strong>of</strong> operations set <strong>for</strong>th in this GCO and other projectplans. Program managers will also consider coordinating their IDE ef<strong>for</strong>ts with any on-goingcontractor ef<strong>for</strong>ts.2.4 Contractor IDE planning. The XYZ program contractors have an important role in planningand execution <strong>of</strong> the IDE. The XYZ training program will require each <strong>of</strong>feror to provide both acontractor’s approach to SDD and either a SDD Implementation Plan (SDDIP) or similar plan (e.g., anIDE Implementation Plan, Program Data Integration Plan, etc.). These documents are used to describethe contractor’s approach to SDD and their plan to implement SDD in accordance with this GCO.2.4.1 Contractor’s approach to SDD. The contractor’s approach to SDD is included in responseto the RFP, and describes the contractor's approach, experiences, and successes in the creation,management, use, and exchange <strong>of</strong> digital in<strong>for</strong>mation. In<strong>for</strong>mation in the contractor’s approach isused to gauge the risk associated with the contractor's ability to provide the digital data products andservices required by the RFP. After contract award, the contractor’s approach should be used as thebasis <strong>for</strong> subsequent planning documents. As a minimum, the contractor’s approach to SDD shouldinclude:a. The contractor's approach and experiences in the management, use, and exchange <strong>of</strong>digital in<strong>for</strong>mation. This description should include, at a minimum, a discussionconcerning the delivery <strong>of</strong> digital data.b. SDD program management, including program objectives and strategy, programmanagement responsibilities, and program management approach.c. In<strong>for</strong>mation system description, including source and destination systems, and relationshipwith Government receiving systems as depicted in the SDD GCO.d. Data protection and integrity, including risk assessment and system security certification.2.4.2 SDD implementation plan. The SDDIP should address capabilities <strong>for</strong> automating theaccess and retrieval <strong>of</strong> technical data, and provide <strong>for</strong> digital exchange and integration between andamong contractor and Government functional areas. The SDDIP should not be a static document, butshould be revised to reflect the reality <strong>of</strong> changing XYZ training program requirements, technology,and improved processes. Program managers may choose to develop CDRL, CLIN, or exhibit languagethat identifies each deliverable and the delivery method(s). The program manager may also choose toaccept alternative approaches to identifying and providing data deliverables that do not require therigidity <strong>of</strong> the <strong>for</strong>mal CDRL process.81

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

Saved successfully!

Ooh no, something went wrong!