Attch_0028_ACWS_Offeror_Software_Solution_2016_05_06.xlsx

XLSX spreadsheet 399 KB Posted May 13, 2016

Attached to: IT AND TELECOM- OTHER IT AND TELECOMMUNICATIONS
Solicitation number: W52P1J16R0058
Issued by: Department of the Army Materiel Command Joint Munitions Command

About this file

From the source

Attachment 0028 ACWS OFFEROR SOFTWARE SOLUTION

View the file

Other files

File	Type	Posted
Attch_0029_ACWS_Section_LM_2017_01_23.pdf	PDF	Jan 24, 2017
Attch_0015_ACWS_Staff_Levels_Skill_Mix_Schedule_2017_01_23.xlsx	XLSX spreadsheet	Jan 24, 2017
W52P1J16R0058-0011.pdf	PDF	Jan 24, 2017
Attch_0030_ACWS_RFP_Attachment_List_STATUS_2017_01_23.pdf	PDF	Jan 24, 2017
VendorName_Attch_0032_EN_XRef_FPR_W52P1J-16-R-0058.xlsx	XLSX spreadsheet	Jan 13, 2017
Attch_0015_ACWS_Staff_Levels_Skill_Mix_Schedule_2017_01_11.xlsx	XLSX spreadsheet	Jan 13, 2017
Attch_0029_ACWS_Section_LM_2017_01_11.pdf	PDF	Jan 13, 2017
Attch_0030_ACWS_RFP_Attachment_List_STATUS_2017_01_11.pdf	PDF	Jan 13, 2017
W52P1J16R0058-0010.pdf	PDF	Jan 13, 2017
W52P1J16R0058-0009.pdf	PDF	Nov 23, 2016
Attch_0019_ACWS_CDRL_List_Delivery_Dates_2016_11_18.xlsx	XLSX spreadsheet	Nov 23, 2016
Attch_0020_ACWS_Price_Matrix_2016_11_18.xlsx	XLSX spreadsheet	Nov 23, 2016
Exhibit_A_CDRLS_Acq_Program_Management_2016_11_18.pdf	PDF	Nov 23, 2016
Attch_0021_ACWS_Price_Matrix_2016_11_18.xlsx	XLSX spreadsheet	Nov 23, 2016
Attch_0015_ACWS_Staff_Levels_Skill_Mix_Schedule_2016_09_30.xlsx	XLSX spreadsheet	Nov 8, 2016
Attch_0001_ACWS_Statement_Of_Objectives_2016_09_30.pdf	PDF	Nov 8, 2016
Exhibit_A_CDRLS_Acq_Program_Management_2016_09_30.pdf	PDF	Nov 8, 2016
Attch_0021_ACWS_Additional_Price_Matrix_2016_09_30.xlsx	XLSX spreadsheet	Nov 8, 2016
Attch_0020_ACWS_Price_Matrix_2016_09_30.xlsx	XLSX spreadsheet	Nov 8, 2016
W52P1J16R0058-0008.pdf	PDF	Nov 8, 2016
Attch_0002_ACWS_Task_Order_0001_Statement_Of_Objs_2016_09_30.pdf	PDF	Nov 8, 2016
Attch_0019_ACWS_CDRL_List_Delivery_Dates_2016_09_30.xlsx	XLSX spreadsheet	Nov 8, 2016
W52P1J16R0058-0007.pdf	PDF	Jun 8, 2016
Attch_0021_ACWS_Additional_Price__Matrix_2016_06_08.xlsx	XLSX spreadsheet	Jun 8, 2016
Attch_0020_ACWS_Price__Matrix_2016_06_08.xlsx	XLSX spreadsheet	Jun 8, 2016
W52P1J16R0058-0006.pdf	PDF	Jun 2, 2016
Attch_0020_ACWS_Price__Matrix_2016_05_25.xlsx	XLSX spreadsheet	Jun 2, 2016
Attch_0016_ACWS_Quality_Assurance_Surveillance_Plan_2016_05_31.pdf	PDF	Jun 2, 2016
Attch_0021_ACWS_Additional_Price__Matrix_2016_05_25.xlsx	XLSX spreadsheet	Jun 2, 2016
Attch_0029_ACWS_Section_LM_2016_05_31.pdf	PDF	Jun 2, 2016
Attch_0016_ACWS_Quality_Assurance_Surveillance_Plan_2016_05_20.pdf	PDF	May 20, 2016
W52P1J16R0058-0005.pdf	PDF	May 20, 2016
Attch_0013_ACWS_DISA_SRF_Form_2016_05_20.docx	DOCX document	May 20, 2016
Attch_0029_ACWS_Section_LM_2016_05_20.pdf	PDF	May 20, 2016
Attch_0029_ACWS_Section_LM_2016_05_17.pdf	PDF	May 17, 2016
W52P1J16R0058-0004.pdf	PDF	May 17, 2016
Exhibit_B_CDRLS_Systems_Engineering_Data_2016_05_06.pdf	PDF	May 13, 2016
Attch_0025_ACWS_Cost_and_SW_Data_Rptg_Plan_2016_05_06.xls	XLS spreadsheet	May 13, 2016
Attch_0024_ACWS_Software_License_Disclosure_2016_05_06.xlsx	XLSX spreadsheet	May 13, 2016
Attch_0026_ACWS_Tech_Demo_Logistics_2016_05_06.pdf	PDF	May 13, 2016
Attch_0002_ACWS_Task_Order_0001_Statement_Of_Objs_2016_05_06.pdf	PDF	May 13, 2016
Attch_0029_ACWS_Section_LM_2016_05_06.pdf	PDF	May 13, 2016
Exhibit_A_CDRLS_Acq_Program_Management_2015_05_06.pdf	PDF	May 13, 2016
Attch_0020_ACWS_Price__Matrix_2016_05_06.xlsx	XLSX spreadsheet	May 13, 2016
Attch_0021_ACWS_Additional_Price__Matrix_2016_05_06.xlsx	XLSX spreadsheet	May 13, 2016
Attch_0017_Small_Business_Participation_2016_05_06.xlsx	XLSX spreadsheet	May 13, 2016
Exhibit_D_CDRLS_Operations_Support_2016_05_06.pdf	PDF	May 13, 2016
Attch_0001_ACWS_Statement_Of_Objectives_2016_05_06.pdf	PDF	May 13, 2016
Attch_0019_ACWS_CDRL_List_Delivery_Dates_2016_05_06.xlsx	XLSX spreadsheet	May 13, 2016
Attch_0027_ACWS_Offeror_Self_Certification_RFP_2016_05_06.xlsx	XLSX spreadsheet	May 13, 2016

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

