RFP M00264-22-R-0003-Amendment 0001.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83)

Prescribed by GSA

FAR (48 CFR) 53.243

The purpose of this amendment 0001 is to:

1) Provide answ ers to vendors questions;

2) Revised section 5.0 of the PWS; and

3)-Revised Addendum 52.212-1.

All other terms and conditions remain unchanged.

1. CONTRACT ID CODE PAGE OF PAGES

S 1 16

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 15-Feb-2022

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X M0026422R0003

X 9B. DATED (SEE ITEM 11)

01-Feb-2022

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, X is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE

RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

15-Feb-2022

CODE

MCINCR - RCO

2010 HENDERSON RD

EILEEN RIVERA

QUANTICO VA 22134

M00264 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

M0026422R0003

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 1449 - CONTINUATION SHEET

The following have been modified:

52.212-1 - ADDENDUM

52.212-1 ADDENDUM TO INSTRUCTIONS TO OFFERORS – COMMERCIAL ITEMS

1.0 ADDITIONAL INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFERORS

In order to maximize efficiency and minimize the effort involved in the proposal evaluation process, all Offerors shall comply with the following instructions for proposal format and content.

Any proposal that does not comply with these instructions may be considered non-responsive and rendered ineligible for award.

All questions must be received by February 14, 2022, at 1:00 PM Eastern Standard Time using

Attachment 3, “Question and Answer” document. All questions shall be submitted via email to

Ms. Eileen Rivera, Contract Specialist, at eileen.rivera@usmc.mil and Mr. Joel M Miró, Contracting Officer at joel.miro@usmc.mil.

PLEASE NOTE: Your subject line should read “ASB-34 T-AVB Services Support RFP

M00264-22-R-0003-Questions”.

Proposals will be accepted via e-mail only. Proposals must be received following the date on

Block 8 to Ms. Eileen Rivera, Contract Specialist, at eileen.rivera@usmc.mil, and Mr. Joel M

Miró, Contracting Officer at joel.miro@usmc.mil.

Pricing information shall be provided in Microsoft Word and Excel format (completed pricing template and basis of estimates). All spreadsheets shall be in Microsoft Excel format such that each mathematical equation is obvious. No fields shall be password protected. All documents requiring signature shall be provided in PDF (e.g., DD-254). In order to maximize efficiency and minimize the effort involved in the proposal evaluation process, all Contractors shall comply with the following instructions for proposal format and content. The proposal that does not comply with these instructions may be considered non-responsive and render the Contractor ineligible for award.

PLEASE NOTE: Your subject line should read “ASB-34 T-AVB Services Support RFP

M00264-22-R-0003-Proposal”.

1.1 Proposal Format

1.1.1 All Offerors are required to submit their proposals in accordance with the format and content specified. All proposals shall meet the following format requirements:

mailto:eileen.rivera@usmc.mil mailto:joel.miro@usmc.mil mailto:eileen.rivera@usmc.mil mailto:joel.miro@usmc.mil

Page Set up 8.5X 11 inch paper size;

Single-spaced typed lines;

1-inch margins on all sides;

12 point font, Times New Roman font for text material;

Page limitations specified below shall not be exceeded. All material in excess of the specified page limits will neither be read nor evaluated. Graphs, tables, charts, attachments, and diagrams are included in the page count. When both sides of a sheet display printed material, it shall be counted as two (2) pages;

No photographs or hyperlinks are permitted;

Microsoft Office compatible files are required;

Spreadsheet files shall include all formulas. All rows, columns, cells, and worksheets shall be visible. Limit is two decimal places (i.e., 12.34);

Pages shall be numbered consecutively within each volume showing volume and page.

For example, page 12 of Volume I is numbered I-12, and page 5 of Volume II is numbered II-5;

Each page must include the solicitation number and the Offeror name

Number of page limits required per volume is as follows:

Volume Volume Title Page Limit

1 Compliance Documentation No limit

2 Factor 1 Technical Capability 30 pages

3 Factor 2: Past Performance 15 pages

4 Factor 3: Price No limit

1.2. Proposal Content

Each proposal shall contain the following volumes/sections:

Volume 1: Compliance Documentation

Volume 2: Factor 1 – Technical Capability

Volume 3: Factor 2 – Past Performance

Volume 4: Factor 3 – Price

1.3 Volume 1 - Compliance Documentation

The proposal shall comply with the following information:

1.3.1 Adherence to proposal format and content.

1.3.2 Include a cover letter with the following information:

1) The RFP number.

2) Company Information. Provide the name, address, DUNS number, CAGE

Code, and telephone number of the Offeror.

