2.7 & 2.8 RFP Preparations Flashcards
EVM Reporting: >= $50M
All IPMDAR formats are mandatory, specifically:
- Monthly IPMDAR with all seven (7) formats
- Compliance with ANSI-EAI 748 EVM Systems
- Integrated Baseline Review (IBR) required
- If greater than $100M, formally validated and accepted, EVMS and routine surveillance by DCMA is performed
EVM Reporting: $50M>X>= $20M
Formats 1, 5, 6, and 7 are mandatory, specifically:
- Monthly IPMDAR with all tailored formats
- Compliance with ANSI-EAI 748 EVM Systems
- Integrated Baseline Review (IBR) required
Formats 2, 3, and 4 are optional
EVM Reporting: $20M>X
At discretion of Program/Project Manager (PM). Optional application.
Formats 1, 5, and 7 would be recommended, and in some cases Format 6 may also be recommended.
Two EV Techniques
Discrete: work is related to the completion of specific end products or services and can be directly planned, scheduled, and measured.
LOE work is of a general or supportive nature that does not produce definite end products
EVM Reports: Integrated Program Management Data Analysis Report (IPMDAR)
Provides cost and schedule performance information
Provides essential project data
- Objective performance status in terms of cost and schedule variances
- Cost impact of known problems
- Identification of emerging problems
- Possible sources of problems
- Schedule deviations from the contract plan
- Updated estimates at completion
EVM Reports: Contract Funds Status Report (CFSR)
provides snap shot of contract funding, expenditures, billings and termination liability
Capability Maturity Model Integration for Development (CCMI-DEV)
Provides a comprehensive integrated set of guidelines for developing products and services which organization is rated against
Range from levels 0-5
Rated on two categories
- Continuous Representation Capability Levels: apply to an organization’s process improvement achievement in individual process areas.
- Staged Representation Maturity Levels: apply to an organization’s process improvement achievement across multiple process areas.
Key Software Aquisition Best Practices
- Adopt Continuous Program Risk Management
- Estimate Cost and Schedule Empirically (cost and schedule estimates are high risk early due to limited info)
- Use Metrics to Manage
- Track Earned Value
- Track Defects against Quality Targets
- Treat People as the Most Important Resource
- Adopt Life Cycle Configuration Management
- Manage and Trace Requirements
9.Use System-Based Software Design - Ensure Data and Database Interoperability
- Define and Control Interfaces
- Design Twice, Code Once
- Assess Reuse Risks and Costs
- Inspect Requirements and Design
- Manage Testing as a Continuous Process
- Compile and Smoke Test Frequently
https://dau.csod.com/content/dau/publications/6573/Content/Projects/Res/library/ACQ2020_M2_L08_KeySoftwareBestPractices.pdf
Four DoD Architecture Framework Views
- All View
- Operational View
- Systems and Services View
- Technical Standards View
Four Data Categories
- Technical Data: Product data; Computer Software Documentation; Computer Data Bases
- Computer Software: programs, source code, algorithms
- Management Data: financial info; schedule; most cost
- Source Selection Data
Five Types fo Data Rights
Unlimited Rights: right to use, modify, reproduce, perform, display, release, or disclose technical data in any manner, and for any purpose whatsoever
Limited Rights: government may use the data within the government but not release the technical data outside of the government
Restricted Rights: government may only run the software on one computer at a time, may make only the minimum copies needed for backup, but may make modifications to the software. No release outside goverment
Government Purpose Rights: government and private funds are used in development effort; GPR expires after a time limit (the standard is five years); During the time government must limit the disclosure of the data outside of the government to government purposes
Specifically Negotiated License Rights: standard license arrangements are modified to the mutual agreement of the contractor and the government
https://dau.csod.com/content/dau/publications/6573/Content/Projects/Res/library/ACQ2020_M2_L08_DataSoftwareIPRights.pdf
Two standard DFARS clauses frequently used as part of the data management strategy
Deferred delivery: allows for the actual delivery of certain pre-determined CDRL items to be deferred until two years after the acceptance of all other items under the contract.
Deferred ordering: allows the government to order the delivery of any technical data or computer software generated under a contract until three years after the acceptance of all other items under the contract.
