Attachment 16 TACP CASS SW 145 Section L 20120627 DRAFT.pdf

FA8307-12-R-0014 Section L

27 June 2012

FA8307-12-R-0014

Attachment 16

Tactical Air Control Party Modernization (TACP-M)

Close Air Support System (CASS)

Software Version 1.4.5

INSTRUCTIONS TO OFFERORS (ITO)

(SECTION L)

Electronic Systems Center

Airborne Network Division (ESC/HNA)

Hanscom Air Force Base, Massachusetts 01731

DRAFT

This is a draft release intended to solicit comments from potential offerors and is subject to change.

TABLE OF CONTENTS

1 PROGRAM STRUCTURE AND OBJECTIVES

2 GENERAL INSTRUCTIONS

2.1 Point of Contact

2.1.1 Debriefings

2.1.2 Discrepancies

2.1.3 Electronic Reference Documents

2.1.4 Notice of Award Without Discussions

2.1.5 Communications

2.2 Organization/Number of Copies/Page Limits

2.2.1 Page Limitations

2.2.2 Cost or Pricing Information

2.2.3 Classified Information

2.2.4 Cross-Referencing

2.2.5 Indexing

2.2.6 Glossary of Abbreviations and Acronyms

2.2.7 Binding and Labeling

2.3 Electronic Offers

2.4 Distribution

2.5 Cover Letter

3 VOLUME I - EXECUTIVE SUMMARY

3.1 Narrative Summary

3.2 Table of Contents and MCRM

4 VOLUME II - TECHNICAL

4.1 General

4.1.1 Technical Risk

4.1.2 Volume Organization

4.2 Subfactor 1: Human Systems Integration

4.3 Subfactor 2: System Architecture, Interfaces, and Performance

4.4 Subfactor 3: Systems Engineering and Program Management

5 VOLUME III - COST/PRICE

5.1 General

5.1.1 Cost/Price Reasonableness and Realism

5.1.2 Estimating Techniques and Methods

5.1.3 Cost/Price Information

5.1.4 Cost or Pricing Data Requirements

5.1.5 CWBS and CWBS Dictionary

5.1.6 Subcontractor/Interdivisional Transfer Cost Proposals

5.1.7 Rounding

5.2 Volume Organization

5.3 SECTION 1: Cost Proposal Summary

5.3.1 Estimating System

5.3.2 Purchasing System

5.3.3 Accounting System

5.3.3.1 Approved System for Performing Cost Type Contracts

5.3.3.2 Adequate Disclosure Statements

5.3.4 Earned Value Management System

5.3.5 Labor Category Descriptions

5.3.6 Escalation Rates

5.3.7 Person-Month/Person-Hour Conversion

5.4 SECTION 2: Cost/Price Data and Estimating Methodology

5.4.1 Cost Formats

5.4.1.1 CLIN Summary by Contract Type

5.4.1.2 Price by WBS

5.4.1.3 CWBS by GFY by Cost

5.4.1.4 CWBS by GFY by Labor Hours

5.4.1.5 Prime Contractor Rates

5.4.1.6 Bill of Material

5.4.1.7 Price Track

5.4.2 Cost-Plus-Incentive-Fee (CPIF) Arrangement

5.4.3 Basis of Estimate

5.4.3.1 Explanation of Estimating Methods Used

5.4.3.2 Management Reduction

5.4.3.3 Engineering Labor Hours

5.4.3.4 Engineering Labor Hour Skill Mix

5.4.3.5 Person-Loading Schedule

5.4.4 Subcontract Analysis

5.4.5 B-Tables

5.5 SECTION 3: Other Information

5.5.1 Commonality with Other Programs

5.5.2 Probable Subcontractors

5.5.3 Government-Owned Facilities

5.5.4 Government Furnished Property/Information/Supplies/Services

6 VOLUME IV - PAST PERFORMANCE

6.1 General

6.2 Proposal Information

6.3 Relevant Contracts

6.4 Specific Content

6.5 Organizational Structure Change History

7 VOLUME V - CONTRACT DOCUMENTATION

7.1 Model Contract/Representations and Certifications

7.1.1 Section A - Solicitation/Contract Form

7.1.2 Section B - Supplies or Services and Costs/Prices

7.1.3 Section F - Deliveries or Performance

7.1.4 Section G - Contract Administrative Data

7.1.5 Section H - Special Contract Requirements

7.1.6 Section I - Contract Clauses

7.1.7 Section J - Contract Attachments

7.1.8 Section K - Representations, Certifications, & Other Statements of Offerors ...28

7.2 Exceptions to Solicitation Requirements

7.3 Other Information Required

7.3.1 Authorized Offeror Personnel

7.3.2 Government Offices

7.3.3 Company/Division Address, Identifying Codes, & Applicable Designations ...29

7.3.4 Attachments to the Model Contract

7.3.4.1 Attachment 4: DD Form 254

7.3.4.2 Attachments 5 & 6: GFP and Base Support

7.3.4.3 Attachment 7: B-Tables

7.3.4.4 Attachment 9: Small Business Subcontracting Plan

7.3.4.5 Attachment 10: Make or Buy Plan

7.3.4.6 Attachment 11: CWBS and CWBS Dictionary

7.3.4.7 Attachment 12: Technical Data and Software License Mapping

7.3.4.8 Attachment 13: TACP CASS Data Rights Assertion List

7.3.4.9 Attachment 14: Associate Contractor Agreements

7.3.4.10 Attachment 15: OCI Mitigation Plan

