ITMA_QA_-_2Final_RFP_-_20180316_-_JC_Update.pdf

Information Technology Management and Analysis May 4, 2018

RFP /

Attachment

Subject

Page #, Paragraph Reference

Question / Comment Responses

1 General Please provide the period of performance estimated start date for this contract. This would be necessary if we have to provide contractor fiscal year hours for the labor resources file and to estimate what fiscal years are involved splitting hours.

Offerors shall use a August 22, 2018 as an estimated start date for proposal purposes. However, the actual start date is not known at this time.

PWS Page 4, Section 1.2

Since the goal of these advisory and assistance services will improve information solutions reliability, improve IT investment portfolio alignment, improve operational effectiveness, improve resilient communications, and improve oversight, the industry needs to understand the current level of support and where a contract will be starting. Will the Government please provide the benchmarks to the current Acceptable Quality Level metrics of the current contract?

This section of the PWS is background information and does not have any associated Acceptable Quality Level metrics. Performance standards are provided in Attachment J-02 QASP Enclosures 1-5.

PWS Page 12, Table 3.0

Performance Objective #5 suggests we will perform operations, but the PWS reads as the contractor will provide oversight with very little operational hands-on work. Can the Government please confirm if this PO #5 is primarily oversight, monitoring and reporting or will it also include significant operations work? If operations work is required, can additional details about the operations tasks be included?

The contractor will perform Advisory & Assistance Services directly supporting the government and will not be performing IT operations and maintenance.

PWS Section 3.1.2 Section 3.1.2 of the Performance Work Statement states that: “Any and all of the above defined A&E Team Support IASAE Level II and III Functions may be executed for the MDA Enterprise. The IASAE must comply with the BMDS Security Classification Guide (SCG) and the respective element/component unique SCG and Program Protection Plans. Per DoDI 8500.01 personnel filling IASAE positions must be qualified and sign a Statement of Acceptance of Responsibilities.” Are these IASAE Level II or III certifications required upon contract award? If not, will the government please provide clarification for the expected timeframe for personnel to obtain the required IASAE certification?

This requirement is now located in Table 9.1 Any personnel in labor category Engineer (Advanced) are required to possess IASAE Level III certification and any personnel in labor category Engineer (Intermediate) to possess IASAE Level II certification. IASAE Level II and III certifications are required at contract award.

5 PWS Para 3.1.3.a “Establish, within 30 days of contract start, and maintain … “. Does the government intend for the 30 days to be within the transition period or subsequent to the transition period?

The PWS paragraph 3.1.3.a requirement has been eliminated, the contractor is expected to utilize existing portal sites on UMKO/CMKO from the start of the PoP.

PWS Para 3.1.3.a Please define/provide full spelling of enterprise SAP system file repositories. This PWS paragraph has changed and does not reference SAP. However, SAP stands for Special Access

Program.

PWS Page 15, multiple starting on 3.1.3.a

All Performance Objectives request to establish and maintain an unclassified and classified Knowledge Online (UMKO/CMKO), JWICS, and SAP file repositories/website/portal sites. A. Do these current sites exist today? B. If so, what technology is used (e.g. Sharepoint v?)? C. If so, will the incoming contractor be able to continue support of the existing platform or will MDA require the new vendor to establish a new site? D. If these sites do not exist today, will we be given the appropriate access on each designated government network to set-up and administer such a website / portal site?

Yes, these sites exist today. Currently, SharePoint 2013 applies to all portal sites. Contractor will support existing platform by adding content to the sites.

PWS Para 3.1.3.b “Establish, within 45 days of contract start, and maintain … “. Does the government intend for the 45 days to be within the transition period or subsequent to the transition period?

The PWS paragraph 3.1.3.b has been eliminated.

PWS Page 15, 3.1.3.b Are there currently any of the listed plans with supporting procedures, or do these need to be created new within 45 days of contract start?

SOPs exist but new SOPs may be generated over time. Current SOPs will be made available upon request after award of contract.

PWS Page 17, 3.2 The title for this section says “Policy Services” but the Performance Objective Table (on pg 12) refers to this objective as “Planning Services”. Please clarify as to which wording is accurate. There are multiple instances of “Policy Services” throughout the section.