Try for free Login

Text version

The file's text, extracted by GovTribe without its formatting.

Cover

TAB: Cover Page RFP# W52P1J-16-R-0058

ATTACHMENT 0028

Instructions

Attachment 0028 OFFEROR SOFTWARE SOLUTION INSTRUCTIONS: For Worksheet and TAB: "Proposed Solution"

Per Section L.3.1, Offeror Shall Submit this Attachment 0028 (ALL TABs) as ONE Separate File, NOT as part of or inside Vol I-V. Comment field limited to 500 characters (spaces included), 15 Page limit for TAB: "Proposed Solution". Offeror SHALL NOT change/remove the Cell Protections. Expanding the Row Height, and/or adding Rows as needed, with the same format is permitted.

Submit as Filename Format: VendorName_Attch_0028_W52P1J-16-R-0058.xlsx (Replace "VendorName" with same company info as in #1 below.)

INSTRUCTIONS for THIS TAB and TAB: "Proposed Solution" (YELLOW):
1. For this TAB: "Instructions", Enter the Offeror information in the cells below and on TAB "Prposed Solution": Company Name, CAGE Code and Certifying Official Signature.
A. Company Name, Address, CAGE Code	B. Company Certifying Official (Digital Signature)

		2. For TAB (YELLOW): "Proposed Solution" Offeror shall complete Excel Columns A - I by providing the appropriate information regarding the Software Product(s) proposed to meet the requirements of the RFP. Provide additional details if needed in Column I "Comments."
		A. LIST all ACWS "RTM Level 4 CAPABILITY-IDs" met with this Software Product version, separated by a comma (See TAB: "Level 4 Detailed Capabilities")	Read TAB (GREEN): "Level 4 Detailed Capabilities". Select from the Excel Column E (YELLOW) list "RTM Level 4 CAPABILITY-IDs" (i.e. DS, GOV, OBJ, ASN) all the Detailed Capabilities met with this Software Product version. (See Examples 1 & 2)
		B. ENTER: Proposed Software Product Name
(Use a separate Excel Row for each Product)	Enter the name of the Software Product proposed to satisfy the requirements in the Requirements Traceability Matrix (RTM). If a suite of products is proposed, list each Product separately. (See Examples 1 & 2)
		C. ENTER: The Software Product Version # and Release Date is proposed? (Enter: Version Number, Date (MM/YYYY)) (Use a separate Excel Row for each version)	Enter the Software Release Version number and release date of the Software Product which is proposed to satisfy the requirement.
		D. ANSWER: Does this Software Product meet the definition of "COTS-CWS", per the SOO Terms of Reference, and have an Authorization to Operate from a Federal/DoD User? (Enter: YES or Otherwise leave blank)	Enter Yes, or leave blank. IF Yes, then the SOO definition applies.
		E. Enter: WHEN was the Software Product first deployed (approved for Authorization to Operate) for use by a Federal / DoD User?
(Enter: MM/YYYY - MM/YYYY, MM/YYYY - Present, or "Future Release")	Enter the dates when the COTS product was used in the past or if it is still being used presently. Use this format: MM/YYYY - MM/YYYY, MM/YYYY - Present, or enter "Future Release".
		F. ENTER: WHERE is or was the Software Product deployed? (Federal/DoD Organization HQ and Location that issued the Authorization to Operate). IF the software version will be first deployed to ACWS or another Organization in the future, Leave BLANK.	Enter the Name or Abbreviations for the (the customer organization HQ) and City, State where the Software Product received an Authorization to Operate for current or past use. (e.g. DHS HQ, Washington, DC; AMC HQ, Huntsville, AL)
		G. ANSWER (YES / Blank): WILL the Software Product Version be first deployed (Initial Authorization to Operate) with the ACWS program? (Enter: YES or Otherwise leave blank)	Enter: Yes or leave blank. Do not enter any other information.
		H. ENTER: HOW MANY licensed users are or were at the deployed location(s)? (by location) IF the software version will be first deployed to ACWS, THEN Leave BLANK.	Enter the number of individual (licensed) users that were/are at the location (Enter location/customer organization = # of Users Licensed). (e.g. DHS HQ = 2450, AMC HQ = 200)
		I. ENTER: Comment for A - H, if needed (Limit of 500 Characters, including spaces)	Only provide comments needed to explain a response or Future Release Example comment to explain a response.
		3. COMPLIANCE Check:

1) All of the TAB (GREEN): "Level 4 Detailed Capabilities", Excel Rows 2 - 54, Column E, "RTM Level 4 CAPABILITY-IDs", shall be allocated to one or more Software Products listed on TAB (YELLOW) "Proposed Solution", Column A.

2) All of the TAB (YELLOW): "Proposed Solution" Column B, "Proposed Software Product Name" listed shall be associated with a License in Attachment 0024 Software License Disclosure.

