W15QKN-15-R-0161.pdf

PDF 252 KB Posted

Attached to
Tactical Mission Command Applications (TMCA) Federal contract opportunity
Solicitation number
W15QKN-15-R-0161
Issued by
Department of the Army Materiel Command Contracting Command Picatinny Arsenal

About this file

Solicitation No. W15QKN-15-R-0161

View the file

Other files for this federal contract opportunity

Other files attached to Tactical Mission Command Applications (TMCA), newest first.
File Type Posted
W15QKN-15-R-0161-0006.pdf PDF
W15QKN-15-R-0161-0005.pdf PDF
W15QKN-15-R-0161-0004.pdf PDF
W15QKN15R0161-0003.pdf PDF
W15QKN-15-R-0161-0002.pdf PDF
W15QKN-15-R-0161-0001.pdf PDF
Attachment_0009_-_Non-Disclosure_and_Non-Use_Agreement_(MCS_BCCS_CPOF_SCG).rtf RTF text file
Attachment_0013_-_Disclosure_of_Lobbying_Activities_(SF-LLL).pdf PDF
Attachment_0010_-_Performance_Requirements_Summary_(PRS)_Quality_Assurance_Surveillance_Plan_(QASP).pdf PDF
Exhibit_A_-_Contract_Data_Requirements_List_(CDRLs)_(DD_Form_1423).pdf PDF
Attachment_0012_-_Review_for_Distribution_of_Information_Form_(ARDEC_3002f).pdf PDF
Attachment_0002_-_Price_Factor_Evaluation_Tables.xlsx XLSX spreadsheet
Attachment_0001_-_Labor_Category_Descriptions.pdf PDF
Attachment_0004_-_DoD_Contract_Security_Classification_Specification_(DD_Form_254).pdf PDF
Attachment_0008_-_Technical_Data_Questionnaire_(AMSTA-AR_Form_1350).pdf PDF
Attachment_0011_-_Past_Performance_Questionnaire.docx DOCX document
Attachment_0007_-_Military_Critical_Technologies_Data_Agreement_(DD_Form_2345).pdf PDF
Attachment_0003_-_Travel_and_ODCs_Evaluated_Price.xlsx XLSX spreadsheet
Attachment_0009_-_Non-Disclosure_and_Non-Use_Agreement_(MCS_IPPP).rtf RTF text file
Show all 19

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

SOLICITATION, OFFER AND AWARD 1. This Contract Is A Rated Order Under

DPAS (15 CFR 700)

Rating Page of Pages

2. Contract Number 3. Solicitation Number 4. Type of Solicitation 5. Date Issued 6. Requisition/Purchase Number Sealed Bid (IFB)

Negotiated (RFP)

7. Issued By Code 8. Address Offer To (If Other Than Item 7)

NOTE: In sealed bid solicitations ‘offer’ and ‘offeror’ mean ‘bid’ and ‘bidder’.

SOLICITATION

9. Sealed offers in original and copies for furnishing the supplies or services in the Schedule will be received at the place specified in item 8, or if handcarried, in the depository located in until (hour) local time (Date).

Caution - Late Submissions, Modifications, and Withdrawals: See Section L, Provision No. 52.214-7 or 52.215-1. All offers are subject to all terms and conditions contained in this solicitation.

10. For Information A. Name B. Telephone (No Collect Calls) C. E-mail Address

Call: Area Code Number Ext.

11. Table Of Contents

(X) Sec. Description Page(s) (X) Sec. Description Page(s)

Part I - The Schedule Part II - Contract Clauses A Solicitation/Contract Form I Contract Clauses

B Supplies or Services and Prices/Costs Part III - List Of Documents, Exhibits, And Other Attach.

C Description/Specs./Work Statement J List of Attachments D Packaging and Marking Part IV - Representations And Instructions E Inspection and Acceptance K Representations, Certifications, and F Deliveries or Performance Other Statements of Offerors G Contract Administration Data L Instrs., Conds., and Notices to Offerors H Special Contract Requirements M Evaluation Factors for Award

OFFER (Must be fully completed by offeror) NOTE: Item 12 does not apply if the solicitation includes the provisions at 52.214-16, Minimum Bid Acceptance Period.

12. In compliance with the above, the undersigned agrees, if this offer is accepted within _____ calendar days (60 calendar days unless a different period is inserted by the offeror) from the date for receipt of offers specified above, to furnish any or all items upon which prices are offered at the price set opposite each item, delivered at the designated point(s), within the time specified in the schedule.

13. Discount For Prompt Payment 10 Calendar Days (%) 20 Calendar Days (%) 30 Calendar Days (%) Calendar Days (%) (See Section I, Clause No. 52.232-8)

14. Acknowledgment of Amendments (The offeror acknowledges Amendment No. Date Amendment No. Date receipt of amendments to the SOLICITATION for offerors and related documents numbered and dated):

15A. Name and Code Facility 16. Name and Title of Person Authorized to Sign Offer Address of (Type or Print) Offeror

15B. Telephone Number 15C. Check if Remittance Address is 17. Signature 18. Offer Date Area Code Number Ext. Different From Above – Enter such

Address In Schedule

AWARD (To be completed by Government)

19. Accepted As To Items Numbered 20. Amount 21. Accounting And Appropriation

22. Authority For Using Other Than Full And Open Competition: 23. Submit Invoices To Address Shown In Item

10 U.S.C. 2304(c)( ) 41 U.S.C. 253(c)( ) (4 copies unless otherwise specified)

24. Administered By (If other than Item 7) Code 25. Payment Will Be Made By Code

26. Name of Contracting Officer (Type or Print) 27. United States Of America 28. Award Date