Planning Services is correct. The PWS has been updated in Amendment 7 to provide consistency.

PWS Page 19, 3.2.3.c and others For all mention of SOPs, do these SOPs currently exist? SOPs exist but new SOPs may be generated over time. Current SOPs will be made available upon request after award of contract.

RFP /

Attachment

Subject

Page #, Paragraph Reference

Question / Comment Responses

12 PWS Page 40, 3.4.3.c(3)(f)

The contractor is asked to operate and maintain the Huntsville Records Center. Can you please provide specifics about this Record Center, such as its size, number of records stored, number of new records received per year, and number of requests received for records to be provided from this Records Center?

The following FY2016 Metrics have been added to Attachment L-09 in Amendment 4. However, this information varies from year to year.

FY2016 Metrics:

* approximately 550 boxes stored

* facility capacity is 1,000 boxes of records *42 new boxes received via 21 transfer requests

* 21 boxes destroyed

* over 20,000 pages scanned *approximately 7,000 pounds of old or scanned records destroyed

* electronic records metrics:

** approximately 1,000,000 unclassified records ** approximately 55,000 classified records ** over 4,000 licenses/accounts ** approximately 0.5 FTE used to perform account maintenance, user training, and archival of electronic records

PWS Page 52, Section 3.6.1

The PWS says the contractor shall assist with VTC, audio/video services, and DRSN. Can the Government please provide the specific vendors and versions of the equipment being used to include VTC, audio/video services, DRSN, as well as both the standard end user telephone and the Unified Communication solution and version, such as Cisco or Avaya?

The expectation is for the offeror to perform Advisory & Assistance Services directly supporting the government and will not be performing IT operations and maintenance of the Unified Communications systems.

PWS Section 9.0

Table Does the table under section 9.0 Transition and Staffing, letter d, indicate required labor categories for each Performance Objective? Does this represent historical data of labor categories performing these Performance Objectives?

Table 9.1 represents the current requirements and is not historical data. Table 9.1 Performance Objective column reflects the labor categories associated with the applicable performance objective.

PWS Pages 61, para 6.0; Page 65, para 9.0.d

The Government has provided Table 6.1 and Table 9.1 to show security clearance requirements and staffing mapping. Based on the Table 9.1, are Offerors required to staff the contract based on the labor categories and skills levels listed in Tables 6.1 and 9.1?

The Offerors should plan to staff the contract using Table 9.1, which provides labor categories and clearance requirements.

RFP /

Attachment

Subject

Page #, Paragraph Reference

Question / Comment Responses

PWS & Exhibit A007

PWS Table 9.1 There appears to be contradictory information between Exhibit A007 and what is listed in the Performance Work (PWS) statement and Table 9.1 Staff Mapping on page 65 of the PWS. In Exhibit A007 Table 1: IA Workforce Primary Duty Positions Metrics it states that the Contractor should have the following IA certified personnel:

• IAM II = 20 qty

• IAM III = 10 qty

• CND-A = 5 qty Section 3.1.2 of the Performance Work Statement states: “Any and all of the above defined A&E Team Support IASAE Level II and III Functions may be executed for the MDA Enterprise. The IASAE must comply with the BMDS Security Classification Guide (SCG) and the respective element/component unique SCG and Program Protection Plans. Per DoDI 8500.01 personnel filling IASAE positions must be qualified and sign a Statement of Acceptance of Responsibilities.” Table 9.1 Staff Mapping on page 65 of the PWS states that certain Contract Labor Categories supporting specific Performance Objectives in the PWS are required to have an IAT II, IAT III, IASAE II, and/or IASAE III level certification. However, there is no mention of IAM II, IAM III, or CND-A requirements in the PWS as stated in the Exhibit A007. Please clarify the information requested in Exhibit A007 regarding IA Workforce Management Reporting. Should the contractor staff according to Table 9.1 Staff Mapping listed in the PWS?

CDRL Exhibit A007 is sample data and not actual data. The offeror should propose to the requirements in the PWS.

17 PWS

