+---+------------------------+-------+----------------------------------+
| # | **Stated Business      | **App | **Comments**                     |
| # | Requirement**          | roved |                                  |
|   |                        | Req   |                                  |
| \ |                        | uirem |                                  |
| # |                        | ent** |                                  |
+===+========================+=======+==================================+
| # |                        |       |                                  |
| # |                        |       |                                  |
| # |                        |       |                                  |
| # |                        |       |                                  |
| # |                        |       |                                  |
| # |                        |       |                                  |
| # |                        |       |                                  |
|   |                        |       |                                  |
+---+------------------------+-------+----------------------------------+
| 1 | The system shall       | Yes   | The Standard Accounting and      |
|   | provide cost reporting |       | Reporting System (STARS) system  |
|   | at least one level     |       | will be implemented with an      |
|   | below the existing     |       | Accounting Flexfield (AFF) that  |
|   | Budget and Reporting   |       | will include an organizational   |
|   | (B&R) structure.       |       | cost center component (Reporting |
|   |                        |       | Entity Segment), a segment       |
|   |                        |       | (Program Segment) that replaces  |
|   |                        |       | the current B&R, and two         |
|   |                        |       | segments below this level        |
|   |                        |       | (Project Segment and Work For    |
|   |                        |       | Others (WFO) Segment). This will |
|   |                        |       | allow costs to be captured at    |
|   |                        |       | levels below the current Budget  |
|   |                        |       | and Reporting (B&R) level.       |
+---+------------------------+-------+----------------------------------+
| 2 | The system shall       | Yes   | The functional requirement is    |
|   | provide cost element   | --    | met through the use of the       |
|   | level detail (e.g.     | with  | Object Class Segment of the AFF. |
|   | labor, materials,      | rev   | This segment is 5 characters in  |
|   | overhead) at the       | ision | length, with the first 3 being   |
|   | lowest level of the    |       | the standard OMB Object Class    |
|   | "B&R" structure.       |       | Code, and the last two available |
|   |                        |       | as a sub-object class to denote  |
|   |                        |       | the detailed cost element.       |
|   |                        |       | However, in discussions during   |
|   |                        |       | the Joint Requirements Design    |
|   |                        |       | Conference, cost element level   |
|   |                        |       | detail was not supported.        |
+---+------------------------+-------+----------------------------------+
| 3 | The system shall       | Yes   | The functional requirement is    |
|   | provide                | --    | met through the use of the       |
|   | **[stand               | with  | Object Class Segment of the AFF. |
|   | ardized]{.underline}** | rev   | The STARS Team has recommended   |
|   | cost element level     | ision | the use of standard codes as     |
|   | detail at the lowest   |       | part of the sub-object class     |
|   | level of the "B&R"     |       | code contained in the last two   |
|   | structure.             |       | characters of the Object Class   |
|   |                        |       | Code Segment of the AFF, and     |
|   |                        |       | thus, the system can fulfill     |
|   |                        |       | this requirement. However, in    |
|   |                        |       | discussions during the Joint     |
|   |                        |       | Requirements Design Conference,  |
|   |                        |       | cost element level detail was    |
|   |                        |       | not supported.                   |
+---+------------------------+-------+----------------------------------+
| 4 | The system shall be    | Yes   | Based on discussions with the    |
|   | capable of comparing   | --    | submitter, this requirement      |
|   | planned costs and      | th    | involves comparison against a    |
|   | obligations to actual  | rough | "spend" plan vs. actual costs.   |
|   | costs and obligations  | worka | For example, if an organization  |
|   | on a monthly basis.    | round | receives an approved annual      |
|   |                        |       | budget (funds control) amount at |
|   |                        |       | the Program Segment level for    |
|   |                        |       | \$12M, they may want to break    |
|   |                        |       | that "hard" funds control amount |
|   |                        |       | into twelve equal buckets. While |
|   |                        |       | the system will prevent them     |
|   |                        |       | from overspending the \$12M, as  |
|   |                        |       | currently configured, it will    |
|   |                        |       | not prevent them from spending   |
|   |                        |       | the entire \$12M in the first    |
|   |                        |       | month. The \$12M is referred to  |
|   |                        |       | as a "hard control", while the   |
|   |                        |       | monthly breakdown is referred to |
|   |                        |       | as a managerial control.         |
|   |                        |       |                                  |
|   |                        |       | Oracle Federal Financial         |
|   |                        |       | Applications includes a          |
|   |                        |       | separate, Federal Budgetary      |
|   |                        |       | entry, control, and reporting    |
|   |                        |       | capability. Budgetary journal    |
|   |                        |       | entries are segregated,          |
|   |                        |       | identified, and recorded         |
|   |                        |       | directly in the General Ledger   |
|   |                        |       | as "actual" journal entries,     |
|   |                        |       | with full U.S. SGL accounting.   |
|   |                        |       | This provides extensive          |
|   |                        |       | reporting of the budgeted vs.    |
|   |                        |       | committed vs. obligated vs.      |
|   |                        |       | costed vs. outlays, and the      |
|   |                        |       | variations of these categories.  |
|   |                        |       |                                  |
|   |                        |       | Standard Oracle Financial        |
|   |                        |       | Applications include a generic   |
|   |                        |       | budget capability as part of the |
|   |                        |       | General Ledger module, intended  |
|   |                        |       | for use by commercial            |
|   |                        |       | organizations. This capability   |
|   |                        |       | supports the concept of "planned |
|   |                        |       | vs. actuals" comparisons and     |
|   |                        |       | reporting similar to the         |
|   |                        |       | managerial controls described    |
|   |                        |       | above. With this approach,       |
|   |                        |       | separate general ledger          |
|   |                        |       | budgetary journal entries are    |
|   |                        |       | segregated, identified, and      |
|   |                        |       | recorded in the General Ledger   |
|   |                        |       | as "planned" journal entries.    |
|   |                        |       | While this functionality could   |
|   |                        |       | be used to fulfill this          |
|   |                        |       | requirement, the team believes   |
|   |                        |       | that it would lead to confusion  |
|   |                        |       | on the part of end-users who     |
|   |                        |       | would have to differentiate      |
|   |                        |       | between budgetary entries        |
|   |                        |       | entered as part of the Federal   |
|   |                        |       | Budgetary process, and budgetary |
|   |                        |       | entries entered through the      |
|   |                        |       | General Ledger budgetary         |
|   |                        |       | process. In addition, no one on  |
|   |                        |       | the team has experience with the |
|   |                        |       | use of this functionality on a   |
|   |                        |       | Federal project, and thus, there |
|   |                        |       | may be functional restrictions   |
|   |                        |       | within the system that we are    |
|   |                        |       | not aware of.                    |
|   |                        |       |                                  |
|   |                        |       | The team believes that there are |
|   |                        |       | a number of workarounds to       |
|   |                        |       | enable managerial controls,      |
|   |                        |       | including custom reporting or    |
|   |                        |       | data extracts using existing     |
|   |                        |       | reporting tools to download data |
|   |                        |       | to a user-controlled             |
|   |                        |       | spreadsheet. Another option      |
|   |                        |       | would be to use the data         |
|   |                        |       | warehouse as a repository for    |
|   |                        |       | this information, with built in  |
|   |                        |       | triggers to generate user        |
|   |                        |       | "alerts" when a managerial       |
|   |                        |       | control has been exceeded.       |
|   |                        |       |                                  |
|   |                        |       | Please bear in mind that in the  |
|   |                        |       | current environment, cost        |
|   |                        |       | reporting based on the           |
|   |                        |       | integrated contractor feed       |
|   |                        |       | occurs after the fact, and at a  |
|   |                        |       | summarized level.                |
|   |                        |       |                                  |
|   |                        |       | This was a request from a single |
|   |                        |       | organization and was not         |
|   |                        |       | generally supported as an        |
|   |                        |       | enterprise requirement.          |
+---+------------------------+-------+----------------------------------+
| 5 | The system shall       | Yes   | The department currently         |
|   | accumulate cost data   |       | utilizes Cost Center to further  |
|   | by cost center (cyber  |       | breakdown three elements;        |
|   | security/network       |       | organization, object class, or   |
|   | operations/help desk   |       | B&R. Our AFF allows for the use  |
|   | support, etc.).        |       | of all three cost center         |
|   |                        |       | definitions. In our              |
|   |                        |       | recommendation, we are using     |
|   |                        |       | cost center as a unique *[cost   |
|   |                        |       | gathering]{.underline}* entity   |
|   |                        |       | within the organizational        |
|   |                        |       | structure only                   |
+---+------------------------+-------+----------------------------------+
| 6 | The system shall       | Yes   | 1\. Cost element detail will be  |
|   | provide the capability |       | captured in the Object Class     |
|   | to budget at levels    |       | segment of the AFF.              |
|   | below the "B&R"        |       |                                  |
|   | structure (e.g. travel |       | 2\. The object class segment is  |
|   | for an organization).  |       | five digits in length. The first |
|   |                        |       | three characters are held for    |
|   |                        |       | the official Office of           |
|   |                        |       | Management and Budget (OMB)      |
|   |                        |       | object class code. The final two |
|   |                        |       | would be utilized as a           |
|   |                        |       | sub-object class in order to     |
|   |                        |       | denote the detailed cost element |
+---+------------------------+-------+----------------------------------+
| 7 | The system shall       | Yes   | 1\. The organizational element   |
|   | identify financial     |       | of cost will be captured in the  |
|   | data for organizations |       | reporting entity segment of the  |
|   | below the allottee.    |       | AFF.                             |
|   |                        |       |                                  |
|   |                        |       | 2\. The reporting entity segment |
|   |                        |       | is five digits in length         |
|   |                        |       | allowing for an extensive        |
|   |                        |       | hierarchy. The reporting entity  |
|   |                        |       | segment is dependent on the      |
|   |                        |       | allottee segment. Each allottee  |
|   |                        |       | will own a unique organizational |
|   |                        |       | hierarchy within the reporting   |
|   |                        |       | entity segment. This means that  |
|   |                        |       | each allottee value will have    |
|   |                        |       | one hundred thousand reporting   |
|   |                        |       | entity values available for use. |
|   |                        |       |                                  |
|   |                        |       | 3\. Within each allottee, a cost |
|   |                        |       | center hierarchy will be         |
|   |                        |       | developed to allow for costs to  |
|   |                        |       | be accumulated within specific   |
|   |                        |       | organizational "buckets". As an  |
|   |                        |       | example, the IT department       |
|   |                        |       | within the Albuquerque           |
|   |                        |       | operations office may further    |
|   |                        |       | breakdown their organization     |
|   |                        |       | with a helpdesk cost center,     |
|   |                        |       | network support cost center, PC  |
|   |                        |       | support cost center, and         |
|   |                        |       | database administration cost     |
|   |                        |       | center. These separate cost      |
|   |                        |       | centers will allow for the       |
|   |                        |       | management of costs related to   |
|   |                        |       | specific organizational          |
|   |                        |       | activities.                      |
+---+------------------------+-------+----------------------------------+
| 8 | The system shall       | Yes   | A separate fund type will be     |
|   | identify financial     | --    | created to handle Congressional  |
|   | data related to        | Co    | earmarks, similar to the         |
|   | Congressional          | vered | functionality used in the legacy |
|   | earmarks.              | in    | DISCAS system. Other earmarks    |
|   |                        | B     | embedded in the language of the  |
|   |                        | udget | appropriation bill will be       |
|   |                        | /     | handled in the Purchasing        |
|   |                        | P     | Module, providing a method to    |
|   |                        | erfor | identify, segregate, and report  |
|   |                        | mance | obligations and costs associated |
|   |                        | T     | with these earmarks.             |
|   |                        | eam's |                                  |
|   |                        | re    |                                  |
|   |                        | quire |                                  |
|   |                        | ments |                                  |
+---+------------------------+-------+----------------------------------+
| 9 | The system shall       | Yes   | This is standard functionality   |
|   | provide capability for |       | (Financial Statement Generator   |
|   | customizable           |       | (FSG) and Discoverer reports).   |
|   | reporting.             |       |                                  |
+---+------------------------+-------+----------------------------------+
| 1 | DOE field offices      | No    | This is a **policy issue**, not  |
| 0 | shall have on-line     |       | a STARS System requirement, and  |
|   | inquiry access to      |       | is not related to STARS System   |
|   | major operating        |       | functionality.                   |
|   | contractor's financial |       |                                  |
|   | data.                  |       |                                  |
+---+------------------------+-------+----------------------------------+
| 1 | Align the Department's | No    | This is a **policy issue**, not  |
| 1 | Work Breakdown         |       | a STARS System requirement. The  |
|   | Structure (WBS) with   |       | STARS System provides this       |
|   | the Department's       |       | capability.                      |
|   | Mission.               |       |                                  |
+---+------------------------+-------+----------------------------------+
| 1 | WBS should have only   | No    | This is a **policy issue**, not  |
| 2 | direct cost            |       | a STARS System requirement. The  |
|   | objectives.            |       | STARS System provides this       |
|   | (Safeguards and        |       | capability.                      |
|   | Security is an         |       |                                  |
|   | indirect function and  |       |                                  |
|   | should not be direct   |       |                                  |
|   | funded.)               |       |                                  |
+---+------------------------+-------+----------------------------------+
| 1 | The system shall be    | Yes   | As a general statement, the      |
| 3 | capable of reporting   | --    | system has the capability to     |
|   | "crosscut" data.       | par   | capture and report information   |
|   | (Note: current         | tial. | associated with cross-cuts.      |
|   | understanding of cross |       | However, in some cases, the      |
|   | cut requirements would | Co    | information is not currently     |
|   | indicate that this is  | vered | captured at the source (e.g. the |
|   | not possible in many   | in    | M&O contractor data feed), and   |
|   | cases.)                | the   | thus, is not available for the   |
|   |                        | B     | STARS system.                    |
|   |                        | udget |                                  |
|   |                        | /     |                                  |
|   |                        | P     |                                  |
|   |                        | erfor |                                  |
|   |                        | mance |                                  |
|   |                        | T     |                                  |
|   |                        | eam's |                                  |
|   |                        | req   |                                  |
|   |                        | uirem |                                  |
|   |                        | ents. |                                  |
+---+------------------------+-------+----------------------------------+
| 1 | The system shall be    | No    | This is a **policy issue**, not  |
| 4 | capable of reporting   |       | a STARS system requirement       |
|   | integrated contractor  |       | shortcoming. Strictly speaking,  |
|   | data no less           |       | the system is fully capable of   |
|   | frequently than        |       | receiving data feeds on          |
|   | weekly.                |       | practically any desired          |
|   |                        |       | frequency.                       |
|   |                        |       |                                  |
|   |                        |       | A full analysis of the impacts   |
|   |                        |       | associated with requiring more   |
|   |                        |       | frequent data from the major     |
|   |                        |       | operating contractors has not    |
|   |                        |       | been completed. Based on         |
|   |                        |       | previous discussions with the    |
|   |                        |       | Financial Management Systems     |
|   |                        |       | Improvement Council (FMSIC) of   |
|   |                        |       | the M&O contractor community,    |
|   |                        |       | the team believes that it would  |
|   |                        |       | be overly burdensome and costly. |
+---+------------------------+-------+----------------------------------+
| 1 | The system shall       | No    | This is a **policy issue**, not  |
| 5 | provide major          |       | a STARS system requirement       |
|   | operating contractor   |       | shortcoming. Strictly speaking,  |
|   | commitments for        |       | we are configuring the system to |
|   | travel, training,      |       | support this level of detail     |
|   | conferences, etc.      |       | using the last two characters of |
|   |                        |       | the OMB Object Class segment.    |
|   |                        |       |                                  |
|   |                        |       | This was a request from a single |
|   |                        |       | organization and was not         |
|   |                        |       | generally supported as an        |
|   |                        |       | enterprise requirement. The      |
|   |                        |       | group believes that the level of |
|   |                        |       | detail is lower than what is     |
|   |                        |       | appropriate for the Departmental |
|   |                        |       | system.                          |
+---+------------------------+-------+----------------------------------+
| 1 | The system shall       | No    | On a monthly basis, the proposed |
| 6 | provide for project    |       | design of the Data Warehouse /   |
|   | performance            |       | Performance Management data      |
|   | information (i.e.      |       | structure will provide for       |
|   | earned value) more     |       | capture or entry of *summarized* |
|   | timely than monthly.   |       | project performance data         |
|   |                        |       | (schedule and cost performance)  |
|   |                        |       | at the Program and / or Project  |
|   |                        |       | Segment level, including         |
|   |                        |       | summarized earned value          |
|   |                        |       | management information.          |
|   |                        |       |                                  |
|   |                        |       | However, this system will not    |
|   |                        |       | provide the project management   |
|   |                        |       | functionality necessary for      |
|   |                        |       | compliance with ANSI/EIA         |
|   |                        |       | Standard 748-98 (see section     |
|   |                        |       | 1.H.1, Section 300 of OMB        |
|   |                        |       | Circular A-11), as the scope of  |
|   |                        |       | the I-MANAGE Program does not    |
|   |                        |       | support a detailed project       |
|   |                        |       | management capability, or a      |
|   |                        |       | detailed work breakdown          |
|   |                        |       | structure integrated with an     |
|   |                        |       | organizational breakdown         |
|   |                        |       | structure.                       |
|   |                        |       |                                  |
|   |                        |       | Note: The Oracle e-Business      |
|   |                        |       | Suite has separate modules for   |
|   |                        |       | this purpose.                    |
+---+------------------------+-------+----------------------------------+
| 1 | The system shall be    | No    | This is a **policy issue**.      |
| 7 | capable of accounting  |       | Strictly speaking, the system is |
|   | for Program Direction  |       | fully capable of achieving this  |
|   | as a direct cost.      |       | objective.                       |
|   |                        |       |                                  |
|   |                        |       | However, the consensus was that  |
|   |                        |       | full cost (including program     |
|   |                        |       | direction) allocation entries    |
|   |                        |       | would be made for financial      |
|   |                        |       | statement reporting purposes at  |
|   |                        |       | the end of the third and fourth  |
|   |                        |       | quarters The indication received |
|   |                        |       | from our surveys and follow up   |
|   |                        |       | interviews did not indicate a    |
|   |                        |       | need for full cost reporting at  |
|   |                        |       | any level lower than the         |
|   |                        |       | financial statements.            |
+---+------------------------+-------+----------------------------------+
| 1 | The system shall be    | Yes   | Full cost (including program     |
| 8 | capable of accounting  |       | direction) entries would be made |
|   | for Program Direction  |       | for financial statement          |
|   | as an indirect cost.   |       | reporting purposes at the end of |
|   |                        |       | the third and fourth quarters    |
|   |                        |       | The indication received from our |
|   |                        |       | surveys and follow up interviews |
|   |                        |       | did not indicate a need for full |
|   |                        |       | cost reporting at any level      |
|   |                        |       | lower than the financial         |
|   |                        |       | statements                       |
+---+------------------------+-------+----------------------------------+
| 1 | No additional detail   | No    | This contradicts the requirement |
| 9 | below that received    |       | established in number 1 above.   |
|   | today is needed (no    |       |                                  |
|   | detail below the "B&R" |       |                                  |
|   | and no more            |       |                                  |
|   | frequently).           |       |                                  |
+---+------------------------+-------+----------------------------------+
| 2 | The system shall       | No    | This is a **policy issue**. The  |
| 0 | provide the ability to |       | frequency and level of detail    |
|   | accrue costs and labor |       | from the M&O contractor data     |
|   | hours for              |       | feed is currently under review.  |
|   | *                      |       | See number 14 above. Strictly    |
|   | *[prime]{.underline}** |       | speaking, the system is fully    |
|   | contractors on a       |       | capable of receiving data feeds  |
|   | weekly basis.          |       | on practically any desired       |
|   |                        |       | frequency.                       |
|   |                        |       |                                  |
|   |                        |       | This was a request from a single |
|   |                        |       | organization and was not         |
|   |                        |       | generally supported as an        |
|   |                        |       | enterprise requirement of the    |
|   |                        |       | Department-wide core financial   |
|   |                        |       | system.                          |
+---+------------------------+-------+----------------------------------+
| 2 | The system shall be    | Yes   | This will be addressed as a      |
| 1 | capable of being       | --    | technical requirement when the   |
|   | automatically          | tra   | appropriate interfaces are       |
|   | reconciled with the    | nsfer | developed, and all interfaces    |
|   | EC-Web and             | to    | require reconciliation           |
|   | e-procurement systems. | STARS | reporting. The team does not see |
|   |                        | D     | this impacting the requirements  |
|   |                        | evelo | for a cost accounting structure. |
|   |                        | pment |                                  |
|   |                        | Team  | Note: This requirement will be   |
|   |                        |       | impacted by the selection of the |
|   |                        |       | e-Procurement solution, which    |
|   |                        |       | should be considered during any  |
|   |                        |       | cost-benefit analysis.           |
+---+------------------------+-------+----------------------------------+
| 2 | The system shall be    | Yes   | This requirement will be covered |
| 2 | capable of identifying | --    | in the design for integration of |
|   | costs associated with  |       | budget and performance data.     |
|   | performance metrics.   | Co    |                                  |
|   |                        | vered |                                  |
|   |                        | in    |                                  |
|   |                        | the   |                                  |
|   |                        | B     |                                  |
|   |                        | udget |                                  |
|   |                        | /     |                                  |
|   |                        | P     |                                  |
|   |                        | erfor |                                  |
|   |                        | mance |                                  |
|   |                        | T     |                                  |
|   |                        | eam's |                                  |
|   |                        | Re    |                                  |
|   |                        | quire |                                  |
|   |                        | ments |                                  |
+---+------------------------+-------+----------------------------------+
| 2 | The system shall be    | Yes   | These costs can be captured      |
| 3 | capable of recording   |       | through the use of the Program,  |
|   | costs identifiable as  |       | Project, WFO or Local Use        |
|   | a separate work        |       | segment.                         |
|   | activity (project,     |       |                                  |
|   | reimbursable work, OMB |       |                                  |
|   | Exhibit 300,           |       |                                  |
|   | Congressional Earmark) |       |                                  |
+---+------------------------+-------+----------------------------------+
| 2 | The system shall be    | Yes   | Standard functionality           |
| 4 | capable of tracking    |       |                                  |
|   | all Federal obligating |       |                                  |
|   | documents.             |       |                                  |
+---+------------------------+-------+----------------------------------+
| 2 | The system shall be    | Yes   | State information can be         |
| 5 | capable of reporting   |       | captured in the AP module for    |
|   | costs by state.        |       | federal transactions. A method   |
|   |                        |       | for capturing the level of       |
|   |                        |       | detail from major operating      |
|   |                        |       | contractors is yet to be         |
|   |                        |       | determined.                      |
+---+------------------------+-------+----------------------------------+
| 2 | The system shall be    | Yes   | Standard functionality           |
| 6 | capable of reporting   |       |                                  |
|   | on reimbursable work   |       |                                  |
|   | performed at           |       |                                  |
|   | Headquarters. (May be  |       |                                  |
|   | an accounting policy   |       |                                  |
|   | issue)                 |       |                                  |
+---+------------------------+-------+----------------------------------+
| 2 | The system shall       | No    | The STARS system allows for only |
| 7 | provide the capability |       | one user determined control      |
|   | to have "hard"         |       | level. That level has been       |
|   | controls on funds at   |       | established at the Congressional |
|   | levels below the       |       | control level. Managerial        |
|   | Congressional Control  |       | controls (i.e. targeted          |
|   | Level.                 |       | reporting and alerts) will be    |
|   |                        |       | available to monitor other       |
|   |                        |       | levels.                          |
+---+------------------------+-------+----------------------------------+
| 2 | The system shall       | No    | This was a request from a single |
| 8 | provide the capability |       | organization and was not         |
|   | to upload from program |       | generally supported as an        |
|   | financial systems.     |       | enterprise requirement.          |
|   |                        |       |                                  |
|   |                        |       | A set of common, enterprise      |
|   |                        |       | interfaces are to be developed   |
|   |                        |       | by the STARS Project Team. In    |
|   |                        |       | addition, Oracle's Application   |
|   |                        |       | Desktop Integrator provides      |
|   |                        |       | standard spreadsheet interface   |
|   |                        |       | capability for specified         |
|   |                        |       | activities (e.g. journal         |
|   |                        |       | entries, reports,                |
|   |                        |       | multi-dimensional analysis       |
|   |                        |       | through the Oracle Journal       |
|   |                        |       | Interface).                      |
|   |                        |       |                                  |
|   |                        |       | However, one of the key          |
|   |                        |       | objectives of the I-MANAGE       |
|   |                        |       | program is to reduce or          |
|   |                        |       | eliminate redundant systems.     |
|   |                        |       | Where STARS, as *an enterprise   |
|   |                        |       | system*, can replace program     |
|   |                        |       | system functionality, interfaces |
|   |                        |       | will not be provided.            |
+---+------------------------+-------+----------------------------------+
| 2 | The system shall       | No    | This is a **policy issue**. One  |
| 9 | provide the capability |       | of the key objectives of the     |
|   | of downloading to      |       | I-MANAGE program is to reduce or |
|   | program financial      |       | eliminate redundant systems.     |
|   | systems.               |       |                                  |
|   |                        |       | Having said this, the system     |
|   |                        |       | will provide the capability to   |
|   |                        |       | download cost data in a standard |
|   |                        |       | format that can then be imported |
|   |                        |       | into other ancillary systems     |
|   |                        |       | with import capability.          |
+---+------------------------+-------+----------------------------------+
| 3 | The system shall       | Yes   | This is standard functionality   |
| 0 | provide the capability |       | (Oracle application). However,   |
|   | to transfer funds      |       | this is a **policy issue**, and  |
|   | between allottees on   |       | should be analyzed to verify the |
|   | an as needed basis.    |       | intent of the process.           |
+---+------------------------+-------+----------------------------------+
| 3 | The system shall       | No    | Data capture within the          |
| 1 | provide the capability |       | applications is defined by the   |
|   | to collect data on an  |       | specific business requirements   |
|   | ad hoc basis.          |       | of each module, and governed by  |
|   |                        |       | validation routines to ensure    |
|   |                        |       | data integrity. Authorized users |
|   |                        |       | may configure generic fields     |
|   |                        |       | (e.g. descriptive flexfields) to |
|   |                        |       | capture information not defined  |
|   |                        |       | within the standard              |
|   |                        |       | functionality, but the system is |
|   |                        |       | not a free-form data dump or     |
|   |                        |       | document storage system. This    |
|   |                        |       | was not identified as a system   |
|   |                        |       | wide need                        |
+---+------------------------+-------+----------------------------------+
| 3 | The system shall track | No -- | This should be handled as part   |
| 2 | financial data back to | tra   | of the I-MANAGE Standard Budget  |
|   | language in the budget | nsfer | System requirements, but is      |
|   | request.               | to    | quite feasible assuming the      |
|   |                        | Sta   | language in the budget request   |
|   |                        | ndard | is tied to specific, common data |
|   |                        | B     | elements shared between the two  |
|   |                        | udget | systems.                         |
|   |                        | S     |                                  |
|   |                        | ystem |                                  |
|   |                        | Re    |                                  |
|   |                        | quire |                                  |
|   |                        | ments |                                  |
+---+------------------------+-------+----------------------------------+
| 3 | The system shall       | No    | This is a **policy issue**. The  |
| 3 | provide the ability to |       | system has the capability to     |
|   | identify and report    |       | fulfill this requirement if data |
|   | direct funded project  |       | received from the M&O contractor |
|   | costs and lab directed |       | community properly segregates    |
|   | research and           |       | and identifies the data          |
|   | development (LDRD)     |       | accordingly. As a general        |
|   | costs without          |       | statement, the system will not   |
|   | "double-counting".     |       | allow double counting assuming   |
|   |                        |       | that the contractors submit a    |
|   |                        |       | balanced transaction file.       |
+---+------------------------+-------+----------------------------------+
| 3 | The system shall       | No    | Does not appear to be a          |
| 4 | enforce consistent use |       | departmental requirement. This   |
|   | of the "Local Use"     |       | contradicts a request by DOE     |
|   | segment, and not allow |       | personnel to allow flexibility   |
|   | individual sites to    |       | in the use of this segment. See  |
|   | utilize the segment in |       | number 42.                       |
|   | a non-standardized     |       |                                  |
|   | way.                   |       |                                  |
+---+------------------------+-------+----------------------------------+
| 3 | The system shall       | Yes - | The system will accomplish this  |
| 5 | provide the ability to | re    | using the Program and Project    |
|   | record and report data | vised | segments in conjunction with the |
|   | by standard cost       |       | last two characters of the       |
|   | element within Project |       | Object Classification segment.   |
|   | ID, where the cost     |       | However, this is a **policy      |
|   | element (element of    |       | issue** in that the level of     |
|   | expense) structure     |       | detail currently received from   |
|   | includes both          |       | the integrated contractors does  |
|   | resources and          |       | not consistently provide this    |
|   | activities.            |       | data.                            |
|   |                        |       |                                  |
|   |                        |       | Note: The wording of this        |
|   |                        |       | requirement was modified based   |
|   |                        |       | on a conversation with the       |
|   |                        |       | submitter.                       |
+---+------------------------+-------+----------------------------------+
| 3 | The system shall       | Yes   | Assuming that the cost center is |
| 6 | provide the ability to | --    | defined in the Reporting Entity  |
|   | define cost centers at | with  | segment of the Accounting        |
|   | a level where a        | qua   | Flexfield, this would be         |
|   | function can be        | lific | provided by standard system      |
|   | discriminated between  | ation | functionality.                   |
|   | other functions.       |       |                                  |
+---+------------------------+-------+----------------------------------+
| 3 | The system shall       | No    | This is a **policy issue**, not  |
| 7 | provide the ability to |       | a system restriction.            |
|   | report costs at level  |       |                                  |
|   | 3 of the WBS.          |       | There is no standard definition  |
|   |                        |       | of WBS within the Department,    |
|   |                        |       | therefore, there is no way to    |
|   |                        |       | identify and segregate costs as  |
|   |                        |       | "level 3". Four separate         |
|   |                        |       | segments have been defined in    |
|   |                        |       | the Accounting Flexfield to      |
|   |                        |       | provide tracking of a WBS,       |
|   |                        |       | including the Program Segment,   |
|   |                        |       | Project Segment, WFO Segment,    |
|   |                        |       | and Local Use Segment. Summary   |
|   |                        |       | or detailed reporting is         |
|   |                        |       | available on individual segment  |
|   |                        |       | levels, or combinations of       |
|   |                        |       | segment levels.                  |
+---+------------------------+-------+----------------------------------+
| 3 | The system must        | Yes   | As a general statement, the      |
| 8 | accumulate actual      |       | current legacy systems, and the  |
|   | contractor costs.      |       | new STARS System do this.        |
+---+------------------------+-------+----------------------------------+
| 3 | The system shall allow | Yes   | This requirement was covered in  |
| 9 | entry of a time-phased | --    | detail in item number 4 above.   |
|   | budget into the        | th    |                                  |
|   | general ledger         | rough |                                  |
|   | budgeting.             | worka |                                  |
|   |                        | round |                                  |
+---+------------------------+-------+----------------------------------+
| 4 | The system shall       | Yes   | Assuming the project identifier  |
| 0 | provide the ability to |       | is entered as a discrete value   |
|   | capture data by the    |       | in the Project Segment of the    |
|   | project identifier.    |       | Accounting Flexfield, this would |
|   |                        |       | be standard functionality.       |
+---+------------------------+-------+----------------------------------+
| 4 | The system shall be    | Yes   | This is a **policy issue**, not  |
| 1 | configured in a manner | --    | a system requirement. This       |
|   | that allows field      | with  | request was generated in         |
|   | offices to define and  | qual  | discussion during the Joint      |
|   | control their own      | ifica | Requirements Development         |
|   | values in the "Local   | tions | Conference, and in general, the  |
|   | Use" segment of the    |       | system can be configured to      |
|   | accounting flex-field. |       | achieve this goal.               |
+---+------------------------+-------+----------------------------------+
| 4 | The "Local Use"        | Yes   | This is a **policy issue**, not  |
| 2 | accounting flex-field  | --    | a system requirement. This       |
|   | segment values should  | with  | request was generated in         |
|   | be classified into     | qual  | discussion during the Joint      |
|   | ranges and assigned to | ifica | Requirements Development         |
|   | specific               | tions | Conference, and in general, the  |
|   | organizational         |       | system can be configured to      |
|   | entities by range.     |       | achieve this goal.               |
+---+------------------------+-------+----------------------------------+
| 4 | The M&O Contractors    | No    | This is a **policy issue.**      |
| 3 | shall be required to   |       |                                  |
|   | modify their systems   |       | A memo has been distributed to   |
|   | to align with the new  |       | the M&O FMSIC group requesting   |
|   | data format of the     |       | more information (i.e. level of  |
|   | Program Segment of the |       | effort, duration, costs) on the  |
|   | accounting flex-field. |       | feasibility of this request.     |
+---+------------------------+-------+----------------------------------+
| 4 | The system shall       | No    | A great deal of effort has been  |
| 4 | provide the ability to |       | expended in analyzing the full   |
|   | identify work for      |       | spectrum or reimbursable work.   |
|   | others that is started |       | As a general statement, this is  |
|   | by one organization,   |       | not a cost accounting            |
|   | performed by another   |       | requirement, and currently, the  |
|   | and paid for by a      |       | STARS Project Team is exploring  |
|   | third.                 |       | ways to fulfill this             |
|   |                        |       | requirement, or re-engineer      |
|   | -                      |       | business processes to alleviate  |
|   |                        |       | the need for this activity.      |
+---+------------------------+-------+----------------------------------+
| 4 | The system shall       | Yes   | State information can be         |
| 5 | provide the ability to |       | captured in the AP module for    |
|   | record and report the  |       | federal transactions. A method   |
|   | location where goods   |       | for capturing the level of       |
|   | will be used, services |       | detail from major operating      |
|   | performed, or dollars  |       | contractors is yet to be         |
|   | spent.                 |       | determined.                      |
+---+------------------------+-------+----------------------------------+
| 4 | The system shall       | No    | This request was submitted by a  |
| 6 | provide the ability to |       | single organization as part of   |
|   | record and report      |       | the followon comments to the     |
|   | individual transaction |       | Joint Requirements Development   |
|   | costs for multiple     |       | Conference. This activity is     |
|   | locations / zip codes  |       | partially met through the        |
|   | and allow an           |       | functionality described in       |
|   | allocation by          |       | number 45 above.                 |
|   | percentage that would  |       |                                  |
|   | be manually entered    |       |                                  |
|   | and total to 100%.     |       |                                  |
+---+------------------------+-------+----------------------------------+