TAB: Instructions - ACWS Offeror Software Solution RFP# W52P1J-16-R-0058

&P of &N &F

Proposed Solution Army Contract Writing System (ACWS) Proposed Software Solution

	Offeror Company Name:
	Offeror Certifying Official Name:
	Column A	Column B	Column C	Column D	Column E	Column F	Column G	Column H	Column I
	LIST all ACWS "RTM Level 4 CAPABILITY-IDs" met with this Software Product version, separated by a comma (See TAB: "Level 4 Detailed Capabilities", Excel Column E)	ENTER: Proposed Software Product Name
(Use a separate Excel Row for each Product)	ENTER: The Software Product Version # and Release Date is proposed? (Enter: Version Number, Date (MM/YYYY)) (Use a separate Excel Row for each version)	ANSWER : Does this Software Product meet the definition of "COTS-CWS", per the SOO Terms of Reference? (YES / Blank)	ENTER: WHEN was the Software Product first deployed (approved for Authorization to Operate) for use by a Federal / DoD User?
(Enter: MM/YYYY - MM/YYYY, MM/YYYY - Present, or "Future Release")	ENTER: WHERE is or was the Software Product deployed? (Federal/DoD Organization HQ and Location that issued the Authorization to Operate). IF the software version will be first deployed to ACWS or another Organization in the future, THEN ENTER "FIRST - Federal/DoD Organization HQ".	ANSWER (YES / Blank): WILL the Software Product Version be first deployed (Initial Authorization to Operate) with the ACWS program? (Enter: YES or Otherwise leave blank)	ENTER: HOW MANY licensed users are or were at the deployed location(s)? (by location) IF the software version will be first deployed to ACWS, THEN Leave BLANK.	ENTER: Comment for A - H if needed (Limit of 500 Characters, including spaces)
	GOV, DS, OBJ, ASN, EXC, FIL, PDA	Example 1: Sample_CWS-COTS_Software	ABC_15.01 (10/2014)	YES	10/2012 - Present	DHS HQ, Washington, DC
