Atch 8_ITO_NetOps SB.doc

PART IV - REPRESENTATIONS AND INSTRUCTIONS

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO OFFERORS____________________________

L055 INFORMATION TO OFFERORS (ITO) AND INSTRUCTIONS FOR PROPOSAL PREPARATION (IFPP) (JAN 2010)

L1.0 PROGRAM STRUCTURE AND OBJECTIVES

See Section J, Performance Work Statement.

L2.0 GENERAL INSTRUCTIONS

(a) This section provides general guidance for preparing proposals as well as specific instructions on the format and content of the proposal. The offeror's proposal must include all data and information stated herein and must be submitted in accordance with these instructions. Non conformance with the instructions provided may result in an unfavorable proposal evaluation. All proposed technical, management, performance and schedule capabilities to meet the requirements shall be realistic and are subject to verification by the Government. The proposal shall be compliant with the requirements as stated in the PWS and Solicitation/Model Contract. The proposal shall be unclassified.

(b) The offeror's proposal shall consist of the written submittal. All information provided by the offeror (as long as it is consistent with the constraints of this RFP, e.g., page limitations) is subject to evaluation as described in Section M. The Government will not award individual CLINs in the RFP to any one contractor, but shall award ALL CLINs. Proposals for a single CLIN, or group thereof, shall be rejected.

(c) The completion and submission of all proposal volumes constitutes the offeror's acceptance to the terms and conditions in this RFP and in any attachments thereto. Proposals shall be late IAW FAR 15.208 if they are not received by the date specified in L2.3 Proposal Format, paragraph (b).

(d) The Government may consider any offeror's exception to the terms and conditions in this RFP to be a deficiency, which may render the offer unacceptable.

L2.0.1 Proposal Clarity The proposals shall be clear, concise, and shall include sufficient detail for effective evaluation substantiating the validity of stated claims. The proposal should not simply rephrase or restate the Government's requirements, but shall provide convincing rationale to address how the offeror intends to meet these requirements. Offerors shall assume that the Government has no prior knowledge of their capabilities and experience, and will base its evaluation on the information presented in the offeror's proposal. The Government intends to evaluate proposals and award contracts without discussions, but reserves the right to conduct discussions if the Contracting Officer later determines them to be necessary.

L2.0.2 Proposal Acceptance Period

The offeror shall make a clear statement in the Contract Documentation Volume V that the proposal is valid for a period of not less than 365 days from receipt.

L2.0.3 Disposition of Unsuccessful Proposals In accordance with FAR Subpart 4.8 (Government Contract Files), the Government will retain the original copy of all unsuccessful proposals. Unless the offeror requests otherwise, the Government will destroy extra copies of such unsuccessful proposals.

L2.1 GENERAL INFORMATION

L2.1.1 Point of Contact

Randi E. Williams, PCO - NETCENTS-2, is the point of contact for this acquisition. Address any questions or concerns to her. Written requests for clarification may be sent via e-mail to the PCO at randi.williams@gunter.af.mil. Official RFP documentation, including RFP amendments, and other related information will be available on the Internet at http://public.gunter.af.mil/aq/netcents/2/ , HTTP://HERBB.HANSCOM.AF.MIL and https://www.fbo.gov/.

L2.1.2 Debriefings

Pre-award notices of exclusion from competitive range: The contracting officer will notify offerors promptly in writing when their proposals are excluded from the competitive range or otherwise eliminated from the competition. IAW FAR 15.505, the offeror may request a pre-award debriefing by submitting a written request for debriefing to the contracting officer within 3 days after receipt of the notice of exclusion from the competition. At the offeror’s request, this debriefing may be delayed until after award. If the debriefing is delayed until after award, it shall include all information normally provided in a post-award debriefing (see 15.506(d)). The contracting officer shall make every effort to debrief the unsuccessful offeror as soon as practicable, but may refuse the request for a debriefing if, for compelling reasons, it is not in the best interests of the Government to conduct a debriefing at that time.

Post-award notices: Within 3 days after the date of contract award, the contracting officer will provide written notification to each offeror whose proposal was in the competitive range but was not selected for award or had not been previously notified. An offeror, upon its written request received by the agency within 3 days after the date on which that offeror has received notification of contract award in accordance with 15.503(b), shall be debriefed and furnished the basis for the selection decision and contract award. To the maximum extent practicable, the debriefing should occur within 5 days after receipt of the written request. Offerors that requested a post-award debriefing in lieu of a pre-award debriefing, or whose debriefing was delayed for compelling reasons beyond contract award, also should be debriefed within this time period. An offeror that was notified of exclusion from the competition (see 15.505(a)), but failed to submit a timely request, is not entitled to a debriefing.

L2.1.3 Discrepancies

If an offeror believes that the requirements in these instructions contain an error, omission, or are otherwise unsound, the offeror shall immediately notify the PCO in writing with supporting rationale as well as the remedies the offeror is asking the PCO to consider as related to the omission or error. (NOTE: Add the following sentence unless FAR 52.215-1(f) Alternate I applies, i.e., unless you have indicated that you intend to have discussions.)

L2.1.4 Electronic Reference Documents

All referenced documents for this solicitation are available on NETCENTS-2 web site at http://public.gunter.af.mil/aq/netcents/2/. (If any necessary documents are not available on FedBizOpps, provide instructions on how potential offerors may obtain those documents (e.g., posted on FedTeds, or use of a Reading Room).)

L2.1.5 Distribution/Submission/Proposal Volumes One complete set of "original" volumes and all other copies IAW Table 1 shall be clearly marked, addressed and mailed, or hand-carried, to the PCO at the following address by 18 November 2010, 12:00 PM (CST):

RANDI E. WILLIAMS

PCO, NETCENTS-2

HQ ESC/HIJK

501 EAST MOORE DR.

BLDG 884, ROOM 1400

MAXWELL AFB - GUNTER ANNEX, AL 36114

NOTE: ALL official mail must have the return address and the addressee in ALL CAPS. Mail that is not properly addressed will be returned for correction by the Official Mail Center (OMC).

L2.1.6 SECTION K - REPRESENTATIONS AND CERTIFICATIONS

IAW FAR 52.204-08, contractor shall submit completed representations, certifications, acknowledgments and statements in compliance with the Online Representation and Certification Application (ORCA) requirements.

L2.1.7 Communications

(See Section L Guide, paragraph 3.3 for specifics on this Paragraph.)

Exchanges of source selection information between government and offerors will be controlled by the PCO. Encrypted e-mail may be used to transmit such information to offerors, and must include “Source Selection Information – See FAR 2.101 and 3.104” in the Subject line.

L2.2 ORGANIZATION/DISTRIBUTION/NUMBER OF COPIES/PAGE LIMITS

(a) The offeror shall prepare the proposal as set forth in Table 1 below. The titles and contents of the volumes should be as defined in Table 1, and shall be within the required page limits and in the number of copies as specified in the table. The contents of each proposal volume are described in the paragraphs noted in Table 1.

(b) Page limitations shall be treated as maximums. If exceeded, the excess pages will not be read or considered in the evaluation of the submission and may be returned to the offeror (i.e., paper copies) as soon as practicable. Each page shall be counted except the following; any Cover Sheets, Table of Contents, Tabs, Glossaries of terms/abbreviations/acronyms, cross reference matrix, resumes and organizational charts. All pages shall be numbered. Sheets printed on both sides shall be numbered on both sides if both sides contain information.

(c) Virus free CDs or DVDs (one volume copy per CD/DVD), shall be encased in a vinyl CD/DVD protector sheet for three-ring binders, and placed in each of their corresponding volume. Indicate on each CD/DVD the volume, title and company name. Offerors shall not password protect any documents. In the event hard copy and soft copy contents conflict, hard copies will take precedence over soft copies. Soft copies shall be compatible with Microsoft Office 2003 or later. Adobe Acrobat 8.0 (or better) format is also acceptable.

(d) Forward one paper copy and one CD/DVD of proposal Volumes I, II, III, IV and V to your cognizant Defense Contract Audit Agency (DCAA) when the PCO copies are delivered. (Submission of proposal volumes to DCAA does not constitute submission of the proposal for evaluation). Failure to provide information to the locations as specified will result in a delay in the evaluation and may negatively affect the evaluation of the offeror's proposal. Be sure to advise DCAA that the proposal is "For Official Use Only" and contains "Source Selection Information - See FAR 52.215-01(e) and 3.104."

Original & 1 paper copy; 2 CDs/DVDs

Original & 2 paper copies; 2 CDs/DVDs

Quality Processes (Reference Section J, Atch 1, Para 7)

Metadata Environments Development

total as part of the Technical Proposal (not including pricing) Included in the Technical Proposal copies

Information Sheets

(PPIS)

Table of Contents (not counted in total)

PPIS - 4 page limit per contract and up to 10 contracts for a total of 40 pages max Original & 1 paper copy; 2 CDs /DVDs

limit Original & 1 paper copy; 2 CDs/DVDs

Table 1- Proposal Organization NOTE: Volume 1 - Executive Summary will not be part of the NETCENTS-2 evaluation.

L2.3 Proposal Format

(a) The offeror's proposal must include all data and information requested herein and must be submitted in accordance with these instructions. The offer shall be compliant with the requirements as stated in the RFP. Nonconformance with the RFP may result in an unfavorable proposal evaluation.

(b) All proposal volumes shall be due 18 November 2010, 12:00 PM (CST).

(c) Elaborate brochures, presentations or documentation, binding, detailed artwork, or other embellishments are unnecessary and are not desired.

L2.3.1 Binding and Labeling

Each volume of the proposal should be separately bound in a three-ring, loose leaf binder permitting the volume to lie flat when open. Staples shall not be used. Binders sent with the proposal shall not contain any markings or graphics (inside or outside), nor any insertions in the spine. A cover sheet should be bound in each book, clearly marked as to volume number, title, copy number, solicitation identification, and the offeror's name. All unclassified document binders shall have a color other than red. Be sure to apply all appropriate markings including those prescribed in accordance with FAR 52.215-1(e), Restriction on Disclosure and Use of Data, and 3.104-4, Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection Information.

Horseblankets shall be clearly marked with the offeror’s name, solicitation number and copy number.

L2.3.2 Page Format Restrictions

