PRE-SOLICITATION DRAFT PWS.docx

SECTION C – DESCRIPTION/SPECS/WORK STATEMENT

SPECIFICATIONS/STATEMENT OF WORK/PERFORMANCE WORK STATEMENT

Work under this performance-based contract shall be performed in accordance with the following description/ specifications/ statement of work (SOW) which herein shall be referred to as Performance Work Statement (PWS):

1.0 PURPOSE

1.1 BACKGROUND

Space and Naval Warfare Systems Center Atlantic (SPAWARSYSCEN Atlantic) Navy and Federal Support Portfolio provides support services to The Tactical Technology Office (TTO) in the Defense Advanced Research Projects Agency (DARPA). DARPA/TTO requires support services in its technical work in the areas of ground systems, maritime systems, air systems, and space systems, with cross-cutting themes of agile development, cooperative autonomy, unmanned systems, and power and propulsion. Scientific engineering support services and administrative support services are required for the existing (examples listed below), planned, and yet to be defined technology programs.

a. Aerial Reconfigurable Embedded System (ARES)

b. Airborne Launch Assist Space Access (ALASA)

c. Aircrew Labor In-Cockpit Automation System (ALIAS)

d. Anti-Submarine Warfare (ASW) Continuous Trail Unmanned Vessel (ACTUV)

e. Blue Wolf

f. Collaborative Operations in Denied Environment (CODE)

g. DARPA Robotics Challenge

h. Experimental Spaceplane (XS-1)

i. Gremlins

j. Ground X-Vehicle Technologies (GXV-T)

k. Hydra

l. Hypersonic Air breathing Weapon Concept (HAWC)

m. Legged Squad Support Systems (LS3)

n. Magneto Hydrodynamic Explosive Munitions (MAHEM)

o. Multi-Azimuth Defense Fast Intercept Round Engagement System (MAD-FIRES)

p. OrbitOutlook

q. Persistent Close Air Support (PCAS)

r. Phoenix

s. Robotic Servicing of Geosynchronous Satellites (RSGS)

t. Space Enabled Effects for Military Engagements (SeeMe)

u. Space Surveillance Telescope (SST)

v. Squad X Core Technologies (SXCT)

w. Tactical Boost Glide (TBG)

x. Tactically Exploited Reconnaissance Node (TERN)

y. Vertical Takeoff and Landing Experimental Plane (VTOL X-Plane)

1.2 SCOPE

The scope of this effort is to provide technical, programmatic/financial, and administrative support services to DARPA/TTO for existing and future DARPA/TTO programs. The support encompasses system engineering support services, materials, facilities, and travel to perform the below tasks for DARPA/TTO programs.

NOTE: Work will not be performed in Afghanistan.

2.0 APPLICABLE DOCUMENTS

All work shall be accomplished using the best commercial practices and current acceptable industry standards. The applicable references and standards invoked will vary within individual tasks and will be specifically called-out in each task order. In accordance with Defense Acquisition Policy changes, maximum utilization of non-Governmental standards will be made wherever practical. Where backward compatibility with existing systems is required, selected interoperability standards will be invoked. For purposes of bidding, the following documents are not exclusive; however, all contractors shall be able to meet those cited when applicable to the task order.

2.1 REQUIRED DOCUMENTS

The following instructional documents are mandatory for use. Unless otherwise specified, the document’s effective date of issue is the date on the request for proposal. Additional applicable documents may be included in specific task orders.

2.2 GUIDANCE DOCUMENTS

In addition to DARPA Instructions, the following documents are to be used as guidance. Unless otherwise specified, the document’s effective date of issue is the date on the request for proposal. Additional applicable documents may be included in specific task orders.

2.3 SOURCE OF DOCUMENTS

The contractor shall obtain all applicable documents. Many documents are available from online sources. Specifications and commercial/industrial documents may be obtained from the following sources:

Copies of Federal Specifications may be obtained from General Services Administration Offices in Washington, DC, Seattle, San Francisco, Denver, Kansas City, MO., Chicago, Atlanta, New York, Boston, Dallas and Los Angeles.

Copies of military specifications may be obtained from the Commanding Officer, Naval Supply Depot, 3801 Tabor Avenue, Philadelphia, PA 19120-5099. Application for copies of other Military Documents should be addressed to Commanding Officer, Naval Publications and Forms Center, 5801 Tabor Ave., Philadelphia, PA 19120-5099.

All other commercial and industrial documents can be obtained through the respective organization’s website.

3.0 PERFORMANCE REQUIREMENTS