3) Authorized Personnel. Provide the name, title, telephone number, facsimile number, and e-mail address of the company/division point of contact that can obligate your company contractually. Also, identify those individuals authorized to negotiate with the Government.

4) “Remit to” address, if different than a mailing address.

5) Acknowledgment of Amendments (if applicable).

6) Agreement with terms. A statement specifying the extent of agreement with all terms, conditions, and provisions included in the RFP. Offerors are to clearly detail any exceptions taken and the rationale for the exceptions taken to the

RFP. Please note that exceptions taken to the RFP may render the proposal unacceptable to the Government.

7) Identify any enclosures being transmitted.

8) State the length of proposal validity (at least a minimum of 180 days).

9) DRAFT DD254.

1.3.3 Organizational Conflict of Interest (OCI) Plan Submission: The Offeror shall submit its

OCI Mitigation Plan (if applicable) that addresses all actual or potential conflicts of interest in adequate detail for the Contracting Officer to determine whether an OCI exists or has been mitigated. The Offeror shall describe how the OCI Mitigation Plan was developed and the company's approach to avoiding, mitigating, or neutralizing any identified OCI risks. If an

Offeror determines that an actual or potential OCI does not exist, the Offeror shall include a statement to that effect as part of its proposal and does not need to submit an OCI Plan.

1.3.3.1 To facilitate resolution of any potential or actual OCIs, Offerors are encouraged to submit their OCI Plans in advance of the proposal submission due date. The OCI Mitigation Plan shall specifically address the OCI disclosures required in this section and explain how the prime willfully avoid, neutralize, or mitigate any OCIs, as indicated in FAR 9.5. As part of its OCI

Mitigation Plan, the Offeror must identify which contracts or subcontracts it will continue to support and those it intends to terminate or allow to lapse to eliminate any conflicts of interest.

The OCI Mitigation Plan shall also address other OCI resolution and mitigation measures to include the divestment of business units.

1.3.4 Include completed DD Form 254 Security Clearance form (Attachment 1). The Offeror shall demonstrate its ability to meet the security requirements of the RFP and in accordance with the DD Form 254. The Contractor shall provide a completed DD Form 254, Contract Security Classification Specification filled out in blocks 6.a., 6b. and 6c.

for the prime Contractor and blocks 7.a., 7.b., and 7.c. for any subContractors.

1.3.5 Offerors will be responsible for ensuring that their subContractor(s) meet(s) security policies and regulations in accordance with the DD Form 254 and applicable security policies and regulations. The proposal must provide sufficient information for the Government to validate the proposed information. The Offeror shall provide specific information that indicates any Facility Clearance Level (FCL), Key Personnel and

Foreign Ownership, Control, or Influence (FOCI) issues and/or concerns by the Offeror, as indicated in the National Industrial Security Program Operating Manual (NISPOM), that have not been properly negated. If no FOCI issues and concerns exist, the Offeror shall state them in the proposal. FCL and FOCI information shall include at least the following:

1. Company Name

2. Address and Zip Code

3. Commercial and Government Entity (CAGE) Code

4. Facility Security Clearance Level

5. Safeguarding Level

1.3.6 Subcontracting Plan submission - All Offerors classified as large businesses under the selected NAICS of this effort are required to submit a subcontracting plan articulating performance and execution of small business goals with their proposal. The subcontracting plan shall comply with FAR clause 52.219-9 and include the details listed at FAR subpart 19.704 - Subcontracting Plan Requirements.

1.4 Volume 2 - Factor 1 – Technical Capability

1.4.1 Factor 1 – Technical Capability: The proposal must clearly demonstrate the Offeror’s knowledge and understanding of the technical and programmatic requirements outlined in the

Performance Work Statement (PWS), ensuring its discussion is not a reiteration and acceptance of the requirements from the PWS but rather a clear articulation of its ability to provide continuous quality support to the ASB-34 T-AVB Program. The contractor must demonstrate the offeror’s capacity to support the identified demonstrated mission areas, to understand the priorities and emerging issues within those areas, and to execute a comprehensive approach that ensures quality performance and use of staff resource to meet objectives without any interruption in training. The proposal shall also include a Work Breakdown Structure (WBS) to include supporting material such as proposed labor categories and labor hours for each labor category as it relates to the RFP/PWS.

1.4.2 Small Business Participation Plan - All Offerors (large or small business) shall submit a

Small Business Participation Plan that demonstrates the extent of small business participation specifically related to the ASB-34 T-AVB Program. The Small Business Participation Plan is separate from the Small Business Subcontracting Plan and shall include the following, at a minimum:

Small business(es) proposed to participate in the performance of the ASB-34 T-AVB Program, using the table below:

Company

Name

Company

Address

Company

CAGE

Code

Company

Type(s)*

Level of

Participation

Work to be

Performed

Total Small Business Participation goal for ASB-34 T-AVB Program is 10%**

*List all applicable business types for each company: small, small disadvantaged, veteran-owned, service-disable veteran-owned, HUB-Zone, women-owned, historically black colleges and universities, minority institutions.

** The level of participation shall be expressed in terms of a percentage of the total contract value (no price information in this section). The goal for small business participation is %.

Documentation demonstrating the Offeror’s commitment to utilize the small business subcontractors proposed above;

Rationale for the proposed level of participation and allocation of work;

Participation shall be provided in terms of percentage of total contract dollars and total dollars of total evaluated price for small business, veteran-owned small business, service-disabled veteran-owned small business, HUBZone small business, small disadvantaged business, and women-owned small business concerns as the prime and/or subcontractors.

A description of additional efforts that will be undertaken to identify and develop opportunities for small business concerns.

NOTE for Large Business Offerors: The small business(es) specified in the Small Business

Participation Plan shall be included in the Small Business Subcontracting Plan.

NOTE for Small Business Offerors: If a small business Offeror proposes as a Prime Contractor, their participation in the contract counts toward small business participation and should be identified as such. The Offeror shall not provide any price information in the Small Business

Participation Plan. However, the information provided shall reconcile to the information submitted in the Price Volume.

1.5 Volume 3 – Factor 2 – Past Performance

1.5.1 The Offeror must provide information on three contracts within the last five years (of the closing date of this solicitation) that are relevant in scope and similar in size and complexity to the tasks required in the PWS, using, “Past Performance Questionnaire” (Attachment 4). As the

Attachment 4 specifies, each previous effort must include the contract or task order number (no solicitation number); dollar value; type of contract; period of performance; and an explanation of how it is relevant to this effort in terms of scope and how it is similar in size and complexity. The explanation should identify how much of the previous effort is relevant to the scope of the requirement by dollar value (i.e., what was the dollar value of the portion of the work performed under the previous effort applicable to this PWS). The Offerors past performance information must demonstrate actions employed to identify risks and overcome problems encountered. The

Offeror shall identify if they were performing on the contract as a prime or a subcontractor.

Note: If submitting for Single Award IDIQ contract past performance record, task orders under an IDIQ contract counts as one (1) past performance record.

If submitting for a Multiple Award IDIQ contract past performance record, each task order referenced in the proposal counts as a past performance record.

1.5.2 If the Offeror relies on past performance information contained in the Contractor

Performance Assessment Report (CPARS), it shall ensure that the information is an interim/final

CPARS record. Draft records will not be considered. If the Offeror relies on past performance information NOT contained in the CPARS, Attachment 5 “Assessor Past Performance

Questionnaire” shall be utilized to obtain Assessor information sent directly to the government

POCs no later than the closing date of this solicitation.

1.5.3 For classified contracts, provide past performance record ensuring that the contract scope of work is unclassified and that the information contained in the PWS is releasable at the unclassified level prior to using this information as a reference for this effort. If information is suitable for unclassified release, then, submit copy of the PWS and CLINs. This information shall be provided as an attachment to only the ORIGINAL copy of this volume.

1.5.4 Provide a current point of contact (POC) for each past performance record included in the proposal.

1.6 Volume 4 – Factor 4 – Price.

1.6.1 The Offeror shall provide its proposed unit pricing and total firm fixed price using

Attachment 2: Pricing Template and SF1449. The pricing template data shall be identical to the

SF1449. In cases where the Pricing Template and the SF1449 conflict, the SF1449 shall take precedence. All information relating to pricing data shall be included in this volume.

Spreadsheets must be submitted in Microsoft Excel 2007 (or later) with no macros and no more than two decimal places. Data contained in the price volume must be consistent with data contained in Volume I and the filled-out CLINs in the Request for Proposal. The price data should support the level of resources proposed in the technical capability volume. The

Contractor must provide sufficient price information to allow the Contracting Officer to determine the reasonableness of the proposed price. This is a firm-fixed-price effort; therefore, all labor rates and pricing totals shall be inclusive of all overhead, G&A, profit, etc. This information shall be incorporated in the pricing workbook, as an added worksheet in Microsoft

Excel.

1.6.2 Due to the competitive nature of this procurement, the Government is not requesting submission of certified cost or pricing data. The Contractor shall not submit certified cost or pricing data substantiating the cost elements being proposed. If adequate competition is not obtained or should a situation develop that the Government will require submission of information other than cost or pricing data, the Contractor should be prepared to submit the cost or pricing data within five business days of request.