(a) Page size shall be 8.5 x 11 inches, not including foldouts. Pages shall be single-spaced. The specified page limits for EN responses will be identified in the letters forwarding the ENs to the offerors. See paragraph L2.3.4 below for additional guidance regarding foldouts. Except for the reproduced sections of the solicitation document, the font size shall be no less than Times New Roman ten (10) point. Use at least 1- inch margins on the top and bottom and 3/4 inch side margins. Pages shall be numbered sequentially by volume. For tables, charts, graphs and figures, the font shall be no smaller than eight (8) points.

(b) Page limitations may be placed on responses to Evaluation Notices (ENs).

L2.3.3 Indexing

Each volume shall contain a detailed table of contents to delineate the subparagraphs within that volume. Tab indexing shall be used to identify sections.

L2.3.4 Foldouts

Legible tables, charts, graphs and figures may be used wherever practical to depict organizations, systems and layout, implementation schedules, plans, etc. These displays shall be legible, easy to follow and shall not exceed 11 by 17 inches in size, with the exception of the Horseblanket, which shall be “E size” drawing in accordance with the CITS ITS Firm Fixed Price Sample Task Order. Foldout pages shall fold entirely within the volume and count as two pages. Foldout pages may only be used for large tables, charts, graphs, diagrams and schematics, not for pages of text. For tables, charts, graphs and figures, the font shall be no smaller than eight (8) point.

L2.3.5 Cross Referencing

(a) To the greatest extent possible, each volume shall be written on a stand‑alone basis so that its contents may be evaluated with a minimum of cross referencing to other volumes of the proposal. Information required for proposal evaluation which is not found in its designated volume will be assumed to have been omitted from the proposal.

or:

(If you require the offeror to develop the matrix, add:)

(b) Cross Reference matrix does not count against the page limitations for their respective volumes.

L2.3.6 Cost or Pricing Information

All cost or pricing information shall be addressed ONLY in the Cost/Price Proposal Volume. Cost trade‑off information, work‑hour estimates, and material kinds and quantities may be used in other volumes only as appropriate for presenting rationale for alternatives or design and trade‑off decisions.

L2.3.7 Glossary of Abbreviations and Acronyms

Each volume shall contain a glossary of all abbreviations and acronyms used, and with an explanation for each. Glossaries do not count against the page limitations for their respective volumes.

L3.0 VOLUME I - EXECUTIVE SUMMARY

L3.1 Format and Specific Contents

L3.1.1 Summary

A concise executive summary of the entire proposal shall be provided including a highlight of any key or unique features, excluding cost. This should be a “big picture” explanation and provide the offeror’s overall approach for the management/operation of the NETCENTS-2 NetOps & Infrastructure Solutions requirements, including proposed subcontractors and/ or teaming arrangements. Identify if this proposal is being submitted as a Joint Venture. The following table shall be included for the prime and 1st tier subcontractor:

Material presented in the Executive Summary shall not be considered towards meeting the requirements for any portions of other volumes of the proposal.

L3.1.2 Table of Contents Include a Master Table of Contents for the entire proposal.

L4.0. VOLUME II – TECHNICAL PROPOSAL

L4.1 General

The purpose of the Technical Proposal Volume is to provide the Government the ability to evaluate the technical capability of the offeror to perform the NETCENTS-2 NetOps & Infrastructure Solutions requirements.

L4.2 Format and Specific Content

L4.2.1 Technical Proposal

In the Technical Proposal Volume, address your proposed approach to meeting the performance or capability requirements of each technical proposal subfactor. The offeror’s technical proposal shall be specific and complete. Legibility, clarity, and coherence are very important. The offeror’s technical proposal should provide as specifically as possible the actual methodologies that will be used. All the requirements specified in the solicitation are mandatory. Through proposal submission, the offeror represents that it will fulfill the requirements specified in the solicitation; therefore, it is not necessary or desirable for an offeror to state this in the proposal. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation. The technical proposal shall not include price information, classified information, or "For Official Use Only" information. The Technical Proposal Volume will be used to evaluate the technical acceptability of the offeror’s proposal. Evaluation will be against the technical acceptability subfactors as specified in Section M of this RFP.

L4.2.2 Volume Organization

The Technical Proposal Volume shall contain the information in tabbed sections IAW the following outline:

1) Table of Contents

2) List of Table and Drawings

3) Glossary

4) Subfactor 1 – Quality Processes

5) Subfactor 2 – Metadata Environments Development

6) Subfactor 3 – Network Management and Network Defense (NM/ND) Cost Reimbursable Sample Task Order

7) Subfactor 4 – CITS Information Transport Systems (ITS) Firm Fixed Price Sample Task Order

8) Subfactor 5 – Management Approach

9) Cross Reference Matrix

L4.2.3 Subfactor 1 - Quality Processes