The following paragraphs list all required support tasks that shall be required throughout the contract life. The contractor shall provide necessary resources and knowledge to support the listed tasks. As noted, contractors shall perform requirements in accordance with Federal Acquisition Regulation (FAR) and/or Defense Federal Acquisition Regulation Supplement (DFARS). Specific objectives shall be dependent on the basic contract and the task order (TO) written against the basic contract. The contractor shall complete all required tasks while controlling and tracking performance and goals in terms of costs, schedules, and resources.

Note: In compliance with SPAWARINST 4720.1A – SPAWAR Modernization and Installation Policy, all contract installation work performed aboard Navy ships and Navy shore sites is under Installation Management Office (IMO) supervision; otherwise, a formal exemption request has been approved. In accordance with the Fleet Readiness Directorate Standard Operating Procedure (FRD SOP), COMSPAWARSYSCOM letter Ser FRD/235 dated 24 Apr 12, the contractor shall, ensure proper notification and status updates of installation work performed outside of SPAWARSYSCEN Atlantic respective Areas of Responsibilities (AORs) are provided to the SPAWAR Officer in Charge (OIC) or applicable Geographic Lead.

3.1 RELEVANT EXPERIENCE

3.1.1 Platform and System Focus Areas

The contractor shall have experience providing technical, programmatic/financial, and administrative support to DARPA/TTO for the following platform and system focus areas:

3.1.1.1 Ground Systems: Areas of interest include: enhancing the capabilities of the soldier, the squad, and ground combat vehicles; enhancing the mobility, logistics, performance, health, lethality, and survivability of individual soldiers and their ability to operate in complex environments; aggregate performance improvement of the combat squad in the conduct of their mission to include mobility, robotics, weapons, sensing, and communications; developing the next generation of combat vehicles focused on the total system performance, to include agility, extreme lethal and non-lethal precision, and survivability while minimizing weight and cost; advanced performance propulsion concepts for ground systems; platform systems which support special operations executed in a low-profile manner aimed at achieving the advantage of speed in tactical environments, surprise, and the application of overwhelming force against specified targets.

3.1.1.2 Maritime Systems: Areas of interest include: platform technologies that enable a dramatic improvement in key operating parameters; sea-based unmanned air vehicles; methods by which human operators effectively perform tasks through remote unmanned systems operations utilizing minimal data content and communications bandwidth; non-lethal approaches to disable maritime platforms; advanced extended range high speed propulsive agile torpedo engagement; innovations in rail gun, coil gun, light gas gun, and advanced cannon technologies; technologies that enable new/novel and cost-effective platform approaches; kinetic and non-kinetic defeat of non-traditional threats and high volume precision engagement; technologies that cost-effectively expand and bridge maritime and sub-surface platform use; and propulsion technologies.

3.1.1.3 Air Systems: Areas of interest include: the full range of hypersonic systems, novel air vehicles, and X-plane demonstrator technologies; air-breathing and non-air-breathing propulsion concepts, advance rotor innovations, aerodynamic structures, thermal management, guidance, navigation, flight controls, sensors, and advanced payloads. Air systems include augmentation of tailored lethality through the use of enhanced precision, electromagnetics, plasma, atmospherics, acoustics, intelligent projectiles, micro-robotics, variable yield capabilities, novel energetics, or reformulation of explosives.

3.1.1.4 Space Systems: Areas of interest include: protection and survivability of space assets; situational awareness required to effectively respond to threats; novel and affordable approaches to obtain coverage and persistence of space capabilities; and rapid, responsive, and affordable access to space and freedom of movement within the space environment. This includes: advancements in hybrid robotic/satellite technology, modular and fractionated space systems, enabling architectures adaptable to multiple space vehicles, techniques that radically reduce launch costs, technologies that enable extreme performance in space systems, and innovative power generation and propulsion for spacecraft.

3.2 TECHNICAL REQUIREMENTS

The contractor shall provide the technical and administrative personnel and expertise to accomplish the following subtasks:

3.2.1. Strategic Planning, Program Formulation and Technical Analysis

3.2.1.1 The contractor shall work with the program managers in developing and researching ideas for formulation of new programs in DARPA/TTO thrust areas.

3.2.1.2 The contractor shall assist in developing strategic and technical plans to promote the DARPA/TTO mission (CDRL A001).

3.2.1.3 The contractor shall provide research expertise and program support of government activities with regard to procurements, schedule (technical and administrative), technical risk, user impact, and technology/system transfer efforts (CDRL A001).

3.2.1.4 The contractor shall provide an in-depth, expert analyses/assessment of proposals to determine the technical merit of proposal objectives and methodologies (CDRL A002).

3.2.1.5 The contractor shall have an understanding and working relationship with the DARPA/TTO programs, government agents, performing contractors, and technical community to review and document technical progress at program reviews and to track milestones, funding profiles, and deliverables for ongoing efforts (CDRL A001).

3.2.1.6 The contractor shall assist in the development and transition of technology and systems to the user community. The contractor shall support the activities of on-going and future work and be familiar with the interaction of the technology/system program with the respective community at large. This shall require identifying and translating user requirements into specific technology/system research and development objectives; illustrating the benefits of applying the technology/system to military equipment users and developers; identifying the military and commercial utility of new products and technology/system developments; defining system architectures and supporting subsystem performance requirements; and generating transition agreements (CDRL A001).

3.2.1.7 The contractor shall conduct quantitative analyses of system mission requirements as they pertain to the potential insertion of advanced technologies; evaluate alternatives and trade-offs; evaluate costs and benefits; investigate compatibility, interoperability, and integration; and study reliability issues (CDRL A002).

3.2.1.8 The contractor shall support program experiment and testing efforts, including preparation of experiment/test plans; coordination with performers, government agents, ranges and test facilities; implementation and inspection of safety requirements (CDRL A001).

3.2.1.9 The contractor shall assemble and manage senior advisory panels consisting of subject matter experts/consultant services and/or highly skilled personnel with specialized training and background to provide studies and assessments on a wide variety of systems and technologies (CDRL A001).

3.2.1.10 The contractor shall provide technical analysis of results and experiments (CDRL A002).

3.2.1.11 The contractor shall support test demonstrations accident/investigation review boards.

3.2.1.12 The contractor shall support agency, office and program experiments, test, events and conferences, including travel and coordination, to include observation, collection, analysis and reporting test results; demonstrating and communicating agency and office projects to various audiences in support of agency outreach functions.

3.2.1.13 The contractor shall complete all required DARPA training courses in accordance with DARPA instructions.

3.3 PROGRAM PLANNING AND FINANCIAL PROCESSING

The contractor shall assist the government project manager providing support at the sponsor level.

3.3.1 The contractor shall be familiar with the DARPA financial systems and processes such as Monitor and the Defense Agency Initiative. The contractor shall be aware of the current business practice by each DARPA/TTO Program Manager for the financial execution of his or her programs. The contractor shall provide personnel expertise in preparing and tracking financial and budgetary data to ensure that the DARPA/TTO program managers can effectively plan and administer their programs and meet both the office and the agency execution benchmarks.

3.3.2 The contractor shall be familiar with the DARPA financial systems and processes to gather information and to prepare program approval documents and contract specific financial execution documentation such as Procurement Requests, Military Interdepartmental Purchase Requests (MIPRs), and other appropriate documentation.

3.3.3 The contractor shall be familiar with the DARPA/TTO programs in order to work with the program managers in strategic planning of budgetary and schedule trade-offs/variance analysis during the source selection.

3.3.4 The contractor shall be familiar with and provide inputs to centralized planning that consolidates performance, budget, and schedule information for existing and future DARPA/TTO programs. This effort shall include attending and understanding the technical reviews where DARPA obtains performing contractor’s feedback on performance and financial issues.

3.3.5 The contractor shall review all program documentation for completeness and consistency with the program goals and broader DARPA/TTO objectives.

3.4 PROGRAM CONTROL

3.4.1 The contractor shall evaluate program plans, work breakdown structures, milestone schedules, test results, contract status reports and other documentation to assess performance, report progress and advise actions necessary to bring programs into technical, schedule and cost compliance with stated objectives of the DARPA/TTO programs.

3.4.2 The contractor shall monitor program progress and conduct baseline and re-baseline analyses and assessments for DARPA/TTO programs (CDRL A001).

3.4.3 The contractor shall conduct red team reviews of programs/performers and provide recommendations for program modifications and improvements for DARPA/TTO programs.

3.4.4 The contractor shall conduct program risk/control assessments for DARPA/TTO programs.

3.4.5 The contractor shall conduct analyses of cost and schedule variances for DARPA/TTO programs.

3.4.6 The contractor shall identify probable impacts of scope/technical changes for DARPA/TTO programs.

3.5 CONFERENCE/MEETING PLANNING

3.5.1 The contractor shall provide the personnel and resources necessary to provide for planning and conducting unclassified and classified (up to TS/SCI level) technical conferences, seminars, workshops and program reviews, as specified by the DARPA/TTO staff. The contractor shall provide services to locate and secure the conference facilities (in the Arlington, VA area and in various sites throughout the US) and coordinate the conferences with other groups and individual participants.

3.5.2 Conference support services for DARPA/TTO programs will be specified at the TO level, but may include: planning, organizing, mailings, scheduling, badging, catering, agenda planning, generating/acquiring conference materials, recording minutes of meetings and proceedings preparation, record publishing, provisioning audio visual services/equipment, and providing security services. The contractor shall help facilitate these technical meetings and provide feedback to the program managers. The contractor shall have the capabilities to establish a logistical transfer system for next-day delivery of conference-related equipment, media storage, transparencies, or bulky documents to other government agencies. The contractor shall also create and/or arrange for, as required at the TO level, display and /or exhibit materials, posters, placards and presentation articles (CDRL A001).

3.5.3 The contractor shall provide the capabilities to organize, provide logistics, and host DARPA/TTO-sponsored meetings and conferences. Due to the quantity of working meetings and high number of personnel required to attend meetings per month, the contractor shall provide the capability to secure a facility located close to DARPA headquarters in Arlington, VA so as to effectively support emergent meetings with little notice due to sensitive topics in support of the program manager and/or office director.

3.5.4 Specific tasking for meetings and conferences will be specified at the TO level, but the contractor shall have the capability to support the following estimates. The government estimates that the number of meetings at the contractor’s facilities may be approximately seven to ten meetings per month (~20-30 people) for DARPA/TTO programs. he government estimates that the number of meetings in the Arlington, VA area may be four to six per month (~75-100 people). The government estimates that the meetings at various US sites may be two to four per year (~200-600 people).

3.6. PROGRAM AND TECHNICAL DOCUMENTATION

3.6.1 The contractor shall provide research, writing, editing, drafting, creation of graphics, production, and technical coordination to create, maintain, and update definitive documentation for the programs as required by the DARPA/TTO program managers. This will include creating, maintaining and archiving viewgraphs, animations/movies, speeches, white papers, videotapes or other media (CDRL A001).

3.7. DOCUMENATION MANAGEMENT AND CONTROL

3.7.1 The contractor shall manage, direct, and coordinate program documentation activities to assure these activities are compatible with technical and programmatic goals. This documentation management effort shall include:

3.7.1.1 Building and maintaining databases, including bibliographic and abstract databases, in the required computer applications environment.

3.7.1.2 Developing and maintaining a comprehensive library/technical documentation center (within a 20 minute walking time from DARPA). The library shall include secure storage for documents classified at the Top Secret level. Criteria for access to the library will be controlled by DARPA. This effort shall include the use of reproduction facilities for controlled or classified documents. In addition, the contractor shall provide reference materials (e.g., topical technical journals, market studies, reference books, textbooks, etc.), related to the above technical areas and specified by DARPA/TTO. The contractor shall provide technical literature surveys and searches. Specific requirements will be specified at the TO level, but the government estimates a requirement of approximately 10 filing cabinets worth of secure storage.

3.7.1.3 Providing resource/reference compilation, retention, logging, reproduction, retrieval and delivery of both unclassified and controlled/classified documents.

3.7.1.4 Developing and maintaining distribution and mailing lists for both classified and unclassified materials.

3.8 PROGRAM SUPPORT

The contractor shall provide the technical and administrative personnel and expertise to accomplish the following subtasks:

3.8.1 Procurement/Broad Agency Announcement Solicitation Support The contractor shall provide the necessary documentation and support for tracking DARPA/TTO procurement/solicitation activities. The contractor shall have an understanding of the government and DARPA procedures and processes for the source selection evaluation process. The contractor shall have a thorough knowledge of the DARPA/TTO source selection plan and a working relationship with the DARPA Contracts Management Office (CMO) personnel and the CMO processes and procedures. The contractor shall provide the following support:

3.8.1.1 Prepare, publish, and coordinate the DARPA/TTO Broad Agency Announcement solicitation documentation (CDRL A001);

3.8.1.2. Handle proposer inquiries, generate response letters, receive and facsimile machine (FAX)/email responses for proposer information;

3.8.1.3 Collect, analyze, and store proposal data in a central tracking system;

3.8.1.4 Distribute proposals to reviewers, collect responses and maintain complete action records (such as evaluation forms and summaries);

3.8.1.5 Track funding decisions for selected proposals;

3.8.1.6 The contractor shall have available an advanced computerized FAX, a mailing list service, and Internet services to handle procurement activities.

3.8.1.7 For planning purposes, it is anticipated that a total of 10 broad agency announcement procurements per year will occur. The contractor shall have available suitable storage containers for all proposal-related material. The contractor shall also have facilities available so that outside reviewers (determined by the government Program Manager, Scientific Review Official/Source Selection Authority and Contracting Officer) have access to the proposals. The contractor shall also work with the program manager to arrange evaluation committee meetings, briefing preparation and follow-up notification to the proposers. This will involve contacting committee members selected by DARPA/TTO and arranging for a meeting room, which could be at DARPA.

