USS TRIPOLI Attachment S-7 Proposal Assessment Rev_1.xlsx

Section L & M Requirements

- The Solicitation Module in PIEE does NOT accept zip file submissions.

- Proposal submissions shall be formatted so that each file name clearly identifies the Proposal Volume that the file is associated with.

- Each Volume shall be formatted with seperate files submitted for each factor.

Text: 12-point Times New Roman font.

Graphics pages text: Not smaller than 10-point font, legible, and readable.

(1) For any WI with a total value of zero labor hours proposed (prime and subcontractor combined) (although material is proposed), provide an explanation as to why.

For any work item (WI) with a total dollar value of zero dollars proposed in the Pricing Workbook (Attachment J-4) provide an explanation as to why. In addition, if applicable:

(2) For any WI with a total dollar value of zero material proposed (prime and subcontractor combined) (although labor is proposed), provide an explanation as to why.

at https://www.sba.gov/contracting/contracting-officials/goaling.

a) Identifies the specific pier(s) ntended to be used for each proposed Availability, and

b) Indicates that those pier(s) meet the minimum characteristics of Table 1 on Attachment S-5.

b) Provide a completed Execution Milestones & Key Event Dates (Attachment J-3) and a signed letter identifying and confirming ownership of a pier available to berth the vessel from the ‘Availability Start’ through ‘Contract Complete’ milestones as outlined in the Execution Milestones & Key Event Dates (Attachment J-3). The representative who signs the letter must be authorized to contractually bind the company. If the offeror is utilizing a subcontractor for physical resources (pier), a letter signed by the subcontractor identifying and confirming committed access to the proposed pier from the ‘Availability Start’ through ‘Contract Complete’ milestone as outlined in the Execution Milestones & Key Events (Attachment J-3) is required. The subcontractor representative who signs the letter must be authorized to contractually bind the company. The proposed pier facilities, whether owned by the offeror or subcontractor, must be accessible by the USS TRIPOLI (LHA 7) without any modification to the vessel. 1. Assess whether, upon receipt of proposals, the Offeror holds a Master Ship Repair Agreement (MSRA) or has demonstrated equivalency as outlined in Section L, subsection V.B.1 Factor 1.

2. Assess whether the Offeror has ownership or committed access to a pier capable of berthing the vessel, in accordance with Section L.

a) Include Key Events, Milestones, tests

b) Schedule each Work Item to the Work Activity level, listing the planned start and planned completion dates, and durations for each Work Activity.

c) Assign each Work Activity with the appropriate predecessor and successor relationships within the contractor’s scheduling software that establish the logic relationship between schedule Work Activities. Each activity must have at least one predecessor and one successor, with the exception of the Key Event Start Availability (which may have no predecessors) and the Key Event Complete Availability (which may have no successors). Each Event and Activity may have more than one predecessor and more than one successor. The preferred relationships between linked predecessor and successor activities is Finish-to-Start. The use of scheduling Lags and Leads should be minimized.

d) Assign appropriate predecessor relationships to each Key Event and Milestone(s) to ensure there is an accurate logical progression through all work activities leading to their assigned Key Event and Milestone(s), ensure milestones are linked to the Key Events they support, and ensure the Production Schedule supports accurate prediction of Key Event and Milestone(s) attainment.

e) Assign appropriate predecessor and successor relationships between the Work Activities conducted on the same component, or in the same location but under differing Work Items, to ensure all related Work Activities across all Work Items are interdependently linked together.

f) Schedule production work and preliminary inspections generating reports required by Attachment J-10 that could result in a change in work to be accomplished or additional material to be procured to support reporting no later than the first 20 percent of the availability duration.

(2) Provide an export of the Production Schedule data elements in a sortable/filterable spreadsheet format compatible with Microsoft Excel. Include the following minimum data elements for each Work Activity in the schedule, as appropriate:

a) Work Item Number (as appropriate): 4-E specification Work Item number

b) Work Activity Identifier: Numerical designator identifying the Work Activity within the Work Breakdown Structure (WBS)

c) Title: Descriptive title of Work Item and Work Activity

d) Key Event: Key Event applicable to the Work Activity

e) Milestone (as appropriate): Milestone applicable to the Work Activity

f) System (as appropriate): System(s) affected

g) Component (as appropriate): Component Unit (For example: tank, valve, motor, pump)

h) Location: Work location/compartment number

i) Executing Activity: ID specific organization: Prime KTR, Sub-KTR

j) Baseline Start: The date identified in the Production Schedule when the contractor plans to start the Work Activity

k) Baseline Finish: The date identified in the Production Schedule when the contractor plans to finish the Work Activity

l) Early Start: Software determined date. The earliest point in time that a Work Activity may start based on the Production Schedule network logic and any other schedule constraints. Early start dates may change as the availability progresses.

m) Early Finish: Software determined date. The earliest point in time that a Work Activity may complete based on the Production Schedule network logic and any other schedule constraints. Early start dates may change as the availability progresses.

n) Late Start: Software determined date. The latest point in time that a Work Activity may begin without delaying the applicable Milestone or Key Event based on the Production Schedule network logic.