The prime contractor shall provide proof of certification (copy of certificate with initial proposal submission) of ISO 9001:2000 or ISO 9001:2008 or ISO/IEC 20000, or of being appraised at Level 2 (or higher) for CMMI Development using the Software Engineering Institute’s (SEI) Standard CMMI Appraisal Method for Process Improvement (SCAMPI) (Method A) by an SEI-authorized lead appraiser, or are extensively documented to achieve a comparable level of quality and are routinely and verifiably followed. This certification must be held at the prime offeror’s organizational level performing the contract. If not ISO certified or SEI appraised, acceptable documentation shall describe all salient Systems Engineering (SE) processes, including requirements management, configuration management, development of specifications, definition and illustration of architectures and interfaces, design, test and evaluation/verification and validation, deployment and maintenance. If not ISO certified or SEI appraised, the offeror shall also provide evidence of the incorporation of automated processes and tools utilized in the offeror’s SE processes.

L4.2.4 Subfactor 2 – Metadata Environments Development

The offeror shall describe an approach to the development of the four critical components of metadata environments presented below. The offeror shall describe the methodology and associated processes, tools, and techniques required to accomplish the following:

1. Create eXtensible Markup Language (XML)-based metadata catalogs (content stores for metacards containing discovery metadata) IAW DoD Discovery Metadata Specification (DDMS)V3.0 pre-release. The offeror shall include in the proposal its methodology/approach to building or configuring a software product to enable the discovery of DDMS AF extensions metadata cards based on XML.

2. Design and implement a metadata population service for assigning metadata values to discoverable assets. The offeror shall include in the proposal its methodology/approach to building and/or configuring a software product to allow an operator to manually populate DDMS elements based on XML payloads, Web Ontology Language (OWL) files, and XML Schema Definition (XSD) files.

3. Create metadata registries. The contractor shall address how to create runtime metadata registries for storing semantic vocabulary artifacts such as OWL files, XML schemata (XSD), and namespaces. The proposal should address the approach for the registry to contain vocabulary assets and services that support delivery of those assets. It should also address how to store definitions of data elements in the metadata catalogs and how to house semantic and representative information.

4. Describe how metadata will support discovery of data. The contractor shall address how to approach indexing, query processing, relevance calculation, and result presentation services.

L4.2.5 Subfactor 3 – Network Management/Network Defense (NM/ND) Cost Reimbursable Sample Task Order

The offeror shall provide a proposal for the task order summarized below and provided in detail in Section J, Attachment 20 of the RFP.

Summary Description of NM/ND Remote Application Management System (RAMS) Cost Reimbursable Sample Task Order

The RAMS is an operations center concept that enables centralized monitoring, management, administration and configuration control of Network Control Centers (NCC) applications in a standardized fashion. NCC applications are defined by the Air Force IT community as central components and embody the seamless, secure, and reliable transport of timely and trusted information across the AF-GIG. Several RAMS will be instantiated to provide AF Network Situation Awareness (SA) to the Integrated Network Operations Security Center (I-NOSC) on the status of applications and have the capability to notify Major Commands (MAJCOM) of problems with services that could affect operational missions.

The offeror shall propose methodologies, processes, tools (if additional are proposed) and techniques for meeting the following requirements. For the purposes of this evaluation each respondent will limit their proposed solution to include ONLY the following critical components of the solution:

1. Management and Monitoring of a Service. The offeror shall provide a recommended approach for remotely managing, monitoring, and administering the following critical existing Air Force applications from a centralized location:

(a) Microsoft Exchange

(b) Blackberry Services

(c) Microsoft Office Communicator

(d) SharePoint Enterprise Content/Information Management

2. Situational Awareness (SA). SA enables operators to understand the current situation and how changes will impact the mission. The offeror shall provide a recommended approach for accomplishing critical SA requirements. The RAMS SA solution shall:

(a) Leverage existing data from the I-NOSC and other existing sources to create the RAMS SA.

(b) Be capable of user filtering of alerts and events from network devices, servers, ancillary applications, and managed applications.

(c) Provide a visualization of server performance, managed application performance, performance of managed application dependencies, network performance, and the correlation between the four.

(d) Detect and pinpoint the source of abnormal network, server, managed application, and interdependent component behavior within one hundred twenty (120) seconds after faults occur within the Air Force enterprise by correlating data that may be obtained through examination of error logs and monitoring internal to the RAMS solution and/or external to the RAMS via the I-NOSC.

(e) Provide alerts to the SA View for viewing immediately upon reception of the alert and within the constraints of the user specified update rate IAW the Sample Task Order

(f) Provide operators with a picture of fused, correlated data from aggregated data sources.

(g) Comply with the display commonality requirement from MIL-STD1472F paragraph 5.1.2.1.1.5: when multiple displays and multiple display formats are used, nomenclature and symbology should be common on all displays.

(h) Display information in a geospatial context when requested by the user.

(i) Use color coding consistently and sparing within and across displays and applications, as per MIL-STD-1472F paragraph 5.2.1.5.6.1.

3. Virtual Infrastructure (VI). A critical component of the RAMS solution is the ability to accomplish critical VI support activities. The RAMS Virtual Infrastructure consolidates enterprise network management and defense capabilities into a single integrated configuration based on a common virtual infrastructure. The solution is intended to support all information systems operating on AF managed networks. The offeror will provide a recommended approach for accomplishing critical VI requirements. The RAMS VI solution shall:

(a) Provide tier-1 storage for all RAMS systems configuration data for thirteen (13) months of historical data.

(b) Provide tier-2 storage for twenty four (24) months of historical RAMS data.