3.8.2 DARPA/TTO World Wide Web (WWW) Support

The contractor shall provide technical assistance and administrative support in updating and maintaining DARPA/TTO web sites on the WWW by performing the following:

3.8.2.1 Maintain individual program Web sites;

3.8.2.2 Provide program content for the DARPA/TTO website;

3.8.2.3 Analyze, create, update, and maintain innovative Web tools to facilitate technical, programmatic, and financial support to the DARPA/TTO program managers;

3.8.3 DARPA/TTO Administrative/Program Support

The contractor shall provide program support personnel on-site at DARPA/TTO. These program support personnel shall perform both general office duties (e.g., answering telephones, typing, and filing) and advanced administrative support activities that require independent judgment and a thorough knowledge of DARPA/TTO policies and procedures (e.g., Pentagon level interface, setting up and completing travel for the DARPA/TTO staff.) program support personnel shall be familiar with PC-based software packages including, but not limited to, MS Office Suite (Word, Excel, Power Point, Outlook Calendar, Project, Internet Explorer, and Access), Informed Filler, Adobe Reader, and the Defense Travel System.

3.9 TRANSITION PLAN/SCHEDULE/PHASING

As specified in individual task orders, the contractor shall provide a detailed Transition Plan (CDRL A001) that outlines the strategy and methodology for transitioning program support services performed under this contract to assure a smooth and effective transition between the incumbent contractor and a follow-on contractor. The Transition Plan shall describe how the contractor’s organization will be staffed, managed and ready to meet the requirements of transitioning the program support services at the end of the contract period. The Transition Plan shall identify the proposed approach to phase-in of management and technical personnel and the implementation of control procedures and methods. The contractor shall establish in the Transition Plan the management controls, procedures, and methods necessary to accomplish a phased transition of program support activities, including personnel staffing, subcontracting, procurement, status reporting, security arrangements, and documentation control, security, and transfer. The Transition Plan shall identify a phased schedule with a transition milestone chart. Requirements critical to transitioning shall be identified, including personnel training, security arrangements (controls and procedures) and documentation transfer (controls and procedures). The phased transition of the contractors technical and management data shall be fully complete and operational 30 days after any follow-on contract is awarded. The Final Transition Plan/Schedule/Phasing document (CDRL A001) should be submitted 120 days prior to the end of the contract. The transition-out plan shall be briefed and approved by DARPA/TTO not later than 60 days before the end of the existing contract period and should identify and define the plan for the transition process from this contract to the follow-on effort (if applicable).

3.10 EQUIPMENT AND MATERIAL SUPPORT

As specified on task orders, the contractor shall provide various equipment/material support that ranges from research, procurement, fabrication, integration, and delivery.

3.10.1 Equipment/Material Research

The contractor shall research specified equipment and/or material within the parameters outline at the task order.

3.10.2 Equipment/Material Procurement

Pursuant to SPAWARINST 4440.12, the contractor shall procure items listed under the Contractor Acquired Property (CAP) paragraph. The contractor shall ensure acquisition selection factors shall include price, availability, reliability, and supportability within current supply system. The contractor shall keep source selection records and make it available for government review as needed. The contractor shall provide all support data and cost estimates necessary to justify a fair and reasonable price per item procured. The contractor shall have an adequate accounting system to track all items and the delivery status per task order and per item. After receipt, the contractor shall have an adequate property management system to track the item location per task order per item. Unless otherwise noted, all items procured by the contractor shall utilized or staged at the contractor’s facility, transported by the contractor to the installation, integrated or consumed in a system, or returned to the government at the completion of the contract/TO. The contractor shall be responsible for generating inventory tracking report(s) (CDRL A003) for the basic contract and/or each task order summary report. Deliverable documentation shall vary and be specified in each TO, if applicable.

Contractor shall recommend items that conform to applicable product validation, identification, and tracking requirements.

(a) Product Validation – The contractor shall certify that it purchases supplies from authorized resellers and/or distributers. Unless otherwise specified, the contractor shall warrant that the products are new, in their original box. The contractor shall obtain all manufacturer products submitted in task/delivery order offers from authentic manufacturers or through legal distribution channels only, in accordance with all applicable laws and policies at the time of purchase. The contractor shall provide the Government with a copy of the End User license agreement, and shall warrant that all manufacturer software is licensed originally to Government as the original licensee authorized to use the manufacturer software. The contractor shall track the licensing information and have it available for government review as needed.

(b) Cybersecurity/Computer Security Requirements – The contractor shall ensure that all products recommended and/or procured that impact cybersecurity or Information Assurance (IA) shall be selected from the National Information Assurance Partnership (NIAP) Validated Products List. The contractor shall ensure the products chosen are based on the appropriate Evaluated Assurance Level (EAL) for the network involved, and utilized in accordance with latest Defense Information Systems Agency (DISA) policy at time of order. The contractor shall store all product information and have it available for government review as needed.

(c) Item Unique Identification (IUID) – In accordance with DFARS clause 252.211-7003/7007 and SECNAVINST 4440.34, the contractor shall ensure that an item manufactured, integrated, or purchased with a unit cost equal to or exceeding $5,000 (or less if item is serially managed or if government specifies items on individual task/delivery orders) is labeled with an item unique identification number or Unique Item Identifier (UII). At time of delivery of the item to the Government, the contractor shall clearly mark and identify each applicable item based on the criteria provided in DoD MIL-STD-130N for those items not already marked. The contractor shall specify the construct, syntax, marking methodology, and quality methodology chosen to mark the required parts and any corresponding technical justification. All IUID information shall be recorded and shall be subject to government review as needed. The contractor shall track IUID items and maintain information being recorded.

(i) After CAP is delivered to the government, the contractor shall enter all items with Unique Item Identifier (UII) in the IUID Registry. The contractor shall register and validate each IUID in the IUID Registry. The contractor shall submit IUID data via Invoicing, Receipt, Acceptance, and Property Transfer (iRAPT) (formerly Wide Area Workflow (WAWF)) as part of the Material Inspection and Receiving Report.

(ii) Contractor shall be responsible maintaining and updating information in the IUID Registry. Contractor shall update custody status when items are designated as government furnished material, returned to government position, change physical location, or has been consumed, destroyed, scrapped, lost or abandoned during contract/TO performance.

3.10.3 Property/Inventory Tracking

In accordance with the FAR, the contractor shall create and maintain internal records of all government property accountable to the contract/TO, including Government-furnished and Contractor-acquired property. In accordance with DFARS, the contractor shall record each item delivered and/or ordered in a Material Inspection and Receiving Report/Inventory Tracking Report (CDRL A003). At a minimum, the report shall track the following information: item description, order date, serial number, model number, lot number, delivery location, and the manufacturer warranty period and expiration date, if applicable. The contractor shall have inventory report information available for government review as needed, and the contractor shall ensure the report information has the ability to be sorted and manipulated by any of the input fields. Separate from the government tracking system, the information in the contractor’s records is a backup to the government records; therefore, the government shall own all data rights to the collected information.

3.11 Warranty Tracking of Serialized Items

As specified in DFARS and Instructions for Electronic Submission of Warranty Tracking and Administration Information for Serialized Items (see CDRL A004 Attachment 1), the contractor shall follow the requirements for any serialized item manufactured or acquired that come with a warranty:

3.11.1 For government specified warranty terms, the government will complete certain fields on the Warranty Tracking Information (WTI) form and Warranty Source of Repair Instructions (WSRI) form and electronically forwarded them to contractor. The contractor shall complete the remaining sections of the WTI and WSRI and forward the forms (CDRL A004) to the Contracting Officer and COR at time of delivery of the warranted serialized item(s).

3.11.2 For contractor/vendor specified warranty terms, the contractor shall complete all data elements for both the WTI and WSRI and shall forward the forms (CDRL A004) electronically to the tech code. The WTI shall be returned to the Contracting Officer and COR at contract/TO award. The completed WSRI shall be returned to the Contracting Officer and COR at either contract/TO award or at time of delivery of the warranted serialized item(s).

3.11.3 For receipt and acceptance of items, the contractor shall comply with the following requirements:

(a) If the WTI and WSRI are submitted manually (as a PDF file), the contractor shall forward documents to COR for review. As required, contractor shall forward approved documents to government personnel responsible for posting the forms to Electronic Data Access (EDA).

(b) If utilizing the Wide Area WorkFlow (WAWF), the contractor shall ensure that the required warranty data is electronically submitted using the Contract Data Requirements List (CDRL) exhibit line item number (ELIN) functionality for the WAWF Materiel Inspection and Receiving Report or WAWF Reparable Receiving Report, as applicable.

4.0 INFORMATION TECHNOLOGY (IT) SERVICES REQUIREMENTS

4.1 INFORMATION TECHNOLOGY (IT) GENERAL REQUIREMENTS

When applicable, the contractor shall be responsible for the following:

4.1.1 Follow DoDI 8510.01 of 12 Mar 2014 when deploying, integrating, and implementing IT capabilities.