1.6.3 The Contractor shall use and not change the not to exceed (NTE) amounts provided in the pricing template and the SF 1449 for cost reimbursement travel CLIN.

1.6.4 Price Information. The total submitted price shall consist of the proposed price for the base period and all option periods and will be incorporated into Schedule of Supplies/Services of the

SF 1449 upon contract award. The prices for all option items will be evaluated in accordance with FAR 52.217-5, Evaluation of Options. The Government makes no guarantee that the option periods will be exercised. It will be the Government’s unilateral right to exercise any option periods and, once option periods are exercised; the Contractor is required to perform the work when ordered during the scheduled period of performance.

1.6.5 The Government reserves the right to incorporate all or part of the successful offeror's proposal into any contract awarded pursuant to this solicitation. In the event of any conflict between the successful offeror's proposal, which is incorporated into the contract awarded pursuant to this solicitation, and any other portion of the contract, the conflict shall be resolved in favor of the contractual terms that were provided in the Government's solicitation. However, in the event that the successful offeror's proposal exceeds any solicitation requirement it will become the minimum or threshold contract requirement.

Under no circumstances shall pricing information and documentation be included elsewhere in the proposal

PERFORMANCE WORK STATEMENT

Performance Work Statement (PWS)

For

T-AVB Training, Program, Planning, and Liaison Support the Avionics Officer, Aviation Sustainment Branch (ASB-34), Headquarters Marine Corps

(HQMC)

1.0 Background

1.1 The T-AVB is a civilian aviation B-Class crewed ship under the Maritime Administration

(MARAD) or Military Sealift Command (MSC) that provides rapid and dedicated sealift for the employment of tailored Intermediate - level Aviation Logistics (AVLOG) support for a deployed

Marine Expeditionary Brigade (MEB) Aviation Combat Element (ACE), in support of

Operational Plan (O-Plan) requirements. It is designed to transport critical Fixed Wing (FW) and Rotary Wing (RW) maintenance and supply assets to a forward operating area and establish an afloat intermediate-level maintenance activity (IMA) Marine Aviation Logistics Squadron

(MALS) in support of deployed Marine aircraft. Due to the dynamic nature of personnel assignment (e.g., turnover), recurring training requirements exist to ensure USMC AVLOG personnel maintain T-AVB operational proficiency. Training is focused primarily on ensuring

USMC AVLOG personnel can accomplish Mission Essential Tasks (MET) on loading, deploying, and offloading AVLOG support packages during real-world contingencies and exercises. Additional training requirements are on using ICODES to create safe load plans for either “transport” or “operational” modes aboard the T-AVB. ICODES will take into account

Mobile Facility (MF) requirements for power, water, and HVAC sources and create a preferred loading sequence for equipment. ICODES is designed to satisfy the focused stow planning demands of the U.S. Army and the U.S. Marine Corps by assisting personnel at the port and rear echelon planning sites to react quickly and efficiently to changing transportation requirements.

However, it must be noted that ICODES is a completely new technology to AVLOG Marines, and it is yet to be certified for the T-AVBs. ICODES user interface and general operations are focused on general ship loading paradigms. T-AVB is a major exception to that domain.

1.2 AVLOG Marines must be exposed and trained in the practical knowledge of the Marine

Aviation Logistics Support Program (MALSP), MALSP Future concepts, and concepts of T-

AVB employment/deployment, characteristics, properties, and uses as they pertain to coordinating and integrating Mobile Facility / T-AVB requirements. Skills in Microsoft Word, Excel, PowerPoint, and Outlook are essential to prepare reports, compile briefs, analyze data, track assets and keep the command appraised of program status. Understanding the impacts to

Trim, Stress, and Stability (TSS) during planning and loading, skilled capabilities in using

ICODES (as it applies to T-AVB) are critical. The ability to communicate both in writing and verbally is essential to articulate requirements and presentations to produce NAVAL messages to commands. Both T-AVB ships have deployed in support of Desert Shield/Storm, Operation

Iraqi Freedom (OIF), and Operation Enduring Freedom (OEF). They provided both required sea-base support and an offload AVLOG capability to offer distributive ops to setting up the land-based support in theater.

1.3 The principal application used to support T-AVB operations is the Government-owned T-

AVB Automated Load Planning System (TALPS), requiring incremental software maintenance releases, documentation updates, and training for OPFOR users. TALPS is being replaced by the

Integrated Computerized Deployment System (ICODES), which is a decision-support system that applies the Integrated Cooperative Decision-Making (ICDM) framework to the domain of ship stow planning and the initial transition is not yet complete. Initial authorized capability is expected to be FY23, assuming Government Acceptance Testing (GAT) is successful.