o) Late Finish: Software determined date. The latest point in time that a Work Activity may be completed without delaying the applicable Milestone or Key Event based on the Production Schedule network logic.

p) Duration: The total number of work periods required to complete a Work Activity.

q) Calendar Identification: Number of scheduled workdays per week

r) Total Float: The total number of workdays that the Contractor can delay a Work Activity without affecting the project finish date.

s) Predecessor: An Activity or Event that immediately precedes one or more Activities or Events with a direct tie in the Total Project Network.

t) Successor: An Activity or Event that immediately follows one or more Activities or Events with a direct tie in the Total Project Network.

u) Constraints: Constraints used as applicable to Work Item or Work Activity. This may be provided within the predecessor or successor field.

(3) Provide the Proposed Production Schedule in the Native Software file

(4) Provide the Proposed Production Schedule in a time-oriented Gantt chart format that shows all work item activities, milestones and key events within the Production Schedule.

(5) Provide the Proposed Production Schedule in a time-oriented Gantt chart format that shows only Critical Path and Controlling Work Items at the Work Activity level and assigned Key Events and/or Milestones.

a) Critical Path: That sequence of Work Activities which forms the work and test chain of the longest duration, and directly affects the completion of the availability. Factors that influence when a Work Activity is on the Critical Path include: time duration required for the Work Activity, space limitations, manpower available, and the predecessor/successor relationships between Work Activities. The Critical Path is determined by automated schedule analysis and will include any sequential set of Work Activities forming the longest chain of events extending throughout the schedule and which has the least Total Float.

b) Controlling Work Items: Those Work Items which include activities that are on the critical path of the Production Schedule, which, by virtue of scope, material requirements, complexity, or other considerations, have the significant potential for impact on the scheduled project Key Events or completion of the availability.

(6) The Offeror shall provide a narrative to explain their Production Schedule. The narrative shall address the following:

a) Describe critical float paths and mention the work items that the Offeror estimates as the most critical and pose the most risk.

b) Demonstrate how the Offeror has scheduled the performance of all work items included in the Availability work package (including both Base and Option items) so as to permit the contract scope increases described in Section B, Note F (all growth work identified in this solicitation) without causing delay or disruption to the work required by the aforementioned work items, to any other Government contract, or to any other work in progress for the Government.

The Government will assess the Offeror’s:

a) Understanding of scope and integration of the required work items in the Specification Package (Attachment J-1).

b) Identification of the critical path and logically sequencing work items.

c) Integration of the milestones and key events in the Execution Milestones & Key Events (Attachment J-3) reasonably.

d) Extent to which the narrative describes the critical float paths and the work items that the Offeror estimates as the most critical and pose the most risk.

e) Extent to which the narrative explains how the Offeror has scheduled the performance of all work items included in the Availability work package (including both Base and Option items) so as to permit the contract scope increases described in Note F without causing delay or disruption to the work required by the aforementioned work items, to any other Government contract, or to any other work in progress for the Government.

Where the offeror does not have recent or relevant past performance information, the Offeror shall affirmatively state that it does not have recent and relevant past performance information for the Government to consider.

If the Offeror does not have CPARS and is required to submit Attachment S-9, the Offeror shall submit a request to their customers to complete the Past Performance Questionnaires (PPQs) NLT 30 days prior to the closing date of this solicitation. The Offerors request to their customer shall include the request to submit completed PPQs to CDR Jonathon Pagnucco, Contracting Officer, jonathan.p.pagnucco.mil@us.navy.mil, and Derek Shirley, Contract Specialist, derek.s.shirley.civ@us.navy.mil, prior to the closing date of this solicitation.

NOTE: The Government reserves the right to use the contract information provided in the offeror’s proposal to obtain data from other sources, such as the Contractor Performance Assessment Reporting System (CPARS) database and from the points of contact identified by the offeror in its proposal.

Any questionnaire received after the proposal due date/time may be considered as late and may not be considered in the Offeror’s past performance evaluation. The Government, at its discretion, will determine whether or not questionnaires received after the proposal due date will be considered. The Past Performance factor will be rated on an Acceptable/Unacceptable basis. The Government will use information provided by the Offeror, as well as any other information deemed necessary as noted in Section L, V, B, 2 to assess the Offeror’s ability to meet the solicitation requirements. This assessment will be based on a demonstrated record of past performance, taking into consideration the recency and relevancy of the past performance information. In evaluating an Offeror’s past performance, the Government reserves the right to contact former customers, Government agencies and other private and public sources of information.

In the case of an Offeror without a record of relevant past performance or for whom information on past performance is not available or so sparse that no meaningful past performance rating can be reasonably assigned, the Offeror may not be evaluated favorably or unfavorably on past performance (see FAR 15.305 (a)(2)(iv)). Therefore, the Offeror shall be determined to have unknown past performance. In the context of acceptability/unacceptability, unknown past performance shall be considered acceptable. The evaluation will include information provided by the Offeror demonstrating compliance with the requirements of FAR 52.219-8 and 52.219-9.