(Signature of Contracting Officer)

IMPORTANT - Award will be made on this Form, or on Standard Form 26, or by other authorized official written notice.

AUTHORIZED FOR LOCAL REPRODUCTION Standard Form 33 (Rev. 9-97) Previous edition is unusable Prescribed By GSA-FAR (48 CFR) 53.214(c)

W15QKN-15-R-0161

X

2015SEP15

2015OCT1503:00pm

DOC9

2015SEP15 SEE SCHEDULE

W15QKN

ARMY CONTRACTING COMMAND - NJ

PICATINNY ARSENAL, NJ 07806-5000

JASON KENLAN

(973)724-9857

ACC-NJ-JA

JASON.A.KENLAN2.CIV@MAIL.MIL

1 98

X 1

X 6 X 12

X 36 X 37

X 38

X 40

X 51

X 74

X 75

X 82

X 93

CONTINUATION SHEET

Reference No. of Document Being Continued Page of

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION A - SUPPLEMENTAL INFORMATION

Buyer Name: JASON KENLAN

Buyer Office Symbol/Telephone Number: ACC-NJ-JA/(973)724-9857

Type of Contract 1: Firm Fixed Price

Kind of Contract: Service Contracts

*** End of Narrative A0000 ***

Executive Summary_________________

The U.S. Army Armament Research, Development and Engineering Center (ARDEC) requires contractor software engineering services in support of Tactical Mission Command Applications (TMCA) including, but not limited to: Command Post of the Future (CPOF), Tactical Applications

(TacApps), Command Web, and other current and future programs relating to Command Post Client (CPC).

The contractor shall provide all personnel, facilities, and materials, except those delineated as Government Furnished Property or

Material (GFP or GFM), necessary to meet the requirements set forth in the Performance Work Statement (PWS). The PWS (and each task order PWS) shall utilize performance-based methods for acquiring services. The contractor shall not perform any requirement unless specified in the PWS.

Contract Strategy, Value, and Period of Performance___________________________________________________

The Government is soliciting this requirement as a full and open competition and anticipates awarding multiple Firm-Fixed-Price (FFP)

Indefinite-Delivery Indefinite-Quantity (IDIQ) contracts with a five (5) year period of performance based upon the proposals that are most advantageous and represent the best value to the Government. The number of contract awards will be based upon the proposals received in response to the solicitation and the amount practical to ensure effective competition on a task order basis. The Government reserves the right to award a single contract should proposal submission identify only one (1) acceptable source. Regardless of the number of contract awards, periodically, at the discretion of the Contracting Officer, market research will be conducted to assess the market for additional capable businesses, in the event additional contractors need to be added to the contract awardee pool.

The total maximum ceiling value of all contracts awarded is $49,000,000.00. The minimum guarantee for each contract awarded is $500.00, which will be obligated under Task Order 0001 at time of base contract award. No disbursement of the minimum guarantee will be made until such time that the contractor has been awarded and successfully completed a task order for services.

The period of performance for each contract awarded shall be:

Ordering Period 1: Twelve (12) months from the date of contract award

Ordering Period 2: Twelve (12) months from the end of Ordering Period 1

Ordering Period 3: Twelve (12) months from the end of Ordering Period 2

Ordering Period 4: Twelve (12) months from the end of Ordering Period 3

Ordering Period 5: Twelve (12) months from the end of Ordering Period 4

Labor Rates___________

The contractor shall propose fully loaded labor rates for all labor categories (defined in Attachment 0001 "Labor Category Definitions") and ordering periods identified in Attachment 0002 "Price Factor Evaluation Tables" of this solicitation. These labor categories and rates will be incorporated into the base contract award and shall be utilized for all task orders. These labor rates are only subject to downward adjustment should contractors choose to submit lower rates when competing for an individual task order. Please note: The labor hours provided in the attachment are for evaluation purposes only and are not to be construed as representing the Government's actual requirements.

Indirect Rates for Travel/Other Direct Costs (ODCs)___________________________________________________

The contractor shall propose indirect rates for travel and ODCs for all ordering periods identified in Attachment 0003 "Travel and ODCs

Evaluated Price" of this solicitation. The indirect rates will be incorporated into the base contract award and shall be utilized for all task orders. These indirect rates are only subject to downward adjustment should contractors choose to submit lower rates when competing for an individual task order. Please note: The travel costs and ODCs provided in the attachment are for evaluation purposes only and are not to be construed as representing the Government's actual requirements.

Security________

The services to be performed under this contract will be at various levels up to and including Secret and require the contractor to gain

2 98

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

access to Picatinny Arsenal, New Jersey and other Government locations, as necessary. Security provisions are identified on Attachment

0004 "DoD Contract Security Classification Specification (DD Form 254)" of this solicitation. Specific security requirements will be identified on a task order basis.

Limited Distribution Data_________________________

The highest Distribution Level for this solicitation/contract is: Distribution Statement D

Attachment 0005 "Maneuver Control System (MCS), Battle Command Common Services (BCCS), and Command Post of the Future (CPOF) Security

Classification Guide (SCG)" dated 29 July 2008 is a Distribution Statement D document, detailed as follows:

Distribution Statement D: Distribution authorized to Department of Defense and U.S. DoD contractors only by specific authority of AR 380-

5. Date of determination is approval date of this document.

The MCS, BCCS, and CPOF SCG contains information exempt from mandatory disclosure under FOIA. Exemption 3 applies.

Export Control Warning: All technical documents that are determined to contain export-controlled technical data shall be marked "WARNING

- This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec 2751, et. seq.)