2.0 Scope

2.1 The scope of this effort is to provide training, technical, and programmatic support to the

Avionics Officer, Aviation Sustainment Branch (ASB-34), Headquarters, United States Marine

Corps (HQMC), for the T-AVB class of aviation logistics support ships on both the east and west coasts, as well as to their Operational Force (OPFOR) users at 2d and 3d Marine Aircraft Wings

(MAWs) and the MARFORs. This PWS defines the scope of necessary support for mission-critical Marine Corps logistics systems, requiring the Contractor to provide project management;

T-AVB operations support, TAVB into ICODES software testing, training and documentation, and on-site liaison with 2d MAW personnel and 3d MAW personnel. Additional requirement includes providing informal help desk support to the user population.

3.0 General Requirements

3.1 The Contractor will be responsible for executing a comprehensive support program that includes providing Subject Matter Expertise (SME) at various professional forums, to liaison with other activities (e.g., Maritime Administration, Military Sealift Command, SEALOG

Activities, Service branches, and DC Installations and Logistics (DC I&L) providing technical planning coordination and execution support for OPFOR exercises and deployments.

3.1.1 The Contractor shall provide suitable technical and analytical expertise to support the scope of activities under this PWS. The Contractor shall appoint a technical manager to act as both coordinator of task activities and to serve as the overall expert for successful completion of this task initiative. Administrative support shall be provided as required.

3.1.2 The Contractor employees shall identify themselves as contractor personnel by introducing themselves or being introduced as contractor personnel and displaying distinguishing badges or other visible identification for meetings with Government personnel. In addition, contractor personnel shall appropriately identify themselves as contractor employees in telephone conversations and in formal and informal written correspondence.

3.1.3 The Contractor shall maintain and update a recommended list o5.0f personnel that requires

CACs for the Contracting Officer’s Representative’s (COR’s) approval.

3.1.4 The Contractor shall obtain the signature on all non-disclosure agreements necessary to interface with other contractors to accomplish the T-AVB mission in support of this PWS in accordance with FAR 9.505-4. Copies of all non-disclosure agreements required for this contract shall be provided to the (COR).

3.1.5 The Contractor personnel on this effort require a minimum of SECRET security clearance to execute necessary support. The contractor shall comply with the provided DD254 stipulations for this contract.

3.1.6 The Contractor shall submit all deliverables to the COR, and the COR is responsible for tracking and acceptance.

3.1.7 The contractor shall provide suitable infrastructure to manage program requirements (e.g., document library, databases) throughout the period of performance to support the scope of activities. Contractor costs for laptops, cellular equipment/services, and other items of convenience are not reimbursable as direct contract costs.

3.1.8 Government on-site support for SME’s at 2d MAW, MCAS Cherry Point, NC, and 3rd

MAW, MCAS Miramar, CA will provide office space and necessary tools (desk, phones, network accounts, etc.) to execute anticipated responsibilities.

3.2 Place of Performance

3.2.1 The work to be performed under all the task of this contract will be performed at the contractor’s facilities and two separate locations:

1) Marine Corps Air Station Miramar, California. Embedded with the Third Marine

Aircraft Wing Plans Department.

2) Marine Corps Air Station Cherry Point, North Carolina. Embedded with the Second

Marine Aircraft Wing Plans Department.

3.3 Recognized Holidays

New Year’s Day

Labor Day

Martin Luther King’s Birthday

Columbus Day

Presidents Day

Veterans Day

Memorial Day

Thanksgiving Day

Juneteenth Christmas Day

Independence Day

3.4 Hours of Operation

3.4.1 The contractor is responsible for providing support between the hours of 0800 to 1600

Monday thru Friday except for Federal holidays specified on PWS 3.3, or when the

Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings. The Contractor must at all times maintain an adequate workforce for the uninterrupted performance of all tasks defined within this PWS when the Government facility is not closed for the above reasons. When hiring personnel, the

Contractor shall keep in mind that the stability and continuity of the workforce are essential.

3.5 Data Rights.

3.5.1 Data, Software and Intellectual Property Rights. In accordance with the DFARS data rights clauses associated with this effort, without limitation, all reports, materials (including, but not limited to, all training and training-related materials including, but not limited to, all SOPs, lessons learned, analyses/evaluations and analyses/evaluation criteria, on-line course materials, computer software/applications and hardware, source code, interfaces, tools, works, and other related items) data, information, and all electronic/digital files and other items described herein, and any other items, (hereinafter referred to individually or collectively as the Work or Works) that are first created, generated, or produced and required to be delivered under, or as a result of, this PWS shall be provided to the U.S. Government/Marine Corps with the level of intellectual property/data rights provided by such DFARS data rights clauses.