The ITMA Performance Work Statement (PWS) does not reference attachment J-01a or attachment L-11 (i.e., Key Product Tables) included with the Request for Proposal. Section 3.1.4 of the Performance Work Statement lists the A&E Team Support Key Products/Technical Data such as: plans, Current CCC Enterprise Strategic Architectural Weaknesses Analysis Report; CCC Enterprise Strategic Architecture Plan; CCC Enterprise Roadmap; technical positions; analysis, findings; recommendations; briefings; and reports; schedules; trip reports; monthly metrics; executive meetings and briefings; weekly activity report;

and portal sites. Will the government please provide clarification for the key products required for the TEAMS ITMA contract? Are the Key Product Tables (attachment J-01a and attachment L-11) to be incorporated into the PWS or is the contractor expected to refer to the Key Products included with each Performance Objective of the TEAMS ITMA PWS?

Attachment J-01a has been removed in Amendment 7. Attachment L-09 is provided for historical purposes.

Attachment L-11 has been deleted in Amendment 7. The key products requirements are written into the PWS performance objectives.

PWS and Key

Products Tables The Key Products listed in J-01a do not match the PWS Performance Objectives in attachment J-01. The Key Products provided appear to be mapped to the Draft RFP PWS. Please provide an updated Key Products Table mapped to the current PWS.

The Key Product Table has been removed in Amendment 7.

RFP /

Attachment

Subject

Page #, Paragraph Reference

Question / Comment Responses

PWS Page 64, 9.0.a and b

In the PWS in 9.0 b., it states the Transition Period ends 14 calendar days after start of period of performance. However, under the Staffing Timeline in 9.0 c., it states that staff will perform all performance objectives NLT 7 calendar days after start of period of performance. This is a extremely compressed and short timeline for an offeror to retain and in-process incumbent personnel or recruit, hire, and in-process new hires. This resume requirement gives a distinct advantage to the incumbent contractor team and places an increased burden on non-incumbent offerors. Revise the staffing timeline table to reflect that staff will be in place and available to perform all performance objectives by the end of the transition period. To decrease transition risk and ensure successful performance on the contract, we recommend a 30 calendar day transition period. A 30 day transition will allow for the successful offeror to perform all required transition activities (i.e. hiring, security, etc.)

Table 9.0 has been updated to state by the end of transition period, which is identified in Section 9.b.

20 PWS Page 64, 9.0.a, b, and c

In the PWS in 9.0 b., it states the contractor shall submit clearance paperwork for hires upon award to immediately begin the physical and network access processes. If the contractor is to submit clearance paper work immediately upon award, it would imply that the contractor already has all personnel on staff. To decrease transition risk and ensure successful performance on the contract, we recommend a that all security requirements must be accomplished by the end of the transition period and remove the requirement for clearance paperwork to be submitted immediately upon award.

Clearance paperwork must be submitted for all hires at contract award. The Government recognizes that additional hires will occur during the transition period with full staffing at the completion of the transition period.

PWS and Section L

PWS Page 64, 20; Section L

The PWS states that, “Key personnel for this effort are the Contract Program Manager and advanced labor category positions (also called Technical Lead(s)).” Section L Instructions to Offeror’s states, “Key personnel resumes shall be submitted as provided in Attachment L-06 – Key Personnel Resume Template.”

Based on this requirement, any labor category that an offeror designates as Advanced is considered a Technical Lead and requires submittal of a resume. For an effort of this size, the CPM and limited few Technical Leads can adequately manage the work to be performed. An executable staffing approach may require hiring numerous personnel into Advanced-level labor categories, but not all of these Advanced-level personnel would necessarily be designated as Technical Leads. In addition, since an offeror’s staffing approach may prioritize retaining qualified incumbent personnel with required security clearances into advanced-level labor category positions, this resume requirement gives a distinct advantage to the incumbent contractor team and places an increased burden on non-incumbent offerors if they bid any advanced labor category positions. This requirement also increasing the likelihood of non-incumbent offerors attempting to contact incumbent personnel to request resumes for inclusion in their proposal submission. We recommend removing the requirement that all labor categories designated as Advanced are considered Technical Lead(s), and revert to the DRFP PWS language stating, “Key personnel for this effort are the Contract Program Manager; and, if proposed, Technical Lead and Subject Matter Experts (SMEs).”

