Attch_0005_Requirements_Traceability_Matrix(RTM)_2015_11_04.xlsx
XLSX spreadsheet 608 KB Posted
- Attached to
- ACWS
- Solicitation number
- W52P1J-16-R-0058
About this file
Attachment 0005
View the file
Other files
Show all 32
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
Cover Page
TAB Index
| Attachment 004 | &"-,Bold"ACWS |
| Requirements Traceability Matrix | &"-,Bold"4 November 2015 |
RFP# W52P1J-16-R-0058
Traceability Index
| Level | Traceability Hierarchy Short Title | Traceability Hierarchy Description |
| 0 | DoD Objectives | The Department of Defense (DoD) Objectives identify business objectives that the Army must implement |
| 1 | ACWS High Level Objectives | The ACWS High Level Objectives documented in Problem Statement |
| 2 | ACWS Business Outcomes | The ACWS Business Outcomes are the expected result of implementing an ACWS HLO and are traced to these HLOs. |
| 3 | Basic Capability Requirements | The Basic Capability Requirements describe the business needs of the Army Contracting Enterprise required to achieve a business outcome and are traced to these business outcomes. Measurements with threshold and objective values. |
| 4 | Detailed Capability Requirements | The Detailed Capability Requirements describe more specific capabilities required to execute the high-level capabilities and trace to a specific high-level capability requirement. Maps to Level One Business Process Models. |
| 5 | ACWS System Requirements | The ACWS ACWS System Requirements describe the system functionality and technical requirements needed to realize the detailed capability requirement. These are traced to detailed capability requirements by virtue of their unique identifier (e.g. PP-ASN-1-1). |
| n/a | Level 1 Business Processes | The Level 1 Business Processes describe the business processes used to perform the end-to-end procurement function in order to achieve desired business outcomes. These are traced to ACWS Business Outcomes. |
| n/a | Level Two Business Processes | The Level Two Business Processes describe the business processes used to perform the end-to-end procurement function in order to achieve desired business outcomes. These are traced to ACWS Business Outcomes. |
| n/a | ACWS Actors (Army Contracting User Roles) | The ACWS Actors define the various user roles anticipated in the ACWS solution as well as the individuals who accomplish the tasks defined in the Army Contracting Enterprise Business Process. |
| n/a | ACWS Terminology and Definitions | The ACWS Terminology and Definitions worsheet defines the various terms used within the Requirements Tracability Matrix in mannor consistant with the overarching ACWS program. |
ACWS Requirements Traceability Matrix 4 November 2015
RFP# W52P1J-16-R-0058
ATTACHMENT 0004
&A &P of &N
Level 0-DoD Objectives
| DoD-ID | DoD Objective Short Title | DoD Objective Description |
| DoDOBJ-1 | Future Contract Writing System | An integrated architectural environment will enable the acquisition of systems, research, goods, and services for Soldiers both in garrison and in deployed environments. (DoD Strategic Plan v2.0, September 2014) |
| DoDOBJ-2 | Contract Administration | Improve Contract Administration and increased visibility and oversight into contract management and administration capability (DoD Strategic Plan v2.0, September 2014) |
| DoDOBJ-3 | Data Integration | Share data sources across domains and various reporting databases of contracting data. Adherence to the USD (AT&L) Linking Financial Data to Contract Documents Memo dated 18 MAR 2009 |
| DoDOBJ-4 | Reduce Complexity | Reduce complexity of contracting business systems throughout all phases of the contracting process (DoD Strategic Plan v2.0, September 2014) |
| DoDOBJ-5 | Net-Ready | Deploy a net-centric solution that supports Military operation, managed on the network and effectively exchanges information (DoD Strategic Plan v2.0, September 2014) |
ACWS Requirements Traceability Matrix 4 November 2015
&A &P of &N
Level 1-High Level Objectives
| DoD-ID | HLO-ID | High Level Outcome (HLO) Short Title | High Level Outcome (HLO) Description |
| DoDOBJ-1 | HLO-1 | Adaptability | Apply Better Buying Power initiatives to achieve efficiencies; Implement and maintain an open and scalable architecture that allows for capability enhancements, system adaptability, and technology insertion. |
| DoDOBJ-2 | HLO-2 | Contract Management and Administration | Optimize standard business processes, procedures, templates and formats to enable contract administration and leverage BI to provide increased visibility and oversight over the management and administration of contracts. |
| DoDOBJ-3 | HLO-3 | Process and Data Exchange | Successful automated data exchanges and workflow across functional domains (procurement, finance, and logistics) and the DoD. |
| DoDOBJ-4 | HLO-4 | Integrated System | Implement an integrated contract writing and management system that performs the full spectrum of procurement business processes to support the awarding and administration of legally binding procurement instruments in accordance with the FAR and its supplements while reducing overall system and process complexity, fostering usability, and eliminating redundant data entry within a single solution. |
| DoDOBJ-5 | HLO-5 | Net-Ready | Supports military operations, is entered and managed on the network, and effectively exchanges information. |
| DoDOBJ-5 | HLO-6 | Operational Availability | Capable of performing its assigned mission for the environment in which it is deployed. |
ACWS Requirements Traceability Matrix 4 November 2015
&A &P of &N
Level 2-Business Outcomes
| DoD-ID | HLO-ID | BO-ID | BO Short Title | Business Outcome Description | Measurement | Targeted Threshold Value | Targeted Objective Value | |
| DoDOBJ-1 | HLO-1 | BO-1 | Emerging Requirements | System will provide baseline capabilities and is adaptable to implement emerging requirements based on policy changes and/or user needs. | Amount of time required for the system to implement changes based upon user needs and policy updates that have been approved by the CCB/PSGB Process. | Implement system change < 8 months after CCB/PSGB approval | Implement system change < 6 months after CCB/PSGB approval | |
| DoDOBJ-2 | HLO-2 | BO-2 | Data Accuracy and Integrity | Enforce standard business rules and workflows to ensure data accuracy and integrity. | Percentage of data reported data that matches the data within ACWS. | 95% of data reported to FPDS-NG and DAADS matches data within ACWS | 98% of data reported to FPDS-NG and DAADS matches data within ACWS | |
| DoDOBJ-3 | HLO-3 | BO-3-1 | Pre-Award Funds Check | Procure-to-Pay Handshake 2; System performs integrity checks that ensures validation and re-verification of data (at the line item level) to account for changes since receipt of a Purchase Request (PR). | Percentage of instruments for which funds-check validations are executed prior to award. | 98% of instruments within ACWS have funds-check executed prior to award | 99.5% of instruments within ACWS have funds-check executed prior to award | |
| DoDOBJ-3 | HLO-3 | BO-3-2 | Integration with Accounting Systems | Procure-to-Pay Handshake 3; Obligations are posted accurately in the appropriate accounting system. | Percentage of instruments that are accurately recorded within the appropriate accounting systems IAW established business rules. | 95% of obligation data is accurately and electronically recorded in the appropriate accounting system | 98% of obligation data is accurately and electronically recorded in the appropriate accounting system | |
| DoDOBJ-3 | HLO-3 | BO-3-3 | Accurate Data Exchange with External Systems | Information shared and/or posted accurately in the appropriate system. | Percentage of instruments that successfully pass the Procurement Data Standard (PDS) validation. | 95% PDS validation success rate | 98% PDS validation success rate | |
| DoDOBJ-3 | HLO-3 | BO-3-4 | Prompt Data Exchange with External Systems | Information shared and/or posted promptly in the appropriate system. | Average time to electronically distribute data to Electronic Document Access (EDA). Transactions originating from 'disconnected state' should be measured from point of data-synchronization. | |||
| EDA Load Date < 24 hours | ||||||||
| (monthly average) | EDA Load Date < 1 hour |
(monthly average)
| DoDOBJ-4 | HLO-4 | BO-4 | Optimized and Standard Business Processes | A Contract Writing System that uses modern technologies to allow for configurable workflow and real-time collaboration using centralized services, standardized business rules, and standard data formats. | The percentage of business process models and templates that have been reduced, simplified or standardized as compared to the AS-IS state. | 15% reduction, simplification or standardization | 25% reduction, simplification or standardization |
| DoDOBJ-5 | HLO-5 | BO-5-1 | Net Ready on NIPRnet | A CWS that is maintained and sustained on the NIPRnet in both CONUS and OCONUS environments. | Authority to Operate (ATO) on NIPRnet. | ATO granted for operations on NIPRnet | ATO granted for operations on NIPRnet |
| DoDOBJ-5 | HLO-5 | BO-5-2 | Net Ready on SIPRnet | A CWS that is maintained and sustained on the SIPRnet in both CONUS and OCONUS environments. | ATO on SIPRnet. | ATO granted for operations on SIPRnet | ATO granted for operations on SIPRnet |
| DoDOBJ-5 | HLO-6 | BO-6-1 | Availability | System is operationally capable of performing assigned mission. | Percentage of time that ACWS is operationally available (MTBF/(MTBF+MTTR)). |
MTBF = Mean Time Between Failure
| MTTR = Mean Time To Repair | 98.5% availability |
| (measured over a complete FY) | 99.5% availability |
(measured over a complete FY)
| DoDOBJ-5 | HLO-6 | BO-6-2 | Reliability | Average time between system failures. | Number of hours between system failures (MTBF). | |
| [Based on 24 hours per day over 28 days] | MTBF > 672 hours (~One Month) | MTBF > 2688 hours (~One Quarter) | ||||
| DoDOBJ-5 | HLO-6 | BO-6-3 | Maintainability | Average amount of time it takes a system or system element to be repaired. | Number of hours to repair system (MTTR). | |
| [Based on 24 hours per day over 28 days] | MTTR < 8 hours | MTTR < 4 hours |
ACWS Requirements Traceability Matrix 4 November 2015
&A &P of &N
Level 3-Basic Capabilities
| DoD-ID | HLO-ID | BO-ID | BASIC-ID | Basic Capability Requirement Short Title | Basic Capability Requirement Description | Trace to 3b - Level 1 Process Model | |
| DoDOBJ-1 | HLO-1 | BO-1 | DS | Disconnected State | The ACE requires the ability to transition from a connected state to a disconnected state and then sync back with the connected state. | TBD | |
| DoDOBJ-1 | |||||||
| DoDOBJ-2 | HLO-1 | ||||||
| HLO-2 | BO-1 | ||||||
| BO-2 | GN | General Requirements | The Army Contracting Enterprise (ACE) requires the ability to implement policies, procedures, and high-level objectives in its business systems. | System Maintenance - System Configuration |
System Maintenance - Clause Maintenance System Maintenance - Business Rule Maintenance System Maintenance - Account Management DoDOBJ-1 DoDOBJ-2 DoDOBJ-4 DoDOBJ-5 HLO-1
HLO-2
HLO-4
HLO-5 BO-1
BO-2
BO-4
BO-5-2 PP Procurement Process Management The Army Contracting Enterprise (ACE) requires a business system to facilitate the collection of procurement data generated throughout the end-to-end contracting process and the presentation of this data in forms, reports, process workflows, and related activities required to execute the mission of the ACE. Contracting - Requirements Development Contracting - Source Selection Contracting - Contract Administration Contracting - Contract Closeout Contracting - Governance and Oversight Contracting - Vendor Engagement Assistance Agreements - Identify Funding Type and Purpose Assistance Agreement - Post-Award Administration Assistance Agreement - Closeout
| DoDOBJ-3 | |
| HLO-3 | BO-3-1 |
BO-3-2
BO-3-3
BO-3-4 IN Interface Specifications The Army Contracting Enterprise (ACE) requires the ability to integrate procurement data consumed by and generated in its business systems with complimentary business systems used throughout the procure-to-pay process at the Federal, DoD, and Army level. Contracting - Requirements Development Contracting - Award Contracting - Contract Administration Assistance Agreements - Identify Funding Type and Purpose Assistance Agreements - Negotiation and Award Assistance Agreement - Post-Award Administration
| DoDOBJ-1 | ||||
| DoDOBJ-4 | HLO-1 | |||
| HLO-4 | BO-1 | |||
| BO-4 | PI | Procurement Instrument | The Army Contracting Enterprise (ACE) requires a business system to faciliate the collection of procurement data for the purposes of creating procurement instruments in accordance with the Federal Acquisition Regulation (FAR), Defense Federal Acquisition Regulation Supplment (DFARS), Army Federal Acquisition Regulation Supplment (AFARS), and Department of Defense Grants and Agreements Regulations (DoDGARs). | Contracting - Solicitation |
Contracting - Award Assistance Agreements Application Assistance Agreement - Negotiation and Award DoDOBJ-5 HLO-5 BO-5 SA System Administration (Technical) The Army Contracting Enterprise (ACE) requires the ability to operate, maintain, and administer the business systems required to execute the ACE mission in a manner that remains compliant with policies, regulations, and standard practices. Contracting - General System Functions System Maintenance - Certifications, Disconnected State, & Local Sys Admin DoDOBJ-1 DoDOBJ-2 DoDOBJ-4 DoDOBJ-5 HLO-1
HLO-2
HLO-4
HLO-5
HLO-6 BO-1
BO-2
BO-4
BO-5
BO-6-1
BO-6-2
BO-6-3 SA System Administration (Technical) The Army Contracting Enterprise (ACE) requires the ability to operate, maintain, and administer the business systems required to execute the ACE mission in a manner that remains compliant with policies, regulations, and standard practices. Contracting - General System Functions System Maintenance - Help Desk, KM, & User Assist.
ACWS Requirements Traceability Matrix 04 November 2015
&A &P of &N
Level 4-Detailed Capabilities
| DoD-ID | HLO-ID | BO-ID | BASIC-ID | CAPABILITY-ID | Detailed Capability Requirement Short Title | Detailed Capability Requirement Description | Trace to 4b - Level 2 Process Models | |
| DoDOBJ-1 | HLO-1 | BO-1 | DS | DS | Disconnected State | The ACE requires the ability to transition from a connected state to a disconnected state and then sync back with the connected state. | Supports all processes | |
| DoDOBJ-1 | HLO-1 | BO-1 | ||||||
| BO-2 | GN | GOV | Governing policies, guidance, memos, etc. which must be considered when implementing requirements | The ACE requires the ability to implement policies, memos, strategies, etc. and to ensure compliance with these governing documents in its business systems. | Supports all processes | |||
| DoDOBJ-1 | HLO-1 | BO-1 | GN | OBJ | Stakeholder Objectives | The ACE requires the ability to implement stakeholder specific objectives in it's business processes and the systems utilized to facilitate those processes. | Supports all processes | |
| DoDOBJ-4 | HLO-4 | BO-4 | PI | ASN | Instrument Associations and Traceability | Procurement instruments and the line items associated with those instruments must maintain traceability of associations between related instruments to facilitate tracking data at the end of the contracting process to requirements received at the beginning of the contracting process. | Basic IDC |
Broad Agency Announcement Contract Modification Definitive Contract Grant/Agreement/OT Grant/Agreement/OT Modification Order RFQ/RFP Solicitation Solicitation Amendment Limited Distribution Solicitation Task/Delivery Order Associate PR Associate Requirements Package
| DoDOBJ-2 | |||||
| DoDOBJ-4 | HLO-2 | ||||
| HLO-4 | BO-2 | ||||
| BO-4 | PP | ADM | Post-Award Administration (other than PI) | The management of the procurement process requires access to post-award data and the presentation of this data to ACE stakeholders in order to monitor the successful execution and compliance with the terms of an award. | Contract Modification |
CDR Resolution COR File Reviews Termination Notices FOIA Requests Performance Reporting Termination Procedures ULO Management Issue Letter of Auth / TBC Closeout
| DoDOBJ-2 | |||||
| DoDOBJ-4 | HLO-2 | ||||
| HLO-4 | BO-2 | ||||
| BO-4 | PP | BIN | Business Intelligence, Dashboards, Reporting, and Metrics | The management of the procurement process requires the ability to query data gathered throughout the end-to-end contracting process, structure that data, and present the data in various formats to ACE stakeholders. | Metrics & Compliance |
Workload Reporting DAADS Reporting FPDS-NG (CARs) Award Notification Posting
| DoDOBJ-2 | |||||
| DoDOBJ-4 | HLO-2 | ||||
| HLO-4 | BO-2 | ||||
| BO-4 | PP | CLO | Contract Closeout Processes | The management of the procurement process requires the ability to identify the events which trigger contract closeout processes and the ability to execute the closeout process in a data-centric manner. | Assistance Agreement Closeout |
Contract Closeout
| DoDOBJ-2 | |||||
| DoDOBJ-4 | HLO-2 | ||||
| HLO-4 | BO-2 | ||||
| BO-4 | PP | EXC | Exceptions to Standard Business Rules | The management of the procurement process requires identification and control of all exceptions to standard business rules and their implementation in business systems. | User Setup & Admin |
| DoDOBJ-2 | |||||
| DoDOBJ-4 | HLO-2 | ||||
| HLO-4 | BO-2 | ||||
| BO-4 | PP | FIL | Official Contract File | The management of the procurement process requires the structured organization of instruments, documents, data, etc. in a filing structure that facilitates the records management activities associated with the end-to-end contracting process. | Establish Procurement Action Record |
Contract File Management Determinations & Findings Workflow-Doc File Review
| DoDOBJ-2 | |||||
| DoDOBJ-4 | HLO-2 | ||||
| HLO-4 | BO-2 | ||||
| BO-4 | PP | PDA | Management of Protests, Disputes, and Appeals | The management of the procurement process requires the ability to record and report on the status of protests, disputes, and appeals submitted in conjunction with a procurement action. | Termination Notices |
Protest Management
| DoDOBJ-2 | |||||
| DoDOBJ-4 | HLO-2 | ||||
| HLO-4 | BO-2 | ||||
| BO-4 | PP | PER | Management of Contracting personnel (other than SA-USR) | The management of the procurement process requires the ability to manage the non-Personally Identifiable Information (non-PII) data associated with the personnel who perform the end-to-end contracting process. Includes Warrants, Organizational Alignment, Position, etc. | Warrant Management |
User Setup & Admin DoDOBJ-4 HLO-4 BO-4 PP REQ Requiring Activity Engagement (other than Source Selection specific) The management of the procurement process requires the ability to actively engage with the requiring activity who is the customer of the procurement process. This data associated with this engagement is consumed by the contracting process as well as generated by the contracting process. COR Assignment/Termination COR File Reviews Calculate Cycle Time Establish Milestones Associate PR Associate Requirements Package Past Performance Evaluations Technical Evaluations DoDOBJ-1 DoDOBJ-2 DoDOBJ-4 HLO-1
HLO-2
HLO-4 BO-1
BO-2
| BO-4 | PP | RUL | Standard Business Rules | The management of the procurement process requires identification and control of standard business rules and their implementation in business systems. | All processes |
| DoDOBJ-2 | |||||
| DoDOBJ-4 | HLO-2 | ||||
| HLO-4 | BO-2 | ||||
| BO-4 | PP | RM | Records Management | The management of the procurement process requires official contract files which have retention requirements. | All processes |
| DoDOBJ-4 | |||||
| DoDOBJ-5 | HLO-4 | ||||
| HLO-5 | BO-4 | ||||
| BO-5 | PP | SEC | Requirements specific to operating in a secure (i.e. SIPRNET) environment | The management of the procurement process requires unique marking and handling rules in order to support Secure Environment Contracting activities. | All processes |
| DoDOBJ-2 | |||||
| DoDOBJ-4 | HLO-2 | ||||
| HLO-4 | BO-2 | ||||
| BO-4 | PP | SPT | Pricing, Legal, Policy, Small Business, Inspections, PMRs, and related functions | The management of the procurement process requires engagement with numerous supporting offices and organizations. This engagement serves as both inputs to the contracting process as well as relies on outputs from the contracting process. | PMRs |
Peer Reviews Small Business Coordination Price Negotiation Memorandum DCAA/DCMA Audit Requests Legal Reviews FOIA Requests Contract Cost/Price Analysis Workflow-Doc File Review
| DoDOBJ-2 | |||||
| DoDOBJ-4 | HLO-2 | ||||
| HLO-4 | BO-2 | ||||
| BO-4 | PP | SRC | Source Selection, Proposal, and Evaluations management | The management of the procurement process requires specific processes and procedures to execute various source selection approaches. The complex nature of some source selection activities require automation tools to facilitate the process, automate data collection and presentation, and optimize collaboration of the source selection team. | Automated Source Selection |
Justification & Approvals Offline Source Selection (Large & Small) Past Performance Evaluations Peer Reviews Price Negotiation Memorandum Reverse Auction Technical Evaluations Cost/Price Analysis Small Business Participation Evaluation
| DoDOBJ-1 | |||||
| DoDOBJ-4 | HLO-2 | ||||
| HLO-1 | BO-2 | ||||
| BO-1 | PP | VDR | Vendor Engagement | The management of the procurement process requires engagement with vendors throughout the end-to-end contracting process. As part of this engagement, data flows in from vendors as well as out to vendors in both a targeted (single vendor communication) and untargeted (public posting) manner. | FBO/ASFI Award Notice |
FBO/ASFI Synopsis Issue Letter of Auth / TBC Limited Distribution Solicitation Solicitation Solicitation Amendment Order RFQ/RFP Broad Agency Announcement Past Performance Evaluations ULO Management Reverse Auction
| DoDOBJ-2 | |||||
| DoDOBJ-4 | HLO-2 | ||||
| HLO-4 | BO-2 | ||||
| BO-4 | PP | WKF | Routing, Assignments, Reviews, Approvals, and similar Workflow; | The management of the procurement process requires the ability for stakeholders to execute tasks in both parrallel and serial order to progress through the end-to-end procurement process. Data generated during the execution of these tasks must be collected for prudent management of the process. | Establish Procurement Action Record |
Audit Justification & Approvals Legal Reviews PMRs Assign Workload Workload Reassignment Workload Reporting Workload Reviews Peer Reviews Workflow-Doc File Review
| DoDOBJ-2 | |||||
| DoDOBJ-4 | HLO-2 | ||||
| HLO-4 | BO-2 | ||||
| BO-4 | PP | WKL | Data & Processes required to manage individual workload | The management of the procurement process requires the ability for an individual executing procurement actions to obtain visibility into the status of their complete set of assigned work in order to balance and prioritize activities associated with the procurement process. | Establish Procurement Action Record |
Calculate Cycle Time Establish Milestones Workload Reporting Workload Reviews DoDOBJ-3 HLO-3 BO-3-1
BO-3-2
BO-3-3
BO-3-4 IN ABSS Interface with ABSS (AF Acctg System used at Joint Bases and by NGB) The ACE requires the ability to exchange data with the Automated Business Services System (ABSS) for the purpose of exchanging accounting, contracting, and related business data. Basic IDC Contract Modification Definitive Contract Grant/Agreement/OT Grant/Agreement/OT Modification Task/Delivery Order DoDOBJ-3 HLO-3 BO-3-1
BO-3-2
BO-3-3
BO-3-4 IN CEFMS Interface with CEFMS The ACE requires the ability to exchange data with the Corps of Engineers Financial Management System (CEFMS) for the purpose of exchanging accounting, contracting, and related business data. Basic IDC Contract Modification Definitive Contract Grant/Agreement/OT Grant/Agreement/OT Modification Task/Delivery Order Associate PR Associate Requirements Package
| DoDOBJ-3 | HLO-3 | BO-3-3 | |||
| BO-3-4 | IN | CISIL | Interface with CISIL | The ACE requires the ability to exchange data with the Central Information System for International Logistics (CISIL) for Foreign Military Sales acquisitions. | Basic IDC |
Contract Modification Definitive Contract Task/Delivery Order Associate PR Associate Requirements Package
| DoDOBJ-3 | HLO-3 | BO-3-3 | |||
| BO-3-4 | IN | CLSLG | Interface with DPAP Clause Logic | The ACE requires the ability for a user of its contract writing system to invoke the Clause Logic Web Service provided by Defense Procurement and Acquisition Policy (DPAP) to obtain clauses for each instrument. | Basic IDC |
Broad Agency Announcement Contract Modification Definitive Contract Grant/Agreement/OT Grant/Agreement/OT Modification Order RFQ/RFP Solicitation Solicitation Amendment Limited Distribution Solicitation Task/Delivery Order
| DoDOBJ-3 | HLO-3 | BO-3-3 | |||
| BO-3-4 | IN | CMP | Interfaces in accordance with a Commercial Practice | The ACE requires systems interfaces to be based on published industry standards. | Supports all processes |
| DoDOBJ-3 | HLO-3 | BO-3-3 | |||
| BO-3-4 | IN | DAADS | Interface with DAADS | The ACE requires the ability to exchange data with the Defense Assistance Award Data System (DAADS) for Department of Defense Grants and Agreement Regulations based award instruments to execute a DD 2566 (Department of Defense Assistance Award Action Report). | Grant/Agreement/OT |
Grant/Agreement/OT Modification
| DoDOBJ-3 | HLO-3 | BO-3-3 | |||
| BO-3-4 | IN | DAMES | Interface with DAMES | The ACE requires the ability to exchange data with the Defense Automated Message Exchange System (DAMES) for Foreign Military Sales acquisitions. | Basic IDC |
Broad Agency Announcement Contract Modification Definitive Contract Grant/Agreement/OT Grant/Agreement/OT Modification Order RFQ/RFP Solicitation Solicitation Amendment Limited Distribution Solicitation Task/Delivery Order Associate PR Associate Requirements Package
| DoDOBJ-3 | HLO-3 | BO-3-3 | |||
| BO-3-4 | IN | DATAWH | Business Intelligence Data Warehouse (ACBIS/VCE-BI) | The ACE requires the ability to exchange data with an enterprise procurement data warehouse to facilitate Business Intelligence functions. | Metrics & Compliance |
Workload Reporting DAADS Reporting FPDS-NG (CARs)
| DoDOBJ-3 | HLO-3 | BO-3-3 | |||
| BO-3-4 | IN | DLIS | Interface with Defense Logistics Information System (unless met via Shared Services Center or other DODAAC Mgmt ) | The ACE requires the ability to exchange data with the Defense Logistics Information System (DLIS) to obtain Address data for Department of Defense Offices. | Basic IDC |
Broad Agency Announcement Contract Modification Definitive Contract Grant/Agreement/OT Grant/Agreement/OT Modification Order RFQ/RFP Solicitation Solicitation Amendment Limited Distribution Solicitation Task/Delivery Order Associate PR Associate Requirements Package
| DoDOBJ-3 | HLO-3 | BO-3-3 | |||
| BO-3-4 | IN | EXT | General External Transaction Requirements | The ACE requires the ability to exchange data with complimentary business systems using specific data exchange formats and technologies for select system integrations. | Supports all processes |
| DoDOBJ-3 | HLO-3 | BO-3-3 | |||
| BO-3-4 | IN | FBO | Interface with FedBizOps prior to SAM | The ACE requires the ability to exchange data with the Government's Single Point of Entry for Federal Business Opportunities to post public notices on Federal Business Opportunities within the Army. | Basic IDC |
Broad Agency Announcement Definitive Contract Solicitation Solicitation Amendment FBO/ASFI Award Notice FBO/ASFI Synopsis
| DoDOBJ-3 | HLO-3 | BO-3-3 | |||
| BO-3-4 | IN | FPDS | Interface with FPDS-NG prior to SAM | The ACE requires the ability to exchange data with the Federal Procurement Data System - Next Generation (FPDS-NG) in order to execute a Contract Action Report for FAR-based award instruments. | Basic IDC |
Contract Modification Definitive Contract Task/Delivery Order FPDS-NG (CARs)
| DoDOBJ-3 | HLO-3 | BO-3-3 | |||
| BO-3-4 | IN | GEX | Interface with Global Exchange (GEX) (WAWF, EDA, MOCAS, etc.) | The ACE requires the ability to exchange data with the Department of Defense Global Exchange (GEX) for automated distribution of award instruments. | Basic IDC |
Contract Modification Definitive Contract Grant/Agreement/OT Grant/Agreement/OT Modification Task/Delivery Order DoDOBJ-3 HLO-3 BO-3-1
BO-3-2
BO-3-3
BO-3-4 IN GFEBS Interface with GFEBS The ACE requires the ability to exchange data with the General Funds Enterprise Business System (GFEBS) for the purpose of exchanging accounting, contracting, and related business data. Basic IDC Contract Modification Definitive Contract Grant/Agreement/OT Grant/Agreement/OT Modification Task/Delivery Order Associate PR Associate Requirements Package
| DoDOBJ-3 | HLO-3 | BO-3-3 | |||
| BO-3-4 | IN | IAPS | Interface with IAPS (AF Acctg System used at Joint Bases and by NGB) | The ACE requires the ability to exchange data with the Integrated Accounts Payable System (IAPS) for the purpose of exchanging accounting, contracting, and related business data. | Basic IDC |
Contract Modification Definitive Contract Grant/Agreement/OT Grant/Agreement/OT Modification Task/Delivery Order Associate PR Associate Requirements Package DoDOBJ-3 HLO-3 BO-3-1
BO-3-2
BO-3-3
BO-3-4 IN LMP Interface with LMP The ACE requires the ability to exchange data with the Logistics Modernization Program (LMP) for the purpose of exchanging accounting, contracting, and related business data. Basic IDC Contract Modification Definitive Contract Grant/Agreement/OT Grant/Agreement/OT Modification Task/Delivery Order Associate PR Associate Requirements Package
| DoDOBJ-3 | HLO-3 | BO-3-3 | |||
| BO-3-4 | IN | RMS | Interface with RMS | The ACE requires the ability to exchange data with the Resident Management System (RMS) for awards issued by the US Army Corps of Engineers where administration will be facilitated by RMS. | Basic IDC |
Contract Modification Definitive Contract Grant/Agreement/OT Grant/Agreement/OT Modification Task/Delivery Order Associate PR Associate Requirements Package
| DoDOBJ-3 | HLO-3 | BO-3-3 | |||
| BO-3-4 | IN | SAM | Interface with SAM (currently Entity mgmt, but eventually all SAM functions including ORCA, EPLS, eSRS, etc.) | The ACE requires the ability to exchange data with the System for Award Management (SAM) to obtain data pertaining to the identify and performance of vendors and awardees. | Basic IDC |
Broad Agency Announcement Contract Modification Definitive Contract Grant/Agreement/OT Grant/Agreement/OT Modification Order RFQ/RFP Solicitation Solicitation Amendment Limited Distribution Solicitation Task/Delivery Order
| DoDOBJ-1 | |||
| DoDOBJ-4 | HLO-1 | ||
| HLO-4 | BO-1 | ||
| BO-4 | PI | ATT | Attachments and Specifications |
| (Section C and J) | Procurement instruments must include specifications of the item and/or services being contracted for which may be specified within the text of the instrument itself or as an attachment/exhibit to the instrument. | Basic IDC |
Broad Agency Announcement Contract Modification Definitive Contract Grant/Agreement/OT Grant/Agreement/OT Modification Order RFQ/RFP Solicitation Solicitation Amendment Limited Distribution Solicitation Task/Delivery Order
| DoDOBJ-4 | HLO-4 | BO-4 | PI | CLS | Clauses, Provisions, & Clause Logic | |
| (Section H, I, K, L, and M) | Procurement instruments must include clauses, provisions, terms and conditions appropriate for the type of instrument being generated in accordance with the FAR, DFARS, AFARS, and DoDGARS. | Basic IDC |
Broad Agency Announcement Contract Modification Definitive Contract Grant/Agreement/OT Grant/Agreement/OT Modification Order RFQ/RFP Solicitation Solicitation Amendment Limited Distribution Solicitation Task/Delivery Order Local Clause Administration
| DoDOBJ-1 | |||
| DoDOBJ-4 | HLO-1 | ||
| HLO-4 | BO-1 | ||
| BO-4 | PI | DOC | Instrument/Header/Document-Level |
| (Section A) | Procurement instruments must identify high/instrument level data to identify the general terms of the contract and present this data in accordance with the prescribed solicitation/contract form. | Basic IDC |
Broad Agency Announcement Contract Modification Definitive Contract Grant/Agreement/OT Grant/Agreement/OT Modification Order RFQ/RFP Solicitation Solicitation Amendment Limited Distribution Solicitation Task/Delivery Order
| DoDOBJ-1 | |||
| DoDOBJ-4 | HLO-1 | ||
| HLO-4 | BO-1 | ||
| BO-4 | PI | FND | Funding (Section G) and |
| Pricing (Section B) | Procurement instruments must include any required accounting and appropriation data and any required contract administration information or instructions other than those on the instrument form. | Basic IDC |
Broad Agency Announcement Contract Modification Definitive Contract Grant/Agreement/OT Grant/Agreement/OT Modification Order RFQ/RFP Solicitation Solicitation Amendment Limited Distribution Solicitation Task/Delivery Order DoDOBJ-4 HLO-4 BO-4 PI LIN Line Item Information (Section B) Procurement instruments must include a description of the supplies or services being procured, present this information in a line item structure that is consistent with DFARS 204 and structure line items to facilitate auditability with the applicable financial and logistics systems. Basic IDC Broad Agency Announcement Contract Modification Definitive Contract Grant/Agreement/OT Grant/Agreement/OT Modification Order RFQ/RFP Solicitation Solicitation Amendment Limited Distribution Solicitation Task/Delivery Order DoDOBJ-4 HLO-4 BO-4 PI LOG Logistics:
Packaging (Section D), Inspection & Acceptance (Section E), and Period of Performance/Delivery (Section F) Procurement instruments must include logistics data associated with the line items to provide packagin, packing, preservation, and marking requirements; inspection, acceptance, quality assurance, and reliability requirements; and the requirements for time, place, and method of delivery or performance. Basic IDC Broad Agency Announcement Contract Modification Definitive Contract Grant/Agreement/OT Grant/Agreement/OT Modification Order RFQ/RFP Solicitation Solicitation Amendment Limited Distribution Solicitation Task/Delivery Order DoDOBJ-4 HLO-4 BO-4 PI PRT Instrument/Form Rendering Procurement instruments and related forms must be presented in a format that is consistent with the prescribed format and clearly presents information in a format that is readable to all actors involved in the procurement process. Basic IDC Broad Agency Announcement Contract Modification Definitive Contract Grant/Agreement/OT Grant/Agreement/OT Modification Order RFQ/RFP Solicitation Solicitation Amendment Limited Distribution Solicitation Task/Delivery Order
| DoDOBJ-5 | HLO-5 | BO-5 | SA | CRT | DIACAP, ATO, CoN, and related Certifications and Accreditations | The administration of ACE business systems requires the compliance of these systems within the DoD Risk Management Framework. | User Setup & Admin | |
| DoDOBJ-4 | HLO-4 | BO-4 | SA | DCM | System Documentation | The administration of ACE business systems requires the development and maintenance of system documentation required for an operator to understand the functions enabled by the business system and ensure the proper execution of administration tasks. | Supports all processes | |
| DoDOBJ-5 | HLO-5 | BO-5 | SA | GUI | Graphical User Interface | The administration of ACE business systems requires the development and implementation of a consistent and intuitive graphical user interface across all platforms and instances of the business system. | Supports all processes | |
| DoDOBJ-1 | ||||||||
| DoDOBJ-4 | HLO-1 | |||||||
| HLO-4 | BO-1 | |||||||
| BO-4 | SA | HLP | Knowledge management functions (e.g. help icons/info, guides, etc.) | The administration of ACE business systems requires the development, implementation, and maintenance of information resources that will facilitate the consistent and proper utilization of the system and troubleshooting activities for unfamiliar outcomes. | Supports all processes | |||
| DoDOBJ-5 | HLO-5 | BO-5 | SA | NWK | Requirements associated with operating on DoD/Army Networks including disconnected states for Expeditionary environments | The administration of ACE business systems requires solution that can be deployed in a web-centric, DoD networked infrastructure. This also includes operations in a temporarily disconnected state. | Supports all processes | |
| DoDOBJ-4 | ||||||||
| DoDOBJ-5 | HLO-4 | |||||||
| HLO-6 | BO-6-2 | SA | LSA | Local System Administration of local rules, data elements, processes, etc. | The adminstration of ACE business systems requires the ability for authorized users at all echeleons in the ACE structure to implement solutions as appropriate for the processes managed at that echelon. | Local Clause Administration |
User Setup & Admin Workload Reassignment DoDOBJ-1 DoDOBJ-2 DoDOBJ-4 DoDOBJ-5 HLO-1
HLO-2
HLO-4
HLO-6 BO-1
BO-2
BO-4
BO-6-1
| BO-6-3 | SA | SYS | Execution of technical system functions (e.g. Digital Signature, CAC Login, Messaging, etc.) | The administration of ACE business systems requires the ability to implement specific technical solutions for various tasks in order to remain compliant with DoD technical standards for business systems. | Supports all processes | |||
| DoDOBJ-4 | HLO-4 | BO-4 | SA | USR | User profile administration & access controls | The administration of ACE business systems requires the ability to manage user accounts, permissions, roles, etc. necessary to ensure proper controls are implemented in the end-to-end procurement process. | User Setup & Admin |
Attachment 004 ACWS Requirements Traceability Matrix 04 November 2015
&A &P of &N
Level 5-System Requirements
| DoD-ID | HLO-ID | BO-ID | BASIC-ID | CAPABILITY-ID | Identifier | Sub Identifier | REQUIREMENT-ID | Short Title | Requirement Description |
| DoDOBJ-1 | HLO-1 | BO-1 | DS | SYS | 1 | 1 | DS-SYS-1-1 | DS-SYS-1-1 | The system shall replicate data across multiple nodes. |
| DoDOBJ-1 | HLO-1 | BO-1 | DS | SYS | 2 | 1 | DS-SYS-2-1 | DS-SYS-2-1 | When a system node is prepared for disconnection from the master data server, it shall enable an authorized system administrator to replicate a subset of the master database into its local data store. |
| DoDOBJ-1 | HLO-1 | BO-1 | DS | SYS | 3 | 1 | DS-SYS-3-1 | DS-SYS-3-1 | When a system node replicates a portion of the master database, the master database shall retrieve and transmit the associated data from complementary systems. |
| DoDOBJ-1 | HLO-1 | BO-1 | DS | SYS | 4 | 1 | DS-SYS-4-1 | DS-SYS-4-1 | When a system node is reconnected to the master data server, it shall synchronize its local data store with the master database. |
| DoDOBJ-1 | HLO-1 | BO-1 | DS | SYS | 5 | 1 | DS-SYS-5-1 | DS-SYS-5-1 | The system shall be deployable on thin client laptop and notebook platforms. |
| DoDOBJ-1 | HLO-1 | BO-1 | DS | SYS | 6 | 1 | DS-SYS-6-1 | DS-SYS-6-1 | The system client will be deployable on approved mobile devices. |
| DoDOBJ-1 | HLO-1 | BO-1 | DS | SYS | 7 | 1 | DS-SYS-7-1 | DS-SYS-7-1 | The system server software shall be approved for deployment on a virtualized Department of Defense platform. |
| DoDOBJ-1 | HLO-1 | BO-1 | DS | SYS | 8 | 1 | DS-SYS-8-1 | DS-SYS-8-1 | The system shall enable an authorized user to configure the local host system to operate in stand alone mode. |
| DoDOBJ-1 | HLO-1 | BO-1 | DS | SYS | 8 | 2 | DS-SYS-8-2 | DS-SYS-8-2 | When a stand alone configured system is reconnected to a network, the system shall synchronize the data from the standalone system with the centralized Army Contract Writing System data base. |
| DoDOBJ-1 | HLO-1 | BO-1 | DS | SYS | 8 | 3 | DS-SYS-8-3 | DS-SYS-8-3 | The system shall be configurable as a stand alone system, in disconnected mode in accordance with ACWS CONOPS. |
| DoDOBJ-1 | HLO-1 | BO-1 | DS | SYS | 8 | 4 | DS-SYS-8-4 | DS-SYS-8-4 | When a disconnected system enters connected mode, it shall synchronize the data entered offline with the centralized system server in accordance with the ACWS CONOPS. |
| DoDOBJ-1 | HLO-1 | BO-1 | GN | GOV | 2 | 1 | GN-GOV-2-1 | GN-GOV-2-1 | The system shall be capable of timely adaptation to changing regulations and business needs. |
| DoDOBJ-1 | HLO-1 | BO-1 | GN | GOV | 2 | 2 | GN-GOV-2-2 | GN-GOV-2-2 | When regulatory or statutory requirements have changed, the system shall be capable of modification within six months to meet the new requirements. |
| DoDOBJ-1 | HLO-1 | BO-1 | GN | GOV | 2 | 3 | GN-GOV-2-3 | GN-GOV-2-3 | When a change to business operations is required due to changed business rules or external Army business systems, the system shall be capable of modification within six months to meet the new requirements. |
| DoDOBJ-1 | HLO-1 | BO-1 | GN | OBJ | 1 | 1 | GN-OBJ-1-1 | GN-OBJ-1-1 | The system shall minimize the entry of redundant data during document, instrument, and Electronic Official File preparation. |
| DoDOBJ-1 | HLO-1 | BO-1 | GN | OBJ | 2 | 1 | GN-OBJ-2-1 | GN-OBJ-2-1 | The system shall minimize the necessity for direct keying during transaction processing. Data should be entered once and shared throughout the system |
| DoDOBJ-1 | HLO-1 | BO-1 | GN | OBJ | 3 | 1 | GN-OBJ-3-1 | GN-OBJ-3-1 | When an action or activity is required throughout the procurement lifecycle, the system shall generate alerts, emails, and notices to notify appropriate individuals. |
| DoDOBJ-2 | HLO-2 | BO-2 | GN | OBJ | 4 | 1 | GN-OBJ-4-1 | GN-OBJ-4-1 | The system shall enable a user to execute a final data integrity validation process prior to finalizing an instrument. |
| DoDOBJ-2 | HLO-2 | BO-2 | GN | OBJ | 4 | 2 | GN-OBJ-4-2 | GN-OBJ-4-2 | When a draft instrument fails a data integrity check, the system shall enable the user to resolve the issues identified. |
| DoDOBJ-2 | HLO-2 | BO-2 | GN | OBJ | 5 | 1 | GN-OBJ-5-1 | GN-OBJ-5-1 | The system shall enable the user to invoke the Defense Procurement and Acquisition Policy (DPAP) data validation web service to validate the data integrity of an instrument. |
| DoDOBJ-2 | HLO-2 | BO-2 | GN | OBJ | 5 | 2 | GN-OBJ-5-2 | GN-OBJ-5-2 | When an instrument is ready for signature, the system shall invoke the Defense Procurement and Acquisition Policy (DPAP) data validation web service web service to conduct a final validation check. |
| DoDOBJ-2 | HLO-2 | BO-2 | GN | OBJ | 5 | 3 | GN-OBJ-5- 3 | GN-OBJ-5- 3 | When the system receives the results of the final data integrity validation process, it shall notify the user. |
| DoDOBJ-2 | HLO-2 | BO-2 | GN | OBJ | 5 | 4 | GN-OBJ-5-4 | GN-OBJ-5-4 | When the results of the final data integrity validation process are received, the system shall enable the user to resolve the issues identified prior to signing the instrument. |
| DoDOBJ-2 | HLO-2 | BO-2 | GN | OBJ | 6 | 1 | GN-OBJ-6-1 | GN-OBJ-6-1 | The system shall automatically perform edit checks as the user executes business processes within the system. |
| DoDOBJ-2 | HLO-2 | BO-2 | GN | OBJ | 7 | 1 | GN-OBJ-7-1 | GN-OBJ-7-1 | The system shall enable a user to establish preferences for automated error checking. |
| DoDOBJ-2 | HLO-2 | BO-2 | GN | OBJ | 8 | 1 | GN-OBJ-8-1 | GN-OBJ-8-1 | The system shall provide the capability for a user to establish personalization preferences for alerts, on-screen help, and automated functions. |
| DoDOBJ-1 | HLO-1 | BO-1 | GN | OBJ | 9 | 1 | GN-OBJ-9-1 | GN-OBJ-9-1 | The system shall enable an enterprise system administrator to create business rules that identify specific data elements within the system as mandatory. |
| DoDOBJ-1 | HLO-1 | BO-1 | GN | OBJ | 10 | 1 | GN-OBJ-10-1 | GN-OBJ-10-1 | The system shall enable a user to obtain data for orders issued by agencies outside the Army against basic instruments issued by the Army using Contract Action Reporting (CAR) data. |
| DoDOBJ-1 | HLO-1 | BO-1 | GN | OBJ | 14 | 1 | GN-OBJ-14-1 | GN-OBJ-14-1 | The system shall secure procurement sensitive data from unauthorized release. |
| DoDOBJ-1 | HLO-1 | BO-1 | GN | OBJ | 14 | 2 | GN-OBJ-14-2 | GN-OBJ-14-2 | The system shall enable the user to mark data created by the system with the appropriate copyright, release restrictions and classification level when customized or configured for use. |
| DoDOBJ-1 | HLO-1 | BO-1 | GN | OBJ | 15 | 1 | GN-OBJ-15-1 | GN-OBJ-15-1 | The system shall enable the user access by allowing automatic log in to multiple applications based on the credentials provided at time of initial log in to the system |
| DoDOBJ-1 | HLO-1 | BO-1 | GN | OBJ | 16 | 1 | GN-OBJ-16-1 | GN-OBJ-16-1 | The system shall enable the user to search individual records for procurement status using a single or multiple descriptors |
| DoDOBJ-1 | HLO-1 | BO-1 | GN | OBJ | 17 | 1 | GN-OBJ-17-1 | GN-OBJ-17-1 | The system shall have the ability to incorporate DASA(P), Procurement Management Review (PMR), HQ, local level checklists and toolkits into the relational data fields and workflows |
| DoDOBJ-1 | HLO-1 | BO-1 | GN | OBJ | 18 | 1 | GN-OBJ-18-1 | GN-OBJ-18-1 | The system shall have the ability to incorporate and monitor progress towards small business and competition goals |
| DoDOBJ-1 | HLO-1 | BO-1 | GN | OBJ | 19 | 1 | GN-OBJ-19-1 | GN-OBJ-19-1 | The system shall have the ability provide visibility for enterprise Army contracts (such as CHESS, MACs, etc.) and make them available to issue instruments against. |
| DoDOBJ-1 | HLO-1 | BO-1 | GN | OBJ | 19 | 2 | GN-OBJ-19-2 | GN-OBJ-19-2 | The system shall have the ability provide ceiling and award visibility into enterprise Army contracts (such as CHESS, MACs, etc.) |
| DoDOBJ-3 | HLO-3 | BO-3-1 |
BO-3-2
BO-3-3
| BO-3-4 | IN | ABSS | 1 | 1 | IN-ABSS-1-1 | IN-ABSS-1-1 | The system shall establish an interface with the Automated Business Services System (ABSS) for the purpose of exchanging accounting, contracting, and related business data. |
| DoDOBJ-3 | |||||||
| DoDOBJ-6 | HLO-3 | BO-3-1 |
BO-3-2
BO-3-3
| BO-3-4 | IN | ABSS | 2 | 1 | IN-ABSS-2-1 | IN-ABSS-2-1 | The system shall receive an incoming Purchase Request (PR) from the Automated Business Services System (ABSS) electronically. |
| DoDOBJ-3 | |||||||
| DoDOBJ-6 | HLO-3 | BO-3-1 |
BO-3-2
BO-3-3
| BO-3-4 | IN | ABSS | 3 | 1 | IN-ABSS-3-1 | IN-ABSS-3-1 | When the system receives a Purchase Request (PR) sent by the Automated Business Services System (ABSS), it shall confirm that the Purchase Request has been received and validated by the system. |
| DoDOBJ-3 | |||||||
| DoDOBJ-6 | HLO-3 | BO-3-1 |
BO-3-2
BO-3-3
| BO-3-4 | IN | ABSS | 3 | 2 | IN-ABSS-3-2 | IN-ABSS-3-2 | When the system cannot validate a Purchase Request (PR) received from the Automated Business Services System (ABSS), it shall send a message to the Automated Business Services System describing the failure condition. |
| DoDOBJ-3 | |||||||
| DoDOBJ-6 | HLO-3 | BO-3-1 |
BO-3-2
BO-3-3
| BO-3-4 | IN | ABSS | 4 | 1 | IN-ABSS-4-1 | IN-ABSS-4-1 | The system shall route an incoming Automated Business Services System (ABSS) Purchase Request based upon the identification data contained in the Purchase Request. |
| DoDOBJ-3 | |||||||
| DoDOBJ-6 | HLO-3 | BO-3-1 |
BO-3-2
BO-3-3
| BO-3-4 | IN | ABSS | 5 | 1 | IN-ABSS-5-1 | IN-ABSS-5-1 | When an authorized user has accepted or rejected a Purchase Request originated by the Automated Business Services System (ABSS) , the system shall automatically notify the Automated Business Services System of this action. |
| DoDOBJ-3 | |||||||
| DoDOBJ-6 | HLO-3 | BO-3-1 |
BO-3-2
BO-3-3
| BO-3-4 | IN | ABSS | 6 | 1 | IN-ABSS-6-1 | IN-ABSS-6-1 | When the system receives a Purchase Request (PR) Amendment sent by the Automated Business Services System (ABSS), it shall confirm that the Purchase Request has been received and validated by the system |
| DoDOBJ-3 | |||||||
| DoDOBJ-6 | HLO-3 | BO-3-1 |
BO-3-2
BO-3-3
| BO-3-4 | IN | ABSS | 6 | 2 | IN-ABSS-6-2 | IN-ABSS-6-2 | When the system cannot validate a Purchase Request Amendment (PR) received from the Automated Business Services System (ABSS), it shall send a message to the Automated Business Services System describing the failure condition. |
| DoDOBJ-3 | HLO-3 | BO-3-3 | |||||
| BO-3-4 | IN | ACPERS | 1 | 1 | IN-ACPERS-1-1 | IN-ACPERS-1-1 | Upon creation of a user profile, the system shall receive and import designated data from Headquarters Army Civilian Personnel System (HQACPERS) into the profile. |
| DoDOBJ-3 | HLO-3 | BO-3-3 | |||||
| BO-3-4 | IN | ACPERS | 2 | 1 | IN-ACPERS-2-1 | IN-ACP-2-1 | The system shall periodically update Headquarters Army Civilian Personnel System (HQACPERS) data. |
| DoDOBJ-3 | |||||||
| DoDOBJ-6 | HLO-3 | BO-3-1 |
BO-3-2
BO-3-3
| BO-3-4 | IN | CEFMS | 1 | 1 | IN-CEFMS-1-1 | IN-CEFMS-1-1 | The system shall establish an interface with the Corps of Engineers Financial Management System (CEFMS) for the purpose of exchanging accounting, contracting, and related business data. |
| DoDOBJ-3 | |||||||
| DoDOBJ-6 | HLO-3 | BO-3-1 |
BO-3-2
BO-3-3
| BO-3-4 | IN | CEFMS | 10 | 1 | IN-CEFMS-10-1 | IN-CEFMS-10-1 | The system shall enable the user to query the delivery status from the Corps of Engineers Financial Management System (CEFMS) based upon a basic instrument identifier. |
| DoDOBJ-3 | |||||||
| DoDOBJ-6 | HLO-3 | BO-3-1 |
BO-3-2
BO-3-3
| BO-3-4 | IN | CEFMS | 10 | 2 | IN-CEFMS-10-2 | IN-CEFMS-10-2 | The system shall enable the user to query the acceptance status of goods and service from the Corps of Engineers Financial Management System (CEFMS) based upon a basic instrument identifier. |
| DoDOBJ-3 | |||||||
| DoDOBJ-6 | HLO-3 | BO-3-1 |
BO-3-2
BO-3-3
| BO-3-4 | IN | CEFMS | 11 | 1 | IN-CEFMS-11-1 | IN-CEFMS-11-1 | When the system receives a Purchase Request (PR) Amendment sent by the Corps of Engineers Financial Management System (CEFMS) it shall confirm that the Purchase Request has been received and validated by the system. |
| DoDOBJ-3 | |||||||
| DoDOBJ-6 | HLO-3 | BO-3-1 |
BO-3-2
BO-3-3
| BO-3-4 | IN | CEFMS | 11 | 2 | IN-CEFMS-11-2 | IN-CEFMS-11-2 | When the system cannot validate a Purchase Request (PR) Amendment received from the Corps of Engineers Financial Management System (CEFMS), it shall send a message to the Corps of Engineers Financial Management System describing the failure condition. |
| DoDOBJ-3 | |||||||
| DoDOBJ-6 | HLO-3 | BO-3-1 |
BO-3-2
BO-3-3
| BO-3-4 | IN | CEFMS | 12 | 1 | IN-CEFMS-12-1 | IN-CEFMS-12-1 | When sending obligation change data to the Corps of Engineers Financial Management System (CEFMS), the system shall publish the following data elements: from amount, to amount, and calculated difference. |
| DoDOBJ-3 | |||||||
| DoDOBJ-6 | HLO-3 | BO-3-1 |
BO-3-2
BO-3-3
| BO-3-4 | IN | CEFMS | 2 | 1 | IN-CEFMS-2-1 | IN-CEFMS-2-1 | The system shall receive an incoming Purchase Request (PR) from the Corps of Engineers Financial Management System (CEFMS) electronically. |
| DoDOBJ-3 | |||||||
| DoDOBJ-6 | HLO-3 | BO-3-1 |
BO-3-2
BO-3-3
| BO-3-4 | IN | CEFMS | 3 | 1 | IN-CEFMS-3-1 | IN-CEFMS-3-1 | When the system receives a Purchase Request (PR) send by the Corps of Engineers Financial Management System (CEFMS) it shall confirm that the Purchase Request has been received and validated by the system. |
| DoDOBJ-3 | |||||||
| DoDOBJ-6 | HLO-3 | BO-3-1 |
BO-3-2
BO-3-3
| BO-3-4 | IN | CEFMS | 3 | 2 | IN-CEFMS-3-2 | IN-CEFMS-3-2 | When the system cannot validate a Purchase Request (PR) received from the Corps of Engineers Financial Management System (CEFMS), it shall send a message to the Corps of Engineers Financial Management System describing the failure condition. |
| DoDOBJ-3 | |||||||
| DoDOBJ-6 | HLO-3 | BO-3-1 |
BO-3-2
BO-3-3
| BO-3-4 | IN | CEFMS | 4 | 1 | IN-CEFMS-4-1 | IN-CEFMS-4-1 | The system shall route an incoming Corps of Engineers Financial Management System (CEFMS) Purchase Request (PR) based upon the identification data contained in the Purchase Request. |
| DoDOBJ-3 | |||||||
| DoDOBJ-6 | HLO-3 | BO-3-1 |
BO-3-2
BO-3-3
| BO-3-4 | IN | CEFMS | 5 | 1 | IN-CEFMS-5-1 | IN-CEFMS-5-1 | When an authorized user has accepted or rejected a Purchase Request (PR) originated by the Corps of Engineers Financial Management System (CEFMS), the system shall automatically notify the Corps of Engineers Financial Management System. |
| DoDOBJ-3 | |||||||
| DoDOBJ-6 | HLO-3 | BO-3-1 |
BO-3-2
BO-3-3
| BO-3-4 | IN | CEFMS | 6 | 1 | IN-CEFMS-6-1 | IN-CEFMS-6-1 | The system shall user to enable the user to validate funds availability in the Corps of Engineers Financial Management System (CEFMS) by submitting a query to the Corps of Engineers Financial Management System prior to finalization of an award instrument in a connected mode. |
| DoDOBJ-3 | |||||||
| DoDOBJ-6 | HLO-3 | BO-3-1 |
BO-3-2
BO-3-3
| BO-3-4 | IN | CEFMS | 7 | 1 | IN-CEFMS-7-1 | IN-CEFMS-7-1 | The system shall send a record of the award data automatically to the Corps of Engineers Financial Management System (CEFMS) when the award instrument is electronically signed. |
| DoDOBJ-3 | |||||||
| DoDOBJ-6 | HLO-3 | BO-3-1 |
BO-3-2
BO-3-3
| BO-3-4 | IN | CEFMS | 8 | 1 | IN-CEFMS-8-1 | IN-CEFMS-8-1 | When the system sends an award instrument to the Corps of Engineers Financial Management System (CEFMS), it shall confirm that the award instrument has been received and validated by CEFMS. |
| DoDOBJ-3 | |||||||
| DoDOBJ-6 | HLO-3 | BO-3-1 |
BO-3-2
BO-3-3
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .