Section_J_Attachment_4_-_Conformance_Matrix_010314FD.xlsx

XLSX spreadsheet 39 KB Posted

Attached to
Solicitation Notice for Workers' Compensation Medical Bill Processing (WCMBP) Federal contract opportunity
Solicitation number
DOL141RP21903
Issued by
Department of Labor Office of the Assistant Secretary for Administration and Management

About this file

Section J Attachment 4 - Conformance Matrix

View the file

Other files for this federal contract opportunity

Other files attached to Solicitation Notice for Workers' Compensation Medical Bill Processing (WCMBP), newest first.
File Type Posted
WCMBP_Section_F_-_Deliveries_and_Performance_AMD_6.doc DOC document
Amendment_6_Questions_and_Responses.xlsx XLSX spreadsheet
WCMBP_Section_J_Attachment_23_-_Government_Furnished_Information_AMD_5.doc DOC document
WCMBP_Section_J_Attachment_9_-_Prior_Experience_Reference_List_Template_AMD_5.doc DOC document
WCMBP_Section_J_Attachment_3_-_Compliance_Matrix_AMD_5.xlsx XLSX spreadsheet
WCMBP_Section_I_-_Contract_Clauses_AMD_5.doc DOC document
WCMBP_Section_J_Attachment_6_-_Question_Submission_Template_AMD_5.xls XLS spreadsheet
WCMBP_Section_J_Attachment_27_-_Glossary_AMD_5.doc DOC document
WCMBP_Section_J_Attachment_1_-_Price_Cost_Schedule_AMD_5.xlsx XLSX spreadsheet
WCMBP_Section_J_Attachment_14_-_Past_Perf_Sub_Consent_Ltr_AMD_5.doc DOC document
WCMBP_Section_J_Attachment_28_-_Government_Furnished_Templates_AMD_5.doc DOC document
WCMBP_Section_J_Attachment_13_-_Past_Performance_Questionaire_Template_AMD3.pdf PDF
WCMBP_Section_J_Attachment_18.5_-_2013_Call_Center_Call_Volumes_by_Program_AMD_3.xlsx XLSX spreadsheet
WCMBP_Section_F_-_Deliveries_and_Performance_AMD_3.doc DOC document
WCMBP_Section_H_-_Special_Contract_Requirements_012314.docx DOCX document
WCMBP_Section_J_Attachment_28_-_Government_Furnished_Templates_AMD_3.doc DOC document
WCMBP_Section_J_Attachment_27_-_Glossary_120213FD.doc DOC document
WCMBP_Section_J_Attachment_25_-_Requirements_Specs_Documents_010614FD.doc DOC document
WCMBP_Section_J_Attachment_30.2_-_Treatment_Suites_Viewer_ER_Diagram_AMD_3.pdf PDF
WCMBP_Section_J_Attachment_30.1_-_Treatment_Suites_Builder_ER_Diagram_AMD_3.pdf PDF
WCMBP_Section_J_Attachment_19_-_Weekly_Call_Minute_Detail_Data_6-5-2013.xls XLS spreadsheet
WCMBP_OFFEROR_QUESTION_Responses-_052914.docx DOCX document
WCMBP_Section_B_-_Supplies_or_Services__Prices-Costs_AMD_3.doc DOC document
WCMBP_Section_J_Attachment_32__-Transition_Out_Plan_Template_AMD_3.doc DOC document
WCMBP_Section_J_Attachment_1_-_Price_Cost_Schedule_AMD_3.xlsx XLSX spreadsheet
WCMBP_Section_J_Attachment_10_-_Prior_Exp_Project_Desc_Template_AMD_3.doc DOC document
WCMBP_Section_C_-_Performance_Work_Statement_AMD_3_052914.doc DOC document
WCMBP_Section_J_Attachment_30_-_Treatment_Suites_Technical_Data_AMD_3.doc DOC document
WCMBP_Section_J_Attachment_18.6_-_1099_Historical_Volumes_from_2009-2012_AMD_3.xlsx XLSX spreadsheet
WCMBP_Section_J_Attachment_18.1_-_Projected_Operational_Volumes_AMD_3.xlsx XLSX spreadsheet
Section_M_-_Evaluation_Factors_for_Award.pdf PDF
Section_K_-_Certifications_.pdf PDF
Section_J_Attachment_27_-_Glossary_120213FD.doc DOC document
Section_13_Edits_and_Audits_Legacy_version_20140106.doc DOC document
Section_18_Bill_Pricing_Legacy_version_20140106.doc DOC document
Section_6_DFEC_Imaging_Legacy_version_20140106.doc DOC document
Section_G_-_Contract_Administration_Data.pdf PDF
Section_J_Attachment_2_-__Proposal_File_Matrix_Template_FD.xls XLS spreadsheet
Section_J_Attachment_7_-_Key_Position_Background_Matrix_Template_FD.xls XLS spreadsheet
Section_J_Attachment_14_-_Past_Perf_Sub_Consent_Ltr_123013FD.doc DOC document
Section_J_Attachment_18.1_-_Projected_Operational_Volumes_122413FD.xlsx XLSX spreadsheet
Section_19_Pharmacy_Legacy_version_20140106.doc DOC document
Section_J_Attachment_12_-_Past_Perf_Contact_Sheet_Template_123013FD.doc DOC document
Section_12_Return_to_Provider_Legacy_version_20140106.doc DOC document
Section_L_-_Instructions_Conditions_and_Notices_to_Offerors.pdf PDF
Section_16_Authorizations_Legacy_version_20140106.doc DOC document
Section_J_Attachment_13_-_Past_Perf_Questionnaire_Template_123013FD.doc DOC document
Section_11_Prompt_Payment_Legacy_version_20140106.doc DOC document
Section_J_Attachment_17_-_DLMS_9_Chapters_400_and_1200_FD.pdf PDF
Section_27_Communications_Legacy_version_20140106.doc DOC document
Show all 50

Solicitation Notice for Workers' Compensation Medical Bill Processing (WCMBP) has more files on GovTribe.

On GovTribe

Work with this file on GovTribe

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

Text version

Sheet

WCMBP CONFORMANCE MATRIX (Instructions from Section L)
*** In the event of a discrepancy between this matrix and sections of the RFP, the RFP is the authority ***
*** The Government advises the Offeror to accurately and specifically identify the location of each instruction within its proposal. Failure to do so may adversely affect the rating of its proposal ***
Section NumberSection NameInstruction IdentifierInstruction TextProposal ReferenceCompliesException/DeviationComments/ExplanationsScreening RoleImpact
Identifies the section number of the instructionIdentifies the instruction to which the proposal must conformIdentify section and/or page number(s) in the proposal where the instruction is satisfiedYes or NoIdentify if the proposal identifies an exception or deviation to the requirementDiscuss relevant issues. (e.g., if the proposal does not address the instructions, describe the rationale and impact of non-conformance)CO = Contracting Officer

TM = Technical/Mgmt Evaluation Team PE = Prior Experience Evaluation Team PET = Price Evaluation Team N/A = Not applicable to initial screening D = Deficiency SW = Significant Weakness W = Weakness

L.1Solicitation Provisions IncorporationL1The Offeror shall complete the following FAR provision blocks of text and submit them as part of the Contract Volume:• FAR 52.209-5 (cited in Section K)COD
L.1Solicitation Provisions IncorporationL2The Offeror shall complete the following FAR provision blocks of text and submit them as part of the Contract Volume:• FAR 52.219-28 (cited in Section I)COD
L.1Solicitation Provisions IncorporationL3The Offeror shall complete the following FAR provision blocks of text and submit them as part of the Contract Volume:• FAR 52.227-15 (cited in Section K)COD
L.1Solicitation Provisions IncorporationL4The Offeror shall complete the following FAR provision blocks of text and submit them as part of the Contract Volume:• FAR 52.203-2 (cited in Section I)COD
L.1Solicitation Provisions IncorporationL5The Offeror shall complete the following FAR provision blocks of text and submit them as part of the Contract Volume:• FAR 52.204-8 (cited in Section K)COD
L.2.5Proposal AcceptanceL6The Offeror shall make a clear statement in the proposal of the date of its validity.COSW
L.3Proposal Preparation InstructionsL7The Offeror shall include in its proposal, all data and information required by this section (L.3).N/AW
L.3Proposal Preparation InstructionsL8The Offeror shall submit its proposal in accordance with these instructions.N/AW
L.3Proposal Preparation InstructionsL9The Offeror shall ensure all pricing information is provided in Volume VII (under separate tab) including submission of Subcontracting Plan.
N/AW
L.3.1Electronic Solicitation ResponsesL10The Offeror shall construct all solicitation responses following the instructions for construction in section L.3.1.1.N/AW
L.3.1Electronic Solicitation ResponsesL11The Offeror shall construct all solicitation responses following the instructions for content in section L.3.1.2.N/AW
L.3.1Electronic Solicitation ResponsesL12The Offeror shall construct all solicitation responses following the instructions for using electronic media in section L.3.1.3.COD
L.3.1Electronic Solicitation ResponsesL13The Offeror shall construct all solicitation responses following the instructions for delivery in section L.3.1.4.PED
L.3.1Electronic Solicitation ResponsesL14The Offeror shall deliver all solicitation responses to the Contracting Officer according to Table 1. [Solicitation Due Dates]PED
L.3.1.1.1File Types and FormatsL15The Offeror shall present information in a solicitation response using file type and formats, such that text and graphics are readable by Microsoft Word 2010.PED
L.3.1.1.1File Types and FormatsL16The Offeror shall present information in a solicitation response using file type and formats, such that tabular numerical data are readable by Microsoft Excel 2010.
L.3.1.1.1File Types and FormatsL17The Offeror shall present information in a solicitation response using file type and formats, such that presentation material, if allowed by the solicitation, are readable by Microsoft PowerPoint 2010.PED
L.3.1.1.1File Types and FormatsL18The Offeror shall present information in a solicitation response using file type and formats, such that schedule is readable by Microsoft Project 2013
L.3.1.1.1File Types and FormatsL19The Offeror shall use only Microsoft Word versions 2010 for presenting revised proposal text and graphics (with change tracking enabled).PEW
L.3.1.1.1File Types and FormatsL20The Offeror shall use only Microsoft Excel 2010 or earlier for price reporting (with no change tracking).PEW
L.3.1.1.2File NamesL21The Offeror shall name files using consistent naming conventions that clearly identify the file.PEW
L.3.1.1.2File NamesL22The Offeror shall store each proposal file in a folder that corresponds to the proposal volume it represents.PEW
L.3.1.1.2File NamesL23The Offeror shall name the files in each proposal volume folder in an unambiguous manner, using plain text language to facilitate the ease of accessing the files for evaluation.PESW / W
L.3.1.1.2File NamesL24The Offeror shall insert the file name in the header of each document.PED
L.3.1.1.3Content SafeguardsL25The Offeror shall save all proposal files with macros and links either disabled or removed.PESW
L.3.1.1.3Content SafeguardsL26The Offeror shall not establish password protection on proposal files.N/AW
L.3.1.1.3Content SafeguardsL27The Offeror shall ensure that Spreadsheet files allow for the viewing of cell contents and embedded formulas.TMW
L.3.1.2ContentL28The Offeror shall construct the solicitation responses using the instructions in the following subsections. [I00016 - I00031.2]PEW
L.3.1.2ContentL29The Offeror’s proposal shall be comprehensive, concise, factual, and complete in order to provide a sound basis for evaluation by the Government.N/AW
L.3.1.2ContentL30The Offeror’s proposal shall be conformant with format instructions in this section (Section L) and the evaluation factors and subfactors described in Section M.N/AW
L.3.1.2.1CommunicationL31The Offeror shall direct all inquiries concerning the solicitation document to the Contracting Officer.PEW
L.3.1.2.1CommunicationL32The Offeror shall make no public announcements pertaining to this procurement without prior approval of the DOL Contracting Officer, unless required to do so by law or a court of competent jurisdiction, and then only in coordination with the Contracting OfficerTMW
L.3.1.2.2Writing StyleL33The Offeror shall write clearly and concisely and include sufficient detail for effective evaluation.TMW
L.3.1.2.2Writing StyleL34The Offeror shall provide a convincing rationale to address how the Offeror intends to meet these requirements (not simply rephrase or restate the Government’s requirements).PESW
L.3.1.2.2Writing StyleL35The Offeror shall assume the Government has no prior knowledge of its capabilities and experience, and that the Government will base its evaluation on the information presented in Offeror’s proposal.PEW
L.3.1.2.3Proposal ProductionL36The Offeror shall avoid the use of elaborate brochures or documentation, binding, detailed artwork, animation, special effects, or other embellishments for document, spreadsheets, presentations, etc.COSW
L.3.1.2.4Embedded GraphicsL37The Offeror shall simplify graphics embedded into documents, spreadsheets, or presentations as much as possible.PEW
L.3.1.2.5Page LimitationsL38The Offeror shall prepare documents within the page limitations specified in Table 2. [Proposal Organization Structure]PEW
L.3.1.2.6Page SizeL39The Offeror shall use the following standards: Page size of 8.5 by 11 inches, except for foldouts.PEW
L.3.1.2.6Page SizeL40The Offeror shall use the following standards: Margins no less than one inch on top and bottom and both sides.PEW
L.3.1.2.6Page SizeL41The Offeror shall use the following standards: Single spacing (not to exceed 46 lines per page).PESW
L.3.1.2.6Page SizeL42The Offeror shall use the following standards: Pages numbered sequentially by proposal volume.PEW
L.3.1.2.6Page SizeL43The Offeror shall not use typesetting, font compression, or other techniques (such as the MS Word feature of setting the paragraph line spacing to “exactly at 12 point”) to reduce character size or spacing.PESW
L.3.1.2.7GraphicsL44The Offeror shall limit these displays [tables, charts, graphs, and figures] to 11 by 17 inches in size.COW
L.3.1.2.7GraphicsL45The Offeror shall avoid the use of foldout pages for pages of text.COW
L.3.1.2.8Text SizeL46Offeror shall format text, headings, lists, tables, charts, graphs, figures, and captions such that the text is no smaller than Arial 12 point for paragraph text.COW
L.3.1.2.8Text SizeL47The Offeror shall format text, headings, lists, tables, charts, graphs, figures, and captions such that the text is no smaller than Arial 12 point bold with initial capitalization for paragraph heading text.COW
L.3.1.2.8Text SizeL48The Offeror shall format text, headings, lists, tables, charts, graphs, figures, and captions such that the text is no smaller than Arial 10 point for bulleted, numbered, or lettered, lists of text.COW
L.3.1.2.8Text SizeL49The Offeror shall format text, headings, lists, tables, charts, graphs, figures, and captions such that the text is no smaller than Arial 10 point for the content of tables, graphs, charts, or figures.N/A - Out of scope of proposal evaluationW
L.3.1.2.8Text SizeL50The Offeror shall format text, headings, lists, tables, charts, graphs, figures, and captions such that the text is no smaller than Arial 12 point bold with initial capitalization for the captions of tables, graphs, charts, or figures.N/A - Out of scope of proposal evaluationW
L.3.1.2.9Proprietary DataL51If an Offeror includes data in their proposals or quotations that they do not want disclosed to the public for any purposes or used by the DOL except for evaluation purposes, the Offeror shall mark the cover page with the following legend: “This proposal includes data that shall not be disclosed outside the Government and shall not be duplicated, used or disclosed - in whole or in part – for any purpose other than to evaluate this proposal. If, however, a contract is awarded to this Vendor as a result of – or in connection with – the submission of this data, the Government shall have the right to duplicate, use, or disclose the data to the extent provided in the resulting contract. This restriction does not limit the Government’s right to use information contained in this data if it is obtained from another source without restriction.”N/A - Out of scope of proposal evaluationW
L.3.1.2.9Proprietary DataL52If an Offeror includes data in their proposals or quotations that they do not want disclosed to the public for any purposes or used by the DOL except for evaluation purposes, the Offeror shall mark each sheet of data it wishes to restrict with the following legend: “Use or disclosure of data contained in this sheet is subject to the restriction on the title page of this proposal.”PEW
L.3.1.3MediaL53The Offeror shall submit their solicitation proposals or quotations and related data on high quality CD-DVD media (Windows format only) with an estimated shelf life of at least 7 years.COSW
L.3.1.3MediaL54The Offeror shall ensure that all submissions media are write-protectedCOSW
L.3.1.3MediaL55The Offeror shall include the following information on each submission: Offeror's Name.COSW
L.3.1.3MediaL56The Offeror shall include the following information on each submission: Releasing Government agency and office (USDOL OWCP).COSW
L.3.1.3MediaL57The Offeror shall include the following information on each submission: Name of effort (Workers' Compensation Medical Bill Process).COW
L.3.1.3MediaL58The Offeror shall include the following information on each submission: Solicitation number.COW
L.3.1.3MediaL59The Offeror shall include the following information on each submission: Date of proposal submission.COW
L.3.1.3MediaL60The Offeror shall include the following information on each submission: Proposal volume number(s) and name(s).COW
L.3.1.3MediaL61The Offeror shall include the following information on each submission: Classification level.COSW
L.3.1.3MediaL62The Offeror shall include the following information on each submission: Media Label: "<MediaNumber> of <MediaTotal>" (e.g., 1 of 3).N/AD
L.3.1.3MediaL63The Offeror shall ensure that subcontractor submissions, if provided, include the same information as above and additionally include the name of the prime contractor.N/AW
L.3.1.3MediaL64The Offeror shall screen all submissions for computer viruses and malware prior to submittal to the Government.COD
L.3.1.3MediaL65The Offerer shall also provide ten (10) hard copy (paper) printouts of its proposal.N/AW
L.3.1.4DeliveryL66The Offeror shall deliver three (3) electronic media copies and ten (10) hard copies of its proposal by courier, hand delivery, or priority (due to Departmental physical security restrictions) mail.COD
L.3.1.4DeliveryL67The Offeror shall deliver other solicitation communications by electronic mail (email) or one of the physical delivery methods outlined above.N/AW
L.3.1.4.2Mail DeliveryL68For solicitation proposals and other large volumes of data, or in the event of an email failure, the Offeror shall use the following address for submissions:

US Department of Labor OASAM, Business Operations Center Div 1, Office of Procurement Services 200 Constitution NW, S-4307

Washington, DC 20210COD
L.3.1.4.2Mail DeliveryL69For a mail delivery, the Offeror shall enclose the submission in sealed packages and mark the packages as specified below. [I00041.1 - I00041.4]COSW
L.3.1.4.2Mail DeliveryL70For each proposal package, the Offeror shall cite the following information on the outside of each package: Mailing Address.COSW
L.3.1.4.2Mail DeliveryL71For each proposal package, the Offeror shall cite the following information on the outside of each package: Solicitation Number.COSW
L.3.1.4.2Mail DeliveryL72For each proposal package, the Offeror shall cite the following information on the outside of each package: Offeror's Name: Offeror's Contracting Officer or designated procurement authority.COW
L.3.1.4.2Mail DeliveryL73For each proposal package, the Offeror shall cite the following information on the outside of each package: Offeror's Name: Offeror's Company.COW
L.3.1.4.2Mail DeliveryL74For each proposal package, the Offeror shall cite the following information on the outside of each package: Offeror's Name: Offeror's Address.COSW
L.3.1.4.2Mail DeliveryL75For each proposal package, the Offeror shall cite the following information on the outside of each package: Marking: Package ___ of ___ (e.g., 1 of 3 total packages submitted). Mark the package with the following instruction: ”DO NOT OPEN IN MAIL ROOM; TO BE OPENED BY PROCURING CONTRACTING OFFICER ONLY”.COSW / W
L.3.2Proposal OrganizationL76The Offeror shall structure the proposal as defined in Table 2. [Proposal Organization Structure]N/AW
L.3.2Proposal OrganizationL77In its proposal, the Offeror shall use the titles, contents, quantities, and page limits of the volume components, as defined in Table 2. [Proposal Organization Structure]. Note that the total page count for both Volume 3.1 (Technical) and Volume 4.1 (Management), when added together, is not to exceed (NTE) 180 pages.COD / SW
L.3.2.1.1Cover LetterL78The Offeror shall provide a cover letter that contains the following information: [I00045.1 - I00048.2]COD / SW
L.3.2.1.1Cover Letter: CertificationL79The Offeror shall include the following statements: “I hereby certify that the proposal provided with this letter contains an accurate recording of [Company Name]’s response to Request for Proposal and includes information sufficient to reproduce the original document, including signatures and other written and graphic images, completely, accurately, and clearly.COSW
L.3.2.1.1Cover Letter: CertificationL80The Offeror shall include the following statements: I further state that the proposal is firm for not less than 180 days from the proposal due date.”COSW
L.3.2.1.1Cover Letter: ComplianceL81The Offeror shall provide a statement of compliance indicating either complete compliance with the solicitation or a detailed analysis of any objections, exceptions, or contingencies to the terms of the solicitation. This statement may reference the Proposal Conformance Matrix or the Proposal Compliance Matrix for details.COSW
L.3.2.1.1Cover Letter: Business AddressL82The Offeror shall provide the complete business address of the OfferorCOSW
L.3.2.1.1Cover Letter: Business AddressL83The Offeror shall provide the corporate name to be used on any resultant contract; if this name does not identify a "parent company" or sponsoring "corporation" name, also provide such identity, as appropriate.COSW
L.3.2.1.1Cover Letter: Business AddressL84The Offeror shall provide the remittance address if different from that above.COD / SW
L.3.2.1.1Cover Letter: SignatureL85An appropriate company officer of the Offeror shall sign the cover letter.COSW
L.3.2.1.1Cover Letter: SignatureL86The Offeror shall submit the completed Cover Letter as part of the Proposal Volume (see Table 2). [Proposal Organization Structure]COD / SW
L.3.2.1.2Proposal File MatrixL87The Offeror shall provide a master table of contents for the entire proposal, in the form of the Proposal File Matrix, which provides a cross-reference from the proposal volume component structure (described in Table 2 [Proposal Organization Structure]) to the softcopy files on the submitted media.PEW
L.3.2.1.2Proposal File MatrixL88The Offeror shall prepare the Proposal File Matrix using the template from Section J.PEW
L.3.2.1.2Proposal File MatrixL89The Offeror shall store proposal volume components in the folders on the submitted media. Components of the same volume should be contained on the same media, but may span media for capacity reasons.PEW
L.3.2.1.2Proposal File MatrixL90The Offeror shall use a row of the template for each file that comprises a volume component (see the highlighted rows of the example in Table 3 [Proposal File Matrix Example]).COD / SW
L.3.2.1.2Proposal File MatrixL91For each proposal volume component, the Offeror shall insert the media label of the media on which it is located, the folder name in which it is located, and the filename(s) that constitute the component into the “Media Label”, Folder”, and “Filename(s)” columns in the Proposal File Matrix.COD / SW
L.3.2.1.2Proposal File MatrixL92The Offeror shall submit the completed Proposal File Matrix as part of the Proposal Volume (see Table 2 [Proposal Organization Structure]).PESW
L.3.2.1.3Proposal Conformance MatrixL93The Offeror shall prepare the “Proposal Conformance Matrix” using the “Proposal Conformance Matrix Template” of Section J.COD / SW
L.3.2.1.3Proposal Conformance MatrixL94The Offeror shall insert a proposal section and / or page reference(s) into the “Proposal Reference” column of each row of the [Conformance] matrix to indicate where the given instruction is satisfied.COD / SW
L.3.2.1.3Proposal Conformance MatrixL95The Offeror shall submit the completed Proposal Conformance Matrix as part of the Proposal Volume (see Table 2 [Proposal Organization Structure]).PESW
L.3.2.1.4Proposal Compliance MatrixL96The Offeror shall prepare the “Proposal Compliance Matrix” using the “Proposal Compliance Matrix Template” in Section J.PEW
L.3.2.1.4Proposal Compliance MatrixL97The Offeror shall insert a proposal reference(s) into the “Proposal Reference” column of each row of the [Conformance] matrix to indicate where the given requirement is satisfied.PESW
L.3.2.1.4Proposal Compliance MatrixL98The Offeror shall ensure that these references are as specific as possible, using section heading numbers, bullet list references, and/or page number, respectively in order of preference.COD / SW
L.3.2.1.4Proposal Compliance MatrixL99The Offeror shall also provide references to projects that demonstrate prior experience by inserting the “Unique Project Identifier” of such projects into the “Project Reference” column of any row of the [Conformance] matrix to which the prior experience applies (see Prior Experience, below).COW
L.3.2.1.4Proposal Compliance MatrixL100The Offeror shall submit the completed Proposal Compliance Matrix as part of the Proposal Volume (see Table 2 [Proposal Organization Structure]).PEW
L.3.2.1.5GlossaryL101The Offeror shall provide a volume containing a glossary of significant terms and all abbreviations and acronyms used, with an explanation for each.COSW
L.3.2.1.5GlossaryL102The Offeror shall alphabetically sort the contents of the glossary.COD / SW
L.3.2.1.5GlossaryL103The Offeror shall submit the completed Glossary as part of the Proposal Volume (see Table 2 [Proposal Organization Structure]).COD / SW
L.3.2.1.6Review Item Location MatrixL104The Offeror shall prepare the “Review Item Location Matrix” using the “Review Item Location Matrix Template” in Section J.
L.3.2.1.6Review Item Location MatrixL105The Offeror shall insert a proposal reference(s) into the “Proposal Reference” column of each row of the matrix to indicate where the given review item is addressed.COD / SW
L.3.2.1.6Review Item Location MatrixL106The Offeror shall ensure that these references are as specific as possible, using section heading numbers, bullet list references, and/or page number, respectively in order of preference.COD / SW
L.3.2.1.6Review Item Location MatrixL107The Offeror shall submit the completed Review Item Location Matrix as part of the Proposal Volume. (see Table 2 [Proposal Organization Structure]).COD / SW
L.3.2.1.7Incumbent ArtifactsL108In its proposal, the Offeror shall provide a list of all artifacts, required from an the incumbent contractor within 30 days of contract award, that are necessary to begin implementation activities for the purposes of assuming operations.COD
L.3.2.2Volume II - Contract VolumeL109The Offeror shall provide any fill-ins or certifications required by Sections A-K of the solicitation as part of the Contract Volume (see Table 2 [Proposal Organization Structure]).TMSW
L.3.2.3.1Technical NarrativeL110The Offeror shall submit the Technical Narrative as part of the Technical Volume (see Table 2 [Proposal Organization Structure]).TMSW
L.3.2.3.1Technical NarrativeL111The Offeror shall organize the Technical Narrative by the subsections of Section C; addressing all requirements in a way that communicates the Offeror’s understanding of the requirements.TMSW
L.3.2.3.1Technical NarrativeL112The Offeror shall organize the Technical Narrative by the subsections of Section C; addressing all requirements in a way that communicates the Offeror’s approach in satisfying the requirements.
L.3.2.3.1Technical NarrativeL113In its Technical Narrative and for each topic of particular interest to the Government below, the Offeror shall discuss its technical solution to satisfy the following requirements. The Offeror shall identify its responses to the topics of particular interest to the Government so that they may be easily referenced by the Government.
a. An effective and efficient phased approach for transitioning to WCMBP full operational capability.TMSW
L.3.2.3.1Technical NarrativeL114In its Technical Narrative and for each topic of particular interest to the Government below, the Offeror shall discuss its technical solution to satisfy the following requirements. The Offeror shall identify its responses to the topics of particular interest to the Government so that they may be easily referenced by the Government.
b. A comprehensive approach to capturing Government requirements, identifying gaps in Offeror’s solution, and satisfying Government requirements.TMSW
L.3.2.3.1Technical NarrativeL115In its Technical Narrative and for each topic of particular interest to the Government below, the Offeror shall discuss its technical solution to satisfy the following requirements. The Offeror shall identify its responses to the topics of particular interest to the Government so that they may be easily referenced by the Government.
c. A comprehensive and formal testing program.TMSW
L.3.2.3.1Technical NarrativeL116In its Technical Narrative and for each topic of particular interest to the Government below, the Offeror shall discuss its technical solution to satisfy the following requirements. The Offeror shall identify its responses to the topics of particular interest to the Government so that they may be easily referenced by the Government.
d. A discussion of the Offeror’s understanding of "Accepted Conditions", as a means to establish eligibility.TMSW
L.3.2.3.1Technical NarrativeL117In its Technical Narrative and for each topic of particular interest to the Government below, the Offeror shall discuss its technical solution to satisfy the following requirements. The Offeror shall identify its responses to the topics of particular interest to the Government so that they may be easily referenced by the Government.
e. A reasonable solution for how the Offeror will address the linkage between provider (group) billing and individual provider billing (i.e. when a provider is part of a group, how both the group and individual provider are simultaneously tracked).TMSW
L.3.2.3.1Technical NarrativeL118In its Technical Narrative and for each topic of particular interest to the Government below, the Offeror shall discuss its technical solution to satisfy the following requirements. The Offeror shall identify its responses to the topics of particular interest to the Government so that they may be easily referenced by the Government.
f. A sound plan to promote the use of Electronic Data Exchange (EDI) by providers who currently do not implement this technology.TMSW
L.3.2.3.1Technical NarrativeL119In its Technical Narrative and for each topic of particular interest to the Government below, the Offeror shall discuss its technical solution to satisfy the following requirements. The Offeror shall identify its responses to the topics of particular interest to the Government so that they may be easily referenced by the Government.
g. The indexing capabilities and volume capacities of any proposed imaging and indexing solutions.TMSW
L.3.2.3.1Technical NarrativeL120In its Technical Narrative and for each topic of particular interest to the Government below, the Offeror shall briefly discuss its technical solution to satisfy the following requirements. The Offeror shall identify its responses to the topics of particular interest to the Government so that they may be easily referenced by the Government.
h. A discussion of the Offeror’s Fraud and Abuse Detection solutionTMSW
L.3.2.3.1Technical NarrativeL121In its Technical Narrative and for each topic of particular interest to the Government below, the Offeror shall discuss its technical solution to satisfy the following requirements. The Offeror shall identify its responses to the topics of particular interest to the Government so that they may be easily referenced by the Government.

i. A discussion of the Offeror’s user interface approach to maximize ease of learning, ease of use, and user assistance.

L.3.2.4.1Management NarrativeL122The Offeror shall submit the Management Narrative as part of the Management Volume (see Table 2 [Proposal Organization Structure]).
L.3.2.4.1Management NarrativeL123The Offeror shall organize the Management Narrative by the subsections of Section C; addressing all requirements in a way that communicates the Offeror’s understanding of the requirements.
L.3.2.4.1Management NarrativeL124The Offeror shall organize the Management Narrative by the subsections of Section C; addressing all requirements in a way that communicates the Offeror’s approach in satisfying the requirements.
L.3.2.4.1Management NarrativeL125In its Management Narrative and for each topic of particular interest to the Government below, the Offeror shall discuss its technical solution to satisfy the following requirements. The Offeror shall identify its responses to the topics of particular interest to the Government so that they may be easily referenced by the Government.
a. A realistic schedule that meets the government's need for an implementation date based on a prioritized, time-phased approach.TMSW
L.3.2.4.1Management NarrativeL126In its Management Narrative and for each topic of particular interest to the Government below, the Offeror shall discuss its technical solution to satisfy the following requirements. The Offeror shall identify its responses to the topics of particular interest to the Government so that they may be easily referenced by the Government.

b. Key personnel that meet all PWS requirements.

L.3.2.4.1 Management Narrative L127 In its Management Narrativee and for each topic of particular interest to the Government below, the Offeror shall discuss its technical solution to satisfy the following requirements. The Offeror shall identify its responses to the topics of particular interest to the Government so that they may be easily referenced by the Government.

c. A realistic work breakdown structure that meets the government's need for transparent cost accounting.TMSW
L.3.2.4.1Management NarrativeL128In its Management Narrative and for each topic of particular interest to the Government below, the Offeror shall discuss its technical solution to satisfy the following requirements. The Offeror shall identify its responses to the topics of particular interest to the Government so that they may be easily referenced by the Government.
d. A realistic staffing plan, including ramp-up and training schedule, to support WCMBP project phases.TMSW
L.3.2.4.1Management NarrativeL129In its Management Narrative and for each topic of particular interest to the Government below, the Offeror shall discuss its technical solution to satisfy the following requirements. The Offeror shall identify its responses to the topics of particular interest to the Government so that they may be easily referenced by the Government.
e. A process for recruiting and retaining a team of qualified and experienced medical professionals, managers, customer service staff, technologists, and medical billing domain experts throughout the life of the contract in the face of turnover, attrition, and competing contract needs.TMSW
L.3.2.4.1Management NarrativeL130In its Management Narrative and for each topic of particular interest to the Government below, the Offeror shall discuss its technical solution to satisfy the following requirements. The Offeror shall identify its responses to the topics of particular interest to the Government so that they may be easily referenced by the Government.
f. A management process to control and report risk and performance against cost and schedule, including the use of corrective action plans in the event of project variances.TMSW
L.3.2.4.1Management NarrativeL131In its Management Narrative and for each topic of particular interest to the Government below, the Offeror shall discuss its technical solution to satisfy the following requirements. The Offeror shall identify its responses to the topics of particular interest to the Government so that they may be easily referenced by the Government.
g. A sound approach to notifying and assisting providers during transition from the incumbent’s operation.TMSW
L.3.2.4.1Management NarrativeL132In its Management Narrative and for each topic of particular interest to the Government below, the Offeror shall discuss its technical solution to satisfy the following requirements. The Offeror shall identify its responses to the topics of particular interest to the Government so that they may be easily referenced by the Government.
h. A teaming approach that minimizes the inherent risk to the Government by minimizing the number of teaming partners. If teaming is proposed, an integrated management approach that provides a common and consistent set of processes and procedures applied across all team members with a single team interface to the Government.TMSW
L.3.2.4.1Management NarrativeL133In its Management Narrative and for each topic of particular interest to the Government below, the Offeror shall discuss its technical solution to satisfy the following requirements. The Offeror shall identify its responses to the topics of particular interest to the Government so that they may be easily referenced by the Government.
i. A corporate organization chart and project organization chart that clearly delineate lines of authority, accountability, and responsibility, as well as a discussion of any applicable Capability Maturity Model Integration (CMMI) or International Standards Organization (ISO) accreditations for the business unit proposing the WCMBP solution.TMSW
L.3.2.4.1Management NarrativeL134In its Management Narrative and for each topic of particular interest to the Government below, the Offeror shall discuss its technical solution to satisfy the following requirements. The Offeror shall identify its responses to the topics of particular interest to the Government so that they may be easily referenced by the Government.
j. A discussion of project team’s access to corporate resources and the breadth and depth of resources available to the team.TMSW
L.3.2.4.1Management NarrativeL135In its Management Narrative and for each topic of particular interest to the Government below, the Offeror shall discuss its technical solution to satisfy the following requirements. The Offeror shall identify its responses to the topics of particular interest to the Government so that they may be easily referenced by the Government.
k. The proposed location of operational sites and proposed work schedule are consistent with WCMBP requirements.TMSW
L.3.2.4.1Management NarrativeL136In its Management Narrative and for each topic of particular interest to the Government below, the Offeror shall discuss its technical solution to satisfy the following requirements. The Offeror shall identify its responses to the topics of particular interest to the Government so that they may be easily referenced by the Government.
l. A discussion of the proposed, tested state-of-the art quality control processes.TMSW
L.3.2.4.2Key PositionsL137The Offeror shall identify and discuss Key Positions, as defined by the requirements of Section C.COD / SW
L.3.2.4.2Key PositionsL138The Offeror shall include the following information as part of the Management Volume (see Table 2 [Proposal Organization Structure]).PESW
L.3.2.4.3Key Positions: Key Position Background MatrixL139The Offeror shall prepare the “Key Position Background Matrix”, using the “Key Position Background Matrix Template” in Section J.COD / SW
L.3.2.4.3Key Positions: Key Position Background MatrixL140The Offeror shall include the name and position of key position candidates, their position(s) or title(s), role(s), and responsibilities for all of the contract references in the “Key Position Background Matrix”.PED / SW
L.3.2.4.3Key Positions: Key Position Background MatrixL141The Offeror shall submit the “Key Position Background Matrix”, as part of the Management Volume (see Table 2 [Proposal Organization Structure]).PESW
L.3.2.4.4Key Positions: Key Position ResumesL142For each Key Position, the Offeror shall provide a resume, using the “Key Position Resume Template” in Section J.PESW
L.3.2.4.4Key Positions: Key Position ResumesL143The Offeror shall clearly describe the individual’s relevant experience and qualifications for the position and should amplify the information in the matrices with current and relevant information on the candidate’s skills and experience.COD / SW
L.3.2.4.4Key Positions: Key Position ResumesL144The Offeror shall include the names and phone numbers of contacts for similar contracts for which proposed employees have worked in the past three years.PESW
L.3.2.4.4Key Positions: Key Position ResumesL145The Offeror shall submit a “Key Position Resume” for each Key Position, as part of the Management Volume (see Table 2 [Proposal Organization Structure]).N/AW
L.3.2.4.5Key Positions: Key Position Letter of CommitmentL146For any proposed individual that is not currently employed by the Offeror, the Offeror shall provide a letter offering employment to the individual (signed by an authorized corporate officer or representative having legal authority to bind the Offeror for performance of the WCMBP contract) and a signed acceptance letter from the individual. These letters shall include:

• The date of availability of the proposed individual

PEW
L.3.2.4.5Key Positions: Key Position Letter of CommitmentL147For any proposed individual that is not currently employed by the Offeror, the Offeror shall provide a letter offering employment to the individual (signed by an authorized corporate officer or representative having legal authority to bind the Offeror for performance of the WCMBP contract) and a signed acceptance letter from the individual. These letters shall include:

• The length of commitment of the individual to the WCMBP Project

COD
L.3.2.4.5Key Positions: Key Position Letter of CommitmentL148If, after submission of the Offeror’s proposal but prior to award, an individual designated as Key Position becomes unavailable, the Offeror shall promptly notify the Contracting Officer and update the proposal accordingly.PESW
L.3.2.4.6Project ScheduleL149The Offeror shall provide a project Gantt chart, derived from the WBS, with accompanying explanation that shows all major project and Offeror approach activities and milestones.
L.3.2.5.1Prior ExperienceL150The Offeror shall identify and discuss prior experience on Government and non-Government contracts that would qualify the Offeror, and any proposed subcontractors, and all persons proposed as key personnel to perform the work defined in Section C.PESW
L.3.2.5.2Prior Experience: Prior Experience Reference ListL151The Offeror shall prepare a “Prior Experience Reference List”, using the “Prior Experience Reference List Template” in Section J.PESW
L.3.2.5.2Prior Experience: Prior Experience Reference ListL152The Offeror shall provide information for all fields specified in the “Prior Experience Reference List”.PEW
L.3.2.5.2Prior Experience: Prior Experience Reference ListL153The Offeror shall ensure that all items listed in their “Prior Experience Reference List” are also listed in their “Past Performance Reference List”.PESW
L.3.2.5.2Prior Experience: Prior Experience Reference ListL154The Offeror shall include projects that demonstrate relevant experience, including each of up to the last ten (10) federal, state, or local government or commercial on-going or completed contracts within the last (5) yearsPEW
L.3.2.5.2Prior Experience: Prior Experience Reference ListL155If no relevant past or ongoing prior experience information exists, the Offeror shall check the box at the bottom of the “Prior Experience Reference List”, which says "The Offeror can cite no past or ongoing projects that provide relevant prior experience to this proposal.”PEW
L.3.2.5.2Prior Experience: Prior Experience Reference ListL156For each project reference on the list, the Offeror shall provide a “Unique Project Identifier” and use this “Unique Project Identifier” in all subsequent references to that project.PESW
L.3.2.5.2Prior Experience: Prior Experience Reference ListL157The Offeror shall construct the “Unique Project Identifier” for a Prior Experience project in the format “PEnnnn”, where ‘nnnn’ is a sequentially increasing integer starting with “0001”.PESW
L.3.2.5.2Prior Experience: Prior Experience Reference ListL158The Offeror shall use the “Unique Project Identifier” in the names of all electronic files related to a given project.COD
L.3.2.5.2Prior Experience: Prior Experience Reference ListL159The Offeror shall sort the reference list in descending order of relevancy (i.e. the most relevant contract listed first).COD
L.3.2.5.2Prior Experience: Prior Experience Reference ListL160The Offeror shall fill in the “Unique Project Identifier” in the “Project Reference” column of the “Proposal Compliance Matrix” (see L.3.2.1.4,”Proposal Compliance Matrix”), when a reference project demonstrates prior experience for a given requirement row of the [Conformance] matrix.PESW
L.3.2.5.2Prior Experience: Prior Experience Reference ListL161The Offeror shall provide contact information for each project referenced as specified. [I00095]COD
L.3.2.5.2Prior Experience: Prior Experience Reference ListL162The Offeror shall submit the “Prior Experience Reference List” as part of the Prior Experience Volume (see Table 2 [Proposal Organization Structure]).PEW
L.3.2.5.3Prior Experience: Prior Experience Project DescriptionL163The Offeror shall prepare a “Prior Experience Project Description” for each project referenced in the “Prior Experience Reference List“, using the “Prior Experience Project Description Template” of Section J.PED
L.3.2.5.3Prior Experience: Prior Experience Project DescriptionL164The Offeror shall provide information for all fields specified in the “Prior Experience Project Description Sheet”.PEW
L.3.2.5.3Prior Experience: Prior Experience Project DescriptionL165The Offeror shall submit a “Prior Experience Project Description” for each project referenced in the “Prior Experience Reference List”, as part of the Prior Experience Volume (see Table 2 [Proposal Organization Structure]).PESW
L.3.2.6Volume VI - Past PerformanceL166The Offeror shall identify and discuss Past Performance on Government and non-Government contracts that are relevant to the work defined in Section C.PEW
L.3.2.6.2Past Performance: Past Performance Reference ListL167The Offeror shall prepare a “Past Performance Reference List”, using the “Past Performance Reference List Template” in Section J.PESW
L.3.2.6.2Past Performance: Past Performance Reference ListL168The Offeror shall ensure that all items listed in their “Past Performance Reference List” are also listed in their “Prior Experience Reference List”.PEW
L.3.2.6.2Past Performance: Past Performance Reference ListL169The Offeror shall include projects that demonstrate relevant experience, including each of up to the last ten (10) federal, state, or local government or commercial on-going or completed contracts within the last (5) years.PEW
L.3.2.6.2Past Performance: Past Performance Reference ListL170If no relevant past or ongoing Past Performance information exists, the Offeror shall check the box at the bottom of the “Past Performance Reference List”, which says "The Offeror can cite no past or ongoing projects that provide past performance to this proposal.”PEW
L.3.2.6.2Past Performance: Past Performance Reference ListL171For each project reference on the list, the Offeror shall provide a “Unique Project Identifier” and shall use this “Unique Project Identifier” in all subsequent references to that project.COD
L.3.2.6.2Past Performance: Past Performance Reference ListL172The Offeror shall construct the “Unique Project Identifier” for Past Performance projects in the format “PPnnnn”, where ‘nnnn’ is a sequentially increasing integer starting with “0001”.PED
L.3.2.6.2Past Performance: Past Performance Reference ListL173The Offeror shall use the “Unique Project Identifier” in the names of all electronic files related to a given project.PESW
L.3.2.6.2Past Performance: Past Performance Reference ListL174The Offeror shall sort the reference list in descending order of relevancy (i.e. the most relevant contract listed first).COD
L.3.2.6.2Past Performance: Past Performance Reference ListL175The Offeror shall structure the Past Performance Reference List, such that the references for the prime contract and major subcontractor(s) are listed in order from highest to lowest according to the amount (in dollars) of work proposed for each.COD
L.3.2.6.2Past Performance: Past Performance Reference ListL176The Offeror shall submit the “Past Performance Reference List” as part of the Past Performance Volume (see Table 2 [Proposal Organization Structure]).PESW
L.3.2.6.3Past Performance: Past Performance Contact SheetL177The Offeror shall prepare a “Past Performance Contact Sheet” for each Past Performance reference, using the “Past Performance Contact Sheet Template” in Section J.COD / SW
L.3.2.6.3Past Performance: Past Performance Contact SheetL178The Offeror shall provide information for all fields specified in the “Past Performance Contact Sheet”.COW
L.3.2.6.3Past Performance: Past Performance Contact SheetL179The Offeror shall submit a “Past Performance Contact Sheet” for each project referenced in the “Past Performance Reference List”, as part of the Past Performance Volume (see Table 2 [Proposal Organization Structure]).COW
L.3.2.6.4Past Performance: Past Performance QuestionnaireL180The Offeror shall prepare “Past Performance Questionnaires”, using the “Past Performance Questionnaire Template" in Section J.PETSW
L.3.2.6.4Past Performance: Past Performance QuestionnaireL181The Offeror shall provide information for all fields in Parts I and II in the “Past Performance Questionnaire”. The customer referenced in the “Past Performance Questionnaire” shall provide the information in Part III.PETSW
L.3.2.6.4Past Performance: Past Performance QuestionnaireL182The Offeror shall submit a completed “Past Performance Questionnaire” for each past performance reference listed in the Past Performance Volume (see Table 2 [Proposal Organization Structure]).PETW
L.3.2.6.5Past Performance: Past Performance Subcontractor Consent LetterL183For each proposed subcontractor, the Offeror shall provide a “Past Performance Subcontractor Consent Letter” (signed by the subcontractor), using the “Past Performance Subcontractor Consent Letter Template” provide in Section J.PETW
L.3.2.6.5Past Performance: Past Performance Subcontractor Consent LetterL184The Offeror shall submit a “Past Performance Subcontractor Consent Letter” for each subcontractor referenced in any “Past Performance Questionnaire”, as part of the Past Performance Volume (see Table 2 [Proposal Organization Structure]).N/AW
L.3.2.7Volume VII - PriceL185The Offeror shall submit data substantiating the pricing proposed to implement the requirements of Section C.
L.3.2.7Volume VII - PriceL186The Offeror shall provide sufficient factual information to establish the fairness, reasonableness, and balance of the proposed price.
L.3.2.7Volume VII - PriceL187The Offeror shall provide price data only in the Price Volume and the Contract Volume.COD
L.3.2.7Volume VII - PriceL188The Offeror shall use trade-off information, work-hour estimates, and material kinds and quantities in other volumes only as appropriate for presenting rationale to support a technical or management position, or unless otherwise specified in this section.COD
L.3.2.7Volume VII - PriceL189The Offeror shall include the following information in the Price Volume (see Table 2 [Proposal Organization Structure]).[I00131 - I00140]COD / SW
L.3.2.7.1Schedule of Supplies or Services and Prices/CostsL190The Offeror shall propose and provide prices for all CLINs, using the definitions in Section B as a basis of estimate.PETSW
L.3.2.7.1Schedule of Supplies or Services and Prices/CostsL191The Offeror shall use the Volume-Sensitive Operational Data table of Section B as a basis for the pricing of its WCMBP solution
L.3.2.7.1Schedule of Supplies or Services and Prices/CostsL192The Offeror shall prepare price build-up information to communicate the cost of requirements satisfaction for each CLIN.
L.3.2.7.1Schedule of Supplies or Services and Prices/CostsL193The Offeror shall prepare one “Schedule of Supplies or Services and Prices/Costs” using the “Attachment 1 - Schedule of Supplies or Services and Prices/Costs Template” in Section JPETSW
L.3.2.7.1Schedule of Supplies or Services and Prices/CostsL194The Offeror shall submit price build-up information for each CLIN in the price build-up tab of Attachment 1, associated with that CLIN.
COD
L.3.2.7.1Schedule of Supplies or Services and Prices/CostsL195The Offeror shall use the predefined fields and formulas in the price build-up tab for each CLIN.PETSW
L.3.2.7.1Schedule of Supplies or Services and Prices/CostsL196The Offeror shall verify that all submitted prices link properly to all CLIN grand totals and the Summary tabPETSW

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated .