WCMBP_Section_J_Attachment_4_-_Conformance_Matrix_AMD_3.xlsx
XLSX spreadsheet 41 KB Posted
- Attached to
- Solicitation Notice for Workers' Compensation Medical Bill Processing (WCMBP) Federal contract opportunity
- Solicitation number
- DOL141RP21903
About this file
Section J - Attachment 4 Conformance Matrix
View the file
Other files for this federal contract opportunity
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 Number | Section Name | Instruction Identifier | Instruction Text | Proposal Reference | Complies | Exception/Deviation | Comments/Explanations |
| Identifies the section number of the instruction | Identifies the instruction to which the proposal must conform | Identify section and/or page number(s) in the proposal where the instruction is satisfied | Yes or No | Identify if the proposal identifies an exception or deviation to the requirement | Discuss relevant issues. (e.g., if the proposal does not address the instructions, describe the rationale and impact of non-conformance) |
| L.1 | Solicitation Provisions Incorporation | L1 | The 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) |
| L.1 | Solicitation Provisions Incorporation | L2 | The 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) |
| L.1 | Solicitation Provisions Incorporation | L3 | The 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) |
| L.1 | Solicitation Provisions Incorporation | L4 | The 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) |
| L.1 | Solicitation Provisions Incorporation | L5 | The 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) |
| L.2.5 L.2.4 | Proposal Acceptance | L6 | The Offeror shall make a clear statement in the proposal of the date of its validity. |
| L.3 | Proposal Preparation Instructions | L7 | The Offeror shall include in its proposal, all data and information required by this section (L.3). |
| L.3 | Proposal Preparation Instructions | L8 | The Offeror shall submit its proposal in accordance with these instructions. |
| L.3 | Proposal Preparation Instructions | L9 | The Offeror shall ensure all pricing information is provided in Volume VII (under separate tab) including submission of Subcontracting Plan. |
| L.3.1 | Electronic Solicitation Responses | L10 | The Offeror shall construct all solicitation responses following the instructions for construction in section L.3.1.1. |
| L.3.1 | Electronic Solicitation Responses | L11 | The Offeror shall construct all solicitation responses following the instructions for content in section L.3.1.2. |
| L.3.1 | Electronic Solicitation Responses | L12 | The Offeror shall construct all solicitation responses following the instructions for using electronic media in section L.3.1.3. |
| L.3.1 | Electronic Solicitation Responses | L13 | The Offeror shall construct all solicitation responses following the instructions for delivery in section L.3.1.4. |
| L.3.1 | Electronic Solicitation Responses | L14 | The Offeror shall deliver all solicitation responses proposals to the Contracting Officer according to Table 1. [Solicitation Due Dates] |
| L.3.1.1.1 | File Types and Formats | L15 | The Offeror shall present information in a solicitation response using file type and formats, such that text and graphics are readable by Microsoft Word 2010. |
| L.3.1.1.1 | File Types and Formats | L16 | The 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.1 | File Types and Formats | L17 | The 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. |
| L.3.1.1.1 | File Types and Formats | L18 | The 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.1 | File Types and Formats | L19 | The Offeror shall use only Microsoft Word versions 2010 for presenting revised proposal text and graphics (with change tracking enabled). |
| L.3.1.1.1 | File Types and Formats | L20 | The Offeror shall use only Microsoft Excel 2010 or earlier for price reporting (with no change tracking). |
| L.3.1.1.2 | File Names | L21 | The Offeror shall name files using consistent naming conventions that clearly identify the file. |
| L.3.1.1.2 | File Names | L22 | The Offeror shall store each proposal file in a folder that corresponds to the proposal volume it represents. |
| L.3.1.1.2 | File Names | L23 | The 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. |
| L.3.1.1.2 | File Names | L24 | The Offeror shall insert the file name in the header of each document. |
| L.3.1.1.3 | Content Safeguards | L25 | The Offeror shall save all proposal files with macros and links either disabled or removed. |
| L.3.1.1.3 | Content Safeguards | L26 | The Offeror shall not establish password protection on proposal files. |
| L.3.1.1.3 | Content Safeguards | L27 | The Offeror shall ensure that Spreadsheet files allow for the viewing of cell contents and embedded formulas. |
| L.3.1.2 L.3.1.1 | Content | L28 | The Offeror shall construct the solicitation responses proposals using the instructions in the following subsections. [I00016 - I00031.2] |
| L.3.1.2 L.3.1.1 | Content | L29 | The Offeror’s proposal shall be comprehensive, concise, factual, and complete in order to provide a sound basis for evaluation by the Government. |
| L.3.1.2 L.3.1.1 | Content | L30 | The Offeror’s proposal shall be conformant with format instructions in this section (Section L) and the evaluation factors and subfactors described in Section M. |
| L.3.1.2.1 | Communication | L31 | The Offeror shall direct all inquiries concerning the solicitation document to the Contracting Officer. |
| L.3.1.2.1 | Communication | L32 | The 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 Officer |
| L.3.1.2.2 L.3.1.1.1 | Writing Style | L33 | The Offeror shall write clearly and concisely and include sufficient detail for effective evaluation. |
| L.3.1.2.2 L.3.1.1.1 | Writing Style | L34 | The 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). |
| L.3.1.2.2 L.3.1.1.1 | Writing Style | L35 | The Offeror shall assume the Government has no prior knowledge of its capabilities and experience, and that the Government will base its evaluation solely on the information presented in Offeror’s proposal. |
| L.3.1.1.2 L.3.1.2.3 | Proposal Production | L36 | The Offeror shall avoid the use of elaborate brochures or documentation, binding, detailed artwork, animation, special effects, or other embellishments for document, spreadsheets, presentations, etc. |
| L.3.1.1.3 L.3.1.2.4 | Embedded Graphics | L37 | The Offeror shall simplify graphics embedded into documents, spreadsheets, or presentations as much as possible. |
| L.3.1.1.4 L.3.1.2.5 | Page Limitations | L38 | The Offeror shall prepare documents proposals within the page limitations specified in Table 2. [Proposal Organization Structure] |
| L.3.1.1.5 L.3.1.2.6 | Page Size | L39 | The Offeror shall use the following standards: Page size of 8.5 by 11 inches, except for foldouts. |
| L.3.1.1.5 L.3.1.2.6 | Page Size | L40 | The Offeror shall use the following standards: Margins no less than one inch on top and bottom and both sides. |
| L.3.1.1.5 L.3.1.2.6 | Page Size | L41 | The Offeror shall use the following standards: Single spacing (not to exceed 46 lines per page). |
| L.3.1.1.5 L.3.1.2.6 | Page Size | L42 | The Offeror shall use the following standards: Pages numbered sequentially by proposal volume. |
| L.3.1.1.5 L.3.1.2.6 | Page Size | L43 | The 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. |
| L.3.1.1.6 L.3.1.2.7 | Graphics | L44 | The Offeror shall limit these displays [tables, charts, graphs, and figures] to 11 by 17 inches in size. |
| L.3.1.1.6 L.3.1.2.7 | Graphics | L45 | The Offeror shall avoid the use of foldout pages for pages of text. |
| L.3.1.1.7 L.3.1.2.8 | Text Size | L46 | Offeror 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. |
| L.3.1.1.7 L.3.1.2.8 | Text Size | L47 | The 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. |
| L.3.1.1.7 L.3.1.2.8 | Text Size | L48 | The 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. |
| L.3.1.1.7 L.3.1.2.8 | Text Size | L49 | The Offeror shall format text, headings, lists, tables, charts, graphs, figures, and captions such that the text is no smaller than Arial 8 10 point for the content of tables, graphs, charts, or figures. |
| L.3.1.1.7 L.3.1.2.8 | Text Size | L50 | The 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. |
| L.3.1.1.8 L.3.1.2.9 | Proprietary Data | L51 | If 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.” |
| L.3.1.1.8 L.3.1.2.9 | Proprietary Data | L52 | If 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.” |
| L.3.1.3 L.3.1.2 | Media | L53 | The 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. |
| L.3.1.3 L.3.1.2 | Media | L54 | The Offeror shall ensure that all submissions media are write-protected. |
| L.3.1.3 L.3.1.2 | Media | L55 | The Offeror shall include the following information on each submission: Offeror's Name. |
| L.3.1.3 L.3.1.2 | Media | L56 | The Offeror shall include the following information on each submission: Releasing Government agency and office (USDOL OWCP). |
| L.3.1.3 L.3.1.2 | Media | L57 | The Offeror shall include the following information on each submission: Name of effort (Workers' Compensation Medical Bill Process). |
| L.3.1.3 L.3.1.2 | Media | L58 | The Offeror shall include the following information on each submission: Solicitation number. |
| L.3.1.3 L.3.1.2 | Media | L59 | The Offeror shall include the following information on each submission: Date of proposal submission. |
| L.3.1.3 L.3.1.2 | Media | L60 | The Offeror shall include the following information on each submission: Proposal volume number(s) and name(s). |
| L.3.1.3 L.3.1.2 | Media | L61 | The Offeror shall include the following information on each submission: Classification level. |
| L.3.1.3 L.3.1.2 | Media | L62 | The Offeror shall include the following information on each submission: Media Label: "<MediaNumber> of <MediaTotal>" (e.g., 1 of 3). |
| L.3.1.3 L.3.1.2 | Media | L63 | The Offeror shall ensure that subcontractor submissions, if provided, include the same information as above and additionally include the name of the prime contractor. |
| L.3.1.3 L.3.1.2 | Media | L64 | The Offeror shall screen all submissions for computer viruses and malware prior to submittal to the Government. |
| L.3.1.3 L.3.1.2 | Media | L65 | The Offerer shall also provide ten (10) hard copy (paper) printouts of its proposal. |
| L.3.1.4 L.3.1.3 | Delivery | L66 | The Offeror shall submit one (1) redacted CD-DVD copy of Volume 1: Technical and one(1) unredacted CD-DVD copy of Volume 1: Technical, Volume 2: Prior Experience, Volume 3: Past Performance and Volume 4: Pricing and ten (10) hard copies of its proposal by courier, hand delivery, or priority (due to Departmental physical security restrictions) mail. |
| L.3.1.4 L.3.1.3 | Delivery | L67 | Offerors shall submit ten (10) redacted hard copies of Volume 1: Technical and one (1) unredacted hard copy of Volume 1: Technical, Volume 2: Prior Experience, Volume 3: Past Performance and Volume 4: Pricing. The Offeror shall deliver other solicitation communications by electronic mail (email) or one of the physical delivery methods outlined above. |
L.3.1.3 L.3.1.4.2 Mail Delivery L68 Offers submitted by express mail services (FEDEX, UPS, DHL, etc.) shall be submitted to:
Ms. Myla Gale and Mr. Elvis Colbert U.S. Department of Labor OASAM-OPS, Room S-4307 200 Constitution Avenue, NW Washington, DC 20210 For 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 Attn: Ms. Myla Gale Div 1, Office of Procurement Services 200 Constitution NW, S-4307 Washington, DC 20210 L.3.1.3 Delivery L228 Offers submitted through US Postal Service shall be mailed to the following address:
Ms. Myla Gale and Mr. Elvis Colbert U.S. Department of Labor OASAM-OPS, Room S-4307 200 Constitution Avenue, NW Washington, DC 20210
| L.3.1.4.1 L.3.1.4.2 | Mail Delivery | L69 | For a mail delivery, the Offeror shall enclose the submission in sealed packages and mark the packages as specified below. [I00041.1 - I00041.4] |
| L.3.1.4.1 L.3.1.4.2 | Mail Delivery | L70 | For each proposal package, the Offeror shall cite the following information on the outside of each package: Mailing Address. |
| L.3.1.4.1 L.3.1.4.2 | Mail Delivery | L71 | For each proposal package, the Offeror shall cite the following information on the outside of each package: Solicitation Number. |
| L.3.1.4.1 L.3.1.4.2 | Mail Delivery | L72 | For 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. |
| L.3.1.4.1 L.3.1.4.2 | Mail Delivery | L73 | For each proposal package, the Offeror shall cite the following information on the outside of each package: Offeror's Name: Offeror's Company. |
| L.3.1.4.1 L.3.1.4.2 | Mail Delivery | L74 | For each proposal package, the Offeror shall cite the following information on the outside of each package: Offeror's Name: Offeror's Address. |
| L.3.1.4.1 L.3.1.4.2 | Mail Delivery | L75 | For 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”. |
| L.3.2 | Proposal Organization | L76 | The Offeror shall structure the proposal as defined in Table 2. [Proposal Organization Structure] |
| L.3.2 | Proposal Organization | L77 | In 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 Section 1.9 (Technical Narrative) and Section 1.10 (Management Narrative), when added together, is not to exceed (NTE) 180 pages. |
| L.3.2.1 | Proposal Organization | L226 | The Offeror shall not include any price information in the Technical Volume. |
| L.3.2.1.1 | Cover Letter | L78 | The Offeror shall provide a cover letter that contains the following information: [I00045.1 - I00048.2] |
| L.3.2.1.1 | Cover Letter: Certification | L79 | The 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. |
| L.3.2.1.1 | Cover Letter: Certification | L80 | The 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.” |
| L.3.2.1.1 | Cover Letter: Compliance | L81 | The 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. |
| L.3.2.1.1 | Cover Letter: Business Address | L82 | The Offeror shall provide the complete business address of the Offeror |
| L.3.2.1.1 | Cover Letter: Business Address | L83 | The 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. |
| L.3.2.1.1 | Cover Letter: Business Address | L84 | The Offeror shall provide the remittance address if different from that above. |
| L.3.2.1.1 | Cover Letter: Signature | L85 | An appropriate company officer of the Offeror shall sign the cover letter. |
| L.3.2.1.1 | Cover Letter: Signature | L86 | The Offeror shall submit the completed Cover Letter as part of the Technical Proposal Volume (see Table 2). [Proposal Organization Structure] |
| L.3.2.1.2 | Proposal File Matrix | L87 | The 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. |
| L.3.2.1.2 | Proposal File Matrix | L88 | The Offeror shall prepare the Proposal File Matrix using the template from Section J. |
| L.3.2.1.2 | Proposal File Matrix | L89 | The 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. |
| L.3.2.1.2 | Proposal File Matrix | L90 | The 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]). |
| L.3.2.1.2 | Proposal File Matrix | L91 | For 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. |
| L.3.2.1.2 | Proposal File Matrix | L92 | The Offeror shall submit the completed Proposal File Matrix as part of the Technical Proposal Volume (see Table 2 [Proposal Organization Structure]). |
| L.3.2.1.3 | Proposal Conformance Matrix | L93 | The Offeror shall prepare the “Proposal Conformance Matrix” using the “Proposal Conformance Matrix Template” of Section J. |
| L.3.2.1.3 | Proposal Conformance Matrix | L94 | The 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. |
| L.3.2.1.3 | Proposal Conformance Matrix | L95 | The Offeror shall submit the completed Proposal Conformance Matrix as part of the Technical Proposal Volume (see Table 2 [Proposal Organization Structure]). |
| L.3.2.1.4 | Proposal Compliance Matrix | L96 | The Offeror shall prepare the “Proposal Compliance Matrix” using the “Proposal Compliance Matrix Template” in Section J. |
| L.3.2.1.4 | Proposal Compliance Matrix | L97 | The 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. |
| L.3.2.1.4 | Proposal Compliance Matrix | L98 | The 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. |
| L.3.2.1.4 | Proposal Compliance Matrix | L99 | The 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). |
| L.3.2.1.4 | Proposal Compliance Matrix | L100 | The Offeror shall submit the completed Proposal Compliance Matrix as part of the Technical Proposal Volume (see Table 2 [Proposal Organization Structure]). |
| L.3.2.1.5 | Glossary | L101 | The Offeror shall provide a section volume containing a glossary of significant terms and all abbreviations and acronyms used, with an explanation for each. |
| L.3.2.1.5 | Glossary | L102 | The Offeror shall alphabetically sort the contents of the glossary. |
| L.3.2.1.5 | Glossary | L103 | The Offeror shall submit the completed Glossary as part of the Technical Proposal Volume (see Table 2 [Proposal Organization Structure]). |
| L.3.2.1.6 | Review Item Location Matrix | L104 | The Offeror shall prepare the “Review Item Location Matrix” using the “Review Item Location Matrix Template” in Section J. |
| L.3.2.1.6 | Review Item Location Matrix | L105 | The 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. |
| L.3.2.1.6 | Review Item Location Matrix | L106 | The 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. |
| L.3.2.1.6 | Review Item Location Matrix | L107 | The Offeror shall submit the completed Review Item Location Matrix, when submitting a revised proposal, as part of the Technical Volume. (see Table 2 [Proposal Organization Structure]). |
| L.3.2.1.7 | Required Incumbent Artifacts | L108 | In 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. |
| L.3.2.2 | Volume II - Contract Volume Technical Proposal | L109 | The 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]). |
| L.3.2.3.1 L.3.2.1.8 | Technical Narrative | L110 | The Offeror shall submit the Technical Narrative as part of the Technical Volume (see Table 2 [Proposal Organization Structure]). |
| L.3.2.3.1 L.3.2.1.8 | Technical Narrative | L111 | The 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. |
| L.3.2.3.1 L.3.2.1.8 | Technical Narrative | L112 | The 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.1.8 | Technical Narrative | L227 | In 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. All assumptions, constraints, and exceptions regarding the offeror’s proposed solution to meet all requirements.
L.3.2.3.1 L.3.2.1.8 Technical Narrative L113 In 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. An effective and efficient phased approach for transitioning to WCMBP full operational capability.
L.3.2.3.1 L.3.2.1.8 Technical Narrative L114 In 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 approach to capturing Government requirements, identifying gaps in Offeror’s solution, and satisfying Government requirements.
L.3.2.3.1 L.3.2.1.8 Technical Narrative L115 In 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 comprehensive and formal testing program.
L.3.2.3.1 L.3.2.1.8 Technical Narrative L116 In 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 discussion of the Offeror’s understanding of "Accepted Conditions", as a means to establish claimant eligibility.
L.3.2.3.1 L.3.2.1.8 Technical Narrative L117 In 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 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).
L.3.2.3.1 L.3.2.1.8 Technical Narrative L118 In 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. A sound plan to promote the use of Electronic Data Exchange (EDI) by providers who currently do not implement this technology.
L.3.2.3.1 L.3.2.1.8 Technical Narrative L119 In 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.
h. The indexing capabilities and volume capacities of any proposed imaging and indexing solutions.
L.3.2.3.1 L.3.2.1.8 Technical Narrative L120 In 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.
i. A discussion of the Offeror’s Fraud and Abuse Detection solution L.3.2.3.1 L.3.2.1.8 Technical Narrative L121 In 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.
j. A discussion of the Offeror’s user interface approach to maximize ease of learning, ease of use, and user assistance.
| L.3.2.4.1 L.3.2.1.9 | Management Narrative | L122 | The Offeror shall submit the Management Narrative as part of the Technical Management Volume (see Table 2 [Proposal Organization Structure]). |
| L.3.2.4.1 L.3.2.1.9 | Management Narrative | L123 | The 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.1 L.3.2.1.9 | Management Narrative | L124 | The 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.1 L.3.2.1.9 | Management Narrative | L125 | In 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.
L.3.2.4.1 L.3.2.1.9 Management Narrative L126 In 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. If applicable, Offerors should indicate which proposed key personnel worked on which prior experience projects listed on the Prior Experience Reference List.
L.3.2.4.1 L.3.2.1.9 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.
L.3.2.4.1 L.3.2.1.9 Management Narrative L128 In 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.
L.3.2.4.1 L.3.2.1.9 Management Narrative L129 In 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.
L.3.2.4.1 L.3.2.1.9 Management Narrative L130 In 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.
L.3.2.4.1 L.3.2.1.9 Management Narrative L131 In 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.
L.3.2.4.1 L.3.2.1.9 Management Narrative L132 In 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.
L.3.2.4.1 L.3.2.1.9 Management Narrative L133 In 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.
L.3.2.4.1 L.3.2.1.9 Management Narrative L134 In 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.
L.3.2.4.1 L.3.2.1.9 Management Narrative L135 In 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.
L.3.2.4.1 L.3.2.1.9 Management Narrative L136 In 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.
| L.3.2.4.2 L.3.2.1.10 | Key Positions | L137 | The Offeror shall identify and discuss Key Positions, as defined by the requirements of Section C. |
| L.3.2.4.2 L.3.2.1.10 | Key Positions | L138 | The Offeror shall include the following information as part of the Technical Management Volume (see Table 2 [Proposal Organization Structure]). |
| L.3.2.4.3 | Key Positions: Key Position Background Matrix | L139 | The Offeror shall prepare the “Key Position Background Matrix”, using the “Key Position Background Matrix Template” in Section J. |
| L.3.2.4.3 | Key Positions: Key Position Background Matrix | L140 | The 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”. |
| L.3.2.4.3 | Key Positions: Key Position Background Matrix | L141 | The Offeror shall submit the “Key Position Background Matrix”, as part of the Management Volume (see Table 2 [Proposal Organization Structure]). |
| L.3.2.4.4 L.3.2.1.11 | Key Positions: Key Position Resumes | L142 | For each Key Position, the Offeror shall provide a resume, using the “Key Position Resume Template” in Section J. |
| L.3.2.4.4 L.3.2.1.11 | Key Positions: Key Position Resumes | L143 | The 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. |
| L.3.2.4.4 L.3.2.1.11 | Key Positions: Key Position Resumes | L144 | The Offeror shall include the names and phone numbers of contacts for similar contracts for which proposed employees have worked in the past three years. |
| L.3.2.4.4 L.3.2.1.11 | Key Positions: Key Position Resumes | L145 | The Offeror shall submit a “Key Position Resume” for each Key Position, as part of the Technical Management Volume (see Table 2 [Proposal Organization Structure]). |
| L.3.2.4.5 L.3.2.1.12 | Key Positions: Key Position Letter of Commitment | L146 | For 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—this may be a single letter with both signatures. Thisese letters shall include: |
• The date of availability of the proposed individual
L.3.2.4.5 L.3.2.1.12 Key Positions: Key Position Letter of Commitment L147 For 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—this may be a single letter with both signatures. Thisese letters shall include:
• The length of commitment of the individual to the WCMBP Project
| L.3.2.4.5 L.3.2.1.12 | Key Positions: Key Position Letter of Commitment | L148 | If, 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. |
| L.3.2.4.6 L.3.2.1.13 | Project Schedule | L149 | The Offeror shall provide a project Gantt chart, derived from the WBS, with accompanying explanation narrative that shows explains all major project and Offeror approach activities and milestones. |
| L.3.2.5.1 L.3.2.1.14 | Volume II - Prior Experience | L150 | The 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. |
| L.3.2.5.2 L.3.2.1.15 | Prior Experience: Prior Experience Reference List | L151 | The Offeror shall prepare a “Prior Experience Reference List”, using the “Prior Experience Reference List Template” in Section J. |
| L.3.2.5.2 L.3.2.1.15 | Prior Experience: Prior Experience Reference List | L152 | The Offeror shall provide information for all fields specified in the “Prior Experience Reference List”. |
| L.3.2.5.2 L.3.2.1.15 | Prior Experience: Prior Experience Reference List | L153 | The Offeror shall ensure that all items listed in their “Prior Experience Reference List” are also listed in their “Past Performance Reference List”. |
| L.3.2.5.2 L.3.2.1.15 | Prior Experience: Prior Experience Reference List | L154 | The Offeror shall include projects that demonstrate relevant experience, including the last five (5) 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. |
| L.3.2.5.2 L.3.2.1.15 | Prior Experience: Prior Experience Reference List | L155 | If 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.” |
| L.3.2.5.2 L.3.2.1.15 | Prior Experience: Prior Experience Reference List | L156 | For 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. |
| L.3.2.5.2 L.3.2.1.15 | Prior Experience: Prior Experience Reference List | L157 | The 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”. |
| L.3.2.5.2 L.3.2.1.15 | Prior Experience: Prior Experience Reference List | L158 | The Offeror shall use the “Unique Project Identifier” in the names of all electronic files related to a given project. |
| L.3.2.5.2 L.3.2.1.15 | Prior Experience: Prior Experience Reference List | L159 | The Offeror shall sort the reference list in descending order of relevancy (i.e. the most relevant contract listed first). |
| L.3.2.5.2 L.3.2.1.15 | Prior Experience: Prior Experience Reference List | L160 | The 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. |
| L.3.2.5.2 L.3.2.1.15 | Prior Experience: Prior Experience Reference List | L161 | The Offeror shall provide contact information for each project referenced as specified. [I00095] |
| L.3.2.5.2 L.3.2.1.15 | Prior Experience: Prior Experience Reference List | L162 | The Offeror shall submit the “Prior Experience Reference List” as part of the Prior Experience Volume (see Table 2 [Proposal Organization Structure]). |
| L.3.2.5.3 L.3.2.1.16 | Prior Experience: Prior Experience Project Description | L163 | The 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. |
| L.3.2.5.3 L.3.2.1.16 | Prior Experience: Prior Experience Project Description | L164 | The Offeror shall provide information for all fields specified in the “Prior Experience Project Description Sheet”. |
| L.3.2.5.3 L.3.2.1.16 | Prior Experience: Prior Experience Project Description | L165 | The 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]). |
| L.3.2.6 L.3.2.1.17 | Volume III - Past Performance | L166 | The Offeror shall identify and discuss Past Performance on Government and non-Government contracts that are relevant to the work defined in Section C. |
| L.3.2.6.2 L.3.2.1.18 | Past Performance: Past Performance Reference List | L167 | The Offeror shall prepare a “Past Performance Reference List”, using the “Past Performance Reference List Template” in Section J. If the offeror has additional Past Performance references that do not correspond to Prior Experience, that is acceptable. |
| L.3.2.6.2 L.3.2.1.18 | Past Performance: Past Performance Reference List | L168 | Past performance references shall be listed for all prior experience. Additional past performance references up to the allowable limit may be considered. The Offeror shall ensure that all items listed in their “Past Performance Reference List” are also listed in their “Prior Experience Reference List”. |
| L.3.2.6.2 L.3.2.1.18 | Past Performance: Past Performance Reference List | L169 | The Offeror shall ensure that all items listed in their “Past Performance Reference List” are also listed in their “Prior Experience Reference List. |
| L.3.2.6.2 L.3.2.1.18 | Past Performance: Past Performance Reference List | L170 | If no relevant past or ongoing Past Performance information exists, the Offeror shall check the box at the bottom of of Attachment 11 located in Section J. the “Past Performance Reference List”, which says "The Offeror can cite no past or ongoing projects that provide past performance to this proposal.” |
| L.3.2.6.2 L.3.2.1.18 | Past Performance: Past Performance Reference List | L171 | For 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. |
| L.3.2.6.2 L.3.2.1.18 | Past Performance: Past Performance Reference List | L172 | The 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”. |
| L.3.2.6.2 L.3.2.1.18 | Past Performance: Past Performance Reference List | L173 | The Offeror shall use the “Unique Project Identifier” in the names of all electronic files related to a given project. |
| L.3.2.6.2 L.3.2.1.18 | Past Performance: Past Performance Reference List | L174 | The Offeror shall sort the reference list in descending order of relevancy (i.e. the most relevant contract listed first). |
| L.3.2.6.2 L.3.2.1.18 | Past Performance: Past Performance Reference List | L175 | The 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. |
| L.3.2.6.2 L.3.2.1.18 | Past Performance: Past Performance Reference List | L176 | The Offeror shall submit the “Past Performance Reference List” as part of the Past Performance Volume (see Table 12 [Proposal Organization Structure]). |
| L.3.2.6.3 L.3.2.1.19 | Past Performance: Past Performance Contact Sheet | L177 | The Offeror shall prepare a “Past Performance Contact Sheet” for each Past Performance reference, using the “Past Performance Contact Sheet Template” in Section J. |
| L.3.2.6.3 L.3.2.1.19 | Past Performance: Past Performance Contact Sheet | L178 | The Offeror shall provide information for all fields specified in the “Past Performance Contact Sheet”. |
| L.3.2.6.3 L.3.2.1.19 | Past Performance: Past Performance Contact Sheet | L179 | The 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 12). |
| L.3.2.6.4 L.3.2.1.20 | Past Performance: Past Performance Questionnaire | L180 | The Offeror shall prepare “Past Performance Questionnaires”, using the “Past Performance Questionnaire Template" in Section J. |
| L.3.2.6.4 L.3.2.1.20 | Past Performance: Past Performance Questionnaire | L181 | The 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. |
| L.3.2.6.4 L.3.2.1.20 | Past Performance: Past Performance Questionnaire | L182 | The Offeror shall submit a completed “Past Performance Questionnaire” for each past performance reference listed in the Past Performance Volume (see Table 12 [Proposal Organization Structure]). |
| L.3.2.6.5 L.3.2.1.21 | Past Performance: Past Performance Subcontractor Consent Letter | L183 | For 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. |
| L.3.2.6.5 L.3.2.1.21 | Past Performance: Past Performance Subcontractor Consent Letter | L184 | The 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]). |
| L.3.2.7 L.3.2.2 | Volume IVII - Price Volume | L185 | The Offeror shall submit data substantiating the pricing proposed to implement the requirements of Section C. |
| L.3.2.7 L.3.2.2 | Volume IVII - Price Volume | L186 | The Offeror shall provide sufficient factual information to establish the fairness, reasonableness, realism, and balance of the proposed price. |
| L.3.2.7 L.3.2.2 | Volume IVII - Price Volume | L187 | The Offeror shall provide price data only in the Price Volume and the Contract Volume. |
| L.3.2.7 L.3.2.2 | Volume IVII - Price Volume | L188 | The Offeror shall use trade-off information, work-hour estimates, and material kinds and quantities in other sections volumes only as appropriate for presenting rationale to support a technical or management position, or unless otherwise specified in this section. |
| L.3.2.7 L.3.2.2 | Volume IVII - Price Volume | L189 | The Offeror shall include the following information in the Price Volume (see Table 12[Proposal Organization Structure]).[I00131 - I00140] |
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 .