4.1.2 Only perform work specified within the limitations of the contract/task order.

4.2 ACQUISITION OF COMMERCIAL SOFTWARE PRODUCTS, HARDWARE, AND RELATED SERVICES

If recommending or purchasing commercial software products, hardware, and related services, the contractor shall ensure they recommend or procure items from approved sources in accordance with the latest DoD policies.

4.2.1 DoD Enterprise Software Initiative Program

The contractor shall utilize the DoD Enterprise Software Initiative (ESI) program (see DFARS 208.74) and government-wide SmartBuy program (see DoD memo dtd 22 Dec 05). The contractor shall ensure any items purchased outside these programs have the required approved waivers as applicable to the program. Software requirements will be specified at the TO level.

4.3 Section 508 Compliance

The contractor shall ensure that all software recommended, procured, and/or developed is compliant with Section 508 of the Rehabilitation Act of 1973, 26 CFR Part 1194 and pursuant to SPAWARINST 5721.1B of 17 Nov 2009. In accordance with FAR 39.204, this requirement does not apply to contractor acquired software that is incidental to the task, software procured/developed to support a program or system designated as a National Security System (NSS) or if the product is located in spaces frequented only by service personnel for maintenance, repair or occasional monitoring of equipment.

5.0 CONTRACT ADMINISTRATION

Contract Administration is required for all contracts; it provides the government a means for contract management and monitoring. Regardless of the level of support, the ultimate objective of the contractor is ensuring the government’s requirements are met, delivered on schedule, and performed within budget.

5.1 CONTRACT LIAISON

The contractor shall assign a technical single point of contact, also known as the Program Manager (PM) who shall work closely with the government Contracting Officer(s) and Contracting Officer’s Representative(s) (COR), as applicable. Note: For Indefinite Delivery/Indefinite Quantity (IDIQ) contracts, CORs will be assigned at the task order level. The contractor PM, located in the contractor’s facility, shall ultimately be responsible for ensuring that the contractor’s performance meets all government contracting requirements within cost and schedule. PM shall have the requisite authority for full control over all company resources necessary for contract performance. The PM shall have authority to approve task order proposals or modifications in emergent situations. The PM shall ultimately be responsible for the following: personnel management; management of government material and assets; and personnel and facility security. In support of open communication, the contractor shall initiate, unless otherwise directed at the task order level, periodic meetings with the COR(s).

5.2 CONTRACT MONITORING AND MAINTENANCE

The contractor shall have processes established in order to provide all necessary resources and documentation during various times throughout the day in order to facilitate a timely task order (TO) award or modification. Prior to task order award, the contractor shall be responsible for providing any required support documentation in a timely manner so as to not disrupt the TO award process. To address urgent requirements, the contractor shall have processes established during business and non-business hours/days in order to provide all necessary documentation and resources to facilitate a timely TO award or modification. NOTE: Directly billing to a TO prior to TO award is prohibited.

5.2.1 Contract Administration Documentation

Various types of contract administration documents are required throughout the life of the contract. At a minimum, the contractor shall provide the following documentation, unless otherwise specified:

5.2.1.1 Contract Status Report (CSR)

The contractor shall develop a Contract Status Report (CDRL A005) and submit it monthly at least 30 days after contract award on the 15 th of each month. Only one report is submitted per contract. The prime shall be responsible for collecting, integrating, and reporting all subcontractor reports. The contractor shall report on various contract functions: schedule, financial, business relations, and staffing plan/key personnel. See applicable DD Form 1423 for additional reporting details and distribution instructions.

5.2.1.2 Task Order Status Report (TOSR)

The contractor shall develop Task Order Status Reports (CDRL A006) and submit monthly, weekly, and/or as cited in the requirements of each task order. The prime shall be responsible for collecting, integrating, and reporting all subcontractor reports. The TOSR includes the following variations of reports:

(a) Monthly TOSR – the contractor shall develop and submit a TO status report monthly at least 30 days after TO award on the 15th of each month for those months the TO is active. The contractor shall report on various TO functions: performance, schedule, financial, business relations, and staffing plan/key personnel; see applicable DD Form 1423 for additional reporting details and distribution instructions. This CDRL includes a Staffing Plan (Attachment 1), Personnel Listing (Attachment 2), and Government Furnished Property (GFP) Template (Attachment 3) necessary for additional data collection as applicable.

5.2.1.3 Task Order Closeout Report

The contractor shall develop a task order (TO) closeout report (CDRL A007) and submit it no later than 15 days before the TO completion date. Prime shall be responsible for collecting, integrating, and reporting all subcontracting information. See applicable DD Form 1423 for additional reporting details and distribution instructions.