The PWS has been updated in Amendment 7 to reflect key personnel as being the Contract Program Manager and Technical Lead(s) but not advanced labor category positions. Subject Matter Experts are no longer included as a category of "key personnel."

RFP /

Attachment

Subject

Page #, Paragraph Reference

Question / Comment Responses

PWS Page 64, 9.0 The PWS states that, “Key personnel for this effort are the Contract Program Manager and advanced labor category positions (also called Technical Lead(s)).” The transition requires the CPM and Technical Lead(s) to be filled at the start of the Period of Performance (PoP). Based on the definition of technical leads being advanced labor category positions, this would require the offeror to have all advanced positions on the first day of the transition/period of performance. This section also notes the CPM and Technical Lead(s) shall meet with the COR, ACOR, COTRS, and Functional Integrator (FI) or their designated representative within 5 workings days of the start of the PoP as part of the transition and Kickoff Meeting. Based on the definition of technical leads being advanced labor category positions and the quantity of advanced labor category positions bid, the number of offeror attendees (CPM and Technical Lead(s)) required to attend the Kickoff could encompass a large number of personnel. This requirement gives a distinct advantage to the incumbent contractor team and places an increased burden on non-incumbent offerors if they bid any advanced labor category positions. This requirement also increasing the likelihood of non-incumbent offerors attempting to contact incumbent personnel to request resumes for inclusion in their proposal submission. We recommend removing the requirement that all labor categories designated as Advanced are considered Technical Lead(s), and revert to the DRFP PWS language stating, “Key personnel for this effort are the Contract Program Manager; and, if proposed, Technical Lead and Subject Matter Experts (SMEs).”

PWS updated to reflect key personnel as being the Contract Program Manager and Technical Lead(s) but not advanced labor category positions.

PWS and Section L

PWS Page 64, Para 9.0; Section

L Page 20, L- 11.2

Section L states, “The contract shall specifically identify its approach to the Contract Program Manager (CPM) and Technical Lead positions, to include whether the CPM will perform both roles or if the Technical Lead will be performed by a separate individual.” This statement allows for the use of a CPM and Technical Lead or a CPM who will be performing as the Technical Lead too. However, the PWS states that, “Key personnel for this effort are the Contract Program Manager and advanced labor category positions (also called Technical Lead(s)).” The Section L requirement does not follow with the PWS definition of Technical Lead (especially if there are more than 1 advanced labor category positions on the contract). We recommend removing the requirement that all labor categories designated as Advanced are considered Technical Lead(s), and revert to the DRFP PWS language stating, “Key personnel for this effort are the Contract Program Manager; and, if proposed, Technical Lead and Subject Matter Experts (SMEs).”

PWS has been updated to reflect key personnel as being the Contract Program Manager and Technical Lead(s) but not advanced labor category positions.

PWS Page 65, Table 9.0

There is a 14 day transition period, however, table 9.0 indicates all staff have to be on board NLT 7 Days after start date. Will the government reconsider this requirement and allow 100% on board NLT 14 days after start date? Having 100% personnel on board in 7 days favors the incumbent who already have the personnel on contract.

Table 9.0 has been updated to state by the end of transition period, which is identified in Section 9.b.

RFP /

Attachment

Subject

Page #, Paragraph Reference

Question / Comment Responses

RFP Page 70;

252.204-7012

Based on the DFARS clause 252.204-7012 in this RFP and the future award documents are these documents considered to be within the definition of Controlled Unclassified Information in accordance with the security requirements of the National Institute of Standards and Technology (NIST) Special Publication 800- 171? If so what are your agency implementing procedures/policy for support services contractors? OR is this DFARS clause applicable only to direct labor personnel working on a Government installation using Government computers?

Please refer to DFARS 252.204-7012 which provides helpful guidance on contractor responsibilities.

For historical reference, NIST SP 800-171 was developed for use on contractor and other nonfederal information systems and networks to protect Controlled Unclassified Information (CUI). DFARS 252.204- 7012 requires that contractors implement NIST SP 800-171 to protect systems and networks that process, store, or transmit "covered defense information" (as defined in the clause). There is no single or prescribed manner in which a contractor may choose to implement the requirements of NIST SP 800-171, or to assess their own compliance with those requirements.

