Attch_0027_ACWS_Offeror_Self_Certification_RFP_2016_05_06.xlsx
XLSX spreadsheet 722 KB Posted
- Attached to
- IT AND TELECOM- OTHER IT AND TELECOMMUNICATIONS
- Solicitation number
- W52P1J16R0058
About this file
Attachment 0027 ACWS OFFEROR SELF CERTIFICATION
View the file
Other files
Show 40 more
Latest 50 of 97 listed here. See the rest on GovTribe.
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
TAB: Cover Page RFP# W52P1J-16-R-0058
ATTACHMENT 0027
&F
Instructions
| Attachment 0027 OFFEROR SELF CERTIFICATION INSTRUCTIONS: For Worksheet and TABS: "Requirements" and "Interfaces" |
| Per Section L.3.1, Offeror Shall Submit this Attachment 0027 (ALL TABs) as ONE Separate File, NOT as part of or inside Vol I-V. Comment field limited to 500 characters (spaces included), No page limit. Offeror may adjust Comment Cell size to ensure readability of contents. Offeror SHALL NOT change/remove the Cell Protections, SHALL NOT add/delete any Rows, Columns or Worksheets. NOTE: Changes in this Version, 1.01, are in Red Font and Underlined. |
Submit as Filename Format: VendorName_Attch_0027_W52P1J-16-R-0058.xlsx (Replace "VendorName" with same company info as in #1 below.)
| TAB - "Requirements Worksheet": Follow Instructions # 1-6 Below | |
| STEP 1.a: Enter the Offeror information in cells below and on TAB: "Requirements Worksheet": Excel Row 3 & 4, "Prime Company Name" and "Certifying Official". | |
| A. Company Name, Address, CAGE Code | B. Company Certifying Official (Digital Signature) |
| STEP 2: In TAB: "Requirements Worksheet" Row # 10 - 1555, read the ACWS Requirement in Excel Columns A - K (GREEN). For Row 5, "COTS-CWS Product Name and Version #" see below: | |
| Excel Row 5 - ENTER: COTS-CWS Software Product Name and Version # | Enter the name of the COTS-CWS Software Product and Version # proposed to satisfy the requirements in each Row of the Requirements Worksheet. If more than one product is proposed to meet the requirement, list each Product separately. (See Example) |
| STEP 3: For each Excel Row # 10 - 1555, read the ACWS Requirement in Excel Columns A - K (GREEN). Submit the proposed response by Select an "X" in the Columns L-R from the Cell Drop Down Menu in the MOST appropriate Column indicating: "How each requirement is met?" Submit only one "X" per row for Excel Columns L - R (SOO Term Categories A - G (YELLOW)) to indicate how the proposed solution will meet the Requirement either by OOTB, Configuration, Enhancement, Extension, Plug-In/3rd Party Software, or Customization. IF Category "A" is Selected and "Demo = No", a Comment Shall be entered. IF Category "A" is Selected and "Demo = Yes", no Comment shall be entered. IF Category "E" is Selected, provide the product name and comment in the "Comment" Column U. IF Category "G" is Selected a Comment Shall be entered in "Comment" Column U. Use TAB "SOO Terms of Reference" for the definitions. |
| A. Requirement is met Out Of The Box (OOTB) |
| B. Requirement is met through Configuration (Conf) |
| C. Requirement is met through an Enhancement (Enhan) |
| D. Requirement is met through an Extension (Extsn) |
| E. Requirement is met through a Plug-In / 3rd Party Software (Plug/3rd) |
| F. Requirement is met through Customization (Cust) |
| G. Requirement Cannot be Met as Written -- See #4 below. |
| COMPLIANCE CHECK: |
Ensure each Requirement (Excel Rows # 10 - 1555) has one and only one "X" response for Excel Column L - R (Matrix Categories A - G)
| STEP 4: Complete Excel Column S "Enter the ACWS Software Build # for Proposed Capability" following the detailed instructions below. | |
| Enter the ACWS Software Build # for Proposed Capability | Enter the Software "Build" Number as a 1 or 2 digit number (1 - 99) that represents the Offeror's proposed incremental Build for which the requirement will be satisfied. No Letters, Decimals or Special Characters. Notes: 1) Do not simply use the Government's Notional Build Schedule from Figure 3 of the SOO unless the Offeror proposes the same approach and schedule. 2) A "Build" is defined as a Testable and Deployable Software Build under Version Control. 3) This Attachment 0027, must align with the proposed IMS and the narrative portion the Vol I Technical/Risk (e.g. Subfactor 1 - Technical Capabilities). |
STEP 5: Complete Excel Column T "Capability available at Technical Demonstration?".
Select from Drop Down list: Demo = Yes / Demo = No.
Select from Drop Down list: Demo = Yes / Demo = No. Demo = Yes: Available for the Proposal Technical Demonstration - The version of a COTS solution that includes those functions, tasks, business processes, forms, or other operations that are available to the Offeror's Demonstration Team - or - the Government Personnel during the conduct of the Technical Demonstration.
Demo = No: Not available during the conduct of the Technical Demonstration.
| STEP 6. "COMMENT" in Column T: |
| - IF Category "A" is Selected and "Demo = No", a Comment Shall be entered. If Category "A" is Selected and "Demo = Yes", no Comment shall be entered. |
- IF Category "E" is Selected, Then Enter the product name and Comment.
- IF Category "G" is Selected, Then a Comment Shall be entered.
Limited comments to 500 Characters (includes spaces).
COMPLIANCE CHECKS for #3 and #4: Ensure each Excel Row # 10 - 1555 Requirement:
- Has a response for Excel Column S "Enter the ACWS Software Build # for Proposed Capability"
- IF Category "E" is Selected, Enter the product name and Comment.
- IF Category "G" is Selected, Then a Comment Shall be entered.
| TAB - "Interfaces": Follow Instruction Step # 7-9 Below to Complete Columns I - K | |
| STEP 7: Excel Column I - ENTER: Proposed Software Product Name and Version # | |
| ENTER: Proposed Software Product Name and Version # | Enter the Proposed Software Product Name and Version # |
| STEP 8: Excel Column J - Available Out of the Box? | |
| Available Out of the Box? | Select "YES" from the Drop Down Menu if the interface is available out of the box; Otherwise Select "NO". Use TAB "SOO Terms of Reference" definition for OOTB. |
| STEP 9: Excel Column K - Anticipated Level of Effort (LOE) to meet Army requirements (See Definitions Below) | |
| Anticipated Level Of Effort (LOE) to Meet Army Requirements? | Using the Cell Drop Down Menu, select one of the categories of the anticipated level of effort (Easy, Medium, Hard, Substantial - defined below) as the proposed LOE required to develop each interface within the context of the proposed solution. Note: This selection must be consistent with other information in the proposal (e.g. Integrated Master Schedule, Attachment 0015 Staff Levels Skill Matrix, and Attachment 0020 Price Matrix). |
| ACWS defined Level of Effort Definitions | |
| EASY | 0 - 500 Labor Hours |
| MEDIUM | 501 - 1000 Labor Hours |
| HARD | 1001 - 1500 Labor Hours |
| SUBSTANTIAL | 1501+ Labor Hours |
| NOTE: Detailed Interface Requirements can be found in TAB: Interfaces and in Attachment 0005 Requirements Traceability Matrix. | |
| TAB - "Interfaces": Excel Column G (Green) ACWS Assigned Interface Complexity - Definitions | |
| HIGH | High complexity denotes work efforts estimated to involve a significant amount of resources and technical development within the solution; the underlying business process being addressed is complex and critical to enabling end-to-end functionality, will require a significant amount of cross-functional coordination, and involves multiple users and related business processes. High complexity work efforts will require substantial coordination between all stakeholders, PM, and system integrators. |
| MEDIUM | Medium complexity represents a significant work effort but is considerably less time-consuming/intensive than High complexity work; the underlying business process is well understood and does not generally consume a great deal of resources or touch points to other processes or organizations but is still critical to the overall solution. There will be some technical development within the solution and the efforts will require some degree of coordination between stakeholders to finalize and implement. |
| LOW | Low complexity work may require some effort to implement but is generally not considered technically challenging. There might be some effort involved to enable the functionality but it should not require a significant amount of time to complete. The business processes supported by low complexity efforts are generally simple and straightforward and do not represent areas typically requiring a great deal of functional expertise or coordination between stakeholders. |
| STEP 10: Excel Column L - Interface Comments "if needed" | |
| Enter Interface Comments "if needed" | Provide comments "if needed" to explain. Limited to 500 Characters (spaces included). |
TAB: Instructions - ACWS OFFEROR SELF CERTIFICATION Attachment 0027 W52P1J-16-R-0058
TAB Page &P of &N &F
Requirements Worksheet
| Army Contract Writing System (ACWS) | |||||||||||||||||||||
| Offeror Self-Certification Requirements/Build Worksheet | |||||||||||||||||||||
| STEP 1.b: | Company: | ||||||||||||||||||||
| Offeror Certifying Official Name: | |||||||||||||||||||||
| STEP 2: | COTS-CWS Software Product Name & Version # | ||||||||||||||||||||
| Column A | Column B | Column C | Column D | Column E | Column F | Column G | Column H | Column I | Column J | Column K | Column L | Column M | Column N | Column O | Column P | Column Q | Column R | Column S | Column T | Column U | |
| DoD-ID | High Level Obj | ||||||||||||||||||||
| HLO-ID | Business Obj | ||||||||||||||||||||
| BO-ID | BASIC-ID | CAPABILITY-ID | Identifier | Sub Identifier | RTM Level 5 | ||||||||||||||||
| REQUIREMENT-ID | Short Title | Requirement Description | Priority | STEP 3: Select an "X" from the Cell Drop Down Menu in the MOST appropriate Category Column indicating: How is the requirement met? (Only one "X" per row) | STEP 4: Enter the ACWS Software Build # for Proposed Capability. IF Category "G", THEN enter "0". | STEP 5: Capability available at Technical Demonstration? | |||||||||||||||
| (Select from Drop Down list: Demo = Yes / Demo = No) | STEP 6: Enter Product Name and comment for Category "E" |
See Instructions to Enter Comment for Categories "A", "G" (Limit to 500 Characters, spaces included)
| A | ||
| (OOTB) | B | |
| (Conf) | C | |
| (Enhan) | D | |
| (Extsn) | E | |
| (Plug/3rd) | F | |
| (Cust) | G |
(Cannot Be Met As Written) Sample_S-1 Sam-1 B-1 CW CWS 0 0 SAM-1-B-CW Sample-Only This is a sample only. Low X 4 Demo = NO If Category "A" is Selected and "Demo = No", a Comment Shall be entered. If Category "A" is Selected and "Demo = Yes", no Comment shall be entered.
If Category "E" is Selected, provide the product name and commment. IF Category "G" is Selected a Comment Shall be entered.
| 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. | Medium |
| 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. | Medium |
| 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. | Medium |
| 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. | Medium |
| 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. | High |
| 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. | Medium |
| 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. | High |
| 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. | High |
| 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. | High |
| 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. | High |
| 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. | High |
| 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. | High |
| 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. | High |
| 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. | |
| High | ||||||||||
| 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. | High |
| 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 | Medium |
| 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. | Medium |
| 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. | High |
| 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. | High |
| 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. | Low |
| 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. | Low |
| 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. | Low |
| 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. | Low |
| 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. | Medium |
| 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. | Low |
| 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. | Low |
| 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. | High |
| 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. | Low |
| 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. | High |
| 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. | High |
| 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 | Medium |
| 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 | Medium |
| 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 | Medium |
| 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 | Medium |
| 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. | Medium |
| 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.) | Medium |
| 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. | High |
| 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. | High |
| 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. | High |
| 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. | High |
| 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. | High |
| 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. | Low |
| 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 | High |
| 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. | High |
| 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. | Medium |
| 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. | Medium |
| 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. | High |
| 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. | Medium |
| 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. | Medium |
| 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. | High |
| 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. | High |
| 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. | High |
| 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. | High |
| 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. | High |
| 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. | High |
| 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. | High |
| 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. | Low |
| 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. | High |
| 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. | High |
| 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. | High |
| DoDOBJ-3 | ||||||||
| DoDOBJ-6 | HLO-3 | BO-3-1 |
BO-3-2
BO-3-3
| BO-3-4 | IN | CEFMS | 8 | 2 | IN-CEFMS-8-2 | IN-CEFMS-8-2 | When CEFMS sends a message to the system describing a failure to receive or validate an award instrument posted to CEFMS, the system shall receive and route this notification to the originating user. | High |
| DoDOBJ-3 | ||||||||
| DoDOBJ-6 | HLO-3 | BO-3-1 |
BO-3-2
BO-3-3
| BO-3-4 | IN | CEFMS | 9 | 1 | IN-CEFMS-9-1 | IN-CEFMS-9-1 | The system shall enable the user to query the funds distribution status of goods and service in the Corps of Engineers Financial Management System (CEFMS) based upon a basic instrument identifier. | Medium | |||
| DoDOBJ-3 | |||||||||||
| DoDOBJ-6 | HLO-3 | BO-3-3 | |||||||||
| BO-3-4 | IN | CISIL | 1 | 1 | IN-CISIL-1-1 | IN-CISIL-1-1 | The system shall establish an interface with the Central Information System for International Logistics (CISIL). | High | |||
| DoDOBJ-3 | |||||||||||
| DoDOBJ-6 | HLO-3 | BO-3-3 | |||||||||
| BO-3-4 | IN | CISIL | 1 | 2 | IN-CISIL-1-2 | IN-CISIL-1-2 | The system shall receive requirements data from the Central Information System for International Logistics (CISIL) for Foreign Military Sales acquisitions. | High | |||
| DoDOBJ-3 | |||||||||||
| DoDOBJ-6 | HLO-3 | BO-3-3 | |||||||||
| BO-3-4 | IN | CISIL | 2 | 1 | IN-CISIL-2-1 | IN-CISIL-2-1 | The system shall send award data to the Central Information System for International Logistics (CISIL) for Foreign Military Sales acquisitions. | High | |||
| DoDOBJ-3 | |||||||||||
| DoDOBJ-6 | HLO-3 | BO-3-3 | |||||||||
| BO-3-4 | IN | CLSLG | 1 | 1 | IN-CLSLG-1-1 | IN-CLSLG-1-1 | The system shall enable a user to invoke the Clause Logic Web Service provided by Defense Procurement and Acquisition Policy (DPAP) to obtain clauses for each instrument. | High | |||
| DoDOBJ-3 | |||||||||||
| DoDOBJ-6 | HLO-3 | BO-3-3 | |||||||||
| BO-3-4 | IN | CLSLG | 1 | 2 | IN-CLSLG-1-2 | IN-CLSLG-1-2 | The system shall accept text and data clauses associated with each instrument from the Defense Procurement and Acquisition Policy (DPAP) Clause Logic Web Service. | High | |||
| DoDOBJ-1 | HLO-3 | BO-3-3 | |||||||||
| BO-3-4 | IN | CLSLG | 2 | 1 | IN-CLSLG-2-1 | IN-CLSLG-2-1 | The system shall enable a user to add additional clauses via the Defense Procurement and Acquisition Policy (DPAP) clause logic web service to a draft instrument. | High | |||
| DoDOBJ-3 | |||||||||||
| DoDOBJ-6 | HLO-3 | BO-3-3 | |||||||||
| BO-3-4 | IN | CMRA | 1 | 1 | IN-CMRA-1-1 | IN-CMRA-1-1 | The system shall establish an interface with the Contractor Manpower Reporting Application (CMRA) for the purpose of receiving the CMRA status report. | High | |||
| DoDOBJ-3 | HLO-3 | BO-3-3 | |||||||||
| BO-3-4 | IN | COR | 1 | 1 | IN-COR-1-1 | IN-COR-1-1 | The system shall provide the capability to utilize an Department of Defense Contracting Officer Representative (COR) Tool integration/web service to fulfill COR-related requirements. | High | |||
| DoDOBJ-4 | HLO-4 | BO-4 | PP | REQ | 1 | 2 | PP-REQ-1-2 | PP-REQ-1-2 | The system shall have the capability for a user to create distribution lists. | Medium | |
| DoDOBJ-3 | HLO-3 | BO-3-3 | |||||||||
| BO-3-4 | IN | COR | 1 | 2 | IN-COR-1-2 | IN-COR-1-2 | The system shall have the capability to receive notifications that COR Appointee Package is available for review | High | |||
| DoDOBJ-3 | HLO-3 | BO-3-3 | |||||||||
| BO-3-4 | IN | COR | 1 | 3 | IN-COR-1-3 | IN-COR-1-3 | The system shall have the capability to send and store acceptance or rejection of the Appointment and subsequent Appointment Letter. | High | |||
| DoDOBJ-3 | HLO-3 | BO-3-3 | |||||||||
| BO-3-4 | IN | COR | 1 | 4 | IN-COR-1-4 | IN-COR-1-4 | The system shall have the capability to receive COR Acknowledgement of Appointment | High | |||
| DoDOBJ-3 | HLO-3 | BO-3-3 | |||||||||
| BO-3-4 | IN | COR | 1 | 5 | IN-COR-1-5 | IN-COR-1-5 | The system shall have the capability to send and receive QASP File(s) | High | |||
| DoDOBJ-3 | HLO-3 | BO-3-3 | |||||||||
| BO-3-4 | IN | COR | 1 | 6 | IN-COR-1-6 | IN-COR-1-6 | The system shall have the capability to receive and file COR Monthly Reports and other COR files | High | |||
| DoDOBJ-3 | HLO-3 | BO-3-3 | |||||||||
| BO-3-4 | IN | COR | 1 | 7 | IN-COR-1-7 | IN-COR-1-7 | The system shall have the capability to send a Notification of Termination | High | |||
| DoDOBJ-3 | HLO-3 | BO-3-3 | |||||||||
| BO-3-4 | IN | COR | 1 | 8 | IN-COR-1-8 | IN-COR-1-8 | The system shall have the capability to send acceptance or rejection notification of QASP File | High | |||
| DoDOBJ-3 | HLO-3 | BO-3-3 | |||||||||
| BO-3-4 | IN | COR | 4 | 1 | IN-COR-4-1 | IN-COR-4-1 | The system shall provide the capability for a user to track COR appointments against an identified requirement (if initiated prior to award) as well as the resulting award instrument. | High | |||
| DoDOBJ-3 | HLO-3 | BO-3-3 | |||||||||
| BO-3-4 | IN | COR | 5 | 1 | IN-COR-5-1 | IN-COR-5-1 | The system shall provide the capability to correlate COR records to award instruments and keep this information current as workload is shifted from one user to another (including shifts where the users are part of two organizations/associated security group). | High | |||
| DoDOBJ-4 | HLO-4 | BO-4 | PP | REQ | 1 | 1 | PP-REQ-1-1 | PP-REQ-1-1 | The system shall enable the user to notify the requiring activity of formal acceptance or rejection of a requirements package. | Medium | |
| DoDOBJ-4 | HLO-4 | BO-4 | PP | REQ | 2 | 1 | PP-REQ-2-1 | PP-REQ-2-1 | The system shall automatically notify a designated user when an incoming requirements package has not been accepted or rejected after 30 days of receipt. | High | |
| DoDOBJ-4 | HLO-4 | BO-4 | PP | REQ | 3 | 1 | PP-REQ-3-1 | PP-REQ-3-1 | When a user formally accepts a Purchase Request or Purchase Request Amendment, the system shall prompt the user to link the respective Purchase Request to an existing Procurement Action Record or create a new Procurement Action Record. | High | |
| DoDOBJ-4 | HLO-4 | BO-4 | PP | REQ | 3 | 2 | PP-REQ-3-2 | PP-REQ-3-2 | When a user formally accepts a Requirements Package, the system shall prompt the user to link the accepted requirements package to an existing Procurement Action Record or create a new Procurement Action Record. | High | |
| DoDOBJ-3 | HLO-3 | BO-3-3 | |||||||||
| BO-3-4 | IN | COR | 10 | 1 | IN-COR-10-1 | IN-COR-10-1 | The system shall provide the capability to receive ongoing surveillance documentation accomplished by the COR throughout the performance of the contract. This includes but is not limited to Monthly Reports, Trip Reports, CPARS documentation, CMRA documentation, Correspondence Reports, etc. | High | |||
| DoDOBJ-3 | HLO-3 | BO-3-3 | |||||||||
| BO-3-4 | IN | COR | 11 | 1 | IN-COR-11-1 | IN-COR-11-1 | The system shall have the capability to send and receive KO File review checklists and surveillance files. | High | |||
| DoDOBJ-3 | HLO-3 | BO-3-3 | |||||||||
| BO-3-4 | IN | COR | 12 | 1 | IN-COR-12-1 | IN-COR-12-1 | The system shall provide the capability to send or to establish minimum reporting requirements (e.g. Monthly Reports, Final Report) for CORs appointed to an award instrument. | High | |||
| DoDOBJ-4 | HLO-4 | BO-4 | PP | REQ | 4 | 1 | PP-REQ-4-1 | PP-REQ-4-1 | The system shall provide the automated capability to notify the requiring activity of a Purchase Request, Purchase Request Amendment or Requirements Package whenever its status changes. | Medium | |
| DoDOBJ-4 | HLO-4 | BO-4 | PP | REQ | 6 | 1 | PP-REQ-6-1 | PP-REQ-6-1 | When an award instrument associated with a Purchase Request has been signed, the system shall automatically notify the requiring activity. | Medium | |
| DoDOBJ-4 | HLO-4 | BO-4 | PP | REQ | 8 | 1 | PP-REQ-8-1 | PP-REQ-8-1 | When a technical data package and associated files are received from Army Engineering Support Activities (ESA) in a requirements package, the system shall segregate this data for storage according to the distribution restrictions and classification level associated with this data. | High | |
| DoDOBJ-4 | HLO-4 | BO-4 | PP | REQ | 9 | 1 | PP-REQ-9-1 | PP-REQ-9-1 | The system shall have the capability to receive planning & forecasting data and import data from excel spreadsheets (1-N list, project listing, spend plans, suggested milestones etc.) to track and manage procurement planning and forecasts | Medium | |
| DoDOBJ-4 | HLO-4 | BO-4 | PP | REQ | 10 | 1 | PP-REQ-10-1 | PP-REQ-10-1 | The system shall have the capability for a user to establish pre-defined customer oriented notices (status, progress, pending, received, etc.) for an individual document, action or package | Medium | |
| DoDOBJ-3 | HLO-3 | BO-3-3 | |||||||||
| BO-3-4 | IN | COR | 18 | 1 | IN-COR-18-1 | IN-COR-18-1 | The system shall provide the capability for a user to receive, view and track the status of a COR appointment throughout the appointment process. | High | |||
| DoDOBJ-3 | HLO-3 | BO-3-3 | |||||||||
| BO-3-4 | IN | COR | 19 | 1 | IN-COR-19-1 | IN-COR-19-1 | The system shall provide the capability for a user to quickly receive and view the status of all COR processes to identify those activities that require action by the individual user viewing the record. | High | |||
| DoDOBJ-3 | HLO-3 | BO-3-3 | |||||||||
| BO-3-4 | IN | CPARS | 1 | 1 | IN-CPARS-1-1 | IN-CPARS-1-1 | The system shall enable the user to access past performance data contained within the Contractor Performance Assessment Reporting System (CPARS) for reporting purposes. | High | |||
| DoDOBJ-3 | |||||||||||
| DoDOBJ-6 | HLO-3 | BO-3-3 | |||||||||
| BO-3-4 | IN | DAADS | 1 | 1 | IN-DAADS-1-1 | IN-DAADS-1-1 | When an Department of Defense Grants and Agreement Regulations based award instrument has been created, the system shall enable a user to initialize a DD 2566 (Department of Defense Assistance Award Action Report) template. | High | |||
| DoDOBJ-3 | |||||||||||
| DoDOBJ-6 | HLO-3 | BO-3-3 | |||||||||
| BO-3-4 | IN | DAADS | 1 | 2 | IN-DAADS-1-2 | IN-DAADS-1-2 | When a Department of Defense Assistance Award DD 2566 (Department of Defense Assistance Award Action Report) template is initialized, the system shall pre-populate a DD 2566 (Department of Defense Assistance Award Action Report) template based on the instrument data, derived or calculated data and/or business rules. | High | |||
| DoDOBJ-3 | |||||||||||
| DoDOBJ-6 | HLO-3 | BO-3-3 | |||||||||
| BO-3-4 | IN | DAADS | 1 | 3 | IN-DAADS-1-3 | IN-DAADS-1-3 | When the system has pre-populated a DD 2566 (Department of Defense Assistance Award Action Report) template, the system shall enable the user to complete the form. | High | |||
| DoDOBJ-3 | |||||||||||
| DoDOBJ-6 | HLO-3 | BO-3-3 | |||||||||
| BO-3-4 | IN | DAADS | 1 | 4 | IN-DAADS-1-4 | IN-DAADS-1-4 | When the user has completed a draft DD 2566 (Department of Defense Assistance Award Action Report) template, the system shall execute a validation check on the draft report. | High | |||
| DoDOBJ-3 | |||||||||||
| DoDOBJ-6 | HLO-3 | BO-3-3 | |||||||||
| BO-3-4 | IN | DAADS | 1 | 5 | IN-DAADS-1-5 | IN-DAADS-1-5 | When a Department of Defense Assistance Award Action Report has been validated, the system shall enable an authorized user to sign the document. | High | |||
| DoDOBJ-3 | |||||||||||
| DoDOBJ-6 | HLO-3 | BO-3-3 | |||||||||
| BO-3-4 | IN | DAADS | 1 | 6 | IN-DAADS-1-6 | IN-DAADS-1-6 | When the final Department of Defense Assistance Award Action Report has been signed, the system shall automatically send the report data to the Defense Assistance Award Data System (DAADS). | High | |||
| DoDOBJ-3 | |||||||||||
| DoDOBJ-6 | HLO-3 | BO-3-3 | |||||||||
| BO-3-4 | IN | DAADS | 2 | 1 | IN-DAADS-2-1 | IN-DAADS-2-1 | When a finalized DD 2566 has been signed, the system shall store the report data in the Electronic Official File. | High | |||
| DoDOBJ-3 | |||||||||||
| DoDOBJ-6 | HLO-3 | BO-3-3 | |||||||||
| BO-3-4 | IN | DAADS | 2 | 2 | IN-DAADS-2-2 | IN-DAADS-2-2 | When the system has stored a DD 2566 report in the Electronic Official File, the system shall enable the user to assemble the document for printing. | High | |||
| DoDOBJ-3 | |||||||||||
| DoDOBJ-6 | HLO-3 | BO-3-3 | |||||||||
| BO-3-4 | IN | DAMES | 1 | 1 | IN-DAMES-1-1 | IN-DAMES-1-1 | The system shall establish an interface with the Defense Automated Message Exchange System (DAMES). | High | |||
| DoDOBJ-3 | |||||||||||
| DoDOBJ-6 | HLO-3 | BO-3-3 | |||||||||
| BO-3-4 | IN | DAMES | 2 | 1 | IN-DAMES-2-1 | IN-DAMES-2-1 | The system shall receive a formatted message in 80 card column format from the Defense Automated Message Exchange System. | High | |||
| DoDOBJ-3 | |||||||||||
| DoDOBJ-6 | HLO-3 | BO-3-3 | |||||||||
| BO-3-4 | IN | DAMES | 2 | 2 | IN-DAMES-2-2 | IN-DAMES-2-2 | The system shall send a formatted message in 80 card column format to the Defense Automated Message Exchange System. | High | |||
| DoDOBJ-3 | |||||||||||
| DoDOBJ-6 | HLO-3 | BO-3-3 | |||||||||
| BO-3-4 | IN | DAMES | 3 | 2 | IN-DAMES-3-1 | IN-DAMES-3-1 | When a valid message is received from the Defense Automated Message Exchange System (DAMES), the system shall send a message to DAMES confirming successful receipt of the message. | High | |||
| DoDOBJ-3 | |||||||||||
| DoDOBJ-6 | HLO-3 | BO-3-3 | |||||||||
| BO-3-4 | IN | DAMES | 3 | 2 | IN-DAMES-3-2 | IN-DAMES-3-2 | When an invalid message is received from the Defense Automated Message Exchange System (DAMES), the system shall send an error message to DAMES indicating why the message failed validation. | High | |||
| DoDOBJ-3 | |||||||||||
| DoDOBJ-6 | HLO-3 | BO-3-3 | |||||||||
| BO-3-4 | IN | DAMES | 4 | 1 | IN-DAMES-4-1 | IN-DAMES-4-1 | When a message is received from the Defense Automated Message Exchange System (DAMES), the system shall route the incoming message to the owner of the procurement action associated with the identification data included in the message. | High | |||
| DoDOBJ-3 | |||||||||||
| DoDOBJ-6 | HLO-3 | BO-3-3 | |||||||||
| BO-3-4 | IN | DATAWH | 1 | 1 | IN-DATAWH-1-1 | IN-DATAWH-1-1 | The system shall interface with an enterprise procurement data warehouse. | High | |||
| DoDOBJ-3 | |||||||||||
| DoDOBJ-6 | HLO-3 | BO-3-3 | |||||||||
| BO-3-4 | IN | DATAWH | 1 | 2 | IN-DATAWH-1-2 | IN-DATAWH-1-2 | The system shall periodically replicate stored system data in the enterprise procurement data warehouse based on criteria established by an enterprise system administrator. | High | |||
| DoDOBJ-3 | |||||||||||
| DoDOBJ-6 | HLO-3 | BO-3-3 | |||||||||
| BO-3-4 | IN | DATAWH | 2 | 1 | IN-DATAWH-2-1 | IN-DATAWH-2-1 | When a user changes the state of an instrument maintained in the system, the system shall send an update of the instrument data to the enterprise procurement data warehouse. | High | |||
| DoDOBJ-3 | |||||||||||
| DoDOBJ-6 | HLO-3 | BO-3-3 | |||||||||
| BO-3-4 | IN | DATAWH | 2 | 2 | IN-DATAWH-2-2 | IN-DATAWH-2-2 | When a user changes procurement action metadata maintained in the system, the system shall send an update of the procurement action metadata to the enterprise procurement data warehouse. | High | |||
| DoDOBJ-3 | |||||||||||
| DoDOBJ-6 | HLO-3 | BO-3-1 |
BO-3-2
BO-3-3
| BO-3-4 | IN | DEAMS | 1 | 1 | IN-DEAMS-1-1 | IN-DEAMS-1-1 | The system shall establish an interface with the Defense Enterprise Accounting and Management System (DEAMS) for the purpose of exchanging accounting, contracting, and related business data. | High |
| DoDOBJ-3 | ||||||||
| DoDOBJ-6 | HLO-3 | BO-3-1 |
BO-3-2
BO-3-3
| BO-3-4 | IN | DEAMS | 10 | 1 | IN-DEAMS-10-1 | IN-DEAMS-10-1 | The system shall user to enable the user to query the delivery status from the Defense Enterprise Accounting and Management System (DEAMS) based upon a basic instrument identifier. | Medium |
| DoDOBJ-3 | ||||||||
| DoDOBJ-6 | HLO-3 | BO-3-1 |
BO-3-2
BO-3-3
| BO-3-4 | IN | DEAMS | 10 | 2 | IN-DEAMS-10-2 | IN-DEAMS-10-2 | The system shall user to enable the user to query the acceptance status of goods and services from the Defense Enterprise Accounting and Management System (DEAMS) based upon a basic instrument identifier. | Medium |
| DoDOBJ-3 | ||||||||
| DoDOBJ-6 | HLO-3 | BO-3-1 |
BO-3-2
BO-3-3
| BO-3-4 | IN | DEAMS | 11 | 1 | IN-DEAMS-11-1 | IN-DEAMS-11-1 | When the system receives a Purchase Request (PR) Amendment sent by the Defense Enterprise Accounting and Management System (DEAMS), it shall confirm that the Purchase Request has been received and validated by the system. | Medium |
| DoDOBJ-3 | ||||||||
| DoDOBJ-6 | HLO-3 | BO-3-1 |
BO-3-2
BO-3-3
| BO-3-4 | IN | DEAMS | 11 | 2 | IN-DEAMS-11-2 | IN-DEAMS-11-2 | When the system cannot validate a Purchase Request (PR) Amendment received from the Defense Enterprise Accounting and Management System (DEAMS), it shall send a message to GFEBS describing the failure condition. | Medium |
| DoDOBJ-3 | ||||||||
| DoDOBJ-6 | HLO-3 | BO-3-1 |
BO-3-2
BO-3-3
| BO-3-4 | IN | DEAMS | 12 | 1 | IN-DEAMS-12-1 | IN-DEAMS-12-1 | When sending obligation change data to the Defense Enterprise Accounting and Management System (DEAMS), the system shall publish the follow data elements: from amount, to amount, and calculated difference. | Medium |
| DoDOBJ-3 | ||||||||
| DoDOBJ-6 | HLO-3 | BO-3-1 |
BO-3-2
BO-3-3
| BO-3-4 | IN | DEAMS | 13 | 1 | IN-DEAMS-13-1 | IN-DEAMS-13-1 | When interfacing with the Defense Enterprise Accounting and Management System (DEAMS), the system shall use Purchase Request Number, Department of Defense Activity Address Code (DoDAAC) of sending activity, Department of Defense Activity Address Code (DoDAAC) of receiving activity, Procurement Instrument Identification Number, Confirmation of Funds Certification including who, when, associated line item, line of accounting, and amount, Confirmation of Funds Obligation, including who, when, associated line item, line of accounting, and amount as key identifiers. | Medium |
| DoDOBJ-3 | ||||||||
| DoDOBJ-6 | HLO-3 | BO-3-1 |
BO-3-2
BO-3-3
| BO-3-4 | IN | DEAMS | 13 | 2 | IN-DEAMS-13-2 | IN-DEAMS-13-2 | The system shall interface the Defense Enterprise Accounting and Management System (DEAMS) using the following transactions: Receive Purchase Request (PR), Receive Amendments, Send Purchase Request Receipt Acknowledgement, Send Purchase Request Error Acknowledgement, Send Purchase Request Acceptance Notice, Send Purchase Request Rejection Notice, Send Final Funds Validation, Receive Final Funds Validation, Send Award Instrument Data, Send Award Obligation Data, Receive Award Posting Acknowledgement, Receive Award Posting Error Acknowledgement, Send Funds Distribution Data, Receive Funds Distribution Data. | Medium |
| DoDOBJ-3 | ||||||||
| DoDOBJ-6 | HLO-3 | BO-3-1 |
BO-3-2
BO-3-3
| BO-3-4 | IN | DEAMS | 13 | 3 | IN-DEAMS-13-3 | IN-DEAMS-13-3 | The system shall use the following key data fields when interfacing with the Defense Enterprise Accounting and Management System (DEAMS): Purchase Request instrument line item number, Award instrument line item number, Line of Accounting data, Accounting Classification Reference Number (ACRN), line item pricing arrangement, line item descriptive data, line item delivery data, receipt data, acceptance data, payment instructions, disbursement data, dates associated with each action, user information associated with each action, and applicable data elements found in the DPAP Purchase Request Data Standard (PRDS). | Medium |
| DoDOBJ-3 | ||||||||
| DoDOBJ-6 | HLO-3 | BO-3-1 |
BO-3-2
BO-3-3
| BO-3-4 | IN | DEAMS | 2 | 1 | IN-DEAMS-2-1 | IN-DEAMS-2-1 | The system shall receive an incoming Purchase Request (PR) from the Defense Enterprise Accounting and Management System (DEAMS)electronically. | Medium |
| DoDOBJ-3 | ||||||||
| DoDOBJ-6 | HLO-3 | BO-3-1 |
BO-3-2
BO-3-3
| BO-3-4 | IN | DEAMS | 3 | 1 | IN-DEAMS-3-1 | IN-DEAMS-3-1 | When the system receives a Purchase Request (PR) sent by the Defense Enterprise Accounting and Management System (DEAMS) it shall confirm that the Purchase Request has been received and validated by the system. | Medium |
| DoDOBJ-3 | ||||||||
| DoDOBJ-6 | HLO-3 | BO-3-1 |
BO-3-2
BO-3-3
| BO-3-4 | IN | DEAMS | 3 | 2 | IN-DEAMS-3-2 | IN-DEAMS-3-2 | When the system cannot validate a Purchase Request (PR) received from Defense Enterprise Accounting and Management System (DEAMS), it shall send message to the General Funds Enterprise Business System describing the failure condition | Medium |
| DoDOBJ-3 | ||||||||
| DoDOBJ-6 | HLO-3 | BO-3-1 |
BO-3-2
BO-3-3
| BO-3-4 | IN | DEAMS | 4 | 1 | IN-DEAMS-4-1 | IN-DEAMS-4-1 | The system shall route an incoming Defense Enterprise Accounting and Management System (DEAMS)Purchase Request (PR) based upon the identification data contained in the Purchase Request. | Medium |
| DoDOBJ-3 | ||||||||
| DoDOBJ-6 | HLO-3 | BO-3-1 |
BO-3-2
BO-3-3
| BO-3-4 | IN | DEAMS | 5 | 1 | IN-DEAMS-5-1 | IN-DEAMS-5-1 | When an authorized user has accepted or rejected a Purchase Request originated by the Defense Enterprise Accounting and Management System (DEAMS) , the system shall automatically notify the General Funds Enterprise Business System | Medium |
| DoDOBJ-3 | ||||||||
| DoDOBJ-6 | HLO-3 | BO-3-1 |
BO-3-2
BO-3-3
| BO-3-4 | IN | DEAMS | 6 | 1 | IN-DEAMS-6-1 | IN-DEAMS-6-1 | The system shall enable the user to validate funds availability in the Defense Enterprise Accounting and Management System (DEAMS) by submitting a query to the DEAMS prior to finalization of an award instrument in a connected mode.. | Medium |
| DoDOBJ-3 | ||||||||
| DoDOBJ-6 | HLO-3 | BO-3-1 |
BO-3-2
BO-3-3
| BO-3-4 | IN | DEAMS | 7 | 1 | IN-DEAMS-7-1 | IN-DEAMS-7-1 | The system shall send a record of the award data automatically to the Defense Enterprise Accounting and Management System (DEAMS) when the award instrument is electronically signed. | Medium |
| DoDOBJ-3 | ||||||||
| DoDOBJ-6 | HLO-3 | BO-3-1 |
BO-3-2
BO-3-3
| BO-3-4 | IN | DEAMS | 8 | 1 | IN-DEAMS-8-1 | IN-DEAMS-8-1 | When the system sends an award instrument to the Defense Enterprise Accounting and Management System (DEAMS), it shall confirm that the award instrument has been received and validated by the DEAMS. | Medium |
| DoDOBJ-3 | ||||||||
| DoDOBJ-6 | HLO-3 | BO-3-1 |
BO-3-2
BO-3-3
| BO-3-4 | IN | DEAMS | 8 | 2 | IN-DEAMS-8-2 | IN-DEAMS-8-2 | When the Defense Enterprise Accounting and Management System (DEAMS) sends a message to the system describing a failure to receive or validate an award instrument posted to the DEAMS, the system shall receive and route this notification to the originating user. | Medium |
| DoDOBJ-3 | ||||||||
| DoDOBJ-6 | HLO-3 | BO-3-1 |
BO-3-2
BO-3-3
| BO-3-4 | IN | DEAMS | 9 | 1 | IN-DEAMS-9-1 | IN-DEAMS-9-1 | The system shall enable the user to query the funds distribution status of goods and services in the Defense Enterprise Accounting and Management System (DEAMS) based upon a basic instrument identifier. | Medium |
| DoDOBJ-3 | ||||||||
| DoDOBJ-6 | HLO-3 | BO-3-3 | ||||||
| BO-3-4 | IN | DLIS | 1 | 1 | IN-DLIS-1-1 | IN-DLIS-1-1 | The system shall interface with the authoritative entity management system, currently the Department of Defense Address Activity Directory (DoDAAD), as provided by the Defense Logistics Agency's (DLA) Defense Logistics Managements Standards Office (DLMSO) to obtain Address data for Department of Defense Offices. | Medium |
| DoDOBJ-3 | ||||||||
| DoDOBJ-6 | HLO-3 | BO-3-3 | ||||||
| BO-3-4 | IN | DLIS | 2 | 1 | IN-DLIS-2-1 | IN-DLIS-2-1 | The system shall request an update of Department of Defense Activity Address Code (DoDAAC) and associated information from the DLA's source system. | Medium |
| DoDOBJ-3 | ||||||||
| DoDOBJ-6 | HLO-3 | BO-3-3 | ||||||
| BO-3-4 | IN | DLIS | 3 | 1 | IN-DLIS-3-1 | IN-DLIS-3-1 | When the system receives an update of Department of Defense Activity Address Code (DoDAAC) and associated information from DLA's authoritative source system for DoDAACs, it shall automatically populate the system's Department of Defense Activity Address Code (DoDAAC) address tables with the data obtained from DLA. | Medium |
| DoDOBJ-3 | ||||||||
| DoDOBJ-6 | HLO-3 | BO-3-3 | ||||||
| BO-3-4 | IN | DLIS | 4 | 1 | IN-DLIS-4-1 | IN-DLIS-4-1 | When interfacing with DLA's authoritative source system for DoDAACs, the system shall use the Department of Defense Activity Address Code (DoDAAC) as a key identifier. | Medium |
| DoDOBJ-3 | ||||||||
| DoDOBJ-6 | HLO-3 | BO-3-3 | ||||||
| BO-3-4 | IN | DLIS | 4 | 2 | IN-DLIS-4-2 | IN-DLIS-4-2 | The system shall interface with DLA's authoritative source system for DoDAACs using the following transactions: Request Department of Defense Activity Address Code (DoDAAC) .txt file, Receive Department of Defense Activity Address Code (DoDAAC).txt file, Send File Transfer Protocol user name and password. | Medium |
| DoDOBJ-3 | ||||||||
| DoDOBJ-6 | HLO-3 | BO-3-3 | ||||||
| BO-3-4 | IN | DLIS | 4 | 3 | IN-DLIS-4-3 | IN-DLIS-4-3 | The system shall use the following key data fields when interfacing with DLA's authoritative source system for DoDAACs: Office Name, Address. | Medium |
| DoDOBJ-3 | ||||||||
| DoDOBJ-6 | HLO-3 | BO-3-3 | ||||||
| BO-3-4 | IN | DMLSS | 1 | 1 | IN-DMLSS-1-1 | IN-DMLSS-1-1 | The system shall establish an interface with the Defense Medical Logistics Support System (DMLSS) for the purposes of exchanging requirements, accounting, contracting, and related business data. | High |
| DoDOBJ-3 | ||||||||
| DoDOBJ-6 | HLO-3 | BO-3-3 | ||||||
| BO-3-4 | IN | DMLSS | 2 | 1 | IN-DMLSS-2-1 | IN-DMLSS-2-1 | The system shall receive requirements data from the Defense Medical Logistics Support System (DMLSS) for non-Army medical related acquisitions. | High |
| DoDOBJ-3 | ||||||||
| DoDOBJ-6 | HLO-3 | BO-3-3 | ||||||
| BO-3-4 | IN | DMLSS | 3 | 1 | IN-DMLSS-3-1 | IN-DMLSS-3-1 | The system shall send award data to the Defense Medical Logistics Support System (DMLSS) for non-Army medical related acquisitions. | High |
| DoDOBJ-3 | ||||||||
| DoDOBJ-6 | HLO-3 | BO-3-3 | ||||||
| BO-3-4 | IN | DMLSS | 4 | 1 | IN-DMLSS-4-1 | IN-DMLSS-4-1 | The system shall route an incoming Defense Medical Logistics Support System (DMLSS) Purchase Request (PR) based upon the identification data contained in the Purchase Request. | Medium |
| DoDOBJ-3 | ||||||||
| DoDOBJ-6 | HLO-3 | BO-3-3 | ||||||
| BO-3-4 | IN | DMLSS | 5 | 1 | IN-DMLSS-5-1 | IN-DMLSS-5-1 | The system shall enable the user to validate funds availability in the Defense Logistics Support System (DMLSS) by submitting a query to the DMLLS prior to finalization of an award instrument in a connected mode. | High |
| DoDOBJ-3 | HLO-3 | BO-3-3 | ||||||
| BO-3-4 | IN | EDA | 1 | 1 | IN-EDA-1-1 | IN-EDA-1-1 | The system shall enable a user to access data for modifications, orders, and order modifications issued by agencies outside the Army against Basic Instruments issued by the Army using the Defense Procurement and Acquisition Policy (DPAP) Conformed Contract web service once that service becomes available. | Low |
| DoDOBJ-3 | ||||||||
| DoDOBJ-6 | HLO-3 | BO-3-3 | ||||||
| BO-3-4 | IN | EDW | 1 | 1 | IN-EDW-1-1 | IN-EDW-1-1 | The system shall interface with the United States Army Corps of Engineers Enterprise Data Warehouse (EDW). | High |
| DoDOBJ-3 | ||||||||
| DoDOBJ-6 | HLO-3 | BO-3-3 | ||||||
| BO-3-4 | IN | EDW | 2 | 1 | IN-EDW-2-1 | IN-EDW-2-1 | When a user changes the state of an instrument maintained in the system, the system shall send an update of the instrument data to the United States Army Corps of Engineers Enterprise Data Warehouse (EDW). | Medium |
| DoDOBJ-3 | ||||||||
| DoDOBJ-6 | HLO-3 | BO-3-3 | ||||||
| BO-3-4 | IN | EDW | 2 | 2 | IN-EDW-2-2 | IN-EDW-2-2 | When a user changes procurement action metadata maintained in the system, the system shall send an update of the procurement action metadata to the United States Army Corps of Engineers Enterprise Data Warehouse (EDW). | Medium |
| DoDOBJ-3 | ||||||||
| DoDOBJ-6 | HLO-3 | BO-3-3 | ||||||
| BO-3-4 | IN | FBO | 1 | 2 | IN-FBO-1-2 | IN-FBO-7-1 | The system must be able to post a solicitation or combined pre-solicitation/solicitation notice to the Federal Business Opportunities | High |
| DoDOBJ-3 | ||||||||
| DoDOBJ-6 | HLO-3 | BO-3-3 | ||||||
| BO-3-4 | IN | FBO | 3 | 1 | IN-FBO-3-1 | IN-FBO-3-1 | The system must be able to post the solicitation to the Federal Business Opportunities | High |
| DoDOBJ-3 | ||||||||
| DoDOBJ-6 | HLO-3 | BO-3-3 | ||||||
| BO-3-4 | IN | FBO | 4 | 1 | IN-FBO-4-1 | IN-FBO-4-2 | The system must be able to electronically post a J&A for Brand Name Specifications, Other than Full and Open Competition and Limited Sources with a link to the applicable solicitation. | High |
| DoDOBJ-3 | ||||||||
| DoDOBJ-6 | HLO-3 | 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 .