5.2.1.4 Cybersecurity Workforce (CSWF) Report

DoD 8570.01-M and DFARS PGI 239.7102-3 have promulgated that contractor personnel shall have documented current Cybersecurity certification status within their contract. The contractor shall develop, maintain, and submit a CSWF Report (CDRL A008) monthly or as applicable at the task order level (Note: If initiated at the TO level, report not necessary at contract level). In accordance with DFARS, if cybersecurity support is provided, the contractor shall provide a Cyber Security Workforce (CSWF) list that identifies those individuals who are IA trained and certified. Utilizing the format provided in CSWF CDRL Attachment 1, the prime contractor shall be responsible for collecting, integrating, and reporting all subcontractor personnel. See applicable DD Form 1423 for additional reporting details and distribution instructions. Contractor shall verify with the COR or other government representative the proper labor category cybersecurity designation and certification requirements.

5.2.1.5 Contractor Manpower Reporting

The following reporting is required for all DoD contracts acquiring services regardless if cost type or firm-fixed price contract:

(a) Contractor Manpower Quarterly Status Report (QSR) The contractor shall provide a Contractor Manpower Quarterly Status Report (CDRL A009) to the government four times throughout the calendar year. Required by SPAWARSYSCEN Atlantic for all active service contracts/TOs (regardless if fixed-price or cost type), the Manpower report itemizes specific contract and/or TO administrative data for SPAWARSYSCEN Atlantic. Reporting period begins at the time of contract/TO award. Utilizing the format provided in QSR CDRL Attachment 1, the contractor shall collect required data throughout the specified performance period and shall submit one cumulative report on the applicable quarterly due date. See applicable DD Form 1423 for additional reporting details and distribution instructions. The following table lists the pre-set submittal due dates and the corresponding performance periods:

(b) Enterprise-wide Contractor Manpower Reporting Application In addition to the QSR CDRL reporting requirements noted above and pursuant to NMCARS 5237.102-90, the contractor shall report all contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the DoD via a secure data collection website – Enterprise-wide Contractor Manpower Reporting Application (eCMRA). Contracted services excluded from reporting are based on Product Service Codes (PSCs). The excluded PSCs are:

The contractor shall completely fill-in all required data fields using the following web address: https://doncmra.nmci.navy.mil/.

Reporting inputs consists of labor hours executed during the contract/TO period of performance within each Government fiscal year (FY) which runs from October 1 through September 30. While inputs may be reported any time during the FY, the contractor shall report all data no later than October 31 of each calendar year. Contractors may direct questions to the help desk at http://www.ecmra.mil/.

5.2.1.6 WAWF Invoicing Notification and Support Documentation Pursuant to DFARS, the contractor shall submit payment requests and receiving reports using DoD Invoicing, Receipt, Acceptance, and Property Transfer (iRAPT) application (part of the Wide Area Work Flow (WAWF) e-Business Suite) which is a secure government Web-based system for electronic invoicing, receipt, and acceptance. The contractor shall provide e-mail notification to the COR when payment requests are submitted to the iRAPT/WAWF and the contractor shall include cost back–up documentation (e.g., delivery receipts, time sheets, & material/travel costs, etc.) to the invoice in iRAPT/WAWF. As requested, the contractor shall directly provide a soft copy of the invoice and any supporting invoice documentation (CDRL A010) directly to the COR within 24 hours of request to assist in validating the invoiced amount against the products/services provided during the billing cycle.

5.3 CONTRACT ORGANIZATIONAL CONFLICT OF INTEREST (OCI)

Due to the type of work performed, there are organizational conflict of interest clauses that are applicable to this contract. The contract shall follow the restrictions as cited in Section H of the contract.

5.3.1 Purpose of the Contract Organization Conflict of Interest clause The primary purpose of this clause is to ensure that:

(a) The Contractor's objectivity and judgment are not biased because of its past, present, or currently planned interests (financial, contractual, organizational, or otherwise), which relate to work performed under this contract.

(b) The Contractor does not obtain an unfair competitive advantage by virtue of its access to non-public information regarding the Government's program plans and actual, or anticipated, resources

(c) By virtue of its access to proprietary information belonging to others, the Contractor does not obtain any unfair competitive advantage.

5.3.2 Scope of the Contract Organizational Conflict of Interest clause The restrictions described herein shall apply to performance or participation by the Contractor and any of its affiliates or their successors in interest (hereafter collectively referred to as "Contractor") in the activities covered by this clause as prime contractor, subcontractor, cosponsor, joint venture, or in any similar capacity.

(a) Maintenance of Objectivity: The Contractor shall be ineligible to participate (in any capacity) in any…