If unsure of what a requirement means, companies may seek additional guidance in the mapping table in Appendix D of NIST SP 800-171, which maps each of the NIST SP 800-171 requirements to relevant security controls that are specified in NIST SP 800-53, "Security and Privacy Controls for Federal Information Systems and Organizations." After identifying the corresponding NIST SP 800-53 control, the company may consult the "Supplemental Guidance" section of the description of that control in NIST SP 800-53 to find clarifying guidance and examples of how to implement that control, which the company may choose to utilize for its implementation of the more performance-based 800-171 requirements.

Ultimately, it is the contractor's responsibility to determine whether it is has implemented the NIST SP 800- 171 (as well as any other security measures necessary to provide adequate security for covered defense information).

Section L Page 9, L-3.3 Given the potential for Volume II to be used to support the evaluation of each factor (as stated in L-6.1), will the Government allow pricing information to also be included in the Executive Summary?

Please do not include pricing information in the Executive Summary.

Section L Page 12, L-4.7 Does the 10 point font for tables, charts, graphs and figures specified for fold-out pages hold for the entire proposal?

For tables, charts, graphs and figures, the font shall be no smaller than 10 point. Except for the reproduced sections of the solicitation document and any non-narrative sections (e.g. tables, graphs, charts, figures, etc.), the text size shall be no less than Microsoft Word Times New Roman 12 point font, single-spaced. See Section L-4.5 and L-4.7.

Section L Page 19, L-10.4 Will the Government accept a recent CPARS for a past performance in lieu of a PPQ? Many customers will not fill out a PPQ if a CPARS is on file.

Yes, but offerors should follow the guidance in Section L 10.4 and Section M 6.0 for how the Government will evaluate past performance.

Section L Page 20, L-11.1 Can the Government confirm the alignment of the bullets in this section to the PWS as follows: Enterprise information technology architecture, engineering and operations (bullet 1) aligns to Objective #1; Unified communications services and systems (bullet 2) aligns to Objective #6; regional IT, CIO and functional operations (bullet 3) aligns to Objective #2. If this is incorrect, request that the Government clarify which objectives within the PWS will receive increased emphasis during the evaluation

The PWS and the relevant sections of L-11.1 have been revised.

Section L Page 28, L-13.5 The wording for #2 is confusing; if an FPRA is not in place, are we still expected to identify the applicable Forward Pricing Rate Proposal? We do not have an FPRA in place; can we provide our basis for labor/ indirect rates as part of the Basis of Estimate (#9 on pg 29)?

Offerors are not required to have an FPRA. Offerors may provide an explanation as part of the Basis of Estimate in the Cost Narrative. In addition, the offeror is required to complete the Indirect Rate build-up Sheet in the Excel Pricing Workbook.

Section L Page 28, L-13.5 We use ERI as our estimating system for labor rates; does the Government consider this a reviewed/ approved system?

No. DCAA reviews and approves accounting, purchasing, and estimating systems.

RFP /

Attachment

Subject

Page #, Paragraph Reference

Question / Comment Responses

Section L Pages 28-29, L-

13.5 Can the Government confirm that if a separate pricing narrative is submitted by a major sub-contractor, it does not need to include elements numbered 4, 5, 6, 7, and 8 of the pricing narrative?

All major subcontractors are required to submit the information required for elements 4,5,6,7, and 8. The major subcontractor can submit their cost narrative directly to the Government if it contains proprietary data.

See paragraph L-13.1.

Section L Page 30, L-14.0 The Bidders’ Documents Library Index was not provided as an attachment Attachment 12 has been included in Amendment 7.

Section L Table L-1 The Draft RFP allotted 25 pages for technical. The Final RFP PWS has significant changes, increased requirements, however, page allocation was reduced to 20 pages. Will the government consider increasing the page allocation for the technical volume back to 25 pages. The PWS has 66 pages of requirements and has only allocated 20 pages for a very complex program.

Page count limitation will not be adjusted. However, Section L-11.1 has been revised.

Section L L-4.14 Section L-4.14 requirement 4 states that “Each volume, except for the Cost Volume, shall have a cover sheet, clearly marked as volume number, “ORIGINAL”, offeror’s name, solicitation title, and solicitation number”. Does this mean that the original unbound Cost Volume does NOT require a cover sheet at all?

Should the unbound original hard copy start with the cover letter?

Yes. The Cost Volume does not require a cover sheet. Cover letter is at the offeror's discretion.

Section L The page limitation for the Technical Expertise/Approach is limited to 20 pages. However, Section L requires offerors to address the execution of all PWS requirements while placing an emphasis on understand of work and demonstrated approach in enterprise information technology architecture, engineering and operations; unified communications services and systems; and regional IT, CIO, and functional operations.

We recommend increasing the page allocation to 30 pages to allow offerors to be able to address all Section L requirements.

Page count limitation will not be adjusted.

Section L and M L-11 and M-7.1 The sections state that evaluation emphasis will be placed on the following areas: Enterprise information technology architecture, engineering and operations, Unified communications services and systems, and regional IT, CIO, and functional operations. These areas seem to align with specific Performance Objectives under the draft PWS. Can you identify which specific Performance Objectives, under the final PWS, these areas pertain to?

Sections L&M have been revised.

Attachment J- 01a

Key Product Tables

The Key Product Tables currently are arranged based on the draft PWS Performance Objectives, i.e., PO’s 1-

5. Since the Performance Objectives in the Final RFP have changed, will the government please update the KPTs to reflect the changes from the draft to the final? This affects the bidder’s staffing and pricing.

The Key Product Table has been removed in Amendment 7.

DD-254 Page 1, Box B Given the potential requirement for CUI storage on site, it appears that some level of safeguarding will be required. Is that correct?

No. Safeguarding only refers to classified information not CUI.

40 DD-254

Page 3, Subcontractor

Classified Access Approval

Recommend that the first sentence be re-worded so that only the PRIME contractor can flow down access and/or dissemination to all sub-contractors.

The intent is to allow the Prime to give access to the 1st tier subcontractor and then the subcontractors to be allowed to flow access down to their 2nd tier and so on.

DD-254 Page 6, Item 11.1

Does the Government anticipate that CUI will reside or transit on contractor information systems? Request clarification on the likelihood of this requirement; many potential offerors will need to harden their systems to support this requirement.

Yes, we anticipate CUI will reside on the prime and their 1st tier subcontractor information sytems. Beyond that it will be the determination of the contractors on how far down CUI is disseminated. MDA would require that only the necessary CUI flow down to lowest tiers. The hardening of the systems (NIST 800-171) would be required if CUI is resident on the unclass systems.

RFP /

Attachment

Subject

Page #, Paragraph Reference

Question / Comment Responses

Attachment L-01 / Attachment L-

Past Performance Information / Past Performance Questionnaire

Will the GOV permit offerors to recreate the information contained in the form in WORD for proposal submission purposes? If an offeror does this within the formatting instructions provided in Section L of the solicitation, will the recreated forms be considered compliant?

The PPI and PPQ as a Word document has been provided in Amendment 7

Attachment L-07 Rates Tab A single set of ERI benchmarks has been provided for the 6 year time period; may we escalate the ERI Benchmarks each year to account for escalation in our rates from year to year? Otherwise, there is a potential that an offeror may break the 90th percentile in the out years, although the rates started within the benchmarks in the first year.

Offerors may escalate the ERI benchmarks from year to year.

Attachment L-07 Labor Resources After reviewing the instructions in the “Labor Resources” excel file it says to use contractor fiscal year hours. Please consider changing this to contract hours to correspond with CLINs and BASE through option years in the “Labor Resources” file.

The Offeror should use contractor fiscal year hours in order to correspond with the contractor fiscal year rates.

Attachment L-09 and PWS

The Historical information states, "All Personnel must hold a minimum of Top Secret security clearance at Base Period of Performance (PoP) start Date. The Government estimates the requirements for Top Secret and SCI as defined in the table below:" Then the table states that 35% of personnel in HSV require Top Secret eligibility as well as 25% of COS, 100% of FBV, and 100% of DHL. Additionally, the PWS states under 6.0 Security Requirements, "employees requiring access to classified information shall be eligible to possess a security clearance commensurate with the level of information for which they require access." Is this historical information or is this a requirement that ALL PERSONNEL must have Top Secret clearance at POP start? Please clarify how many personnel require Top Secret clearances, and what date these are required.