(c) Provide backup capabilities.

4. Enterprise Requirements. A critical component of the RAMS solution is the ability to support enterprise requirements. For purposes of this evaluation, those requirements specific to the transfer and reporting of information between tools within the RAMS and the transfer of data and information to and from the I-NOSC. The offeror will provide a recommended approach for accomplishing the following critical management functions. The transfer of data will include the following requirements:

(a) SOAP-based web services shall conform to the Web Services Interoperability (WS-I) Basic Profile 1.1

(b) All HTTP-based services shall be uniquely identified using Uniform Resource Identifiers (URIs).

(c) XML instance documents shall declare their encoding style.

(d) XML instance documents shall reference a registered namespace in the DoD Metadata Registry.

(e) XML documents shall be validated using their XML schema.

5. The offeror shall provide the knowledge, abilities, skills (to include the skill level) and products (if additional are proposed) needed to accomplish the requirements identified in the task order. The offeror shall use the Work Breakdown Structure (WBS) provided in Attachment 21 to indicate the estimated level of effort and type of labor used, to include the appropriate mix of labor categories, for the requirements of this sample task. This information shall be provided to Level 4 of the WBS.

L4.2.6 Subfactor 4 - CITS Information Transport Systems (ITS) Firm Fixed Price Sample Task Order

The offeror shall provide a proposal describing an approach, methodology and associated processes, tools, and techniques required to accomplish the work in the sample task order summarized below and provided in detail in Section J, Attachment 14 of the RFP.

Summary Description of CITS ITS Firm Fixed Price Sample Task Order

The offeror’s proposal shall describe an approach for conducting Site Survey and Integration for Information Transport System (ITS) to establish an integrated enterprise Air Force Network Operations (AFNetOps) capability at Yokota AFB. The offeror shall propose an integrated solution using Commercial Off-the-Shelf (COTS) products to provide the Communications Squadron (CS) at Yokota AFB a high bandwidth information transport capability that will support the war fighters’ current and future mission requirements. Information requiring transport includes classified and unclassified data, voice, video, sensor, and imagery traffic It shall also maximize the cost effective use of existing equipment and facilities, fully integrating them into the system, and ensuring full compliance with the ITS Baseline Program Directive (BPD).

For the purposes of this evaluation each respondent shall limit their proposed solution to include ONLY the following critical components of the solution:

1. An outside plant topology and associated narrative description on how the outside plant topology was developed, assumptions made and other considerations to include fiber optic cable design and compliance with design requirements as it relates to the ITNs, CEBNs, and EBNs.

2. A network topology and associated narrative description on how the network topology was developed, assumptions made and other considerations to include provisions for Power Over Ethernet (POE), compliance with design requirements as it relates to the ITNs, CEBNs, and EBNs, and rational for the technology requirements being proposed.

3. One 332 package will include a sampling of one ITN and one EBN, as long as all associated allied support work (raceways, grounds, electrical, etc) are identified. This will include a single and two story facility and associated narrative description on how the outside plant topology was developed, assumptions made and other considerations to include the documentation associated with the technology requirements and the design requirements as it relates to the ITNs, CEBNs, and EBNs.

4. A narrative description describing how the offeror would implement the installation for Yokota AFB. The proposal shall reference the Building List, ITS Architecture, and Baseline Program Directive provided as attachments in Section J. The offeror proposal will describe the sequence of events on how they would install their proposed design.

5. The knowledge, abilities, skills (to include level of skill), and products (if additional are proposed) needed to accomplish the requirements identified in the task order using the CITS Pricing Model provided in Section J, Attachment 19. Specific instructions for using the pricing model are contained in the attachment as well as in Section L6.2.2.3.1.

L4.2.7 Subfactor 5 – Management Approach

The offeror shall describe its management processes and how it will ensure services and products provide an overarching, executable solution set, consistent with the proposed approach. Key focus areas for evaluation are:

1. Staffing processes, by which the offeror

(a) Recruits highly qualified employees for the task orders,

(b) Employs methods and processes that provides for accession. The Government defines accession as opportunities/programs/policies for employees to be successful within the organization.

(c) Employs methods and processes to retain highly qualified personnel;

(d) Provides for employee professional growth;

(e) Employs methods and processes for ensuring continuity of services during personnel absences due to sickness, leave and voluntary or involuntary termination from employment such that impact to the Government is minimal

2. Worldwide support processes, including a discussion of the offeror’s approach to bidding on and responding to task orders involving OCONUS locations; including personnel; and timelines for proposal preparation activities in order to fulfill OCONUS task orders associated with the type of work described in the NetOps & Infrastructure Solutions PWS.

L4.3 Cross-reference Matrix The offeror shall include a completed Cross Reference Matrix IAW Table 2 below:

Reference (volume, page and paragraph)

Para M2.1

Subfactor 3 – NM/ND Sample Task Order

· Management and Monitoring of a Service.

· Situational Awareness (SA)

· Virtual Infrastructure (lV)

· Enterprise Requirements

Para M2.3

Subfactor 4 – CITS ITS Sample Task Order

· Outside Plant Top

· Network Top

· 332 Pkg

· Technology Req

· Installation Description

· Design Compliance Para 3.2.1.4

3.2.2;3.2.2.2;3.2.2.2.1;3.2.2.2.2

3.2.2.2.2.1;3.2.2.2.3;3.2.2.2.3.2;

3.2.2.2.3.3;3.2.2.2.4;3.2.2.2.4.3;

3.2.2.2.4.4;3.2.2.2.4.5;3.2.2.2.4.6;

3.3.1; 4.2.5.1;4.2.5.2;4.2.6;

4.2.7;

Subfactor 5 –

Management Approach

Table 2 - Cross-reference Matrix

L5.0. VOLUME III – PAST PERFORMANCE

L5.1 General

The offeror shall provide past performance information for evaluation. Failure to provide the information may result in the offeror being removed from consideration for award. Note: An offeror with no past performance experience should submit the Volume with an explanation that they have no recent or relevant experience. The Government will evaluate past performance through an integrated analysis of recency, relevancy, and the quality of work performed. In evaluating the offerors past performance record the Government may use past performance information gathered from various sources, which may include but is not limited to, information obtained from the Past Performance Information Retrieval System (PPIRS), Contractor Performance Assessment Reporting Systems (CPARS), similar systems of other Government departments and agencies, questionnaires tailored to the circumstances of this acquisition, Defense Contract Management Agency (DCMA) channels, interviews with program managers and contracting officers, site visits and other sources known to the Government including commercial sources.

L5.1.1 Past Performance Volume The offeror shall submit a Past Performance Volume containing the following:

TABS

CONTENT

1. Table of Contents shall list all documents contained in the Past Performance Volume, but will not be counted towards applicable page limits.

2. Relevant Contracts are to be provided via Past Performance Information Sheets in accordance with Section J, Attachment 13. The offeror may include information on not more than (10) contracts. Of those ten (10), not more than five (5) may be contracts performed by significant subcontractors*. For example, if you submit information on seven (7) contracts performed by you (the Prime), then you may submit information on no more than three (3) contracts performed by significant subcontractors. Only 10 total PPIS are to be submitted. Offerors are permitted to submit less than the (10) allowed but are encouraged to provide as many as possible to have the greatest impact on the overall Confidence Assessment. Offerors submitting less than the maximum number (10) of allowable citations shall acknowledge this on the bottom of the Relevancy Matrix and that they do not intend to submit more than what is provided (see Section J, Attachment 11). If applicable, you shall acknowledge by initialing the corresponding statement on the bottom of the Relevancy Matrix. Each relevant contract shall have been performed during the past (3) years from the date of issuance of this solicitation. Each Performance Information Sheet for each contract is limited to (4) pages. Offerors are cautioned that the Government will use data provided by each offeror in this volume and data obtained from other sources in the evaluation of past performance. For a description of the characteristics or aspects the Government will consider in determining relevance, see Section J, Attachment 9.

3. Consent Letters in accordance with Section J, Attachment 10 (no page limit).

4. Offerors shall identify what aspects of the contract are deemed relevant to the proposed effort using the Relevancy Matrix in Section J, Attachment 11 (no page limit).

NOTES:

Your Past Performance Information Sheets shall not exceed (4) pages per reference with up to (10) references allowed for a maximum of (40) pages.