or the Export Administration Act of 1979, as amended, Title 50, U.S.C., App. 2401 et. seq. Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of DoD Directive 5230.25." When it is technically infeasible to use the entire statement, an abbreviated marking may be used, and a copy of the full statement added to the "Notice To Accompany Release of Export-Controlled Data" required by DoD Directive 5230.25.

Destruction Notice: Destroy by any method that will prevent disclosure of contents or reconstruction of the document.

Attachment 0006 "Maneuver Control System (MCS) Interim Program Protection Plan (IPPP)" dated 21 August 2006 is a For Official Use Only

(FOUO) document.

To obtain a copy of the MCS, BCCS, and CPOF SCG, ARDEC/WSEC Policies, and MCS IPPP: Interested parties to this solicitation shall mail/email a signed and approved copy of Attachment 0007 "Military Critical Technologies Data Agreement (DD Form 2345)" or a copy of their applicable license issued by the U.S. Department of State if the offeror is a non U.S. company, a completed and signed copies of

Attachment 0008 "Technical Data Questionnaire (AMSTA-AR Form 1350)", and a completed and signed copies of Attachment 0009 "Non-

Disclosure and Non-Use Agreement" to:

U.S. Army Contracting Command - New Jersey

ATTN: Christie Vicci

ACC-NJ-JA

Bldg. 9, Phipps Road

Picatinny Arsenal, NJ 07806-5000

Proposal Submission and Evaluation__________________________________

All proposals shall be submitted in accordance with the Instructions, Conditions, and Notices to Offerors section of this solicitation.

No proposals submitted via email or the Army Single Face to Industry (ASFI) website will be accepted. The Government shall evaluate all proposal in accordance with the Evaluation Factors for Award section of this solicitation.

Ordering Procedures___________________

As requirements are identified by the Government, individual task orders will be solicited. Requests for Proposals (RFPs) for each task order will be issued to contractors via email and will provide a description of the requirements, proposal submission instructions, and evaluation procedures. Each contractor shall be provided a fair opportunity to compete for individual task orders exceeding $3,000 in accordance with FAR 16.505(b)(1)(i) unless one of the statutory exceptions stated in FAR 16.505(b)(2)(i) or DFARS 216.505-70(b)(1) apply. Each task order period of performance shall not exceed twelve (12) months.

The Government anticipates utilizing best value tradeoff evaluation procedures for task orders; however, reserves the right to use lowest price technically acceptable evaluation procedures if warranted by task order requirements. Task orders will be competed on a FFP basis and Price will be an evaluation factor. The Government may utilize additional evaluation factors, such as Technical or Past

Performance. Contractors shall propose labor categories and rates in accordance with Attachment 0002 "Price Factor Evaluation Tables" and labor hours necessary to meet task order requirements. If necessary, additional travel and ODCs to meet task order requirements shall be included in the task order proposal. Contractors shall propose indirect rates for travel and ODCs in accordance with Attachment

0003 "Travel and ODCs Evaluated Price". Labor and indirect rates are only subject to downward adjustment should contractors choose to submit lower rates when competing for an individual task order. Detailed evaluation procedures will be provided on a task order basis.

Please note: The Contracting Officer is the only Government representative with the authority to award task orders under this contract.

All task orders will indicate:

3 98

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

1. Date of Task Order

2. Contract Number and Order Number

3. Contract Line Item Number (CLIN) and Description

4. Period of Performance

5. Place of Performance

6. Accounting and Appropriation Data

7. Payment Office

Please also see applicable contract clauses:

DFARS 252.216-7006 Ordering (MAY 2011)

FAR 52.216-19 Ordering Limitations (OCT 1995)

FAR 52.216-22 Indefinite Quantity (OCT 1995)

*** END OF NARRATIVE A0001 ***

Regulatory Cite Title Date Regulatory Cite Title Date _______________ ______________________________________________________________________ ____________ _______________ ______________________________________________________________________ ____________

A-1 52.215-4006 GENERAL INFORMATION TO OFFERORS OR QUOTERS (AS6042) MAR/2012

1. Responses must set forth full, accurate and complete information as required by this solicitation (including attachments). "Fill-ins" are provided on Standard Form 18, Standard Form 33, and other solicitation documents. Examine the entire solicitation carefully.

The penalty for making false statements is prescribed in 18 U.S.C. 1001.

2. Responses must be plainly marked with the Solicitation Number and the date and local time set forth for bid opening or receipt of proposals in the solicitation document.

3. Information regarding the timeliness of response is addressed in the provision of the solicitation entitled either "Late Submission, Modification and Withdrawal of Bid or Instructions to Offerors Competitive Acquisitions".

4. Procurement Information:

_X_ This Procurement is unrestricted

___ This Procurement is ___% set-aside for __________________.

The applicable SIC/NAICS codes are: 541330.

5. Issuing Office:

U.S. Army Contracting Command - New Jersey

ATTN: Jason Kenlan

ACC-NJ-JA

Bldg. 9, Phipps Road

Picatinny Arsenal, NJ 07806-5000

Email: jason.a.kenlan2.civ@mail.mil

6. Additional Information: n/a

7. Point of Contact for Information:

Name: Jason Kenlan

Title: Contract Specialist

Email: jason.a.kenlan2.civ@mail.mil

A-2 52.215-4004 IDENTIFICATION OF WORK PERFORMED AT A GOVERNMENT LOCATION (AS7027) OCT/2010

1. Offeror will specify in his proposal the place(s) of performance of the work.

2. Where the place(s) of performance includes, in whole or part, a Government location, installation, facility, office space, etc. the offeror will:

a. Specify which work will be performed at a Government location and which will be performed at a contractor location.

4 98

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

b. Identify any Government locations, buildings, room numbers, areas etc. where that part of the work will be performed.

c. If a government location is provided under another contract, specify the contract number, PCO, COR or other Government point of contact, etc.

d. If any offeror personnel currently have access to a Government electronic mail account or have in their possession a

Government identification badge, specify all such persons, badge numbers, e-mail accounts, etc.

e. Specify any Government furnished equipment needed to perform the work under this solicitation such as office space, other space, utilities, physical access, e-mail accounts, and the like on which the proposal is based.

f. Separate in the proposal any differing overhead, G&A and other applicable cost or pricing information applicable to the work to be performed at a government location vs. contractor location.

g. If applicable, furnish a copy of any prior or current agreement for the use of such Government location(s).

A-3 52.224-4001 DISCLOSURE OF UNIT PRICE INFORMATION (AS7029) OCT/2010

This constitutes notification pursuant to Executive Order 12600, Pre-Disclosure Notification Procedures for Confidential Commercial

Information (June 23, 1987), of our intention to release unit prices in response to any request under the Freedom of Information Act, 5

USC 552. Unit price is defined as the contract price per unit or item purchased. We consider any objection to be waived unless the contracting officer is notified of your objection to such posting prior to submission of initial proposals.

5 98

PIIN/SIIN

Page of

Name of Offeror or Contractor:

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

Reference No. of Document Being Continued

MOD/AMD

SECTION B - SUPPLIES OR SERVICES AND PRICES/COSTS

0001 MINIMUM ORDERING OBLIGATION $ ___________________________ __________________

SERVICE REQUESTED: MINIMUM ORDERING OBLIGATION

CLIN CONTRACT TYPE:

Firm Fixed Price

The offeror shall not propose a price for CLIN 0001.

The minimum ordering obligation for each contract shall be $500.00, which will be obligated under Task

Order 0001. No disbursement will be made until such time that the contractor has been awarded and successfully completed a task order for services.

(End of narrative B001)

Deliveries or Performance _________________________

0002 LABOR - ORDERING PERIOD 1 $ _________________________ __________________

SERVICE REQUESTED: PSC: R425

CLIN CONTRACT TYPE:

Firm Fixed Price

The contractor shall provide software engineering services in accordance with the requirements of the

Performance Work Statement (PWS).

Labor categories and rates shall be in accordance with Attachment 0001 "Labor Category Definitions" and

Attachment 0002 "Price Factor Evaluation Tables".

(End of narrative B001)

Inspection and Acceptance _________________________

INSPECTION: Destination ACCEPTANCE: Destination

Deliveries or Performance _________________________

0003 LABOR - ORDERING PERIOD 2 $ _________________________ __________________

6 98

Page of

Name of Offeror or Contractor:

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

Reference No. of Document Being Continued

MOD/AMD

SERVICE REQUESTED: PSC: R425

CLIN CONTRACT TYPE:

Firm Fixed Price

The contractor shall provide software engineering services in accordance with the requirements of the

Performance Work Statement (PWS).

Labor categories and rates shall be in accordance with Attachment 0001 "Labor Category Definitions" and

Attachment 0002 "Price Factor Evaluation Tables".

(End of narrative B001)

Inspection and Acceptance _________________________

INSPECTION: Destination ACCEPTANCE: Destination

Deliveries or Performance _________________________

0004 LABOR - ORDERING PERIOD 3 $ __________________________ __________________

SERVICE REQUESTED: PSC: R425

CLIN CONTRACT TYPE:

Firm Fixed Price

The contractor shall provide software engineering services in accordance with the requirements of the

Performance Work Statement (PWS).

Labor categories and rates shall be in accordance with Attachment 0001 "Labor Category Definitions" and

Attachment 0002 "Price Factor Evaluation Tables".

(End of narrative B001)

Inspection and Acceptance _________________________

INSPECTION: Destination ACCEPTANCE: Destination

Deliveries or Performance _________________________

0005 LABOR - ORDERING PERIOD 4 $ _________________________ __________________

SERVICE REQUESTED: PSC: R425

CLIN CONTRACT TYPE:

Firm Fixed Price

7 98

Page of

Name of Offeror or Contractor:

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

Reference No. of Document Being Continued

MOD/AMD

The contractor shall provide software engineering services in accordance with the requirements of the

Performance Work Statement (PWS).

Labor categories and rates shall be in accordance with Attachment 0001 "Labor Category Definitions" and

Attachment 0002 "Price Factor Evaluation Tables".

(End of narrative B001)

Inspection and Acceptance _________________________

INSPECTION: Destination ACCEPTANCE: Destination

Deliveries or Performance _________________________

0006 LABOR - ORDERING PERIOD 5 $ _________________________ __________________

SERVICE REQUESTED: PSC: R425

CLIN CONTRACT TYPE:

Firm Fixed Price

The contractor shall provide software engineering services in accordance with the requirements of the

Performance Work Statement (PWS).

Labor categories and rates shall be in accordance with Attachment 0001 "Labor Category Definitions" and

Attachment 0002 "Price Factor Evaluation Tables".

(End of narrative B001)

Inspection and Acceptance _________________________

INSPECTION: Destination ACCEPTANCE: Destination

Deliveries or Performance _________________________

0007 TRAVEL $ ______ __________________

SERVICE REQUESTED: TRAVEL

CLIN CONTRACT TYPE:

Firm Fixed Price

8 98

Page of

Name of Offeror or Contractor:

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

Reference No. of Document Being Continued

MOD/AMD

The contractor shall travel on a task order basis to meet Performance Work Statement (PWS) requirements.