ANNEX 1: MASTER CROSS REFERENCE MATRIX

ANNEX 2: CONTRACT WORK BREAKDOWN STRUCTURE

ANNEX 3: COST FORMATS

ANNEX 4: TACP TEST AND TRAINING LOCATIONS

ANNEX 5: PAST PERFORMANCE INFORMATION

ANNEX 6: PAST PERFORMANCE QUESTIONNAIRE

INSTRUCTIONS TO OFFERORS (ITO)

1 PROGRAM STRUCTURE AND OBJECTIVES

The TACP CASS Software v1.4.5 program is part of a U.S. Air Force effort to modernize software for communications and command and control (C2) processing systems for the Air

Support Operations Center (ASOC), Tactical Operation Centers (TOC), mounted operations, and dismounted operations. The TACP CASS Software will provide a standard communication and processing capability for TACP ASOC and TOC operations at the Corps, Division, Brigade, and

Battalion echelons. The TACP CASS Software, hosted on a variety of computers that are integrated with TACP radios, computers, and antennas from the TOCs, a.k.a. Communications and Support (C&S) equipment, provides a complete communication and processing system across the TACP environment.

The CASS Software v1.4.5 development effort will include all system and software engineering and testing to field this next generation of CASS software on multiple platforms (e.g., mounted, dismounted) within the TACP environment. Interim Contractor Support (ICS)/Contractor

Logistics Support (CLS) will be required once the new software version (v1.4.5) is fielded.

The current fielded CASS Software is v1.4.2. CASS Software v1.4.4 was developed by

Rockwell Collins, Poway, CA, and is being fielded starting in October 2012, with ICS for v1.4.4 expected to be provided by Rockwell Collins through September 2015.

2 GENERAL INSTRUCTIONS

This section of the ITO provides general guidance for preparing proposals as well as specific instructions on the format and content of the proposal.

a. The offeror’s proposal must include all data and information requested by the ITO and must be submitted in accordance with these instructions. The offer shall be compliant with the requirements as stated in the Statement of Work (SOW), System Requirements

Document (SRD), Contract Data Requirements List (CDRL), and Model Contract. Non-conformance with the instructions provided in this ITO may result in an unfavorable proposal evaluation.

b. The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The proposal should not simply rephrase or restate the Government’s requirements but rather shall provide convincing rationale to address how the offeror intends to meet these requirements.

Offerors shall assume that the Government has no prior knowledge of their facilities and experience and will base its evaluation on the information presented in the offeror’s proposal.

c. Elaborate brochures or documentation, binding, detailed art work, or other embellishments are unnecessary and are not desired.

d. The proposal acceptance period for this solicitation is stated in Section A of the Model

Contract. The offeror shall make a clear statement in the proposal and Contract

Documentation volume that the proposal is valid through the end of that period.

e. In accordance with FAR Subpart 4.8 (Government Contract Files), the Government will retain one copy of the successful and all unsuccessful proposals. Unless the offeror requests otherwise, the Government will destroy extra copies of such unsuccessful proposals.

2.1 Point of Contact

The Contracting Officer is the sole point of contact for this acquisition. Offerors shall address all questions or concerns regarding this solicitation to the Contracting Officer using the following address:

Ms. Edna C. Alonis

TACP Contracting Officer

ESC/HNAK

5 Eglin Street, Bldg 1624

Hanscom AFB, MA 01731-2100

Phone: (781) 225-4070

E-mail: edna.alonis@hanscom.af.mil

2.1.1 Debriefings

The Contracting Officer will promptly notify offerors of any decision to exclude them from the competitive range, whereupon they may request and receive a debriefing in accordance with

FAR 15.505. The Contracting Officer will notify unsuccessful offerors in the competitive range of the source selection decision in accordance with FAR 15.503(b). Upon such notification, unsuccessful offerors may request and receive a debriefing. Offerors desiring a debriefing must make their request in accordance with the requirements of FAR 15.505 or 15.506, as applicable.

Debriefings will be conducted in accordance with AFFARS 5315.506.

2.1.2 Discrepancies

If an offeror believes that the requirements in these instructions contain an error, omission, or are otherwise unsound, the offeror shall immediately notify the Contracting Officer in writing with supporting rationale.

2.1.3 Electronic Reference Documents

All referenced documents for this solicitation are available on the Federal Business Opportunities

(FedBizOpps) web site at http://www.fedbizopps.gov.

http://www.fedbizopps.gov/

Potential offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to the website for this solicitation. The Government, while trying to ensure document applicability and currency, does not warrant the accuracy or compliance of the information contained in the library’s documents. All documents are subject to revisions and changes without further notice.

2.1.4 Notice of Award Without Discussions

The Government reserves the right to evaluate proposals and make award without discussions.

2.1.5 Communications

Exchanges of source selection information between Government and offerors will be controlled by the Contracting Officer. Email may be used to transmit such information to offerors only if the email can be sent and received encrypted and includes “Source Selection Information – See

FAR 2.101 & 3.104a” in the Subject line. Otherwise, source selection information will be transmitted via US Postal Mail, Fed-Ex or telephone as appropriate.

2.2 Organization/Number of Copies/Page Limits

The offeror shall prepare the proposal as set forth in the Proposal Organization table (Table 2.2 below). The titles and contents of the volumes shall be as defined in this table, all of which shall be within the required page limits and with the number of copies as specified in Table 2.2. The volumes identified in the table shall be separately bound in three-ring, loose-leaf binders. The contents of each proposal volume are described in the ITO paragraph as noted in the table below.