Attachment L-09 has been updated in Amendment 7. PWS Table 9.1 contains requirements for security clearances for each of the labor categories. Personnel requiring Top Secret clearance must be "Top Secret Eligible" at contract start.

46 Attachment L-09 and PWS

Attachment L-09 Historical data indicates “All Personnel must hold a minimum of Top Secret clearance at Base Period of Performance start date”, however, the table indicates that for HSV and COS the % required by POP start date is 35% and 25%, respectively. Additionally, Table 6.1 indicates that not all personnel require a TS clearance. Did the government mean to require all personnel to have a Secret clearance at POP start date?

Attachment L-11 has been deleted in Amendment 7 and replaced with Attachment L-09. PWS Table 9.1 contains requirements for security clearances for each of the labor categories. All personnel requiring Secret clearances must have the clearance at contract award. Personnel requiring Top Secret clearance must be "Top Secret Eligible" at contract start.

Attachment L-09 Bottom of Page The minimum Security Clearance requirement for this solicitation as stated in the PWS is Secret; however, the paragraph above the last table states that all personnel must hold a minimum TS clearance. Please clarify.

Attachment L-09 has been updated in Amendment 7. Also, see Attachment L-10.

Attachment L-10 Labor Cat

Descriptions Educational requirements do not offer commensurate years of experience as an exception. Will the government accept commensurate years of experience for the education degree requirements? If yes, recommend 10 years for a MA/MS.

Attachment L-10 has been updated in Amendment 7. Years of experience is not an exception to the educational requirements.

RFP /

Attachment

Subject

Page #, Paragraph Reference

Question / Comment Responses

Attachment L-10 Labor Competency Descriptions

Attachment L-10_Labor Competency Descriptions do not list the required DoD Approved Baseline Certifications for each labor category as mentioned in Table 9.1 Staff Mapping on page 65 of the Performance Work Statement. For example, in Table 9.1 Staff Mapping in the PWS (page 65), it states a Technician (Advanced) supporting Performance Objective #4 (Information Management Services) is required to obtain the IAT III DoD IA Approved Baseline Certification. Will the government please provide clarification on the DoD 8570 certifications required for this TEAMS ITMA contract?

Table 9.1 has been updated in Amendment 7 and Figure 3.4.1 is deleted.

50 Attachment L-10

Labor Competency Descriptions

Attachment L-10_Labor Competency Descriptions list multiple security clearance options for each labor category than what is listed in Table 9.1 Staff Mapping on page 65 of the Performance Work Statement. For example, the Engineer (Advanced) Labor Category in Attachment L-10 states the security clearance requirements for this position are TS, TS/SCI or S; however, on page 65 of the PWS (Table 9.1 Staff Mapping) it states that the Engineer (Advanced) is required to hold a TS/SCI clearance. Will the government please provide clarification for the security clearances required for each labor category?

Table 9.1 has been updated in Amendment 7 and Figure 3.4.1 is deleted.

Attachments L- 10 and L-7

Labor Competency Descriptions

The Labor Competency Descriptions lists Engineering (Basis), Specialist (Basic) and Technician (Basic) labor categories and descriptions. However, these labor categories are not included in the Attachment L-07 Excel Pricing Workbook. We recommend adding these labor categories to the Attachment L-07 Excel Pricing Workbook in the labor Category tab, Rates tab, FBLRs tab, and the drop down menu on the Labor Resources tab and listing the ERI Benchmarks data points on the rate tab.

The labor categories in the Labor Competency Descriptions are included in Attachment L-07 Excel Pricing Workbook in Amendment 7.

Attachment L-10 All Labor Competency descriptions are usually accompanied by minimum experience levels; will the

Government provide these for each competency?

Attachment L-10 has been updated in Amendment 7.

Attachment L-10 What qualifications do Technical Leads and SMEs need to meet? Asked another way, which Labor

Competency (ies) should TLs be aligned to?

Technical Lead qualifications and the qualifications of those considered to have technical expertise in specific areas are at the offeror's discretion in their proposed approach. See paragraph L-11.2 and reference Attachment L-10 for appropriate category.