Travel (indirect rates) shall be in accordance with

Attachment 0003 "Travel and ODCs Evaluated Price".

(End of narrative B001)

Inspection and Acceptance _________________________

INSPECTION: Destination ACCEPTANCE: Destination

Deliveries or Performance _________________________

0008 OTHER DIRECT COSTS (ODCS) $ _________________________ __________________

SERVICE REQUESTED: ODCS

CLIN CONTRACT TYPE:

Firm Fixed Price

The contractor shall provide incidental materials and other direct costs (ODCs) on a task order basis necessary to meet Performance Work Statement (PWS) requirements.

ODCs (indirect rates) shall be in accordance with

Attachment 0003 "Travel and ODCs Evaluated Price".

(End of narrative B001)

Inspection and Acceptance _________________________

INSPECTION: Destination ACCEPTANCE: Destination

Deliveries or Performance _________________________

0009 BASE CLIN FOR CONTRACT DATA REQUIREMENTS LIST _____________________________________________

(CDRLS) _______

The below ELINs are associated with the Data Items on the Contract Data Requirements List (CDRL)(DD Form

1423), in Section J.

(End of narrative A001)

A001 CDRLS $ ** NSP ** _____ __________________

9 98

Page of

Name of Offeror or Contractor:

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

Reference No. of Document Being Continued

MOD/AMD

SERVICE REQUESTED: CDRLS

A001 - Monthly Status, Progress Management Report

A002 - Contractor Roster

A003 - Software Requirements Specification

A004 - System Design Document

A005 - System/Subsystem Design Description

A006 - Failure Analysis

A007 - Interface Control Document

A008 - Software Test Description

A009 - Source Code and Documentation

A010 - Preliminary Design Review

A011 - Critical Design Review

A012 - Tactical Mission Command Application

A013 - 3PDK Software

A014 - Engineering Releases, Patches, Technical

Bulletins

A015 - Software Trouble Report

A016 - User Jury Report

A017 - Miscellaneous Technical Reports

A018 - 3PDK Training Materials

A019 - Program of Instruction

A020 - Field Support Technical Manuals

A021 - Accident/Incident Report

The contractor shall prepare and deliver all data in accordance with the Performance Work Statement (PWS) and requirements set forth in the CDRLs (DD Form

1423).

(End of narrative B001)

Inspection and Acceptance _________________________

INSPECTION: Destination ACCEPTANCE: Destination

Deliveries or Performance _________________________

10 98

Page of

Name of Offeror or Contractor:

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

Reference No. of Document Being Continued

MOD/AMD

0010 CONTRACTOR MANPOWER REPORTING (CMR) $ ___________________________________ __________________

SERVICE REQUESTED: CMR

The contractor shall complete Contractor Manpower

Reporting (CMR) in accordance with the Performance

Work Statement (PWS).

(End of narrative B001)

Inspection and Acceptance _________________________

INSPECTION: Destination ACCEPTANCE: Destination

Deliveries or Performance _________________________

11 98

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION C - DESCRIPTION/SPECIFICATIONS/WORK STATEMENT

PERFORMANCE WORK STATEMENT (PWS)

for

Tactical Mission Command Applications (TMCA)

1. Background

2. Scope

3. Performance Requirements

4. General Information

5. Performance Requirements Summary (PRS) / Quality Assurance Surveillance Plan (QASP)

6. Accounting for Contract Service

7. Security

8. Homeland Security Presidential Directive (HSPD) - 12

1. Background ___________

The US Army Research, Development and Engineering Command (RDECOM), Armament Research Development, and Engineering Center (ARDEC) is responsible for the design, development, and integration of the Tactical Mission Command Applications (TMCA) software applications in support of Army Common Operating Environment (COE), Command Post Computing Environment (CP CE) objectives.

2. Scope _____

The contractor shall provide software and systems engineering lifecycle support including, but not limited to, TMCA design, development, software coding and implementation, and testing activities including unit and systems integration and fielding support. The contractor must provide competent personnel with the appropriate level of education and experience necessary to provide engineering support on the following scope requirements activities.

3. Performance Requirements ________________________

The contractor shall, as required, execute task orders in support of the following management, technical and logistics areas. The following requirements are representative of potential requirements that may be issued in accordance with this PWS paragraph under a specific task order.

3.1 TMCA GENERAL REQUIREMENTS

3.1.1 COLLABORATION

The contractor shall design, develop, and implement system and software improvements that enhance users ability to interact and collaborate within and between echelons of command and across boundaries. This may take the form of collaboration with other systems already present in the Army inventory through the coordination and development of new interfaces. These efforts shall include, but are not limited to:

- Design and implement collaboration solutions that span the dismounted, mounted, command post, garrison, and enterprise domains.

- Design and implement collaboration solutions that degrade gracefully in the presence of disconnected, intermittent, or latent communications.

- Design and implement collaboration solutions that provide "collaboration as a service" between TMCA and other systems.

- Design and implement collaboration solutions that enable collaboration between the TMCA and other thick-client, thin-client, Web-based, mounted, or handheld systems that have been or may be developed by the Government

- Design and implement collaboration enhancements as identified by the Government.

3.1.2 SUPPORT FOR DISPARATE COMMUNICATIONS

The contractor shall design, develop, and implement a capability to operate in a disparate, asynchronous communications environment.

The capability involves not only simultaneously operating across satellite, Mobile Subscriber Equipment (MSE) and tactical Frequency

Modulation (FM) communications, but also supporting new and emerging DoD and Army networks. These efforts shall include, but are not limited to:

12 98

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

- Design and implement the TMCA to be compatible with WIN-T Increments.

- Design and implement the TMCA to support communications in messaging-based environments such as the Lower Tactical Internet.

- In concert with the network capabilities developed by the Government, design and implement TMCA capabilities that make the TMCA system more network-aware and able to report on the current status and configuration of network links.

- Design and implement collaboration solutions that are designed for low-bandwidth tactical networking environments

- Design and implement the TMCA to be compatible with other communications systems and protocols as specified by the Government

3.1.3 SCALABILITY

The contractor shall design, develop and implement system and software architectures that support distributed collaboration, data replication and synchronization, and data distribution among thousands of users in near-real-time. These efforts shall include, but are not limited to:

- Design and implement system and software architectures, software components and software functionality needed to support a robust, massively distributed, real-time collaboration system. The collaboration architecture shall be reliable, minimize bandwidth requirements, be supportable, maximize performance and support security regulations. All software development shall support new and changing requirements to the system and software architectures.

- Design and implement a capability to co-host a Command Post compliant Virtual Machines with a Command Post client in support of a battalion and below configuration. The purpose of this capability is to reduce bandwidth during collaboration between battalion and below units and higher echelons.

- Design and implement robust information filtering capabilities to enable users to declutter or otherwise simplify the information being displayed.

- Design and implement system and architecture enhancements that enable disparate TMCA enclaves to discover and connect with each other with minimal manual assistance.

3.1.4 WEB/THIN-CLIENT CAPABILITY

The following are representative of the task requriments that may be issued in accordance with this PWS paragraph under a specific Task

Order: These efforts shall include, but are not limited to:

- Design and implement a robust, secure application capability to support hundreds of "edge" users simultaneously. "Edge" users are those who do not have access to the Command Post Thick client. The application based capability shall provide secure access to Command

Post data along with the capability to query and map such data. Iterative development shall be based upon new and emerging requirements.

- Design and implement the capability for thin-client users to be able to view briefings conducted in the TMCA CIAS.

- Design, develop, implement and/or manage an "application store" that shall serve as a central repository of thin client applications or widgets for PM Mission Command or other functional domains

- Design and implement widgets and/or thin client applications that extend or interface to the Command Post server infrastructure.

3.1.5 SUPPORTABILITY

The contractor shall incrementally improve the supportability of the TMCA and server components with the objective of minimizing the support staff and support costs necessary to effectively maintain the TMCA in operation. The contractor shall optimize the TMCA to maximize supportability by soldiers. The following are representative of the task requriments that may be issued in accordance with this PWS paragraph under a specific Task Order: These efforts shall include, but are not limited to:

- Design and implement solutions that minimize the length of time and simplify the process required to back-up and maintain the data repository. Solutions should also reduce or remove disruptions to users during scheduled and unscheduled back-ups.

- Design and implement cost-effective solutions to improve the garbage collection process on the data repository. Garbage collection removes unreachable data within the Repository. Viable solutions shall produce efficiencies in the time required to perform necessary garbage collection on the data repository while minimizing hardware requirements. Solutions should also reduce or remove disruptions to the data availability during scheduled and unscheduled garbage collection.

13 98

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

- Automate routine collaboration and application server maintenance tasks, such as repository back-up, repository garbage collection, restoration of back-ups and databridge support.

- Design and implement software solutions that minimize the need for on-site field support.

- Automate the deployment of new software versions, patches, and hot-fixes. Installations and upgrades shall minimize the user actions required successfully complete the installation or upgrade. Maximize use of standard Windows installation programs.

- Provide engineering support for new and emerging requirements that support a smaller logistics footprint and increased system supportability.

- Design and implement software that supports new and emerging requirements that reduce the logistics footprint and/or increase system supportability.

- Design and implement tools that eliminate the need for users or field support engineers to use the "u-form browser" to administer the system.

- Design and implement tools and capabilities that allow for remote administration and maintenance of CIAS enclaves to the greatest extent practicable, including administration and troubleshooting of OCONUS enclaves from CONUS locations.

- Provide an installation that requires minimal user intervention and automates configuration settings, including security settings, to the largest extent possible.

- Provide a start-up capability that minimizes the number of actions a user must take to access all functionality.

- Provide Remote Admin tools that are able to manage both TMCA, CIAS, and other environment capabilities.

- Design and implement diagnostic and prognostic maintenance capabilities.

- Develop other supportability improvements as directed by the Government.

3.1.6 STABILITY

The contractor shall maintain and improve the stability of TMCA to enhance the users experience.

- Design and implement software that has increased fault tolerance for network instability.

- Design and implement functionality to react appropriately to degraded network connectivity.

- Design and implement software that automatically detects incompatible versions of the TMCA application on the network and reacts accordingly.

3.1.7 SERVER INFRASTRUCTURE IMPROVEMENTS

The contractor shall make improvements to the server infrastructure of the TMCA covering the repository, interoperability, data replication, distribution, and synchronization, remote administration and monitoring, and search capabilities.

- Evaluate the advantages of implementing new repository architectures. Specifically evaluate solutions that could enhance query and sorting capabilities and simplify repository maintenance.

- Design and implement a capability to quickly and easily discover data patterns in the TMCA repository.

- Design and implement a capability to discover and create dynamic temporary connections between disparate TMCA enclaves within the same network and/or security domain. These connections shall permit collaboration between enclaves without manual setup/reconfiguration.

- Design and implement a collaboration architecture that shall allow multiple points for data to be ingested into the system. Each echelon shall be able to connect its standard data feeds into the system. Allow the system to accept nonstandard data feeds that are on-the-fly definable into a recognizable schema (such as XML Schema). Allow for system data to be exported from the system at the same echelons for ingestion by other systems.

- Evaluate the benefits and drawbacks of moving away from the current embedded database architecture for the repository.

- Design and implement a system solution that allows both management and merges of multiple, separate repositories to support disconnected operations in theatre.

14 98

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

- Design and implement solutions that maximize the efficient use of server resources in the operation of the TMCA system.

- Other server infrastructure improvements as directed by the Government

3.1.8 HARDWARE CONFIGURATIONS

The contractor shall, based on the operational environment where the TMCA shall operate, provide solutions that allow the TMCA client and/or server software to operate on various hardware platforms (both ruggedized and non-ruggedized), to include, but not be limited to, workstations, laptops, tablets, PDAs, etc.

- Design and implement TMCA and/or server software in the following hardware environments:

- Mounted Battle Command on the Move (MBCOTM)

- Army Airborne Command and Control System (A2C2S)

- 1, 2 or 3 screen display configurations

- tablet configurations

- smartphone configurations

- other mobile or hand-held configurations

- large screen display configurations

- ruggedized hardware configurations

- standalone laptop configurations

- other emerging hardware configurations, including integration with mounted vehicle computing hardware

- Design and implement TMCA and/or server software in the following dismounted/mobile software environments:

- Linux/Unix

- Android

- Apple iOS

- Microsoft Windows (mobile variants)

- Other operating systems as directed by the Government

- Provide heuristics and usability studies to develop a TMCA software/user interface design that provides for effective operation and collaboration on different hardware variants.

- Support touch-screen capabilities on all hardware configurations where touch-screens are provided.

- Support voice recognition and transcription capabilities.

- Support "soft" keyboards and pointing devices where device capabilities permit.

- Support other technologies and/or capabilities that are embedded with available device hardware, including Geospatial Positioning

System (GPS), accelerometers, cameras, microphones, etc.

3.1.9 WIRELESS MAN-PORTABLE OPERATIONS

The contractor shall develop a man-portable version of the TMCA to include, but not limited to:.

- Design and implement a secure, wireless, man-portable TMCA capability that provides real-time collaboration and C2 capabilities.

Based upon heuristics, usability studies and the user feedback process, a subset of TMCA capabilities may be provided via the secure, wireless, man-portable client. System and software design must be IAW with Paragraph 3.2.2.1, "System and Software Design Objectives."

- Develop a TMCA design that provides for effective operation and collaboration in a single screen display.

- Design and implement a wireless, dismounted TMCA capability based upon an approved system and software design. Support new and emerging wireless, man-portable capabilities.

3.1.10 MISSION COMMAND ON-THE-MOVE

The contractor shall develop a system and software design that supports a ruggedized Mission Command on the Move (MCOTM) capability in a variety of potential hardware/vehicle platforms.

- Design and implement secure real-time collaboration and C2 capabilities.

- Integrate TMCA with existing mounted hardware environments and support a more limited screen capability while providing effective operations and collaboration.

15 98

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

- Design and implement a ruggedized MCOTM capability that supports the approved system and software design. Support new and emerging requirements.

3.1.11 DISCONNECTED OPERATIONS

The contractor shall develop and/or enhance the capability for individual TMCA or groups of TMCA to operate while disconnected from the network and/or server environment and effectively reconnect and synchronize all required data. Operational scenarios include (1)

Network outages or hardware failures affecting one or multiple machines (2) Unit Task Re-organization of an individual TMCA or enclave from one TMCA enclave to another.

- Design and implement a TMCA standalone capability. A TMCA standalone capability shall allow an operator to use TMCA command and control capabilities while disconnected from the network. Once network connectivity is re-established, a bi-directional exchange of all relevant data will occur between TMCA clients and the TMCA repository.

- Design and implement the capability for standalone TMCA networks/enclaves to connect to other enclaves and initiate a bi-directional exchange of all relevant data until both networks are fully synchronized.

3.1.12 PLANNING AND REHEARSAL

The contractor shall implement military planning and/or rehearsal capabilities into the TMCA. The following are representative of the task requriments that may be issued in accordance with this PWS paragraph under a specific Task Order:

These efforts shall include, but are not limited to:

- Design and implement a military orders data architecture and solution for the TMCA.

- Design and implement course of action (COA) development capabilities for use by military planners.

- Design and implement wargaming capabilities.

- Design and implement mission rehearsal capabilities.

- Design and implement tools that enable the commander to track actual versus expected progress against an operations plan.

- Design and implement tools that support the Military Decision-Making Process while not locking users into a single way of approaching the "art" of planning.

- Design and implement solutions that provide for change management and tracking of planning and orders products.

- Design and implement solutions that provide the ability to digitally sign and disseminate orders.

- Design and implement solutions that support intelligence preparation of the battlefield.

- Design and implement other military planning and/or rehearsal capabilities as specified by the Government.

3.1.13 DEVELOPMENT KIT AND APIS

TMCA is intended to be a common point for integration of capability across warfighting function domains. To achieve this, the contractor may be required to enhance existing and/or develop (DI-IPSC-81441A) new Developer Kits or Application Programming Interfaces

(APIs) to allow third-party developers to write applications, tools, utilities, etc. for the TMCA infrastructure utilizing the TMCA GUI or server components. The following are representative of the task requriments that may be issued in accordance with this PWS paragraph under a specific Task Order: These efforts shall include, but are not limited to:

- Design, develop, implement, and make available to third party developers, a set of open and standard Application Program Interfaces

(APIs) that would allow for a plug in set of functionality to be developed.

- Design and implement a 3rd Party Development Toolkit (3PDK) that would enable a third party to develop a application "plug in" using the tools provided within the TMCA CIAS client and server, without software code.

- Design and implement the TMCA CIAS data repository to enable third-party developers to extend and/or tailor the base TMCA CIAS data model.

- Design and implement new and/or enhanced interfaces using commercially-open standards and technologies.

16 98

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

- Design and implement new and/or enhanced system capabilities using commercial standards and technologies, minimizing the use of proprietary, custom, or infrequently-used technologies.

- Design and implement APIs and software components that permit non-TMCA and capabilities to collaborate natively with the TMCA through the integration of the developed APIs and/or software components into the non-TMCA systems or capabilities.

- Other development kit and/or API capabilities as directed by the Government

3.1.14 PRIVILEGES AND PERMISSIONS

The contractor shall provide a robust, secure, and user-friendly permissions scheme within the TMCA environment by:

- Design and implement a secure, robust, user permissions scheme that supports both current and new requirements. Designs should provide permission "rules" that are easy for the operator to understand and use.

- Design and implement improved permissions to view data and products in addition to permissions for changing items.

- Design and implement the capability to authenticate users and services against emerging Army technologies/systems for authentication, such as Active Directory, Web Services Security, and Public Key Infrastructure (PKI)

- Design and implement solutions for access to tools, capabilities, and data within the TMCA environment based upon the role of the user logging in.

- Other privileges and permissions improvements as directed by the Government

3.1.15 INFORMATION ASSURANCE

TMCA is a key component of Army Mission Command and must meet applicable DoD and Army security requirements. The following are representative of the task requriments that may be issued in accordance with this PWS paragraph under a specific Task Order: These efforts shall include, but are not limited to:

- Perform a security assessment of the TMCA.

- Design and implement new capabilities that address TMCA security weaknesses.

- Support the government in responding to emerging changes in the platform environment, including but not limited to operating system or other patches, changes to security guidance, and implementation of new security tools.

- Design and implement the ability for the TMCA to take advantage of multiple-level security systems and technologies

- Enhance or modify existing classification and releasability marking capabilities

- Work with the Government to implement a Cross-Domain Guard solution where applicable for TMCA.

- Other information assurance improvements as directed by the Government

3.2 ARCHITECTURE AND SYSTEMS ENGINEERING

3.2.1 SYSTEM ARCHITECTURE

The contractor shall develop a final architecture and system design that will achieve the capabilities set forth in the approved CDD and/or CPD. The final architecture must ultimately comply with the following Government initiatives, i.e. Network Centric Enterprise

Services (NCES), GIG Information Assurance architecture, Net Centric Implementation Documents, and evolving Network Centric Operations and Warfare Reference Model (NCOW RM) versions. The contractor shall monitor these evolving requirements for applicability and conformance. Architecture design trades shall not be made by the contractor which conflict with or degrade the migration to final compliance with these requirements.

The architecture shall consist of the following DoD Architecture Framework (DoDAF) products:

- OV-1, OV-4, OV-5, OV-7, SV-1, SV-2, SV-4, SV-5, SV-6, SV-10c, SV-11

The System Design shall include a conformance analysis to the GIG standards such as:

- NCOW RM, NCES, NCIDS

17 98

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

The contractor shall produce CADM compliant SML architecture products in accordance with the requirements specified in CJCSI 6212.01 D.

The contractor shall integrate the government provided operational views into the TMCA architecture and produce integrated CADM conformant XML architecture products. constituent architecture data elements used to represent the same information are specified in a consistent manner such that architecture data elements defined in one view are the same (i.e. same names, definitions, and values) as architecture data elements referenced in another.

3.2.2 SYSTEM ENGINEERING

The contractor shall perform system engineering activities, to include but not be limited to, system architecture and design;

requirements definition and analysis; interface with external agencies; quantitative and qualitative analysis of system performance and reliability; and support of Army and Joint Interoperability.

The contractor shall provide (DI-IPSC-81435A) detailed system design and engineering support to all other functional areas of contract activity (i.e. software design/development/integration, test, Integrated Logistics Support (ILS), safety, security, etc,), as required, to ensure that program objectives are met.

The contractor shall provide System Engineering services to support Army exercises such as preparing and verifying data loads and post exercise analysis of issues and enhancements to the TMCA. The contractor shall support architecture evaluations by the government through the system lifecycle.

3.2.2.1 System and Software Design Objectives

The following are the system and software design objectives for the TMCA.

a. Throughout TMCA, industry-accepted design objectives for systems and software shall be employed.

b. The system and software design to support network operations must be secure, extensible, responsive, and supportable.

c. System and software designs to support edge users (i.e., web portal) must emphasize performance, flexibility, supportability, security and extensibility.

d. Interfaces must be designed with a focus on maintainability, extensibility, supportability, performance, reuse, and system security.

e. All software shall be designed with an emphasis on reliability, availability, modifiability and supportability.

f. All software shall be designed in such a manner as to minimize or eliminate the usage of proprietary or non-commercial technologies except where specifically directed or authorized by the Government.

g. The system architecture shall be flexible to ensure successful implementation of changing requirements and emerging technologies.

h. The contractor should place a special system engineering emphasis pertaining to the design, integration, interoperability, standardization, use, location and display of all of the data processed by the system.

i. The TMCA shall continue to be a platform for the integration of capabilities developed by other WfFs. Software designs should strive to minimize the impact of changes upon the 3rd-party developers that will use the system.

j. The system should always be designed and implemented to provide maximum backwards compatibility and backwards interoperability.

3.2.2.2 Systems Engineering Deliverables

3.2.2.2.1…

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 .