IRM_Requirements_20161213.xlsx
XLSX spreadsheet 20 KB Posted
- Attached to
- GFEBS Increment II - RFI
- Solicitation number
- W52P1J-17-R-INC2
About this file
IRM Requirements
View the file
Other files
| File | Type | Posted |
|---|---|---|
| INC_II_QA_20161219.pdf | ||
| RFI_Matrix_20161212.xlsx | XLSX spreadsheet | |
| IRM_Problem_Statement_(Redacted)_20161213.docx | DOCX document | |
| DoDI_5000.02.pdf | ||
| Risk_Reduction_Ph_Diagram_20161213.pptx | PPTX presentation | |
| GFEBS_Portfolio_Task_Descriptions_20161213.docx | DOCX document | |
| Increment_Development_Schedule_20161213.pdf | ||
| GFEBS_Portfolio_RFI_20161213.docx | DOCX document | |
| Draft__EFI_Problem_Statement_(Redacted)_20161213.docx | DOCX document | |
| SLTT_Requirements_20161213.xlsx | XLSX spreadsheet | |
| SLTT_Problem_Statement_(Redacted)_20161213.docx | DOCX document | |
| EFI_Capability_Description_Sample_20161213.docx | DOCX document |
Show all 12
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Requirements
| Notes | Relationship | Requirement | Component Capability | Sub Component Capability |
| BEP-1 | The system should provide automated functionality to maintain budget and spend plan information | Budget Execution Planning (BEP) | ||
| BEP-1.01 | To add value to the Budget Planning process, the Core financial system should provide automated functionality to compare planned spending to actual spending. | Budget Execution Planning | Monitor Execution | |
| BEP-1.02 | To support the Funds Control/Funds Availability Editing activity, the Core financial system must provide automated functionality to monitor the use of funds against financial operating and spending plans. | Budget Execution Planning | Monitor Execution | |
| BEP-1.03 | To add value to the Funds Distribution process, the Core financial system should provide automated functionality to update allotments, sub-allotments, allocations and legal and administrative limitations based on changes to operating plans. | Budget Execution Planning | Monitor Execution | |
| BEP-1.04 | To add value to the Budget Planning process, the Core financial system should provide automated functionality to maintain financial operating and spending plans for future periods (i.e., future fiscal years). | Budget Execution Planning | Manage Spend Plans | |
| BEP-1.05 | To add value to the Budget Planning process, the Core financial system should provide automated functionality to maintain current and multiple historical versions of plans. | Budget Execution Planning | Manage Spend Plans | |
| BEP-1.06 | To support the Budget Planning process, the Core financial system must provide automated functionality to export financial operating and spending plan data at the accounting line item level in an Excel or American Standard Code for Information Interchange (ASCII) text delimited file format. | Budget Execution Planning | Manage Spend Plans | |
| BEP-1.07 | To support the Funds Control/Funds Availability Editing activity, the Core financial system must provide automated functionality to maintain open documents to show the status of commitments, obligations, advances, accruals and disbursements by document (commodity) line item. | Budget Execution Planning | Monitor Execution | |
| CC-1 | The system must meet the technical reporting requirements of the user community | Cross-cutting (CC) | ||
| CC-1.01 | The system must enable the use of a single, standard operating procedures for planning and reporting on transactions. | Cross-cutting | Standard Reporting | |
| CC-1.01.01 | Must provide the ability to export the data/reports into printable formats and MS Office applications (Excel, Word, etc.). | Cross-cutting | System Configuration Requirement | |
| CC-2 | The system must enable specific technical features to meet the planning needs of the Army | Cross-cutting | ||
| CC-2.01 | Must provide a Global change capability (batch change capability). Ability to make mass changes to TDA(s) or PBG (AMSCO roll, LIN change, MOS change, etc.). | Cross-cutting | Manage TDAs | |
| CC-2.02 | Must provide a Help screen. | Cross-cutting | System Configuration Requirement | |
| CC-2.03 | Must provide drop down menu capability. | Cross-cutting | System Configuration Requirement | |
| CC-X | Must have ability to capture legacy LOA and capture in terms of enduring LOA | Cross-cutting | ||
| HT-1 | The system must consolidate legacy and enduring system data into a single repository. | Historical Transactions (HT) | Historical Transactions | |
| New 102 | HT-1.01 | Must provide interface with legacy accounting systems for historical transactions until legacy system retirement. | Historical Transactions | Produce Budget Guidance |
| MBP-1 | The system must enable command and Army-wide program planning and reporting from a single solution. | MACOM Budget Prep (MBP) | Define & Justify Command-wide Budget Requirements | |
| MBP-1.02 | To add value to the Budget Planning process, the Core financial system should provide automated functionality to activate future period plans based on a specified plan start date or on-demand. | MACOM Budget Prep | Define & Justify Command-wide Budget Requirements | |
| MBP-1.03 | To add value to the Budget Preparation process, the Core financial system should provide automated functionality to import budget formulation data (e.g., Presidential/Office of Management and Budget (OMB) pass backs, congressional markup documents, and internal agency decisions). | MACOM Budget Prep | Produce Budget Guidance | |
| MBP-1.04 | To add value to the Budget Planning process, the Core financial system should provide automated functionality to generate plan results based on multiple measures including fixed dollar amounts, unit costs, cost allocations, labor hours or full-time equivalents (FTEs). | MACOM Budget Prep | Define & Justify Command-wide Budget Requirements | |
| New 136 | MBP-1.05 | Must provide edit capability that validates data elements for PBG and POM submissions. | MACOM Budget Prep | Produce Budget Guidance |
| MBP-2 | The system must have the ability to receive and distribute PBG | MACOM Budget Prep | ||
| MBP-2.01 | Ability to distribute PBG to subordinate commands. Ability to revise the PBG and/or add command guidance prior to distribution of the PBG to ?level 3? organizations. | MACOM Budget Prep | Produce Budget Guidance | |
| MBP-2.01.01 | Allow users to select desired PBG Cycle when creating reports. | MACOM Budget Prep | Define & Justify Command-wide Budget Requirements | |
| MBP-2.01.02 | Must allow the user to Import a set of PBG adjustments from an Excel spreadsheet | MACOM Budget Prep | Produce Budget Guidance | |
| MBP-2.02 | To add value to the Budget Preparation process, the Core financial system should provide automated functionality to import budget submission guidance, other narrative text and briefing material written using common PC desktop applications (e.g., MS Word). | MACOM Budget Prep | Generate Schedules and Exhibits | |
| MBP-3 | Produce and submit the command Program Objective Memorandum (POM) requirements in standard format | MACOM Budget Prep | Define & Justify Command-wide Budget Requirements | |
| MBP-3.01 | To add value to the Budget Preparation process, the Core financial system should provide automated functionality to calculate prior year budgets, actual spending amounts and variances at the line item level. | MACOM Budget Prep | Define & Justify Command-wide Budget Requirements | |
| MBP-3.01.01 | To add value to the Budget Preparation process, the Core financial system should provide automated functionality to export prior year budgets, actual spending and variances at the line item level in an excel or ASCII text delimited file format. | MACOM Budget Prep | Generate Schedules and Exhibits | |
| MBP-3.02 | To add value to the Budget Preparation process, the Core financial system should provide automated functionality to generate multiple budgets based on alternative agency-specified accounting structures, funding levels, and spending criteria. | MACOM Budget Prep | Generate Schedules and Exhibits | |
| CC | MBP-3.02.01 | Must provide ability to Download DA Program Budget Guidance from Probe Database with ability to compare up to 4 multiple posted positions (funding, validated, requested, and critical requirements; manpower requirements; funding ?BIN?, dollar, manpower, and requirement audit trails). Report capability that highlights funding changes at the summary or detail level for each POM file issued during the POM Cycle by MDEP, APPN, and BIN Sub-Category | MACOM Budget Prep | Analyze Manpower Requirements and End Strength |
| Update | MBP-3.02.02 | Must provide capability to download PBG historical file positions (start, lock, audit trails, APPN File, Base File, POM File, BESPOM File) based on Resource Organization Codes (ROCs) available in DFAS Manual 37-100. | MACOM Budget Prep | Collect and Submit Schedule 8 |
| MBP-3.03 | To add value to the Budget Preparation process, the Core financial system should provide automated functionality to classify budget projections using accounting classification elements (e.g., Apportionment categories, Authority type, etc.). | MACOM Budget Prep | Define & Justify Command-wide Budget Requirements | |
| MBP-3.04 | To add value to the Budget Preparation process, the Core financial system should provide automated functionality to generate budget information for multiple budget cycles (e.g. monthly, quarterly, semi-annual, and yearly). | MACOM Budget Prep | Generate Schedules and Exhibits |
Sheet5
| 137 | PMM Manning/Reporting | PMM-2.1.1 | Added by IMCOM: Must provide turnover rate by occupational series for specified period of time; required for CEP. | Application | Program Manning/Manpower Planning | Analyze Manpower Requirements and End Strength | |
| 93 | Update to manning | PMM-3.1.16 | Must allow a user to designate a person as part time by indicating they use up only part of an AUTH (.1,.5,etc) (requires HQDA decision) | Application | Program Manning/Manpower Planning | Manage TDAs | |
| 98 | x manning | PMM-3.1.18 | Must allow user to add a personnel record, edit a personnel record, or delete a personnel record. User must also be able to protect specified fields, so they are not overwritten by daily DCPDS and TAPDB updates. When manpower authorizations are moved between paragraphs/lines within TDA Section II, personnel should move automatically/correspondingly within Manning document. | Application | Program Manning/Manpower Planning | Manage TDAs | |
| 15 | Manning | PMM-3.2.2 | Must provide capability to interface/reconcile with DCPS. | Application | Program Manning/Manpower Planning | Manage TDAs | |
| 95 | ? | Manning | PMM-3.4.2 | added by ATEC: Provide means to update DCPDS and DCPS to correct APC/AMSCO/Parno/Line | Application | Program Manning/Manpower Planning | Manage TDAs |
| 131 | Compare | PMM-5.2.2 | Added by USARC: Reserve Command uses TDA UIC + TPU UIC and RGN codes in Manning Document to facilitate Full-Time Support (FTS) management, allocation, end strength reports. Must have continued ability to manage and report at this level. | Application | Program Manning/Manpower Planning | Analyze Manpower Requirements and End Strength |
Stats
| # of Requirements by component capability |
| Mandatory vs. value added |
Observations
| MACOM Budget Prep Reporting requirements |
| Schedules submitted |
Relationship Legend
| Relationship Schema | |||
| Component Capabilities | Acronym | Requirement Type | # Schema |
| Budget Execution Planning | BEP | Business | x |
| Historical Transactions | HT | Functional | x.x |
| MACOM Budget Preparation | MBP | Application | x.x.x |
| Program Manning/Manpower Planning | PMM | Technical | x.x.x.x |
Sub Component Capabailties
| Sub-component Capabilities | Sub-component Capabilities aligned to Component Capabilities |
| Monitor Execution | Budget Execution Planning |
| Historical Transactions | Monitor Execution |
| Define & Justify Command-wide Budget Requirements | Manage Spend Plan |
| Produce Budget Guidance | Historical Transactions |
| Generate Schedules and Exhibits | Historical Transactions |
| Affordability Analysis | MACOM Budget Preparation |
| Analyze Manpower Requirements and End Strength | Define & Justify Command-wide Budget Requirements |
| Collect and Submit Schedule 8 | Produce Budget Guidance |
| Create and Manage Manning Documents | Generate Schedules and Exhibits |
| Manage TDAs | Program Manning/Manpower Planning |
| System Configuration Requirement | Affordability Analysis |
| Standard Reporting | Analyze Manpower Requirements and End Strength |
| Collect and Submit Schedule 8 | |
| Create and Manage Manning Documents | |
| Manage TDAs | |
| Cross Cutting | |
| System Configuration Requirement | |
| Standard Reporting |
File details come from the government source that posted it. Updated .