3.5.2 Such data rights and related clauses include, but may not be limited to: DFARS Clauses

252.227-7012 Patent License and Release Contract; 252.227-7013 Rights in Technical Data--

Noncommercial Items; 252.227-7015 Technical Data–Commercial Items; 252.227-7016 Rights in Bid or Proposal Information; 252.227-7017 - Identification and Assertion of Use, Release, or

Disclosure Restrictions; 252.227-7020 - Rights in Special Works; 252.227-7021 Rights in Data--

Existing Works; 252.227-7024 Notice and Approval of Restricted Designs; 252.227-7025 -

Limitations on the Use or Disclosure of Government-Furnished Information Marked with

Restrictive Legends; 252.227-7027 Deferred Ordering of Technical Data or Computer Software;

and 252.227-7037 Validation of Restrictive Markings on Technical Data.

3.5.3 Using the format described by DFARS 252.227-7017, the Contractor will provide the COR with a data rights assertion listing for all deliverables including both non-commercial and commercial technical data and computer software. Furthermore, the contractor shall not use the contractor’s or a third-party’s proprietary data, information, software, items and/or other materials for any purpose without meeting the requirements of DFARS clauses 252.227-7020 and/or 252.227-7025, and without the specific, written approval by the Contracting Officer, prior to start of any work.

3.5.4 Moreover, except as provided in writing by the Contracting Officer, no Work, information, material and/or other item created, generated, produced and required to be delivered under, or as a result of, this PWS/effort shall be used by the Contractor or any of its employees/agents, subcontractors and/or representatives, for any purpose other than for the support and performance of this PWS. Still further, the Contractor is obligated to protect from unauthorized use or disclosure all Government confidential or classified material and/or Government-owned proprietary, and/or Personally Identifiable Information or Personal Privacy Items obtained in the course of performance under the Government contract, as long as such data remains proprietary, confidential, sensitive, or classified.

3.6 Travel Requirement

3.6.1 Contractor will be required to travel to USMC bases, CONUS, and possible OCONUS during the performance of this contract to attend meetings, conferences, and training. The contractor may be required to travel to off-site training locations and to ship training aids to these locations in support of this PWS. Local travel within a 50 mile radius for all team members will not be reimbursed. Contractor will be authorized travel expenses consistent with the substantive provisions of FAR 31.205-46 and the limitation of funds specified in this contract. All CONUS and OCONUS travel requires Government approval/authorization and notification to the COR.

3.6.2 The expected level of travel is detailed below:

LOCATION

# TRIPS

IN BASE

YR

# OF

TRIPS

IN

OY1

# OF

TRIPS

IN

OY2

# OF

TRIPS

IN

OY3

# OF

TRIPS

IN

OY4

Camp Pendleton, CA 2 2 2 2 2

Camp Lejeune, NC 2 2 2 2 2

Cherry Point, NC 3 3 3 3 3

Norfolk, VA 1 1 1 1 1

Philadelphia, PA 4 4 4 4 4

San Diego, CA 2 2 2 2 2

Scott AFB, IL 2 2 2 2 2

NAS Patuxent River, MD 1 1 1 1 1

4.0 Specific Requirements

4.1 Task 1: Training Support

4.1.1 The Contractor shall provide liaison support for the T-AVB ships for coordination of quarterly training requirements.

4.1.2 The Contractor shall provide training to the USMC AVLOG personnel to accomplish

Mission Essential Tasks of loading, deploying, and offloading AVLOG support packages.

4.1.3 The Contractor shall provide training to the USMC COMM personnel on the operation and maintenance requirements of the communications and data systems installed on the T-AVB.

4.1.4 The Contractor shall provide training to the USMC AVLOG personnel on the use of

ICODES to create safe load plans for either “transport” or “operational” modes aboard the T-

AVB once the migration from TALPS is complete. Historically there are four classes per year at each MAW, with an average of 3 students per class. The Contractor shall support the ICODES application training providing expertise in response to OPFOR requirements. Support also includes managing training requirements to ensure user efficiency and providing expertise to resolve both Marine Corps and external agency issues affecting the employment of ICODES once it has transitioned.

4.1.5 The Contractor personnel shall maintain a record of all personnel receiving training. No later than five business days after the training is complete, the on-site Contractor personnel shall provide the WING AVIONICS Officer the training roster, either by electronic means, scanned copies, or paper. At the COR’s request, the Contractor will provide a consolidated training roster from all commands which have received training to ASB-34.