For all criteria areas, citation references shall be at the task order or stand-alone contract level (No IDIQ's).

The citations provided shall be from either the prime or sub that is proposed to complete the work under this contract.

*Significant subcontractor – Those subcontractors the offeror considers necessary to accomplish critical aspects of the requirement. Additionally, significant subcontractors will only consist of 1st tier subcontractors, and when used to provide Past Performance Information in proposal submission shall not be substituted after contract award unless approved by NETCENTS-2 NetOps & Infrastructure Solutions PCO.

L5.1.1.1 Specific Content

Offerors may include a discussion of efforts accomplished by the offeror to resolve problems encountered on those citations provided in the PPIS, Attachment 13, to identify and manage program risk. Merely having problems does not automatically equate to a Limited or No Confidence rating, since the problems encountered may have been on a more complex program, or an offeror may have subsequently demonstrated the ability to overcome the problems encountered. The offeror is required to clearly demonstrate management actions employed in overcoming problems and the effects of those actions, in terms of improvements achieved or problems rectified. For example, submittal of quality performance indicators or other management indicators that clearly support that an offeror has overcome past problems is required.

L5.1.1.2 Consent/Client Authorization Letters

Past performance information concerning subcontractors and teaming partners cannot be disclosed to a private party without the subcontractor’s or teaming partner’s consent. Because the offeror is a private party, the Government will need consent before disclosing subcontractor/teaming partner past performance information to the offeror during exchanges. In an effort to assist the Government in assessing your past performance record a consent letter is provided in Section J, Attachment 10 and shall be completed by each subcontractor and/or teaming partner identified in your proposal within Volume I, referenced within L3.1.1. The completed consent letter(s) shall be submitted as part of the Past Performance Volume, but will not be considered in the page count of that Volume. Should the offeror not submit a completed consent letter for a major or critical subcontractor/teaming partner the Government will not disclose/discuss the applicable past performance information other than with that prospective subcontractor or teaming partner being reviewed. If there is a concern with the proposed subcontractor’s or teaming partner’s past performance, the offeror can be notified, but no details may be discussed without the subcontractor’s or teaming partner’s permission.

L5.1.1.3 Questionnaires

The Government requests the offeror send out Past Performance Questionnaires and Cover Letters to each of the Points of Contact (POCs) identified in the Past Performance Volume. The questionnaire shall be completed by the person responsible for the contract being referenced (i.e. Contracting Officer, Contracting Officer Technical Representative, Quality Assurance Personnel, Quality Assurance Evaluator, or Civilian Equivalent). The offeror will complete Section 1 prior to sending the questionnaire to the POC. Sections 2 through 5 shall not be filled out by the offeror and provided to the customer. The questionnaire responses should be the independent opinions of the person responsible for the contract and not those of the offeror.Once the questionnaires are completed by the POCs, the information contained therein shall be considered sensitive and shall not be released to you, the offeror. Questionnaires shall be sent directly to the Government by the respondent not later than the due date for the past performance volume. The questionnaire and cover letter can be found at Section J, Attachment 12.

L6.0 VOLUME IV – COST/PRICE

L6.1 General Instructions

L6.1.1 Cost/Price Reasonableness and Realism

This section is to assist you in submitting information other than cost or pricing data that is required to evaluate the reasonableness, realism, and balance of your proposed cost/price. Compliance with these requirements is mandatory and failure to comply may result in rejection of your proposal. Note that unrealistically low proposed costs or prices, initially or subsequently, may be grounds for eliminating a proposal from competition either on the basis that the offeror does not understand the requirement or has made an unrealistic proposal. Additionally, unbalanced pricing poses an unacceptable risk to the Government and may be a reason to reject an offeror’s proposal. Offers should be sufficiently detailed to demonstrate their reasonableness, realism, and balance. The burden of proof for credibility of proposed costs/prices rests with the offeror.

L6.1.2 Estimating Techniques and Methods

When responding to the Cost/Price Volume requirements in the solicitation, the offeror and associated subcontractors may use any generally accepted estimating technique, including contemporary estimating methods, to develop their estimates.

L6.1.3 Cost/Price Information

Information beyond that required by this instruction shall not be submitted, unless you consider it essential to document or support your cost/price position. All information relating to the proposed price, including all required supporting documentation, shall be included in the section of the proposal designated as the Cost/Price Volume. Under no circumstances shall this information and documentation be included elsewhere in the proposal.

L6.1.4 Cost or Pricing Information Requirements

In accordance with FAR 15.403-1(b) and 15.403-3(a), information other than cost or pricing data may be required to support price reasonableness and cost realism. Information shall be provided in accordance with FAR 15.403-5. If, after receipt of proposals, the CO determines that there is insufficient information available to determine price reasonableness and none of the exceptions in FAR 15.403-1 apply, the offeror shall be required to submit cost or pricing data.

L6.1.5 Rounding

All costs or prices provided shall be carried out to two decimal places.

L6.2 Volume Organization

The Cost/Price Volume shall consist of the following tabbed sections, which will be explained in detail in the following instructions:

SECTION 1 – INTRODUCTION

SECTION 2 – SUMMARY INFORMATION

SECTION 3 – OTHER INFORMATION

SECTION 4 – FINAL PROPOSAL REVISION (THIS SECTION SHALL APPLY ONLY IF THE PROCURING CONTRACTING OFFICER REQUESTS A FINAL PROPOSAL REVISION)

L6.2.1 SECTION 1 – INTRODUCTION

Include table of contents; glossary of abbreviations and acronyms; summary descriptions of accounting, estimating, and purchasing systems; and changes to estimating, accounting practices.

L6.2.1.1 Table of Contents

The table of contents shall specify by page number the location of information requested in these instructions.

L6.2.1.2 Glossary of Abbreviations and Acronyms

Each volume shall contain a glossary of all abbreviations and acronyms used with an explanation for each. Glossaries do not count against the page limitations for their respective volumes.

L6.2.1.3 Accounting System

For CLINs requiring other than Firm Fixed Price (FFP) prices (i.e., Fixed Price Incentive, Cost Plus Fixed Fee, etc.) involving cost information reporting or for reconciliation purposes, an adequate accounting system is required.

Also, identify any deviations from your standard procedures in preparing this proposal.

L6.2.1.4 Estimating System

Provide a summary description of your standard estimating system or methods. Also, identify any deviations from your standard estimating procedures in preparing this proposal volume. Indicate whether you have Government approval of your system and, if so, provide evidence of such approval.

L6.2.1.5 Purchasing System

Provide a summary description of your purchasing system or methods (e.g., how material requirements are determined, how sources are selected, when firm quotes are obtained, what provision is made to ensure quantity and other discounts). Also, identify any deviations from your standard procedures in preparing this proposal. Indicate whether you have Government approval of your system and, if so, provide evidence of such approval.

L6.2.2 SECTION 2 – SUMMARY INFORMATION

L6.2.2.1 NetOps & Infrastructure Solutions Price Proposal Workbook

Complete the NetOps & Infrastructure Solutions Price Proposal Workbook’s separate worksheets (Cover Page, Category Functional Skill Sets, Maximum Labor -Hour Rates Best Estimated Quantities (BEQ) Worksheet, Cost Reimbursable Sample TO, and Total Evaluated Price (TEP) Worksheet) and the CITS Pricing Model included with Attachment 19 as described below. The offerors shall provide a full labor category description (with qualifications) for each proposed labor category addressing the specific skill sets and skill levels and how they can perform this work through experience and/or training. Electronic submissions shall be made using the NetOps & Infrastructure Solutions Price Proposal Workbook in Excel format to allow electronic manipulation of data for evaluation purposes. The offeror shall not password protect the NetOps & Infrastructure Solutions Price Proposal Workbook located in Section J, Attachment 21.

L6.2.2.1.1 Cover Page Worksheet

Complete the Cover Page worksheet by inserting the Offeror Name, Offeror Address, City, State, Zip, Point of Contact, Phone 1, Phone 2, Fax 1, Fax 2, E-mail 1, and E-mail 2 into the appropriate cells.

L6.2.2.1.2 TEP Worksheet

Offerors shall insert total prices for each sample task order into their respective total price rows in the TEP worksheet. The offeror’s total Labor-Hour (LH) Price from the Maximum Labor-Hour Rates BEQ Worksheet will automatically populate the Total Labor Price Row in the TEP worksheet. Specific instructions for submitting responses to the sample task orders follow in paragraphs below.

L6.2.2.2 Instructions for Network Management/Network Defense (NM/ND) Cost Reimbursable Sample Task Order

For the purposes of the NETCENTS-2 source selection, only the paragraphs annotated with an asterisk in the Specific Requirements section of the sample task order, Section J Attachment 20, will be included in the TEP. Proposals shall be broken out by year, option, and CLIN, as applicable. Offerors shall provide a detailed cost build-up by WBS to level 4 (reflecting all elements of cost and the bases of estimates) based upon the proposed approach described in the technical volume to accomplish the task order using the WBS provided in Section J, Attachment 21. Offerors shall include an extra column in their Level 4 WBS matrix (in both the hours and costs displays of Level 4) to indicate which elements of their level 4 WBS map to the asterisked items in the Specific Requirements section of the sample task order. These rows indicated will be summed and included in the TEP, while the rows not indicated as mapping to the asterisked items will not be included in the TEP.

The proposal shall reflect the proposed labor categories, to include skill sets and skill levels, estimated hours in each, materials, travel and ODCs, and all applicable rates and factors (including direct labor rate, fringe rate, overhead, G&A, other indirect rates or factors and profit, as applicable) and the cost model used to develop the proposed cost. Additionally, the offeror shall input the proposed cost/price into the Cost Reimbursable Sample TO tab of the Price Proposal Workbook (Section J, Attachment 21) in the format prescribed. Offerors shall also submit a list of each major material item and applicable equipment exceeding $2500 unit cost showing nomenclature, part number, quantity required, and unit price as part of the List of Materials (Sections 1.1.1 and 1.1.2) in the Cost Reimbursable Sample TO tab of the Price Proposal Workbook (Section J, Attachment 21). Offerors shall also include basis of estimate.

The proposed approach and required resources must demonstrate a full understanding of the scope and complexity of the effort set forth in the sample task order technical requirements. Offerors shall base their estimate on the location specified in the task order. Offerors shall describe key assumptions and factors/methodologies used to derive the scope and level of effort proposed to meet the requirement. The model provided on CD-ROM shall be in Microsoft Excel 2003 (or higher) format to allow manipulation of data for evaluation purposes.

L6.2.2.3 Instructions for CITS Information Transport Systems (ITS) Firm Fixed Price Sample Task Order The offeror shall propose a complete firm fixed price solution for the CITS program ITS sample task provided in Section J, Attachment 14 by completing the CITS Pricing Model provided in Section J, Attachment 19. The Government will escalate each offeror’s base period total price by the Consumer Price Index for general inflation for 2011-16 to represent pricing of all option periods. Detailed instructions to complete the Model are provided in paragraph L6.2.2.3.1 and in Section J, Attachment 19. Following are some general instructions.

L6.2.2.3.1 Instructions for the CITS Pricing Model The data provided by the government with the Sample Task Order is more detailed than that which will be provided for competition for CITS ITS task orders after Source Selection. For example, additional data is provided to give offerors the information needed to solve the problem in the form of a Network List of Materials (LOM) that is provided with the Sample Task Order; sample TO includes LOM, LOMs will not be provided with actual TOs. This LOM will be “generic” (i.e., not based on any particular vendor's equipment items). Following are guidelines for price inputs for the CITS Pricing Model (Section J, Attachment 19):

a. Offerors shall propose a fully burdened price for each task element of the CITS Pricing Model that is pertinent as indicated by quantity in each of the tabs in the workbook. Fully burdened is defined as including all applicable items such as Direct & Indirect Labor, Management, Material, Material Handling, Shipping, G&A, Profit, Test & Installation Equipment, Cost of Money, etc.

b. Offerors should develop their sample TO, evaluation only, element prices assuming the location is Yokota AB, Japan and the Location Factor is 1.

c. Travel and ODCs, if applicable, shall be included as part of the sample task order and not as a separate CLIN.