In addition, one (1) hard copy and one (1) electronic copy shall be delivered to the offeror’s cognizant DCMA and Defense Contract Audit Agency (DCAA) offices.

Table 2.2 - Proposal Organization

Volume Volume Title Copies Page Limits

Cover Letter 5x paper

3x CD

1 page

I Executive Summary

(including Master Cross Reference

Matrix)

5x paper

3x CD

Executive Summary: 4 pages

MCRM: No page limit

II Technical

(including HMI Style Guide;

Integrated Master Schedule; and

Appraisal Plan & Appraisal

Disclosure Reports)

5x paper

3x CD

Technical: 30 pages

HMI Style Guide: 20 pages

IMS: 10 pages

AP/ADR: No page limit

III Cost/Price 5x paper

3x CD

No page limit

IV Past Performance 5x paper

3x CD

5 pages per referenced contract

V Contract Documentation 5x paper

3x CD

No page limit file:///C:/Documents%20and%20Settings/PowellRo/far/Far02.doc%23T2101 file:///C:/Documents%20and%20Settings/PowellRo/far/FAR03.DOC%23b3104

2.2.1 Page Limitations

Page limitations shall be treated as maximums. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal and excess paper copies will be returned to the offeror as soon as practicable. If discussions are held, page limitations may be placed on responses to Evaluation Notices (ENs). The specified page limits for EN responses will be identified in the letters forwarding the ENs to the offerors.

a. A page is defined as each face of a sheet of paper containing information. When both sides of a sheet display printed material, it shall be counted as two pages. Page size shall be 8.5 x 11 inches, not including foldouts. Pages shall be typed single space except for the reproduced sections of the solicitation document. The text size shall be no less than

12 point (Times New Roman). Tracking, kerning, and leading values shall not be changed from the default values of the word processing or page layout software. Use at least 1 inch margins on the top and bottom and sides of pages. Pages shall be numbered sequentially by volume. These page format restrictions shall also apply to responses to

ENs. These limitations shall apply to both electronic and hard copy proposals.

b. Legible tables, charts, graphs and figures shall be used wherever practical to depict organizations, systems and layout, implementation schedules, plans, etc. These displays shall be uncomplicated, legible, and shall not exceed 11 by 17 inches in size. Foldout pages shall fold entirely within the volume and will be counted as two (2) pages. Foldout pages may only be used for large tables, charts, graphs, diagrams and schematics not for pages of text. For tables, charts, graphs and figures, the text shall be no smaller than

10 point (Times New Roman or Arial). These limitations shall apply to both electronic and hard copy proposals.

2.2.2 Cost or Pricing Information

All cost or pricing information shall be addressed only in the Cost/Price and Contract

Documentation volumes. Cost trade-off information, work-hour estimates, and material kinds and quantities may be used in other volumes only as appropriate for presenting rationale for alternatives or design and trade-off decisions.

All pricing information shall be addressed in the Contract Documentation volume, i.e., in

Section B of the Schedule and the B-Table attachments (see paragraphs 7.1.2 and 7.3.4.3 for further instructions).

2.2.3 Classified Information

The proposal volumes listed in Table 2.2 shall be unclassified.

2.2.4 Cross-Referencing

To the greatest extent possible, each volume shall be written on a stand-alone basis so that its contents may be evaluated with a minimum of cross referencing to other volumes of the proposal. Information required for proposal evaluation which is not found in its designated volume will be assumed to have been omitted from the proposal.

2.2.5 Indexing

Each volume shall contain a more detailed table of contents to delineate the paragraphs and subparagraphs within that volume. The table of contents does not count against the page limitations. Tab indexing shall be used to identify sections.

2.2.6 Glossary of Abbreviations and Acronyms

Each volume shall contain a glossary of all abbreviations and acronyms used, with an explanation for each. Glossaries do not count against the page limitations for the respective volumes.

2.2.7 Binding and Labeling

Each volume of the proposal should be separately bound in a three-ring, loose leaf binder permitting the volume to lie flat when open. Staples shall not be used. A cover sheet should be bound in each book, clearly marked as to volume number, title, copy number, solicitation identification, and the offeror’s name. The same identifying data should be placed on the spine of each binder. All unclassified document binders shall have a color other than red or other applicable security designation colors. Be sure to apply all appropriate markings including those prescribed in accordance with FAR 52.215-1(e), Restriction on Disclosure and Use of Data, and

FAR 3.104-4, Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection Information. The portions of the proposal listed in Section 7.3.4 shall be included in any contract awarded. They must include a cover page as provided in the model contract and be dated. Each page must be numbered and must contain the solicitation number and the applicable contract document designation (“Attachment 1,” “Exhibit A,” etc.). These documents must not include the offeror’s name, logos, or any other identification. They must also be free of any markings on restriction of data use or disclosure. Include such markings only on separate cover sheets. Offerors are advised that should they be awarded a contract, the data contained in these documents will be part of the contract and no longer entitled to exemption from public release as contractor bid or proposal information.

2.3 Electronic Offers

The content and page size of electronic copies must be identical to the hard copies. For electronic copies, indicate on each CD the volume number and title. Use separate files to permit rapid location of all portions, including subfactors, exhibits, annexes, and attachments, if any.