AMC HQ, Huntsville, AL		DHS HQ = 2450
AMC HQ = 200	Only comments needed to explain a response.
	DS, ADM, BIN, CLO	Example 2: NewSample_COTS_Software	DEFG_1.0 (11/2019)		Future Release	FIRST - DHS HQ, Washington, DC	YES		Future Release Example comment to explain a response.

TAB: Proposed Solution - ACWS Offeror Software RFP# W52P1J-16-R-0058

&P of &N &F

Level 4 Detailed Capabilities

	DoD-ID	HLO-ID	BO-ID	BASIC-ID	RTM Level 4
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

	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 Cure Notices FOIA Requests Performance Reporting Termination Procedures ULO Management Issue Letter of Auth / TBC

	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) Congressional Notifications

	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

	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.	Cure 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

	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

	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

	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

	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

	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

	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

	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

	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

	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

	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 echeloen.	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

TAB: ACWS Detailed Capabilities - Level 4 RFP# W52P1J-16-R-0058

&P of &N &F

SOO Terms of Reference

TAB: SOO Terms of Reference RFP# W52P1J-16-R-0058

&P of &N &F image1.png

Microsoft_Word_Document1.docx Attachment 0001 ACWS Statement of Objectives (Excerpt).

2.2. Terms of Reference

The following terms are defined to ensure consistency in context. The definitions here shall take precedence over the content in the Requirements Traceability Matrix (Attachment 0004) or any other Request for Proposal (RFP) attachment. The RTM was approved 4 November 2015, and the definitions below were refined after that date.

· Commercially Available Off-the-Shelf Contract Writing System (COTS-CWS) – A commercially available software application, or product, whose core competency (out of the box) is to generate and issue FAR-based contracting actions (awards, orders, or modifications).

· Out Of The Box (OOTB) – The released version of a COTS solution that includes those functions, capabilities, tasks, business processes, forms, or other operations that are available to any authorized user upon installation and initial setup of the hardware and software.

· Configuration – Any change within the defined set of COTS product parameters which the user can set and does not result in customization of the COTS product.

Software configuration typically:

· Enables or disables functionality that is readily available in the COTS product;

· Includes the initial setup of a large system (e.g., install parameters, data-element names, functional security model, User Interface (UI) modification, settings, processes);

· Includes the use of available menus and/or wizards to set the parameters that determine the workflow; and

· Is not lost with a version upgrade of the COT product.

· Enhancement: Capability that results from changes to the core code of a COTS product in order to improve existing functionality that cannot otherwise be accomplished through configuration or modification. Enhancements are expected to be included in future releases of the COTS product. Enhancements are anticipated to be system upgrades necessary to ensure continued alignment, improvement, and standardization of end-to-end contracting processes and maturation of infrastructure to handle the large transaction volume and data demands. This may include application version upgrades, automation of manual business process steps, automated access to additional data required for report completeness, major updates to meet changes in compliance requirements, and infrastructure modernization to address additional users, system scalability, technology refresh, prevailing industry standards, and emerging technologies.

· Extension – Software code that provides additional functionality in the ACWS solution without disturbing the core software code. It may include additional interfaces, automation of additional contract writing/administration processes, and new data fields. Does not require a secondary license.

· Plug-In / 3rd Party – A software component that provides capability that cannot be inherently accomplished by the core COTS solution, and which requires a secondary license. This component will be installed or integrated with the existing COTS product(s) and should not require changes to the core code of the existing COTS product(s). It may include additional interfaces, automation of additional contract writing/administration processes, and new data fields. Once installed/integrated, the operations should seamlessly execute and be unnoticeable to the user.

· Customization – Any software development work to change or extend the functionality of a COTS product, resulting in changes to the core code of the COTS product that may or may not be incorporated as enduring functionality within the COTS baseline.

Software customization may be used to create reports, interfaces, conversion objects, extensions, forms, or other capability to satisfy requirements specific to the Army that could not otherwise be implemented by the configuration process. Customization of the COTS product requires a detailed understanding of the COTS implementation and data schemas in order to develop new or change existing functionality of the product.

image2.emf

File details come from the government source that posted it. Updated Nov 14, 2017.