Issues with the Draft FY2008 Exh. 300

-   What criteria will OMB use to evaluate the Exh. 300 submissions?
    Will there be 3 separate sets of criteria since Parts II, III, and
    IV are mutually exclusive? How will these criteria compare to the
    criteria used in the past?

-   Who or what criteria determine the classification for mixed
    lifecycle investments (i.e., investments that are some combination
    of development, maintenance, and/or eGov/LOB?) Note: mixed lifecycle
    investments are explicitly listed as a type of investment in
    question 6 on page 1.

-   Are all development/acquisition (i.e., Part II) investments expected
    to use EVM and be ANSI-748 compliant? What if the
    Department's/agency's EVM policy does not require these investments
    to be using EVM or be ANSI-748 compliant?

-   To what degree does the mix of contractor and government resources
    used on a project influence whether 1) an EVM clause is required as
    a clause in the contract or 2) the contractor's cost systems are
    required to be ANSI-748 complaint? If it does not influence it at
    all, why is the question in the Exh. 300?

-   What does "agency" mean? Does it mean CFO Act-level agency (i.e.,
    Department or independent agency) as is implied on page 1, question
    2 of the draft Exh. 300? Or does it mean a component of a Department
    as is stated on page 10, comment c?

-   Why does Table 1 of the Performance Information section on page 6
    need to be included? Doesn't Table 2 cover the same information?

-   The Sec. C, question 8 (on page 13) is "Is the department requesting
    a change in the performance baseline?" What performance baseline is
    this question referring to?

-   On pages 14, 16, and 20 in each of the milestone tables, the table
    as setup appears to assume that the milestones are in both the
    initial baseline and the current baseline. In fact, milestones in an
    initial baseline may not be in current baseline, and milestones in
    current baseline may not have been in initial baseline. Yet fields
    are shown as required in each.

Errors and Issues in the Draft FY 2008 XML Schema

**(Relative to the draft Exh. 300 form dated 4/6/06)**

Below are various errors that we found when examining the XML schema
file (OMB300v3.0.0.xsd) for the new Exh. 300

.

Many instances of data elements that are not logically dependent or
independent:

![](media/image1.png){width="5.5569444444444445in" height="4.0375in"}

![](media/image2.png){width="5.5569444444444445in"
height="4.029861111111111in"}

![](media/image3.png){width="5.802083333333333in"
height="4.215972222222222in"}

This is a compound question with a single answer:

![](media/image4.png){width="5.802083333333333in"
height="4.215972222222222in"}

The year date format adds a comma:

![](media/image5.png){width="5.5569444444444445in" height="4.0375in"}

FEA SRM selection items are not included:

![](media/image6.png){width="5.300694444444445in" height="3.84375in"}

Section E: Security and Privacy, question 8 is out of order because it
is embedded in the same XML hierarchy set as questions 3 and 4.

![](media/image7.png){width="5.684722222222222in"
height="4.1305555555555555in"}

The SPI and CPI figures should be numbers and not just integers:

![](media/image8.png){width="5.5569444444444445in" height="4.0375in"}

UPIs are required to be in old 23 digit format and not the revised 17
digit format:

![](media/image9.png){width="5.5569444444444445in"
height="4.159722222222222in"}

![](media/image10.png){width="5.5569444444444445in"
height="4.159722222222222in"}

![](media/image11.png){width="5.684722222222222in"
height="4.2555555555555555in"}

# Budget data cannot be in decimal+3-digit format even though the Exh. 53 allows it. 

![](media/image12.png){width="5.5569444444444445in"
height="4.167361111111111in"}**\
**

Sec. E, Question 6a calls for multiple answers, but schema only calls
for a dollar value:

![](media/image13.png){width="5.5569444444444445in"
height="4.167361111111111in"}

# Shouldn't the project manager's name be a required data element?

![](media/image14.png){width="5.802083333333333in"
height="4.204166666666667in"}

# Shouldn't the privacy POC's name be a required data element (and not just their phone number)?

![](media/image14.png){width="6.0159722222222225in"
height="4.366666666666666in"}