The offeror shall submit volumes I through V in electronic format, using recordable CDs. Each volume shall be in a different directory/folder on a CD. Special file decompression software shall not be required. The electronic copies of the proposal shall be submitted in a format readable by Microsoft (MS) Office Word 2007, MS Office Excel 2007, MS Office Project 2007, and MS Office PowerPoint 2007, as applicable. In the event that hard copies and electronic copies of a proposal are submitted and if there are any discrepancies between the hard copies and the electronic copies of the proposal, the hard copies will be used for evaluation. The documents file:///C:/Documents%20and%20Settings/PowellRo/far/FAR52.215.doc%23b522151 file:///C:/Documents%20and%20Settings/PowellRo/far/FAR03.DOC%23b31044 identified in paragraph 7.4.1 will be incorporated in any contract awarded and must be submitted in single, stand alone files, and must not include a proprietary marking.

2.4 Distribution

The “original” proposal shall be identified. Proposals shall be addressed to the Contracting

Officer and must be received on the date specified in the RFP to: ESC/HNAK, 5 Eglin St. Bldg

1624, Hanscom AFB, MA 01731-2100, Attn: TACP Contracting Officer. Directions to

Hanscom AFB may be obtained at: http://www.hanscom.af.mil.

Be sure to advise the Administrative Contracting Officer (ACO) and the DCAA for prime and subcontractors that the proposal is “For Official Use Only” and “Source Selection Information--

See FAR 2.101 and FAR 3.104a.”

2.5 Cover Letter

A letter of transmittal or executive cover letter shall be included within the proposal submission.

This letter shall not exceed one (1) page in length. The cover letter shall state that the enclosed proposal is valid for the period stated in Section A of the RFP.

3 VOLUME I - EXECUTIVE SUMMARY

In the executive summary volume, the offeror shall provide the following information:

3.1 Narrative Summary

The narrative summary of the entire proposal should be concise while addressing the significant risks and highlighting any key or unique features, excluding cost/price. The salient features of the summary should tie in with Section M evaluation factors/subfactors. Any summary material presented here shall not be considered as meeting the requirements for any portions of other volumes of the proposal. The Executive Summary shall also identify all subcontractors, joint venture partners and a brief description of their planned roles in the effort. A list of all participating divisions and locations (prime, subcontractors, and joint venture partners) shall be furnished and it shall be indicated whether teaming agreements have been executed or not. An organization chart of the proposed TACP CASS team shall be provided to show all key personnel (offeror, subcontractors, joint venture partners, etc.) and to depict how the offeror’s team fits within the company. The organization chart shall start at the level of the offeror’s Chief

Executive Officer and clearly identify the entire chain of command specifying the name, title, and division name and location. The reporting lines and names, title, division name, and location of personnel responsible for quality assurance shall also be included. Phone numbers for points of contact including the Division’s Vice President (VP), program manager and contracting manager shall be provided. The contact list should also identify those personnel authorized to negotiate on behalf of their company. Furthermore, the list should indicate the person to contact in the event the offeror is awarded a contract (providing, at a minimum, the contact’s title, phone number, fax number, and mailing address).

file:///C:/Documents%20and%20Settings/PowellRo/far/Far02.doc%23T2101 file:///C:/Documents%20and%20Settings/PowellRo/far/FAR03.DOC%23b3104

3.2 Table of Contents and MCRM

Volume I shall include a table of contents and Master Cross Reference Matrix (MCRM) (see

Annex 1), based on paragraph numbering. The MCRM shall show how the proposal relates to the RFP.

4 VOLUME II - TECHNICAL

4.1 General

In the Technical volume, address the proposed approach to meeting all performance and capability requirements identified in the RFP. The Technical volume should be specific and complete. Legibility, clarity, and coherence are very important. Each offeror’s proposal will be evaluated against the Technical subfactors defined in Section M, Evaluation Factors for Award.

Using the instructions provided below, provide as specifically as possible the actual methodology that will be used for accomplishing/satisfying these subfactors. All the requirements specified in the solicitation are mandatory and must be satisfied by the proposed technical solution. Do not merely reiterate or reformulate the requirements specified in the solicitation.

4.1.1 Technical Risk

Address Technical Risk within each subfactor by identifying those aspects of the proposal that are considered to have the potential for disruption of schedule, increased cost, poor performance, the need for increased Government oversight, and/or the likelihood of unsuccessful contract performance. Classify each risk in accordance with the DoD Source Selection Procedures, Table 3, Technical Risk Ratings. Provide the rationale for each risk and its rating, including quantitative estimates of the impact on cost, schedule, and performance. Describe the impact of each identified risk in terms of its potential to interfere with or prevent the successful accomplishment of other contract requirements (for example, SOW or SRD requirements), whether or not those requirements are specifically evaluated as subfactors. Propose realistic solutions or risk mitigations for identified risks that will eliminate or reduce risk to an acceptable level. Identify and classify any new risks introduced by such risk mitigation.

4.1.2 Volume Organization

The Technical volume shall be organized according to the following outline:

1. Table of Contents

2. List of Tables and Drawings

3. Glossary

4. Subfactor 1: Human Systems Integration

5. Subfactor 2: System Architecture, Interfaces, and Performance

6. Subfactor 3: Systems Engineering & Program Management

7. Attachment A: Human Machine Interface (HMI) Style Guide

8. Attachment B: Integrated Master Schedule (IMS)

9. Attachment C: Appraisal Plan and Appraisal Disclosure Reports

4.2 Subfactor 1: Human Systems Integration

The offeror shall describe their overall approach to Human Systems Integration (HSI), including:

a. Summarize key aspects of the proposed HSI Program Plan (including tailoring of

MIL-STD-46855A with supporting rationale) that describe:

1) How user proficiency will be enhanced, to using the v1.4.4 user interface as starting point for evolving the v1.4.5 HMI, and how training and field impacts will be minimized.

2) The approach to establishing and reporting HMI metrics.

3) How user-centered analyses, such as prototyping, task analysis, usability analysis, are employed during the design process.

4) The planned involvement of (and coordination to obtain) end-user personnel (e.g., operators, maintainers, trainers, and support personnel) in assessing the design, operation, maintenance, training, and support of the CASS Software.

5) The approach for performing mission analysis for the ASOC, TOC, and Dismounted users to understand requirements common to each and requirements unique to each to ensure the HMI is effectively tailored for each echelon.

6) The methods by which the offeror will analyze and meet requirements for personnel survivability.

7) The relationship of the offeror’s primary organization elements(s) to its primary HSI organization elements, and the relationships of the HSI organization element(s) to other organization elements responsible for areas affected by HSI, such as systems engineering design, training, and test and evaluation. The composition of the HSI

Working Group (e.g., contractor, subcontractor, and Government HSI domain representatives and user representatives), and its responsibility, authority, and accountability for ensuring compliance with HSI requirements and documenting the

HMI design.

b. Provide an initial Human Machine Interface (HMI) Style Guide addressing standards, best practices, and design guidelines for the HMI that illustrate how CASS Software HMI design elements:

1) Adapt to support multiple echelons, user roles, hardware configurations, and growth for new capabilities.

2) Allow ease and flexibility for the operator to execute the mission.

3) Support timely, correct messaging, including data entry, forms, navigation, help/cues, and error handling/prevention.

4) Allow visibility and ease of response to monitoring and status accounting data for hardware and software interfaces.

5) Provide prompt, current, and visible status information

(e.g., alerts and pop-ups).

6) Provide accessibility and ease of use of geo-rectification and target mensuration.

7) Support ease of operator interaction with ownship, hostile, and friendly track data.

8) Allow ease of manipulation and display of mapping and screen overlays, situational awareness filtering, and off-screen indicators.

9) Permit ease of manual/automated configuration of radios and peripheral hardware.

10) Implement correct, consistent use of battlefield geometry data.

c. Describe how the proposed HSI approach results in increased TACP operational efficiency to include supporting, requesting, and executing close air support (CAS) missions, with reduced operational risks such as delayed or canceled missions, missed attack opportunities, fratricide, loss of aircraft, collateral damage, incorrect target engagement, and lack of massing fires.

4.3 Subfactor 2: System Architecture, Interfaces, and Performance

The offeror shall describe their overall technical solution for system architecture, interfaces, and performance, including:

a. Provide a functional block diagram(s) of the proposed TACP CASS Software depicting all

CSCIs and major components including all interfaces to Communications and Support

(C&S) equipment (radios, antennas, computers, etc.) specified in the SRD, showing how the architecture is modular, flexible, and scalable.

1) Describe how the architecture and each software component comply with industry and Government standards, and identify all vendor-unique extensions to interface standards.

2) Describe how each element of the proposed software architecture adapts to the TACP computing platforms specified in the SRD and is able to integrate with potential future TACP computing platforms.

3) Describe the key aspects of the software architecture that support post-delivery upgrades of the delivered TACP CASS Software v1.4.5, e.g., aircraft operational flight program (OFP) upgrades, without requiring major modifications to existing designs, components, or platform installation.

4) Describe the approach to reducing the risk of technical obsolescence of CASS

Software or dependency on a single source for software components and integration.

b. Define all CASS Software internal and external interfaces (physical, electrical, logical, mechanical, etc.) and identify which interfaces are and are not designed to an open standard.

1) Describe how the proposed design can adapt to future changes to interfaces such as hardware and external messages.

2) Describe the approach to transition non-open internal and external CASS Software interfaces to open internal and external interfaces including rationale for maintaining any non-open interfaces.

c. Present a design that meets the capabilities, functions, integration, performance, and quality requirements in the SRD, with supporting technical analyses and other information that attest to the soundness and maturity of the proposed design.

1) Provide analysis showing how the design meets the reliability, maintainability, and availability requirements for a supportable TACP CASS Software system.

2) Describe the design for fault tolerance that provides for graceful degradation and recovery from failures.

3) Identify the demonstrated maturity level of each of the proposed TACP CASS

Software components in TACP environments, specifically the:

a) Achievement of Net-ready KPP and threshold requirements.

b) Ability to obtain Army Interoperability Certification (AIC).

c) Ability to pass all required Air Force message standards testing and certifications (i.e., AFSIT/AFC2IC).

d) Ability to pass all Joint Interoperability Test and Certification (JITC) requirements for TACP CASS including message standards testing.

e) Mitigation of effects of anticipated OFP changes.

4.4 Subfactor 3: Systems Engineering and Program Management

The offeror shall describe their overall approach to systems engineering and program management, including:

a. Describe the Systems Engineering (including all aspects of Software Engineering) and

Program Management overall approach, organizations (and their capabilities, their responsibilities, and their authorities), methods, models, tools, and processes used for the design, implementation, integration, production, and fielding support for the TACP CASS

Software.

1) Provide an Integrated Master Schedule (IMS) which provides a summary of key program events and a detailed set of tasks and activities that are structured according to the Contract Work Breakdown Structure (CWBS). All tasks/activities in the IMS should be logically linked together showing predecessor/successor relationships. The

IMS tasks/activities shall be directly traceable to the CWBS, SOW, and CDRL. The