4.2 Task 2: Budget Support

4.2.1 The on-site Contractor personnel shall tack expenditures and coordinate with WING

AVIONICS Officer to support the management of the assigned T-AVB Program Planning, Programming, Budgeting, and Execution (PPBE) for the assigned MAW. PPBE is used to analyze requirements, allocate resources, submit budgets, and spend appropriated dollars to support the T-AVB operation and training for the assigned MAW.

4.2.2 The Contractor shall identify any unfunded requirements capable of being executed in the current fiscal year for the assigned MAW.

4.2.3 The contractor shall monitor the funding codes, and correct appropriations are utilized.

4.2.4 The contractor shall support reconciliation of funding requirements with the MAW

Comptroller quarterly.

4.3 Task 3: Planning Support

4.3.1 The Contractor shall coordinate and schedule training with the appropriate T-AVB for all training.

4.3.2 The Contractor shall maintain communications with the MARAD contracted ship support personnel permanently assigned to maintain the T-AVBs in order to stay current on the ships’ status and enhance coordination efforts for the assigned MAW.

4.3.3 The Contractor shall support the T-AVB program office (ASB-34) in developing program plans for Ship Service Life extensions or ship replacements as well as other Program level initiatives.

4.3.4 Programmatic: All personnel work directly as ASB-34 representatives for the OPFORs.

The Contractor on-site personnel shall schedule and coordinate with assigned MAW G1, G3, G4, G5, G6, ALD, and Comptroller on all exercises pertaining to the T-AVB for the assigned MAW.

The contractor shall schedule and coordinate with G6, ALD, Comptroller, Marine Wing

Communication Squadron (MWCS), and Marine Aviation Logistics Squadron (MALS) on all

Communication Exercises for the assigned MAW.

4.3.5 The Contractor's on-site personnel shall coordinate with MEF G3 and MAW G3 to develop a yearly Training Evaluation Exercise Planning (TEEP) event for T-AVB as well as develop a five-year T-AVB training plan for the assigned MAW.

4.4 Task 4: Technical and Systems Support

4.4.1 The Contractor shall perform requirements analysis, requirements verification, functional analysis, functional and physical verification, performance verification, and systems analyses such as USMC COMM upgrades, IMA Electrical System improvements, and deliver an Analysis and Recommendation Report to ASB-34.

4.4.2 The Contractor shall capture deficiencies and draft a punch list of any Ship-Alterations or upgrades required. The list shall be delivered to HQMC ASB-34 for validation of requirements.

The Contractor shall also track approved ship alterations progress and status.

4.4.3 The Contractor shall support testing of ICODES by testing version releases for accuracy and functionality and provide the testing results to the SDDC and HQMC ASB-34.

4.4.4 The Contractor shall maintain the currency of training materials to match the current states of the T-AVB ships and the appropriate ship loading software.

4.4.5 The Contractor shall maintain the TALPS application functionality and database accuracy until the migration to ICODES is complete. Estimated migration is anticipated to be completed in FY 22-23.

4.4.6 The Contractor shall continue to support the TALPS application until the transition to

ICODES is complete and then for a period not longer than one year from ICODES receiving authorization for use by TAVBs.

4.4.7 TALPS support shall include: providing and maintaining the TALPS application upon

COR/ASB-34 request and implementing updates to system documentation until such time as

ICODES receives authorization for use by T-AVB. TALPS support is a diminishing requirement being replaced by an increasing level of effort to support T-AVB in ICODES.

4.4.8 The Contractor shall respond to all OPFOR requirements; historically, there have been 1 to

2 per year.

4.4.9 The Contractor shall update Marine Corps Reference Publication (MCRP) 3-20A.2

Aviation Logistics Support Ship (T-AVB) as required (formerly known as the TAVB Logistics

Planner’s Manual “T-AVB Yellow Book”).

4.4.10 The Contractor shall coordinate with MARCORSYSCOM Publications directorate to facilitate updates to MCRP 3-20A.2.

4.5 Task 5: Management Support

4.5.1 Contract Status Reporting. The Contractor shall provide monthly status reports on task accomplishments throughout the life cycle of the contract. Program Management Reviews

(PMR) frequency and content will be determined at the COR-Contractor kick-off meeting.

PMRs shall then be briefed on that schedule and shall also include the status of the contract at that time. Monthly reports shall include a report of funds spent on travel and funds remaining in travel budgets for each contract option.

4.5.2 The Contractor shall attend meetings and draft meeting minutes in support of the following disciplines: engineering, programmatic, financial, and milestone reviews. The Contractor shall prepare and deliver agendas five days prior to each meeting and prepare and deliver conference minutes no later than 15 days after the event. Historically there are 25 or fewer meetings per year.

