Attachment 2- Fort Combat Kansas Sample Task Order Instructions.pdf
PDF 143 KB Posted
- Solicitation number
- W91RUS
View the file
Other files
Show all 46
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
ATTACHMENT 2
MISSION SUPPORT SUBFACTOR 4 - SAMPLE TASK ORDER INSTRUCTIONS
SAMPLE TASK ORDER SUBMISSION INSTRUCTIONS – FORT COMBAT, KANSAS
Assume an IMCS IV contract has been awarded to your company. Prepare a proposal that accomplishes the requirements in the Fort Combat, Kansas Performance Work Statement (Attachment 3). Your company will be evaluated in accordance with the instructions below and the Basis for Award found in the Solicitation documents. Please remember the page limit for the Mission Support Factor is 55 pages. The limit for the Sample Task Order is 30 pages and the remaining Sub-factors under Mission Support are 25 pages for a total of 55 pages.
1. The U.S. Army has a requirement for Information Management Communications Services (IMCS) at Fort Combat, Kansas, in support of the Network Enterprise Center (NEC). The period of performance is scheduled to begin 01 July 2021 with a 12 month base period and four one year option periods.
Sample Task Order Period of Performance:
Base Period: 01 July 2021 to 30 June 2022 Option Year One: 01 July 2022 to 30 June 2023 Option Year Two: 01 July 2023 to 30 June 2024 Option Year Three: 01 July 2024 to 30 June 2025 Option Year Four: 01 July 2025 to 30 June 2026 52.217-8 Extension -6 Months 01 July 2026 - 31 December 2026
2. Submit a written technical proposal in consideration of the Performance Work Statement, DD 254, and the Service Contract Act/ Davis-Bacon Act wage determinations.
3. A page is defined as each face of a sheet of paper containing information. When both sides of a sheet display printed material, it shall be counted as two pages. Unless otherwise indicated, each page shall be counted except as indicated in paragraph c, Page Limit Exceptions, below. Page limitations shall be treated as maximums. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal.
a. Page size shall be 8.5 x 11 inches, not including foldouts. Pages may be single-spaced but shall have at least double spacing between paragraphs and factors. Except for the reproduced sections of the solicitation document, Attachment 11 (Pricing Worksheet), and items specified in paragraph (b) below, the text size shall be no less than 12 point, Times New Roman type. Tracking, kerning, and leading values shall not be changed from the default values of the word processing or page layout software. Use at least one-inch margins on all sides. Pages shall be numbered sequentially by volume, with each volume starting at page one.
b. Legible tables, charts, graphs, drawings, and diagrams may be used wherever practical to depict organizations, systems and layouts, implementation schedules, and plans. Arial, size 10 font shall be used for tables, charts, graphics, drawings, and diagrams. Tables, charts, graphics, drawings, or diagrams appearing to contain narrative ordinarily used for technical approach, technical methodology, or technical solutions will be redacted and not considered for evaluation, or the entire proposal will be rejected at the Government's discretion.
c. Page Limit Exceptions. The following documents are excluded from the page limitation requirements as described in the table above and, further, do not require page numbering: cover page, table of contents, glossary, compliance matrices, indices, list of tables, list of acronyms, staffing worksheets, labor category descriptions, Past Performance List of References, and the Price volume and worksheets.
d. Offeror’s need not address the paragraphs found in the “Part 1 General” portion of the
PWS as part of their Technical Proposal. The Offeror’s Statement of Compliance will serve as acknowledgement regarding the “Part 1 General” portion of the PWS.
e. The Tools, Equipment, and Vehicle List shall be provided as a separate attachment to the
Technical Proposal. The Tools, Equipment, and Vehicle List will not be counted against the page limitation for the Technical Proposal; however the list should be reasonable in length to adequately identify the tools, equipment, and vehicles necessary to support the requirement. Include vehicles’ minimum year, make, and model information. In lieu of make/model information you can provide a description of the vehicles’ characteristics and capabilities. Do not include any other information in this attachment as it WILL NOT be evaluated.
SAMPLE TASK ORDER TECHNICAL PROPOSAL
The Sample Task Order Proposal shall consist of a written narrative that is the Offeror’s proposed solution to the requirement contained in the Fort Combat, Kansas Sample Task Order Performance Work Statement (PWS). The technical and critical services discussions should be practical, straightforward, specific, concise, and complete.
Offerors shall demonstrate an understanding of the tasks required through a comprehensive discussion of each of the following:
1. Critical Services Factor – The Offeror’s proposal shall demonstrate a thorough understanding of the following critical areas. The services provided to these areas are essential to the NEC’s mission and merit special consideration.
a. Information Technology (IT) Systems Support C.2.5.2 Desktop/ Software/Peripheral Services/Release Management and Password Management, C.2.5.5 Management of Data Network Services, C.2.5.9 Remedy Administration, C.2.5.10 Information Technology Analysis and C.2.5.10.1 IT Analysis. Offeror shall demonstrate its approach to administration, troubleshooting, and documenting of the Campus Area Networks (CANs) to include routers and switches, necessary to operate and maintain networks which encompass, but are not limited to, NIPRNET, SIPRNET, networks, Wireless (secure/non-secure with WIDS), and VPN.
b. Telecommunication Support Services (C.2.6 and associated sub paragraphs). The technical narrative shall address the offeror’s management approach and proposed technical solution to provide support for Enterprise Classified voice over Internet Protocol Systems (ECVoIP) in coordination with DISA and NETCOM. The offeror shall also address their approach for operation and maintenance of Integrated Access Devices (IAD) connected into the VoIP environment supporting Unified Communications.
c. Vehicle Requirements. The proposal shall include vehicles with capabilities to perform the described mission through all four seasons as described above at Fort Combat. Fort Combat’s terrain varies from a common cantonment area to geographically dispersed training areas with hills, mountains and forested areas. Other areas includes test ranges that model multiple terrain scenarios. Include vehicles’ make, model, and year information.
2. Technical Approach (need not include PWS paragraphs covered 2.12 (QCP), 2.13 (QA), 2.16 Third Party Damages). The Offeror’s proposal shall include its technical solution that fulfills, and demonstrates, an understanding of the Government’s requirements. Parroting or merely reiterating the objectives or reformulate the requirements specified in the solicitation or the PWS will result in the proposal being removed from consideration for award. The Offeror’s proposal shall acknowledge an understanding of the remaining Performance Work Statement requirements (this include any paragraphs not addressed in the critical areas or specifically stated throughout the Sample Task Order Proposal Instructions) and affirmatively state that it possess the capabilities, technical skills, and experience necessary to perform the work listed in all the functional areas.
3. SEE SOLICITAION PROPOSAL INSTRUCTIONS FOR PRICING INSTRUCTION AND
EVALAUATION CRITERIA.
File details come from the government source that posted it. Updated .