IMS shall include a critical path analysis. The tasks identified in the IMS shall be sufficient to demonstrate that the entire program being proposed is executable within the resources and schedule proposed.

2) Describe how the proposed approach supports future upgrades and technology refreshes while minimizing impacts in the field and the support infrastructure.

3) Describe the plans for providing training for TACP users and maintainers, how the training is tailored for TACP echelons, and how the training increases TACP proficiency and mission availability.

4) Provide the Appraisal Plan and full Appraisal Disclosure Report(s) showing the findings for any Software Engineering Institute (SEI) Standard Capability Maturity

Model Integration (CMMI) Assessment Method for Process Improvement (SCAMPI)

A, B, or C assessments conducted for the overarching organization/business unit, as well as for the organization/business unit in which TACP CASS v1.4.5 program will be assigned, within the last three years. The AP and ADRs shall be provided in a separate section in the Technical volume, as specified in Table 2.2. The ADR(s) shall be in accordance with the full SEI SCAMPI requirements and procedures. Provide the plan and schedule for when the offeror’s organization will be executing the TACP

CASS v1.4.5 program at a level of process proficiency commensurate with CMMI-

DEV V1.2 Level 3 or higher (or its equivalent) for all Level 2 and 3 process areas that will be used by the program. If the organization has undergone another type of formal, recognized process implementation assessment within the last three years, provide the formal plans and results as well as information regarding who conducted the assessment, and track the findings to the standard SCAMPI process. If a subcontractor(s) will be developing a product(s) for delivery to the offeror to be integrated with the TACP CASS Software, then ADRs for the subcontractor(s) shall also be provided.

b. Describe the approach to integrating TACP CASS Software onto all mission computers while remaining backwards compatible with legacy TACP CASS Software v1.4.4 and patches, including:

1) Describe the approach to design process management, documentation, system integration facilities, and configuration control in facilitating software interoperability and integration.

2) Describe the processes for coordinating engineering activities between the offeror’s team and the legacy TACP CASS Software ICS teams for incorporating ICS maintenance upgrades and any OFP changes into the CASS Software v1.4.5 baseline.

c. Describe the overall software development processes to be used for TACP CASS

Software v1.4.5, including:

1) Provide estimates of the amount of software to be developed as well as the effort and schedule proposed. Provide the basis for the size estimates, at the lowest level at which they were made. Describe the method(s) by which the effort and schedule were estimated and indicate what specific phases of development are included in the estimates.

2) Describe the plan for developing defect-free software. Include a description of the software development process and the standards followed throughout that process, specifically including those processes (e.g., design reviews and code inspections) that are directed at reducing defects in all software development artifacts. For any proposed software reuse (including unmodified and modified pre-existing software from any source, as well as Commercial Off-the-Shelf (COTS) or Government OTS

(GOTS) software, a full description of the software reuse shall be provided that includes the following:

a) The source(s) of the reused software, its version identification number, when it will be available to the program, and what data rights are provided with the reused software.

b) The offeror’s experience with, or prior use of, the reused software and an assessment by the offeror regarding the specific TACP CASS requirements that can be met by the reused software.

c) An assessment of the results from any testing and operational use to which the reused software has been subjected.

d) The process that will be used to ensure that either there will be no reused code in TACP CASS that is unused by TACP CASS, or that the unused code will not impact the certification, operation, or lifecycle cost of TACP CASS.

e) The quality of the reused software (to include open software defect reports) and what will be done to bring unmodified and modified code and the associated documentation up to the standards that the offeror will use for its own software development.

f) Estimates of the sizes of anticipated design and code modifications, the efforts required for those modifications, and the integration and testing efforts required for all reused software.

3) Describe the software integration approach and how the proposed facilities support the software integration process.

d. Describe the overall test and validation strategy to include what resources are required for verifying that TACP CASS Software requirements are met, including:

1) Describe the approach to evaluation of software system effectiveness, network hardware suitability, interoperability/compatibility (including processing of all current TACP CASS messages in accordance with standards), and integration of

TACP CASS with all TACP platforms, aircraft OFPs, and radios.

2) Describe the contractor test (CT) approach, including HMI tests, interface tests, system-level tests, stress tests, tests for fault tolerance, regression tests, and tests for the full range of current TACP operations.

3) Describe how the proposed TACP CASS Software components meet DoD

Information Assurance Certification and Accreditation Process (DIACAP) requirements, ensuring that the TACP CASS Software components adequately address all information assurance (IA) performance, certification, and accreditation requirements.

e. Describe the approach to providing ICS/Contractor Logistics Support (CLS) that enhances supportability without significantly impacting existing support infrastructure, including:

1) Describe the procedures and resources required for help desk operations.

2) Describe the approach to providing software service packs/patches.

3) Describe the processes and resources required for the proposed field support concept.

f. Map all licenses pertaining to technical data for commercial items or non-commercial items; or commercial and non-commercial computer software; and firmware in

Attachment 12, Technical Data and Software License Mapping, in accordance with paragraph 7.3.4.7. Complete Attachment 13 to the RFP, TACP CASS Data Rights

Assertions List, in accordance with paragraph 7.3.4.8.

g. Provide a Small Business Subcontracting Plan in accordance with paragraph 7.3.4.4.

5 VOLUME III - COST/PRICE

5.1 General

The offeror shall submit a Cost/Price volume that complies with the instructions in this ITO section. The ground rules and assumptions (e.g., contract type, contract items, delivery schedule.

GFE/GFP, etc.) of the prospective contract are provided in the appropriate sections of the RFP.