4.5.3 The Contractor shall draft Naval Messages to support exercises and deployments. The

Naval Messages shall report the location of the event, as well as initial and final Agendas (these may be separate messages).

5.0 Deliverables

Deliverable Reference Due Date

Contractor's Progress, Status and

Management Report

Subtitle: Monthly Status Report

4.1, 4.2, 4.3,

4.4 and 4.5

No lather than 15 days after the end of the preceeding reporting period.

Subtitle: T-AVB Program Status

Report

4.1, 4.2, 4.3,

4.4 and 4.5

Due to COR as determined by the COR

Technical Report - Study/Services

Subtitle: Technical report

4.4 Due to COR as determined by

the COR

Contractor's Progress, Status and

Management Report

Subtitle: Travel report

4.5 Due to COR as determined by

the COR

Subtitle: Staffing plan, WBS, Quality

Assessment

4.1, 4.2, 4.3,

4.4 and 4.5

Due to COR as determined by the COR

Computer Software Product End Items

Subtitle: TALPS Software Release

4.1 and 4.4 Due to COR as determined by the COR.

Commercial Off-The-Shelf (COTS)

Manual and Associated Supplemental

Data

Subtitle: Publications, training.

4.1, 4.2, 4.3,

4.4 and 4.5

Due to COR as determined by the COR

6.0 Performance Requirement Summary

The contractor service requirements are summarized into performance objectives that relate directly to mission essential items. The performance threshold briefly describes the minimum acceptable levels of service required for each requirement. These thresholds are critical to mission success.

PWS Para Performance

Objectives

Performance

Standard

Acceptable

Quality

Level (AQL)

Monitoring

Method

Incentive

Task:

Training

Support

PWS 4.1

Provide appropriate training for the users’ needs, Upon completion of training, each user is proficient in all the learning

The users that are trained can perform at a

-User Surveys

-Proficiency tests

-CPARS

rating ranging from desktop users to system administrators objectives and is able to function at not less than 90% proficiency level

90% proficient level to safely load/unload and deploy the T-AVB.

-Validated calls to and response by system administrators;

-Audit of training course(s) by program manager

Task:

Training

Support

PWS 4.1.2

Provide training and technical assistance to ensure that USMC is proficient at loading and deploying the T-

AVB.

Ongoing technical training/assistance for 2nd and 3rd

MAW is required to maintain proficiency. As a result of the ongoing CSS training, users

(Marines) will be

100% proficient in loading T-

AVBs in operational and transport mode.

Since the loading and unloading of the T-AVB is a safety issue, there is no acceptable margin for error. The proficient level is 100%

-After action information from annual load-ex training and - activation will determine acceptable level of qualified personnel.

- CPARS

rating

Task:

Training

Support

PWS 4.1.4

Provide training continuity in utilization of the T-

AVB load planning system

(TALPS/ICODES).

-Bi-annual

Communication and loading/unloading exercises to maintain USMC proficiency.

-Support all requests for

T-AVB support outside of the scheduled activation periods.

100% of all requests for support are supported within the allotted budget.

-Physically monitor the

Load/Unload exercises to evaluate the

Marines proficiency during the training evolution.

- CPARS

rating

Task:

Technical and Systems

Support

PWS 4.4

Ensure ship alterations are required, completed, monitored and vetted through appropriate organizations.

-Ensure Ship alterations or upgrades are needed and accomplished to provide sustained use by the

USMC.

Should provide a

90% solution for the purpose of the upgrade or alterations.

-Through inspection process and

IAW current required standards.

- CPARS

-Technical and

Systems requirements should meet current MARAD, MSC, and

SEALOG

activities standards.

Task:

Technical and Systems

Support

PWS 4.4.7

Ensure TALPS is maintained and prepared to migrate to the ICODES loading unloading program.

-TALPS must be maintained and prepared for and until transition to

ICODES.

-Transition should meet the intended

ICODES

transition dates.

Provide a

90% solution during the first load attempt for the T-AVB.

-Physical monitoring of the loading process using the TALPS and

ICODES

loading systems

- CPARS

rating

Task:

Technical and Systems

Support

PWS 4.4

Provide an ongoing list of equipment maintained on the

T-AVB and the operational status of said equipment needed for deployment.

-Ensure equipment aboard the T-AVB is maintained and ready for operational use for exercises and emergent operational needs

-Equipment should be maintained in working order.

95% of the onboard prepositioned equipment should be in working order.

-Inspection process and bi-annual use of the equipment during exercise activation of the

T-AVB.

- CPARS

(End of Summary of Changes)