Any subcontractor that will be responsible for 10 percent or more of the proposed effort must submit separate Cost/Price volumes in accordance with the guidelines given to the prime contractor/offeror below. Compliance with these instructions is mandatory and failure to comply may result in rejection of the proposal.

The Contracting Officer has made a preliminary determination of “Adequate Price Competition.”

Therefore, a Certificate of Current Cost or Pricing Data per FAR 15.403-4 will not be required, and any references to said Certificate or to “PL 87-653” elsewhere in this document are not applicable. In the event that adequate competition does not emerge in response to the solicitation, the Contracting Officer may require current cost or pricing data in accordance with

FAR 15.4.

5.1.1 Cost/Price Reasonableness and Realism

The offeror shall submit data other than certified cost or pricing data that is required to evaluate the reasonableness of the proposed cost/price. Note that unrealistically low or high proposed costs or prices, initially or subsequently, may be grounds for eliminating a proposal from competition either on the basis that the offeror does not understand the requirement or has submitted an unrealistic proposal. Offers should be sufficiently detailed to demonstrate their reasonableness. The burden of proof for credibility of proposed costs/prices rests with the offeror. Additionally, unbalanced pricing poses an unacceptable risk to the Government and may be a reason to reject an offeror’s proposal.

5.1.2 Estimating Techniques and Methods

When responding to the Cost/Price volume requirements in the solicitation, the offeror and associated subcontractors may use any generally accepted estimating technique, including contemporary estimating methods, such as Cost-to-Cost and Cost-to-Non-Cost Estimating

Relationships (CERs), commercially available parametric cost models, in-house developed parametric cost models, etc., to develop their estimates. Estimating techniques and methods must be in accordance with the offeror’s Cost Accounting Standards (CAS) disclosure statement, if applicable. If necessary, reasonable and supportable allocation techniques may be used to spread hours and/or costs to lower levels of the Contract Work Breakdown Structure (CWBS).

The offeror shall identify all ground rules and assumptions used in developing the cost documentation

5.1.3 Cost/Price Information

Information beyond that required by this instruction shall not be submitted, unless it is essential to document or support the offeror’s cost/price position. All information relating to the proposed cost/price, including all required supporting documentation, must be included in the section of the proposal designated as the Cost/Price volume. Under no circumstances shall this data and documentation be included elsewhere in the proposal, except for the required pricing data in the Contract Documentation volume and B-Table attachments.

5.1.4 Cost or Pricing Data Requirements

In accordance with FAR 15.403-1(b) and 15.403-3(a), data other than certified cost or pricing data may be required to support a determination of price reasonableness. Data shall be provided in accordance with FAR 15.403-5. If, after receipt of proposals, the Contracting Officer determines that there is insufficient data available to determine price reasonableness and none of the exceptions in FAR 15.403-1 apply, the offeror shall be required to submit additional cost or pricing data.

5.1.5 CWBS and CWBS Dictionary

The CWBS in Annex 2 shall serve as the framework for organizing the TACP CASS Software v1.4.5 contract. In the Cost/Price volume, the offeror may propose and must specifically identify in the proposal, any adjustments, additions or changes at or above the lowest level defined in

Annex 2 to improve reporting accuracy, consistency, and relevancy. However, the offeror is permitted to expand the CWBS to lower levels of detail at their discretion, when the detail enhances the effectiveness of the CWBS in satisfying program objectives, satisfies critical visibility requirements, and does not overburden the offeror’s management control system. See paragraph 7.3.4.6 for further instructions.

5.1.6 Subcontractor/Interdivisional Transfer Cost Proposals

Separate Cost/Price volumes, including cost formats (Section L Annex 3 Cost Formats.xlsx) for

TACP-M CASS shall be submitted by each major subcontractor and interdivisional transfer

(IDT) (including subsidiaries) that exceeds a dollar threshold of 10 percent of the overall effort.

(Note: If the Basis of Estimate (BOE) for an IDT or subcontractor over the 10 percent dollar threshold are included in the prime’s consolidated BOE, the subcontractor proposal need not include a separate BOE submission as long as there is a one-to-one match between BOEs and the subcontractor proposal.) If a subcontractor considers any portion of cost documentation

“proprietary,” that portion of the documentation shall be submitted under separate cover directly to the Contracting Officer. This documentation must be submitted by the same date and time that the prime contractor’s proposal is due to the Contracting Officer. The prime proposal, however, shall uniquely identify major subcontractor, interdivisional, and other subcontractor labor hours, material prices, and total burdened costs. The prime contractor is responsible for the consistency of the cost data between the prime contractor submission and the subcontractor/ interdivisional submission. The prime contractor shall provide a cost/price evaluation for subcontractors/interdivisional transfer that exceed the dollar threshold of 10 percent. The evaluation must describe the evaluation rationale that leads to the prime’s conclusion that the subcontract price is realistic and reasonable. Any price adjustments to the major subcontractor/ interdivisional submission, and vendor’s and other subcontractor’s proposed prices, that are included in the prime proposal submission, including discounting or expected decreases to be achieved in negotiations, shall be fully identified and explained. All subcontract and vendor costs presented in the prime proposal shall include the prime’s indirect burden (e.g., G&A or handling burden).

5.1.7 Rounding

All dollar amounts provided shall be rounded to the nearest dollar. All loaded labor rates shall be rounded to the nearest penny.

5.2 Volume Organization

The Cost/Price volume shall consist of the following sections:

1. Section 1: Cost Proposal Summary

2. Section 2: Cost/Price Data and Estimating Methodology

3. Section 3: Other Information

5.3 SECTION 1: Cost Proposal Summary

The offeror shall prepare a cost proposal summary that includes an introduction, table of contents, overview, and summary descriptions of estimating, purchasing, and accounting systems; also changes to estimating, accounting practices, or CAS Disclosure Statement.

5.3.1 Estimating System

Provide a summary description of the offeror’s standard estimating system or methods. The summary description shall cover separately each major cost element (e.g., Direct Material, Engineering Labor, Manufacturing Labor, Indirect Costs, Other Direct Costs, Overhead, G&A).

Also, identify any deviations from the standard estimating procedures in preparing this proposal volume. Indicate whether the Government has approved of the estimating system and if so, provide evidence of such approval.

5.3.2 Purchasing System

The offeror shall provide a summary description of its purchasing system and methods (e.g., how material requirements are determined, how sources are selected, when firm quotes are obtained, what provision is made to ensure quantity and other discounts). The offeror shall identify any deviations from its standard procedures in preparing this proposal. Estimating techniques and methods must be in accordance with their CAS disclosure statement. The offeror shall indicate whether the Government has approved the system and, if so, provide evidence of such approval.

5.3.3 Accounting System

Indicate whether the offeror has Government approval of their accounting system and if so, provide evidence of such approval. Also, identify any deviations from the offeror’s standard procedures in preparing this proposal. The offeror shall provide current status of its CAS

Disclosure Statement and explain any inadequacies or non-compliances.

5.3.3.1 Approved System for Performing Cost Type Contracts

The offeror shall provide a current (within 12 months from date of proposal submittal) audit report, finding, or letter from the offeror’s cognizant ACO or DCAA office stating that the offeror’s accounting system has been approved and/or is adequate for cost type contracts. If it has been over 12 months since the accounting system was reviewed, the offeror shall provide a statement that the accounting system has not changed since being reviewed. If the accounting system has changed, a certification shall be provided indicating that the changes have not impacted the approval or adequacy of the accounting system. In accordance with FAR

16.306(c), no cost type contract may be awarded unless the limitations in FAR 16.301-3 are met.

This clause establishes limitations that the contractor’s accounting system be adequate for determining costs. Therefore, no award can be made to an offeror whose accounting system has not been determined to be adequate for cost type contracts. This impacts all team member/subcontractors if the prime anticipates awarding cost type contracts to any of the subcontractors. If no cost type subcontracts are to be awarded, the offeror shall so state. If cost type subcontracts are to be awarded, the offeror shall provide the necessary information from the subcontractors.

5.3.3.2 Adequate Disclosure Statements

The offeror shall provide a current (within 12 months from date of proposal submittal) audit report, finding, or letter from the offeror’s cognizant ACO or DCAA office stating that the offeror’s Disclosure Statement is adequate. In accordance with FAR 30.202-6, a contracting officer shall not award a CAS-covered contract until the cognizant Federal agency official

(CFAO) has made a written determination that a required Disclosure Statement is adequate. This impacts all team member/subcontractors.

5.3.4 Earned Value Management System

Provide a summary description of the offeror’s Earned Value Management (EVM) system and application. Identify any deviations from the offeror’s standard procedures in preparing this proposal. Indicate whether the Defense Contract Management Agency (DCMA) has certified the

EVM system and, if so, provide evidence of such certification. Any outstanding Corrective

Action Requests (CAR) by DCMA shall also be identified.

5.3.5 Labor Category Descriptions

Provide a complete description of all contractor and subcontractor labor rate categories utilized in this proposal. Categories shall include prime and subcontractor rates. The descriptions shall include the types of activities performed under the labor category, duties, level of responsibility, years of experience, and level of education ranges for each category.

5.3.6 Escalation Rates

Identify the escalation rates used for materials, equipment, subcontracts, direct labor, and indirect expenses. Describe the basis of the escalation rates.

5.3.7 Person-Month/Person-Hour Conversion

Identify the person-month to person-hour conversion factors used in preparing the cost proposal.

5.4 SECTION 2: Cost/Price Data and Estimating Methodology

The offeror shall provide the cost/price data and estimating methodology for the offeror’s proposal as described below. See Annex 4 for a list of TACP test and training locations to assist with the travel estimates.

5.4.1 Cost Formats

The offeror shall submit cost formats (see Annex 3) using an electronic format compatible with

Microsoft Excel 2007 (“.xlsx”) containing embedded formulas that provide insight into the build-up of their cost proposal. The cost formats are provided as “Section L Annex 3 Cost

Formats.xlsx.” Offerors may make adjustments to the cost formats (add additional rows or columns to worksheets) if needed to reflect additional cost elements consistent with their accounting/estimating system. The offeror shall not remove or delete rows, columns or worksheets. The offeror shall include in-house, inter-divisional, subcontractor, and associate contractor activities. Below is a description of each section of the Excel file Cost Format.

5.4.1.1 CLIN Summary by Contract Type

This worksheet provides a CLIN summary of the effort broken out by Contract Type by CLIN.

The FFP CLINS 0007, 1009, 1010, 2009, 2010, 3009, 3010, 4009, and 4010 should all be directly inputted into this sheet. For the CPIF CLINs, this worksheet should include formulas that reference the Target Cost, FCCOM, and Target Fee from the CLIN 0001, 0002, 1008, 2008, 3008, and 4008 worksheets.